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 20:20 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 091EA1AE167 for <dhcwg@ietfa.amsl.com>; Fri, 6 Dec 2013 12:20:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.502
X-Spam-Level:
X-Spam-Status: No, score=-14.502 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, 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 kQoHiky5habf for <dhcwg@ietfa.amsl.com>; Fri, 6 Dec 2013 12:20:20 -0800 (PST)
Received: from rcdn-iport-2.cisco.com (rcdn-iport-2.cisco.com [173.37.86.73]) by ietfa.amsl.com (Postfix) with ESMTP id 7A2041AE107 for <dhcwg@ietf.org>; Fri, 6 Dec 2013 12:20:20 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2709; q=dns/txt; s=iport; t=1386361217; x=1387570817; h=from:to:subject:date:message-id: content-transfer-encoding:mime-version; bh=+q0y4UGONknRoX1ieXeQhgfgX+0BA68rpM6y1zTB/Ug=; b=BNMlz0roBsMf14xZwNqyaIc3wCXYOu0nE0qCmEf347LaFT7XYNBDwUxQ kEGMY+N0q8hRzts681yaAp5yKd8etaHD5omprrEKZZ3GHq3niz9k0gqLv pwLujAxfeVCKkFyGlvXEjL/37qhkMQZkVjrfZJw9IFN14TlVaKv5EORWt s=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgUFAHYwolKtJV2Y/2dsb2JhbABZgwc4U7kEgSMWdIIlAQEBBAEBARodNBcGAQgRBAEBAQoUCS4LFAkJAQQBEgiHeg3AcReOXQI+gxqBEwOZRJBjgWuBPoIq
X-IronPort-AV: E=Sophos;i="4.93,842,1378857600"; d="scan'208";a="289873665"
Received: from rcdn-core-1.cisco.com ([173.37.93.152]) by rcdn-iport-2.cisco.com with ESMTP; 06 Dec 2013 20:20:08 +0000
Received: from xhc-rcd-x10.cisco.com (xhc-rcd-x10.cisco.com [173.37.183.84]) by rcdn-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id rB6KK1Hl029420 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Fri, 6 Dec 2013 20:20:03 GMT
Received: from xmb-rcd-x04.cisco.com ([169.254.8.232]) by xhc-rcd-x10.cisco.com ([173.37.183.84]) with mapi id 14.03.0123.003; Fri, 6 Dec 2013 14:20:01 -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: Ac7ywFiOXFinITfhQ4SAN2eVQP2gUw==
Date: Fri, 6 Dec 2013 20:20:00 +0000
Message-ID: <489D13FBFA9B3E41812EA89F188F018E1ADD660D@xmb-rcd-x04.cisco.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 20:20:24 -0000

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

On 01/07/2013 5:44 PM, Bernie Volz (volz) wrote:
> The draft-ietf-dhc-option-guidelines-12,
> http://tools.ietf.org/html/draft-ietf-dhc-option-guidelines-12,
> addresses the comments from the previous (-11) last call. While 
> originally I expected to have a short (1 week) last call for the 
> updated document, I think it best to have the standard 2 weeks given 
> the time of year (and the Independence Day holiday in the US).
>
>
>
> Please review the draft and indicate whether or not you feel this 
> version is ready to be published. Your response matters to the 
> process, so please do respond.
>
>
>
> Do note: While I encourage full reviews, the main focus is to assure 
> we have consensus on the recent changes from the -11. The -11 WGLC 
> support will be taken into consideration.
>
>
>
> As Tomek is an author, I will evaluate consensus after July 15, 2013.
>
>
>
> -          Bernie
>
>
>
>
>
> _______________________________________________ dhcwg mailing list
> dhcwg@ietf.org https://www.ietf.org/mailman/listinfo/dhcwg
>
_______________________________________________
dhcwg mailing list
dhcwg@ietf.org
https://www.ietf.org/mailman/listinfo/dhcwg