Last Call: <draft-ietf-sipping-nat-scenarios-15.txt> (Best Current Practices for NAT Traversal for Client-Server SIP) to Informational RFC

The IESG <iesg-secretary@ietf.org> Fri, 18 February 2011 22:32 UTC

Return-Path: <iesg-secretary@ietf.org>
X-Original-To: ietf-announce@core3.amsl.com
Delivered-To: ietf-announce@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 5EA3D3A6D71 for <ietf-announce@core3.amsl.com>; Fri, 18 Feb 2011 14:32:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.498
X-Spam-Level:
X-Spam-Status: No, score=-102.498 tagged_above=-999 required=5 tests=[AWL=0.101, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lam4i9GoFzFR for <ietf-announce@core3.amsl.com>; Fri, 18 Feb 2011 14:32:53 -0800 (PST)
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 432FE3A6DB1 for <ietf-announce@ietf.org>; Fri, 18 Feb 2011 14:32:53 -0800 (PST)
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: Last Call: <draft-ietf-sipping-nat-scenarios-15.txt> (Best Current Practices for NAT Traversal for Client-Server SIP) to Informational RFC
X-Test-IDTracker: no
X-IETF-IDTracker: 3.12
Message-ID: <20110218223253.14754.86592.idtracker@localhost>
Date: Fri, 18 Feb 2011 14:32:53 -0800
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: ietf@ietf.org
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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, 18 Feb 2011 22:32:54 -0000

The IESG has received a request from an individual submitter to consider
the following document:
- 'Best Current Practices for NAT Traversal for Client-Server SIP'
  <draft-ietf-sipping-nat-scenarios-15.txt> as an Informational RFC

The IESG plans to make a decision in the next few weeks, and solicits
final comments on this action. Please send substantive comments to the
ietf@ietf.org mailing lists by 2011-03-18. Exceptionally, comments may be
sent to iesg@ietf.org instead. In either case, please retain the
beginning of the Subject line to allow automated sorting.

Abstract

   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 provides
   concrete recommendations and a unified method for NAT traversal as
   well as documenting corresponding flows.


The file can be obtained via
http://datatracker.ietf.org/doc/draft-ietf-sipping-nat-scenarios/

IESG discussion can be tracked via
http://datatracker.ietf.org/doc/draft-ietf-sipping-nat-scenarios/



No IPR declarations have been submitted directly on this I-D.