Document Action: 'NAT Traversal Practices for Client-Server SIP' to Informational RFC (draft-ietf-sipping-nat-scenarios-15.txt)

The IESG <iesg-secretary@ietf.org> Fri, 13 May 2011 21:49 UTC

Return-Path: <iesg-secretary@ietf.org>
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1A638E085D for <ietf-announce@ietfa.amsl.com>; Fri, 13 May 2011 14:49:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level:
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fTM8a26jugsb; Fri, 13 May 2011 14:49:44 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 376CBE089C; Fri, 13 May 2011 14:49:44 -0700 (PDT)
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Subject: Document Action: 'NAT Traversal Practices for Client-Server SIP' to Informational RFC (draft-ietf-sipping-nat-scenarios-15.txt)
X-Test-IDTracker: no
X-IETF-IDTracker: 3.54
Message-ID: <20110513214944.1680.25055.idtracker@ietfa.amsl.com>
Date: Fri, 13 May 2011 14:49:44 -0700
Cc: RFC Editor <rfc-editor@rfc-editor.org>
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf-announce>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 13 May 2011 21:49:45 -0000

The IESG has approved the following document:
- 'NAT Traversal Practices for Client-Server SIP'
  (draft-ietf-sipping-nat-scenarios-15.txt) as an Informational RFC

This document has been reviewed in the IETF but is not the product of an
IETF Working Group.

The IESG contact person is Robert Sparks.

A URL of this Internet Draft is:
http://datatracker.ietf.org/doc/draft-ietf-sipping-nat-scenarios/




          Technical Summary
             Traversal of the Session Initiation Protocol (SIP) and the
             sessions it establishes through Network Address Translators 
             (NATs) is a complex problem.  Currently there are many deployment
             scenarios and traversal mechanisms for media traffic.  
             This document aims to provide concrete recommendations and 
             a unified method for NAT traversal as well as documenting 
             corresponding flows.

          Working Group Summary
             Much of the development of this document took place in the SIPPING WG
             where it had strong support.
             
          Document Quality
             This document defines no new protocol elements.
             Earlier versions of the document were thoroughly reviewed within the SIPPING WG. 
             Francois Audet, Vijay Gurbani, Dan Wing, Ali Keranen and 
             Jerry Yin provided detailed WG reviews of the document. 
             In addition, area/cross-area reviews were done by 
             Remi Denis-Courmant (BEHAVE/TSV area) and Philip Matthews (RAI area).
             Dan Wing provided a final review ensuring that the technical 
             details align with the more recently published BEHAVE WG 
             documents (e.g., TURN)

          Personnel
             Mary Barnes is the WG chair shepherd. Robert Sparks is the
             responsible Area director. 

RFC Editor Note:

  Please change the title of the document as follows:

  OLD:
    Best Current Practices for NAT Traversal for Client-Server SIP
  NEW:
    NAT Traversal Practices for Client-Server SIP