BOA I-D authors, Perhaps some of my confusion from this discussion stems from the use of the term "bogon". So, with that, I have two more questions I'm hoping will help clarify the goals here for me.
1) Given the use of the term "bogon" within sidr today, it's clearly much wider than the traditional "unallocated from IANA or an RIR" AS number or prefix. Exactly what is a "bogon" in your mind, and shouldn't it be spelled out in the draft? The use of the term "invalid" recurs throughout, but what constitutes a bogon here appears to be well beyond today's operational interpretation of such a term. Projecting this effort under the auspices of "bogons" as we know them today seems a bit inadequate. 2) The BOA draft suggests that if a valid ROA exists for a given prefix then a BOA should be disregarded. Can you explain to me where or why this apparent conflict would occur? 3) Also, I'm still not entirely up to speed here, but say, as an ISP, I issue a ROA for a prefix I want to permit another AS to originate. IF a BOA exists for the AS originating the route then according to the BOA draft "local policies" should be enacted (e.g., drop the "route object"). However, if for a prefix, then if a ROA exists it should essentially trump the BOA. Could you explain the logic behind this text? Thanks! -danny _______________________________________________ sidr mailing list [email protected] https://www.ietf.org/mailman/listinfo/sidr
