[icnrg] Some comments on NRS presentation

<Marc.Mosko@parc.com> Thu, 07 April 2016 13:15 UTC

Return-Path: <Marc.Mosko@parc.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 1801612D7EF for <icnrg@ietfa.amsl.com>; Thu, 7 Apr 2016 06:15:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.9
X-Spam-Level:
X-Spam-Status: No, score=-6.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-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 EUuIdftY-EtP for <icnrg@ietfa.amsl.com>; Thu, 7 Apr 2016 06:15:27 -0700 (PDT)
Received: from smtp.parc.xerox.com (alpha.Xerox.COM [13.1.64.93]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0156912D91C for <icnrg@irtf.org>; Thu, 7 Apr 2016 06:15:18 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by smtp.parc.xerox.com (Postfix) with ESMTP id 1ABCC6C0098 for <icnrg@irtf.org>; Thu, 7 Apr 2016 06:15:18 -0700 (PDT)
X-Virus-Scanned: Debian amavisd-new at newalpha.parc.com
Received: from smtp.parc.xerox.com ([127.0.0.1]) by localhost (smtp.parc.xerox.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EiMm4BkpcW4k for <icnrg@irtf.org>; Thu, 7 Apr 2016 06:15:17 -0700 (PDT)
Received: from exchangehub.parc.xerox.com (vertigo.parc.xerox.com [13.2.13.102]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by smtp.parc.xerox.com (Postfix) with ESMTPS id DF4116C0095 for <icnrg@irtf.org>; Thu, 7 Apr 2016 06:15:17 -0700 (PDT)
Received: from E2010DAG5.corp.ad.parc.com ([fe80::3d0b:7158:aec4:e05e]) by vertigo.corp.ad.parc.com ([fe80::606e:47ce:f5e2:fe3a%14]) with mapi id 14.03.0266.001; Thu, 7 Apr 2016 06:15:17 -0700
From: Marc.Mosko@parc.com
To: icnrg@irtf.org
Thread-Topic: Some comments on NRS presentation
Thread-Index: AQHRkM+HpBbssRnoGkmpLMPIxjnq0A==
Date: Thu, 07 Apr 2016 13:15:16 +0000
Message-ID: <8CC55AED-EC6F-4450-91E5-C3130425CF34@parc.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [31.133.179.24]
Content-Type: multipart/alternative; boundary="_000_8CC55AEDEC6F445091E5C3130425CF34parccom_"
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/icnrg/LHo1EQxtKs1LDTpRna3dPLjiITI>
Subject: [icnrg] Some comments on NRS presentation
X-BeenThere: icnrg@irtf.org
X-Mailman-Version: 2.1.17
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, 07 Apr 2016 13:15:33 -0000

Jungha,

Here are some suggestions on the NRS motivation slide use cases.

Also, you might look at Trammell’s draft https://tools.ietf.org/html/draft-trammell-inip-pins-01

Use case 1: One to many resolution
- An NRS should be able to return multiple locators
- Don’t get in to how  an NRS chooses to register multiple records
- Similar to returning multiple RRs

Use case 2: Aliases
- An NRS should be able to go from one name to another name
- Could it also provide the “A” records  too?
- Similar to a CNAME
- Are there security issues around this, delegation?
- Also, in ICN, aren’t we always talking about going from one name to another name?  Is this use case supposed to be something different than the normal use of NRS in ICN?

Use case 3: Name to IP address
- The ability to return a network endpoint based on a name.  I’d generalize it from IP address.
- (PARC did work on this in “custodian routing” https://www.parc.com/content/attachments/custodian-based-information.pdf, which was a bit more like a SIP system)
- This might also be generalized to returning different query types as part of the name resolution (e.g. A, TXT, keys, etc).

As someone noted in the meeting, there is a lot of similarity in the use cases to DNS.  It might be good to look at what extensions/modifications to DNS would be required to meet the needs of ICN NRS.

Marc