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

Document Type Active Internet-Draft (bess WG)
Last updated 2017-10-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: April 23, 2018                   Tohoku Institute of Technology
                                                        October 20, 2017

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

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 two MIB modules which will be used by
   other MIB modules for monitoring and/or configuring Layer 2 and Layer
   3 Virtual Private Networks 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 April 23, 2018.

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 April 23, 2018                 [Page 1]
Internet-Draft             L2L3-VPN-MCAST MIB               October 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  . . . . . . . . .   3
   3.  Summary of MIB Modules  . . . . . . . . . . . . . . . . . . .   4
   4.  Definitions . . . . . . . . . . . . . . . . . . . . . . . . .   4
     4.1.  L2L3-VPN-MCAST-TC-MIB Object Definitions  . . . . . . . .   4
     4.2.  L2L3-VPN-MCAST-MIB Object Definitions . . . . . . . . . .   9
   5.  Security Considerations . . . . . . . . . . . . . . . . . . .  17
   6.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  18
   7.  References  . . . . . . . . . . . . . . . . . . . . . . . . .  18
     7.1.  Normative References  . . . . . . . . . . . . . . . . . .  18
     7.2.  Informative References  . . . . . . . . . . . . . . . . .  20
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  21

1.  Introduction

   In BGP/MPLS Virtual Private Networks (VPNs), Border Gateway Protocol
   (BGP) is used for distributing routes and MultiProtocol Label
   Switching (MPLS) is used for forwarding packets accross service
   provider networks.

   The procedures for supporting multicast in BGP/MPLS Layer 3 (L3) VPN
   are specified in [RFC6513].  The procedures for supporting multicast
   in BGP/MPLS Layer 2 (L2) VPN are specified in [RFC7117].  Throughout
   this document, we will use the term "L2L3VpnMCast network" to mean
   BGP/MPLS L2 and L3 VPN that support multicast.

   L2L3VpnMCast networks use various transport mechanisms for forwarding
   a packet to all or a subset of Provider Edge routers (PEs) across
   service provider networks.  These transport mechanisms are abstracted
   as provider tunnels (P-tunnels).  The type of a P-tunnel indicates
   the type of the tunneling technology used to establish the P-tunnel.
   The syntax and semantics of an identifier of the established are
   determined by the type of the P-tunnel [RFC6514].  The P-tunnel type
   and the P-tunnel identifier together identify a P-tunnel.

   A BGP attribute that specifies information of a P-tunnel is called
   Provider Multicast Service Interface (PMSI) tunnel attribute.  The
   PMSI tunnel attribute is advertised/received by PEs in BGP auto-
   discovery (A-D) routes.  [RFC6514] defines the format of a PMSI
   tunnel attribute.  The P-tunnel type and the P-tunnel identifier are
Show full document text