[address-policy-wg] 2009-05 New Policy Proposal (Multiple IPv6 /32 Allocations for LIRs)

>    Can anybody (maybe from a RIPE staff) give a number of LIR's with
>    more than one AS assigned? This can give us a rough estimate.

There are also companies like us who have a dozen or more LIR's. Some
of those LIRs might only have one AS. It's not necessarily easy for RIPE
or anyone else to figure out which LIRs belong to the same organization.

It is risky to make assumptions based on trawling the RIPE database
because it is:

a) a warped and incomplete view
b) historical information

We don't really know how closely IPv6 networks will resemble IPv4
networks. Of course, many organizations will come up with some network
transition plan that mirrors their IPv4 networks onto IPv6, but there
will also be innovators who do something completely different. When
other organizations begin to copy the innovators, it is a whole new
environment.

IPv6 makes it much easier to create push-type services like
phone-ringing and it is hard to predict the impact of such services. For
example, the simply ability to make a telephone ring in your house,
created a huge increase in demand for telephones, far beyond the demand
created by merely transmitting sound over the wire. Many of the original
telephone services faded away completely, once phone-ringing was
invented, and nowadays, the only people who know about services other
than telephone calls, are the people who read books on telephone
history.

RIPE policy on IPv6 needs to avoid being restrictive, and if we have
accidentally made the policy restrictive, or if too many people
mistakenly interpret the policy as being restrictive, then we need to
change it.

--Michael Dillon