Re: [6lowpan] Ready for WGLC? (Re: Latest version of IPv6 over BT-LE draft)

<> Thu, 22 September 2011 13:53 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 6056921F8C40 for <>; Thu, 22 Sep 2011 06:53:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.999
X-Spam-Status: No, score=-2.999 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, J_CHICKENPOX_52=0.6, RCVD_IN_DNSWL_LOW=-1]
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id NlzxUgprTitG for <>; Thu, 22 Sep 2011 06:53:19 -0700 (PDT)
Received: from ( []) by (Postfix) with ESMTP id 9E6D121F8C31 for <>; Thu, 22 Sep 2011 06:53:18 -0700 (PDT)
Received: from ( []) by (Switch-3.4.4/Switch-3.4.3) with ESMTP id p8MDtZBT032127; Thu, 22 Sep 2011 16:55:49 +0300
Received: from ([]) by over TLS secured channel with Microsoft SMTPSVC(6.0.3790.4675); Thu, 22 Sep 2011 16:55:32 +0300
Received: from ( by ( with Microsoft SMTP Server (TLS) id; Thu, 22 Sep 2011 15:53:13 +0200
Received: from ([]) by ([]) with mapi id 14.01.0339.002; Thu, 22 Sep 2011 15:53:13 +0200
From: <>
To: <>, <>, <>
Thread-Topic: [6lowpan] Ready for WGLC? (Re: Latest version of IPv6 over BT-LE draft)
Thread-Index: AQHMdtPRK6TlyPrgJ0Sk4OZWWwl9nZVZ1OEA
Date: Thu, 22 Sep 2011 13:53:12 +0000
Message-ID: <>
In-Reply-To: <A337AA36B3B96E4D853E6182B2F27AE2D1671A068A@NLCLUEXM03.connect1.local>
Accept-Language: en-US
Content-Language: en-US
x-originating-ip: []
Content-Type: text/plain; charset="us-ascii"
Content-ID: <>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginalArrivalTime: 22 Sep 2011 13:55:32.0755 (UTC) FILETIME=[4BB61630:01CC792F]
X-Nokia-AV: Clean
Subject: Re: [6lowpan] Ready for WGLC? (Re: Latest version of IPv6 over BT-LE draft)
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: Thu, 22 Sep 2011 13:53:23 -0000

DHCPv6 for 6LoWPAN network.

In the current version of I-D, there's one chapter (3.2.1) describing
"IPv6 Address Configuration", which mentioned "Stateless
autoconfiguration". Stateless autoconfiguration is defined in RFC4862,
which is different from "stateful autoconfiguration" (aka DHCPv6).

Compared with 6LoWPAN over BT-LE, draft-ietf-6lowpan-nd has defined the
mechanism to configure IPv6 addresses for 6LoWPAN over 802.15.4. In
draft-ietf-6lowpan-nd-17, there're several assumptions for 6lowpan-nd. It
says "All nodes in the network have an EUI-64 interface identifier in
order to do address auto-configuration and detect duplicate addresses."
Also, draft-ietf-6lowpan-nd introduces the Address Registration mechanism
and the optional DAD mechanism. DHCPv6 is not optimized for low-power and
lossy networks including 802.15.4 and BT-LE.

I think it is necessary to make the "IPv6 address configuration" for
6LoWPAN over BT-LE clear in the future revision.

Thank you!

Best Regards,
Minjun, Xi
Nokia Research Center

On 9/19/11 9:54 PM, "ext Dijk, Esko" <> wrote:

>Dear BT-LE authors, all,
>I haven't done a detailed review but I have one technical
>comment/question. The typical case in the I-D is a BT-LE mobile phone,
>connected to the internet, acting as a 6LBR and distributing an IP prefix
>to 6LNs. Is it the intention that an IP prefix for the 6LoWPAN can be
>obtained by the phone via DHCPv6 ?  If so would an ISP support this for a
>phone connected to their 3G network?
>Obtaining an IP prefix by the 6LBR seems necessary to enable routing from
>a host on the internet to a 6LN.
>Esko Dijk
>Philips Corporate Technologies, Research
>High Tech Campus 34, Eindhoven, The Netherlands
>-----Original Message-----
>From: [] On
>Behalf Of Carsten Bormann
>Sent: Friday 9 September 2011 14:43
>Subject: [6lowpan] Ready for WGLC? (Re: Latest version of IPv6 over BT-LE
>we are now looking at the third WG version (-02) of this draft.
>Are we ready to do a working-group last-call on this?
>-- if you see something major that needs to be done before this is ready,
>please speak up now.
>   (If you have technical comments, or maybe some editorial suggestions,
>these are also useful at this point, although there also will be time to
>comment in the actual WGLC.)
>-- conversely, if you have reviewed the document and like it, please do
>speak up (and please do say what you have specifically looked at).
>Of course, we don't want to go into a WGLC with glaring omissions (I
>gather Appendix A is not really a necessary part of this spec), and we
>also don't want to go into WGLC if the working group hasn't been able to
>review the document or, worse, if nobody actually cares.
>Please respond to this message by Sep 16.
>Gruesse, Carsten
>6lowpan mailing list
>The information contained in this message may be confidential and legally
>protected under applicable law. The message is intended solely for the
>addressee(s). If you are not the intended recipient, you are hereby
>notified that any use, forwarding, dissemination, or reproduction of this
>message is strictly prohibited and may be unlawful. If you are not the
>intended recipient, please contact the sender by return e-mail and
>destroy all copies of the original message.
>6lowpan mailing list