If the RLP bit is dependent upon ops folks getting the right
config-bit set for each customer we would want that to be as much
automated as possible so there would be the least chance for 'forgot
to set the bit' or 'set bit incorrectly'.
Some sort of mapping of a prefix-route to eBGP neighbors to
I think I see the current plan as a it challenging to depend upon...
If the RLP bit is dependent upon ops folks getting the right
config-bit set for each customer we would want that to be as much
automated as possible so there would be the least chance for 'forgot
to set the bit' or 'set bit
(Cc'ing sidr list also since there is interest there too in this topic.)
If A's customer C does not want A to propagate, then C has a choice not to
send
the prefix-route to A in the first place.
Given that choice, why would C instead choose to poison or downgrade by
altering RLP bits?
Q:
