[rfc-dist] RFC 5979 on NSIS Operation over IP Tunnels

rfc-editor at rfc-editor.org rfc-editor at rfc-editor.org
Tue Mar 15 16:50:29 PDT 2011

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

        RFC 5979

        Title:      NSIS Operation over IP Tunnels 
        Author:     C. Shen, H. Schulzrinne,
                    S. Lee, J. Bang
        Status:     Experimental
        Stream:     IETF
        Date:       March 2011
        Mailbox:    charles at cs.columbia.edu, 
                    hgs at cs.columbia.edu, 
                    sung1.lee at samsung.com,  
                    jh0278.bang at samsung.com
        Pages:      27
        Characters: 69850
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-nsis-tunnel-13.txt

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

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.

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

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 at 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

More information about the rfc-dist mailing list