Last Call Review of draft-ietf-anima-stable-connectivity-07
review-ietf-anima-stable-connectivity-07-secdir-lc-nystrom-2017-11-27-00
| Request | Review of | draft-ietf-anima-stable-connectivity-07 |
|---|---|---|
| Requested revision | 07 (document currently at 10) | |
| Type | Last Call Review | |
| Team | Security Area Directorate (secdir) | |
| Deadline | 2017-11-25 | |
| Requested | 2017-11-12 | |
| Requested by | Terry Manderson | |
| Authors | Toerless Eckert , Michael H. Behringer | |
| I-D last updated | 2017-11-27 | |
| Completed reviews |
Secdir Last Call review of -07
by Magnus Nyström
(diff)
Iotdir Last Call review of -07 by Francesca Palombini (diff) Genart Last Call review of -07 by Matthew A. Miller (diff) Opsdir Last Call review of -07 by Carlos M. Martínez (diff) Tsvart Telechat review of -07 by Yoshifumi Nishida (diff) |
|
| Comments |
INT and IOT reviewers, please pay additional attention to section 2.1. Stable Connectivity for Centralized OAM Security reviewers, in addition to the Sec Considerations section please review section 2.1.7. Encryption of data-plane connections Thanks! |
|
| Assignment | Reviewer | Magnus Nyström |
| State | Completed | |
| Request | Last Call review on draft-ietf-anima-stable-connectivity by Security Area Directorate Assigned | |
| Reviewed revision | 07 (document currently at 10) | |
| Result | Has nits | |
| Completed | 2017-11-27 |
review-ietf-anima-stable-connectivity-07-secdir-lc-nystrom-2017-11-27-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 describes how to leverage the Automatic Control Plane (ACP) in Automatic Networks (AN) to provide stable and secure connectivity for Operations, Administration and Maintenance (OAM) processes. The document is intended to be *informational*. The document is well written and has an adequate Security Considerations section. I have no issues with this document. Minor nit: "encryption protected" -> "encrypted." -- -- Magnus