RFC 5973 on NAT/Firewall NSIS Signaling Layer Protocol (NSLP)

rfc-editor@rfc-editor.org Wed, 06 October 2010 19:15 UTC

Return-Path: <wwwrun@rfc-editor.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 282B43A71C4; Wed, 6 Oct 2010 12:15:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.6
X-Spam-Level:
X-Spam-Status: No, score=-102.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001, 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 iqcnHM3eEq+m; Wed, 6 Oct 2010 12:15:21 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1890:1112:1::2f]) by core3.amsl.com (Postfix) with ESMTP id 92A813A71C9; Wed, 6 Oct 2010 12:15:03 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 87EFEE06FC; Wed, 6 Oct 2010 12:16:04 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 5973 on NAT/Firewall NSIS Signaling Layer Protocol (NSLP)
From: rfc-editor@rfc-editor.org
Message-Id: <20101006191604.87EFEE06FC@rfc-editor.org>
Date: Wed, 06 Oct 2010 12:16:04 -0700
Cc: nsis@ietf.org, rfc-editor@rfc-editor.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
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: Wed, 06 Oct 2010 19:15:23 -0000

A new Request for Comments is now available in online RFC libraries.

        
        RFC 5973

        Title:      NAT/Firewall NSIS Signaling Layer Protocol 
                    (NSLP) 
        Author:     M. Stiemerling, H. Tschofenig,
                    C. Aoun, E. Davies
        Status:     Experimental
        Stream:     IETF
        Date:       October 2010
        Mailbox:    Martin.Stiemerling@neclab.eu, 
                    Hannes.Tschofenig@nsn.com, 
                    cedaoun@yahoo.fr,  elwynd@dial.pipex.com
        Pages:      90
        Characters: 219962
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-nsis-nslp-natfw-25.txt

        URL:        http://www.rfc-editor.org/rfc/rfc5973.txt

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 publicly 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.  This document defines an Experimental 
Protocol for the Internet community.

This document is a product of the Next Steps in Signaling Working Group of the IETF.


EXPERIMENTAL: This memo defines an Experimental Protocol for the
Internet community.  It does not specify an Internet standard of any
kind. Discussion and suggestions for improvement are requested.
Distribution of this memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  http://www.ietf.org/mailman/listinfo/ietf-announce
  http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html.
For downloading RFCs, see http://www.rfc-editor.org/rfc.html.

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
Association Management Solutions, LLC