Subject: [icnrg] FW: New Version Notification for draft-anilj-icnrg-dnc-qos-icn-01.txt

From: "Anil Jangam (anjangam)" <[email-masked]>
Date: Wed, 11 Sep 2019 18:19:23 +0000

Dear Colleagues, 

We have posted an update to ICN QoS treatment draft incorporating the feedback we gathered based on an offline discussion with Mark Mosko. 
The changes captures the choices we have to encode the QoS marker in the Interest/Content packet. We added a new section (4) and added some additional text in section 5.1 and 6.2. 

We request you all to review and provide your comments/feedback. 

Thank you,
/anil.

    A new version of I-D, draft-anilj-icnrg-dnc-qos-icn-01.txt
    has been successfully submitted by Anil Jangam and posted to the
    IETF repository.
    
    Name:		draft-anilj-icnrg-dnc-qos-icn
    Revision:	01
    Title:		QoS Treatments in ICN using Disaggregated Name Components
    Document date:	2019-09-11
    Group:		Individual Submission
    Pages:		18
    URL:            https://www.ietf.org/internet-drafts/draft-anilj-icnrg-dnc-qos-icn-01.txt
    Status:         https://datatracker.ietf.org/doc/draft-anilj-icnrg-dnc-qos-icn/
    Htmlized:       https://tools.ietf.org/html/draft-anilj-icnrg-dnc-qos-icn-01
    Htmlized:       https://datatracker.ietf.org/doc/html/draft-anilj-icnrg-dnc-qos-icn
    Diff:           https://www.ietf.org/rfcdiff?url2=draft-anilj-icnrg-dnc-qos-icn-01
    
    Abstract:
       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, it's 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.

    
    Please note that it may take a couple of minutes from the time of submission
    until the htmlized version and diff are available at tools.ietf.org.
    
    The IETF Secretariat