[111441] in North American Network Operators' Group
Re: v6 & DSL / Cable modems [was: Private use of non-RFC1918 IP
daemon@ATHENA.MIT.EDU (David W. Hankins)
Thu Feb 5 19:13:38 2009
Date: Thu, 5 Feb 2009 16:14:21 -0800
From: "David W. Hankins" <David_Hankins@isc.org>
To: NANOG list <nanog@nanog.org>
In-Reply-To: <op.uowivcb7tfhldh@rbeam.xactional.com>
Errors-To: nanog-bounces@nanog.org
--JSkcQAAxhB1h8DcT
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
On Thu, Feb 05, 2009 at 06:15:02PM -0500, Ricky Beam wrote:
>> You might like to review the DHCPv6 specification and try some of its=20
>> implementations.
Joe is being a little overzealous. Unfortunately, there are very
few DHCPv6 clients in the wild today. I think this has grown slightly
since the last time I've had good information on it; Windows Vista,
DOCSIS 3.0, Solaris and other platform specific unixes (unsure of all
the right names and versions). Most free unixes have to be manhandled
to install a client.
The truth is it is actually not very likely that you can build an
IPv6 network today using DHCPv6, unless you have large populations
of those systems.
Most IPv6 deployments today use SLAAC to get an address, and rely upon
DHCPv4 to deliver configuration state (even IETF meetings do this).
Still, it isn't bad to have a DHCPv6 server running to hand out some
IPv6 addresses for configuration state now and again, so Joe is not
entirely wrong.
> I can recall many posts over the years from the IPng WG telling people th=
ey=20
> didn't need DHCP.
There is no need to recall! Subscribe to any IETF mailing list, and
be assured you will still hear the same thing.
--=20
David W. Hankins "If you don't do it right the first time,
Software Engineer you'll just have to do it again."
Internet Systems Consortium, Inc. -- Jack T. Hankins
--JSkcQAAxhB1h8DcT
Content-Type: application/pgp-signature
Content-Disposition: inline
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.9 (GNU/Linux)
iEYEARECAAYFAkmLgNwACgkQcXeLeWu2vmre+gCcDfbHCeeTMmZ021WWf00IrtKS
55kAn3K1cs3V8hpNGPsOLrg7a8bJC5NF
=4KKI
-----END PGP SIGNATURE-----
--JSkcQAAxhB1h8DcT--
