L2L3 VPN Multicast MIB
draft-ietf-bess-l2l3-vpn-mcast-mib-01

SYNTAX        L2L3VpnMcastProviderTunnelType
     MAX-ACCESS    not-accessible
     STATUS        current
     DESCRIPTION
         "For BGP-based I/S-PMSI signaling for either PIM or BGP-MVPN,
          per RFC 6514 section 5, 'PMSI Tunnel Attribute':

     The Tunnel Type identifies the type of the tunneling technology used
     to establish the PMSI tunnel. The type determines the syntax and
     semantics of the Tunnel Identifier field. This document defines the
     following Tunnel Types:

       0 - No tunnel information present
       1 - RSVP-TE P2MP LSP
       2 - mLDP P2MP LSP
       3 - PIM-SSM Tree
       4 - PIM-SM Tree
       5 - PIM-Bidir Tree
       6 - Ingress Replication
       7 - mLDP MP2MP LSP

          For UDP-based S-PMSI signaling for PIM-MVPN, RFC 6513 does not
          specify if a PIM provider tunnel is SSM, SM or Bidir,
          and an agent can use either type 3, 4, or 5 based on its
          best knowledge."
     ::= { l2L3VpnMcastPmsiTunnelAttributeEntry 2 }

  l2L3VpnMcastPmsiTunnelAttributeLabel OBJECT-TYPE
     SYNTAX        MplsLabel
     MAX-ACCESS    not-accessible
     STATUS        current
     DESCRIPTION
         "For BGP-based I/S-PMSI signaling,
          per RFC 6514 section 5, 'PMSI Tunnel Attribute':

     If the MPLS Label field is non-zero, then it contains an MPLS label
     encoded as 3 octets, where the high-order 20 bits contain the label
     value. Absence of MPLS Label is indicated by setting the MPLS Label
     field to zero.

          For UDP-based S-PMSI signaling for PIM-MVPN, this is not
          applicable for now, as RFC 6513 does not specify
          mpls encapsulation and tunnel aggregation with UDP-based
          signaling."
     ::= { l2L3VpnMcastPmsiTunnelAttributeEntry 3 }

  l2L3VpnMcastPmsiTunnelAttributeId OBJECT-TYPE
     SYNTAX        OCTET STRING ( SIZE (0..37) )

Zhang                   Expires February 12, 2016               [Page 6]
Internet-Draft             L2L3-VPN-MCAST MIB                August 2015

     MAX-ACCESS    not-accessible
     STATUS        current
     DESCRIPTION
         "For BGP-based signaling, as defined in RFC 6514 section 5,
          'PMSI Tunnel Attribute'.

          For UDP-based S-PMSI signaling for PIM-MVPN, RFC 6513 only
          specifies the 'P-Group' address, and that is filled into
          the first four octets of this field."
     ::= { l2L3VpnMcastPmsiTunnelAttributeEntry 4 }

  l2L3VpnMcastPmsiTunnelPointer OBJECT-TYPE
     SYNTAX        RowPointer
     MAX-ACCESS    read-only
     STATUS        current
     DESCRIPTION
         "If the tunnel exists in some MIB table, this is the
          row pointer to it."
     ::= { l2L3VpnMcastPmsiTunnelAttributeEntry 5 }

  l2L3VpnMcastPmsiTunnelIf OBJECT-TYPE
     SYNTAX        RowPointer
     MAX-ACCESS    read-only
     STATUS        current
     DESCRIPTION
         "If the tunnel has a corresponding interface, this is the
          row pointer to the ifName table."
     ::= { l2L3VpnMcastPmsiTunnelAttributeEntry 6 }

  -- Conformance Information

  l2L3VpnMcastGroups      OBJECT IDENTIFIER ::= {l2L3VpnMcastConformance 1}
  l2L3VpnMcastCompliances OBJECT IDENTIFIER ::= {l2L3VpnMcastConformance 2}

  -- Compliance Statements

  l2L3VpnMcastCompliance MODULE-COMPLIANCE
      STATUS  current
      DESCRIPTION
         "The compliance statement: no mandatory groups "
      MODULE  -- this module
      ::= { l2L3VpnMcastCompliances 1 }

  -- units of conformance

  l2L3VpnMcastOptionalGroup    OBJECT-GROUP
      OBJECTS {
          l2L3VpnMcastPmsiTunnelPointer,

Zhang                   Expires February 12, 2016               [Page 7]
Internet-Draft             L2L3-VPN-MCAST MIB                August 2015

          l2L3VpnMcastPmsiTunnelIf
          }
      STATUS      current
      DESCRIPTION
          "Support of these object is not required."
      ::= { l2L3VpnMcastGroups 1 }

  END

5.  Security Considerations

   N/A

6.  IANA Considerations

   IANA is requested to root MIB objects in the MIB module contained in
   this document under the transmission subtree.

   .

7.  References

7.1.  Normative References

   [RFC2578]  McCloghrie, K., Ed., Perkins, D., Ed., and J.
              Schoenwaelder, Ed., "Structure of Management Information
              Version 2 (SMIv2)", STD 58, RFC 2578,
              DOI 10.17487/RFC2578, April 1999,
              <http://www.rfc-editor.org/info/rfc2578>.

   [RFC2579]  McCloghrie, K., Ed., Perkins, D., Ed., and J.
              Schoenwaelder, Ed., "Textual Conventions for SMIv2",
              STD 58, RFC 2579, DOI 10.17487/RFC2579, April 1999,
              <http://www.rfc-editor.org/info/rfc2579>.

   [RFC2580]  McCloghrie, K., Ed., Perkins, D., Ed., and J.
              Schoenwaelder, Ed., "Conformance Statements for SMIv2",
              STD 58, RFC 2580, DOI 10.17487/RFC2580, April 1999,
              <http://www.rfc-editor.org/info/rfc2580>.

   [RFC6513]  Rosen, E., Ed. and R. Aggarwal, Ed., "Multicast in MPLS/
              BGP IP VPNs", RFC 6513, DOI 10.17487/RFC6513, February
              2012, <http://www.rfc-editor.org/info/rfc6513>.

Zhang                   Expires February 12, 2016               [Page 8]
Internet-Draft             L2L3-VPN-MCAST MIB                August 2015

   [RFC6514]  Aggarwal, R., Rosen, E., Morin, T., and Y. Rekhter, "BGP
              Encodings and Procedures for Multicast in MPLS/BGP IP
              VPNs", RFC 6514, DOI 10.17487/RFC6514, February 2012,
              <http://www.rfc-editor.org/info/rfc6514>.

   [RFC7117]  Aggarwal, R., Ed., Kamite, Y., Fang, L., Rekhter, Y., and
              C. Kodeboniya, "Multicast in Virtual Private LAN Service
              (VPLS)", RFC 7117, DOI 10.17487/RFC7117, February 2014,
              <http://www.rfc-editor.org/info/rfc7117>.

7.2.  Informative References

   [RFC3410]  Case, J., Mundy, R., Partain, D., and B. Stewart,
              "Introduction and Applicability Statements for Internet-
              Standard Management Framework", RFC 3410,
              DOI 10.17487/RFC3410, December 2002,
              <http://www.rfc-editor.org/info/rfc3410>.

Author's Address

   Zhaohui Zhang
   Juniper Networks, Inc.
   10 Technology Park Drive
   Westford, MA  01886
   USA

   EMail: zzhang@juniper.net

Zhang                   Expires February 12, 2016               [Page 9]