[icnrg] CCNx 1.0 selector discovery

<Marc.Mosko@parc.com> Mon, 01 August 2016 16:07 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 6D60512DCAE for <icnrg@ietfa.amsl.com>; Mon, 1 Aug 2016 09:07:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.901
X-Spam-Level:
X-Spam-Status: No, score=-6.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 hj-Qw7SvK3eK for <icnrg@ietfa.amsl.com>; Mon, 1 Aug 2016 09:07:33 -0700 (PDT)
Received: from omega.xerox.com (omega.xerox.com [13.1.64.95]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F0F3412DCAB for <icnrg@irtf.org>; Mon, 1 Aug 2016 09:07:32 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by omega.xerox.com (Postfix) with ESMTP id BA28E520350 for <icnrg@irtf.org>; Mon, 1 Aug 2016 09:07:32 -0700 (PDT)
X-Virus-Scanned: Debian amavisd-new at parc.com
Received: from omega.xerox.com ([127.0.0.1]) by localhost (smtp.parc.xerox.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cwu1h5gzI4Up for <icnrg@irtf.org>; Mon, 1 Aug 2016 09:07:32 -0700 (PDT)
Received: from exchangehub.parc.xerox.com (e2010hub1.parc.xerox.com [13.2.12.22]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by omega.xerox.com (Postfix) with ESMTPS id 995FD5202B6 for <icnrg@irtf.org>; Mon, 1 Aug 2016 09:07:32 -0700 (PDT)
Received: from E2010DAG5.corp.ad.parc.com ([fe80::3d0b:7158:aec4:e05e]) by e2010hub1.corp.ad.parc.com ([fe80::8945:a39d:8c92:373f%11]) with mapi id 14.03.0301.000; Mon, 1 Aug 2016 09:07:32 -0700
From: Marc.Mosko@parc.com
To: icnrg@irtf.org
Thread-Topic: CCNx 1.0 selector discovery
Thread-Index: AQHR7A7Orns1o/4raUeG3Cxq6SKtMA==
Date: Mon, 01 Aug 2016 16:07:31 +0000
Message-ID: <1CF8BBE2-11AA-4E1A-BCFC-275091EAADBE@parc.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [13.2.116.104]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <038F1333546F1E42A777DB8C6A34148E@ad.parc.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/icnrg/3Unc5UkbTM0B_HVQhr10iYTl_OI>
Subject: [icnrg] CCNx 1.0 selector discovery
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: Mon, 01 Aug 2016 16:07:34 -0000

All,

Back in 2014, I believe we discussed how to use an equivalent of NDN/CCNx 0.x selector discovery in CCNx 1.0, but we never publicly published that spec.  It was tied up with some early drafts of CCNx 1.0.  Here is a writeup of how to do the equivalent of selector based discovery on top of CCNx 1.0.  I do not intend this to be the single, canonical way of doing discovery.  I think there are many ways one could do it, and CCNx 1.0 provides the flexibility to use different discovery protocols.

I had to update it a fair bit from the pre-public 1.0 spec it was written against at that time.  Therefore, there may still be a few issues with how it is written up and I would appreciate feedback.

Marc

https://www.ietf.org/id/draft-mosko-icnrg-selectors-00.txt


P.S. 
Some other example discovery protocols are described here:

http://www.ccnx.org/pubs/hhg/4.8%20CCNx%201.0%20Simple%20Service%20Discovery%20for%20Content%20Centric%20Networks.pdf
http://www.ccnx.org/pubs/hhg/4.7%20CCNx%201.0%20Collection%20Synchronization.pdf

P.P.S 
Also on the NDN-INTEREST mailing list, I gave another example that is more SQL-like in syntax and returns row sets (not data objects), and allows one to specifically exclude an entire Content Store.
http://www.lists.cs.ucla.edu/pipermail/ndn-interest/2016-March/001051.html