Re: [icnrg] CCNx drafts

Ravi Ravindran <ravi.ravindran@huawei.com> Wed, 06 April 2016 20:05 UTC

Return-Path: <ravi.ravindran@huawei.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 2A2ED12D608 for <icnrg@ietfa.amsl.com>; Wed, 6 Apr 2016 13:05:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.23
X-Spam-Level:
X-Spam-Status: No, score=-4.23 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 Cn_q_83hfNsf for <icnrg@ietfa.amsl.com>; Wed, 6 Apr 2016 13:05:06 -0700 (PDT)
Received: from dfwrgout.huawei.com (dfwrgout.huawei.com [206.16.17.72]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EF4CB12D50C for <icnrg@irtf.org>; Wed, 6 Apr 2016 13:05:05 -0700 (PDT)
Received: from 172.18.9.243 (EHLO dfweml705-chm.china.huawei.com) ([172.18.9.243]) by dfwrg02-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id BOT78344; Wed, 06 Apr 2016 15:05:04 -0500 (CDT)
Received: from SJCEML703-CHM.china.huawei.com (10.218.25.36) by dfweml705-chm.china.huawei.com (10.193.5.142) with Microsoft SMTP Server (TLS) id 14.3.235.1; Wed, 6 Apr 2016 13:05:03 -0700
Received: from SJCEML701-CHM.china.huawei.com ([169.254.3.126]) by SJCEML703-CHM.china.huawei.com ([169.254.5.228]) with mapi id 14.03.0235.001; Wed, 6 Apr 2016 13:05:01 -0700
From: Ravi Ravindran <ravi.ravindran@huawei.com>
To: "Ignacio.Solis@parc.com" <Ignacio.Solis@parc.com>, "icnrg@irtf.org" <icnrg@irtf.org>
Thread-Topic: CCNx drafts
Thread-Index: AQHRkCWyVYU4InXekkyoB5pEuUmVU599UfXA
Date: Wed, 06 Apr 2016 20:04:58 +0000
Message-ID: <D96E28F4A22C864DBC6C871B5B1C4CC320BEA54C@SJCEML701-CHM.china.huawei.com>
References: <93B70326-6A66-4E39-9E07-5CFADCCBE7D3@parc.com>
In-Reply-To: <93B70326-6A66-4E39-9E07-5CFADCCBE7D3@parc.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.212.246.90]
Content-Type: multipart/alternative; boundary="_000_D96E28F4A22C864DBC6C871B5B1C4CC320BEA54CSJCEML701CHMchi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
X-Mirapoint-Virus-RAPID-Raw: score=unknown(0), refid=str=0001.0A0B0203.57056BF1.002A, ss=1, re=0.000, recu=0.000, reip=0.000, cl=1, cld=1, fgs=0, ip=169.254.3.126, so=2013-06-18 04:22:30, dmn=2013-03-21 17:37:32
X-Mirapoint-Loop-Id: 991b6f2e8bd2dd36d2950e68c344d33b
Archived-At: <http://mailarchive.ietf.org/arch/msg/icnrg/65jmMh4QGuSqNOtWf3v0nEKe_pk>
Subject: Re: [icnrg] CCNx drafts
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: Wed, 06 Apr 2016 20:05:08 -0000

Hi Nacho,

Can you clarify if Nameless Objects are within the scope of these draft ?. I tried looking for its reference and couldn’t find it in the drafts. These are some of my concerns if nameless objects are in scope:


1.       With Nameless Objects the Interest names are locators and Contentobject hash digest which serve as an identifier is part of the hash restriction. Though at this point the protocol doesn’t  separate the ID/locator name space explicitly in the protocol, it will be good to clarify that names can also be locators when nameless objects are requested. Towards this, I would suggest to define locator names as another namespace  in the semantics document and differentiate it from the names assigned by applications i.e. the producers. This would also be in line with the Manifest proposal which distinguishes Hash IDs and Locators in its definition. This ID/Locator name space separation is what we have been arguing for through the forwarding-label draft.  To complement the nameless object proposal, we also updated the draft with the use case of using Content HashIDs with forwarding-labels in Section 9.2 of the draft https://tools.ietf.org/html/draft-ravi-ccn-forwarding-label-02



2.       Also I would suggest to introduce nameless objects as a new type of content object itself, instead of it being defined as a regular content object which doesn’t have a name TLV for two reasons: Firstly, producers may choose to publish named and nameless version at the same time, explicitly distinguishing them would help forwarders to apply appropriate processing; Second, this differentiates from the case of a malformed named object for which the router may end up computing its hash unnecessarily.



Regards,
Ravi

From: icnrg [mailto:icnrg-bounces@irtf.org] On Behalf Of Ignacio.Solis@parc.com
Sent: Wednesday, April 06, 2016 2:00 PM
To: icnrg@irtf.org
Subject: [icnrg] CCNx drafts

Hi folks.

We are interested in moving the CCNx documents forward. The base docs, moving them towards publication. The ccnx:// one adopting it and moving it towards publication.

https://tools.ietf.org/html/draft-irtf-icnrg-ccnxmessages-02
https://tools.ietf.org/html/draft-irtf-icnrg-ccnxsemantics-02
https://tools.ietf.org/html/draft-mosko-icnrg-ccnxurischeme-00

The drafts have been pretty stable for a while. We made some minor updates to the documents with the Paris feedback and we will be discussing these tomorrow. We know this can be a lengthy process and we wanted to start the discussion on the list.

Please start voicing feedback and concerns.  The base documents are group documents and we would like the group to be ok with what they say.

Cheers,

Nacho

--
Nacho (Ignacio) Solis
Protocol Architect
Principal Scientist
Palo Alto Research Center (PARC)
+1(650)812-4458
Ignacio.Solis@parc.com<mailto:Ignacio.Solis@parc.com>