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

Document Type Active Internet-Draft (bess WG)
Last updated 2017-06-06
Replaces draft-ietf-l3vpn-mvpn-mib
Stream IETF
Intended RFC status Proposed Standard
Formats plain text pdf html bibtex
Stream WG state WG Consensus: Waiting for Write-Up
Document shepherd Mach Chen
IESG IESG state I-D Exists
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to "Mach Chen" <mach.chen@huawei.com>
Network Working Group                                      Z. Zhang, Ed.
Internet-Draft                                                   Juniper
Intended status: Standards Track                                 S. Asif
Expires: December 8, 2017                                           AT&T
                                                                A. Green
                                                                      BT
                                                           S. Gulranjani
                                                                   Cisco
                                                                 P. Jain
                                                          Alcatel-Lucent
                                                         H. Tsunoda, Ed.
                                          Tohoku Institute of Technology
                                                           June 06, 2017

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

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 MVPN, Multicast in MultiProtocol Label Switching/Border
   Gateway Protocol (MPLS/BGP) IP Virtual Private Networks (VPNs) 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 December 8, 2017.

Zhang, et al.           Expires December 8, 2017                [Page 1]
Internet-Draft             L3VPN Multicast MIB                 June 2017

Copyright Notice

   Copyright (c) 2017 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
   described in the Simplified BSD License.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
     1.1.  Terminology . . . . . . . . . . . . . . . . . . . . . . .   3
   2.  The Internet-Standard Management Framework  . . . . . . . . .   4
   3.  MCAST-VPN-MIB . . . . . . . . . . . . . . . . . . . . . . . .   4
     3.1.  Summary of MIB Module . . . . . . . . . . . . . . . . . .   4
     3.2.  MIB Module Definitions  . . . . . . . . . . . . . . . . .   7
   4.  Security Considerations . . . . . . . . . . . . . . . . . . .  36
   5.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  37
   6.  Acknowledgement . . . . . . . . . . . . . . . . . . . . . . .  37
   7.  References  . . . . . . . . . . . . . . . . . . . . . . . . .  37
     7.1.  Normative References  . . . . . . . . . . . . . . . . . .  37
     7.2.  Informative References  . . . . . . . . . . . . . . . . .  39
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  39

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 Network (VPN).  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) exchange the VPN customer multicast
   (C-multicast) routing information with each other.  In [RFC6513], two
   basic methods for exchanging C-multicast routing information are
   defined (1) Protocol Independent Multicast (PIM) [RFC4601] and (2)
   BGP.

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

Zhang, et al.           Expires December 8, 2017                [Page 2]
Show full document text