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] 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 ]
Nick Hilliard
nick at foobar.org
Wed Nov 8 12:24:15 CET 2017
Gert Doering wrote: > both would work to solve the (real) problem at hand, and Jordi's approach > would certainly much easier than trying to come up with unambiguous wording > to "permit some, disallow other" use cases. this is a restatement of the long-standing question about whether the RIPE community should continue with the idea of differentiating between PA and PI address space. If we're going to go down this road, this is a substantial change to make, with far-reaching consequences, and it needs a good deal more attention than a couple of lines in the ipv6 policy doc. Nick
- 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 ]