[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
IPv6 Confusion
- Subject: IPv6 Confusion
- From: trejrco at gmail.com (TJ)
- Date: Tue, 17 Feb 2009 15:49:08 -0500
- In-reply-to: <[email protected]>
- References: <6CDE22DE80A63A4DACF4FE2C916519A53F022F784D@BLV11EXVS01.corp.dm.local> <[email protected]> <6CDE22DE80A63A4DACF4FE2C916519A53F022F788E@BLV11EXVS01.corp.dm.local> <050701c99135$df0f0ed0$9d2d2c70$@net> <[email protected]>
>do this, but others here do). For example, getting over the stateless
>autoconfig religion (which was never fully thought out -- how does a
>autoconfig'd device get a DNS name associated with their address in a
DNSSEC-
>signed world again?) and letting network operators use DHCP with IPv6 the
way
>they do with IPv4.
While I wouldn't call SLAAC a religion, I will say (again) that it works in
many cases for some people, today - and whether you consider SLAAC
"half-baked" or "slim-by-design" is a subjective matter.
In the meantime, I am also a proponent for letting ops use DHCPv6 ...
especially DHCPv6-PD!