Re: [dhcwg] I-D Action: draft-ietf-dhc-conn-status-00.txt

"Bernie Volz (volz)" <volz@cisco.com> Tue, 04 February 2014 17:23 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 9CE071A012A for <dhcwg@ietfa.amsl.com>; Tue, 4 Feb 2014 09:23:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -15.036
X-Spam-Level:
X-Spam-Status: No, score=-15.036 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.535, 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 j0cHM8l4BJJc for <dhcwg@ietfa.amsl.com>; Tue, 4 Feb 2014 09:23:24 -0800 (PST)
Received: from rcdn-iport-6.cisco.com (rcdn-iport-6.cisco.com [173.37.86.77]) by ietfa.amsl.com (Postfix) with ESMTP id ABFB61A0130 for <dhcwg@ietf.org>; Tue, 4 Feb 2014 09:23:23 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1600; q=dns/txt; s=iport; t=1391534603; x=1392744203; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=CiVy48jnBY6Qv58lGqWU9apsj19JS/PfZF0waNRJsZs=; b=O0m5EILpuFw30KDbAoCoOtyy1fUgoyTtu+EZn3H3dDvVuGCEBLQvof+q Uk0N4/G3S+Wmf1SGfjX9BE4en+vx0GpVN/UO75TTI9eaRZ1Q037jZ+LUr teo4t/02r4rM1TPNcQKZo2aDWAZvXQgY8cnbNiwe5vOeWnDIVra5nKf+L I=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AksFAI4h8VKtJV2d/2dsb2JhbABZgww4V74agQ0WdIIlAQEBBAEBATc0CwwEAgEIEQQBAQEKFAkHJwsUCQgCBAENBQgTh2oNzhgTBI4hIzEHBoMegRQBA6pMgy2CKg
X-IronPort-AV: E=Sophos;i="4.95,781,1384300800"; d="scan'208";a="301793258"
Received: from rcdn-core-6.cisco.com ([173.37.93.157]) by rcdn-iport-6.cisco.com with ESMTP; 04 Feb 2014 17:23:23 +0000
Received: from xhc-aln-x11.cisco.com (xhc-aln-x11.cisco.com [173.36.12.85]) by rcdn-core-6.cisco.com (8.14.5/8.14.5) with ESMTP id s14HNN1S016859 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Tue, 4 Feb 2014 17:23:23 GMT
Received: from xmb-rcd-x04.cisco.com ([169.254.8.213]) by xhc-aln-x11.cisco.com ([173.36.12.85]) with mapi id 14.03.0123.003; Tue, 4 Feb 2014 11:23:23 -0600
From: "Bernie Volz (volz)" <volz@cisco.com>
To: Ted Lemon <ted.lemon@nominum.com>, Simon Perreault <simon.perreault@viagenie.ca>
Thread-Topic: [dhcwg] I-D Action: draft-ietf-dhc-conn-status-00.txt
Thread-Index: AQHPIceo9bzRNIc0t0+9ZDQfaLepUpqlVorA
Date: Tue, 04 Feb 2014 17:23:22 +0000
Message-ID: <489D13FBFA9B3E41812EA89F188F018E1AE5596C@xmb-rcd-x04.cisco.com>
References: <20140204093611.4914.51694.idtracker@ietfa.amsl.com> <52F0F3C2.20807@viagenie.ca> <4B094E1A-431F-4F2B-9004-37D6D12BE8F8@nominum.com> <52F0F8F4.4060905@viagenie.ca> <EEEC392B-7B7B-4AAE-BE24-AEC944DFABFA@nominum.com> <52F0FFE6.3050802@viagenie.ca> <C16244FB-DC1A-4E2A-8E51-64DB20F5C341@nominum.com> <52F1173A.8070903@viagenie.ca> <A5CF49F5-C56D-4A47-9D85-938ED1A82542@nominum.com>
In-Reply-To: <A5CF49F5-C56D-4A47-9D85-938ED1A82542@nominum.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.86.240.97]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "dhcwg@ietf.org WG" <dhcwg@ietf.org>
Subject: Re: [dhcwg] I-D Action: draft-ietf-dhc-conn-status-00.txt
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: Tue, 04 Feb 2014 17:23:28 -0000

This may be one consequence of trying to make the draft more generic.

The original problem was about DNS (DNS64) as I recall from draft-wing-dhc-dns-reconfigure-02.

There were only two significant transitions in the dns-reconfigure draft: IPv6-only transition to Dual-Stack and Dual-Stack to IPv6-only.

As this option is only for DHCPv6, this is only useful when IPv6 (DHCPv6) is present. The question is whether IPv4 is also present on the host or not as that could influence the DNS information returned.


This one may be a good document to add to the Agenda for the London IETF - to try to resolve exactly what problems this is trying to solve and when, and then to figure out the solution. Hopefully one or more of the authors' will make a request for time at the London IETF.

- Bernie

-----Original Message-----
From: dhcwg [mailto:dhcwg-bounces@ietf.org] On Behalf Of Ted Lemon
Sent: Tuesday, February 04, 2014 11:39 AM
To: Simon Perreault
Cc: dhcwg@ietf.org WG
Subject: Re: [dhcwg] I-D Action: draft-ietf-dhc-conn-status-00.txt

On Feb 4, 2014, at 11:37 AM, Simon Perreault <simon.perreault@viagenie.ca> wrote:
> And then I further wondered: what use is this draft if a client is 
> IPv4-only? The DHCPv6 server would not be able to talk to the client.

If the client is IPv4-only, the DHCPv4 server might change its behavior, but the DHCPv6 server would not, because there would be no behavior.   :)

_______________________________________________
dhcwg mailing list
dhcwg@ietf.org
https://www.ietf.org/mailman/listinfo/dhcwg