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

Document Type Active Internet-Draft (bess WG)
Last updated 2017-02-20
Replaces draft-ietf-l3vpn-l2l3-vpn-mcast-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
Internet-Draft                                    Juniper Networks, Inc.
Intended status: Standards Track                              H. Tsunoda
Expires: August 25, 2017                  Tohoku Institute of Technology
                                                       February 21, 2017

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

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 common managed objects used by other MIB
   modules which are designed for monitoring and/or configuring both
   Layer 2 and Layer 3 Virtual Private Networks (VPN) that support
   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 August 25, 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

Zhang & Tsunoda          Expires August 25, 2017                [Page 1]
Internet-Draft             L2L3-VPN-MCAST MIB              February 2017

   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.  Summary of MIB Module . . . . . . . . . . . . . . . . . . . .   4
   4.  Definitions . . . . . . . . . . . . . . . . . . . . . . . . .   5
     4.1.  L2L3-VPN-MCAST-TC-MIB Object Definitions  . . . . . . . .   5
     4.2.  L2L3-VPN-MCAST-MIB Object Definitions . . . . . . . . . .   6
   5.  Security Considerations . . . . . . . . . . . . . . . . . . .  13
   6.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  14
   7.  References  . . . . . . . . . . . . . . . . . . . . . . . . .  14
     7.1.  Normative References  . . . . . . . . . . . . . . . . . .  14
     7.2.  Informative References  . . . . . . . . . . . . . . . . .  16
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  16

1.  Introduction

   [RFC7117] and [RFC6513] specify procedures for supporting multicast
   in Border Gateway Protocol/MultiProtocol Label Switching (BGP/MPLS)
   Layer 2 (L2) and Layer 3 (L3) VPN (Virtual Private Network),
   respectively.

   Multicast service in BGP/MPLS L2 and L3 VPN can be achieved by using
   various kinds of transport mechanism for forwarding a packet to all
   or a subset of Provider Edge routers (PEs) across service provider
   networks.  Such transport mechanisms are referred to as provider
   tunnels (P-tunnels).

   The signaling of P-tunnel choice is very similar for multicast in
   both L2 and L3 VPNs.  [RFC7117] and [RFC6513] describe BGP-based
   mechanisms for Virtual Private LAN Service (VPLS) and Multicast VPN
   (MVPN), respectively.  [RFC6514] defines the Provider Multicast
   Service Interface (PMSI) tunnel attribute, a BGP attribute that
   specifies information of a P-tunnel.  The PMSI tunnel attribute is
   advertised/received by PEs in BPG auto-discovery (A-D) routes.
   [RFC6513] also proposes a UDP-based signaling mechanism.

   This document defines a textual conventions (TC) that can be used to
   represent types of P-tunnels used for multicast in BGP/MPLS L2 or L3
   VPN within MIB module specifications.

   This document also describes common managed objects used by other MIB
   modules which are designed for monitoring and/or configuring both L2
   and L3 VPN that support multicast.
Show full document text