Re: [icnrg] Last Call: draft-irtf-icnrg-icnlowpan

"Dirk Kutscher" <> Tue, 11 February 2020 10:54 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id CADD61200B7 for <>; Tue, 11 Feb 2020 02:54:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.299
X-Spam-Status: No, score=-1.299 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_SBL=0.5, URIBL_SBL_A=0.1] autolearn=no autolearn_force=no
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id pqLA4j90sjSh for <>; Tue, 11 Feb 2020 02:54:20 -0800 (PST)
Received: from ( []) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 0182C12007C for <>; Tue, 11 Feb 2020 02:54:19 -0800 (PST)
Received: from [] ([]) by (mreue009 []) with ESMTPSA (Nemesis) id 1MQeIA-1iotpy1iqM-00NhyX; Tue, 11 Feb 2020 11:54:12 +0100
From: Dirk Kutscher <>
To: Colin Perkins <>
Cc: ICNRG <>
Date: Tue, 11 Feb 2020 11:54:06 +0100
X-Mailer: MailMate (1.13.1r5671)
Message-ID: <>
In-Reply-To: <>
References: <> <>
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 8bit
X-Provags-ID: V03:K1:85XbxTPePc3ZMYpGgp+XKbFBY45eLQx5Wuy6UT9iJtA2hKbIusj flt3I/Vq9SqYIX7mr83K5f/hFxj/CySfzzfG3tjiKHpgEHgppVmQJZVXDqHzSV4IWDr4SoV t+n/7RbKri8+H5j9pDXnajHZt6Nin6qNq/HPdWbH62GqjeiRBAaQGzTQmdQ5gDCMiAWsh6B fAhHVHSIl4QKQw6mCIXcg==
X-UI-Out-Filterresults: notjunk:1;V03:K0:CY6vv9u60J8=:dsrtj0ahCsrQxrAPxmnYM4 tdVv4ygAXzW8BOHV9V7OC6jul9kTyqmLdVRwqyMx8G6lEmQE2ybws15/os5bLzYkWG55YRIjQ SGRKqqhOykTQs1LLbt0bFTQIkQAo4ly3Mrb9msWzYscoC9/6MGSMV4Yr7+saf55wJ6JE30/ed fNAR12DX2zoVKH8bgGMRZRE6tu1f3vN3bSnGZwerbMpDX28VJPvJ0ZmdRAWrBj8xZE/YyaVwz xyfHHcfmsU0h13teBMITNt6EYryMaJedmRLLwpYnWgGZDZnR5FnQeA0LhJdpU9JSplHlTZ290 ITjyqB3+sPbPadDnXrkEn/r+dfMGVptzwRQ3cfKmUdtDQrvEG6Vbp7oIvypgahzb21nXxcV/M OtSNHaGeOanHkEPqvrqxVIgHZamtJeYQq+7AFNTd8Fi7SEC6+sT2EF11mhYjqabYsyoOXxZEK 1nmvDkjEoZoHwffSi/PAGriC0xNe0ui0lURJM5JRLtwsAsvY9QzRR4P2XThdWbBj7wdh1DVp1 glfSi0viyhq7rqr1wlZvpr6sIROzDlE+dx1swpGvXyNPKIraubc5vgNQXDRD/C5bQbsJ1x+bp onEqmoAwUMvsq5DxSD8QVgBx1z9EU+8OZq1ehuBDAb1v6Ec7VIfdTKnLaeu8eeNNkdQ0ZuV8T Uiy+D5w/T4a+kJxbTe7Svw58PIM+GnxzUICtE8i5lYAVcbnGbSXyER3A6yFfNiRrGvVagr4Zk zMISAAmJjkT0k8SimJMRFTyUt9d6xu1kHT19k1RGd/Oy7uukMBvR8bWFlVb6pMY3Z9C/MfL79 44oLnInJZIk5+6ze8Pslb0+LIMrj6nd4ukjJkn9x+d/g4C5QcZ14emv9ZuFpgfGa0tAieIK
Archived-At: <>
Subject: Re: [icnrg] Last Call: draft-irtf-icnrg-icnlowpan
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Information-Centric Networking research group discussion list <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Tue, 11 Feb 2020 10:54:22 -0000


Thanks for the comments!

> Drafts to be published as RFCs in the IRTF stream need to include 
> various notices, as described in RFC 5743 Section 2.1. Some of those 
> notices look to be missing from this draft and will need to be added 
> before it can be published.

Yes, good point — that should be added.

> It’s also important for a draft to be published as an Experimental 
> RFC to be clear about what experiment being performed. Section 10 of 
> the draft includes a brief implementation report, describing 
> experiments that have been conducted using this protocol, which is 
> good, but the draft says very little about what experiments remain to 
> be done and what can be learnt from further experimental deployment of 
> this protocol. Would it be possible to add some additional context 
> about how this fits with ongoing experiments in this space?

So, that may actually be a good general advice for publishing 
Experimental RFCs in the IRTF. Normally, we would say that a 
specification (like this one) would hopefully lead to additional 
implementations, so that there would be interop tests and potentially 
tests in larger networks (scalability, performance etc.).

In the IRTF, we might be able to do a little better and provide some 
guidance as to what might be interesting experiments to do, what are 
things that we need to understand better etc.

How do the authors feel about adding something in this direction?

Regarding next steps, we (chairs) suggest that the authors produce a 
revision reflecting those comments. Since these are relatively minor, we 
don’t need another last call (unless the authors prefer that), so that 
we would then move to IRSG review.


> Regards,
> Colin
>> On 22 Jan 2020, at 08:42, Dirk Kutscher <> wrote:
>> Hello ICNRG,
>> This is a last call for comments on draft-irtf-icnrg-icnlowpan (ICN 
>> Adaptation to LowPAN Networks (ICN LoWPAN)).
>> We want to publish this as an Experimental RFC. Please read it and 
>> let us know if you think there are issues. The last call ends on 
>> February 7th, i.e., 2.5 weeks from today.
>> Abstract
>>   This document defines a convergence layer for CCNx and NDN over 
>>   802.15.4 LoWPAN networks.  A new frame format is specified to adapt
>>   CCNx and NDN packets to the small MTU size of IEEE 802.15.4.  For
>>   that, syntactic and semantic changes to the TLV-based header 
>> formats
>>   are described.  To support compatibility with other LoWPAN
>>   technologies that may coexist on a wireless medium, the dispatching
>>   scheme provided by 6LoWPAN is extended to include new dispatch 
>> types
>>   for CCNx and NDN.  Additionally, the link fragmentation component 
>> of
>>   the 6LoWPAN dispatching framework is applied to ICN chunks.  In its
>>   second part, the document defines stateless and stateful 
>> compression
>>   schemes to improve efficiency on constrained links.  Stateless
>>   compression reduces TLV expressions to static header fields for
>>   common use cases.  Stateful compression schemes elide state local 
>> to
>>   the LoWPAN and replace names in data packets by short local
>>   identifiers.
>> Best regards,
>> Dirk on behalf of ICNRG chairs
>> _______________________________________________
>> icnrg mailing list
> -- 
> Colin Perkins
> _______________________________________________
> icnrg mailing list