Terry Manderson has entered the following ballot position for draft-ietf-grow-blackholing-02: Discuss
When responding, please keep the subject line intact and reply to all email addresses included in the To and CC lines. (Feel free to cut this introductory paragraph, however.) Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html for more information about IESG DISCUSS and COMMENT positions. The document, along with other ballot positions, can be found here: https://datatracker.ietf.org/doc/draft-ietf-grow-blackholing/ ---------------------------------------------------------------------- DISCUSS: ---------------------------------------------------------------------- Firstly, thank you for documenting operational practice. With regards to section 3.3: "BGP speakers SHOULD only accept and honor BGP announcements carrying the BLACKHOLE community .." I really question why this is a "SHOULD" and not a "MUST", even in an informational RFC. Is the ability for a transit provider so loose that appropriate route filters from a peer ASN can't be applied so that only a "SHOULD" is practical? In which case I do question the sanity of making such a recommendation and thus service available if some other ASN might be able to inject the route and affect another service, even by mistake. Potentially if RPKI is in use, then a peer AS might be able to validate the announcement against a ROA. But it strikes me that this is not the machinery you would want to tack on in this case. The same could be said for section 3.2. I would be rather wary of NOT adding a NO_ADVERTISE (at the very least) and to be honest SHOULD still seems far too loose for me. Almost all of the recipe's that I've gazed upon ---------------------------------------------------------------------- COMMENT: ---------------------------------------------------------------------- >From a comment point of view, this informational document is agnostic on any operational differences between 2-byte and 4-byte ASNs. Is that intentional? Are there any operational differences worth calling out in regard to using extended communities etc? _______________________________________________ GROW mailing list [email protected] https://www.ietf.org/mailman/listinfo/grow
