IETF Logo Mail Archive

Re: [dhcwg] What sorts of services does DHCP configure?

Ted Lemon <ted.lemon@nominum.com> Wed, 16 October 2013 15:26 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 2283321F9FAE for <dhcwg@ietfa.amsl.com>; Wed, 16 Oct 2013 08:26:19 -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 W7qUDyL-xTZE for <dhcwg@ietfa.amsl.com>; Wed, 16 Oct 2013 08:26:12 -0700 (PDT)
Received: from exprod7og110.obsmtp.com (exprod7og110.obsmtp.com [64.18.2.173]) by ietfa.amsl.com (Postfix) with ESMTP id 43BD421F9C7D for <dhcwg@ietf.org>; Wed, 16 Oct 2013 08:26:10 -0700 (PDT)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob110.postini.com ([64.18.6.12]) with SMTP ID DSNKUl6wEUdRjK5pVoJC2BXauWusKJxQGJWC@postini.com; Wed, 16 Oct 2013 08:26:10 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 BD33E1B82E5 for <dhcwg@ietf.org>; Wed, 16 Oct 2013 08:26:09 -0700 (PDT)
Received: from webmail.nominum.com (cas-01.win.nominum.com [64.89.228.131]) (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 9C8E719005C; Wed, 16 Oct 2013 08:26:09 -0700 (PDT) (envelope-from Ted.Lemon@nominum.com)
Received: from [10.0.10.40] (192.168.1.10) by CAS-01.WIN.NOMINUM.COM (192.168.1.100) with Microsoft SMTP Server (TLS) id 14.3.158.1; Wed, 16 Oct 2013 08:26:09 -0700
Content-Type: text/plain; charset="iso-8859-1"
MIME-Version: 1.0 (Mac OS X Mail 7.0 \(1812\))
From: Ted Lemon <ted.lemon@nominum.com>
In-Reply-To: <525EAC58.5060009@s-carlsen.dk>
Date: Wed, 16 Oct 2013 11:26:07 -0400
Content-Transfer-Encoding: quoted-printable
Message-ID: <B98C8DFE-6217-4B68-9FE5-926FCC67F71C@nominum.com>
References: <0CAF13FF2DE695F55BFEEB8BD88E542A@thehobsons.co.uk> <489D13FBFA9B3E41812EA89F188F018E1AD1E42C@xmb-rcd-x04.cisco.com> <525EA740.7000902@s-carlsen.dk> <489D13FBFA9B3E41812EA89F188F018E1AD1E5A1@xmb-rcd-x04.cisco.com> <525EAC58.5060009@s-carlsen.dk>
To: Sten Carlsen <stenc@s-carlsen.dk>
X-Mailer: Apple Mail (2.1812)
X-Originating-IP: [192.168.1.10]
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>, "Bernie Volz (volz)" <volz@cisco.com>
Subject: Re: [dhcwg] What sorts of services does DHCP configure?
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: Wed, 16 Oct 2013 15:26:19 -0000

On Oct 16, 2013, at 11:10 AM, Sten Carlsen <stenc@s-carlsen.dk> wrote:
> The problem then becomes to define where list 2 should/could be dumped? Assuming the floor is not really acceptable.

We don't need to go that far.   The reason I asked this question is that there was strong pushback from the apps area on the recommendation against using FQDNs in DHCP options.   We propose to make the language clearer, but wanted to see what the working group thought about it.

Whether some apps get configured using DHCP or not, the question is, should we make recommendations that assume that this is the common use case for DHCP options, or is the common use case for DHCP options what you and Bernie seem to agree it is: configuring devices.

v2.23.0 | Report a Bug | By Email