Re: [icnrg] CCNx Drafts - next steps
Alex Afanasyev <alexander.afanasyev@ucla.edu> Mon, 06 April 2015 19:29 UTC
Return-Path: <cawka1@gmail.com>
X-Original-To: icnrg@ietfa.amsl.com
Delivered-To: icnrg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0D2FE1A90EA for <icnrg@ietfa.amsl.com>; Mon, 6 Apr 2015 12:29:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.349
X-Spam-Level:
X-Spam-Status: No, score=-2.349 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham
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 IvWWrwjQy3i4 for <icnrg@ietfa.amsl.com>; Mon, 6 Apr 2015 12:29:25 -0700 (PDT)
Received: from mail-pa0-f47.google.com (mail-pa0-f47.google.com [209.85.220.47]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 326B41A90EB for <icnrg@irtf.org>; Mon, 6 Apr 2015 12:29:25 -0700 (PDT)
Received: by paboj16 with SMTP id oj16so53438645pab.0 for <icnrg@irtf.org>; Mon, 06 Apr 2015 12:29:24 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=content-type:mime-version:subject:from:in-reply-to:date:message-id :references:to; bh=yIPvvybBgM7rHl/iJFOdia5CQLGvlZ98D7OG9GG+pfg=; b=fvKu5vmD5uDKOXNjj6fr5MaqdCfdven1YSOB5h7NFAMEXbhBCVtRvo6YoHamNq2wb6 18k90eg43iDyVHqS8Gyls/oew0Q4ean56Z00snavq4XaLOCU2p3WgSw/ij7oOuDc15Ss cAWBEN3mdJYsusvZ1AQ3ggj7aCX9cAbQs7eguxu0kI3p5OROa9RY+VDFf8l6Stbpnqq4 6Nh5AAzK2J0UBVOXBR+Ug231Ca+vmqWr8gGHsIBzaZywg2okfy4e224Ssa1VQYO0VAiC IqWQl0xILArhOVNYwkZnpx71eWs87hbIQEWXtcT0FuSRr+GNn/9xHh/ZzMIFA+gYz89A KNTQ==
X-Received: by 10.68.161.4 with SMTP id xo4mr30129058pbb.65.1428348564707; Mon, 06 Apr 2015 12:29:24 -0700 (PDT)
Received: from ?IPv6:2607:f010:3f9::1004? ([2607:f010:3f9::1004]) by mx.google.com with ESMTPSA id t9sm5597930pas.3.2015.04.06.12.29.23 for <icnrg@irtf.org> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 06 Apr 2015 12:29:23 -0700 (PDT)
Content-Type: multipart/signed; boundary="Apple-Mail=_36446B62-8DE2-438D-A7A3-80F77F72A4AA"; protocol="application/pgp-signature"; micalg="pgp-sha256"
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2070.6\))
X-Pgp-Agent: GPGMail 2.5b6
From: Alex Afanasyev <alexander.afanasyev@ucla.edu>
In-Reply-To: <04969803-D699-48E9-BCA3-4EC7802AE76E@parc.com>
Date: Mon, 06 Apr 2015 12:29:22 -0700
Message-Id: <044961EE-4787-4309-843E-41C2B56B3AD0@ucla.edu>
References: <B3ACABF0-7089-4AC6-826E-9C262A73FD93@parc.com> <98A1BD58-C4B8-497E-8AEB-E720FEF53697@orandom.net> <04969803-D699-48E9-BCA3-4EC7802AE76E@parc.com>
To: icnrg@irtf.org
X-Mailer: Apple Mail (2.2070.6)
Archived-At: <http://mailarchive.ietf.org/arch/msg/icnrg/azkZLInkp2nfWHn1zcj5Pt-VkH0>
Subject: Re: [icnrg] CCNx Drafts - next steps
X-BeenThere: icnrg@irtf.org
X-Mailman-Version: 2.1.15
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: <http://www.irtf.org/mail-archive/web/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, 06 Apr 2015 19:29:28 -0000
> On Apr 6, 2015, at 10:02 AM, Laura.Hill@parc.com wrote: > > Thank you - sorry for the mis-statement - I am new to IETF. We took a sense of the room and people “hummed” that they were in favor of adopting the docs as an experimental platform (not exclusive): > > Hums overwhelmingly agreed we should go forward with the adoption of the documents as an experimental option. > > Laura I want to make a few statements. - People who attended IETF meeting in Dallas represent a small portion of those who are involved with ICN research research group. Therefore, hums, as Dave pointed, represent only a sense of the room (which in my opinion was skewed), not the opinion of the research group. - The conversation and humming was about packet format, not the platform. - I disagree with adopting at this time (even non-exclusively) a packet format that represents an architecture that represents a subset of research efforts of the ICN research group. I'm also against adopting multiple formats that are currently proposed, as I don't see the benefits for the ICNRG research efforts (e.g., to allow faithfully compare the results), as architectures behind the proposed formats have several major differences that directly impact applications. Non-adoption does not prevent any experimentation with the technology and platform(s), rather it allows a more flexible way to evolve protocols, architectures, applications. In my opinion, the latter (the applications) should be the primary focus of the research group. Before adopting a format, there are so many question yet to be answered that no doubt would require certain features/changes from the packet: how ICN and individual proposed architectures allow applications to be implemented in better ways? What are new application patterns become available in ICN? How ICN improves security aspect of applications (+not reduces security of the existing apps)? How to enable seamingless infrastructure-full and infrastructure-less communication in ICN; etc. — Alex >> On Apr 6, 2015, at 9:55 AM, David IMAP Mailstore <daveoran@orandom.net <mailto:daveoran@orandom.net>> wrote: >> >> On Apr 6, 2015, at 9:49 AM, <Laura.Hill@parc.com <mailto:Laura.Hill@parc.com>> <Laura.Hill@parc.com <mailto:Laura.Hill@parc.com>> wrote: >> >>> For those that missed the ICNRG meeting in Dallas, we voted to adopt the CCNx protocol drafts as ICNRG drafts. >> No, we did not. We don't vote. >> We took the sense of the room, which was to adopt the drafts as RG Drafts, as opposed to individual contributions. >> >> Also, per IRTF procedures, no decisions are made definitively in meetings. They are taken by a poll on the mailing list, which has not yet occurred. I hope to get a message on this out to the list this week. >> >> Also, I any of these messages, please be sure people are pointed to the IPR disclosure associated with them so peoe can assess what if any problems that poses. >> >> Thanks (chair hat on) >> DaveO >> >>> Please make sure that you take the time and read through the current set of drafts so you can provide feedback. >>> >>> CCNx Semantics: http://tools.ietf.org/html/draft-mosko-icnrg-ccnxsemantics-01 <http://tools.ietf.org/html/draft-mosko-icnrg-ccnxsemantics-01> >>> This draft describes the semantics of the CCNx protocol independently of encoding. >>> >>> CCNx Packet Format: http://tools.ietf.org/html/draft-mosko-icnrg-ccnxmessages-01 <http://tools.ietf.org/html/draft-mosko-icnrg-ccnxmessages-01> >>> This draft specifies a Type-Length-Value (TLV) packet format and the TLV type and value encodings for the CCNx network protocol as specified in th CCNx Semantics document. >>> >>> For your reference, additional specifications have also been submitted: >>> CCNx Labeled Content: http://tools.ietf.org/html/draft-mosko-icnrg-ccnxlabeledcontent-00 <http://tools.ietf.org/html/draft-mosko-icnrg-ccnxlabeledcontent-00> >>> CCNx Content Object Chunking: http://tools.ietf.org/html/draft-mosko-icnrg-ccnxchunking-00 <http://tools.ietf.org/html/draft-mosko-icnrg-ccnxchunking-00> >>> CCNx End-to-End Fragmentation: http://tools.ietf.org/html/draft-mosko-icnrg-ccnxfragmentation-00 <http://tools.ietf.org/html/draft-mosko-icnrg-ccnxfragmentation-00> >>> CCNx Serial Versioning: http://tools.ietf.org/html/draft-mosko-icnrg-ccnxserialversion-00 <http://tools.ietf.org/html/draft-mosko-icnrg-ccnxserialversion-00> >>> >>> We would like to get a new set of drafts out for the next ICNRG meeting, so keep this in mind if you want to send feedback or contribute. The cut-off date for drafts is 2015-07-06. We would like to have the updates ready at least a week before to schedule meeting time as needed. >>> >>> Many thanks! >>> >>> Laura >>> ---- >>> Laura Hill >>> Manager, Documentation and Information Architecture >>> Palo Alto Research Center (PARC) >>> +1 (650) 812-4493 >>> Laura.Hill@parc.com <mailto:Laura.Hill@parc.com>
- [icnrg] CCNx Drafts - next steps Laura.Hill
- Re: [icnrg] CCNx Drafts - next steps David IMAP Mailstore
- Re: [icnrg] CCNx Drafts - next steps Laura.Hill
- Re: [icnrg] CCNx Drafts - next steps Alex Afanasyev
- Re: [icnrg] CCNx Drafts - next steps Ignacio.Solis
- Re: [icnrg] CCNx Drafts - next steps Stephen Farrell
- Re: [icnrg] CCNx Drafts - next steps MUSCARIELLO Luca IMT/OLN
- Re: [icnrg] CCNx Drafts - next steps Ignacio.Solis
- Re: [icnrg] CCNx Drafts - next steps Marie-Jose Montpetit
- Re: [icnrg] CCNx Drafts - next steps MUSCARIELLO Luca IMT/OLN
- Re: [icnrg] CCNx Drafts - next steps Ignacio.Solis
- Re: [icnrg] CCNx Drafts - next steps Mark Stapp
- Re: [icnrg] CCNx Drafts - next steps MUSCARIELLO Luca IMT/OLN
- Re: [icnrg] CCNx Drafts - next steps Eggert, Lars
- Re: [icnrg] CCNx Drafts - next steps Ignacio.Solis
- Re: [icnrg] CCNx Drafts - next steps MUSCARIELLO Luca IMT/OLN
- Re: [icnrg] CCNx Drafts - next steps David R. Oran
- Re: [icnrg] CCNx Drafts - next steps Ignacio.Solis
- Re: [icnrg] CCNx Drafts - next steps christian.tschudin
- Re: [icnrg] CCNx Drafts - next steps Marc.Mosko
- Re: [icnrg] CCNx Drafts - next steps MUSCARIELLO Luca IMT/OLN
- Re: [icnrg] CCNx Drafts - next steps Ignacio.Solis
- Re: [icnrg] CCNx Drafts - next steps christian.tschudin