Some comments on this draft. I apologize if they are duplicates. Section 5 should only allow the UAS to send a 199 if it sent a dialog creating (101-199) provisional response. I know its implicit, but needs to be explicitly stated to prevent extra traffic. Suggest something like this:
When a UAS wants to terminate an INVITE server transaction it sends a non-2xx SIP final response, as specified in [RFC3261]. In addition, if the UAS has previously sent a dialog creating 1xx response (101-199) for the transaction, then prior to sending the non-2xx SIP final response, the UAS MAY send a 199 response to indicate that the early dialog is being terminated. The 199 response MUST have the same tag in the To header as sent in the dialog creating 1xx response. In section 6 requires a forking proxy to send 199s for all early dialogs associated with the non-2xx response. However, if there are multiple forking proxies along the path (or some UASs send 199s), that could result in multiple 199's for a given dialog. IMO, if the proxy has already forwarded a 199 for a given dialog, it should not send one of its own. On the topic of UAS's sending 199, I actually think things will work better if they did. I know there has been lots of discussion about B2BUAs doing it, but consider a UAS that is aware that it has multiple registered contacts (via presence or registration event package or other means), it might want to send the 199 to be sure that it does reach the UAC (in case the proxy does not support it). Section 8 Open Issues: IMO, the 199's To-tag should identify the dialog being terminated. IMO, the 199's body MAY contain message/sipfrag with the non-2xx response code and important headers like Warning. cheers, (-:bob -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED] Sent: Friday, May 23, 2008 1:15 PM To: [EMAIL PROTECTED] Cc: [email protected] Subject: [Sip] I-D ACTION:draft-ietf-sip-199-00.txt A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Session Initiation Protocol Working Group of the IETF. Title : Response Code for Indication of Terminated Dialog Author(s) : C. Holmberg Filename : draft-ietf-sip-199-00.txt Pages : 9 Date : 2008-5-15 This specification defines a new SIP response code, 199 Early Dialog Terminated, which a SIP entity can use to indicate upstream that an early dialog has been terminated. The response code can be used by a SIP entity, normally a forking SIP proxy, to allow the UAC to know that an early dialog has been terminated before it a final response is sent to the request. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-sip-199-00.txt Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. _______________________________________________ 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
