From - Tue Jun 25 09:16:39 2002 X-Mozilla-Status: 0001 X-Mozilla-Status2: 00000000 Return-Path: Received: from opus.cs.columbia.edu (opus.cs.columbia.edu [128.59.20.100]) by magnum.cs.columbia.edu (8.11.6/8.9.3) with ESMTP id g5OM7Op23328; Mon, 24 Jun 2002 18:07:24 -0400 Received: from optimus.ietf.org (ietf.org [132.151.1.19]) by opus.cs.columbia.edu (8.12.1/8.12.1) with ESMTP id g5OM7Npe022018; Mon, 24 Jun 2002 18:07:24 -0400 (EDT) Received: from optimus.ietf.org (localhost [127.0.0.1]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id RAA19055; Mon, 24 Jun 2002 17:47:37 -0400 (EDT) Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id RAA18996 for ; Mon, 24 Jun 2002 17:47:33 -0400 (EDT) Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA03339; Mon, 24 Jun 2002 17:46:45 -0400 (EDT) Message-Id: <200206242146.RAA03339@ietf.org> To: IETF-Announce: ; Cc: RFC Editor , Internet Architecture Board , sip@ietf.org, sipping@ietf.org From: The IESG Date: Mon, 24 Jun 2002 17:46:45 -0400 Subject: [Sipping] Protocol Action: The Reason Header Field for the Session Initiation Protocol to Proposed Standard Sender: sipping-admin@ietf.org Errors-To: sipping-admin@ietf.org X-Mailman-Version: 1.0 Precedence: bulk List-Id: SIPPING Working Group (applications of SIP) X-BeenThere: sipping@ietf.org The IESG has approved publication of the following Internet-Drafts as Proposed Standards: o The Reason Header Field for the Session Initiation Protocol o SIP Extension for Registering Non-Adjacent Contacts These documents are the product of the Session Initiation Protocol Working Group and the Session Initiation Proposal Investigation Working Group. The IESG contact persons are Allison Mankin and Scott Bradner. Technical Summary The document 'The Reason Header Field for the Session Initiation Protocol' defines a header field, Reason, that can be used to say why a particular SIP request was issued. The same SIP request can be issued for a variety of reasons. For example, a SIP CANCEL request can be issued if the call has completed on another branch or was abandoned before answer. While the protocol and system behavior is the same in both cases, namely, alerting will cease, the user interface may well differ. In the second case, the call may be logged as a missed call, while this would not be appropriate if the call was picked up elsewhere. The Reason header field is also intended to be used to encapsulate a final status code in a provisional response. This functionality is needed to resolve the "Heterogeneous Error Response Forking Problem", or HERFP. The document 'Session Initiation Protocol Extension Header Field for Registering Non-Adjacent Contacts' defines a SIP extension header "Path" which can be used when network topology may have one or more SIP proxies between the UA and the registrar, such that any request traveling from the user's home network to the registered UA must traverse these proxies. The Path header is used to discover and record the sequence of proxies in the registrar. Working Group Summary The SIP working group supported publication of these documents. Both were deemed to have broad applicability and merit the extension of the set of SIP headers. Protocol Quality These documents were reviewed for the IESG by Allison Mankin. Note to RFC Editor: The "protocol" item in the ABNF says: protocol = SIP / Q.850 / token but SIP and Q.850 are literal strings, so it should say: protocol = "SIP" / "Q.850" / token _______________________________________________ Sipping mailing list https://www1.ietf.org/mailman/listinfo/sipping This list is for NEW development of the application of SIP Use sip-implementors@cs.columbia.edu for questions on current sip Use sip@ietf.org for new developments of core SIP