Hi, >From Section 4 (Client Behaviour) part of this draft, I understood that primary objective of this draft is to give >indication to UAC to release resources, if any. I am little worried about extra messaging that will be seen because of >199 implementation. Can there be a way to tell proxies and UAS downstream that UAC has some resources reserved for this >call and would be interested in receiving 199, if possible? > >IMO, UAC (mostly) is in better understanding of the resources that it has reserved for a particular call. So UAC can >selectively add something in INVITE to tell downstream proxies/ UAS' about its interest. > >IMO, we can have a package for 199 and UAC can use "Supported" header to indicate entities downstream that it would be >interested in getting 199 for this *particular* call. Implicitly it would mean that UAC has reserved some resources. I >understand that we would changing the meaning of "Supported" header on per call basis :-(. Something else may be?
I am not sure you would "break" anything by using Supported "per call". As far as I know, it is nowhere said that a UAC must included the same option-tags in the Supported header for every call it makes... It is true that the primary objective is to give the indication to the UAC, but in some environments there could also be intermediates (P-CSCF controlling PCC in IMS for example) that are interested in this indication. 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
