Last Call Review of draft-ietf-bess-evpn-lsp-ping-08
review-ietf-bess-evpn-lsp-ping-08-secdir-lc-shekh-yusef-2022-10-11-00
| Request | Review of | draft-ietf-bess-evpn-lsp-ping |
|---|---|---|
| Requested revision | No specific revision (document currently at 11) | |
| Type | Last Call Review | |
| Team | Security Area Directorate (secdir) | |
| Deadline | 2022-10-18 | |
| Requested | 2022-10-04 | |
| Authors | Parag Jain , Ali Sajassi , Samer Salam , Sami Boutros , Greg Mirsky | |
| I-D last updated | 2022-10-11 | |
| Completed reviews |
Rtgdir Last Call review of -07
by Joel M. Halpern
(diff)
Genart Last Call review of -08 by Joel M. Halpern (diff) Secdir Last Call review of -08 by Rifaat Shekh-Yusef (diff) Tsvart Last Call review of -08 by Wesley Eddy (diff) Dnsdir Last Call review of -08 by Di Ma (diff) Secdir Telechat review of -09 by Rifaat Shekh-Yusef (diff) |
|
| Assignment | Reviewer | Rifaat Shekh-Yusef |
| State | Completed | |
| Request | Last Call review on draft-ietf-bess-evpn-lsp-ping by Security Area Directorate Assigned | |
| Posted at | https://mailarchive.ietf.org/arch/msg/secdir/w5bVxePU0OwEQSr87Si6PboRMqU | |
| Reviewed revision | 08 (document currently at 11) | |
| Result | Has nits | |
| Completed | 2022-10-11 |
review-ietf-bess-evpn-lsp-ping-08-secdir-lc-shekh-yusef-2022-10-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. LSP Ping is a widely deployed Operation, Administration, and Maintenance mechanism in MPLS networks. This document describes mechanisms for detecting data plane failures using LSP Ping in MPLS based EVPN and PBB-EVPN network Summary: Ready This document builds on top of an existing and widely deployed mechanism, by adding new TLVs to the LSP Ping mechanism. The existing mechanism security properties are well defined in existing standards, and this document does not seem to make any changes that impacts the existing security properties. I did not see any mention of potential impact of the new TLVs on privacy. It would be nice if that could be addressed in the security considerations section.