This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/ipv6-wg@ripe.net/
Lack of DHCPv6 (was: Re: [ipv6-wg] New draft document available: ... )
- Previous message (by thread): Lack of DHCPv6 (was: Re: [ipv6-wg] New draft document available: ... )
- Next message (by thread): Lack of DHCPv6 (was: Re: [ipv6-wg] New draft document available: ... )
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Fredrik Pettai
pettai at nordu.net
Tue Nov 16 16:02:09 CET 2010
On Nov 15, 2010, at 9:07 PM, Michael Schneider/calispera.com wrote: > Fredrik Pettai wrote on 15.11.2010 15:37:24: >> (Shane also told me that Apple are supporters of the zeroconf > philosophy, >> so they are of a different opinion of how things should be solved. > Share: >> correct me if I interpreted you wrong) > > Hi Fredrik, > yes you are right, Apples zeroconf initiative called Bonjour ( > www.apple.com/bonjour). > >> I also know an engineer at Apple, and according to him, the only way of >> influencing decisions of what should be fixed / added etc. is to > bugreport it (@ >> https://bugreport.apple.com). The more people that do this, the better, >> and more likelier that it will be implemented. > >> So, spread the word... let Apple know what you think about (the lack of) > DHCPv6. > > But, what is the need for dhcpv6 if you have technologys like IPv6 SAC > mechanism with (for example) MulticastDNS ( > draft-cheshire-dnsext-multicastdns.txt) support. > > IMHO at least 80% of standard (office) environments don`t need any dhcpv6 > support. > Let me know what you are think about it. For the home user that's fine, but maybe not for a enterprise network. It's not just about provisioning DNS/resolver configuration to clients. It's about access control, e.g. to be able to centrally manage which client that are connected/assigned an IP. Traceability e.g. which client where connect a specific time etc. to name a few of the common things you do with a centralized DHCP(v4) solution today. (I do confess that I'm not up to speed on the IPv6 development since ~1 year back) Regards, /P
- Previous message (by thread): Lack of DHCPv6 (was: Re: [ipv6-wg] New draft document available: ... )
- Next message (by thread): Lack of DHCPv6 (was: Re: [ipv6-wg] New draft document available: ... )
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ ipv6-wg Archives ]