QSPEC Template for the Quality-of-Service NSIS Signaling Layer Protocol (NSLP)
RFC 5975
Document | Type |
RFC - Experimental
(October 2010; No errata)
Was draft-ietf-nsis-qspec (nsis WG)
|
|
---|---|---|---|
Authors | Gerald Ash , Cornelia Kappler , David Oran , Attila Bader | ||
Last updated | 2015-10-14 | ||
Stream | IETF | ||
Formats | plain text html pdf htmlized bibtex | ||
Stream | WG state | (None) | |
Document shepherd | No shepherd assigned | ||
IESG | IESG state | RFC 5975 (Experimental) | |
Consensus Boilerplate | Unknown | ||
Telechat date | |||
Responsible AD | Magnus Westerlund | ||
Send notices to | (None) |
Internet Engineering Task Force (IETF) G. Ash, Ed. Request for Comments: 5975 AT&T Category: Experimental A. Bader, Ed. ISSN: 2070-1721 Ericsson C. Kappler, Ed. ck technology concepts D. Oran, Ed. Cisco Systems, Inc. October 2010 QSPEC Template for the Quality-of-Service NSIS Signaling Layer Protocol (NSLP) Abstract 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. Status of This Memo This document is not an Internet Standards Track specification; it is published for examination, experimental implementation, and evaluation. This document defines an Experimental Protocol for the Internet community. This document is a product of the Internet Engineering Task Force (IETF). It represents the consensus of the IETF community. It has received public review and has been approved for publication by the Internet Engineering Steering Group (IESG). Not all documents approved by the IESG are a candidate for any level of Internet Standard; see Section 2 of RFC 5741. Ash, et al. Experimental [Page 1] RFC 5975 QoS NSLP QSPEC Template October 2010 Information about the current status of this document, any errata, and how to provide feedback on it may be obtained at http://www.rfc-editor.org/info/rfc5975. Copyright Notice Copyright (c) 2010 IETF Trust and the persons identified as the document authors. All rights reserved. This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License. Ash, et al. Experimental [Page 2] RFC 5975 QoS NSLP QSPEC Template October 2010 Table of Contents 1. Introduction ....................................................4 1.1. Conventions Used in This Document ..........................6 2. Terminology .....................................................6 3. QSPEC Framework .................................................7 3.1. QoS Models .................................................7 3.2. QSPEC Objects ..............................................9 3.3. QSPEC Parameters ..........................................11 3.3.1. Traffic Model Parameter ............................12 3.3.2. Constraints Parameters .............................14 3.3.3. Traffic-Handling Directives ........................16 3.3.4. Traffic Classifiers ................................17 3.4. Example of QSPEC Processing ...............................17 4. QSPEC Processing and Procedures ................................20 4.1. Local QSPEC Definition and Processing .....................20 4.2. Reservation Success/Failure, QSPEC Error Codes, and INFO-SPEC Notification ................................23 4.2.1. Reservation Failure and Error E Flag ...............24 4.2.2. QSPEC Parameter Not Supported N Flag ...............25 4.2.3. INFO-SPEC Coding of Reservation Outcome ............25 4.2.4. QNE Generation of a RESPONSE Message ...............26Show full document text