I don't remember any history of this, but would contend that the way RFC 3903 text is written in regards to bodies in responses is tantamount to saying "bodies in responses is for further study". It is basically trying to say, if in implementing this you receive a body in a response, then don't start failing things at the SIP transaction level.
And remember, this requires an event package to define the usage, and you need RFCs to define event packages, so I suspect any expert review or above would take a very deep look at any such definition. Keith > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On > Behalf Of Hadriel Kaplan > Sent: Monday, December 01, 2008 10:41 PM > To: Eric Burger; Anders Kristensen > Cc: SIP List > Subject: Re: [Sip] INFO Framework - one pakage per INFO > > Umm, wouldn't it only keep it for the duration of a > transaction lifetime, which is the same as it would have to > do if it were to send it in an upstream INFO request? > > PUBLISH, for example, does this doesn't it? You don't > respond to a PUBLISH until you've fully processed the publish > request, including all Event Package body content. (and both > request and response can have bodies for their event package) > > -hadriel > > > > -----Original Message----- > > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On > Behalf Of > > Eric Burger > > Sent: Monday, December 01, 2008 5:21 PM > > To: Anders Kristensen > > Cc: SIP List > > Subject: Re: [Sip] INFO Framework - one pakage per INFO > > > > What you are asking for is the UAS to keep state > indefinitely on each > > 200 OK, because the UAC may or may not be there to retransmit the > > first INFO request. That does not sound like an ideal design. > _______________________________________________ > 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 > _______________________________________________ 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
