Re: [dhcwg] New Version Notification for draft-wing-dhc-dns-reconfigure-01.txt

Ted Lemon <Ted.Lemon@nominum.com> Tue, 02 July 2013 16:56 UTC

Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7FC6521F9EC1 for <dhcwg@ietfa.amsl.com>; Tue, 2 Jul 2013 09:56:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.599
X-Spam-Level:
X-Spam-Status: No, score=-106.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TPP-ruJ1zobT for <dhcwg@ietfa.amsl.com>; Tue, 2 Jul 2013 09:56:40 -0700 (PDT)
Received: from exprod7og125.obsmtp.com (exprod7og125.obsmtp.com [64.18.2.28]) by ietfa.amsl.com (Postfix) with ESMTP id B9EDE21F9EB5 for <dhcwg@ietf.org>; Tue, 2 Jul 2013 09:56:40 -0700 (PDT)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob125.postini.com ([64.18.6.12]) with SMTP ID DSNKUdMGSAkFCQiqRyMj3KB71hqOlA2h03Wl@postini.com; Tue, 02 Jul 2013 09:56:40 PDT
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id 644091B821E for <dhcwg@ietf.org>; Tue, 2 Jul 2013 09:56:40 -0700 (PDT)
Received: from webmail.nominum.com (cas-01.win.nominum.com [64.89.228.131]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTPS id 5D7F419005D; Tue, 2 Jul 2013 09:56:40 -0700 (PDT) (envelope-from Ted.Lemon@nominum.com)
Received: from MBX-01.WIN.NOMINUM.COM ([64.89.228.133]) by CAS-01.WIN.NOMINUM.COM ([64.89.228.131]) with mapi id 14.02.0318.004; Tue, 2 Jul 2013 09:56:40 -0700
From: Ted Lemon <Ted.Lemon@nominum.com>
To: "Bernie Volz (volz)" <volz@cisco.com>
Thread-Topic: [dhcwg] New Version Notification for draft-wing-dhc-dns-reconfigure-01.txt
Thread-Index: AQHOdCenS2HB7oYtEky7nP+0jJgy+ZlQS9sAgABa/4CAAUKZAIAAJFaAgAAEmYCAAAOIgIAAAVsA
Date: Tue, 02 Jul 2013 16:56:39 +0000
Message-ID: <8D23D4052ABE7A4490E77B1A012B6307751F7E9A@mbx-01.win.nominum.com>
References: <8D23D4052ABE7A4490E77B1A012B6307751F61CD@mbx-01.win.nominum.com> <B235506D63D65E43B2E40FD27715372E1CE292C3@xmb-rcd-x07.cisco.com> <489D13FBFA9B3E41812EA89F188F018E185CF3B1@xmb-rcd-x04.cisco.com> <8D23D4052ABE7A4490E77B1A012B6307751F7DA9@mbx-01.win.nominum.com> <489D13FBFA9B3E41812EA89F188F018E185CF4B7@xmb-rcd-x04.cisco.com>
In-Reply-To: <489D13FBFA9B3E41812EA89F188F018E185CF4B7@xmb-rcd-x04.cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [192.168.1.10]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <81175454D4210B468595CB663833F9EA@nominum.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>, "Tirumaleswar Reddy (tireddy)" <tireddy@cisco.com>
Subject: Re: [dhcwg] New Version Notification for draft-wing-dhc-dns-reconfigure-01.txt
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.12
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, 02 Jul 2013 16:56:47 -0000

On Jul 2, 2013, at 12:51 PM, "Bernie Volz (volz)" <volz@cisco.com> wrote:
> I just figured if there was value, that this seemed like a much more streamlined approach. The draft didn't seem to address what happens when the client sends in requests (and making the DHCP server remember this from a reconfigure-request seemed a bit odd -- why not have the relay include this in each Relay-Forw if this is 'needed').

Yes.   Also, why not just have an option that says "client is dual-stack, or not" and let the DHCP server decide what to do about it, rather than getting all specific about what it does with it?

> There's also the question of whether the client itself c/should tell the server this (i.e., it has a v4 address) -- if it is important. That would eliminate the relay from having to do the monitoring.

Requires client changes, so it's understandable that we'd want to do it in relays.   Of course, there's a third unanswered question, which is "what about DHCPv4?"