On 4/8/26 06:48, Martin Pels wrote:
On 08/04/2026 11:40, [email protected]
wrote:
I read the draft and understand the idea of not to focus on specific
technical implementations and requirements.
I'd like to suggest adding in section "Originating and Propagating
BGP Routes" more details -
Operators <bcp14>MUST NOT</bcp14> advertise BGP routes for prefixes
that are not globally routable, including prefixes from bogon
address space and prefixes more specific than commonly accepted
global routing limits (e.g., longer than /24 for IPv4 or /48 for IPv6)
I think "MUST NOT" is too strong. There are scenarios where
advertising more specifics may be a good idea operationally (while
knowing that their reach will be limited).
The opsec-inform document, section 5.3, goes into some more detail about
prefix lengths and where they are accepted. For this document, dropping
the e.g. will remove the conflicting advice.
This is a reminder for grow participants that the current work is spread
across 3 different documents. I'd encourage you to see how the advice
for each document harmonizes with the others. Doubly so since we have
one document progressing through last call without the other two in the
logical cluster.
-- Jeff
_______________________________________________
GROW mailing list -- [email protected]
To unsubscribe send an email to [email protected]
