[151068] in North American Network Operators' Group
Re: filtering /48 is going to be necessary
daemon@ATHENA.MIT.EDU (Sven Olaf Kamphuis)
Sat Mar 10 17:52:10 2012
Date: Sat, 10 Mar 2012 22:50:35 +0000 (UTC)
From: Sven Olaf Kamphuis <sven@cb3rob.net>
To: Jimmy Hess <mysidia@gmail.com>
In-Reply-To: <CAAAwwbV3D1v7138RmFw6+UxXyHgLB6HBsxZ8xrmTWNLX=GfiCw@mail.gmail.com>
Cc: "nanog@nanog.org" <nanog@nanog.org>
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org
we also should have expanded the ASN to minimum 64 bits at the time it was
expanded to 32 bit for exactly the same reason btw.
there -are- some technical reasons why /64's would be practical as
"end-site" stuff, and if we want to be able to make all those end site
networks independant, we'd need 64 bit asn's to go along with that.
but main thing: just get enough ram in your stuff, and stop imposing
stupid limitations. (not my problem if your routers keep reloading the
table or rebooting themselves because they're from 1993 ffs ;)
you did buy a new iphone i bet.. why no modern routers.
On Sat, 10 Mar 2012, Jimmy Hess wrote:
> On Sat, Mar 10, 2012 at 12:52 AM, George Bonser <gbonser@seven.com> wrote:
>>> I'm well into my second decade of having a v6 prefix in the dfz and am
>>> passingly familiar with powers of two...
>> Point is that expecting people globally to take a /48 from PA space probably isn't a realistic expectation.
>
> Exactly....
> What's more realistic is you have to get a single /48 of PI space for
> people to carry that globally.
>
> And if you have 5 discontiguous networks, what the RIRs should do is
> carve a /44 out for your
> present and future PI allocations and issue you the 8 /48s;
> the PI /48 routing slots
> that you have justified need for -- arranged so that they fall within
> the same /45.
>
>
> --
> -JH
>
