Subject: [bess] Shepherd review on draft-ietf-bess-l2l3-vpn-mcast-mib-01

From: Mach Chen <[email-masked]>
Date: Tue, 22 Dec 2015 09:03:43 +0000

Hi Authors,

I am requested (by the WG chairs) to shepherd this draft, here are my shepherd review comments on this document.

1. Idnits tool shows:
  ** There are 4 instances of too long lines in the document, the longest one
     being 3 characters in excess of 72.

2. Expand the unwell-known abbreviations when first use.

2. Abstract says:
"This memo defines an experimental portion of the Management
   Information Base for use with network management protocols in the
   Internet community."

But the intended status of this document is "Standards Track", what's the real intention?

3. From the title, the document is to define mibs for L2 and L3 Multicast VPNs, it's better to define and scope what are L2 multicast VPN and L3 multicast VPN. And the draft uses "Multicast in VPN" to identify MVPN, it seems not accurate. It's better to use the consistent definition and description for MVPN through the whole document IMHO.

4. Section 4,
The LAST-UPDATED, ORGANIZATION, CONTACT-INFO and the Revision history should be updated to reflect the latest status.

5. Page 5,

This document defines the following flags:

       + Leaf Information Required (L)"

s/+ Leaf Information Required (L)"/ Leaf Information Required (L)"

6.
Section 5.  Security Considerations
   "N/A"

The same issue as the MVPN mib, please enhance it.

7. Please make sure that the MIB Modules are compiled cleanly.

Best regards,
Mach