Re: [dhcwg] Last call on draft-ietf-dhc-dhcpv6-ldra-01

"MILES DAVID" <David.Miles@alcatel-lucent.com> Fri, 27 November 2009 05:40 UTC

Return-Path: <David.Miles@alcatel-lucent.com>
X-Original-To: dhcwg@core3.amsl.com
Delivered-To: dhcwg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 509513A6962 for <dhcwg@core3.amsl.com>; Thu, 26 Nov 2009 21:40:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.449
X-Spam-Level:
X-Spam-Status: No, score=-2.449 tagged_above=-999 required=5 tests=[AWL=-0.150, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3]
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 310sbqgXFeV8 for <dhcwg@core3.amsl.com>; Thu, 26 Nov 2009 21:40:53 -0800 (PST)
Received: from hoemail1.alcatel.com (hoemail1.alcatel.com [192.160.6.148]) by core3.amsl.com (Postfix) with ESMTP id C8DFD3A6959 for <dhcwg@ietf.org>; Thu, 26 Nov 2009 21:40:52 -0800 (PST)
Received: from horh1.usa.alcatel.com (h172-22-218-55.lucent.com [172.22.218.55]) by hoemail1.alcatel.com (8.13.8/IER-o) with ESMTP id nAR5ejbv018329; Thu, 26 Nov 2009 23:40:46 -0600 (CST)
Received: from mail.apac.alcatel-lucent.com (h202-65-2-130.alcatel.com [202.65.2.130]) by horh1.usa.alcatel.com (8.13.8/emsr) with ESMTP id nAR5ehQs020426; Thu, 26 Nov 2009 23:40:44 -0600 (CST)
Received: from sgsinsbhs01.ad4.ad.alcatel.com (sgsinsbhs01.ap.lucent.com [135.254.109.34]) by mail.apac.alcatel-lucent.com (8.13.7/8.13.7/Alcanet1.0) with ESMTP id nAR5cD2G027128; Fri, 27 Nov 2009 13:38:14 +0800
Received: from SGSINSMBS02.ad4.ad.alcatel.com ([135.254.109.29]) by sgsinsbhs01.ad4.ad.alcatel.com with Microsoft SMTPSVC(6.0.3790.3959); Fri, 27 Nov 2009 13:40:41 +0800
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Date: Fri, 27 Nov 2009 13:40:40 +0800
Message-ID: <986DCE2E44129444B6435ABE8C9E424D04656158@SGSINSMBS02.ad4.ad.alcatel.com>
In-Reply-To: <200911262237.XAA09429@TR-Sys.de>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [dhcwg] Last call on draft-ietf-dhc-dhcpv6-ldra-01
Thread-Index: Acpu6Sbp/+uBgZITTaiK5mvGzazGEgAOs5Ow
References: <200911262237.XAA09429@TR-Sys.de>
From: MILES DAVID <David.Miles@alcatel-lucent.com>
To: Alfred HÎnes <ah@TR-Sys.de>, dhcwg@ietf.org
X-OriginalArrivalTime: 27 Nov 2009 05:40:41.0328 (UTC) FILETIME=[27F3DF00:01CA6F24]
X-Scanned-By: MIMEDefang 2.57 on 172.22.12.27
X-Scanned-By: MIMEDefang 2.64 on 202.65.2.130
Subject: Re: [dhcwg] Last call on draft-ietf-dhc-dhcpv6-ldra-01
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 27 Nov 2009 05:40:54 -0000

Hi Alfred,

I must have missed the earlier comments regarding this as they are certainly appreciated (and should have been incorporated back then). I thought we got most of them last time (thanks for that review as well) so my apologies here.

I'll find the old posting and ensure the guidelines are followed.

Cheers,

-David

-----Original Message-----
From: dhcwg-bounces@ietf.org [mailto:dhcwg-bounces@ietf.org] On Behalf Of Alfred HÎnes
Sent: Friday, 27 November 2009 9:07 AM
To: dhcwg@ietf.org
Subject: Re: [dhcwg] Last call on draft-ietf-dhc-dhcpv6-ldra-01

Folks,
I also support this draft.

I have studied it again and found a bunch of additional editorial
nits that need to be addressed before publication, but simply don't
have the cycles available for a complete writeup this (+next) week.

The only detail IMHO important for clarity is adding precision in
the figures in sections 7.1 through 7.3 :
The arrow lines below the network diagrams should be extended to
precisely represent the span of the IPv6 links; since the LDRA
is operating at layer 2, no IPv6 link can terminate in an LDRA;
so all arrows should end below an interface of either a "Client",
"Relay*", or "Server" box (where 'interface' in the artwork means
the part of the graphical representation of the node that joins
the line representing the physical link).
I had mentioned this in an earlier review, including detailed
examples of how the artwork might better look like, but these
recommendations have not been followed so far.

Also, the [L2RA] ref. needs to be updated.

I'll try to compile the list of editorials soon, but that should
not hold off the draft now.


Kind regards,
  Alfred HÎnes.