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] FW: Policy Reciprocity
- Previous message (by thread): [address-policy-wg] FW: Policy Reciprocity
- Next message (by thread): [address-policy-wg] FW: Policy Reciprocity
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Nick Hilliard
nick at foobar.org
Wed Oct 21 13:16:18 CEST 2020
Jim Reid wrote on 21/10/2020 09:32: > Fair enough Shane. [Though I don’t agree legacy space is/was a > mistake.] However nobody can rewind history. So until someone invents > time travel, we just have to live with what you think was a mistake. more to the point, the legacy policy resources document says that if RIPE community policy is created or updated, it only applies to legacy address space if the policy says so explicitly. The consequence of this is that legacy address holders can easily veto any future changes to legacy address policy that they don't like. Some people think this is a great idea; other don't and feel this was a mistake. Either way it's irrelevant because it's not really possible to back out of this sort of policy arrangement. The most sensible approach in the circumstances is leave it and move on. Nick
- Previous message (by thread): [address-policy-wg] FW: Policy Reciprocity
- Next message (by thread): [address-policy-wg] FW: Policy Reciprocity
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]