RFC 5979: NSIS Operation over IP Tunnels
In plain English — editorial summary, not part of the RFC
NSIS Quality of Service (QoS) signaling enables applications to perform QoS reservation along a data flow path. When the data flow path contains IP tunnel segments, NSIS QoS signaling has no effect within those tunnel segments. Therefore, the resulting tunnel segments could become the weakest QoS link and invalidate the QoS efforts in the rest of the end-to-end path. The problem with NSIS signaling within the tunnel is caused by the tunnel encapsulation that masks packets' original IP header fields. Those original IP header fields are needed to intercept NSIS signaling messages and classify QoS data packets. This document defines a solution to this problem by mapping end-to-end QoS session requests to corresponding QoS sessions in the tunnel, thus extending the end-to-end QoS signaling into the IP tunnel segments. This document defines an Experimental Protocol for the Internet community.
Document record
- Document ID
- RFC5979
- Published
- March 2011
- Authors
- C. Shen; H. Schulzrinne; S. Lee; J. Bang
- Status
- EXPERIMENTAL
- Stream
- IETF
- Area
- tsv
- Pages
- 27
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 5977RMD-QOSM: The NSIS Quality-of-Service Model for Resource Management in DiffservCurrent
October 2010
- RFC 5981Authorization for NSIS Signaling Layer ProtocolsCurrent
February 2011
- RFC 5973NAT/Firewall NSIS Signaling Layer Protocol (NSLP)Current
October 2010
- RFC 5971GIST: General Internet Signalling TransportCurrent
October 2010
- RFC 5980NSIS Protocol Operation in Mobile EnvironmentsCurrent
March 2011
- RFC 5978Using and Extending the NSIS Protocol FamilyCurrent
October 2010
- RFC 5976Y.1541-QOSM: Model for Networks Using Y.1541 Quality-of-Service ClassesCurrent
October 2010
- RFC 5975QSPEC Template for the Quality-of-Service NSIS Signaling Layer Protocol (NSLP)Current
October 2010
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?