IETF Logo Mail Archive

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

"Reinaldo Penno (repenno)" <repenno@cisco.com> Tue, 22 October 2013 16:10 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 8DD3811E81B7 for <dhcwg@ietfa.amsl.com>; Tue, 22 Oct 2013 09:10:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.516
X-Spam-Level:
X-Spam-Status: No, score=-10.516 tagged_above=-999 required=5 tests=[AWL=0.083, 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 vLc-tNPNKH+4 for <dhcwg@ietfa.amsl.com>; Tue, 22 Oct 2013 09:10:36 -0700 (PDT)
Received: from rcdn-iport-5.cisco.com (rcdn-iport-5.cisco.com [173.37.86.76]) by ietfa.amsl.com (Postfix) with ESMTP id 1E05711E840A for <dhcwg@ietf.org>; Tue, 22 Oct 2013 09:10:33 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1863; q=dns/txt; s=iport; t=1382458233; x=1383667833; h=from:to:cc:subject:date:message-id:in-reply-to: content-id:content-transfer-encoding:mime-version; bh=gNQoYQVWADzAzkxBNUuJNVIqBK4MAX80zpJCtRAwHhE=; b=ihgll351bbm90glzgHEdnaxLIw0HB6yUOnfisdOTk9PQRxUw4+Haoy7p TRbo6db1skPJUsAVTvN8oB/6PN6S8cCXI7ys1RBdnT8LbMS1AXD0hJDZg XFuOPizdjBJ33OB97lfLojxxtgeOQM+WsPfLABunVozIjIIWmudZ9sem4 4=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AisFAKqiZlKtJV2Y/2dsb2JhbABZgwc4VL5IgSUWdIInAQQ6NAsSAQgiFEIlAgQOBQiHfrpUjx0xB4MfgQoDmTiQWIMkgio
X-IronPort-AV: E=Sophos;i="4.93,549,1378857600"; d="scan'208";a="275169580"
Received: from rcdn-core-1.cisco.com ([173.37.93.152]) by rcdn-iport-5.cisco.com with ESMTP; 22 Oct 2013 16:10:32 +0000
Received: from xhc-rcd-x01.cisco.com (xhc-rcd-x01.cisco.com [173.37.183.75]) by rcdn-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id r9MGAUM9029377 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Tue, 22 Oct 2013 16:10:31 GMT
Received: from xmb-rcd-x04.cisco.com ([169.254.8.27]) by xhc-rcd-x01.cisco.com ([173.37.183.75]) with mapi id 14.02.0318.004; Tue, 22 Oct 2013 11:10:30 -0500
From: "Reinaldo Penno (repenno)" <repenno@cisco.com>
To: Ted Lemon <Ted.Lemon@nominum.com>
Thread-Topic: [dhcwg] I-D Action: draft-ietf-dhc-topo-conf-00.txt
Thread-Index: AQHOztr9CyHJhGQ69kaVnq/uHEmJSpoAa4KAgACt74D//6nFgA==
Date: Tue, 22 Oct 2013 16:10:30 +0000
Message-ID: <45A697A8FFD7CF48BCF2BE7E106F06040B73B14D@xmb-rcd-x04.cisco.com>
In-Reply-To: <5B14C587-4223-4157-AF2B-C9F26C499504@nominum.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: <7DB2670925372942BF4828681890505F@emea.cisco.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 16:10:41 -0000

Ted,

On 10/22/13 7:19 AM, "Ted Lemon" <Ted.Lemon@nominum.com> wrote:

>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.

[RP] that is what I'm doing.

>
>The short answer, though, is that SIP is probably an example of an
>application that (a) should not be configured by DHCP and

[RP] But this draft gives as example in section 5 a DHCP server giving the
address of a SIP server as a DHCP option.

>(b) if it is configured by DHCP anyway, should probably be configured
>using an FQDN.

[RP] And this draft provides the opposite example. In the example in
section 5 the SIP server option is sent as an IP address. This draft says:

"The DHCP server then resolves the domain names listed in the options
   and sends a sip-server option containing the IP addresses that the
   resolver returned for sip.omashu.example.org, and a dns-server option
   containing the IP addresses returned by the resolver for
   dns1.omashu.example.org and dns2.omashu.example.org."


>

v2.23.0 | Report a Bug | By Email