[pkg-dhcp-devel] Bug#592539: (isc-dhcp-server: supply additional initscript for IPv6 daemon): Yet another idea how to solve this issue

[Philipp Kern]

Hi,

On Mon, Oct 29, 2012 at 12:52:42PM +0100, Axel Beckert wrote:
> Philipp Kern wrote:
> > > This fix will enhance the IPv6-readyness in wheezy a lot, as in the
> > > next years the IPv6 rollout in corporate networks requires DHCPv6 in
> > > most cases (beside maybe parallel DHCPv4).
> > Meh, DHCPv6 is mostly used with Windows clients anyway.
> 
> I disagree. DHCPv6 is used a lot where you don't want SLAAC tell
> outsiders (e.g. Google) how much hardware from which vendor is used in
> your company/school

- privacy extensions

> and/or if you don't want your users to use privacy extensions to be
> able to audit the internal network. That's all not OS-dependent.

- 802.1x
- ND cache polling and/or traps

Auditing by "I gave him that address so he has to use it" in an address
space as vast as IPv6 is ridiculous IMHO. In IPv4 you really ran into
conflicts.

> > Many people relate the necessity of running DHCPv4 when using IPv4
> > with DHCPv6 and IPv6.
> I don't think so. 

I know that there's the fixed assumption by many people that stateful
DHCPv6 is essential, because that's how it's done with IPv4.

> > That's simply not true.
> IMHO wrong. There's a true core in it: If you need to announce HTTP
> proxies, NTP servers and other stuff besides just IP addresses in your
> IPv6 network, SLAAC doesn't suffice and you need DHCPv6 even if SLAAC
> is in use.

Stateless DHCPv6, yes. Which can often also be provided by the network
components themselves because it's stateless. (But now I may be
suggesting to use proprietary components in your network, which is also
the reality, but I can as well shut up because it doesn't help the point
here.)

Kind regards
Philipp Kern
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 490 bytes
Desc: Digital signature
URL: <http://lists.alioth.debian.org/pipermail/pkg-dhcp-devel/attachments/20121029/84762c3e/attachment.pgp>