Default External BGP (EBGP) Route Propagation Behavior without Policies
Note: This ballot was opened for revision 07 and is now closed.
(Alia Atlas) Yes
(Ben Campbell) Yes
Alissa Cooper Yes
Warren Kumari Yes
(Alexey Melnikov) (was No Objection) Yes
Alvaro Retana Yes
(Adam Roach) Yes
Thank you for Appendix A; I think it is very helpful. Dale Worley's name appears twice in the Acknowledgements section.
Deborah Brungard No Objection
(Benoît Claise) No Objection
The Appendix A is typically what the OPS directorate would look for.
(Spencer Dawkins) No Objection
I echo Adam's appreciation for Appendix A.
(Suresh Krishnan) No Objection
(Mirja Kühlewind) No Objection
(Terry Manderson) No Objection
(Kathleen Moriarty) No Objection
(Eric Rescorla) No Objection
I am having a little trouble reading Appendix A. If I understand correctly, the idea is: - In version N, you have a behavior X - In version N+1, you introduce a setting S with default value S=X - In version N+2 you change the default to S=!X However, the text says that "installations upgraded from release N+1 will adhere to the previous insecure behavior" Do you need to say that in N+1, you save the value S=X so that in N+1, it continues to apply?