>From bis-09: 7.3.3 Compact Form
SIP provides a mechanism to represent common header field names in an abbreviated form. This may be useful when messages would otherwise become too large to be carried on the transport available to it (exceeding the maximum transmission unit (MTU) when using UDP, for example). These compact forms are defined in Section 20. A compact form MAY be substituted for the longer form of a header field name at any time without changing the semantics of the message. A header field name MAY appear in both long and short forms within the same message. Implementations MUST accept both the long and short forms of each header name. so the answers are: 1. Yes 2. No 3. Yes - rob -----Original Message----- From: Vishal [mailto:[EMAIL PROTECTED]] Sent: Tuesday, June 04, 2002 6:13 AM To: [EMAIL PROTECTED] Subject: [Sip-implementors] compact encoding Hi , I have following questions regarding compact encoding of sip header fields 1. should sip message be considered valid if it contains long and short field notations simultaneously? 2. Is there any header field available which informs whether sip message is using long or short field names ? 3. Is it manatory to have compact encoding support at sip application? regards, vishal _______________________________________________ Sip-implementors mailing list [EMAIL PROTECTED] http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors _______________________________________________ Sip-implementors mailing list [EMAIL PROTECTED] http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
