<html><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><blockquote type="cite" class=""><blockquote type="cite" class="">Just FYI: <a href="https://www.rfc-editor.org/rfc/rfc7999.txt" class="">https://www.rfc-editor.org/rfc/rfc7999.txt</a><br class="">I guess this feature deserves to be implemented.<br class=""></blockquote><br class="">Oh, sure. We plan to implement it.<br class=""></blockquote><br class=""><div class="">It would be nice if export filters for the Kernel protocol could set a route type, as in iproute(8):<br class=""><br class=""></div><blockquote style="margin: 0 0 0 40px; border: none; padding: 0px;" class=""><div class="">TYPE := [ unicast | local | broadcast | multicast | throw |</div><div class=""> unreachable | prohibit | <b class="">blackhole</b> | nat ]</div></blockquote><div class=""><br class=""></div><div class="">That would probably make more versatile than a static RFC7999 hack, while allowing to easily implement RFC7999 and others.</div><div class=""><br class=""></div><div class="">Greetings,</div><div class=""><br class=""></div><div class=""><span class="Apple-tab-span" style="white-space:pre"> </span>Clemens</div><div class=""><br class=""></div></body></html>