Hi Holger,
MESSAGE request size may grow beyond 1300 bytes en-route to UAS, but UAC must ensure that it doesn't send a request that is more than 1300 bytes. 1300 is taken from hop-to-hop transport layer requirement, but in the case of MESSAGE it is applied end-to-end for better congestion control. Ramakrishna -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Holger Schmidt Sent: Wednesday, November 09, 2005 7:58 PM To: [email protected] Subject: [Sip-implementors] SIP MESSAGE request Dear all, I have a question regarding SIP MESSAGE request specified in RFC 3428. It specifies that ... """ The size of MESSAGE requests outside of a media session MUST NOT exceed 1300 bytes, unless the UAC has positive knowledge that the message will not traverse a congestion-unsafe link at any hop, or that the message size is at least 200 bytes less than the lowest MTU value found en route to the UAS. Larger payloads may be sent as part of a media session, or using some type of content-indirection. """ How can I guarantee that the message will not grow above this 1300 bytes limit when being routed through a chain of proxies (which add their via headers -> increases the message size...) Any help would be appreciated. Thank you, Holger _______________________________________________ Sip-implementors mailing list [email protected] http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors Confidentiality Notice The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain confidential or privileged information. If you are not the intended recipient, please notify the sender at Wipro or [EMAIL PROTECTED] immediately and destroy all copies of this message and any attachments. _______________________________________________ Sip-implementors mailing list [email protected] http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
