Hadriel Kaplan wrote:
> 
>> -----Original Message-----
>> From: Brett Tate [mailto:[EMAIL PROTECTED]
>> Sent: Tuesday, March 18, 2008 1:54 PM
>> To: Paul Kyzivat; Hadriel Kaplan
>> Cc: [email protected]
>> Subject: RE: [Sip] Comment/question on draft-ietf-sip-body-handling-01.txt
>>
>>> I could be convinced that there should be some normative
>>> specification of the *minimum* message size that all sip
>>> clients and servers MUST be prepared to support.
>> RFC 3261 section 18.1.1 currently provides a normative minimum:
>> "However, 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."
>>
>> Are devices actually exceeding the minimum required by RFC 3261?
> 
> Yes.  Some folks think >1MB is ok.  I think they're nuts. :)
> 
>> Or are
>> vendors interpreting "handle" as though it is valid to return failure
>> responses because of size even though less than the normative minimum to
>> handle?
> 
> Yes.  That section of 3261 is about messages - it says nothing about bodies.  
> Some devices reject requests with bodies that exceed a length, where that 
> length is less than the full 64k for the whole message.  For example, one of 
> my companies' products will reject a SIP message with an overall body bigger 
> than 32KB by default.  It's configurable, but I think we're compliant to 
> reject such by default.

Well, a message includes the body. At least in the case of a proxy I 
think it would be unreasonable to claim that you support a message that 
large yet reject the message because the body is too large.

Aside from an overall limit on message size, IMO a node ought not reject 
a message because some body part it doesn't process is "too large" for 
it. If it has reason to process the body part then perhaps it may have 
cause to reject a part that is too large.

        Paul

> -hadriel
> 
_______________________________________________
Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use [EMAIL PROTECTED] for questions on current sip
Use [EMAIL PROTECTED] for new developments on the application of sip

Reply via email to