[icnrg] Post-Prague actions for ICNRG participants
"David R. Oran" <daveoran@orandom.net> Sat, 06 April 2019 21:12 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 13C3E1200A0 for <icnrg@ietfa.amsl.com>; Sat, 6 Apr 2019 14:12:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, 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 nt_hw_YN0vFT for <icnrg@ietfa.amsl.com>; Sat, 6 Apr 2019 14:12:36 -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 CA3CF12006B for <icnrg@irtf.org>; Sat, 6 Apr 2019 14:12:36 -0700 (PDT)
Received: from [192.168.15.128] ([IPv6:2601:184:4081:19c1:dded:3080:ffc6:d47d]) (authenticated bits=0) by spark.crystalorb.net (8.14.4/8.14.4/Debian-4+deb7u1) with ESMTP id x36LCWNj031378 (version=TLSv1/SSLv3 cipher=AES256-GCM-SHA384 bits=256 verify=NO) for <icnrg@irtf.org>; Sat, 6 Apr 2019 14:12:34 -0700
From: "David R. Oran" <daveoran@orandom.net>
To: ICNRG <icnrg@irtf.org>
Date: Sat, 06 Apr 2019 17:12:32 -0400
X-Mailer: MailMate (1.12.4r5625)
Message-ID: <264A6B23-879D-446D-B9D4-1B8F0F67BB50@orandom.net>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="=_MailMate_0D784943-ECE3-4E6F-8DA4-24AB248C2F40_="
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/icnrg/s6yikp5XrYNPeKWzEvooJp095Yc>
Subject: [icnrg] Post-Prague 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: Sat, 06 Apr 2019 21:12:39 -0000
Dear ICNRGers, Thanks for a really productive pair of meetings at IETF 104 in Prague. Special thanks for folks who made the effort to work on their drafts and move things forward. Now that everybody is back, of course you can chill out and not think about ICNRG until it gets close to meeting again in Montreal in July. No such luck! 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.
- [icnrg] Post-Prague actions for ICNRG participants David R. Oran