Re: [dhcwg] Review of Service-Discovery-Type options in DHCP

If you use the domain name search list as a resource discovery search list 
as well, then this constrains your use of the domain name search list in a 
way that makes me uncomfortable.   Likewise with the domain name.   If a 
mechanism like this is the right way to go (and I don't agree that it is), 
then it would have to be another search list - it should not be overloaded.

TBF, I would rather use SLP than either DHCP or DNS, if it worked.   My 
interest in promoting the use of DHCP options for this is not that I think 
it's the right solution in the end, but that I think it's useful now.   It 
also provides a useful upgrade path for non-SLP-compliant devices - you 
have the DHCP server do the SLP request on behalf of the client.   This 
allows SLP and non-SLP clients to coexist in a way that is not obnoxious 
for the network administrator.  Non-SLP clients might get different results,
  because of the weaknesses of DHCP as a service location protocol, but they 
will get results.

I see a lot of pushback on using DHCP for service location, and I wonder if 
some of this is motivated by a wish to eliminate competition for SLP, so 
that SLP has a chance to get deployed.   If so, perhaps I've described a 
way that everybody can win.   It's definitely not my intention to prevent 
deployment of SLP to benefit DHCP.   I just want something that works, and 
I think that having two solutions that solve the problem in different ways 
is likely to produce the right results.

_______________________________________________
dhcwg mailing list
dhcwg@ietf.org
https://www1.ietf.org/mailman/listinfo/dhcwg