[address-policy-wg] Real multihoming or anycast?

On Tue, 2005-03-29 at 15:47 +0100, Michael.Dillon at radianz.com wrote:
> > Nonetheless they want to multihome, and they want to _really_ multihome,
> > being that anycast instances are usually scattered all over the globe.
> > This implies that there must be a way to get a (however big) routable
> > block that's unlikely to be filtered - well, the proposal has it all.
> 
> Why not learn from the lessons of radio spectrum? A fixed number of
> 3G frequency allocations were put up for auction (or beauty contest).
> 
> Why should RIPE not offer a limited number of /32 allocations for
> operators of anycast fabrics? I suggest that RIPE offer 16 allocations
> of /32 to organizations who intend to operate diverse anycast fabrics
> globally to serve TLD operators and others who can benefit from 
> an anycast fabric. Select the winners by beauty contest based on 
> technical and commercial fitness.

Very simple answer for what is possible with _CURRENT_ policy:

8<-------------------
jeroen at purgatory:~$ whois -h whois.arin.net GOOGLE-IPV6

OrgName:    Google Inc. 
OrgID:      GOGL
Address:    1600 Amphitheatre Parkway
City:       Mountain View
StateProv:  CA
PostalCode: 94043
Country:    US

NetRange:   2001:4860:0000:0000:0000:0000:0000:0000 - 2001:4860:FFFF:FFFF:FFFF:FFFF:FFFF:FFFF 
CIDR:       2001:4860:0000:0000:0000:0000:0000:0000/32 
NetName:    GOOGLE-IPV6
NetHandle:  NET6-2001-4860-1
Parent:     NET6-2001-4800-0
NetType:    Direct Allocation
Comment:    
RegDate:    2005-03-14
Updated:    2005-03-14
----------------->8

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: </ripe/mail/archives/address-policy-wg/attachments/20050330/bfad1c05/attachment.sig>