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-03 Discussion Period extended until 15 July 2016 (Locking Down the Final /8 Policy)
- Previous message (by thread): [address-policy-wg] 2016-03 Discussion Period extended until 15 July 2016 (Locking Down the Final /8 Policy)
- Next message (by thread): [address-policy-wg] 2016-03 Discussion Period extended until 15 July 2016 (Locking Down the Final /8 Policy)
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
William Waites
ww at hubs.net.uk
Mon Jun 20 10:39:05 CEST 2016
Gert Doering <gert at space.net> writes: > But I'm close to giving up on this and calling a ban on further > changes to the IPv4 policy For what it's worth, the new version suits us just fine. Marking the numbers as non-transferrable should raise the barrier for speculators which seems likely to help the situation. Raising the barrier much higher would put new entrants, particularly in rural areas in conditions of market failure at a serious disadvantage. I would still like to see some requirement to demonstrate that addresses are actually assigned and in use even in the case of mergers though. Best wishes, -w -- William Waites Network Engineer HUBS AS60241
- Previous message (by thread): [address-policy-wg] 2016-03 Discussion Period extended until 15 July 2016 (Locking Down the Final /8 Policy)
- Next message (by thread): [address-policy-wg] 2016-03 Discussion Period extended until 15 July 2016 (Locking Down the Final /8 Policy)
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]