[nvo3] Secdir last call review of draft-ietf-nvo3-evpn-applicability-04
Kyle Rose via Datatracker <noreply@ietf.org> Tue, 12 July 2022 01:28 UTC
Return-Path: <noreply@ietf.org>
X-Original-To: nvo3@ietf.org
Delivered-To: nvo3@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 0620AC18873D; Mon, 11 Jul 2022 18:28:26 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Kyle Rose via Datatracker <noreply@ietf.org>
To: secdir@ietf.org
Cc: draft-ietf-nvo3-evpn-applicability.all@ietf.org, last-call@ietf.org, nvo3@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 8.6.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <165758930601.5155.8066530853145266053@ietfa.amsl.com>
Reply-To: Kyle Rose <krose@krose.org>
Date: Mon, 11 Jul 2022 18:28:26 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/nvo3/kvTohoy9Bs9cD7DLqOO8oDp_4xY>
Subject: [nvo3] Secdir last call review of draft-ietf-nvo3-evpn-applicability-04
X-BeenThere: nvo3@ietf.org
X-Mailman-Version: 2.1.39
List-Id: "Network Virtualization Overlays \(NVO3\) Working Group" <nvo3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/nvo3>, <mailto:nvo3-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/nvo3/>
List-Post: <mailto:nvo3@ietf.org>
List-Help: <mailto:nvo3-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/nvo3>, <mailto:nvo3-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 12 Jul 2022 01:28:26 -0000
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.
- [nvo3] Secdir last call review of draft-ietf-nvo3… Kyle Rose via Datatracker
- Re: [nvo3] Secdir last call review of draft-ietf-… Rabadan, Jorge (Nokia - US/Sunnyvale)