IETF Logo Mail Archive

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

"Prashanth Patil (praspati)" <praspati@cisco.com> Mon, 01 July 2013 13:32 UTC

Return-Path: <praspati@cisco.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 DA59411E80E8 for <dhcwg@ietfa.amsl.com>; Mon, 1 Jul 2013 06:32:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level:
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
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 PEHcX5GoRhSH for <dhcwg@ietfa.amsl.com>; Mon, 1 Jul 2013 06:32:22 -0700 (PDT)
Received: from rcdn-iport-1.cisco.com (rcdn-iport-1.cisco.com [173.37.86.72]) by ietfa.amsl.com (Postfix) with ESMTP id F38E311E811B for <dhcwg@ietf.org>; Mon, 1 Jul 2013 06:32:21 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1064; q=dns/txt; s=iport; t=1372685542; x=1373895142; h=from:to:cc:subject:date:message-id:in-reply-to: content-id:content-transfer-encoding:mime-version; bh=bq+jZh9I4mzZs8ff7ZxaIPZehIOlfp4TtKVgTtgQowg=; b=lD686eiVhg2E1Z7Xub+UZGktIEtzBRfijzQoDtjGotrePK3krerIyC19 7+awnywCMPe3nnWti8ufD0xg5HwFue+bPWNgKtMcnVCZiQZeEGWGpiik4 EbPEkO/dD5O6uiui2sVnxdwC+EOmmpLsrhzdHFvfkmiSJf7JoFH6+7cTQ w=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgIFAPaD0VGtJXG8/2dsb2JhbABagwl7vxh8FnSCIwEBAQQ6PQISAQgYChRCJQIEDgUIiAe7Xo8tMQeDBGMDk3aVF4MRgig
X-IronPort-AV: E=Sophos;i="4.87,974,1363132800"; d="scan'208";a="229232574"
Received: from rcdn-core2-1.cisco.com ([173.37.113.188]) by rcdn-iport-1.cisco.com with ESMTP; 01 Jul 2013 13:32:21 +0000
Received: from xhc-rcd-x08.cisco.com (xhc-rcd-x08.cisco.com [173.37.183.82]) by rcdn-core2-1.cisco.com (8.14.5/8.14.5) with ESMTP id r61DWLe4013886 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Mon, 1 Jul 2013 13:32:21 GMT
Received: from xmb-rcd-x07.cisco.com ([169.254.7.39]) by xhc-rcd-x08.cisco.com ([173.37.183.82]) with mapi id 14.02.0318.004; Mon, 1 Jul 2013 08:32:21 -0500
From: "Prashanth Patil (praspati)" <praspati@cisco.com>
To: Ted Lemon <Ted.Lemon@nominum.com>
Thread-Topic: [dhcwg] New Version Notification for draft-wing-dhc-dns-reconfigure-01.txt
Thread-Index: AQHOY3uM9UALGIVfFEmPJoU9Kl4stpkq4qaAgCD5gwCABMu2gA==
Date: Mon, 01 Jul 2013 13:32:20 +0000
Message-ID: <B235506D63D65E43B2E40FD27715372E1CE281BD@xmb-rcd-x07.cisco.com>
In-Reply-To: <8D23D4052ABE7A4490E77B1A012B6307751F0BE8@mbx-01.win.nominum.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/14.3.4.130416
x-originating-ip: [173.39.67.75]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <39CF619529081B438A34F62C3E94C393@emea.cisco.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 13:32:28 -0000

Hi Ted,

On 28/06/13 11:18 PM, "Ted Lemon" <Ted.Lemon@nominum.com> wrote:

>On Jun 7, 2013, at 8:44 AM, Prashanth Patil (praspati)
><praspati@cisco.com> wrote:
>> This draft proposes a mechanism to extend DHCPv6 such that a DHCPv6
>>Relay
>> Agent can dynamically influence priority of DNS servers provided to a
>> host, so that a host can use an optimal DNS server for resolution.
>
>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.

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.

-Prashanth


>
>If you really want the relay to be the source of knowledge about DNS, why
>not return DNS servers via a relay-supplied options option?
>

v2.23.0 | Report a Bug | By Email