Re: [6lowpan] Working Group Last call for draft-ietf-6lowpan-nd-15

"Dijk, Esko" <esko.dijk@philips.com> Wed, 02 March 2011 17:00 UTC

Return-Path: <esko.dijk@philips.com>
X-Original-To: 6lowpan@core3.amsl.com
Delivered-To: 6lowpan@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 286A53A681E for <6lowpan@core3.amsl.com>; Wed, 2 Mar 2011 09:00:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level:
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 838gr-gDJ4FS for <6lowpan@core3.amsl.com>; Wed, 2 Mar 2011 09:00:50 -0800 (PST)
Received: from DB3EHSOBE002.bigfish.com (db3ehsobe002.messaging.microsoft.com [213.199.154.140]) by core3.amsl.com (Postfix) with ESMTP id 9C5AB3A6774 for <6lowpan@ietf.org>; Wed, 2 Mar 2011 09:00:49 -0800 (PST)
Received: from mail59-db3-R.bigfish.com (10.3.81.242) by DB3EHSOBE002.bigfish.com (10.3.84.22) with Microsoft SMTP Server id 14.1.225.8; Wed, 2 Mar 2011 17:01:55 +0000
Received: from mail59-db3 (localhost.localdomain [127.0.0.1]) by mail59-db3-R.bigfish.com (Postfix) with ESMTP id 3F13A6F8471; Wed, 2 Mar 2011 17:01:55 +0000 (UTC)
X-SpamScore: -42
X-BigFish: VPS-42(zz15d6O9251J936eK542N217bLzz1202hzz8275bh8275dh1033ILz2dh2a8h668h61h)
X-Spam-TCS-SCL: 0:0
X-Forefront-Antispam-Report: KIP:(null); UIP:(null); IPVD:NLI; H:smtpx.philips.com; RD:smtpx.philips.com; EFVD:NLI
Received: from mail59-db3 (localhost.localdomain [127.0.0.1]) by mail59-db3 (MessageSwitch) id 1299085314756652_22095; Wed, 2 Mar 2011 17:01:54 +0000 (UTC)
Received: from DB3EHSMHS003.bigfish.com (unknown [10.3.81.245]) by mail59-db3.bigfish.com (Postfix) with ESMTP id AB64031004F; Wed, 2 Mar 2011 17:01:54 +0000 (UTC)
Received: from smtpx.philips.com (168.87.56.20) by DB3EHSMHS003.bigfish.com (10.3.87.103) with Microsoft SMTP Server (TLS) id 14.1.225.8; Wed, 2 Mar 2011 17:01:50 +0000
Received: from NLHILEXH01.connect1.local (172.16.153.76) by connect1.philips.com (172.16.156.40) with Microsoft SMTP Server (TLS) id 8.3.106.1; Wed, 2 Mar 2011 18:01:44 +0100
Received: from NLCLUEXM03.connect1.local ([172.16.157.42]) by NLHILEXH01.connect1.local ([172.16.153.76]) with mapi; Wed, 2 Mar 2011 18:01:49 +0100
From: "Dijk, Esko" <esko.dijk@philips.com>
To: Carsten Bormann <cabo@tzi.org>, 6lowpan <6lowpan@ietf.org>
Date: Wed, 02 Mar 2011 18:01:44 +0100
Thread-Topic: [6lowpan] Working Group Last call for draft-ietf-6lowpan-nd-15
Thread-Index: AcvOu2QD3bGAAnkXSUmoWlkG22GPqAKPw1+A
Message-ID: <A337AA36B3B96E4D853E6182B2F27AE2C72952CFA8@NLCLUEXM03.connect1.local>
References: <79D3D27D-F813-4773-8289-F973AB01F743@tzi.org>
In-Reply-To: <79D3D27D-F813-4773-8289-F973AB01F743@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
Subject: Re: [6lowpan] Working Group Last call for draft-ietf-6lowpan-nd-15
X-BeenThere: 6lowpan@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Working group discussion for IPv6 over LowPan networks <6lowpan.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Wed, 02 Mar 2011 17:00:51 -0000

Dear authors, all,

Here are my comments/questions regarding the 6lowpan-nd-15 draft. In general the document looks in good shape.

1)  Parts on multicast may benefit from some more clarification:
section 5.1 "A host would never multicast" -> is this "A host MUST NOT multicast" or SHOULD NOT ?

section 5.6 "Multicast addresses are considered to be on-link and are resolved as specified in [RFC4944] or the appropriate IP-over-foo document."
However section 5.7 says "As all prefixes but the link-local prefix are always assumed to be off-link, multicast-based address resolution between neighbors is not needed",  implying the contrary that multicast addresses are always off-link. Does this conflict?
Also, section 5.6 appears to refer to RFC 4944 Section 9, which is only applicable for mesh-under configurations. What about multicast in route-over configurations?  (Should it be made more explicit here?)

Finally, the text in 5.6  "All other prefixes are assumed to be off-link [RFC5889]" should perhaps be moved lower, so that it indicates the final case of this section. I.e. to first describe the special cases, then finally describe the "all other" case would be clearer I think.


2) Registration lifetime calculation:
 section 5.8.2. mentions "the maximum Registration lifetime is about 7 days".  Taking 65535 units of 60 seconds however, I find 45.5 days?


3)  Finally, some typos & minor remarks:

section 1.3 last paragraph: "involunterily"
"NCE" abbreviation is not defined on first use, also not used in RFC 4861, so should perhaps be defined here.

section 1.4 "messages in host-router interface and" -> "messages in host-router interfaces and" ?
"multhop" -> multihop

section 3.1 "mechanism using new Address" ->"mechanism using a new Address"

section 3.5 "As Routers send RAs to hosts, and when routers optionally receive RA messages or receive multicast NS messages from other Routers the result is Garbage-collectible NCEs."
-> Maybe more clear using:  "When Routers send RAs to hosts, and when routers optionally receive RA messages or receive multicast NS messages from other Routers, the result is Garbage-collectible NCEs."

section 4.1 "an SLLA option MUST be include" -> abbreviation "SLLA" is not defined on first use. Also not used in RFC 4861 main text, so could be defined here.

section 5.5 (last sent.) "use a router it is registered, it" -> "use a router it is registered to, it"

overall:  The text "section section" appears a few times.


best 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: Thursday 17 February 2011 16:58
To: 6lowpan
Subject: [6lowpan] Working Group Last call for draft-ietf-6lowpan-nd-15

In September/October, we had the first WGLC on 6LoWPAN-ND, which
resulted in a number of detailed comments and two resulting
fine-tuning iterations of the draft.

draft-ietf-6lowpan-nd-15.txt has been out for two months now.
I understand it has taken part in several interops with multiple
implementations in this period; no issues came up.

We now start the Working Group Last Call on:

   http://tools.ietf.org/html/draft-ietf-6lowpan-nd-15

The document is planned to be submitted by this Working Group to the
IESG for publication as a Standards-Track Document.

This is a two-week Working-Group Last-Call, ending on Thursday,
2011-03-03 at 2359 UTC.

Please review the changes to the document carefully once more, and
send your comments to the 6lowpan list.  Please also do indicate to
the list if you are all-OK with the document.

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.