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

"Dijk, Esko" <esko.dijk@philips.com> Mon, 19 September 2011 13:52 UTC

Return-Path: <esko.dijk@philips.com>
X-Original-To: 6lowpan@ietfa.amsl.com
Delivered-To: 6lowpan@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D48BE21F8BEE for <6lowpan@ietfa.amsl.com>; Mon, 19 Sep 2011 06:52:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.474
X-Spam-Level:
X-Spam-Status: No, score=-5.474 tagged_above=-999 required=5 tests=[AWL=1.125, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Mt40OWgar1ef for <6lowpan@ietfa.amsl.com>; Mon, 19 Sep 2011 06:52:19 -0700 (PDT)
Received: from TX2EHSOBE004.bigfish.com (tx2ehsobe002.messaging.microsoft.com [65.55.88.12]) by ietfa.amsl.com (Postfix) with ESMTP id 3536821F8BE8 for <6lowpan@ietf.org>; Mon, 19 Sep 2011 06:52:19 -0700 (PDT)
Received: from mail83-tx2-R.bigfish.com (10.9.14.241) by TX2EHSOBE004.bigfish.com (10.9.40.24) with Microsoft SMTP Server id 14.1.225.22; Mon, 19 Sep 2011 13:54:41 +0000
Received: from mail83-tx2 (localhost.localdomain [127.0.0.1]) by mail83-tx2-R.bigfish.com (Postfix) with ESMTP id D6C721140095; Mon, 19 Sep 2011 13:54:41 +0000 (UTC)
X-SpamScore: -38
X-BigFish: VPS-38(zz217bL15d6O9251J542Mzz1202hzz1033IL8275bh8275dhz2dh2a8h668h839h944h61h)
X-Spam-TCS-SCL: 0:0
X-Forefront-Antispam-Report: CIP:168.87.56.20; KIP:(null); UIP:(null); IPVD:NLI; H:smtpx.philips.com; RD:smtpx.philips.com; EFVD:NLI
Received: from mail83-tx2 (localhost.localdomain [127.0.0.1]) by mail83-tx2 (MessageSwitch) id 1316440480557220_23784; Mon, 19 Sep 2011 13:54:40 +0000 (UTC)
Received: from TX2EHSMHS045.bigfish.com (unknown [10.9.14.247]) by mail83-tx2.bigfish.com (Postfix) with ESMTP id 76885C40050; Mon, 19 Sep 2011 13:54:40 +0000 (UTC)
Received: from smtpx.philips.com (168.87.56.20) by TX2EHSMHS045.bigfish.com (10.9.99.145) with Microsoft SMTP Server (TLS) id 14.1.225.22; Mon, 19 Sep 2011 13:54:40 +0000
Received: from NLHILEXH04.connect1.local (172.16.153.45) by connect1.philips.com (172.16.156.152) with Microsoft SMTP Server (TLS) id 8.3.106.1; Mon, 19 Sep 2011 15:54:33 +0200
Received: from NLCLUEXM03.connect1.local ([172.16.157.42]) by NLHILEXH04.connect1.local ([172.16.153.45]) with mapi; Mon, 19 Sep 2011 15:50:53 +0200
From: "Dijk, Esko" <esko.dijk@philips.com>
To: "johanna.1.nieminen@nokia.com" <johanna.1.nieminen@nokia.com>, Carsten Bormann <cabo@tzi.org>
Date: Mon, 19 Sep 2011 15:54:32 +0200
Thread-Topic: [6lowpan] Ready for WGLC? (Re: Latest version of IPv6 over BT-LE draft)
Thread-Index: Acxu7ZD5yELfhJDQQB+hBYvRHzF+rgH42csQ
Message-ID: <A337AA36B3B96E4D853E6182B2F27AE2D1671A068A@NLCLUEXM03.connect1.local>
References: <5FA713B99ACAA6478C065A155E206B4608E013@008-AM1MPN1-043.mgdnok.nokia.com> <4AB4A5FC-C722-46C2-8BAD-133E742A2AC7@tzi.org>
In-Reply-To: <4AB4A5FC-C722-46C2-8BAD-133E742A2AC7@tzi.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: philips.com
Cc: "6lowpan@ietf.org" <6lowpan@ietf.org>
Subject: Re: [6lowpan] Ready for WGLC? (Re: Latest version of IPv6 over BT-LE draft)
X-BeenThere: 6lowpan@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Working group discussion for IPv6 over LowPan networks <6lowpan.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/6lowpan>, <mailto:6lowpan-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/6lowpan>
List-Post: <mailto:6lowpan@ietf.org>
List-Help: <mailto:6lowpan-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/6lowpan>, <mailto:6lowpan-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 19 Sep 2011 13:52:19 -0000

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.

regards,
Esko


Esko Dijk

Philips Corporate Technologies, Research
High Tech Campus 34, Eindhoven, The Netherlands
esko.dijk@philips.com




-----Original Message-----
From: 6lowpan-bounces@ietf.org [mailto:6lowpan-bounces@ietf.org] On Behalf Of Carsten Bormann
Sent: Friday 9 September 2011 14:43
To: 6lowpan@ietf.org
Subject: [6lowpan] Ready for WGLC? (Re: Latest version of IPv6 over BT-LE draft)

6LoWPANners,

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
6lowpan@ietf.org
https://www.ietf.org/mailman/listinfo/6lowpan

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.