Protocol Action: 'Usage of the Session Description Protocol (SDP) Alternative Network Address Types (ANAT) Semantics in the Session Initiation Protocol (SIP)' to Proposed Standard
The IESG <iesg-secretary@ietf.org> Wed, 01 December 2004 19:34 UTC
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA15386; Wed, 1 Dec 2004 14:34:34 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CZaKh-0001iE-7r; Wed, 01 Dec 2004 14:40:11 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CZZTg-0006Oo-H3; Wed, 01 Dec 2004 13:45:24 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CZYk4-0002dF-At; Wed, 01 Dec 2004 12:58:16 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA04438; Wed, 1 Dec 2004 12:58:13 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CZYpQ-0006vS-1L; Wed, 01 Dec 2004 13:03:48 -0500
Received: from apache by megatron.ietf.org with local (Exim 4.32) id 1CZXyx-0002qJ-DO; Wed, 01 Dec 2004 12:09:35 -0500
X-test-idtracker: no
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Message-Id: <E1CZXyx-0002qJ-DO@megatron.ietf.org>
Date: Wed, 01 Dec 2004 12:09:35 -0500
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 82c9bddb247d9ba4471160a9a865a5f3
Cc: sip mailing list <sip@ietf.org>, sip chair <rohan@ekabal.com>, Internet Architecture Board <iab@iab.org>, sip chair <dean.willis@softarmor.com>, RFC Editor <rfc-editor@rfc-editor.org>
Subject: Protocol Action: 'Usage of the Session Description Protocol (SDP) Alternative Network Address Types (ANAT) Semantics in the Session Initiation Protocol (SIP)' to Proposed Standard
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: ietf-announce.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
Sender: ietf-announce-bounces@ietf.org
Errors-To: ietf-announce-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 02ec665d00de228c50c93ed6b5e4fc1a
The IESG has approved the following document: - 'Usage of the Session Description Protocol (SDP) Alternative Network Address Types (ANAT) Semantics in the Session Initiation Protocol (SIP) ' <draft-ietf-sip-anat-usage-00.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 describes how to use the Alternative Network Address Types (ANAT) semantics of the SDP grouping framework in SIP. In particular, we define the sdp-anat SIP option-tag. This SIP option-tag ensures that SDP session descriptions using ANAT are only handled by SIP entities with ANAT support. The document describes the issues if SIP entities interpret ANAT media grouping without the expectation that an option-tag will identify them. ANAT media groupings allow a SIP entity to signal its peer that it has both IPv4 and IPv6 address support (within SDP's ability to express both families). There is no presumption of how these addresses should be chosen by the two peers, but the ANAT grouping in SDP supports the application's use of ICE (Interactive Connectivity Establishment) RFC 3424-aware NAT traversal methodology. Working Group Summary This draft was developed because draft-ietf-mmusic-anat required a SIP option-tag for use with SIP. The SIP Working Group supported working group adoption and advancement of the draft. Protocol Quality The specification was reviewed for the IESG by Allison Mankin. Some discussion was needed to require strong error handling. RFC Editor Note: Expand the first appearance of ANAT in the Abstract and the Introduction - Alternative Network Address Types Security Considerations OLD: The natural choice to integrity protect header fields in SIP is S/MIME. NEW: The natural choice to integrity protect header fields in SIP is S/MIME. [RFC3853] And please add a normative reference to RFC 3853. _______________________________________________ IETF-Announce mailing list IETF-Announce@ietf.org https://www1.ietf.org/mailman/listinfo/ietf-announce