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

Ted Lemon <Ted.Lemon@nominum.com> Tue, 22 October 2013 14:19 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 3842E21E809B for <dhcwg@ietfa.amsl.com>; Tue, 22 Oct 2013 07:19:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.591
X-Spam-Level:
X-Spam-Status: No, score=-106.591 tagged_above=-999 required=5 tests=[AWL=0.008, 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 ddHtiNr5JBhm for <dhcwg@ietfa.amsl.com>; Tue, 22 Oct 2013 07:19:32 -0700 (PDT)
Received: from exprod7og129.obsmtp.com (exprod7og129.obsmtp.com [64.18.2.122]) by ietfa.amsl.com (Postfix) with ESMTP id 8296F11E83E5 for <dhcwg@ietf.org>; Tue, 22 Oct 2013 07:19:13 -0700 (PDT)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob129.postini.com ([64.18.6.12]) with SMTP ID DSNKUmaJYWefN4Dbaf3WqaCNHwicBlCmsDyP@postini.com; Tue, 22 Oct 2013 07:19:13 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 2B4641B82E0 for <dhcwg@ietf.org>; Tue, 22 Oct 2013 07:19:13 -0700 (PDT)
Received: from webmail.nominum.com (cas-02.win.nominum.com [64.89.228.132]) (using TLSv1 with cipher RC4-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 242F9190052; Tue, 22 Oct 2013 07:19:13 -0700 (PDT) (envelope-from Ted.Lemon@nominum.com)
Received: from MBX-01.WIN.NOMINUM.COM ([64.89.228.133]) by CAS-02.WIN.NOMINUM.COM ([64.89.228.132]) with mapi id 14.03.0158.001; Tue, 22 Oct 2013 07:19:07 -0700
From: Ted Lemon <Ted.Lemon@nominum.com>
To: "Reinaldo Penno (repenno)" <repenno@cisco.com>
Thread-Topic: [dhcwg] I-D Action: draft-ietf-dhc-topo-conf-00.txt
Thread-Index: AQHOztr+qeyvH50ZYkS21xtwsh9mdZoBAmMAgAA4lAA=
Date: Tue, 22 Oct 2013 14:19:07 +0000
Message-ID: <5B14C587-4223-4157-AF2B-C9F26C499504@nominum.com>
References: <45A697A8FFD7CF48BCF2BE7E106F06040B73AEFA@xmb-rcd-x04.cisco.com>
In-Reply-To: <45A697A8FFD7CF48BCF2BE7E106F06040B73AEFA@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: <1DC076D98862C544A14AF0E4C6EF8019@nominum.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>
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 14:19:39 -0000

On Oct 22, 2013, at 6:56 AM, Reinaldo Penno (repenno) <repenno@cisco.com> wrote:
> 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.

It would be helpful if you were to review the discussion that happened on this very mailing list about a week ago about the topic of whether it makes sense to configure applications using DHCP.   If you do so, and feel that the question you ask above was not adequately addressed during that discussion, please add to the discussion.

The short answer, though, is that SIP is probably an example of an application that (a) should not be configured by DHCP and (b) if it is configured by DHCP anyway, should probably be configured using an FQDN.