QoS Treatments in ICN using Disaggregated Name Components

Document Type Expired Internet-Draft (individual)
Authors Anil Jangam  , Prakash Suthar  , Milan Stolic 
Last updated 2020-09-10 (latest revision 2020-03-09)
Stream (None)
Intended RFC status (None)
Expired & archived
pdf htmlized bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Expired
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at


Mechanisms for specifying and implementing end-to-end Quality of service (QoS) treatments in Information-Centric Networks (ICN) has not been explored so far. There has been some work towards implementing QoS in ICN; however, the discussions are mainly centered around strategies used in efficient forwarding of Interest packets. Moreover, as ICN has been tested mainly as an IP overlay, its QoS is still governed by the IP QoS framework and there is a need for implementing QoS in ICN natively. This document describes mechanisms to classify and provide associated "name-based" extensions to identify QoS within the framework of ICN's core design principles. The name-based design provides a mechanism to carry QoS information and implement the treatments as ICN packets travel across different routers in the ICN network. Detailed discussion is provided for QoS specific procedures in each of the ICN network elements i.e. consumer, producer, and forwarder.


Anil Jangam (anjangam@cisco.com)
Prakash Suthar (psuthar@cisco.com)
Milan Stolic (mistolic@cisco.com)

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)