[89112] in North American Network Operators' Group
Re: shim6 @ NANOG (forwarded note from John Payne)
daemon@ATHENA.MIT.EDU (Owen DeLong)
Thu Mar 2 16:39:36 2006
Date: Thu, 02 Mar 2006 13:38:58 -0800
From: Owen DeLong <owen@delong.com>
To: Michael.Dillon@btradianz.com, nanog@nanog.org
In-Reply-To: <OF525A488C.7AC723CE-ON80257125.0056D442-80257125.00586A60@btradianz.com>
Errors-To: owner-nanog@merit.edu
--==========5C9ACFE62A2C8C2BBAA6==========
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
>> The other PI assignment policies that have been proposed either
>> require that you have a /19 already in IPv4 (lots of hosting
>> companies don't have anything this size), or have tens/hundreds of
>> thousands of devices.
>
> It has also been suggested that the simple presence of
> multihoming should be sufficient justification for PI space.
>
Current PI policy in the ARIN region is /22 for IPv4.
>> Even if a hosting company does get a /32 or a /44 or whatever, the
>> "you can't deaggregate your assignment at all" policy rules out
>> having multiple independent POPs unless you somehow arrange to get
>> multiple allocations(which isn't possible now).
>
> People have done creative things with tunnels in the past.
> The widespread existence of MPLS backbones makes that
> even easier. You will always be able to find one situation
> that simply will not fit a given policy. Regardless, we still
> need to have some reasonable policy that creates a level
> playing field, does not unecessarily restrain trade, and
> creates possibilities that smart entrepreneurs can exploit
> to expand the network.
>
Another option is to create separate ORGs for each colo and get
an allocation for each ORG.
Owen
--
If it wasn't crypto-signed, it probably didn't come from me.
--==========5C9ACFE62A2C8C2BBAA6==========
Content-Type: application/pgp-signature
Content-Transfer-Encoding: 7bit
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (Darwin)
iD8DBQFEB2Xyn5zKWQ/iqj0RAvKaAJ9wLBXZuEely1dHOa/3TG0GZikRgQCbBBe7
xATFjpTFAQN+sVUszWWWmkg=
=syfj
-----END PGP SIGNATURE-----
--==========5C9ACFE62A2C8C2BBAA6==========--
