RFC 5973: NAT/Firewall NSIS Signaling Layer Protocol (NSLP)
In plain English — editorial summary, not part of the RFC
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.
Document record
- Document ID
- RFC5973
- Published
- October 2010
- Authors
- M. Stiemerling; H. Tschofenig; C. Aoun; E. Davies
- Status
- EXPERIMENTAL
- Stream
- IETF
- Area
- tsv
- Pages
- 90
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 5971GIST: General Internet Signalling TransportCurrent
October 2010
- RFC 5977RMD-QOSM: The NSIS Quality-of-Service Model for Resource Management in DiffservCurrent
October 2010
- RFC 5979NSIS Operation over IP TunnelsCurrent
March 2011
- RFC 5981Authorization for NSIS Signaling Layer ProtocolsCurrent
February 2011
- RFC 4094Analysis of Existing Quality-of-Service Signaling ProtocolsCurrent
May 2005
- RFC 8041Use Cases and Operational Experience with Multipath TCPCurrent
January 2017
- RFC 3726Requirements for Signaling ProtocolsCurrent
April 2004
- RFC 6714Connection Establishment for Media Anchoring (CEMA) for the Message Session Relay Protocol (MSRP)Current
August 2012
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?