0.30
2008-09-23
@@ -36,6 +42,7 @@
Clarified that session-accept action accepts only the content definition(s) in the session-initiate.
Added optional thread element.
Clarified tie breaks for transport-replace.
+ Modified namespaces to incorporate namespace versioning.
Cleaned up XML schemas.
@@ -955,6 +962,11 @@ PENDING o----------------------+ |
Which party originally generated the content type (used to prevent race conditions regarding modifications); the defined values are "initiator" and "responder" (where the default is "initiator"). |
REQUIRED |
+
+ disposition |
+ How the content definition is to be interpreted by the recipient. The meaning of this attribute matches the "Content-Disposition" header as defined in &rfc2183; and applied to SIP by RFC 3261. The value of this attribute SHOULD be one of the values registered in the &ianadispositions;. The default value of this attribute is "session". |
+ OPTIONAL |
+
name |
A unique name or identifier for the content type according to the creator, which MAY have meaning to a human user in order to differentiate this content type from other content types (e.g., two content types containing video media could differentiate between "room-pan" and "slides"). |
@@ -1220,7 +1232,9 @@ PENDING o----------------------+ |
-
+
@@ -1228,8 +1242,16 @@ PENDING o----------------------+ |
-
-
+
+
+