I like that and hope it's acceptable to the community.
But it was a very small nit - if it turns out to be problematic, I'm ok
leaving things as they were.
RjS
On 3/17/20 10:26 PM, Randy Bush wrote:
I wanted to avoid "be able to be" and have an explicit actor. I see
the difficulty you point to below.
i am happy to change to the following
As the origin AS may be modified by outbound policy, a BGP speaker
MUST apply ROV policy semantics using the My Autonomous System number
in the BGP OPEN message (see RFC 4271 section 4.2) issued to the peer
to which the UPDATE is being sent.
but, in my free opinion, as it is in IETF LC, the change is enough that
it might require approval by chairs and/or AD.
randy
--
last-call mailing list
last-call@xxxxxxxx
https://www.ietf.org/mailman/listinfo/last-call
