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 New Policy Proposal (Locking Down the Final /8 Policy)
- Previous message (by thread): [address-policy-wg] 2016-03 New Policy Proposal (Locking Down the Final /8 Policy)
- Next message (by thread): [address-policy-wg] 2016-03 New Policy Proposal (Locking Down the Final /8 Policy)
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Denis Fondras
ripe at liopen.fr
Wed May 18 10:13:15 CEST 2016
I do not support this proposal as long as this is not cleared : > With regards to sub-allocations, I fail to understand what problem are > you trying to solve? Isn't delegating resources downstream towards > end-users (i.e., making assignments or sub-allocations) essentially the > whole point of operating an LIR? Stopping LIRs from doing "LIR stuff" > seems ill advised to me - or what am I missing here? > However I support the spirit of this proposal where allocation from RIPE and usage of IPv4 should be made harder. If IPv4 requires more work than IPv6 then perhaps we will see an increase in IPv6 usage (or I might be naive) > The proposal needs guidance to the NCC as to which specific /22 the NCC > should de-register. The oldest? The least-assigned? > I don't think so. LIR might be free to give back any /22 it suits better. Denis
- Previous message (by thread): [address-policy-wg] 2016-03 New Policy Proposal (Locking Down the Final /8 Policy)
- Next message (by thread): [address-policy-wg] 2016-03 New Policy Proposal (Locking Down the Final /8 Policy)
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]