<html><head><meta http-equiv="Content-Type" content="text/html; charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><div class=""><div style="color: rgb(0, 0, 0); letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><br class=""></div></div><div><blockquote type="cite" class=""><div class="">On Jan 31, 2019, at 1:28 PM, Roel Parijs <<a href="mailto:roel.parijs@gmail.com" class="">roel.parijs@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div dir="ltr" class=""><div dir="ltr" class=""><div class="">For our BGP customers the problem is more complex. Our BGP customers can send us the RTBH community, and we will drop the traffic at our borders. Since we're only running a small network, we don't have the capacity to deal with large attacks. If we would be able to forward (and maybe alter it) this RTBH community towards our upstream providers, the impact on our network would be limited. However, the RFC states that an announcement tagged with the blackhole community should get the no_advertise or no_export community.</div><div class=""><br class=""></div><div class="">What is your opinion on this ?</div><div class=""><br class=""></div></div></div></div></blockquote></div><br class=""><div class="">In RFC7999 section 3.2 the first paragraph talks about what you're mentioning, NO_EXPORT and/or NO_ADVERTISE. It uses the word SHOULD. SHOULD has special meaning in RFCs, its not MUST. Its also not MAY. RFC2119 talks about the way these words should be interpreted. </div><div class=""><br class=""></div><div class="">In the next paragraph it says that extreme caution should be used when "purposefully propagating IP prefixes tagged with the BLACKHOLE community outside the local routing domain, unless policy explicitly aims at doing just that."</div><div class=""><br class=""></div><div class="">So if your local routing policy is to propagate those blackholes on to your upstreams (and its mutually agreed and they're configured to accept them), then it can be done. Nothing technical in the RFC stopping that. </div><div class=""><br class=""></div><div class="">Theo</div><div class=""><br class=""></div></body></html>