BGP/MPLS Layer 3 VPN Multicast Management Information Base
draft-ietf-bess-mvpn-mib-10

Document Type Active Internet-Draft (bess WG)
Last updated 2018-08-20 (latest revision 2018-08-10)
Replaces draft-ietf-l3vpn-mvpn-mib
Stream IETF
Intended RFC status Proposed Standard
Formats plain text pdf html bibtex
Stream WG state Submitted to IESG for Publication
Document shepherd Mach Chen
Shepherd write-up Show (last changed 2018-08-08)
IESG IESG state In Last Call (ends 2018-09-03)
Consensus Boilerplate Unknown
Telechat date
Responsible AD Martin Vigoureux
Send notices to "Mach Chen" <mach.chen@huawei.com>
IANA IANA review state IANA - Review Needed
IANA action state None
Network Working Group                                         H. Tsunoda
Internet-Draft                            Tohoku Institute of Technology
Intended status: Standards Track                         August 11, 2018
Expires: February 12, 2019

       BGP/MPLS Layer 3 VPN Multicast Management Information Base
                      draft-ietf-bess-mvpn-mib-10

Abstract

   This memo defines a portion of the Management Information Base (MIB)
   for use with network management protocols in the Internet community.
   In particular, it describes managed objects to configure and/or
   monitor Multicast communication over IP Virtual Private Networks
   (VPNs) supported by MultiProtocol Label Switching/Border Gateway
   Protcol (MPLS/BGP) on a Provider Edge router.

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 February 12, 2019.

Copyright Notice

   Copyright (c) 2018 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

Tsunoda                 Expires February 12, 2019               [Page 1]
Internet-Draft             L3VPN Multicast MIB               August 2018

   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
     1.1.  Terminology . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  The Internet-Standard Management Framework  . . . . . . . . .   3
   3.  MCAST-VPN-MIB . . . . . . . . . . . . . . . . . . . . . . . .   4
     3.1.  Summary of MIB Module . . . . . . . . . . . . . . . . . .   4
     3.2.  MIB Module Definitions  . . . . . . . . . . . . . . . . .   5
   4.  Security Considerations . . . . . . . . . . . . . . . . . . .  50
   5.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  53
   6.  Acknowledgement . . . . . . . . . . . . . . . . . . . . . . .  53
   7.  References  . . . . . . . . . . . . . . . . . . . . . . . . .  53
     7.1.  Normative References  . . . . . . . . . . . . . . . . . .  54
     7.2.  Informative References  . . . . . . . . . . . . . . . . .  56
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .  56

1.  Introduction

   [RFC6513], [RFC6514], and [RFC6625] specify procedures for supporting
   multicast in Border Gateway Protocol/MultiProtocol Label Switching
   (BGP/MPLS) Layer 3 (IP) Virtual Private Networks (VPNs).  Throughout
   this document, we will use the term "Multicast VPN" (MVPN) [RFC6513]
   to refer to a BGP/MPLS IP VPN that supports multicast.

   Provider Edge routers (PEs) attaching to a particular MVPN exchange
   customer multicast (C-multicast) routing information with neighboring
   PEs.  In [RFC6513], two basic methods for exchanging C-multicast
   routing information are defined (1) Protocol Independent Multicast
   (PIM) [RFC7761] and (2) BGP.

   In the rest of this document we will use the term "PIM-MVPN" to refer
   to the case where PIM is used for exchanging C-multicast routing
   information, and "BGP-MVPN" to refer to the case where BGP is used
   for exchanging C-multicast routing information.

   This document describes managed objects to configure and/or monitor
   MVPNs.  Most of the managed objects are common to both PIM-MVPN and
   BGP-MVPN, and some managed objects are BGP-MVPN specific.

1.1.  Terminology

   This document adopts the definitions, acronyms and mechanisms
   described in [RFC4364], [RFC6513], and [RFC6514].  Familiarity with
   Multicast, MPLS, Layer 3 (L3) VPN, MVPN concepts and/or mechanisms is

Tsunoda                 Expires February 12, 2019               [Page 2]
Internet-Draft             L3VPN Multicast MIB               August 2018

   assumed.  Some terms specifically related to this document are
   explained below.

   An MVPN can be realized by using various kinds of transport
   mechanisms for forwarding a packet to all or a subset of PEs across
Show full document text