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

[Sheng Jiang <[e-mail]>]

>The basic philosophy is that DHCP should be used for getting a DEVICE (client)
>connectivity to a network and network resources needed for connectivity, not
>to configure all of the services a USER might want to use.

Agree.

Now, the question will be whether all configuration can be clearly categorized into network connectivities or user services. I guess, there may be controversy for some network connectivities that may open for specific services.

Sheng

>- Bernie
>
>-----Original Message-----
>From: [e-mail] [mailto:[e-mail]] On Behalf
>Of Simon Hobson
>Sent: Wednesday, October 16, 2013 9:10 AM
>To: [e-mail] WG
>Subject: Re: [dhcwg] What sorts of services does DHCP configure?
>
>"Reinaldo Penno (repenno)" wrote:
>Sten Carlsen wrote:
>>> I tend to look at this from the opposite side, what are the services
>>> that need to be configured and infomation that needs to be delivered? And
>as a consequence what are the tools?
>>> What is in the toolbox now and what is missing? Some of the missing tools
>are leading to ugly hacks now.
>>> The answer might not be DHCP, but then what is it?
>
>> Agree with Sten.
>
>
>I do too.
>
>Looking back through the thread, I agree with Ted - we have options for
>things that it doesn't make sense for DHCP to configure. IMO I can see no use
>case for configuring IMAP like services - those are user-centric (or more
>importantly, user-account centric - there is a difference) and in the general
>case not connected to network location.
>
>SMTP is similarly (IMO) generally user-account specific. When I'm sending
>mail, I will normally expect to use my "home" server for the account - which is
>the one server in the world that I can authenticate to and know that it will
>pass my outbound mail (not reject or block it because the email address isn't
>one accepted by whatever random SMTP server the DHCP config might
>supply).
>As an aside, I believe Exchange client config is done initially by DNS - the client
>does a lookup for autoconfigure.<domain name> and requests the config
>from it. In a large corporate environment, it's possible that they simply setup
>difference autoconfig servers (I assume this is an integral part of Exchange
>but that's not something I've worked with) and configure the local DNS
>accordingly. Which leads on to ...
>
>DNS. This is not as location agnostic as Ted makes out in his first post. IME it's
>far from rare to have different views of the DNS in different locations - so
>accessing web.mycompanyname.com in one office may well take you to a
>server close (in network terms) to the user. Move to a different office and this
>same FQDN may well resolve to a different IP. Anycast addressing could well
>achieve the same thing, but fiddling with the DNS is easier (and more
>understandable for a lot of people).
>
>And then we get services like SIP.
>For a "public" account then the config is again user-account specific -
>wherever I am I'll need to connect back to the same registrar. If the telephony
>provider has multiple SIP registrar servers then I may well be best connecting
>to whichever one is closest (in network terms) to me - but that's not
>something some random DHCP admin will have any knowledge of when
>setting up his server.
>But there may well be corporate SIP implementations where DHCP is currently
>the best (or least bad ?) way of configuring things. For devices that are only
>intended to work within the corporate network, the various administrators
>could would out which SIP options to pass to a device depending on network
>location. But again, I think that such a config system would be better if
>separate from DHCP.
>
>
>To finish, as has already been pointed out - much of this is "if we were starting
>from here we wouldn't do ..." - not because the original decisions were wrong
>in the context in which they were taken, but simply because things have
>changed dramatically over the years.
>_______________________________________________
>dhcwg mailing list
>[e-mail]
>https://www.ietf.org/mailman/listinfo/dhcwg
>_______________________________________________
>dhcwg mailing list
>[e-mail]
>https://www.ietf.org/mailman/listinfo/dhcwg