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] 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 ]
Gert Doering
gert at space.net
Thu Dec 3 19:23:38 CET 2015
Hi, On Thu, Dec 03, 2015 at 06:21:27PM +0100, h.lu at anytimechinese.com wrote: > And if my fellow colleague here has an opinion on this interpretation of "need" as well as the two examples I was given, enlighten me your thought, would really appreciated. If the customer just moves the same amount of stuff from A to B without anything changing hands or a reduction in the number of machines/services, *need* will still be satisfied. But Andrea has raised a significant point here: if *documentation* is not updated, the assignment is no longer valid, as that is a strict requirement (both for direct PI assignments and for PA-through-LIR assignments, it was not clear from your e-mail which sort you are referring to). Assuming PI, and assuming you are talking about the RIPE NCC making assignments ("Ripe" can not make assignments, as that's the policy-making community, read: all of us), I'm fairly sure the e-mail that contains the actual network that has been assigned clearly contains that requirement, to always keep the documentation up to date. Now, answerung to your second example: if you documented need for 3 locations, and part of that documentation contained something like "we need to upgrade the assignment size to a /24 to handle routing requirements, but we really only have 3 hosts on each site" - and then you move everything to one location, the original criteria would *not* apply any longer, as a single /24 would perfectly well serve to number these combined 9 hosts plus the routing requirements. So, individual cases are different (and I fully trust the NCC to understand the fine nuances, and to apply pain where necessary). Gert Doering -- APWG chair -- have you enabled IPv6 on something today...? SpaceNet AG Vorstand: Sebastian v. Bomhard Joseph-Dollinger-Bogen 14 Aufsichtsratsvors.: A. Grundner-Culemann D-80807 Muenchen HRB: 136055 (AG Muenchen) Tel: +49 (0)89/32356-444 USt-IdNr.: DE813185279 -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 811 bytes Desc: not available URL: </ripe/mail/archives/address-policy-wg/attachments/20151203/a6d99cfd/attachment.sig>
- 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 ]