Re: [dhcwg] WG Adoption Call - draft-wing-dhc-dns-reconfigure-02 - respond by Jan 27, 2014

"Bernie Volz (volz)" <volz@cisco.com> Mon, 13 January 2014 16:10 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 5E7F31AE19F for <dhcwg@ietfa.amsl.com>; Mon, 13 Jan 2014 08:10:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -15.039
X-Spam-Level:
X-Spam-Status: No, score=-15.039 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.538, 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 gaTwSf06tPg1 for <dhcwg@ietfa.amsl.com>; Mon, 13 Jan 2014 08:10:38 -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 4FB751AC4A7 for <dhcwg@ietf.org>; Mon, 13 Jan 2014 08:10:38 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=3096; q=dns/txt; s=iport; t=1389629427; x=1390839027; h=from:to:subject:date:message-id:references:in-reply-to: content-transfer-encoding:mime-version; bh=316wvL+3CPmlMoQjw8EicL23SdC1ix7GZHVzjfyNv7w=; b=QBuw0l8PWGOWvo/mgoaWGeOnTG1m1Mllamny1Ks7Bb8s0Em/Q+hE7eUc dAXyce1uMRelgSozNdhUljFAwtIwSx/6+BSvFeyndr92Ku9D+F6Pk/Vam aPBc/yLWcXS1LfBatxj/2fWbGRUVyUjbgrZ9E8hZCAaoTWn+sRBSselhy E=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AiMFAPUO1FKtJXG//2dsb2JhbABagws4VrlugRQWdIIlAQEBBAEBARoKRxcEAgEIEQQBAQsdBycLFAkIAQEEARIIh3wNxE4XjjYBAR44BoMegRMEiQuQPJBlgW+BPoFxOQ
X-IronPort-AV: E=Sophos;i="4.95,653,1384300800"; d="scan'208";a="296962219"
Received: from rcdn-core2-4.cisco.com ([173.37.113.191]) by rcdn-iport-2.cisco.com with ESMTP; 13 Jan 2014 16:10:27 +0000
Received: from xhc-rcd-x01.cisco.com (xhc-rcd-x01.cisco.com [173.37.183.75]) by rcdn-core2-4.cisco.com (8.14.5/8.14.5) with ESMTP id s0DGAREN014010 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Mon, 13 Jan 2014 16:10:27 GMT
Received: from xmb-rcd-x04.cisco.com ([169.254.8.37]) by xhc-rcd-x01.cisco.com ([173.37.183.75]) with mapi id 14.03.0123.003; Mon, 13 Jan 2014 10:10:27 -0600
From: "Bernie Volz (volz)" <volz@cisco.com>
To: Simon Perreault <simon.perreault@viagenie.ca>, "dhcwg@ietf.org" <dhcwg@ietf.org>
Thread-Topic: [dhcwg] WG Adoption Call - draft-wing-dhc-dns-reconfigure-02 - respond by Jan 27, 2014
Thread-Index: Ac8QcQDsRAhiIYjCTp6frUYpiNZ3DQANxxuAAAvHSGA=
Date: Mon, 13 Jan 2014 16:10:26 +0000
Message-ID: <489D13FBFA9B3E41812EA89F188F018E1AE1AE39@xmb-rcd-x04.cisco.com>
References: <489D13FBFA9B3E41812EA89F188F018E1AE1A630@xmb-rcd-x04.cisco.com> <52D408FD.9000509@viagenie.ca>
In-Reply-To: <52D408FD.9000509@viagenie.ca>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.86.240.189]
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [dhcwg] WG Adoption Call - draft-wing-dhc-dns-reconfigure-02 - respond by Jan 27, 2014
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: Mon, 13 Jan 2014 16:10:40 -0000

Hi:

Once adopted, we can request changes.

I too think it would be better to just provide information about the current state of a host's addresses rather than report transition states (transitions would trigger a Reconfigure-request). If there is a good reason for reporting state changes, perhaps both should be reported (i.e., flags and state change - or old vs new state)? That way the server can use either set to do its processing?

Also, as mentioned in the document, the option should be allowed to be sent by the host directly (though of course, it will be far quicker to get this rolled out if the relay agents are modified rather than all hosts).

- Bernie

-----Original Message-----
From: dhcwg [mailto:dhcwg-bounces@ietf.org] On Behalf Of Simon Perreault
Sent: Monday, January 13, 2014 10:41 AM
To: dhcwg@ietf.org
Subject: Re: [dhcwg] WG Adoption Call - draft-wing-dhc-dns-reconfigure-02 - respond by Jan 27, 2014

In favour. I commented on earlier revisions.

Comments for future revisions:

- First, I think it would be better protocol design to make OPTION_HOST_CONNECTIVITY contain a bit field, where IPv4 and IPv6 would be represented by bits that could be toggled independently. Other bits would be reserved for future use.

- Second, is it necessary for the relay to track and report *transitions*? Isn't it better to make the relay report the current state only, and let the DHCP server figure out the transition based on the previous state?

- Third, if we keep working with transitions, what is the initial state of a new host? If I plug in a host and it sends an RA, does it go from "no stack" to "IPv6-only"? Reporting the current state would deal with this easily, whereas reporting transitions would require a new set of messages I suppose.

Simon

Le 2014-01-13 10:12, Bernie Volz (volz) a écrit :
> Hi all:
>
> A call for adoption is being initiated at the request of the authors 
> to determine whether there is WG consensus to adopt
> draft-wing-dhc-dns-reconfigure-02 as a DHC WG item. Please state 
> whether or not you're in favor of the adoption by replying to this 
> mail. If you are not in favor, please also state your objections in your response.
> This adoption call will complete on January  27, 2014.
>
> The HTML version of the document can be viewed at 
> http://tools.ietf.org/html/draft-wing-dhc-dns-reconfigure-02.
>
> If there is consensus to adopt as a WG document, we will confirm with 
> Ted to get it on the charter.
>
> Regards,
>
> Tomek & Bernie
>
>
>
> _______________________________________________
> dhcwg mailing list
> dhcwg@ietf.org
> https://www.ietf.org/mailman/listinfo/dhcwg
>


--
DTN made easy, lean, and smart --> http://postellation.viagenie.ca
NAT64/DNS64 open-source        --> http://ecdysis.viagenie.ca
STUN/TURN server               --> http://numb.viagenie.ca
_______________________________________________
dhcwg mailing list
dhcwg@ietf.org
https://www.ietf.org/mailman/listinfo/dhcwg