Return-Path: <Borje.Ohlman@abc.se>
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 99C6212010F
 for <icnrg@ietfa.amsl.com>; Tue, 11 Feb 2020 04:08:03 -0800 (PST)
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, HTML_MESSAGE=0.001, SPF_HELO_NONE=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 rEbymUignh9p for <icnrg@ietfa.amsl.com>;
 Tue, 11 Feb 2020 04:08:00 -0800 (PST)
Received: from hekla.abc.se (hekla.abc.se [158.174.61.227])
 (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 0AA331200F9
 for <icnrg@irtf.org>; Tue, 11 Feb 2020 04:07:59 -0800 (PST)
Received: from emb-w79mfh05.ki.sw.ericsson.se
 (sessfw95-sesbfw95-85.ericsson.net [192.176.1.85])
 by hekla.abc.se (OpenSMTPD) with ESMTPSA id 93d4fa8d
 (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256:NO) for <icnrg@irtf.org>;
 Tue, 11 Feb 2020 13:07:58 +0100 (CET)
From: =?utf-8?Q?B=C3=B6rje_Ohlman?= <Borje.Ohlman@abc.se>
Content-Type: multipart/alternative;
 boundary="Apple-Mail=_28F2C646-3EBC-4343-9E93-7BBCFE948868"
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\))
Message-Id: <A4488FED-AFCE-42F5-A3DB-B3C72501C245@abc.se>
Date: Tue, 11 Feb 2020 13:07:55 +0100
To: icnrg <icnrg@irtf.org>
X-Mailer: Apple Mail (2.3445.104.11)
Archived-At: <https://mailarchive.ietf.org/arch/msg/icnrg/4jpNTTqkDnC4hEq2M82XmvFDJSs>
Subject: [icnrg] Next ICNRG meetings in Vancouver: Agenda proposals are invited
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: Tue, 11 Feb 2020 12:08:04 -0000


--Apple-Mail=_28F2C646-3EBC-4343-9E93-7BBCFE948868
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

ICNRG will meet at the IETF 107 Vancouver, 21 Mar 2020 - 27 Mar 2020  We =
plan to have a full day interim Sunday, March 22nd and a regular ICNRG =
meeting sometime during the IETF week.

Agenda proposals for our ICNRG meetings in Vancouver are invited. Please =
send your proposals to the mailing list or directly to the chairs.

Invited agenda topics include, but are not limited to:=20
ICN & QoS
ICN & IoT
ICN & NRS,=20
Measurement and Instrumentation
Enhancements to base CCNx protocols (Manifests, Path Steering, Flow =
Balance enhancements, reflexive forwarding extensions).
=E2=80=A6
Please also see Dave=E2=80=99s excellent list on ICNRG ToDo:s, the email =
containing it is attached for your convenience.

Registration - Please register for the interim meeting Sunday March 22nd=20=


 =
<http://trac.tools.ietf.org/group/irtf/trac/wiki/icnrg#Registration-Please=
registerfortheinterimmeeting>
We are looking for a sponsor of the interim meeting that could offer =
refreshments during the breaks. Proposals are most welcome''
For more info please see: =
http://trac.tools.ietf.org/group/irtf/trac/wiki/icnrg =
<http://trac.tools.ietf.org/group/irtf/trac/wiki/icnrg>


B=C3=B6rje, Dave & Dirk
_______________________________________________

--Apple-Mail=_28F2C646-3EBC-4343-9E93-7BBCFE948868
Content-Type: multipart/mixed;
 boundary="Apple-Mail=_31985124-D2E6-4B5D-AFE2-ED53B44F5F18"


--Apple-Mail=_31985124-D2E6-4B5D-AFE2-ED53B44F5F18
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=utf-8

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html; =
charset=3Dutf-8"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; line-break: after-white-space;" class=3D"">
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dutf-8" =
class=3D""><div style=3D"word-wrap: break-word; -webkit-nbsp-mode: =
space; line-break: after-white-space;" class=3D"">



<div style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; =
line-break: after-white-space;" class=3D"">
<div style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; =
-webkit-line-break: after-white-space;" class=3D""><p class=3D""><font =
face=3D"Times New Roman, times, serif" class=3D""><span =
style=3D"font-size: 15px;" class=3D"">ICNRG will meet at the IETF 107 =
Vancouver, 21 Mar 2020 - 27 Mar&nbsp;2020&nbsp; We plan to have =
a&nbsp;full day interim&nbsp;Sunday, March 22nd and a regular ICNRG =
meeting sometime during the IETF week.</span></font></p><p =
class=3D""><strong class=3D""><font face=3D"Times New Roman, times, =
serif" class=3D""><span style=3D"font-size: 15px;" class=3D"">Agenda =
proposals for&nbsp;our ICNRG meetings in Vancouver are invited. Please =
send your proposals to the mailing list or directly to the =
chairs.</span></font></strong></p>
<ul style=3D"font-family: 'Times New Roman', times, serif; font-size: =
15px;" class=3D"">
<li class=3D"">Invited agenda topics include, but are not limited =
to:&nbsp;</li><li class=3D"">ICN &amp; QoS</li><li class=3D"">ICN &amp; =
IoT</li><li class=3D"">ICN &amp; NRS,&nbsp;<li class=3D"">Measurement =
and Instrumentation
</li><li class=3D"">Enhancements to base CCNx protocols (Manifests, Path =
Steering, Flow Balance enhancements, reflexive forwarding extensions).
</li><li class=3D"">=E2=80=A6</li></li></ul>
<h3 id=3D"Agenda" style=3D"font-family: Arial, Verdana, 'Bitstream Vera =
Sans', Helvetica, sans-serif; letter-spacing: -0.018em; =
page-break-after: avoid; font-size: 14px; margin-left: -18px;" =
class=3D""><i class=3D"">Please also see Dave=E2=80=99s excellent list =
on ICNRG ToDo:s, the email containing it is attached for your =
convenience.</i></h3><h3 id=3D"Agenda" style=3D"font-family: Arial, =
Verdana, 'Bitstream Vera Sans', Helvetica, sans-serif; letter-spacing: =
-0.018em; page-break-after: avoid; font-size: 14px; margin-left: -18px;" =
class=3D"">
<span style=3D"letter-spacing: -0.018em;" class=3D"">Registration - =
Please register for the interim meeting Sunday March =
22nd&nbsp;</span></h3>
<h3 id=3D"Registration-Pleaseregisterfortheinterimmeeting" =
style=3D"font-family: Arial, Verdana, 'Bitstream Vera Sans', Helvetica, =
sans-serif; letter-spacing: -0.018em; page-break-after: avoid; =
font-size: 14px; margin-left: -18px;" class=3D"">
<a class=3D"anchor" =
href=3D"http://trac.tools.ietf.org/group/irtf/trac/wiki/icnrg#Registration=
-Pleaseregisterfortheinterimmeeting" title=3D"Link to this section" =
style=3D"color: rgb(215, 215, 215); border: none; font-size: 0.8em; =
vertical-align: text-top; visibility: hidden;"></a></h3>
<ul style=3D"font-family: 'Times New Roman', times, serif; font-size: =
15px;" class=3D"">
<li class=3D""><em class=3D"">We are looking for a sponsor of the =
interim meeting that could offer refreshments during the breaks. =
Proposals are most welcome''</em></li></ul>
<div class=3D"">For more info please see:&nbsp;<a =
href=3D"http://trac.tools.ietf.org/group/irtf/trac/wiki/icnrg" =
class=3D"">http://trac.tools.ietf.org/group/irtf/trac/wiki/icnrg</a></div>=

<div class=3D""><br class=3D"">
</div>
<div class=3D""><br class=3D"">
</div>
<div class=3D""><span class=3D"Apple-tab-span" =
style=3D"white-space:pre"></span>B=C3=B6rje, Dave &amp; Dirk</div>
_______________________________________________<br =
class=3D""></div></div></div></body></html>=

--Apple-Mail=_31985124-D2E6-4B5D-AFE2-ED53B44F5F18
Content-Disposition: attachment;
 filename*0="[icnrg] Status from Chairs and actions for the ICNRG participant"; 
 filename*1="s: Resend with some updates.eml"
Content-Type: message/rfc822; x-mac-hide-extension=yes; x-unix-mode=0666;
 name="[icnrg] Status from Chairs and actions for the ICNRG participants:
 Resend with some updates.eml"
Content-Transfer-Encoding: binary

Return-Path: <icnrg-bounces@irtf.org>
X-Spam-Checker-Version: SpamAssassin 3.4.3 (2019-12-06) on hekla.abc.se
X-Spam-Level: 
X-Spam-Status: No, score=-3.0 required=5.0 tests=DKIMWL_WL_HIGH,DKIM_SIGNED,
 DKIM_VALID,HEADER_FROM_DIFFERENT_DOMAINS,HTML_MESSAGE,
 MAILING_LIST_MULTI,RCVD_IN_DNSWL_MED,SPF_HELO_NONE,SPF_PASS
 autolearn=disabled version=3.4.3
Delivered-To: Borje.Ohlman@abc.se
Received: from mail.ietf.org (mail.ietf.org [4.31.198.44])
 by hekla.abc.se (OpenSMTPD) with ESMTPS id babf91e5
 (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256:NO)
 for <Borje.Ohlman@abc.se>; Mon, 27 Jan 2020 16:11:59 +0100 (CET)
Received: from ietfa.amsl.com (localhost [IPv6:::1])
 by ietfa.amsl.com (Postfix) with ESMTP id 2B2D7120839
 for <Borje.Ohlman@abc.se>; Mon, 27 Jan 2020 07:11:57 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1;
 t=1580137917; bh=ZqtkkJ3BELKGd9ksA+FOALQwYnDucyMBCYEBOlRtgUY=;
 h=From:To:Date:Subject:List-Id:List-Unsubscribe:List-Archive:
 List-Post:List-Help:List-Subscribe;
 b=JR4yXdSX1TXnJ1QAdWDNtPs0F87/cGS025emN80L56IWDuqjfAg/02FVXYxm2lHwY
 H217nE0zQ6783SOcROTuBilYxEHjK9j78roLK6lXY7xQ8Z9TAm1Lxl13YalEtYbmgc
 hH00QgDJxp/Nh3gCXog8N4YhTtBK61sdtLh/qSNA=
X-Mailbox-Line: From icnrg-bounces@irtf.org  Mon Jan 27 07:11:53 2020
Received: from ietfa.amsl.com (localhost [IPv6:::1])
 by ietfa.amsl.com (Postfix) with ESMTP id B36C61208BE;
 Mon, 27 Jan 2020 07:11:49 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1;
 t=1580137909; bh=ZqtkkJ3BELKGd9ksA+FOALQwYnDucyMBCYEBOlRtgUY=;
 h=From:To:Date:Subject:List-Id:List-Unsubscribe:List-Archive:
 List-Post:List-Help:List-Subscribe;
 b=xYhHjBMfs6QF7Dad3Wpw7rO00nzdL0XfTa7WZJ0NWOMAYa1YHEdjyB1csZQK250DA
 hRnEXNTyQ8dLwJYbQdc0hIAAnFpa9jaf3Gux1Z5b4rG5HcXCoqlu4S2exc3HBAPMJe
 JZWqeIa47cy2tJPI9jvWdM68sK/UN3feVbq2e0VE=
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 821B912082A
 for <icnrg@ietfa.amsl.com>; Mon, 27 Jan 2020 07:11:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
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 ZnUK6znw1wZK for <icnrg@ietfa.amsl.com>;
 Mon, 27 Jan 2020 07:11:41 -0800 (PST)
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 12DE9120864
 for <icnrg@irtf.org>; Mon, 27 Jan 2020 07:11:41 -0800 (PST)
Received: from [192.168.15.102] ([IPv6:2601:184:407f:80ce:b185:bb81:5473:a3a5])
 (authenticated bits=0)
 by spark.crystalorb.net (8.14.4/8.14.4/Debian-4+deb7u1) with ESMTP id
 00RFBaPl001113
 (version=TLSv1/SSLv3 cipher=AES256-GCM-SHA384 bits=256 verify=NO)
 for <icnrg@irtf.org>; Mon, 27 Jan 2020 07:11:38 -0800
From: "David R. Oran" <daveoran@orandom.net>
To: ICNRG <icnrg@irtf.org>
Date: Mon, 27 Jan 2020 10:11:30 -0500
X-Mailer: MailMate (1.13.1r5676)
Message-ID: <9C1F9A85-C830-417D-BF46-DD103E14B21B@orandom.net>
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/icnrg/pkh1huGR_3HynTd9dzQ1hfvzsVk>
Subject: [icnrg] Status from Chairs and actions for the ICNRG participants:
 Resend with some updates
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>
Content-Type: multipart/mixed; boundary="===============4329396420508431507=="
Errors-To: icnrg-bounces@irtf.org
Sender: "icnrg" <icnrg-bounces@irtf.org>


--===============4329396420508431507==
Content-Type: multipart/alternative;
 boundary="=_MailMate_516B45E4-26A0-48B6-9F60-946AD2639542_="
Content-Transfer-Encoding: 8bit


--=_MailMate_516B45E4-26A0-48B6-9F60-946AD2639542_=
Content-Type: text/plain; charset="UTF-8"; format=flowed; markup=markdown
Content-Transfer-Encoding: 8bit

First, Happy New Year to everybody! We hope you had a good holiday 
season and are recharged to help ICNRG move our work forward in 2020. 
This message serves to give current RG status, request reviews and other 
actions from you folks, and remind people of our plans for the Vancouver 
IETF in March. Specific actions we would like from you are in **bold**. 
As you can see, we’ve got a lot of interesting work ahead of us!

Two notes on this resend:
1. The original message said the Vancouver Interim was scheduled for 
Saturday. It is actually on *Sunday*.

2. Please check the Wiki for agenda planning. In particular, we are 
looking for talks on the topic areas we plan to concentrate on at the 
Sunday Interim.

###First, some status updates:###

- “Deployment Considerations for Information-Centric Networking 
(ICN)” 
(https://datatracker.ietf.org/doc/draft-irtf-icnrg-deployment-guidelines/) 
is now in the RFC Editor queue for final processing and publication as 
an Informational RFC.

- Both “Research Directions for Using ICN in Disaster Scenarios” 
(https://datatracker.ietf.org/doc/draft-irtf-icnrg-disaster/) and 
“Information-Centric Networking (ICN): CCNx and NDN Terminology” 
(https://datatracker.ietf.org/doc/draft-irtf-icnrg-terminology/) have 
successfully passed IESG Conflict Review and will be soon going to the 
RFC editor for publication. The former needs a few editorial updates; 
the latter has been updated and is in the hands of the IRTF chair to 
move into final editing.

- “Native Deployment of ICN in LTE, 4G Mobile Networks” 
(https://datatracker.ietf.org/doc/draft-irtf-icnrg-icn-lte-4g/) has 
passed RG last call, last call comments have been addressed in the 
latest version, and it is now in the IRTF chair’s hands to initiate 
the IRSG Review.

- “Architectural Considerations of ICN using Name Resolution 
Service” 
(https://datatracker.ietf.org/doc/draft-irtf-icnrg-nrsarch-considerations/) 
has passed RG last call and we will be submitting it for IRSG Review in 
the coming days.

- “Design Guidelines for Name Resolution Service in ICN” 
(https://datatracker.ietf.org/doc/draft-irtf-icnrg-nrs-requirements/) 
has some last call comments that need further consideration and hence we 
will be issuing a second Last Call on this document in the coming days.

- “ICN Adaptation to LowPAN Networks (ICN LoWPAN)” 
(https://datatracker.ietf.org/doc/draft-irtf-icnrg-icnlowpan/) has 
gotten wide support and we will be issuing an RG Last Call for it in the 
coming days. Please look for the last call announcement and 
**re-review** this important document.

###Second, please take time to review the these active RG documents##
We hope to move them forward toward last call if appropriate, in time to 
discuss in Vancouver.

- We recently adopted “Enabling ICN in 3GPP's 5G NextGen Core 
Architecture” 
(https://datatracker.ietf.org/doc/draft-irtf-icnrg-5gc-icn/) as an ICNRG 
working draft. **Please review** so we can discuss moving this forward.

- “File-Like ICN Collections (FLIC)” 
(https://datatracker.ietf.org/doc/draft-irtf-icnrg-flic/) got a major 
update just prior to the Singapore meeting and urgently needs more 
review. The authors plan to have an updated draft prior to Vancouver, 
but **please review the current version** so we can make progress as 
rapidly as possible. The hope is to be able to issue a last call soon 
after our Vancouver meeting.

###Third, please take time to review the these active individual 
contributions and weigh in on whether they should be adopted as ICNRG 
working drafts.##
We hope decide about these in time to discuss in Vancouver.

- “Internet Services over ICN in 5G LAN Environments” 
(https://datatracker.ietf.org/doc/draft-trossen-icnrg-internet-icn-5glan/) 
**needs review**.

- “Considerations in the development of a QoS Architecture for 
CCNx-like ICN protocols” 
(https://datatracker.ietf.org/doc/draft-oran-icnrg-qosarch/) **needs 
review**. Also look for a message from Börje or Dirk about the 
chairs’ proposed next steps for this document.

- “Path Steering in CCNx and NDN” 
(https://datatracker.ietf.org/doc/draft-oran-icnrg-pathsteering/) 
**needs review and assessment of suitability to adopt as an ICNRG 
working draft**.

- “Maintaining CCNx or NDN flow balance with highly variable data 
object sizes” 
(https://datatracker.ietf.org/doc/draft-oran-icnrg-flowbalance/) **needs 
review and assessment of suitability to adopt as an ICNRG working 
draft**.

- “Flow Classification in Information Centric Networking” 
(https://datatracker.ietf.org/doc/draft-moiseenko-icnrg-flowclass/) 
**needs review and assessment of suitability to adopt as an ICNRG 
working draft**.

- “QoS Treatments in ICN using Disaggregated Name Components” 
(https://datatracker.ietf.org/doc/draft-anilj-icnrg-dnc-qos-icn/) 
**needs review and assessment of suitability to adopt as an ICNRG 
working draft**.

- “ICN Traceroute Protocol Specification” 
(https://datatracker.ietf.org/doc/draft-mastorakis-icnrg-icntraceroute/) 
and “ICN Ping Protocol Specification” 
(https://datatracker.ietf.org/doc/draft-mastorakis-icnrg-icnping/) has 
had review, but we **need advice about adoption as RG documents**

- “Hop-by-Hop Authentication in Content-Centric Networking/Named Data 
Networking” (https://datatracker.ietf.org/doc/draft-li-icnrg-hopauth/) 
**needs review and assessment of suitability to adopt as an ICNRG 
working draft**.

- “An Alternative Delta Time encoding for CCNx using Interval Time 
from RFC5497” 
(https://datatracker.ietf.org/doc/draft-gundogan-icnrg-ccnx-timetlv/) 
**needs review and assessment of suitability to adopt as an ICNRG 
working draft**.

- “Requirements and Challenges for User-level Service Managements of 
IoT Network by utilizing Artificial Intelligence” 
(https://datatracker.ietf.org/doc/draft-choi-icnrg-aiot/) **needs 
initial review**.

###Fourth, we have started planning logistics and agendas for our 
meetings at IETF 107 in Vancouver, March 21-27.###

We plan to have both a regular meeting during the week and an all-day 
Interim meeting on Sunday. We hope to devote the Interim to a few “hot 
topics”, and have proposed that these be:
	— Quality of Service
	— Measurement and Instrumentation
	— Enhancements to base CCNx protocols (Manifests, Path Steering, Flow 
Balance enhancements, reflexive forwarding extensions).

So, please **propose agenda items**, consider **giving a talk** on one 
of the discussion topic areas identified for the interim meeting, and 
**register for the interim as customary** (by editing the Wiki page at 
https://trac.ietf.org/trac/irtf/wiki/icnrg).

Thanks for not treating this as TL;DR and actually getting to the end!!

Your ever-vigilant Chairs, Börje, Dirk and DaveO.

--=_MailMate_516B45E4-26A0-48B6-9F60-946AD2639542_=
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE html>
<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/xhtml; charset=3Dutf-8"=
>
</head>
<body>
<div style=3D"font-family:sans-serif"><div style=3D"white-space:normal">
<p dir=3D"auto">First, Happy New Year to everybody! We hope you had a goo=
d holiday season and are recharged to help ICNRG move our work forward in=
 2020. This message serves to give current RG status, request reviews and=
 other actions from you folks, and remind people of our plans for the Van=
couver IETF in March. Specific actions we would like from you are in <str=
ong>bold</strong>. As you can see, we=E2=80=99ve got a lot of interesting=
 work ahead of us!</p>

<p dir=3D"auto">Two notes on this resend:<br>
1. The original message said the Vancouver Interim was scheduled for Satu=
rday. It is actually on <em>Sunday</em>.</p>

<ol>
<li value=3D"2">Please check the Wiki for agenda planning. In particular,=
 we are looking for talks on the topic areas we plan to concentrate on at=
 the Sunday Interim.</li>
</ol>

<h3 style=3D"font-size:1.1em">First, some status updates:</h3>

<ul>
<li><p dir=3D"auto">=E2=80=9CDeployment Considerations for Information-Ce=
ntric Networking (ICN)=E2=80=9D (<a href=3D"https://datatracker.ietf.org/=
doc/draft-irtf-icnrg-deployment-guidelines/" style=3D"color:#3983C4">http=
s://datatracker.ietf.org/doc/draft-irtf-icnrg-deployment-guidelines/</a>)=
 is now in the RFC Editor queue for final processing and publication as a=
n Informational RFC.</p></li>
<li><p dir=3D"auto">Both =E2=80=9CResearch Directions for Using ICN in Di=
saster Scenarios=E2=80=9D (<a href=3D"https://datatracker.ietf.org/doc/dr=
aft-irtf-icnrg-disaster/" style=3D"color:#3983C4">https://datatracker.iet=
f.org/doc/draft-irtf-icnrg-disaster/</a>) and =E2=80=9CInformation-Centri=
c Networking (ICN): CCNx and NDN Terminology=E2=80=9D (<a href=3D"https:/=
/datatracker.ietf.org/doc/draft-irtf-icnrg-terminology/" style=3D"color:#=
3983C4">https://datatracker.ietf.org/doc/draft-irtf-icnrg-terminology/</a=
>) have successfully passed IESG Conflict Review and will be soon going t=
o the RFC editor for publication. The former needs a few editorial update=
s; the latter has been updated and is in the hands of the IRTF chair to m=
ove into final editing.</p></li>
<li><p dir=3D"auto">=E2=80=9CNative Deployment of ICN in LTE, 4G Mobile N=
etworks=E2=80=9D (<a href=3D"https://datatracker.ietf.org/doc/draft-irtf-=
icnrg-icn-lte-4g/" style=3D"color:#3983C4">https://datatracker.ietf.org/d=
oc/draft-irtf-icnrg-icn-lte-4g/</a>) has passed RG last call, last call c=
omments have been addressed in the latest version, and it is now in the I=
RTF chair=E2=80=99s hands to initiate the IRSG Review.</p></li>
<li><p dir=3D"auto">=E2=80=9CArchitectural Considerations of ICN using Na=
me Resolution Service=E2=80=9D (<a href=3D"https://datatracker.ietf.org/d=
oc/draft-irtf-icnrg-nrsarch-considerations/" style=3D"color:#3983C4">http=
s://datatracker.ietf.org/doc/draft-irtf-icnrg-nrsarch-considerations/</a>=
) has passed RG last call and we will be submitting it for IRSG Review in=
 the coming days.</p></li>
<li><p dir=3D"auto">=E2=80=9CDesign Guidelines for Name Resolution Servic=
e in ICN=E2=80=9D (<a href=3D"https://datatracker.ietf.org/doc/draft-irtf=
-icnrg-nrs-requirements/" style=3D"color:#3983C4">https://datatracker.iet=
f.org/doc/draft-irtf-icnrg-nrs-requirements/</a>) has some last call comm=
ents that need further consideration and hence we will be issuing a secon=
d Last Call on this document in the coming days.</p></li>
<li><p dir=3D"auto">=E2=80=9CICN Adaptation to LowPAN Networks (ICN LoWPA=
N)=E2=80=9D (<a href=3D"https://datatracker.ietf.org/doc/draft-irtf-icnrg=
-icnlowpan/" style=3D"color:#3983C4">https://datatracker.ietf.org/doc/dra=
ft-irtf-icnrg-icnlowpan/</a>) has gotten wide support and we will be issu=
ing an RG Last Call for it in the coming days. Please look for the last c=
all announcement and <strong>re-review</strong> this important document.<=
/p></li>
</ul>

<h3 style=3D"font-size:1.1em">Second, please take time to review the thes=
e active RG documents</h3>

<p dir=3D"auto">We hope to move them forward toward last call if appropri=
ate, in time to discuss in Vancouver.</p>

<ul>
<li><p dir=3D"auto">We recently adopted =E2=80=9CEnabling ICN in 3GPP's 5=
G NextGen Core Architecture=E2=80=9D (<a href=3D"https://datatracker.ietf=
=2Eorg/doc/draft-irtf-icnrg-5gc-icn/" style=3D"color:#3983C4">https://dat=
atracker.ietf.org/doc/draft-irtf-icnrg-5gc-icn/</a>) as an ICNRG working =
draft. <strong>Please review</strong> so we can discuss moving this forwa=
rd.</p></li>
<li><p dir=3D"auto">=E2=80=9CFile-Like ICN Collections (FLIC)=E2=80=9D (<=
a href=3D"https://datatracker.ietf.org/doc/draft-irtf-icnrg-flic/" style=3D=
"color:#3983C4">https://datatracker.ietf.org/doc/draft-irtf-icnrg-flic/</=
a>) got a major update just prior to the Singapore meeting and urgently n=
eeds more review. The authors plan to have an updated draft prior to Vanc=
ouver, but <strong>please review the current version</strong> so we can m=
ake progress as rapidly as possible. The hope is to be able to issue a la=
st call soon after our Vancouver meeting.</p></li>
</ul>

<h3 style=3D"font-size:1.1em">Third, please take time to review the these=
 active individual contributions and weigh in on whether they should be a=
dopted as ICNRG working drafts.</h3>

<p dir=3D"auto">We hope decide about these in time to discuss in Vancouve=
r.</p>

<ul>
<li><p dir=3D"auto">=E2=80=9CInternet Services over ICN in 5G LAN Environ=
ments=E2=80=9D (<a href=3D"https://datatracker.ietf.org/doc/draft-trossen=
-icnrg-internet-icn-5glan/" style=3D"color:#3983C4">https://datatracker.i=
etf.org/doc/draft-trossen-icnrg-internet-icn-5glan/</a>) <strong>needs re=
view</strong>.</p></li>
<li><p dir=3D"auto">=E2=80=9CConsiderations in the development of a QoS A=
rchitecture for CCNx-like ICN protocols=E2=80=9D (<a href=3D"https://data=
tracker.ietf.org/doc/draft-oran-icnrg-qosarch/" style=3D"color:#3983C4">h=
ttps://datatracker.ietf.org/doc/draft-oran-icnrg-qosarch/</a>) <strong>ne=
eds review</strong>. Also look for a message from B=C3=B6rje or Dirk abou=
t the chairs=E2=80=99 proposed next steps for this document.</p></li>
<li><p dir=3D"auto">=E2=80=9CPath Steering in CCNx and NDN=E2=80=9D (<a h=
ref=3D"https://datatracker.ietf.org/doc/draft-oran-icnrg-pathsteering/" s=
tyle=3D"color:#3983C4">https://datatracker.ietf.org/doc/draft-oran-icnrg-=
pathsteering/</a>) <strong>needs review and assessment of suitability to =
adopt as an ICNRG working draft</strong>.</p></li>
<li><p dir=3D"auto">=E2=80=9CMaintaining CCNx or NDN flow balance with hi=
ghly variable data object sizes=E2=80=9D (<a href=3D"https://datatracker.=
ietf.org/doc/draft-oran-icnrg-flowbalance/" style=3D"color:#3983C4">https=
://datatracker.ietf.org/doc/draft-oran-icnrg-flowbalance/</a>) <strong>ne=
eds review and assessment of suitability to adopt as an ICNRG working dra=
ft</strong>.</p></li>
<li><p dir=3D"auto">=E2=80=9CFlow Classification in Information Centric N=
etworking=E2=80=9D (<a href=3D"https://datatracker.ietf.org/doc/draft-moi=
seenko-icnrg-flowclass/" style=3D"color:#3983C4">https://datatracker.ietf=
=2Eorg/doc/draft-moiseenko-icnrg-flowclass/</a>) <strong>needs review and=
 assessment of suitability to adopt as an ICNRG working draft</strong>.</=
p></li>
<li><p dir=3D"auto">=E2=80=9CQoS Treatments in ICN using Disaggregated Na=
me Components=E2=80=9D (<a href=3D"https://datatracker.ietf.org/doc/draft=
-anilj-icnrg-dnc-qos-icn/" style=3D"color:#3983C4">https://datatracker.ie=
tf.org/doc/draft-anilj-icnrg-dnc-qos-icn/</a>) <strong>needs review and a=
ssessment of suitability to adopt as an ICNRG working draft</strong>.</p>=
</li>
<li><p dir=3D"auto">=E2=80=9CICN Traceroute Protocol Specification=E2=80=9D=
 (<a href=3D"https://datatracker.ietf.org/doc/draft-mastorakis-icnrg-icnt=
raceroute/" style=3D"color:#3983C4">https://datatracker.ietf.org/doc/draf=
t-mastorakis-icnrg-icntraceroute/</a>) and =E2=80=9CICN Ping Protocol Spe=
cification=E2=80=9D (<a href=3D"https://datatracker.ietf.org/doc/draft-ma=
storakis-icnrg-icnping/" style=3D"color:#3983C4">https://datatracker.ietf=
=2Eorg/doc/draft-mastorakis-icnrg-icnping/</a>) has had review, but we <s=
trong>need advice about adoption as RG documents</strong></p></li>
<li><p dir=3D"auto">=E2=80=9CHop-by-Hop Authentication in Content-Centric=
 Networking/Named Data Networking=E2=80=9D (<a href=3D"https://datatracke=
r.ietf.org/doc/draft-li-icnrg-hopauth/" style=3D"color:#3983C4">https://d=
atatracker.ietf.org/doc/draft-li-icnrg-hopauth/</a>) <strong>needs review=
 and assessment of suitability to adopt as an ICNRG working draft</strong=
>.</p></li>
<li><p dir=3D"auto">=E2=80=9CAn Alternative Delta Time encoding for CCNx =
using Interval Time from RFC5497=E2=80=9D (<a href=3D"https://datatracker=
=2Eietf.org/doc/draft-gundogan-icnrg-ccnx-timetlv/" style=3D"color:#3983C=
4">https://datatracker.ietf.org/doc/draft-gundogan-icnrg-ccnx-timetlv/</a=
>) <strong>needs review and assessment of suitability to adopt as an ICNR=
G working draft</strong>.</p></li>
<li><p dir=3D"auto">=E2=80=9CRequirements and Challenges for User-level S=
ervice Managements of IoT Network by utilizing Artificial Intelligence=E2=
=80=9D (<a href=3D"https://datatracker.ietf.org/doc/draft-choi-icnrg-aiot=
/" style=3D"color:#3983C4">https://datatracker.ietf.org/doc/draft-choi-ic=
nrg-aiot/</a>) <strong>needs initial review</strong>.</p></li>
</ul>

<h3 style=3D"font-size:1.1em">Fourth, we have started planning logistics =
and agendas for our meetings at IETF 107 in Vancouver, March 21-27.</h3>

<p dir=3D"auto">We plan to have both a regular meeting during the week an=
d an all-day Interim meeting on Sunday. We hope to devote the Interim to =
a few =E2=80=9Chot topics=E2=80=9D, and have proposed that these be:<br>
    =E2=80=94 Quality of Service<br>
    =E2=80=94 Measurement and Instrumentation<br>
    =E2=80=94 Enhancements to base CCNx protocols (Manifests, Path Steeri=
ng, Flow Balance enhancements, reflexive forwarding extensions).</p>

<p dir=3D"auto">So, please <strong>propose agenda items</strong>, conside=
r <strong>giving a talk</strong> on one of the discussion topic areas ide=
ntified for the interim meeting, and <strong>register for the interim as =
customary</strong> (by editing the Wiki page at <a href=3D"https://trac.i=
etf.org/trac/irtf/wiki/icnrg" style=3D"color:#3983C4">https://trac.ietf.o=
rg/trac/irtf/wiki/icnrg</a>).</p>

<p dir=3D"auto">Thanks for not treating this as TL;DR and actually gettin=
g to the end!!</p>

<p dir=3D"auto">Your ever-vigilant Chairs, B=C3=B6rje, Dirk and DaveO.</p=
>
</div>
</div>
</body>
</html>

--=_MailMate_516B45E4-26A0-48B6-9F60-946AD2639542_=--


--===============4329396420508431507==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
icnrg mailing list
icnrg@irtf.org
https://www.irtf.org/mailman/listinfo/icnrg

--===============4329396420508431507==--

--Apple-Mail=_31985124-D2E6-4B5D-AFE2-ED53B44F5F18
Content-Transfer-Encoding: 7bit
Content-Type: text/html;
	charset=us-ascii

<html><head><meta http-equiv="Content-Type" content="text/html; charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">
</div>
</div>

</div></body></html>
--Apple-Mail=_31985124-D2E6-4B5D-AFE2-ED53B44F5F18--

--Apple-Mail=_28F2C646-3EBC-4343-9E93-7BBCFE948868--

