Re: [dhcwg] WGLC for draft-ietf-dhc-dhcpv4-over-dhcpv6-03 - Respond by Dec 9, 2013

<ian.farrer@telekom.de> Wed, 27 November 2013 09:50 UTC

Return-Path: <ian.farrer@telekom.de>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 30E811ADFF4 for <dhcwg@ietfa.amsl.com>; Wed, 27 Nov 2013 01:50:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.25
X-Spam-Level:
X-Spam-Status: No, score=-2.25 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_DE=0.35, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pJZMvpLWD24l for <dhcwg@ietfa.amsl.com>; Wed, 27 Nov 2013 01:50:08 -0800 (PST)
Received: from tcmail93.telekom.de (tcmail93.telekom.de [80.149.113.205]) by ietfa.amsl.com (Postfix) with ESMTP id CC6AF1ADF95 for <dhcwg@ietf.org>; Wed, 27 Nov 2013 01:50:07 -0800 (PST)
Received: from he113657.emea1.cds.t-internal.com ([10.134.99.17]) by tcmail91.telekom.de with ESMTP/TLS/AES128-SHA; 27 Nov 2013 10:50:06 +0100
Received: from HE111643.EMEA1.CDS.T-INTERNAL.COM ([10.134.93.12]) by HE113657.emea1.cds.t-internal.com ([::1]) with mapi; Wed, 27 Nov 2013 10:50:05 +0100
From: <ian.farrer@telekom.de>
To: <volz@cisco.com>, <dhcwg@ietf.org>
Date: Wed, 27 Nov 2013 10:50:07 +0100
Thread-Topic: [dhcwg] WGLC for draft-ietf-dhc-dhcpv4-over-dhcpv6-03 - Respond by Dec 9, 2013
Thread-Index: Ac7rVgvL8ofAQmQsTsS60U2WXbOfAQ==
Message-ID: <CEBB74DD.9C090%ian.farrer@telekom.de>
In-Reply-To: <489D13FBFA9B3E41812EA89F188F018E1ADA99A8@xmb-rcd-x04.cisco.com>
Accept-Language: en-US, de-DE
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/14.3.8.130913
acceptlanguage: en-US, de-DE
Content-Type: multipart/alternative; boundary="_000_CEBB74DD9C090ianfarrertelekomde_"
MIME-Version: 1.0
Subject: Re: [dhcwg] WGLC for draft-ietf-dhc-dhcpv4-over-dhcpv6-03 - Respond by Dec 9, 2013
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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: Wed, 27 Nov 2013 09:50:14 -0000

Hi,

A couple of comments on the current version of the draft:

Section 8, the sentence beginning ‘The client that intends…’ should read ‘A client that intends….'

Section 8  - Question regarding the sentence ‘The 4o6 DHCP client MUST NOT request the DHCPv4-over-DHCPv6 Enable Option nor the 4o6 Server Address Option in the Boot-request-v6 message’. I think that this text as written is ambiguous.

Is it meant to mean that the boot-request-v6-message can contain any DHCPv6 option with the exception of the 4o6 enable and 4o6 server options? Saying that the client may not request certainly implies that the client could include an ORO option alongside OPTION_BOOTP_MSG. Is the intention to allow this?

If not, why exclude requesting the 4o6 server option? Obviously, it’s pointless allowing the Enable option, but sending the 4o6 server option within the BOOTREPLYV6 to allow a dedicated DHCP4o6 server to tell the client to use unicast seems like it could be a good idea. What’s the reason for specifically excluding it?

There’s also a few other places in the text that need to be aligned with this (the ‘options’ description in Sec 5.2 and paragraph 8 of section 8).

Thanks,
Ian


From: "Bernie Volz (volz)" <volz@cisco.com<mailto:volz@cisco.com>>
Date: Sunday, 24 November 2013 23:02
To: "dhcwg@ietf.org<mailto:dhcwg@ietf.org>" <dhcwg@ietf.org<mailto:dhcwg@ietf.org>>
Subject: [dhcwg] WGLC for draft-ietf-dhc-dhcpv4-over-dhcpv6-03 - Respond by Dec 9, 2013


Folks, the authors of draft-ietf-dhc-dhcpv4-over-dhcpv6-03 (http://tools.ietf.org/html/draft-ietf-dhc-dhcpv4-over-dhcpv6-03.txt) believe it is ready for working group last call. Please review this draft and indicate whether or not you feel it is ready to be published. Your input is important! Please respond by Dec 9th, 2013.



At the time of this writing, there is no IPR reported against this draft.



Bernie will be the document shepherd.



Thanks,


-          Tomek & Bernie