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] Fwd: Suggestions on a new asn assignment policy
- Previous message (by thread): [address-policy-wg] Fwd: Suggestions on a new asn assignment policy
- Next message (by thread): [address-policy-wg] Fwd: Suggestions on a new asn assignment policy
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
David Huberman
David.Huberman at microsoft.com
Tue Aug 11 14:33:13 CEST 2015
> Hm, so you want to move to a model that does post-auditing in case of > suspected misbehavior (which would involve revokation in case of abuse has > been detected), instead of doing pre-auditing of each request? Correct. Automate and remove the hostmasters from making engineering decisions about OUR networks. > So this sounds like the model employed for DNS domains. This requires > committes of impartial people judging the facts and blah blah blah. It also > involves text how this process works. > > So while I am not opposed to this suggestion, I fear that's it's more > complicated to implement than what might be obvious at first glance. Strongly disagree. It relies on the NCC to do what the NCC has done well for 25 years: be a numbers registry. Where fraud is suspected or discovered, act in the best interests of the Internet. The NCC is well practiced in detecting and fighting fraud, and continually improves in this regard. Trust the NCC staff to do their jobs well; they know what they're doing.
- Previous message (by thread): [address-policy-wg] Fwd: Suggestions on a new asn assignment policy
- Next message (by thread): [address-policy-wg] Fwd: Suggestions on a new asn assignment policy
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]