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/[email protected]/
[address-policy-wg] 2016-04 Review Phase (IPv6 Sub-assignment Clarification)
- Previous message (by thread): [address-policy-wg] 2016-04 Review Phase (IPv6 Sub-assignment Clarification)
- Next message (by thread): [address-policy-wg] 2016-04 Review Phase (IPv6 Sub-assignment Clarification)
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Kai 'wusel' Siering
wusel+ml at uu.org
Wed Nov 8 18:11:50 CET 2017
On 08.11.2017 16:54, Nick Hilliard wrote: > JORDI PALET MARTINEZ wrote: >> I don’t think reaching consensus in the PI/PA change will be so easy >> in the “near future” (considering that it may require a long >> implementation time), and a middle way proposal looks feasible to >> me. > but it's not a middle way: it's removing the block on sub-assigning to > other parties, which is the thing that distinguishes PI from PA. It's not, as that isn't a distinction; sub-assigning is blocked in general. Quoting https://www.ripe.net/publications/docs/ripe-684#assign: > 2.6. Assign > > To “assign” means to delegate address space to an ISP or End User for specific use within the Internet infrastructure they operate. Assignments must only be made for specific purposes documented by specific organisations and are not to be sub-assigned to other parties. Regards, -kai
- Previous message (by thread): [address-policy-wg] 2016-04 Review Phase (IPv6 Sub-assignment Clarification)
- Next message (by thread): [address-policy-wg] 2016-04 Review Phase (IPv6 Sub-assignment Clarification)
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]