[bess] Secdir last call review of draft-ietf-bess-l2l3-vpn-mcast-mib-15

Robert Sparks <rjsparks@nostrum.com> Thu, 23 August 2018 18:13 UTC

Return-Path: <rjsparks@nostrum.com>
X-Original-To: bess@ietf.org
Delivered-To: bess@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 5A6E2130EE4; Thu, 23 Aug 2018 11:13:46 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Robert Sparks <rjsparks@nostrum.com>
To: secdir@ietf.org
Cc: draft-ietf-bess-l2l3-vpn-mcast-mib.all@ietf.org, ietf@ietf.org, bess@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.83.1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <153504802630.12083.17997182428916670301@ietfa.amsl.com>
Date: Thu, 23 Aug 2018 11:13:46 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/bess/AYHU_XaNMQ9p9Obby14OEMpsrMA>
Subject: [bess] Secdir last call review of draft-ietf-bess-l2l3-vpn-mcast-mib-15
X-BeenThere: bess@ietf.org
X-Mailman-Version: 2.1.27
List-Id: BGP-Enabled ServiceS working group discussion list <bess.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/bess>, <mailto:bess-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/bess/>
List-Post: <mailto:bess@ietf.org>
List-Help: <mailto:bess-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/bess>, <mailto:bess-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 23 Aug 2018 18:13:47 -0000

Reviewer: Robert Sparks
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

This document is ready for publication as Proposed Standard RFC.

This document provides a pair of MIB modules intended as building blocks for
other MIB modules that will monitor/configure layer 2 and layer 3 virtual
private networks supporting multicast.

The MIB objects are all not-accessible or read-only. The security
considerations section follows the guidance at

The document had a thorough MIB doctor review.