[Sip] Protocol Action: 'Session Initiation Protocol Extension Header Field for Service Route Discovery During Registration' to Proposed Standard

The IESG <iesg-secretary@ietf.org> Fri, 01 August 2003 19:07 UTC

Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA05103 for <sip-archive@odin.ietf.org>; Fri, 1 Aug 2003 15:07:41 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19ifFF-0008Fz-1N for sip-archive@odin.ietf.org; Fri, 01 Aug 2003 15:07:17 -0400
Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h71J7HVf031735 for sip-archive@odin.ietf.org; Fri, 1 Aug 2003 15:07:17 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19ifE3-00087q-3X; Fri, 01 Aug 2003 15:06:03 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19ifDV-000874-Bb for sip@optimus.ietf.org; Fri, 01 Aug 2003 15:05:29 -0400
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA04799 for <sip@odin.ietf.org>; Fri, 1 Aug 2003 15:05:22 -0400 (EDT)
Received: from apache by asgard.ietf.org with local (Exim 4.14) id 19ifCg-0006o7-GF; Fri, 01 Aug 2003 15:04:38 -0400
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce:;
Cc: Internet Architecture Board <iab@iab.org>, RFC Editor <rfc-editor@rfc-editor.org>, sip@ietf.org
Message-Id: <E19ifCg-0006o7-GF@asgard.ietf.org>
Date: Fri, 01 Aug 2003 15:04:38 -0400
Subject: [Sip] Protocol Action: 'Session Initiation Protocol Extension Header Field for Service Route Discovery During Registration' to Proposed Standard
Sender: sip-admin@ietf.org
Errors-To: sip-admin@ietf.org
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sip>, <mailto:sip-request@ietf.org?subject=unsubscribe>
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sip>, <mailto:sip-request@ietf.org?subject=subscribe>

The IESG has approved the Internet-Draft 'Session Initiation Protocol 
Extension Header Field for Service Route Discovery During Registration' 
<draft-ietf-sip-scvrtdisco-04.txt> as a Proposed Standard. This document is 
the product of the Session Initiation Protocol Working Group. The IESG 
contact persons are Allison Mankin and Jon Peterson.

Technical Summary
                                                                                
            This document defines a SIP extension header field used in
            conjunction with responses to REGISTER requests to provide a
            mechanism by which a registrar may inform a registering User
            Agent (UA), that is, an end-user, of a service route that the UA
            may use to request outbound services from the registrar's domain.
                                                                                
            SIP has a Route Header which is used to loose source route
            messages, and this Service Route extension allows providers to
            offer plans in which a user can ensure that they visit a provider's
            proxy at which they registered. IETF protocols should neither favor
            nor preclude* such capabilities. Security for the user and the
            provider are provided by the use of the SIP sips: address of record
            mandating that the hops be carried over TLS, and use of S/MIME for
            the bodies in the messages.
                                                                                
                                                                                
Working Group Summary
                                                                                
            There was active review. This document was split out from
            the other direction, called the PATH header and worked on until
            it had adequate clarity and security. Its current version has
            good consensus.
                                                                                
                                                                                
Protocol Quality
                                                                                
        This document has been reviewed for the IESG by Rohan Mahy and
        and Allison Mankin. Some implementations were tested in recent
        interoperability events.


_______________________________________________
Sip mailing list  https://www1.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sipping@ietf.org for new developments on the application of sip