This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/address-policy-wg@ripe.net/
[address-policy-wg] 2013-06 New Policy Proposal (PA/PI Unification IPv6 Address Space)
- Previous message (by thread): [address-policy-wg] 2013-06 New Policy Proposal (PA/PI Unification IPv6 Address Space)
- Next message (by thread): [address-policy-wg] 2013-06 New Policy Proposal (PA/PI Unification IPv6 Address Space)
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Tore Anderson
tore at fud.no
Mon Sep 30 19:00:10 CEST 2013
* Nick Hilliard > On 30/09/2013 17:41, Tore Anderson wrote: >> Then you would have only one path and no confusion: >> >> RIR[RIPE NCC] -> LIR -> End User > > you would have confusion about who the address space holder was and what > the end user's rights and obligations were to the ripe ncc. If you're > going to suggest this, talk to the RIPE NCC legal eagles because it's a > difficult area. All existing PI holders would become simultaneously both the LIR *and* the End User in the above chain, so I'm not sure where this confusion would come from? It would essential be the same as if a current LIR assigns its entire allocation to itself (its own infrastructure) and has no external End Users. I have a feeling this already happens a quite a bit in IPv4 these days... Tore
- Previous message (by thread): [address-policy-wg] 2013-06 New Policy Proposal (PA/PI Unification IPv6 Address Space)
- Next message (by thread): [address-policy-wg] 2013-06 New Policy Proposal (PA/PI Unification IPv6 Address Space)
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]