Re: [icnrg] Review of ICN Terminology document (draft-wissingh-icnrg-terminology-01)

David Oran <daveoran@orandom.net> Wed, 24 May 2017 21:56 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 37D74129BF7 for <icnrg@ietfa.amsl.com>; Wed, 24 May 2017 14:56:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MIME_QP_LONG_LINE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham 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 4dyO_aHeuKU7 for <icnrg@ietfa.amsl.com>; Wed, 24 May 2017 14:56:23 -0700 (PDT)
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 94278129C07 for <icnrg@irtf.org>; Wed, 24 May 2017 14:56:23 -0700 (PDT)
Received: from [192.168.15.109] (c-73-149-20-147.hsd1.ma.comcast.net [73.149.20.147]) (authenticated bits=0) by spark.crystalorb.net (8.14.4/8.14.4/Debian-4+deb7u1) with ESMTP id v4OLuHL3014377 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Wed, 24 May 2017 14:56:19 -0700
Content-Type: multipart/signed; boundary="Apple-Mail-BD9A7A61-BAEA-4AE1-A2FE-E1B4B0DD0EC2"; protocol="application/pkcs7-signature"; micalg="sha1"
Mime-Version: 1.0 (1.0)
From: David Oran <daveoran@orandom.net>
X-Mailer: iPad Mail (14F89)
In-Reply-To: <D96E28F4A22C864DBC6C871B5B1C4CC3229A9EC0@SJCEML702-CHM.china.huawei.com>
Date: Wed, 24 May 2017 17:56:16 -0400
Cc: "Wissingh, B.F." <bastiaan.wissingh@tno.nl>, "icnrg@irtf.org" <icnrg@irtf.org>
Content-Transfer-Encoding: 7bit
Message-Id: <1A54B04A-F59B-4983-87B7-0F8F3D80DCCE@orandom.net>
References: <860B46EC-D3DD-4F60-A4FE-9EA65BEBDBAD@orandom.net> <D96E28F4A22C864DBC6C871B5B1C4CC3229A9EC0@SJCEML702-CHM.china.huawei.com>
To: Ravi Ravindran <ravi.ravindran@huawei.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/icnrg/SRrwqBB6RovtpwYYgMBRFeV_fps>
Subject: Re: [icnrg] Review of ICN Terminology document (draft-wissingh-icnrg-terminology-01)
X-BeenThere: icnrg@irtf.org
X-Mailman-Version: 2.1.22
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, 24 May 2017 21:56:31 -0000

Read carefully - I said "location" not "locator". Things may or may not have locations independent of whether you decide to assign architectural or protocol constructs like a "locator" to them.

___________________________
iDevice - please excuse typos.

> On May 24, 2017, at 5:52 PM, Ravi Ravindran <ravi.ravindran@huawei.com> wrote:
> 
> When we proposed forwarding labels for Interest packets, there was a push back on using the terms ID/Locator, hence we submitted this draft where we use the terms "Application Identifier and "Network Identifier", so another term if we don’t want to use the locator terminology, the draft itself focusses on the motivation on the need for network identifiers.
> 
> https://tools.ietf.org/html/draft-azgin-icnrg-ni-00
> 
> Towards the terminology draft, I had suggested to include this (NI or Locators) term during the offline group meeting at the last IETF meeting, but there were no supporters for this.
> 
> Regards,
> Ravi
> 
> -----Original Message-----
> From: icnrg [mailto:icnrg-bounces@irtf.org] On Behalf Of David Oran
> Sent: Wednesday, May 24, 2017 10:09 AM
> To: Wissingh, B.F. <bastiaan.wissingh@tno.nl>
> Cc: icnrg@irtf.org
> Subject: Re: [icnrg] Review of ICN Terminology document (draft-wissingh-icnrg-terminology-01)
> 
> I was starting to review a couple of ICNRG current drafts, and saw that the term “location” is used a lot, partly to distinguish ICN from host-centric designs that name things based on their “location”.
> 
> I then peeked into the terminology draft and didn’t find a definition of “location”. While adding this might re-open some tricky conversations about topologically-sensitive names, name resolution between “location independent” and “location dependent” names etc. I think we are on balance better off by having an agreed definition of “location” in the context of ICN than waffling and not defining it.
> 
> What do folks think?
> 
> DaveO