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] An interesting policy question
- Previous message (by thread): [address-policy-wg] An interesting policy question
- Next message (by thread): [address-policy-wg] An interesting policy question
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Sander Steffann
sander at steffann.nl
Thu Dec 3 20:25:29 CET 2015
Hi Lu, > Because if *need* includes whole package of justification material, then by definition, change any thing in that package(for example, location of the server, upstream provider), would request NCC approval for the assignment again It depends what the conditions were for getting the assignment in the first place. If you were allowed to make an assignment for reason X then you can't just change X. You can change Y and Z, as long as they weren't part of the condition. What those fictional X, Y and Z might be are completely dependent on the actual policy, and for addresses we don't have any needs criteria anymore so this is all hypothetical. > therefore effectively requested NCC to manage all the infrastructure adjustment by it's members(assure the LIR do not have assignment window), because the need has changed. Are you still talking about RIPE NCC here? You are talking about situations and concepts that seem to have nothing to do with our region... Let's stop this discussion on hypothetical impact of hypothetical policy. Cheers, Sander
- Previous message (by thread): [address-policy-wg] An interesting policy question
- Next message (by thread): [address-policy-wg] An interesting policy question
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]