Re: [icnrg] RG Last call on the ICN in LTE, 4G document - closes October 6th, 2019

"Milan Stolic (mistolic)" <mistolic@cisco.com> Thu, 19 December 2019 22:11 UTC

Return-Path: <mistolic@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 04474120180 for <icnrg@ietfa.amsl.com>; Thu, 19 Dec 2019 14:11:24 -0800 (PST)
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=Qm6ZmhVX; dkim=pass (1024-bit key) header.d=cisco.onmicrosoft.com header.b=Gay/CgHl
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 D06nGi00impe for <icnrg@ietfa.amsl.com>; Thu, 19 Dec 2019 14:11:22 -0800 (PST)
Received: from alln-iport-4.cisco.com (alln-iport-4.cisco.com [173.37.142.91]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4FD1E120048 for <icnrg@irtf.org>; Thu, 19 Dec 2019 14:11:22 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=5280; q=dns/txt; s=iport; t=1576793482; x=1578003082; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=B4rZQwxm403fA2x+RShmFagvH8LhSl6h5A5P/ilGAsA=; b=Qm6ZmhVX4Eu6GW3ognk+QZXzSU1IwvvLyD3pWunKONe+76MCkaCuyc3E sZNQNN5RpB8EbAZCahzsODc70z4s2kiSpUsuIsZpSJlDzNowTDAGlv6f7 s6PAX0jQ63JUcYOUgw+Sd/1Jc5fdbPYe/0NwsU9vSzIOWnM35OuwtwT4b 8=;
IronPort-PHdr: =?us-ascii?q?9a23=3A1Hl04BSUQ4+q7JhDS8cq0y3drdpsv++ubAcI9p?= =?us-ascii?q?oqja5Pea2//pPkeVbS/uhpkESXBNfA8/wRje3QvuigQmEG7Zub+FE6OJ1XH1?= =?us-ascii?q?5g640NmhA4RsuMCEn1NvnvOik7B9hFUF5u13q6KkNSXs35Yg6arw=3D=3D?=
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0BoAwAZ9ftd/5FdJa1lDg4BAQEBAQc?= =?us-ascii?q?BAREBBAQBAYFrBAEBCwGBTCknBYFEIAQLKgqDfINGA4p0gl+YCIFCgRADVAk?= =?us-ascii?q?BAQEMAQEtAgEBg0CBAAIXggUkNwYOAgMNAQEEAQEBAgEFBG2FNwyFXgEBAQE?= =?us-ascii?q?DEhERDAEBMgUBCwQCAQYCEQQBAQMCJgICAjAVCAgCBAENBQgagjWDEgMuAZE?= =?us-ascii?q?RkGQCgTiIYXWBMoJ+AQEFhRAYggwJgQ4oAYUchnwagUE/gRFHgh4uPoJkBIE?= =?us-ascii?q?uARIBIQUQI4JWMoIKIo1PgmieWAqCNIZMj2eWEYRAhEGKEJpRAgQCBAUCDgE?= =?us-ascii?q?BBYFoI2dxcBWDJ1AYDY0SOIM7ihg7dAEBgSaNOoEiAYEPAQE?=
X-IronPort-AV: E=Sophos;i="5.69,333,1571702400"; d="scan'208";a="386294777"
Received: from rcdn-core-9.cisco.com ([173.37.93.145]) by alln-iport-4.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 19 Dec 2019 22:11:21 +0000
Received: from XCH-ALN-005.cisco.com (xch-aln-005.cisco.com [173.36.7.15]) by rcdn-core-9.cisco.com (8.15.2/8.15.2) with ESMTPS id xBJMBL7R027877 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Thu, 19 Dec 2019 22:11:21 GMT
Received: from xhs-aln-001.cisco.com (173.37.135.118) by XCH-ALN-005.cisco.com (173.36.7.15) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Thu, 19 Dec 2019 16:11:20 -0600
Received: from xhs-aln-003.cisco.com (173.37.135.120) by xhs-aln-001.cisco.com (173.37.135.118) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Thu, 19 Dec 2019 16:11:20 -0600
Received: from NAM10-BN7-obe.outbound.protection.outlook.com (173.37.151.57) by xhs-aln-003.cisco.com (173.37.135.120) with Microsoft SMTP Server (TLS) id 15.0.1473.3 via Frontend Transport; Thu, 19 Dec 2019 16:11:20 -0600
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=Mod3rebj/ykSiLrTGDKlEI22TUjKXk9uY5bldizW/cAao0njIMw0QHDsDol7It25d686J7qOr6Mr8uGc6+tV44KJcF1yw1ExlC94EeQ76i4pz4DY/D2/BVRvoG65A6urp81/DeRE5SGn22D5UNtkDOclpTwnmz3G1a0jgXJ+PquXfYyGeBM/8ibOCR3d6fD0gMFeduLeDEGFPVjpo9vRJ2zpOs8wtkni2mNo4RaHohTBm0yiBaEhdhvZmXX26PsCjvwe2q8Fdo3lf7zU6o1kNJ/Zv75O4sNUJkH+po/E+J+pKrleNs3Z8IPRZogRnhn/xPSaxX+TK4T8KxBBGAJ3qQ==
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=B4rZQwxm403fA2x+RShmFagvH8LhSl6h5A5P/ilGAsA=; b=JCNau/cKg2LoTjOtDl9khxQvIoOkdHaV1C9y8JANixpeaG9CAe4aKyYzrLpIK2eUVPFkxZyPYysQPvV950kKzCSTtaPjTKyxbpItmQaHvGSF27yPcFM+ib9GyPGTKPcl3LPpTiyyljcUdljRExb5yXoOwtnzN5rS48WSpnfHrs0I6idJeiurvCidkM36kffc9KLTl5x6bIuaYwgNBS+adbmbGWRUb2evWRQ7bR9lThog0bOZFUh0TrIrQ8DsHOgrp8H2hGggpWdAlM4HEcLeZGsN21+d0FuAPzyoc8nkHkok4hq/UmlMjZDyKayogr64re57aMQChDeW/lIKvKidHg==
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=B4rZQwxm403fA2x+RShmFagvH8LhSl6h5A5P/ilGAsA=; b=Gay/CgHlE73N6TRovUEmFNhuQ+eXEbsJYjxwEWKpEMJC8E/p20bL7krUgawl2yDIERsWOfgM6HciOQq3BE6zxGwuJKO+aV8jQ3GSaOUl1K9uFgQmxgDnaXVt0iK6cbS8vtyeOvgmrjFzT4OqfEiP3jbtN3v4Z6srZL5BFKdeDNI=
Received: from CH2PR11MB4504.namprd11.prod.outlook.com (10.186.149.218) by CH2PR11MB4392.namprd11.prod.outlook.com (10.141.118.212) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2559.14; Thu, 19 Dec 2019 22:11:19 +0000
Received: from CH2PR11MB4504.namprd11.prod.outlook.com ([fe80::80fb:a86f:124f:6fa0]) by CH2PR11MB4504.namprd11.prod.outlook.com ([fe80::80fb:a86f:124f:6fa0%3]) with mapi id 15.20.2559.012; Thu, 19 Dec 2019 22:11:19 +0000
From: "Milan Stolic (mistolic)" <mistolic@cisco.com>
To: "David R. Oran" <daveoran@orandom.net>, "Anil Jangam (anjangam)" <anjangam@cisco.com>, "Reed, Martin J" <mjreed@essex.ac.uk>
CC: Dirk Kutscher <ietf@dkutscher.net>, "icnrg@irtf.org" <icnrg@irtf.org>, =?utf-8?B?QsO2cmplIE9obG1hbg==?= <borje.ohlman=40ericsson.com@dmarc.ietf.org>, Akbar Rahman <Akbar.Rahman@InterDigital.com>, "Prakash Suthar (psuthar)" <psuthar@cisco.com>
Thread-Topic: [icnrg] RG Last call on the ICN in LTE, 4G document - closes October 6th, 2019
Thread-Index: AQHVb1seypGAc6vs80SArFPbvQy2ZKc7JUfggECCzfCAE2n6QoAAUEWAgACzlICAD5UEAIAi51TQ
Date: Thu, 19 Dec 2019 22:11:19 +0000
Message-ID: <CH2PR11MB4504B814AA34568C657D5510CA520@CH2PR11MB4504.namprd11.prod.outlook.com>
References: <AAF75EAF-C068-4FDB-8A78-B1DF0A6ADA2F@ericsson.com> <DM6PR10MB3418B5C2344B0AB87C29EE3BE7840@DM6PR10MB3418.namprd10.prod.outlook.com> <MWHPR11MB1376CAB77B27B1EBDDC57682CA7F0@MWHPR11MB1376.namprd11.prod.outlook.com> <MWHPR11MB1376A6970F3CEF9A32353E15CA7F0@MWHPR11MB1376.namprd11.prod.outlook.com> <74ADE31D-AB1E-4EC3-AC41-EA05ED0B49E3@dkutscher.net> <627A079D-ABC0-4405-AE38-CF9F211E4ECA@orandom.net> <DDC01383-EE1D-468D-A1EA-E9537F8A83A0@cisco.com> <3EDBA25A-3F90-4BE9-83CE-41001B80FA47@orandom.net>
In-Reply-To: <3EDBA25A-3F90-4BE9-83CE-41001B80FA47@orandom.net>
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=mistolic@cisco.com;
x-originating-ip: [72.163.2.245]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 588fb66d-6687-4bdf-6904-08d784d05ff3
x-ms-traffictypediagnostic: CH2PR11MB4392:
x-ms-exchange-transport-forked: True
x-microsoft-antispam-prvs: <CH2PR11MB4392A07DCC4E9927CBE24602CA520@CH2PR11MB4392.namprd11.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:10000;
x-forefront-prvs: 0256C18696
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(376002)(39860400002)(346002)(136003)(396003)(366004)(199004)(189003)(13464003)(55016002)(107886003)(71200400001)(8676002)(5660300002)(53546011)(6506007)(8936002)(316002)(81166006)(9686003)(54906003)(86362001)(66574012)(81156014)(110136005)(66556008)(66476007)(66446008)(33656002)(64756008)(478600001)(76116006)(4326008)(186003)(7696005)(66946007)(2906002)(52536014)(26005); DIR:OUT; SFP:1101; SCL:1; SRVR:CH2PR11MB4392; H:CH2PR11MB4504.namprd11.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:1; MX:1;
received-spf: None (protection.outlook.com: cisco.com does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: RGGc5Hb9Nc3PXc9NNN7GvTTVNTenS042o1hsXBPVkxXsiBhPmIIAZG4OUHmjM7pJgSso2kHbyU6YM6p5rGRJ5pDiaHM+OIXLGM6QfOML4ZryGy0VCaGR/jbNUFTKfB4ldema36eu+OKoykadbjoD/EH6grZw5O28K/cK4Haq8KgNQ8Big81nsp5WTJfLgpNLf91yCfhhj+k1ZBSOwL+NuFsFECNGoEb3LrIfc61HutArnz6mk/iM1Qkmm9Fw+2rtUr/IrTsGa3ms649RVbrfb54b6f3GBEU4SdvTZ//f+aas/IsQjkSFhKYLBM8HEJz9vLBcAzoGwvAlOtqTXj6UBXZcjIK6MO0cJR/nJGDtMvda10PFxFJXkPnI/RtF9yCuUogv8bRoDPXLUN5re5N0rAgAFN80wXBtDfX2mw/JZona2QKm2xdMDUfIp1hnwcRr65DElpFqoaETMXHxwZaPTvwhWBIASaCTFBwl68NvxCwEgPzeCXQRWK400z8BFEHA
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: 588fb66d-6687-4bdf-6904-08d784d05ff3
X-MS-Exchange-CrossTenant-originalarrivaltime: 19 Dec 2019 22:11:19.3106 (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: 9NY3hSiWm14TIU4peUiXQKoBiMgWlISRjWKgWHHaEe91LvVF2+0l0BkDoSn8IR9UfBwO6oA0Cq/I7dhNADCEAg==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: CH2PR11MB4392
X-OriginatorOrg: cisco.com
X-Outbound-SMTP-Client: 173.36.7.15, xch-aln-005.cisco.com
X-Outbound-Node: rcdn-core-9.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/icnrg/Tq2GCk2jfl-fx3BnWADCN4bYgsI>
Subject: Re: [icnrg] RG Last call on the ICN in LTE, 4G document - closes October 6th, 2019
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: Thu, 19 Dec 2019 22:11:24 -0000

Hello,

First of all: Dave, thank you for your feedback.

I wanted to check with Martin if he feels that his concerns were addressed appropriately, and to see what we can do to move the draft to the next stage.

Thank you,
Prakash, Anil and Milan

-----Original Message-----
From: David R. Oran <daveoran@orandom.net>; 
Sent: Wednesday, November 27, 2019 11:05
To: Anil Jangam (anjangam) <anjangam@cisco.com>;
Cc: Dirk Kutscher <ietf@dkutscher.net>;; icnrg@irtf.org; Milan Stolic (mistolic) <mistolic@cisco.com>;; Börje Ohlman <borje.ohlman=40ericsson.com@dmarc.ietf.org>;; Akbar Rahman <Akbar.Rahman@InterDigital.com>;; Prakash Suthar (psuthar) <psuthar@cisco.com>;
Subject: Re: [icnrg] RG Last call on the ICN in LTE, 4G document - closes October 6th, 2019

I went through the -05 (finally - sorry for the delay), and the writing is substantially improved. There are still a number of grammar glitches an infelicitous wordings, but it probably would not be helpful to request another pass at this point. If this gets positive reception from the IRSG reviewers, the remaining editorial corrections can be made during RFC editor processing.

In terms of the responses to my comments, I’m not 100% happy, but I’d again rather this got IRSG review with a new set of eyes than holding things up. See below for the few places I think my comments might have not been adequately addressed. I snipped out the ones that we are on the same page for.

So, let’s pass this on to the next stage of IRSG review as long as Martin is also happy.
DaveO.

On 17 Nov 2019, at 14:07, Anil Jangam (anjangam) wrote:


> •          On the top of page 10, you say “However, a common 
> limitation of these research efforts is that they focus on faster 
> routing of Interest request towards the content rather than the 
> quality of experience based on actual content delivery. For that to 
> happen, QoS should be implemented and enforced on the Data packet 
> path.” I don’t know what this is doing here. It isn’t terribly helpful 
> to just invoke QoS. It’s also not appropriate to bring QoE into this, 
> as QoE is an application layer concept. Lastly, there is current 
> research on QoS for ICN, so the statement isn’t all that accurate.
>
> [AJ] We reworded it as – “focus of these research efforts is on faster 
> routing of Interest requests towards the content rather than content 
> delivery.”
>
This isn’t an improvement, I don’t think. QoS is about unfair allocation of resources, which applies equally to routing of requests and delivery of content. There is active research spanning the whole range of designs and machinery. I can provide citations if you want.

>
>
> •          On page 14, I’m not sure what you mean by “signed 
> key”? In any event the actual key is not usually in the data packet; 
> only a key-id or key locator.
>
I no longer see the offending text, but since the page numbers have changed I don’t have the context to know whether the underlying comment is still valid and there’s no specific response in the email to this comment.

> •          on page 17, what do you mean by “stored in the ICN 
> node”? Is this producers, repos, caches, or all of the above?
>
> [AJ] To address this, we added this – “stored in the ICN node (such as 
> repos, caches)”
>
Hmmm, there’s more going on here than I noticed the first time around. 
The text still confusing me is the qualifier “in the tunnel path” 
since if you do ICN there is no longer a tunnel path. In any event, now that at my request you mention repositories (and you should probably spell that out rather than using the shorter “repos”) the text is now wrong since repositories don’t have to be on-path to the producer and can be separately expressed in the routing.