Hi, >>This is what I was afraid of... > >>I think that having to use URIs in order to recognize the info package is 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.
Sounds ok. But, doesn't the Info-Package header syntax still have to allow the piggy-backer to: 1) List multiple info packages 2) For each listed info package, provide the cid ? Regards, Christer _______________________________________________ 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
