Re: [dhcwg] I-D Action: draft-ietf-dhc-topo-conf-00.txt

"Reinaldo Penno (repenno)" <repenno@cisco.com> Tue, 22 October 2013 10:56 UTC

Return-Path: <repenno@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 C322D21F9E9D for <dhcwg@ietfa.amsl.com>; Tue, 22 Oct 2013 03:56:51 -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=[AWL=0.000, 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 Vz-1vcT3a4rI for <dhcwg@ietfa.amsl.com>; Tue, 22 Oct 2013 03:56:47 -0700 (PDT)
Received: from rcdn-iport-9.cisco.com (rcdn-iport-9.cisco.com [173.37.86.80]) by ietfa.amsl.com (Postfix) with ESMTP id 4923321F9F4F for <dhcwg@ietf.org>; Tue, 22 Oct 2013 03:56:37 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2464; q=dns/txt; s=iport; t=1382439398; x=1383648998; h=from:to:subject:date:message-id:in-reply-to:content-id: content-transfer-encoding:mime-version; bh=j5bnWlaR3V1D8b1R14PdJTKKXRpD4Y026qi2lWDbg9Y=; b=REUL95qbfRlI6BXLGY0xRzOdNmtglrjIEJArvmlP7dEnpAcX2JhW9LOX BdwICu0+RJs5dTdHSFLSHcxlWjVg2/urGKR2DtmWEt6vXmRdFezwXsKW+ 0gWJF7iZI5nrPqfkYPQ4g7cwd6baWOdqj+ttmnammYJVUZXVRN7I2MEXD g=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Au8FAOFYZlKtJV2a/2dsb2JhbABZgwc4VL5IgSYWbQeCJwEEAQEBNzQdAQgiFDcLJQIEEwiHfg2ZEqFajxU4gx+BCgOZOJBYgySCKg
X-IronPort-AV: E=Sophos;i="4.93,547,1378857600"; d="scan'208";a="272033632"
Received: from rcdn-core-3.cisco.com ([173.37.93.154]) by rcdn-iport-9.cisco.com with ESMTP; 22 Oct 2013 10:56:37 +0000
Received: from xhc-aln-x03.cisco.com (xhc-aln-x03.cisco.com [173.36.12.77]) by rcdn-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id r9MAuaiS026534 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL) for <dhcwg@ietf.org>; Tue, 22 Oct 2013 10:56:36 GMT
Received: from xmb-rcd-x04.cisco.com ([169.254.8.27]) by xhc-aln-x03.cisco.com ([173.36.12.77]) with mapi id 14.02.0318.004; Tue, 22 Oct 2013 05:56:36 -0500
From: "Reinaldo Penno (repenno)" <repenno@cisco.com>
To: "dhcwg@ietf.org" <dhcwg@ietf.org>
Thread-Topic: [dhcwg] I-D Action: draft-ietf-dhc-topo-conf-00.txt
Thread-Index: AQHOztr9CyHJhGQ69kaVnq/uHEmJSpoAa4KA
Date: Tue, 22 Oct 2013 10:56:36 +0000
Message-ID: <45A697A8FFD7CF48BCF2BE7E106F06040B73AEFA@xmb-rcd-x04.cisco.com>
In-Reply-To: <20131022035744.9824.93057.idtracker@ietfa.amsl.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/14.2.3.120616
x-originating-ip: [10.21.101.23]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <6FF342B06BCECC4CB7E96ED7D87BAC58@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [dhcwg] I-D Action: draft-ietf-dhc-topo-conf-00.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, 22 Oct 2013 10:56:52 -0000

Ted/Tomek,

Thanks for this draft. It is very informative. One concern that I have is
that the approach described in figure 3 makes it harder to handle failures.

Another approach is to have the DHCP Server return the same FQDN returned
to all clients. Each client sends a DNS request and gets a DNS reply based
on the source IP of the request. This is the de-facto geo load balancing
which not only allows for locality but also failure. For example, let's
suppose DHCP Server resolves sip.omashu.example.org to 2001:DB8:0:0::2 and
give that IP to the client. Later this SIP Server fails, now what should
the client do? If the client possesses the domain name, it just resolves
it again, gets a different IP address (for a different SIP server) and it
is good to go. If the client only possesses the IP address of the SIP
server, it is stuck until that specific SIP server is online again.

Thanks,

Reinaldo



On 10/21/13 8:57 PM, "internet-drafts@ietf.org" <internet-drafts@ietf.org>
wrote:

>
>A New Internet-Draft is available from the on-line Internet-Drafts
>directories.
> This draft is a work item of the Dynamic Host Configuration Working
>Group of the IETF.
>
>	Title           : Customizing DHCP Configuration on the Basis of Network
>Topology
>	Author(s)       : Ted Lemon
>                          Tomek Mrugalski
>	Filename        : draft-ietf-dhc-topo-conf-00.txt
>	Pages           : 10
>	Date            : 2013-10-21
>
>Abstract:
>   DHCP servers have evolved over the years to provide significant
>   functionality beyond that which is described in the DHCP base
>   specifications.  One aspect of this functionality is support for
>   context-specific configuration information.  This memo describes some
>   such features and makes recommendations as to how they can be used.
>
>
>The IETF datatracker status page for this draft is:
>https://datatracker.ietf.org/doc/draft-ietf-dhc-topo-conf
>
>There's also a htmlized version available at:
>http://tools.ietf.org/html/draft-ietf-dhc-topo-conf-00
>
>
>Please note that it may take a couple of minutes from the time of
>submission
>until the htmlized version and diff are available at tools.ietf.org.
>
>Internet-Drafts are also available by anonymous FTP at:
>ftp://ftp.ietf.org/internet-drafts/
>
>_______________________________________________
>dhcwg mailing list
>dhcwg@ietf.org
>https://www.ietf.org/mailman/listinfo/dhcwg