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

"Bernie Volz (volz)" <volz@cisco.com> Fri, 06 December 2013 21:00 UTC

Return-Path: <volz@cisco.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 6085B1AE0D8 for <dhcwg@ietfa.amsl.com>; Fri, 6 Dec 2013 13:00:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.502
X-Spam-Level:
X-Spam-Status: No, score=-9.502 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] 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 ZYPYcJJlkSBl for <dhcwg@ietfa.amsl.com>; Fri, 6 Dec 2013 13:00:09 -0800 (PST)
Received: from alln-iport-1.cisco.com (alln-iport-1.cisco.com [173.37.142.88]) by ietfa.amsl.com (Postfix) with ESMTP id 953461AE08E for <dhcwg@ietf.org>; Fri, 6 Dec 2013 13:00:09 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2620; q=dns/txt; s=iport; t=1386363606; x=1387573206; h=from:to:subject:date:message-id:references:in-reply-to: content-transfer-encoding:mime-version; bh=xg1SERrOV/bmG87aYib5Hm1rpTV9ExdGapx2UvjkrKM=; b=a0MDBA79+BDAwYYdHoLLEKF02e7fYcQfmbFN7zfKaQll7OoWNncRUXbH 28NoUXA1MLwneRtjmggdX5ek9vaA+0xpeU+6xCy+uyy1ujqkHcKsH6rVe 1/TfkwxA8hVhPvvGSnHhnv1of4UTfwwD+wWdpAm2qUjNNPOtMLPIrTWgm 4=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgUFAKc5olKtJV2d/2dsb2JhbABZgwc4U7kIgSMWdIIlAQEBBAEBATc0FwQCAQgRBAEBAQoUCQcnCxQJCAEBBAESCId6DcBwEwSOXzgGgxqBEwOqJ4FrgT6CKg
X-IronPort-AV: E=Sophos;i="4.93,842,1378857600"; d="scan'208";a="4935835"
Received: from rcdn-core-6.cisco.com ([173.37.93.157]) by alln-iport-1.cisco.com with ESMTP; 06 Dec 2013 21:00:05 +0000
Received: from xhc-rcd-x14.cisco.com (xhc-rcd-x14.cisco.com [173.37.183.88]) by rcdn-core-6.cisco.com (8.14.5/8.14.5) with ESMTP id rB6L05w4009904 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Fri, 6 Dec 2013 21:00:05 GMT
Received: from xmb-rcd-x04.cisco.com ([169.254.8.232]) by xhc-rcd-x14.cisco.com ([173.37.183.88]) with mapi id 14.03.0123.003; Fri, 6 Dec 2013 15:00:04 -0600
From: "Bernie Volz (volz)" <volz@cisco.com>
To: Tom Taylor <tom.taylor.stds@gmail.com>, "dhcwg@ietf.org" <dhcwg@ietf.org>
Thread-Topic: [dhcwg] WGLC for draft-ietf-dhc-dhcpv4-over-dhcpv6-03 - Respond by Dec 9, 2013
Thread-Index: Ac7ywFiOXFinITfhQ4SAN2eVQP2gUwANpwMAAAxFV6A=
Date: Fri, 6 Dec 2013 21:00:04 +0000
Message-ID: <489D13FBFA9B3E41812EA89F188F018E1ADD6721@xmb-rcd-x04.cisco.com>
References: <489D13FBFA9B3E41812EA89F188F018E1ADD660D@xmb-rcd-x04.cisco.com> <52A2385C.7020706@gmail.com>
In-Reply-To: <52A2385C.7020706@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.86.244.216]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
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: Fri, 06 Dec 2013 21:00:13 -0000

No. That is not the case. The 4o6 DHCP client doesn't start communicating until it has received the option(s) from the DHCPv6 server and then it knows whether it got a list of servers to send to or whether it should use the default multicast address. Read the paragraph previous to the one in question.

- Bernie

-----Original Message-----
From: dhcwg [mailto:dhcwg-bounces@ietf.org] On Behalf Of Tom Taylor
Sent: Friday, December 06, 2013 3:50 PM
To: Bernie Volz (volz); dhcwg@ietf.org
Subject: Re: [dhcwg] WGLC for draft-ietf-dhc-dhcpv4-over-dhcpv6-03 - Respond by Dec 9, 2013

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
>
...
_______________________________________________
dhcwg mailing list
dhcwg@ietf.org
https://www.ietf.org/mailman/listinfo/dhcwg