[NSIS] FW: New Version Notification for draft-ietf-nsis-nslp-natfw-22

"Martin Stiemerling" <Stiemerling@nw.neclab.eu> Wed, 03 February 2010 15:06 UTC

Return-Path: <Stiemerling@nw.neclab.eu>
X-Original-To: nsis@core3.amsl.com
Delivered-To: nsis@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 54C7C3A67B2 for <nsis@core3.amsl.com>; Wed, 3 Feb 2010 07:06:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.382
X-Spam-Level:
X-Spam-Status: No, score=-2.382 tagged_above=-999 required=5 tests=[AWL=0.217, BAYES_00=-2.599]
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 2+Ze1KsVzXy7 for <nsis@core3.amsl.com>; Wed, 3 Feb 2010 07:06:47 -0800 (PST)
Received: from smtp0.neclab.eu (smtp0.neclab.eu [195.37.70.41]) by core3.amsl.com (Postfix) with ESMTP id B3CA13A6991 for <nsis@ietf.org>; Wed, 3 Feb 2010 07:06:43 -0800 (PST)
Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp0.neclab.eu (Postfix) with ESMTP id 04C122C01D47B for <nsis@ietf.org>; Wed, 3 Feb 2010 16:07:26 +0100 (CET)
X-Virus-Scanned: Amavisd on Debian GNU/Linux (atlas2.office)
Received: from smtp0.neclab.eu ([127.0.0.1]) by localhost (atlas2.office [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id glj9Vbebd+4s for <nsis@ietf.org>; Wed, 3 Feb 2010 16:07:25 +0100 (CET)
Received: from VENUS.office (mx2.office [192.168.24.15]) by smtp0.neclab.eu (Postfix) with ESMTP id DF6922C000352 for <nsis@ietf.org>; Wed, 3 Feb 2010 16:07:20 +0100 (CET)
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: base64
Date: Wed, 03 Feb 2010 16:07:20 +0100
Message-ID: <547F018265F92642B577B986577D671C01165C13@VENUS.office>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: New Version Notification for draft-ietf-nsis-nslp-natfw-22
Thread-Index: Acqk4bkSBOoM0zF/R6GOox6kzVsR6AAAMkTw
From: Martin Stiemerling <Stiemerling@nw.neclab.eu>
To: NSIS <nsis@ietf.org>
Subject: [NSIS] FW: New Version Notification for draft-ietf-nsis-nslp-natfw-22
X-BeenThere: nsis@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Next Steps in Signaling <nsis.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/nsis>, <mailto:nsis-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/nsis>
List-Post: <mailto:nsis@ietf.org>
List-Help: <mailto:nsis-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/nsis>, <mailto:nsis-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 03 Feb 2010 15:06:48 -0000

Sorry folks, the -21 version missed two paragraphs.

Please use the -22 version as soon as it pops up in the repository.

  Martin

stiemerling@nw.neclab.eu

NEC Laboratories Europe - Network Research Division
NEC Europe Limited | Registered Office: NEC House, 1 Victoria Road, London W3 6BL | Registered in England 2832014 

> -----Original Message-----
> From: IETF I-D Submission Tool [mailto:idsubmission@ietf.org]
> Sent: Wednesday, February 03, 2010 4:00 PM
> To: Martin Stiemerling
> Cc: Hannes.Tschofenig@nsn.com; cedric@caoun.net; elwynd@dial.pipex.com
> Subject: New Version Notification for draft-ietf-nsis-nslp-natfw-22
> 
> 
> A new version of I-D, draft-ietf-nsis-nslp-natfw-22.txt has been
> successfuly submitted by Martin Stiemerling and posted to the IETF
> repository.
> 
> Filename:	 draft-ietf-nsis-nslp-natfw
> Revision:	 22
> Title:		 NAT/Firewall NSIS Signaling Layer Protocol (NSLP)
> Creation_date:	 2010-02-03
> WG ID:		 nsis
> Number_of_pages: 94
> 
> Abstract:
> This memo defines the NSIS Signaling Layer Protocol (NSLP) for
> Network Address Translators (NATs) and firewalls.  This NSLP allows
> hosts to signal on the data path for NATs and firewalls to be
> configured according to the needs of the application data flows.  For
> instance, it enables hosts behind NATs to obtain a public reachable
> address and hosts behind firewalls to receive data traffic.  The
> overall architecture is given by the framework and requirements
> defined by the Next Steps in Signaling (NSIS) working group.  The
> network scenarios, the protocol itself, and examples for path-coupled
> signaling are given in this memo.
> 
> 
> 
> The IETF Secretariat.
>