I agree that SIP allows UDP fragmentation. However for vulnerability reasons, UDP fragmentation support is disabled within some deployments.
Including requests within responses is discussed within the following expired draft. See security section for reason others than size. http://tools.ietf.org/html/draft-ietf-sip-hop-limit-diagnostics-03 > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On > Behalf Of Scott Lawrence > Sent: Tuesday, September 23, 2008 11:28 AM > To: Iñaki Baz Castillo > Cc: Sip-implementors@lists.cs.columbia.edu > Subject: Re: [Sip-implementors] respone code for wrong routed > SIP request > > > On Tue, 2008-09-23 at 16:21 +0200, Iñaki Baz Castillo wrote: > > 2008/9/23, Klaus Darilion <[EMAIL PROTECTED]>: > > > > > > it would also be helpful to include the request as a > > > message/sipfrag > body in the response, since this gives > the sender > > > some hope of > understanding how the request reached the > wrong place. > > > > > > > > > Sounds useful. Nevertheless I wonder why there is no dedicated > > > response code. > > > > I think that is dangerous since a SIP reply containing a > request would > > have a greater size that could not be sent via UDP. > > RFC 3261, section 18.1: > > implementations MUST be able to handle messages up to the maximum > datagram packet size. For UDP, this size is 65,535 bytes, > including > IP and UDP headers. _______________________________________________ Sip-implementors mailing list Sip-implementors@lists.cs.columbia.edu https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
