Re: [6lowpan] Titles of 6LoWPAN RFCs

Alexandru Petrescu <> Fri, 01 July 2011 16:20 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 6E97F1F0C79 for <>; Fri, 1 Jul 2011 09:20:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -3.249
X-Spam-Status: No, score=-3.249 tagged_above=-999 required=5 tests=[AWL=1.000, BAYES_00=-2.599, GB_I_LETTER=-2, HELO_EQ_FR=0.35]
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id 3Ea-1Nn-FmoR for <>; Fri, 1 Jul 2011 09:20:28 -0700 (PDT)
Received: from ( []) by (Postfix) with ESMTP id 5DFC31F0C58 for <>; Fri, 1 Jul 2011 09:20:28 -0700 (PDT)
Received: from ( []) by (8.14.2/8.14.2/CEAnet-Internet-out-2.2) with ESMTP id p61GKRbJ025875 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for <>; Fri, 1 Jul 2011 18:20:27 +0200
Received: from ( []) by (8.14.4/8.14.4) with ESMTP id p61GKQ31013202 for <>; Fri, 1 Jul 2011 18:20:27 +0200 (envelope-from
Received: from [] ( []) by (8.13.8/8.13.8/CEAnet-Intranet-out-1.1) with ESMTP id p61GKQLu022056 for <>; Fri, 1 Jul 2011 18:20:26 +0200
Message-ID: <>
Date: Fri, 01 Jul 2011 18:20:26 +0200
From: Alexandru Petrescu <>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; fr; rv: Gecko/20110616 Thunderbird/3.1.11
MIME-Version: 1.0
References: <>
In-Reply-To: <>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
Subject: Re: [6lowpan] Titles of 6LoWPAN RFCs
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Working group discussion for IPv6 over LowPan networks <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Fri, 01 Jul 2011 16:20:29 -0000

Le 29/06/2011 13:20, Carsten Bormann a écrit :
> While completing the RFC editor work for 6LoWPAN-HC, the issue of
> supplying correct and useful titles for our RFCs came up again.
> You may recall that we went through a little bit of discussion already
> for 6LoWPAN-ND, which has the same problem.
> The exposition of the problem takes a couple of paragraphs, so bear
> with me, please.
> Superficially, one part of the problem is that the marker that people
> are using to find our work, 6LoWPAN, was built out of the WPAN
> abbreviation invented by IEEE.
> One issue with that is that, strictly speaking, 6LoWPAN would require
> a double expansion in an RFC title as in
> 6LoWPAN (IPv6 over Low Power WPAN (Wireless Personal Area Networks))
> WPAN also is a bad short-term politically motivated term -- it was
> needed in IEEE to get the 802.15.4 radio accepted under 802.15.
> WPAN ("Wireless Personal Area Networks") is highly misleading, as
> there is nothing at all "Personal Area" about 802.15.4 WPANs.
> The deciding characteristic is the low-power, limited-range design
> (which, as a consequence, also causes the additional characteristic of
> lossiness that ROLL has chosen for its "Low-Power/Lossy" moniker).
> Still, the misleading four letters WPAN are part of the now well-known
> "6LoWPAN" acronym, and we may need to use this acronym to make sure
> the document is perceived in the right scope.
> In the recent history of 6LoWPAN-HC being fixed up to address WGLC
> comments, there was a silent title change.
> HC-13 used the title: (September 27, 2010)
>         Compression Format for IPv6 Datagrams in 6LoWPAN Networks
> HC-14 changed this to: (February 14, 2011)
>          Compression Format for IPv6 Datagrams in Low Power and
>                         Lossy Networks (6LoWPAN)
> This borrows ROLL's term "Low-Power and Lossy Networks", which may
> seem natural to the authors, who have done a lot of work in ROLL.
> Note that the ROLL WG has a wider scope than the 6LoWPAN WG (it is at
> layer three, connecting different link layer technologies), so it may
> be useful to retain a distinction between 6LoWPANs and LLNs.
> Specifically, 6LoWPAN-HC as defined has a lot of dependencies on
> RFC 4944 and IEEE 802.15.4, so using it as-is in generic "LLNs" would
> be inappropriate.  (It sure can be adapted for many non-6LoWPAN LLNs,
> but that would be a separate draft.)
> 6LoWPAN-ND has a similar problem.  Indeed, some of the concepts of
> 6LoWPAN-ND may be applicable to a lot of networks that benefit from
> relying less on multicast.  In an attempt to widen the scope, there
> was a title change when we rebooted the ND work to simplify it:
> ND-08: (February 1, 2010)
>                         6LoWPAN Neighbor Discovery
> ND-09: (April 27, 2010)
>      Neighbor Discovery Optimization for Low-power and Lossy Networks
> However, the document as it passed WGLC still is focused on 6LoWPANs
> (e.g., it contains specific support for 6COs).
> For both HC and ND, I don't think we properly discussed the attempted
> title changes in the WG.
> So what are the specific issues to be decided?
> I see at least:
> -- Should we drop the 6LoWPAN marker from our documents?
>     (Note that RFC 4944 doesn't have it, but in the 4 years since, the
>     term has gained some recognition.)
>     Should there be another common marker?
>     -- E.g., should we change over the whole documents (HC, ND) to LLN?
>     -- Should we just refer to IEEE 802.15.4 in the title (no 6LoWPAN)?
>        HC = Compression Format for IPv6 Datagrams over IEEE 802.15.4 Networks
>        ND = Neighbor Discovery Optimization for IEEE 802.15.4 Networks
>     -- Or should we stick with 6LoWPAN in both title and body?
> -- If the latter, what is an appropriate expansion of 6LoWPAN?
>     Can we get rid of the "Personal" in the expansion?
>     -- IPv6 over Low power Wireless Personal Area Networks [RFC4944]
>     -- IPv6-based Low power Wireless Personal Area Networks [RFC4944]
>     -- IPv6 over Low-Power Wireless Area Networks
>     -- IPv6-based Low-power WPANs
>     -- Other ideas?
> -- Whatever we decide about the above:
>     What is the relationship between the well-known term 6LoWPAN and
>     ROLL LLNs?
> Since 6LoWPAN-HC is waiting in the RFC editor queue, blocked for just
> this title issue, I'd like to resolve these questions quickly.
> Please provide your reasoned opinion to this mailing list by July 1.

My reasoned opinion is that there may be something fundamentally wrong 
in inventing the 6lowpan name as if IPv6 for lowpan is some different IPv6.

In various contexts I hear "in this network we don't run IPv6 and we run 

IPv6-over-802.15.4 is IPv6-over-foo if you wish.  In this sense it needs 
an MTU req, an identifier mapping for address configuration (uni- and 

IPv6-over-lowpan depends on what lowpan is, and lowpan is not defined 
anywhere.  It is a term invented by 6lowpan to mean something it thinks 
others mean when they don't actually.


> Gruesse, Carsten
> _______________________________________________
> 6lowpan mailing list