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-03 New Version and Impact Analysis Published (Locking Down the Final /8 Policy)
- Previous message (by thread): [address-policy-wg] 2016-03 New Version and Impact Analysis Published (Locking Down the Final /8 Policy)
- Next message (by thread): [address-policy-wg] 2016-03 New Version and Impact Analysis Published (Locking Down the Final /8 Policy)
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Alexey Galaev
alex at vpsville.ru
Wed Oct 19 19:03:43 CEST 2016
Agree with Sascha. -1 for this policy from me. BR, Alexey Galaev +7 985 3608004, http://vpsville.ru ----- Исходное сообщение ----- От: "Sascha Luck [ml]" <apwg at c4inet.net> Кому: address-policy-wg at ripe.net Отправленные: Среда, 19 Октябрь 2016 г 17:36:18 Тема: Re: [address-policy-wg] 2016-03 New Version and Impact Analysis Published (Locking Down the Final /8 Policy) I still oppose this proposal. Rationale: 1) It creates yet another class of address space when the goal should be to have only one class. 2) It is potentially harmful to the interests of both the RIPE community and the RIPE NCC by forcing the establishment of an IPv4 "black market", something that the "last /8" policy was *specifically* supposed to prevent. This has direct implications for the quality of registry records, particularly with regard to who *actually* controls a resource. 3) The impact on IPv4 resource consumption is determined by the NCC Impact statement to be "small". This small reduction comes at the price of increased bureaucracy and cost for the businesses that make up the membership. 4) The proposal establishes, as the overriding goal of IP(v4) policy, the conservation of IPv4 resources. This should not be the case, the overriding goal should instead be a transition to IPv6 as quickly as possible. (Re-arranging the deck chairs will not prevent the ship from sinking) rgds, Sascha Luck
- Previous message (by thread): [address-policy-wg] 2016-03 New Version and Impact Analysis Published (Locking Down the Final /8 Policy)
- Next message (by thread): [address-policy-wg] 2016-03 New Version and Impact Analysis Published (Locking Down the Final /8 Policy)
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]