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

Ted Lemon <Ted.Lemon@nominum.com> Mon, 01 July 2013 18:58 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 0814B11E823F for <dhcwg@ietfa.amsl.com>; Mon, 1 Jul 2013 11:58:23 -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=[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 1wDUi1znq1Sf for <dhcwg@ietfa.amsl.com>; Mon, 1 Jul 2013 11:58:04 -0700 (PDT)
Received: from exprod7og120.obsmtp.com (exprod7og120.obsmtp.com [64.18.2.18]) by ietfa.amsl.com (Postfix) with ESMTP id 8701411E823A for <dhcwg@ietf.org>; Mon, 1 Jul 2013 11:58:04 -0700 (PDT)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob120.postini.com ([64.18.6.12]) with SMTP ID DSNKUdHRPCY47w1sDY0VMC6xpr+UsarhmuJ5@postini.com; Mon, 01 Jul 2013 11:58:04 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 B07B71B821F for <dhcwg@ietf.org>; Mon, 1 Jul 2013 11:58:03 -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 7FC9319005D; Mon, 1 Jul 2013 11:58:03 -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; Mon, 1 Jul 2013 11:58:03 -0700
From: Ted Lemon <Ted.Lemon@nominum.com>
To: "Prashanth Patil (praspati)" <praspati@cisco.com>
Thread-Topic: [dhcwg] New Version Notification for draft-wing-dhc-dns-reconfigure-01.txt
Thread-Index: AQHOdCenS2HB7oYtEky7nP+0jJgy+ZlQS9sAgABa/4A=
Date: Mon, 01 Jul 2013 18:58:02 +0000
Message-ID: <8D23D4052ABE7A4490E77B1A012B6307751F61CD@mbx-01.win.nominum.com>
References: <B235506D63D65E43B2E40FD27715372E1CE281BD@xmb-rcd-x07.cisco.com>
In-Reply-To: <B235506D63D65E43B2E40FD27715372E1CE281BD@xmb-rcd-x07.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: <F9CF986D3638294E88824C35609A45E8@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: Mon, 01 Jul 2013 18:58:23 -0000

(ad hat off)

On Jul 1, 2013, at 9:32 AM, Prashanth Patil (praspati) <praspati@cisco.com> wrote:
> Yes, this was one of the suggestions made earlier. Notification from relay
> then becomes generic and not specific to DNS. The server decides whatever
> actions need to be done, such as reconfiguring DNS server lists.

I'm sorry, but you did not answer my question.   The question was this:

>> Why don't you just configure the DHCP server to return DNS servers in a
>> different order for different links?   Links are identified by relay
>> agent, so this gets you the precise behavior you want, but with a
>> centralized configuration file rather than with per-relay configuration.

That is, I am not suggesting this as an alternative.   I am asking you why you don't consider this to be a better alternative.

The reason I ask is that what you are proposing is extremely harmful.   You are requiring new special protocol extension with new special-case code to be added to the DHCP server to handle this use case, and you are requiring that relay agents throughout the network be individually configured to specify behavior on the DHCP server, which is a maintenance nightmare.

So if you want to do something this harmful, you should have a good explanation for why it's better than the alternative.