[101291] in North American Network Operators' Group
Re: IPv6 Addressing Plans
daemon@ATHENA.MIT.EDU (Jeroen Massar)
Thu Dec 27 14:00:25 2007
Date: Thu, 27 Dec 2007 19:59:15 +0100
From: Jeroen Massar <jeroen@unfix.org>
To: michael.dillon@bt.com
CC: nanog@nanog.org
In-Reply-To: <D03E4899F2FB3D4C8464E8C76B3B68B001A3D1D5@E03MVC4-UKBR.domain1.systemhost.net>
Errors-To: owner-nanog@merit.edu
This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--------------enig55533F76CE012435824C4EDC
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
michael.dillon@bt.com wrote:
[..]
> -Do not assign from PoP aggregates=20
What do you mean with the above? If I understand the line correctly,
then I disagree with it.
IMHO generally ones network infrastructure is pretty aggregated
internally already as the physical structure is most likely also a
star/bus topology which fans out towards the endusers, while the core is
where you connect to the Internet. When you have 'home users' and even
residential users they generally get connected to a PoP for a certain
neighborhood. Generally these users won't move around the country. As
such, just give the PoP a /40 or whatever you need to serve the users
from that site. This keeps the number of internal routes low. Now if you
have a well paying customer who wants to take their /48 along, just
announce the more specific in iBGP. Of course never announce a de-agg of
the allocation you received into eBGP.
Or did you mean something different?
Greets,
Jeroen
--------------enig55533F76CE012435824C4EDC
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (MingW32)
iD8DBQFHc/YDKaooUjM+fCMRAkWKAJ9hRKmjMQIu6Fs+sXor8xH+J/xdQQCgjrWF
FCxXUudZWG4lixTBtLUY7H4=
=t635
-----END PGP SIGNATURE-----
--------------enig55533F76CE012435824C4EDC--
