Hi, Based on the discussions in Dublin, it was agreed to move forward with 199 based on the following assumptions:
- We will not define an option-tag for 199 support. - We will remove any text talking about adding a sipfrag body into the 199 response (potential future usage of 199 e.g. to solve HERFP would define such procedures) - A UAS IS allowed to send 199 (see more in the remaining open issues section further down). Please let me know if you have strong objections to any of these. OPEN ISSUES, which we need to solve are: 1) Is a proxy allowed to send 199 in the first place, or are only UASes allowed to do it? 2) Assuming proxies are allowed to send 199 (see issue 1), are proxies allowed to send 199 reliably? It would mean that they need to terminate the associated PRACK, which is claimed to not be normal proxy behavior. 3) Assuming proxies are allowed to send 199 (see issue 1), are proxies allowed to send 199 unreliably, even if 100rel is required? Claims for: - Since 199 is only an indciation, it can be seen as something similar to 100 Trying, which is never sent reliably - Proxies are not affected by the Require header, so even if the request contains 'Require: 100rel' it does not affect proxies Claims against: - It is not normal proxy behvior to trigger and send a non-100 response in the first place. 4) Is it a MAY/RECOMMENDATION/SHOULD/MUST for UAS to send 199? Please give your opinions :) 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
