Skip to main content

Last Call Review of draft-ietf-nvo3-evpn-applicability-04
review-ietf-nvo3-evpn-applicability-04-secdir-lc-rose-2022-07-11-00

Request Review of draft-ietf-nvo3-evpn-applicability
Requested revision No specific revision (document currently at 05)
Type Last Call Review
Team Security Area Directorate (secdir)
Deadline 2022-07-11
Requested 2022-06-27
Authors Jorge Rabadan , Matthew Bocci , Sami Boutros , Ali Sajassi
Draft last updated 2022-07-11
Completed reviews Rtgdir Last Call review of -03 by Mach Chen (diff)
Opsdir Last Call review of -04 by Scott O. Bradner (diff)
Genart Last Call review of -04 by Reese Enghardt (diff)
Secdir Last Call review of -04 by Kyle Rose (diff)
Assignment Reviewer Kyle Rose
State Completed
Review review-ietf-nvo3-evpn-applicability-04-secdir-lc-rose-2022-07-11
Posted at https://mailarchive.ietf.org/arch/msg/secdir/RP_NK0o3oJ1aPNwNSaaFMfPYNFg
Reviewed revision 04 (document currently at 05)
Result Has Nits
Completed 2022-07-11
review-ietf-nvo3-evpn-applicability-04-secdir-lc-rose-2022-07-11-00
I have reviewed this document as part of the security directorate's ongoing
effort to review all IETF documents being processed by the IESG.  These
comments were written primarily for the benefit of the security area directors.
 Document editors and WG chairs should treat these comments just like any other
last call comments.

This document is Ready with Nits.

There are no novel security issues presented by this work. Some may present
themselves in follow-up documents (e.g., in draft-sajassi-bess-secure-evpn),
but this document doesn't itself describe anything new that would require
security considerations beyond those of the underlying protocols and
infrastructure.

Nits:

* Add "EVI" to the glossary. But also...

* I'll amplify Scott Bradner's observation that this document would be a lot
easier to read without every other word being an abbreviation.