Hi Kyle,
Thanks for reviewing.
We added EVI to the glossary and tried to reduce the number of acronyms in version 05.
Hope it reads better now.
Thank you.
Jorge
From: Kyle Rose via Datatracker <noreply@xxxxxxxx>
Date: Monday, July 11, 2022 at 6:28 PM
To: secdir@xxxxxxxx <secdir@xxxxxxxx>
Cc: draft-ietf-nvo3-evpn-applicability.all@xxxxxxxx <draft-ietf-nvo3-evpn-applicability.all@xxxxxxxx>, last-call@xxxxxxxx <last-call@xxxxxxxx>, nvo3@xxxxxxxx <nvo3@xxxxxxxx>
Subject: Secdir last call review of draft-ietf-nvo3-evpn-applicability-04
Reviewer: Kyle Rose
Review result: Has Nits
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.
|
--
last-call mailing list
last-call@xxxxxxxx
https://www.ietf.org/mailman/listinfo/last-call
