RFC 5975 on QSPEC Template for the Quality-of-Service NSIS Signaling Layer Protocol (NSLP)

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

        RFC 5975

        Title:      QSPEC Template for the Quality-of-Service 
                    NSIS Signaling Layer Protocol (NSLP) 
        Author:     G. Ash, Ed.,
                    A. Bader, Ed.,
                    C. Kappler, Ed.,
                    D. Oran, Ed.
        Status:     Experimental
        Stream:     IETF
        Date:       October 2010
        Mailbox:    gash5107@yahoo.com, 
                    Attila.Bader@ericsson.com, 
                    cornelia.kappler@cktecc.de,  oran@cisco.com
        Pages:      64
        Characters: 153418
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-nsis-qspec-24.txt

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

The Quality-of-Service (QoS) NSIS signaling layer protocol (NSLP) is used 
to signal QoS reservations and is independent of a specific QoS model 
(QOSM) such as IntServ or Diffserv.  Rather, all information specific to a 
QOSM is encapsulated in a separate object, the QSPEC.  This document 
defines a template for the QSPEC including a number of QSPEC parameters.  
The QSPEC parameters provide a common language to be reused in several 
QOSMs and thereby aim to ensure the extensibility and interoperability of
QoS NSLP.  While the base protocol is QOSM-agnostic, the parameters
that can be carried in the QSPEC object are possibly closely coupled
to specific models.  The node initiating the NSIS signaling adds an
Initiator QSPEC, which indicates the QSPEC parameters that must be
interpreted by the downstream nodes less the reservation fails,
thereby ensuring the intention of the NSIS initiator is preserved
along the signaling path.  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