RMD-QOSM: The NSIS Quality-of-Service Model for Resource Management in Diffserv (RFC5977)
Original Publication Date: 2010-Oct-01
Included in the Prior Art Database: 2010-Oct-07
Internet Society Requests For Comment (RFCs)
A. Bader: AUTHOR [+5]
This document describes a Next Steps in Signaling (NSIS) QoS Model for networks that use the Resource Management in Diffserv (RMD) framework ([RMD1], [RMD2], [RMD3], and [RMD4]). RMD adds admission control to Diffserv networks and allows nodes external to the networks to dynamically reserve resources within the Diffserv domains.
Internet Engineering Task Force (IETF) A. Bader Request for Comments: 5977 L. Westberg Category: Experimental Ericsson ISSN: 2070-1721 G. Karagiannis University of Twente C. Kappler ck technology concepts T. Phelan Sonus October 2010
RMD-QOSM: The NSIS Quality-of-Service Model for Resource Management in Diffserv
This document describes a Next Steps in Signaling (NSIS) Quality-of- Service (QoS) Model for networks that use the Resource Management in Diffserv (RMD) concept. RMD is a technique for adding admission control and preemption function to Differentiated Services (Diffserv) networks. The RMD QoS Model allows devices external to the RMD network to signal reservation requests to Edge nodes in the RMD network. The RMD Ingress Edge nodes classify the incoming flows into traffic classes and signals resource requests for the corresponding traffic class along the data path to the Egress Edge nodes for each flow. Egress nodes reconstitute the original requests and continue forwarding them along the data path towards the final destination. In addition, RMD defines notification functions to indicate overload situations within the domain to the Edge nodes.
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.