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/routing-wg@ripe.net/
[routing-wg] [ipv6-wg] MERIT Darknet Experiment and RPKI alerts
- Previous message (by thread): [routing-wg] MERIT Darknet Experiment and RPKI alerts
- Next message (by thread): [routing-wg] [ipv6-wg] MERIT Darknet Experiment and RPKI alerts
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Dan Luedtke
maildanrl at gmail.com
Sat Dec 8 23:43:19 CET 2012
On Wed, Dec 5, 2012 at 11:27 AM, Daniel Karrenberg <daniel.karrenberg at ripe.net> wrote: > I think we should be very conscious about when we invoke the policy process. In areas like address space distribution and registration formal policies are vital. However, invoking the policy process whenever anyone has an issue with what the NCC does or did is not the right thing to do. Policies are bureaucracy and should be created *only* if there is no other way. Although this particular experiment might have not helped pushing signed routes and also caused a lot of confusing for some operators, I generally like the idea of the NCC support experiments. Only in an environment where NCC staff does not need to go through hundreds of policies and regulations right before every single step, worthy experiments bringing up worthy results can take place. To sum it all up: Please do *not* make a policy just because NCC staff acts open minded. Regards Dan (who dislikes bureaucracy in general) -- Dan Luedtke http://www.danrl.de
- Previous message (by thread): [routing-wg] MERIT Darknet Experiment and RPKI alerts
- Next message (by thread): [routing-wg] [ipv6-wg] MERIT Darknet Experiment and RPKI alerts
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]