Re: INFO Framework - one pakage per INFO

Paul Kyzivat wrote:
> 
> 
> Eric Burger wrote:
>> Let us try again.
>>
>> INFO is a method that *transports* Application-Level "messages".
>>
>> INFO is NOT a method of Application-Level messaging.
> 
> I guess you are asserting the above, right?
> 
> Its possible that is what the original authors of INFO intended, though
> it isn't entirely clear to me if that is the case.\

I believe that's what we meant :-)

If a UAS doesn't understand the body of an INFO, it presumably sends a
415 (like it would for any other required body part it doesn't understand).

I quote from RFC 2976:

      If the INFO request contains a body that the server does not
      understand then, in the absence of INFO associated processing
      rules for the body, the server MUST respond with a 415 Unsupported
      Media Type message.

This is significant for choosing which of several alternative body types
might be supported for a given package.

If the "not understood" is at the level of the application state, fixing
that is an application problem, not a problem for the SIP protocol. Fix
it in the package, not the transport.

--
Dean
_______________________________________________
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