[ppml] Fw: IRS goes IPv6!

[Jeroen Massar]

On Tue, 2006-02-14 at 14:33 -0600, Stephen Sprunk wrote:
> [ Forwarded from NANOG, for those that aren't on it, and edited for 
> brevity ]
> 
> Thus spake "Jeroen Massar" <jeroen at unfix.org>
> > I Ar Es,
> >
> > At least they have received the 2610:30::/32 allocation from ARIN.
> > Lets see if they how taxing they find IPv6 ;)
> ...
> > OrgName:    Internal Revenue Service
> ...
> > NetRange:   2610:0030:0000:0000:0000:0000:0000:0000 -
> > 2610:0030:FFFF:FFFF:FFFF:FFFF:FFFF:FFFF
> > CIDR:       2610:0030:0000:0000:0000:0000:0000:0000/32
> ...
> > NetType:    Direct Allocation
> 
> How, exactly, did the IRS manage to get a direct allocation from ARIN?  Did 
> they somehow qualify as an LIR?  Did they snow the staffers?  Did the US 
> Govt put some sort of pressure on ARIN?
> 

There are two points I wanted to make with the email, though not many
caught it I guess (could be because of the broken sentence ;) :
 - a pun: 'how taxing the IRS would find IPv6'
   * difficulty of getting the address space (alloc)
   * difficulty of setting up and starting to use it (deploy)
 - the fact that everybody can get address space.

It is very simple: Current policy has 1 main entry:
 - requirement for more than 200 'sites'

The word 'site' is very open. Every single office building of the IRS
can be counted as a seperate entity. They most likely don't have
connectity to the $world, but they do need address space. Thus they
request from ARIN their address space, specify that they have 200++
sites and simply get it (after having paid up etc).

Most likely it will never pop up on the internet, but that is not what
the RIR's are for; they only provide address space and this organisation
showed a requirement for address space.

> If end sites like the IRS can get direct allocations today,
> perhaps all this 
> discussion about PI space is moot and we don't need 2005-1 et al.

The policy doesn't cover 1 case: SMB's who who want their own address
space for various reasons (mostly being independent). For these cases
their should come a new policy which allows them to get a /48 or upto
something like a /40 depending on how much they really need and if they
consist out of a lot of networks or just a few.

These 'small' blocks should be allocated from a single large block, per
RIR or globally chunked into a portion each for a RIR. This would, in
case of routing scalability issues to start some aggregation or other
weird tricks in those blocks, assuming that they will become the gross
of the table. Shim6 and future work could then use the /48 as an ID,
while using the /48 they receive from their upstream as the IP which is
routed. But that is just keeping in mind the future and that we can't
envision what will happen, though the math is pretty easy (every
business a /48, X million businesses/other-sites globally...)

Greets,
 Jeroen

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 240 bytes
Desc: This is a digitally signed message part
URL: <https://lists.arin.net/pipermail/arin-ppml/attachments/20060215/750b0cfe/attachment.sig>