[secdir] Secdir telechat review of draft-ietf-bess-evpn-inter-subnet-forwarding-14

Chris Lonvick via Datatracker <noreply@ietf.org> Tue, 29 June 2021 22:30 UTC

Return-Path: <noreply@ietf.org>
X-Original-To: secdir@ietf.org
Delivered-To: secdir@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 162163A1550; Tue, 29 Jun 2021 15:30:17 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Chris Lonvick via Datatracker <noreply@ietf.org>
To: <secdir@ietf.org>
Cc: bess@ietf.org, draft-ietf-bess-evpn-inter-subnet-forwarding.all@ietf.org, last-call@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 7.33.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <162500581702.14479.10740784349692238870@ietfa.amsl.com>
Reply-To: Chris Lonvick <lonvick.ietf@gmail.com>
Date: Tue, 29 Jun 2021 15:30:17 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/secdir/MpfHlAz25yLpmXGuhUWZxQiFODg>
Subject: [secdir] Secdir telechat review of draft-ietf-bess-evpn-inter-subnet-forwarding-14
X-BeenThere: secdir@ietf.org
X-Mailman-Version: 2.1.29
List-Id: Security Area Directorate <secdir.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/secdir>, <mailto:secdir-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/secdir/>
List-Post: <mailto:secdir@ietf.org>
List-Help: <mailto:secdir-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/secdir>, <mailto:secdir-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 29 Jun 2021 22:30:17 -0000

Reviewer: Chris Lonvick
Review result: Ready


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.

The summary of the review is READY.

This is a re-review. The Security Considerations section has been updated and
addresses the issues I noted from the version -09 I previously reviewed. The
additions to the section do a very good job of addressing the adherence to or
differences from the security considerations sections of the referenced RFCs.