[101289] in North American Network Operators' Group
Re: v6 subnet size for DSL & leased line customers
daemon@ATHENA.MIT.EDU (Leo Bicknell)
Thu Dec 27 08:52:52 2007
Date: Thu, 27 Dec 2007 08:51:14 -0500
From: Leo Bicknell <bicknell@ufp.org>
To: North American Network Operators Group <nanog@merit.edu>
Mail-Followup-To: North American Network Operators Group <nanog@merit.edu>
In-Reply-To: <34C7D1EB-1214-490C-AB64-A80925DDBA15@muada.com>
Errors-To: owner-nanog@merit.edu
--k+w/mQv8wyuph6w0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
In a message written on Thu, Dec 27, 2007 at 11:27:13AM +0100, Iljitsch van=
Beijnum wrote:
> 100% of the DHCP functionality). But apart from that, some of the =20
> choices made along the way make DHCPv6 a lot harder to use than DHCP =20
> for IPv4. Not only do you lack a default gateway (which is actually a =20
> good thing for fate sharing reasons) but also a subnet prefix length =20
> and any extra on-link prefixes. So even if you do address =20
> configuration with DHCPv6 you need RAs for that other information. =20
I would note, it's not too late to fix these problems. We don't
have wide spread IPv6 deployment yet, and I can't imagine it's all
that hard to send a default gateway in DHCPv6, for example.
--=20
Leo Bicknell - bicknell@ufp.org - CCIE 3440
PGP keys at http://www.ufp.org/~bicknell/
Read TMBG List - tmbg-list-request@tmbg.org, www.tmbg.org
--k+w/mQv8wyuph6w0
Content-Type: application/pgp-signature
Content-Disposition: inline
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (FreeBSD)
iD8DBQFHc63RNh6mMG5yMTYRAtm4AJ9twDLKkHFBD2mX3NC370ONwXDvxQCfRDGG
lTDDsOll/7MiFhyiUMBhQio=
=bCSk
-----END PGP SIGNATURE-----
--k+w/mQv8wyuph6w0--
