Hi Rifaat
We have addressed your comments in the security section of the new version of the darft (draft-ietf-bess-evpn-lsp-ping-09).
Thanks
Parag
From:
BESS <bess-bounces@xxxxxxxx> on behalf of Rifaat Shekh-Yusef via Datatracker <noreply@xxxxxxxx>
Date: Tuesday, October 11, 2022 at 9:54 AM
To: secdir@xxxxxxxx <secdir@xxxxxxxx>
Cc: bess@xxxxxxxx <bess@xxxxxxxx>, draft-ietf-bess-evpn-lsp-ping.all@xxxxxxxx <draft-ietf-bess-evpn-lsp-ping.all@xxxxxxxx>, last-call@xxxxxxxx <last-call@xxxxxxxx>
Subject: [bess] Secdir last call review of draft-ietf-bess-evpn-lsp-ping-08
Reviewer: Rifaat Shekh-Yusef
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.
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.
_______________________________________________
BESS mailing list
BESS@xxxxxxxx
https://www.ietf.org/mailman/listinfo/bess
|
--
last-call mailing list
last-call@xxxxxxxx
https://www.ietf.org/mailman/listinfo/last-call
