[address-policy-wg] IPv6 PI request is turned down for my multihomed hosting facility - Why?

Hi,

On Wed, Mar 30, 2011 at 09:17:31AM +0000, Tero Toikkanen wrote:
> http://www.ripe.net/ripe/docs/ripe-509#----pa-vs--pi-address-space
> 
> "PI space cannot be re-assigned or further assigned to other parties."
> 
> The text is the same for IPv4 PI and IPv6 PI, but you still can't get both for the same use. Why not? In my opinion the policy is the same for both, but it seems it's not interpreted in the same way.

Actually, there's a significant difference and that has been pointed out
a number of times on the list and at the last RIPE meetings.

The IPv4 policy has this sentence:

http://www.ripe.net/ripe/docs/ripe-509#----network-infrastructure-and-end-user-networks

6.2 Network Infrastructure and End User Networks

IP addresses used solely for the connection of an End User to a
service provider (e.g. point-to-point links) are considered part
of the service provider's infrastructure. These addresses do not
have to be registered with the End User's contact details but can
be registered as part of the service provider's internal infrastructure.
When an End User has a network using public address space this must
be registered separately with the contact details of the End User.

... and this specific clause is not in the IPv6 policy, so "networks
used to number end customers" are considered "part of the assignment
to this end customer".

(Which makes sense for DSL and cable etc. networks, where you really
want to assign a /56 or /48 anyway, and not start tricking around with
single-address-assignment from PI blocks)

Gert Doering
        -- APWG chair
-- 
did you enable IPv6 on something today...?

SpaceNet AG                        Vorstand: Sebastian v. Bomhard
Joseph-Dollinger-Bogen 14          Aufsichtsratsvors.: A. Grundner-Culemann
D-80807 Muenchen                   HRB: 136055 (AG Muenchen)
Tel: +49 (89) 32356-444            USt-IdNr.: DE813185279