Does anyone read the draft before they comment? Folks have been saying, "What would an INFO with multiple body parts look like?"
READ PAGES 31-32!!!
The example there uses a Content-ID of abcd9999qq and abcd1234zz. Does not look like a URI to me...
On Nov 30, 2008, at 12:28 PM, Hadriel Kaplan wrote:
-----Original Message----- From: Christer Holmberg [mailto:[EMAIL PROTECTED] Sent: Sunday, November 30, 2008 7:12 AM Hi, This is what I was afraid of...I think that having to use URIs in order to recognize the info packageis anything but simple...Agreed. But I don't think we need to. Legacy INFO is already deployed. Subscribe/Notify is already deployed. UPDATE is already deployed. MESSAGE is already deployed. None of them use a CID for the body part that is germane to their method's context, AFAIK. It is up to the piggy-backer uses that want to add other body-parts to use CID for their parts. For example, if you wanted to add a body part for geo-loc to a Notify message that was sent for a presence package, the Geolocation header would contain a CID, not the Event header.This "problem" already exists for current SIP messages, and it's up to the new extensions that add body-parts to solve it in a backward- compatible way for all message methods. We don't need to solve it specifically for INFO.-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
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ 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
