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

"Anil Jangam (anjangam)" <anjangam@cisco.com> Wed, 11 September 2019 18:19 UTC

Return-Path: <anjangam@cisco.com>
X-Original-To: icnrg@ietfa.amsl.com
Delivered-To: icnrg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 47CB5120BBF for <icnrg@ietfa.amsl.com>; Wed, 11 Sep 2019 11:19:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.5
X-Spam-Level:
X-Spam-Status: No, score=-14.5 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com header.b=Af8bJmkb; dkim=pass (1024-bit key) header.d=cisco.onmicrosoft.com header.b=RrDSKTZJ
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kPiEDewQy-BW for <icnrg@ietfa.amsl.com>; Wed, 11 Sep 2019 11:19:27 -0700 (PDT)
Received: from alln-iport-1.cisco.com (alln-iport-1.cisco.com [173.37.142.88]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0E4CE12024E for <icnrg@irtf.org>; Wed, 11 Sep 2019 11:19:27 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=3662; q=dns/txt; s=iport; t=1568225967; x=1569435567; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=DMSJ48+9frNE1CFouDjI3FX31279dQPVD0PJG/0j04c=; b=Af8bJmkbZUGnyCIistb5mgA5U0QBkQn4go8ZEmqMtrZLZLGsGobp4Vyw wDmnG4c2Ydue5XicL6of4bTKhGgKMYgEJRMa2rifNX5F60Y5Hbn6infIm 4yAhm9PSEU3BbiYOmvAPLHsw5gj4iC9M/iQag+pXMEsIbGjX9Xb0rS869 Q=;
IronPort-PHdr: =?us-ascii?q?9a23=3AhtCLNhF9BvRo2uxqytzHrJ1GYnJ96bzpIg4Y7I?= =?us-ascii?q?YmgLtSc6Oluo7vJ1Hb+e4z1Q3SRYuO7fVChqKWqK3mVWEaqbe5+HEZON0pNV?= =?us-ascii?q?cejNkO2QkpAcqLE0r+effsbSU8E81HfFRk5Hq8d0NSHZW2ag=3D=3D?=
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0AJAACIOXld/4oNJK1bChoBAQEBAQI?= =?us-ascii?q?BAQEBBwIBAQEBgVMFAQEBAQsBgURQA21WIAQLKgqEF4NHA4RShhWaTIEuFIE?= =?us-ascii?q?QA1QJAQEBDAEBJQgCAQGEPwIXgj4jNAkOAgMJAQEEAQEBAgEGBG2FLgELhUs?= =?us-ascii?q?CAQMSEREMAQE1AgEPAgEIGgImAgICMBUGAQYDAgQOJ4MAAYFqAx0BAgyfZQK?= =?us-ascii?q?BOIhhc4Eygn0BAQWBNgIOQUCCQhiCFgmBDCgBi3cYgUA/gTgfgkw+gmEBAQI?= =?us-ascii?q?BARaBDw2DNjKCJo9AhUWXRgqCIYcBjXYbgjRwhlCPFo1/gTiGTJBqAgQCBAU?= =?us-ascii?q?CDgEBBYFSOIFYcBUaSwGCQQmCOYNyhRSFP3MBgSiNXAGBIgEB?=
X-IronPort-AV: E=Sophos;i="5.64,494,1559520000"; d="scan'208";a="324352092"
Received: from alln-core-5.cisco.com ([173.36.13.138]) by alln-iport-1.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 11 Sep 2019 18:19:26 +0000
Received: from XCH-RCD-014.cisco.com (xch-rcd-014.cisco.com [173.37.102.24]) by alln-core-5.cisco.com (8.15.2/8.15.2) with ESMTPS id x8BIJQl0027701 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL) for <icnrg@irtf.org>; Wed, 11 Sep 2019 18:19:26 GMT
Received: from xhs-rtp-001.cisco.com (64.101.210.228) by XCH-RCD-014.cisco.com (173.37.102.24) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Wed, 11 Sep 2019 13:19:25 -0500
Received: from xhs-aln-002.cisco.com (173.37.135.119) by xhs-rtp-001.cisco.com (64.101.210.228) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Wed, 11 Sep 2019 14:19:24 -0400
Received: from NAM04-CO1-obe.outbound.protection.outlook.com (173.37.151.57) by xhs-aln-002.cisco.com (173.37.135.119) with Microsoft SMTP Server (TLS) id 15.0.1473.3 via Frontend Transport; Wed, 11 Sep 2019 13:19:24 -0500
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=lUVNsiGFUwWWYrRk6YQLukSiFVY/ZJCE9A3sGtKaCHrv9/JxP+CqZ4jcNasQ0UpU19Fdj+QkTSdSkV4Hr9n3bPeENfj+vk9J6PyjEWHd/sB5XuFZNyHxFr6bUD8hT7OhtqNle0bTQTlVLsCzxF0hbwuq1MgmeLpVxNb3qghNs+TwLl0at/auUPqQXloTNi1wpY9EvXKpuqTM1GXfvPa2JTDCPBytFSzJjasXO17lFgYbBTXGQrNzry7DMSDk2h3wlXtbNiy4uvXs/Q4pNhGZnAxZW/snRJwkA0MWvPBIb201rF6pu7hK0JpDf/Bk1XxTnmzHeKib4SfvyGVehFItYA==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=DMSJ48+9frNE1CFouDjI3FX31279dQPVD0PJG/0j04c=; b=i8bQQqruGk6nJTxfh90N+oxUIk4DRkHX6LcM4XTelOWPBnpft/V/OnKPuMlQmSS5GcCG9VzQoU0QXnLb4g/FACniVnpBuVwwKm9ikQ0mrIUA2Dyu78luH/KjK+xM45CBiHWdtvepgXiy06Iqt77TL9UnVXse3Bv/+K25ExxKTk3Q3bLt1ItbWvnJZfLIfUa6gplW8FkeiqTmIKfYot83c1zpvkcI5W1RwAGZuLV9WxHE5RIVG3MSRTV/xlEtpsrpjzFH2lxr15MxYpzq4zvuryFIUpVmMzu1wKY64iayuEymXyxp/C0xeC1GIRWGxZU9bYLgl9Y8mAaELZ1sXZFQCg==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=cisco.com; dmarc=pass action=none header.from=cisco.com; dkim=pass header.d=cisco.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cisco.onmicrosoft.com; s=selector2-cisco-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=DMSJ48+9frNE1CFouDjI3FX31279dQPVD0PJG/0j04c=; b=RrDSKTZJwIqBJ+WoW0yaeFspbaQM9kza4PzpAJhOQ1YUQPea2U4pEOEzMmVPUlnFX1qaI1fo2+MpvfBX7EWJFGGDPmI7VxcauknV5K40GTLmRfNZJInnp5CMnTwK6CQctkMFPsm1s68h8mYDuC89Bmzhs5x47sM0WRukG/30rsw=
Received: from BYAPR11MB3687.namprd11.prod.outlook.com (20.178.237.160) by BYAPR11MB3783.namprd11.prod.outlook.com (20.178.238.225) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2241.13; Wed, 11 Sep 2019 18:19:23 +0000
Received: from BYAPR11MB3687.namprd11.prod.outlook.com ([fe80::e973:d3ae:2f2d:cbe2]) by BYAPR11MB3687.namprd11.prod.outlook.com ([fe80::e973:d3ae:2f2d:cbe2%6]) with mapi id 15.20.2241.018; Wed, 11 Sep 2019 18:19:23 +0000
From: "Anil Jangam (anjangam)" <anjangam@cisco.com>
To: "icnrg@irtf.org" <icnrg@irtf.org>
CC: "Prakash Suthar (psuthar)" <psuthar@cisco.com>, "Milan Stolic (mistolic)" <mistolic@cisco.com>
Thread-Topic: New Version Notification for draft-anilj-icnrg-dnc-qos-icn-01.txt
Thread-Index: AQHVaIeYbmGH5RdYrUSNiGeW8Zc2VqcmVHeA
Date: Wed, 11 Sep 2019 18:19:23 +0000
Message-ID: <B7D30CBD-14F5-474D-B699-A1BD150A91A3@cisco.com>
References: <156819595706.18506.4968922997891651176.idtracker@ietfa.amsl.com>
In-Reply-To: <156819595706.18506.4968922997891651176.idtracker@ietfa.amsl.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: spf=none (sender IP is ) smtp.mailfrom=anjangam@cisco.com;
x-originating-ip: [128.107.241.167]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 9859734a-d985-4756-b9c2-08d736e4927f
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(5600166)(711020)(4605104)(1401327)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(2017052603328)(7193020); SRVR:BYAPR11MB3783;
x-ms-traffictypediagnostic: BYAPR11MB3783:
x-ms-exchange-purlcount: 5
x-ms-exchange-transport-forked: True
x-microsoft-antispam-prvs: <BYAPR11MB3783E17993C1E53235797703C1B10@BYAPR11MB3783.namprd11.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:9508;
x-forefront-prvs: 0157DEB61B
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(4636009)(376002)(366004)(39860400002)(136003)(396003)(346002)(189003)(199004)(256004)(26005)(66574012)(7736002)(54906003)(2906002)(486006)(316002)(305945005)(99286004)(476003)(11346002)(2616005)(14454004)(2501003)(14444005)(446003)(33656002)(478600001)(966005)(71200400001)(102836004)(6506007)(6486002)(413944005)(3846002)(6116002)(71190400001)(76176011)(66476007)(36756003)(66946007)(4326008)(66446008)(64756008)(25786009)(81156014)(15650500001)(1730700003)(186003)(66556008)(8936002)(6916009)(8676002)(76116006)(2351001)(5640700003)(5660300002)(6306002)(2473003)(6512007)(86362001)(66066001)(107886003)(6436002)(81166006)(229853002)(53936002); DIR:OUT; SFP:1101; SCL:1; SRVR:BYAPR11MB3783; H:BYAPR11MB3687.namprd11.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:1;
received-spf: None (protection.outlook.com: cisco.com does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam-message-info: ZFlZ2XSIJBNKspJfQPvr4HJ77yjnFFRsLeh0oPNS5WkWRo3I8AjBTLF58DulnIQQwwMm8KxjStWcLgocZFsk4pSBf7+4HolNmvUy7ZkqP9wMy6koOY2+v3o0fs26+k3taIU6dx6TDNVF80zwYscfpb4+otuNcv0gKra/q/vqnN1G9J24CcL4RAynaH0UMF232Ga41qCeU6SpLepOZJFUGmfNy3LU9XA+m8Ugn8oQsSTtD45UPkQko83jcOuEpguvxHMqCaEk4R7BRACiUK5TTGDzxYixbZr7TkadjWg1/XWMxa0chRKhrhqKTV5EtQ3tP0jvb0p7pLjvgl6EFWdJVE8RDS1v4CXfhDbTAqzLmxyomPuFItoVX4HAFfXSzqgGmWKwc3dmLurEypxbf89cW80qc46WviEd0TKnZA7KaRA=
Content-Type: text/plain; charset="utf-8"
Content-ID: <376F5E69B91C74419E34650A0098534C@namprd11.prod.outlook.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: 9859734a-d985-4756-b9c2-08d736e4927f
X-MS-Exchange-CrossTenant-originalarrivaltime: 11 Sep 2019 18:19:23.3362 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 5ae1af62-9505-4097-a69a-c1553ef7840e
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: DMkVxrAA+BHCuuRXU86JKRZ/xwEGpFG+q+5rwB5105vYkGC0p7ATf+/taVjo2mcClHK1rAm9SZvynJD+vfU+qQ==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BYAPR11MB3783
X-OriginatorOrg: cisco.com
X-Outbound-SMTP-Client: 173.37.102.24, xch-rcd-014.cisco.com
X-Outbound-Node: alln-core-5.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/icnrg/nDN4ETQqJemOnVd69DG8cV--bOw>
Subject: [icnrg] FW: New Version Notification for draft-anilj-icnrg-dnc-qos-icn-01.txt
X-BeenThere: icnrg@irtf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Information-Centric Networking research group discussion list <icnrg.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/options/icnrg>, <mailto:icnrg-request@irtf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/icnrg/>
List-Post: <mailto:icnrg@irtf.org>
List-Help: <mailto:icnrg-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/icnrg>, <mailto:icnrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Wed, 11 Sep 2019 18:19:29 -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