On Tue, 11 Aug 2015, David Huberman wrote:
Existing ASN policy suffices if we simply strike one sentence about
multi-homing (and then ask the NCC to generally automate the
implementation). Existing ASN policy references the criteria in RFC1930
as justification for an ASN, and an audit can rely on the text to clear
out any stupidity.
Yes?
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?
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.
--
Mikael Abrahamsson email: [email protected]
