Re: [icnrg] I-D Action: draft-irtf-icnrg-icnlowpan-05.txt

Cenk Gündoğan <> Thu, 19 September 2019 17:32 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 28BEF12006A for <>; Thu, 19 Sep 2019 10:32:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.698
X-Spam-Status: No, score=-1.698 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, FROM_EXCESS_BASE64=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: (amavisd-new); dkim=fail (2048-bit key) reason="fail (bad RSA signature)"
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id 0qw3kZucjNZd for <>; Thu, 19 Sep 2019 10:32:46 -0700 (PDT)
Received: from mail.localdomain ( []) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 8ECF9120059 for <>; Thu, 19 Sep 2019 10:32:46 -0700 (PDT)
Received: from localhost (unknown []) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) (No client certificate requested) by mail.localdomain (Postfix) with ESMTPSA id 0F42524169 for <>; Thu, 19 Sep 2019 19:30:17 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple;; s=201712; t=1568914217; bh=SNlaGBSi+IpGQ8jxbFiXpR3YSSL76TH6+X1h5g71fPM=; h=References:From:To:Subject:In-reply-to:Date:From; b=ZJCLkhghJ1wBAmHaQeYl4QHrQptJv5kdC49AXf3SWpD0uXsFMTNed+w79HUjRbg9w mnQZWIQc9dAs3BSUj225wKUXkCIWc28uF/ch5xNpzz7/q3155HGnE8A/1h5y6SWdwr ayGMZoGMwSuSR7TCqVAqO/t/sWLQ4z5iKha8e47ph8Z6vm4MOfbSZi57N6w/xKhWQv NZpc4z2UZueVE9C4B8iHGfduVwPAGh0ylV94WAp2Z738tVoRrEAJYXSB6qlJSgzRt0 UWmQB4yiDpCsBA1xiqotoXveKO9Zzv0IielOWe30QDCvM+IfrM5aahxL3oqb1qDbEy jc6ThKSQH7Bsw==
References: <>
User-agent: mu4e 1.2.0; emacs 26.3
From: Cenk =?utf-8?B?R8O8bmRvxJ9hbg==?= <>
In-reply-to: <>
Date: Thu, 19 Sep 2019 19:32:43 +0200
Message-ID: <>
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="===-=-="; micalg=pgp-sha256; protocol="application/pgp-signature"
Archived-At: <>
Subject: Re: [icnrg] I-D Action: draft-irtf-icnrg-icnlowpan-05.txt
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: Thu, 19 Sep 2019 17:32:48 -0000


this update adds an extensibility mechanism to the ICNLoWPAN dispatch
format. This allows future I-Ds to extend the compression rule set
and to react to changes in the CCNx and NDN packet format.

Further, I want to bring our last discussion on the name compression
topic into focus (former mail is attached). The very essence of this
discussion is:

* the current default name compression strategy in ICNLoWPAN is
  restrictive, but effective, if ((only generic-typed name components
  are used) && (all component lengths <= 15 octets)). Also note that
  this stateless compression is invoked hop-wise and mostly for
  Interests only, since returning name prefixes for Data messages are
  elided by the stateful compression and added by ICNLoWPAN before
  passing the Data packet to the CCNx/NDN network stack.

* do we want to keep the simple name compression (above) as default
  and work on more elaborate compression schemes (including
  static/dynamic dictionary-based approaches, e.g.) as part of future
  I-Ds? The new extensibility mechanism (in the last update) surely
  opens the door to future I-Ds that solely focus on the name
  compression and which simply integrate into ICNLoWPAN.

We will bring up this discussion again during the interim meeting in
Macau and a lively discussion on site or on the list is greatly
appreciated (:


--- Begin Message ---

in the last ICNRG meeting (Montreal), Thomas presented the current state
of the ICNLoWPAN [1] document. The conclusion of discussions during the
talk was to investigate whether a name compression scheme with relaxed
restrictions than the predefined one might be better suited. An idea
formed to support names with varying (but most frequently used) name
component types. For CCNx, these seem to be T_NAMESEGMENT, T_IPID, and
MAY include T_CHUNK [2] and T_VERSION [3]. For NDN, these seem to
include GenericNameComponent, TimestampNameComponent,
VersionNameComponent and SequenceNumberNameComponent [4]. Both lists are
by no means complete, as for both protocols new (frequently used) name
component types can still emerge.

As a reminder .. the currently defined name compression scheme as per
[1] has the following restrictions:

1) all name component types are elided and GenericNameComponent (NDN) /
T_NAMESEGMENT (CCNx) are assumed for all components. No other name
component types are expected.

2) name component lengths are restricted to 15 octets max, in order to
fit the length of two consecutive components into 1 octet.

Our initial motivation was to have a scheme that removes most of the TLV
overhead and our assumption was that IoT deployments usually use
machine-to-machine communications (which MAY carry less semantics in the

To proceed with this discussion and to promote the progression of the
ICNLoWPAN document, we would like to propose the following:

In light of the flexibility and extensibility of CCNx / NDN, we would
also make the "compression octets" of ICNLoWPAN extensible. An example:
we would assign a bit in Figure 13+16 of [1] (respectively for CCNx) to
indicate a second, following octet to be part of the compression
algorithm. In this following octet, we can then allocate a number of
bits to (i) select a name compression algorithm (deviating from the
default) and (ii) define necessary compression parameters. Specific
definitions for (i) and (ii), and possible other things also, could then
be handled by future I-D documents as the need arises from new features
added to CCNx and NDN.

The questions I intend to provoke are:

(i) is the group O.K. with making ICNLoWPAN dispatches extensible?

(ii) should we think of a more elaborate name compression scheme as
default behaviour for ICNLoWPAN, or would the group be O.K. with keeping
the currently defined (highly restrictive, but very low-overhead) name
compression scheme provided in [1]? Other name compression algorithms
(e.g., static/dynamic dictionary-based approaches with proper dictionary
(re-)distribution; I believe Marc has some ideas on this) can then be
added to the ICNLoWPAN extension octet via new I-Ds once mature ideas



Cenk Gündoğan

Hamburg University of Applied Sciences
Dept. of Computer Science / Internet Technologies Group
Berliner Tor 7, 20099 Hamburg, Germany
Fon: +49 40 42875 - 8426
--- End Message ---
Cenk Gündoğan

Hamburg University of Applied Sciences
Dept. of Computer Science / Internet Technologies Group
Berliner Tor 7, 20099 Hamburg, Germany
Fon: +49 40 42875 - 8426

On Thu, Sep 19 2019 at 19:27 +0200, wrote:

> A New Internet-Draft is available from the on-line Internet-Drafts directories.
> This draft is a work item of the Information-Centric Networking RG of the IRTF.
>         Title           : ICN Adaptation to LowPAN Networks (ICN LoWPAN)
>         Authors         : Cenk Gundogan
>                           Thomas C. Schmidt
>                           Matthias Waehlisch
>                           Christopher Scherb
>                           Claudio Marxer
>                           Christian Tschudin
> 	Filename        : draft-irtf-icnrg-icnlowpan-05.txt
> 	Pages           : 47
> 	Date            : 2019-09-19
> Abstract:
>    This document defines a convergence layer for CCNx and NDN over IEEE
>    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.
> The IETF datatracker status page for this draft is:
> There are also htmlized versions available at:
> A diff from the previous version is available at:
> Please note that it may take a couple of minutes from the time of submission
> until the htmlized version and diff are available at
> Internet-Drafts are also available by anonymous FTP at:
> _______________________________________________
> icnrg mailing list