Re: [icnrg] Pre-Montreal actions for ICNRG participants

"David R. Oran" <daveoran@orandom.net> Fri, 07 June 2019 17:46 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 F35E3120071 for <icnrg@ietfa.amsl.com>; Fri, 7 Jun 2019 10:46:43 -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, SPF_HELO_NONE=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 P-x-H5zqrVLb for <icnrg@ietfa.amsl.com>; Fri, 7 Jun 2019 10:46:42 -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 19E81120058 for <icnrg@irtf.org>; Fri, 7 Jun 2019 10:46:42 -0700 (PDT)
Received: from [174.63.80.213] ([IPv6:2601:184:4081:19c1:28c7:e221:4a87:fc8f]) (authenticated bits=0) by spark.crystalorb.net (8.14.4/8.14.4/Debian-4+deb7u1) with ESMTP id x57HkcuA010320 (version=TLSv1/SSLv3 cipher=AES256-GCM-SHA384 bits=256 verify=NO); Fri, 7 Jun 2019 10:46:40 -0700
From: "David R. Oran" <daveoran@orandom.net>
To: "Mosko, Marc" <mmosko@parc.com>
Cc: ICNRG <icnrg@irtf.org>
Date: Fri, 07 Jun 2019 13:46:38 -0400
X-Mailer: MailMate (1.12.5r5635)
Message-ID: <452E8920-8000-44D0-9B87-AAA0D1C8086E@orandom.net>
In-Reply-To: <BYAPR15MB327257BD5D6C3B1A9AA44ACBAD100@BYAPR15MB3272.namprd15.prod.outlook.com>
References: <EB25435B-B038-4AB9-B4FF-104455FEAF15@orandom.net> <BYAPR15MB327257BD5D6C3B1A9AA44ACBAD100@BYAPR15MB3272.namprd15.prod.outlook.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/icnrg/7tum9-8mf4Ece0QWd25IGwni7Sg>
Subject: Re: [icnrg] Pre-Montreal actions for ICNRG participants
X-BeenThere: icnrg@irtf.org
X-Mailman-Version: 2.1.29
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: Fri, 07 Jun 2019 17:46:44 -0000

Thanks! That would be great.

On 7 Jun 2019, at 13:39, Mosko, Marc wrote:

> I had spoken with Christian some (long) time ago about helping with 
> FLIC, but it got lost in trying to finish up the ccnx specs.  Now that 
> those are done, I can give some time to FLIC.
>
> Marc
>
> ________________________________________
> From: icnrg <icnrg-bounces@irtf.org> on behalf of David R. Oran 
> <daveoran@orandom.net>
> Sent: Friday, June 7, 2019 8:38 AM
> To: ICNRG
> Subject: [icnrg] Pre-Montreal actions for ICNRG participants
>
> Dear ICNRGers,
>
> It’s getting close to meeting again in Montreal in July. There are a 
> bunch of things we went over in Prague that need serious attention 
> from the RG. The chairs have enumerated these below; please try to 
> make time to review and comment on these drafts and give the chairs 
> advice on the best way to move our current work plan forward.
>
> When doing reviews and/or responding to this message, please do a 
> separate message/thread for each of the drafts we want you to review 
> and comment on, and/or weigh in on advice for next steps.
>
> Here goes:
>
> CCNInfo
> https://datatracker.ietf.org/doc/draft-irtf-icnrg-ccninfo/
> Needs ICNRG review and comment - more eyes on it please!
>
> Ping & Traceroute
> https://datatracker.ietf.org/doc/draft-mastorakis-icnrg-icnping/
> https://datatracker.ietf.org/doc/draft-mastorakis-icnrg-icntraceroute/
> These need to be reviewed in the context of overlap and 
> complementarity with CCNInfo. They are relatively mature at this point 
> so what is the ICNRG view on RG adoption?
>
> FLIC draft
> https://datatracker.ietf.org/doc/draft-irtf-icnrg-flic/
> This draft has expired, but it is really important for us as Manifests 
> are a major part of evolving the ICN architecture.
> The Chairs want to strongly encourage some ICNRG folks to pick this up 
> and finish it. It doesn’t need a lot of work to complete, at least 
> for a version 1 specification.
>
> ICN LowPAN
> https://datatracker.ietf.org/doc/draft-irtf-icnrg-icnlowpan/
> Updates were presented in Prague. The authors and chairs think this is 
> getting close to being ready for RG last call. Please review and weigh 
> in on whether we should last call this document.
>
> NRS Documents
> https://datatracker.ietf.org/doc/draft-irtf-icnrg-nrs-requirements/
> https://datatracker.ietf.org/doc/draft-irtf-icnrg-nrsarch-considerations/
> Updates were presented in Prague. These are quite mature at this point 
> and the chairs think they are ready for RG Last Call if the ICNRG 
> participants think they should be moved forward. Please let us know 
> your views on this.
>
> ICN QoS using Disaggregated Names
> https://datatracker.ietf.org/doc/draft-anilj-icnrg-dnc-qos-icn/
> This was presented (remotely) in Prague. Please review and comment as 
> QoS treatments are a fundamental part of any QoS design for ICN.
>
> Quality of Service for ICN in the IoT
> https://datatracker.ietf.org/doc/draft-gundogan-icnrg-iotqos/
> This is a new draft, presented in Prague. Please review and comment.
>
> Flow Classification in Information Centric Networking
> https://datatracker.ietf.org/doc/draft-moiseenko-icnrg-flowclass/
> Presented again in Prague. This had some review a while back, but 
> needs more. Please indicate if you think this is appropriate for 
> adoption now as an RG draft.
>
> Enabling ICN in 3GPP's 5G NextGen Core Architecture
> https://datatracker.ietf.org/doc/draft-ravi-icnrg-5gc-icn/
> Presented in Prague. Needs review and comment, especially as a 
> potential companion to the already-adopted 4G-LTE work.
>
> Your ever-vigilant chairs.

DaveO