L2L3 VPN Multicast MIB
draft-ietf-l3vpn-l2l3-vpn-mcast-mib-00

The information below is for an old version of the document
Document Type Active Internet-Draft (l3vpn WG)
Last updated 2013-10-14
Replaced by rfc8502, draft-ietf-bess-l2l3-vpn-mcast-mib
Stream IETF
Intended RFC status (None)
Formats plain text pdf html bibtex
Stream WG state WG Document (wg milestones: Mar 2014 - Submit specification..., Jun 2015 - Submit specification... )
Document shepherd None
IESG IESG state I-D Exists
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to (None)
L3 VPN Working Group                                            J. Zhang
Internet-Draft                                    Juniper Networks, Inc.
Intended status: Standards Track                        October 14, 2013
Expires: April 17, 2014

                         L2L3 VPN Multicast MIB
                   draft-ietf-l3vpn-l2l3-vpn-mcast-mib-00

Abstract

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

   In particular, it describes managed objects common to both VPLS and
   VPN Multicast.

Status of This Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at http://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on April 17, 2014.

Copyright Notice

   Copyright (c) 2013 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (http://trustee.ietf.org/license-info) in effect on the date of
   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with respect
   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as

Zhang                     Expires April 17, 2014                 [Page 1]

Internet-Draft             L2L3-VPN-MCAST MIB               October 2013

   described in the Simplified BSD License.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . . . 3
   2.  The Internet-Standard Management Framework  . . . . . . . . . . 3
   3.  Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . 3
   4.  Summary of MIB Module . . . . . . . . . . . . . . . . . . . . . 3
   5.  Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . 3
   6.  Security Considerations . . . . . . . . . . . . . . . . . . . . 8
   7.  IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 8
   8.  References  . . . . . . . . . . . . . . . . . . . . . . . . . . 8
     8.1.  Normative References  . . . . . . . . . . . . . . . . . . . 8
     8.2.  Informative References  . . . . . . . . . . . . . . . . . . 9

Zhang                     Expires April 17, 2014                 [Page 2]

Internet-Draft             L2L3-VPN-MCAST MIB               October 2013

1.  Introduction

   Multicast in VPLS and VPN can be achieved by using provider tunnels
   to deliver to all or a subset of PEs.  The signaling of provider
   tunnel choice is very similar for both VPLS and VPN multicast (aka
   MVPN), and this memo describes managed objects common to both VPLS
   Multicast [I-D.ietf-l2vpn-vpls-mcast] and MVPN [RFC 6513/6514].

2.  The Internet-Standard Management Framework

   For a detailed overview of the documents that describe the current
   Internet-Standard Management Framework, please refer to section 7 of
   RFC 3410 [RFC3410].

   Managed objects are accessed via a virtual information store, termed
   the Management Information Base or MIB.  MIB objects are generally
   accessed through the Simple Network Management Protocol (SNMP).
   Objects in the MIB are defined using the mechanisms defined in the
   Structure of Management Information (SMI).  This memo specifies a MIB
   module that is compliant to the SMIv2, which is described in STD 58,
   RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580
   [RFC2580].

3.  Conventions

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
   document are to be interpreted as described in RFC 2119 [RFC2119].

4.  Summary of MIB Module

   L2L3-VPN-MCAST-MIB ontains a Textual Convention,
   L2L3VpnMcastProviderTunnelType, and a
   l2L3VpnMcastPmsiTunnelAttributeTable.  Other MIB objects ([I-D.ietf-
   l2vpn-vpls-mcast], [I-D. ietf-l3vpn-mvpn-mib]) may point to entries
   in the l2L3VpnMcastPmsiTunnelAttributeTable.

5.  Definitions

    L2L3-VPN-MCAST-MIB DEFINITIONS ::= BEGIN

    IMPORTS
        MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE,
        experimental, Unsigned32
           FROM SNMPv2-SMI

        MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP

Show full document text