draft-ietf-bess-l2l3-vpn-mcast-mib-15.txt   draft-ietf-bess-l2l3-vpn-mcast-mib-16.txt 
Network Working Group Z. Zhang Network Working Group Z. Zhang
Internet-Draft Juniper Networks, Inc. Internet-Draft Juniper Networks, Inc.
Intended status: Standards Track H. Tsunoda Intended status: Standards Track H. Tsunoda
Expires: February 12, 2019 Tohoku Institute of Technology Expires: March 11, 2019 Tohoku Institute of Technology
August 11, 2018 September 07, 2018
L2L3 VPN Multicast MIB L2L3 VPN Multicast MIB
draft-ietf-bess-l2l3-vpn-mcast-mib-15 draft-ietf-bess-l2l3-vpn-mcast-mib-16
Abstract Abstract
This memo defines a portion of the Management Information Base (MIB) This memo defines a portion of the Management Information Base (MIB)
for use with network management protocols in the Internet community. for use with network management protocols in the Internet community.
In particular, it describes two MIB modules which will be used by In particular, it describes two MIB modules which will be used by
other MIB modules for monitoring and/or configuring Layer 2 and Layer other MIB modules for monitoring and/or configuring Layer 2 and Layer
3 Virtual Private Networks that support multicast. 3 Virtual Private Networks that support multicast.
Status of This Memo Status of This Memo
skipping to change at page 1, line 35 skipping to change at page 1, line 35
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on February 12, 2019. This Internet-Draft will expire on March 11, 2019.
Copyright Notice Copyright Notice
Copyright (c) 2018 IETF Trust and the persons identified as the Copyright (c) 2018 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
skipping to change at page 2, line 14 skipping to change at page 2, line 14
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License. described in the Simplified BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
1.1. Terminology . . . . . . . . . . . . . . . . . . . . . . . 3 1.1. Terminology . . . . . . . . . . . . . . . . . . . . . . . 3
2. The Internet-Standard Management Framework . . . . . . . . . 4 2. The Internet-Standard Management Framework . . . . . . . . . 4
3. Summary of MIB Modules . . . . . . . . . . . . . . . . . . . 4 3. Summary of MIB Modules . . . . . . . . . . . . . . . . . . . 4
4. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 4 4. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 4
4.1. L2L3-VPN-MCAST-TC-MIB Object Definitions . . . . . . . . 4 4.1. L2L3-VPN-MULTICAST-TC-MIB Object Definitions . . . . . . 4
4.2. L2L3-VPN-MCAST-MIB Object Definitions . . . . . . . . . . 9 4.2. L2L3-VPN-MULTICAST-MIB Object Definitions . . . . . . . . 9
5. Security Considerations . . . . . . . . . . . . . . . . . . . 15 5. Security Considerations . . . . . . . . . . . . . . . . . . . 15
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 16 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 16
7. Acknowledgement . . . . . . . . . . . . . . . . . . . . . . . 17 7. Acknowledgement . . . . . . . . . . . . . . . . . . . . . . . 17
8. References . . . . . . . . . . . . . . . . . . . . . . . . . 17 8. References . . . . . . . . . . . . . . . . . . . . . . . . . 17
8.1. Normative References . . . . . . . . . . . . . . . . . . 17 8.1. Normative References . . . . . . . . . . . . . . . . . . 17
8.2. Informative References . . . . . . . . . . . . . . . . . 19 8.2. Informative References . . . . . . . . . . . . . . . . . 19
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 20 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 20
1. Introduction 1. Introduction
In BGP/MPLS Virtual Private Networks (VPNs), Border Gateway Protocol In BGP/MPLS Virtual Private Networks (VPNs), Border Gateway Protocol
(BGP) is used for distributing routes and MultiProtocol Label (BGP) is used for distributing routes and MultiProtocol Label
Switching (MPLS) is used for forwarding packets accross service Switching (MPLS) is used for forwarding packets across service
provider networks. provider networks.
The procedures for supporting multicast in BGP/MPLS Layer 3 (L3) VPN The procedures for supporting multicast in BGP/MPLS Layer 3 (L3) VPN
are specified in [RFC6513]. The procedures for supporting multicast are specified in [RFC6513]. The procedures for supporting multicast
in BGP/MPLS Layer 2 (L2) VPN are specified in [RFC7117]. Throughout in BGP/MPLS Layer 2 (L2) VPN are specified in [RFC7117]. Throughout
this document, we will use the term "L2L3VpnMCast network" to mean this document, we will use the term "L2L3VpnMCast network" to mean
BGP/MPLS L2 and L3 VPN that support multicast. BGP/MPLS L2 and L3 VPN that support multicast.
L2L3VpnMCast networks use various transport mechanisms for forwarding L2L3VpnMCast networks use various transport mechanisms for forwarding
a packet to all or a subset of Provider Edge routers (PEs) across a packet to all or a subset of Provider Edge routers (PEs) across
skipping to change at page 4, line 22 skipping to change at page 4, line 22
the Management Information Base or MIB. MIB objects are generally the Management Information Base or MIB. MIB objects are generally
accessed through the Simple Network Management Protocol (SNMP). accessed through the Simple Network Management Protocol (SNMP).
Objects in the MIB are defined using the mechanisms defined in the Objects in the MIB are defined using the mechanisms defined in the
Structure of Management Information (SMI). This memo specifies a MIB Structure of Management Information (SMI). This memo specifies a MIB
module that is compliant to the SMIv2, which is described in STD 58, 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 RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580
[RFC2580]. [RFC2580].
3. Summary of MIB Modules 3. Summary of MIB Modules
This document defines two MIB modules: L2L3-VPN-MCAST-TC-MIB and This document defines two MIB modules: L2L3-VPN-MULTICAST-TC-MIB and
L2L3-VPN-MCAST-MIB. L2L3-VPN-MULTICAST-MIB.
o L2L3-VPN-MCAST-TC-MIB contains two Textual Conventions: o L2L3-VPN-MULTICAST-TC-MIB contains two Textual Conventions:
L2L3VpnMcastProviderTunnelType and L2L3VpnMcastProviderTunnelId. L2L3VpnMcastProviderTunnelType and L2L3VpnMcastProviderTunnelId.
L2L3VpnMcastProviderTunnelType provides an enumeration of the L2L3VpnMcastProviderTunnelType provides an enumeration of the
P-tunnel types. L2L3VpnMcastProviderTunnelId represents an P-tunnel types. L2L3VpnMcastProviderTunnelId represents an
identifier of a P-tunnel. identifier of a P-tunnel.
o L2L3-VPN-MCAST-MIB defines a table o L2L3-VPN-MULTICAST-MIB defines a table
l2L3VpnMcastPmsiTunnelAttributeTable. An entry in this table l2L3VpnMcastPmsiTunnelAttributeTable. An entry in this table
corresponds to the attribute information of a specific P-tunnel on corresponds to the attribute information of a specific P-tunnel on
a PE router. Entries in this table will be used by other MIB a PE router. Entries in this table will be used by other MIB
modules for monitoring and/or configuring L2L3VpnMCast network. modules for monitoring and/or configuring L2L3VpnMCast network.
The table index uniquely identifies a P-tunnel. It is composed of The table index uniquely identifies a P-tunnel. It is composed of
a type and indentifier of a P-tunnel. The table may also be used a type and identifier of a P-tunnel. The table may also be used
in conjunction with other MIBs, such as MPLS Traffic Engineering in conjunction with other MIBs, such as MPLS Traffic Engineering
MIB (MPLS-TE-STD-MIB) [RFC3812], to obtain further information MIB (MPLS-TE-STD-MIB) [RFC3812], to obtain further information
about a P-tunnel. It may also be used in conjunction with the about a P-tunnel. It may also be used in conjunction with the
Interfaces Group MIB (IF-MIB) [RFC2863] to obtain further Interfaces Group MIB (IF-MIB) [RFC2863] to obtain further
information about the interface corresponding to a P-tunnel. information about the interface corresponding to a P-tunnel.
4. Definitions 4. Definitions
4.1. L2L3-VPN-MCAST-TC-MIB Object Definitions 4.1. L2L3-VPN-MULTICAST-TC-MIB Object Definitions
L2L3-VPN-MCAST-TC-MIB DEFINITIONS ::= BEGIN L2L3-VPN-MULTICAST-TC-MIB DEFINITIONS ::= BEGIN
IMPORTS IMPORTS
MODULE-IDENTITY, mib-2 MODULE-IDENTITY, mib-2
FROM SNMPv2-SMI -- [RFC2578] FROM SNMPv2-SMI -- [RFC2578]
TEXTUAL-CONVENTION TEXTUAL-CONVENTION
FROM SNMPv2-TC; -- [RFC2579] FROM SNMPv2-TC; -- [RFC2579]
l2L3VpnMcastTCMIB MODULE-IDENTITY l2L3VpnMcastTCMIB MODULE-IDENTITY
LAST-UPDATED "201808101200Z" -- 10th August, 2018 LAST-UPDATED "201809071200Z" -- 7th September, 2018
ORGANIZATION "IETF BESS Working Group." ORGANIZATION "IETF BESS Working Group."
CONTACT-INFO CONTACT-INFO
" Zhaohui Zhang " Zhaohui Zhang
Juniper Networks, Inc. Juniper Networks, Inc.
10 Technology Park Drive 10 Technology Park Drive
Westford, MA 01886 Westford, MA 01886
USA USA
Email: zzhang@juniper.net Email: zzhang@juniper.net
Hiroshi Tsunoda Hiroshi Tsunoda
skipping to change at page 5, line 39 skipping to change at page 5, line 39
"This MIB module specifies textual conventions for "This MIB module specifies textual conventions for
Border Gateway Protocol/MultiProtocol Label Border Gateway Protocol/MultiProtocol Label
Switching Layer 2 and Layer 3 Virtual Private Networks Switching Layer 2 and Layer 3 Virtual Private Networks
that support multicast (L2L3VpnMCast networks). that support multicast (L2L3VpnMCast networks).
Copyright (C) The Internet Society (2018). Copyright (C) The Internet Society (2018).
" "
-- Revision history. -- Revision history.
REVISION "201808101200Z" -- 10th August, 2018 REVISION "201809071200Z" -- 7th September, 2018
DESCRIPTION DESCRIPTION
"Initial version, published as RFC XXXX." "Initial version, published as RFC XXXX."
-- RFC Ed.: replace XXXX with actual RFC number and remove this note -- RFC Ed.: replace XXXX with actual RFC number and remove this note
::= { mib-2 AAAA } ::= { mib-2 AAAA }
-- IANA Reg.: Please assign a value for "AAAA" under the -- IANA Reg.: Please assign a value for "AAAA" under the
-- 'mib-2' subtree and record the assignment in the SMI -- 'mib-2' subtree and record the assignment in the SMI
-- Numbers registry. -- Numbers registry.
skipping to change at page 9, line 5 skipping to change at page 9, line 5
REFERENCE REFERENCE
"RFC6514, Section 5 "RFC6514, Section 5
RFC4875, Section 19.1 RFC4875, Section 19.1
RFC6388, Section 2.2 and 3.2 RFC6388, Section 2.2 and 3.2
RFC7524, Section 14.1 RFC7524, Section 14.1
" "
SYNTAX OCTET STRING ( SIZE (0|4|8|12|16|17|24|29|32) ) SYNTAX OCTET STRING ( SIZE (0|4|8|12|16|17|24|29|32) )
END END
4.2. L2L3-VPN-MCAST-MIB Object Definitions 4.2. L2L3-VPN-MULTICAST-MIB Object Definitions
L2L3-VPN-MCAST-MIB DEFINITIONS ::= BEGIN L2L3-VPN-MULTICAST-MIB DEFINITIONS ::= BEGIN
IMPORTS IMPORTS
MODULE-IDENTITY, OBJECT-TYPE, mib-2, zeroDotZero MODULE-IDENTITY, OBJECT-TYPE, mib-2, zeroDotZero
FROM SNMPv2-SMI -- [RFC2578] FROM SNMPv2-SMI -- [RFC2578]
MODULE-COMPLIANCE, OBJECT-GROUP MODULE-COMPLIANCE, OBJECT-GROUP
FROM SNMPv2-CONF -- [RFC2580] FROM SNMPv2-CONF -- [RFC2580]
RowPointer RowPointer
FROM SNMPv2-TC -- [RFC2579] FROM SNMPv2-TC -- [RFC2579]
MplsLabel MplsLabel
FROM MPLS-TC-STD-MIB -- [RFC3811] FROM MPLS-TC-STD-MIB -- [RFC3811]
L2L3VpnMcastProviderTunnelType, L2L3VpnMcastProviderTunnelType,
L2L3VpnMcastProviderTunnelId L2L3VpnMcastProviderTunnelId
FROM L2L3-VPN-MCAST-TC-MIB; -- [RFCXXXX] FROM L2L3-VPN-MULTICAST-TC-MIB; -- [RFCXXXX]
-- RFC Ed.: replace XXXX with actual RFC number and remove this note -- RFC Ed.: replace XXXX with actual RFC number and remove this note
l2L3VpnMcastMIB MODULE-IDENTITY l2L3VpnMcastMIB MODULE-IDENTITY
LAST-UPDATED "201808101200Z" -- 10th August, 2018 LAST-UPDATED "201809071200Z" -- 7th September, 2018
ORGANIZATION "IETF BESS Working Group." ORGANIZATION "IETF BESS Working Group."
CONTACT-INFO CONTACT-INFO
" Zhaohui Zhang " Zhaohui Zhang
Juniper Networks, Inc. Juniper Networks, Inc.
10 Technology Park Drive 10 Technology Park Drive
Westford, MA 01886 Westford, MA 01886
USA USA
Email: zzhang@juniper.net Email: zzhang@juniper.net
Hiroshi Tsunoda Hiroshi Tsunoda
skipping to change at page 10, line 17 skipping to change at page 10, line 17
information of the provider tunnels (P-tunnels) on a PE router. information of the provider tunnels (P-tunnels) on a PE router.
This MIB module will be used by other MIB modules designed for This MIB module will be used by other MIB modules designed for
monitoring and/or configuring Border Gateway monitoring and/or configuring Border Gateway
Protocol/MultiProtocol Label Switching Protocol/MultiProtocol Label Switching
Layer 2 and Layer 3 Virtual Private Layer 2 and Layer 3 Virtual Private
Network that support multicast (L2L3VpnMCast network). Network that support multicast (L2L3VpnMCast network).
Copyright (C) The Internet Society (2018). Copyright (C) The Internet Society (2018).
" "
-- Revision history. -- Revision history.
REVISION "201808101200Z" -- 10th August, 2018 REVISION "201809071200Z" -- 7th September, 2018
DESCRIPTION DESCRIPTION
"Initial version, published as RFC XXXX." "Initial version, published as RFC XXXX."
-- RFC Ed.: replace XXXX with actual RFC number and remove this note -- RFC Ed.: replace XXXX with actual RFC number and remove this note
::= { mib-2 BBBB } ::= { mib-2 BBBB }
-- IANA Reg.: Please assign a value for "BBBB" under the -- IANA Reg.: Please assign a value for "BBBB" under the
-- 'mib-2' subtree and record the assignment in the SMI -- 'mib-2' subtree and record the assignment in the SMI
-- Numbers registry. -- Numbers registry.
skipping to change at page 14, line 43 skipping to change at page 14, line 43
::= { l2L3VpnMcastConformance 1 } ::= { l2L3VpnMcastConformance 1 }
l2L3VpnMcastGroups OBJECT IDENTIFIER l2L3VpnMcastGroups OBJECT IDENTIFIER
::= { l2L3VpnMcastConformance 2 } ::= { l2L3VpnMcastConformance 2 }
-- Compliance Statements -- Compliance Statements
l2L3VpnMcastCoreCompliance MODULE-COMPLIANCE l2L3VpnMcastCoreCompliance MODULE-COMPLIANCE
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The core compliance statement for SNMP entities "The core compliance statement for SNMP entities
which implement the L2L3-VPN-MCAST-MIB Module." which implement the L2L3-VPN-MULTICAST-MIB Module."
MODULE -- this module MODULE -- this module
MANDATORY-GROUPS { MANDATORY-GROUPS {
l2L3VpnMcastCoreGroup l2L3VpnMcastCoreGroup
} }
::= { l2L3VpnMcastCompliances 1 } ::= { l2L3VpnMcastCompliances 1 }
l2L3VpnMcastFullCompliance MODULE-COMPLIANCE l2L3VpnMcastFullCompliance MODULE-COMPLIANCE
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The full compliance statement for SNMP entities "The full compliance statement for SNMP entities
which implement the L2L3-VPN-MCAST-MIB Module." which implement the L2L3-VPN-MULTICAST-MIB Module."
MODULE -- this module MODULE -- this module
MANDATORY-GROUPS { MANDATORY-GROUPS {
l2L3VpnMcastCoreGroup, l2L3VpnMcastCoreGroup,
l2L3VpnMcastOptionalGroup l2L3VpnMcastOptionalGroup
} }
::= { l2L3VpnMcastCompliances 2 } ::= { l2L3VpnMcastCompliances 2 }
-- units of conformance -- units of conformance
skipping to change at page 17, line 5 skipping to change at page 17, line 5
responsibility to ensure that the SNMP entity giving access to an responsibility to ensure that the SNMP entity giving access to an
instance of this MIB module is properly configured to give access to instance of this MIB module is properly configured to give access to
the objects only to those principals (users) that have legitimate the objects only to those principals (users) that have legitimate
rights to indeed GET or SET (change/create/delete) them. rights to indeed GET or SET (change/create/delete) them.
6. IANA Considerations 6. IANA Considerations
The MIB module in this document uses the following IANA-assigned The MIB module in this document uses the following IANA-assigned
OBJECT IDENTIFIER values recorded in the SMI Numbers registry: OBJECT IDENTIFIER values recorded in the SMI Numbers registry:
Descriptor OBJECT IDENTIFIER value Name Description OBJECT IDENTIFIER value
---------- ----------------------- ----------------- -------------------------- ----------------------
l2L3VpnMcastTCMIB { mib-2 AAAA } l2L3VpnMcastTCMIB L2L3-VPN-MULTICAST-TC-MIB { mib-2 AAAA }
l2L3VpnMcastMIB { mib-2 BBBB } l2L3VpnMcastMIB L2L3-VPN-MULTICAST-MIB { mib-2 BBBB }
Editor's Note (to be removed prior to publication): the IANA is Editor's Note (to be removed prior to publication): the IANA is
requested to assign a value for "AAAA" and "BBBB" under the 'mib-2' requested to assign a value for "AAAA" and "BBBB" under the 'mib-2'
subtree and to record the assignment in the SMI Numbers registry. subtree and to record the assignment in the SMI Numbers registry.
When the assignment has been made, the RFC Editor is asked to replace When the assignment has been made, the RFC Editor is asked to replace
"AAAA" and "BBBB" (here and in the MIB module) with the assigned "AAAA" and "BBBB" (here and in the MIB module) with the assigned
value and to remove this note. value and to remove this note.
7. Acknowledgement 7. Acknowledgement
 End of changes. 21 change blocks. 
27 lines changed or deleted 27 lines changed or added

This html diff was produced by rfcdiff 1.47. The latest version is available from http://tools.ietf.org/tools/rfcdiff/