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

"David R. Oran" <daveoran@orandom.net> Wed, 27 November 2019 17:05 UTC

Return-Path: <daveoran@orandom.net>
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 8C8B9120967 for <icnrg@ietfa.amsl.com>; Wed, 27 Nov 2019 09:05:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=unavailable autolearn_force=no
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 MoliOQ3ZL-9q for <icnrg@ietfa.amsl.com>; Wed, 27 Nov 2019 09:05:29 -0800 (PST)
Received: from spark.crystalorb.net (spark.crystalorb.net [IPv6:2607:fca8:1530::c]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CA19512004D for <icnrg@irtf.org>; Wed, 27 Nov 2019 09:05:29 -0800 (PST)
Received: from [66.31.202.149] ([IPv6:2601:184:407f:80ce:466:ff54:dfbf:9f19]) (authenticated bits=0) by spark.crystalorb.net (8.14.4/8.14.4/Debian-4+deb7u1) with ESMTP id xARH5BUU009655 (version=TLSv1/SSLv3 cipher=AES256-GCM-SHA384 bits=256 verify=NO); Wed, 27 Nov 2019 09:05:13 -0800
From: "David R. Oran" <daveoran@orandom.net>
To: "Anil Jangam" <anjangam@cisco.com>
Cc: "Dirk Kutscher" <ietf@dkutscher.net>, icnrg@irtf.org, "Milan Stolic" <mistolic@cisco.com>, "=?utf-8?q?B=C3=B6rje?= Ohlman" <borje.ohlman=40ericsson.com@dmarc.ietf.org>, "Akbar Rahman" <Akbar.Rahman@InterDigital.com>, "Prakash Suthar" <psuthar@cisco.com>
Date: Wed, 27 Nov 2019 12:05:06 -0500
X-Mailer: MailMate (1.13r5667)
Message-ID: <3EDBA25A-3F90-4BE9-83CE-41001B80FA47@orandom.net>
In-Reply-To: <DDC01383-EE1D-468D-A1EA-E9537F8A83A0@cisco.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>
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/icnrg/y-2px3ZtrLWNH9PQQit0KbkukHQ>
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: Wed, 27 Nov 2019 17:05:30 -0000

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.