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

Sten Carlsen <stenc@s-carlsen.dk> Tue, 15 October 2013 22:12 UTC

Return-Path: <stenc@s-carlsen.dk>
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 43B4E11E818B for <dhcwg@ietfa.amsl.com>; Tue, 15 Oct 2013 15:12:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.519
X-Spam-Level:
X-Spam-Status: No, score=-2.519 tagged_above=-999 required=5 tests=[AWL=0.080, BAYES_00=-2.599, HTML_MESSAGE=0.001, NO_RELAYS=-0.001]
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 gb3-PWbjJGwS for <dhcwg@ietfa.amsl.com>; Tue, 15 Oct 2013 15:12:13 -0700 (PDT)
Received: from mail2.s-carlsen.dk (mail2.s-carlsen.dk [IPv6:2001:16d8:dd00:81ac::17]) by ietfa.amsl.com (Postfix) with ESMTP id 4D09221F9B10 for <dhcwg@ietf.org>; Tue, 15 Oct 2013 15:12:13 -0700 (PDT)
Received: from silver3airport.s-carlsen.dk (unknown [IPv6:2001:16d8:dd00:81ac:5ab0:35ff:fe78:122b]) by mail2.s-carlsen.dk (Postfix) with ESMTPA id 0291626C9; Wed, 16 Oct 2013 00:12:11 +0200 (CEST)
Message-ID: <525DBDBB.9060905@s-carlsen.dk>
Date: Wed, 16 Oct 2013 00:12:11 +0200
From: Sten Carlsen <stenc@s-carlsen.dk>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:24.0) Gecko/20100101 Thunderbird/24.0.1
MIME-Version: 1.0
To: Ted Lemon <ted.lemon@nominum.com>
References: <82A56139-52CC-47A6-9A5B-3708E18D9B86@fugue.com> <525C8B08.5010109@s-carlsen.dk> <27497AD8-45FA-4685-82DA-431DC9787802@nominum.com> <525CFF57.3080506@s-carlsen.dk> <00CFFD78-D4CB-4FD7-ACF4-6446D24A29CD@nominum.com>
In-Reply-To: <00CFFD78-D4CB-4FD7-ACF4-6446D24A29CD@nominum.com>
Content-Type: multipart/alternative; boundary="------------020802090902000808060005"
Cc: "dhcwg@ietf.org WG" <dhcwg@ietf.org>
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: Tue, 15 Oct 2013 22:12:14 -0000

On 15/10/13 22.50, Ted Lemon wrote:
> On Oct 15, 2013, at 4:39 AM, Sten Carlsen <stenc@s-carlsen.dk> wrote:
>> I do see your point, what I try to say is that there is no other system that knows your location within the network better. So either you use DHCP to hand out a "configuration server" including maybe parameters or do configurations it self.
>>
>> I do see that a different type of service to do all those configurations looks like a good idea, however it also means that that the management systems now will have yet another system to manage from the same database.
>>
>> A question: will there be many networks that only have one of the two types of server?
> Hm, I think you've hit on another question.   I'm not sure it's central, but it's worth thinking about.   The SMTP server doesn't vary depending on where in the local network topology the host is connected.   The DNS server needn't either.   The router does, obviously.   Can you think of other examples?
Depending if the organisation is local or global, I can think of the
selection of printers. It is rather impractical to print on the homely
printer when you are abroad. I have not seen this solved in a really
good way yet but I have seen the problems. Normally I don't print much
but some items must be on paper and finding a printer usually takes forever.
At least show me the local printer portal that knows about all local
printers.
>
> BTW, DNS servers frequently are set up with maps of the network in the way that you describe, and indeed one of the arguments against the advice given on FQDNs in the Option Guidelines document is that people might want to do that, and if the DHCP server does the DNS lookup, it won't work.
>

-- 
Best regards

Sten Carlsen

No improvements come from shouting:

       "MALE BOVINE MANURE!!!"