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

Tom Taylor <tom.taylor.stds@gmail.com> Fri, 06 December 2013 20:49 UTC

Return-Path: <tom.taylor.stds@gmail.com>
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 46F411AE3E2 for <dhcwg@ietfa.amsl.com>; Fri, 6 Dec 2013 12:49:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-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 cva-06zb0pBM for <dhcwg@ietfa.amsl.com>; Fri, 6 Dec 2013 12:49:39 -0800 (PST)
Received: from mail-ie0-x22f.google.com (mail-ie0-x22f.google.com [IPv6:2607:f8b0:4001:c03::22f]) by ietfa.amsl.com (Postfix) with ESMTP id 81BC21AE3D4 for <dhcwg@ietf.org>; Fri, 6 Dec 2013 12:49:39 -0800 (PST)
Received: by mail-ie0-f175.google.com with SMTP id x13so2166851ief.6 for <dhcwg@ietf.org>; Fri, 06 Dec 2013 12:49:35 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=z48UUvJqNPVug0qBGUno2aqwNQ/gHasJLZDNDO5misA=; b=LWvt8aVOQuzzw5Enef2MKKpNjsYiEvYusNebd7l7FSR2x82HIYxHZmApeuszE+1EJT Vnoh4KPij9HQUhULF1N9GNa6sYmsf7qTwAhGIOenGbgxlnIcMZKuaJ6iFxYmkRDKU/kB 7wjCFQE1jvFSHmSswss/kS3TlCKzN7R5YnxKbgNMJ4OmaKk5W6r2cPZqu2iIQ0Bb42JQ Sufzi3x96NHB6VCQxaYPYzQ72BxvOjOVVBkImptRul9uNUOx3lSLymikutGoUCDO4x2h 5GQbHCGI8z1RxeToRI0h1UnzbOMs1x36fRLW/Sd4j6O7HJXtn+l2aQtZeGD/LeBObUqO +b/w==
X-Received: by 10.50.79.138 with SMTP id j10mr4729137igx.2.1386362975684; Fri, 06 Dec 2013 12:49:35 -0800 (PST)
Received: from [192.168.1.65] ([64.56.250.4]) by mx.google.com with ESMTPSA id k6sm5534596igx.8.2013.12.06.12.49.34 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 06 Dec 2013 12:49:35 -0800 (PST)
Message-ID: <52A2385C.7020706@gmail.com>
Date: Fri, 06 Dec 2013 15:49:32 -0500
From: Tom Taylor <tom.taylor.stds@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.1.1
MIME-Version: 1.0
To: "Bernie Volz (volz)" <volz@cisco.com>, "dhcwg@ietf.org" <dhcwg@ietf.org>
References: <489D13FBFA9B3E41812EA89F188F018E1ADD660D@xmb-rcd-x04.cisco.com>
In-Reply-To: <489D13FBFA9B3E41812EA89F188F018E1ADD660D@xmb-rcd-x04.cisco.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
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: Fri, 06 Dec 2013 20:49:41 -0000

I think "initially" is correct. When the client first comes up, it does 
not normally have a server unicast address. Even though the client and 
server have not yet agreed on 4o6 provisioning at that point, the client 
has reached the 4o6 server using multicast.

Tom

On 06/12/2013 3:20 PM, Bernie Volz (volz) wrote:
> Fixed the subject ...
>
> Yes, this is a good point. I am not sure initially is any better.
>
> Perhaps this should just be reworded to say that the client uses one
> of the two methods (multicast to All_DHCP_Relay_Agents_and_Servers)
> or to the list indicated in the option.
>
> - Bernie
>
> -----Original Message----- From: dhcwg
> [mailto:dhcwg-bounces@ietf.org] On Behalf Of Tom Taylor Sent: Friday,
> December 06, 2013 3:02 PM To: Bernie Volz (volz); dhcwg@ietf.org
> Subject: Re: [dhcwg] WGLC - draft-ietf-dhc-option-guidelines-12 -
> Respond by July 15
>
> I've just reviewed all the discussion of Server address and I think
> what I'm about to say is still relevant. This is just a trivial
> wording remark.
>
> The last paragraph of Section 4 says:
>
> Typically, a 4o6 DHCP client communicates with the 4o6 DHCP servers
> using well-known All_DHCP_Relay_Agents_and_Servers multicast
> address. Client SHOULD request the 4o6 Server Address Option from a
> DHCPv6 server and the server may be configured to respond to the
> client with one such option that contains one or more unicast
> addresses of the 4o6 DHCP Servers.  The server includes 4o6 Server
> Address Option in Advertise and Reply messages.  The format of the
> option is defined in Section 6.3.
>
> The word "typically" in the first sentence seems to clash with "[The]
> client SHOULD request ..." in the next sentence. Do you mean to say
> "initially" rather than "typically"?
>
> Tom Taylor
>
...