Re: [Last-Call] Genart last call review of draft-ietf-sidrops-ov-egress-01

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



> 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



[Index of Archives]     [IETF Annoucements]     [IETF]     [IP Storage]     [Yosemite News]     [Linux SCTP]     [Linux Newbies]     [Mhonarc]     [Fedora Users]

  Powered by Linux