< draft-ietf-bess-l2l3-vpn-mcast-mib-10.txt   draft-ietf-bess-l2l3-vpn-mcast-mib-11.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 28, 2018 Tohoku Institute of Technology Expires: April 23, 2018 Tohoku Institute of Technology
August 27, 2017 October 20, 2017
L2L3 VPN Multicast MIB L2L3 VPN Multicast MIB
draft-ietf-bess-l2l3-vpn-mcast-mib-10 draft-ietf-bess-l2l3-vpn-mcast-mib-11
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 28, 2018. This Internet-Draft will expire on April 23, 2018.
Copyright Notice Copyright Notice
Copyright (c) 2017 IETF Trust and the persons identified as the Copyright (c) 2017 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
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
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 . . . . . . . . . 3
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 . . . . . . . . 5 4.1. L2L3-VPN-MCAST-TC-MIB Object Definitions . . . . . . . . 4
4.2. L2L3-VPN-MCAST-MIB Object Definitions . . . . . . . . . . 9 4.2. L2L3-VPN-MCAST-MIB Object Definitions . . . . . . . . . . 9
5. Security Considerations . . . . . . . . . . . . . . . . . . . 16 5. Security Considerations . . . . . . . . . . . . . . . . . . . 17
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 17 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 18
7. References . . . . . . . . . . . . . . . . . . . . . . . . . 17 7. References . . . . . . . . . . . . . . . . . . . . . . . . . 18
7.1. Normative References . . . . . . . . . . . . . . . . . . 17 7.1. Normative References . . . . . . . . . . . . . . . . . . 18
7.2. Informative References . . . . . . . . . . . . . . . . . 20 7.2. Informative References . . . . . . . . . . . . . . . . . 20
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 20 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 21
1. Introduction 1. Introduction
In BGP/MPLS Virtual Private Networks (VPN), 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 accross 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" to mean BGP/MPLS this document, we will use the term "L2L3VpnMCast network" to mean
L2 and L3 VPN that support multicast. BGP/MPLS L2 and L3 VPN that support multicast.
This document describes textual conventions (TCs) and common managed
objects (MOs) which will be used by other Management Information Base
(MIB) modules for monitoring and/or configuring L2L3VpnMCast.
L2L3VpnMCast can be achieved by using various kinds of transport
mechanisms 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). TCs and
MOs defined in this document will be used by other MIB modules for
monitoring and/or configuring both L2 and L3 VPNs that support
multicast.
There are two types of signaling mechanisms of P-tunnel choice: BGP-
based and UDP-based [RFC6513]. BGP-based mechanisms for Virtual
Private LAN Service and Multicast VPN are described in [RFC7117] and
[RFC6513], respectively. In [RFC6513], a UDP-based signaling L2L3VpnMCast networks use various transport mechanisms for forwarding
mechanism is also specified. 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 A BGP attribute that specifies information of a P-tunnel is called
Provider Multicast Service Interface (PMSI) tunnel attribute. The Provider Multicast Service Interface (PMSI) tunnel attribute. The
PMSI tunnel attribute is advertised/received by PEs in BGP auto- PMSI tunnel attribute is advertised/received by PEs in BGP auto-
discovery (A-D) routes. [RFC6514] defines the format of a PMSI discovery (A-D) routes. [RFC6514] defines the format of a PMSI
tunnel attribute. tunnel attribute. The P-tunnel type and the P-tunnel identifier are
in a PMSI tunnel attribute.
This document describes textual conventions (TCs) and common managed
objects (MOs) which will be used by other Management Information Base
(MIB) modules for monitoring and/or configuring L2L3VpnMCast network.
This document defines two TCs to represent This document defines two TCs to represent
(a) the tunnel type of a P-tunnel and (a) the type of a P-tunnel and
(b) the identifier of a P-tunnel (b) the identifier of a P-tunnel
respectively. respectively.
This document also describes common MOs that provide the information The document also defines MOs that will provide the information
in a PMSI tunnel attribute and corresponding tunnel information to contained in a PMSI tunnel attribute and corresponding P-tunnel
other MIB modules. information.
1.1. Terminology 1.1. Terminology
This document adopts the definitions, acronyms and mechanisms This document adopts the definitions, acronyms and mechanisms
described in [RFC6513] [RFC6514] [RFC7117] and other documents that described in [RFC6513] [RFC6514] [RFC7117] and other documents that
they refer to. Familiarity with Multicast, MPLS, Layer 3 VPN, they refer to. Familiarity with Multicast, MPLS, Layer 3 VPN,
Multicast VPN concepts and/or mechanisms is assumed. Some terms Multicast VPN concepts and/or mechanisms is assumed. Some terms
specifically related to this document are explained below. specifically related to this document are explained below.
"Provider Multicast Service Interface (PMSI)" [RFC6513] is a "Provider Multicast Service Interface (PMSI)" [RFC6513] is a
skipping to change at page 4, line 35 skipping to change at page 4, line 29
o L2L3-VPN-MCAST-TC-MIB contains two Textual Conventions: o L2L3-VPN-MCAST-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-MCAST-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. The table modules for monitoring and/or configuring L2L3VpnMCast network.
index uniquely identifies a tunnel. It is composed of a tunnel The table index uniquely identifies a P-tunnel. It is composed of
type and a tunnel indentifier. The table may also be used in a type and indentifier of a P-tunnel. The table may also be used
conjunction with other MIBs, such as MPLS Traffic Engineering MIB in conjunction with other MIBs, such as MPLS Traffic Engineering
(MPLS-TE-STD-MIB) [RFC3812], to obtain further information of a MIB (MPLS-TE-STD-MIB) [RFC3812], to obtain further information
tunnel by following the row pointer of the corresponding tunnel's about a P-tunnel. It may also be used in conjunction with the
row in this table. It may also be used in conjunction with
Interfaces Group MIB (IF-MIB) [RFC2863] to obtain further Interfaces Group MIB (IF-MIB) [RFC2863] to obtain further
information of the interface corresponding to the tunnel by information about the interface corresponding to a P-tunnel.
following the row pointer of the corresponding tunnel's row in
this table.
4. Definitions 4. Definitions
4.1. L2L3-VPN-MCAST-TC-MIB Object Definitions 4.1. L2L3-VPN-MCAST-TC-MIB Object Definitions
L2L3-VPN-MCAST-TC-MIB DEFINITIONS ::= BEGIN L2L3-VPN-MCAST-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 "201708211200Z" -- 21th August, 2017 LAST-UPDATED "201710041200Z" -- 4th October, 2017
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 26
Taihaku-ku, Sendai, 982-8577 Taihaku-ku, Sendai, 982-8577
Japan Japan
Email: tsuno@m.ieice.org Email: tsuno@m.ieice.org
Comments and discussion to bess@ietf.org Comments and discussion to bess@ietf.org
" "
DESCRIPTION DESCRIPTION
"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 Network Switching Layer 2 and Layer 3 Virtual Private Network
that support multicast (L2L3VpnMCast). that support multicast (L2L3VpnMCast network).
Copyright (C) The Internet Society (2017). Copyright (C) The Internet Society (2017).
" "
-- Revision history. -- Revision history.
REVISION "201708211200Z" -- 21th August, 2017 REVISION "201710041200Z" -- 4th October, 2017
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.
-- RFC Ed.: When the above assignment has been made, please -- RFC Ed.: When the above assignment has been made, please
-- remove the above note -- remove the above note
-- replace "AAAA" here with the assigned value and -- replace "AAAA" here with the assigned value and
-- remove this note. -- remove this note.
-- Textual convention -- Textual convention
L2L3VpnMcastProviderTunnelType ::= TEXTUAL-CONVENTION L2L3VpnMcastProviderTunnelType ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This textual convention enumerates values "This textual convention enumerates values
representing the type of a provider tunnel (P-tunnel) representing the type of a provider tunnel (P-tunnel)
used for L2L3VpnMCast. used for L2L3VpnMCast network.
These labeled numbers are aligned with the definition These labeled numbers are aligned with the definition
of Tunnel types in Section 5 of [RFC6514] and of Tunnel types in Section 5 of [RFC6514] and
Section 14.1 of [RFC7524]. Section 14.1 of [RFC7524].
The enumerated values and the corresponding tunnel type The enumerated values and the corresponding P-tunnel type
are as follows: are as follows:
noTunnelInfo (0) : no tunnel information present noTunnelInfo (0) : no tunnel information present
[RFC6514]
rsvpP2mp (1) : RSVP-TE P2MP LSP [RFC4875] rsvpP2mp (1) : RSVP-TE P2MP LSP [RFC4875]
ldpP2mp (2) : mLDP P2MP LSP [RFC6388] ldpP2mp (2) : mLDP P2MP LSP [RFC6388]
pimSsm (3) : PIM-SSM Tree [RFC7761] pimSsm (3) : PIM-SSM Tree [RFC7761]
pimAsm (4) : PIM-SM Tree [RFC7761] pimAsm (4) : PIM-SM Tree [RFC7761]
pimBidir (5) : BIDIR-PIM Tree [RFC5015] pimBidir (5) : BIDIR-PIM Tree [RFC5015]
ingressReplication (6) : Ingress Replication [RFC6513] ingressReplication (6) : Ingress Replication [RFC6513]
ldpMp2mp (7) : mLDP MP2MP LSP [RFC6388] ldpMp2mp (7) : mLDP MP2MP LSP [RFC6388]
transportTunnel (8) : Transport Tunnel [RFC7524] transportTunnel (8) : Transport Tunnel [RFC7524]
These numbers are registered at IANA. These numbers are registered at IANA.
A current list of assignments can be found at A current list of assignments can be found at
<https://www.iana.org/assignments/bgp-parameters/ <https://www.iana.org/assignments/bgp-parameters/
bgp-parameters.xhtml#pmsi-tunnel-types>. bgp-parameters.xhtml#pmsi-tunnel-types>.
" "
REFERENCE REFERENCE
"RFC4875 "RFC4875
RFC5015
RFC6388 RFC6388
RFC6513 RFC6513
RFC6514, Section 5 RFC6514, Section 5
RFC7385 RFC7385
RFC7524, Section 14.1 RFC7524, Section 14.1
RFC7761 RFC7761
" "
SYNTAX INTEGER SYNTAX INTEGER
{ {
noTunnelInfo (0), noTunnelInfo (0),
rsvpP2mp (1), rsvpP2mp (1),
ldpP2mp (2), ldpP2mp (2),
pimSsm (3), pimSsm (3),
pimAsm (4), pimAsm (4),
pimBidir (5), pimBidir (5),
ingressReplication (6), ingressReplication (6),
ldpMp2mp (7), ldpMp2mp (7),
skipping to change at page 7, line 49 skipping to change at page 7, line 48
noTunnelInfo (No tunnel information) 0 0 noTunnelInfo (No tunnel information) 0 0
rsvpP2mp (RSVP-TE P2MP LSP) 12 24 rsvpP2mp (RSVP-TE P2MP LSP) 12 24
ldpP2mp (mLDP P2MP LSP) 17 29 ldpP2mp (mLDP P2MP LSP) 17 29
pimSsm (PIM-SSM Tree) 8 32 pimSsm (PIM-SSM Tree) 8 32
pimAsm (PIM-SM Tree) 8 32 pimAsm (PIM-SM Tree) 8 32
pimBidir (BIDIR-PIM Tree) 8 32 pimBidir (BIDIR-PIM Tree) 8 32
ingressReplication (Ingress Replication) 4 16 ingressReplication (Ingress Replication) 4 16
ldpMp2mp (mLDP MP2MP LSP) 17 29 ldpMp2mp (mLDP MP2MP LSP) 17 29
transportTunnel (Transport Tunnel) 8 32 transportTunnel (Transport Tunnel) 8 32
A L2L3VpnMcastProviderTunnelType object of value Tunnel type is set to 'No tunnel information present'
noTunnelInfo(0) indicates that the corresponding when the PMSI Tunnel attribute carries no tunnel
Provider Multicast Service Interface (PMSI) Tunnel information (no Tunnel Identifier).
attribute does not have a Tunnel Identifier.
The value of the corresponding L2L3VpnMcastProviderTunnelId The value of the corresponding L2L3VpnMcastProviderTunnelId
object will be a string of length zero. object will be a string of length zero.
When the L2L3VpnMcastProviderTunnelType object is of value For tunnel type rsvpP2mp(1), the corresponding Tunnel
rsvpP2mp(1), the corresponding Tunnel Identifier is composed of Identifier is composed of Extended Tunnel ID (4 octets in IPv4,
Extended Tunnel ID (4 octets in IPv4, 16 octets in IPv6), 16 octets in IPv6), Reserved (2 octets), Tunnel ID (2 octets),
Reserved (2 octets), Tunnel ID (2 octets), and and P2MP ID (4 octets).
P2MP ID (4 octets).
The size of the corresponding L2L3VpnMcastProviderTunnelId The size of the corresponding L2L3VpnMcastProviderTunnelId
object will be 12 octets in IPv4 and 24 octets in IPv6. object will be 12 octets in IPv4 and 24 octets in IPv6.
When the L2L3VpnMcastProviderTunnelType object is of value For tunnel type ldpP2mp(2), the corresponding Tunnel Identifier
ldpP2mp(2), the corresponding Tunnel Identifier is P2MP is the P2MP Forwarding Equivalence Class (FEC) Element
Forwarding Equivalence Class (FEC) Element [RFC6388]. [RFC6388]. The size of the corresponding
The size of the corresponding L2L3VpnMcastProviderTunnelId L2L3VpnMcastProviderTunnelId object will be 17 octets
object will be 17 octets in IPv4 and 29 octets in IPv6 in IPv4 and 29 octets in IPv6.
When the L2L3VpnMcastProviderTunnelType object is of value For tunnel type pimSsm(3), PimAsm(4), and PimBidir(5), the
pimSsm(3), PimAsm(4), or PimBidir(5), the corresponding corresponding Tunnel Identifier is composed of the source IP
Tunnel Identifier is composed of the source IP address address and the group IP address.
and the group IP address.
The size of the corresponding L2L3VpnMcastProviderTunnelId The size of the corresponding L2L3VpnMcastProviderTunnelId
object will be 8 octets in IPv4 and 32 octets in IPv6. object will be 8 octets in IPv4 and 32 octets in IPv6.
When the L2L3VpnMcastProviderTunnelType object is of value For tunnel type ingressReplication(6), the Tunnel Identifier is
ingressReplication(6), the Tunnel Identifier is
the unicast tunnel endpoint IP address of the local PE. the unicast tunnel endpoint IP address of the local PE.
The size of the corresponding L2L3VpnMcastProviderTunnelId The size of the corresponding L2L3VpnMcastProviderTunnelId
object will be 4 octets in IPv4 and 16 octets in IPv6. object will be 4 octets in IPv4 and 16 octets in IPv6.
When the L2L3VpnMcastProviderTunnelType object is of value For tunnel type ldpMp2mp(7), the Tunnel Identifier is
ldpMp2mp(7), the Tunnel Identifier is MP2MP FEC Element MP2MP FEC Element [RFC6388].
[RFC6388].
The size of the corresponding L2L3VpnMcastProviderTunnelId The size of the corresponding L2L3VpnMcastProviderTunnelId
object will be 17 octets in IPv4 and 29 octets in IPv6. object will be 17 octets in IPv4 and 29 octets in IPv6.
When the L2L3VpnMcastProviderTunnelType object is of value For tunnel type transportTunnel(8), the Tunnel Identifier
transportTunnel(8), the Tunnel Identifier is a tuple of is a tuple of Source PE Address and Local Number,
Source PE Address and Local Number, which is a number which is a number that is unique to the Source PE [RFC7524].
that is unique to the Source PE [RFC7524].
Both Source PE Address and Local Number are 4 octets in IPv4 Both Source PE Address and Local Number are 4 octets in IPv4
and 16 octets in IPv6. and 16 octets in IPv6.
The size of the corresponding L2L3VpnMcastProviderTunnelId The size of the corresponding L2L3VpnMcastProviderTunnelId
object will be 8 octets in IPv4 and 32 octets in IPv6. object will be 8 octets in IPv4 and 32 octets in IPv6.
" "
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
skipping to change at page 9, line 36 skipping to change at page 9, line 29
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-MCAST-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 "201708211200Z" -- 21th August, 2017 LAST-UPDATED "201710041200Z" -- 4th October, 2017
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 4 skipping to change at page 9, line 45
Westford, MA 01886 Westford, MA 01886
USA USA
Email: zzhang@juniper.net Email: zzhang@juniper.net
Hiroshi Tsunoda Hiroshi Tsunoda
Tohoku Institute of Technology Tohoku Institute of Technology
35-1, Yagiyama Kasumi-cho 35-1, Yagiyama Kasumi-cho
Taihaku-ku, Sendai, 982-8577 Taihaku-ku, Sendai, 982-8577
Japan Japan
Email: tsuno@m.ieice.org Email: tsuno@m.ieice.org
Comments and discussion to bess@ietf.org Comments and discussion to bess@ietf.org
" "
DESCRIPTION DESCRIPTION
"This MIB module defines a table representing the attribute "This MIB module defines a table representing the attribute
information of 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 that support multicast (L2L3VpnMCast network).
Copyright (C) The Internet Society (2017). Copyright (C) The Internet Society (2017).
" "
-- Revision history. -- Revision history.
REVISION "201708211200Z" -- 21th August, 2017 REVISION "201710041200Z" -- 4th October, 2017
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 11, line 4 skipping to change at page 11, line 8
-- Table of PMSI Tunnel Attributes -- Table of PMSI Tunnel Attributes
l2L3VpnMcastPmsiTunnelAttributeTable OBJECT-TYPE l2L3VpnMcastPmsiTunnelAttributeTable OBJECT-TYPE
SYNTAX SEQUENCE OF L2L3VpnMcastPmsiTunnelAttributeEntry SYNTAX SEQUENCE OF L2L3VpnMcastPmsiTunnelAttributeEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An entry in this table corresponds to "An entry in this table corresponds to
the attribute information of a specific the attribute information of a specific
P-tunnel on a PE router. P-tunnel on a PE router.
A part of attributes correspond to fields in A part of attributes correspond to fields in
a Provider Multicast Service Interface (PMSI) Tunnel a Provider Multicast Service Interface (PMSI) Tunnel
attribute advertised and received by a PE router. attribute advertised and received by a PE router.
The entries will be referred to by other MIB modules The entries will be referred to by other MIB modules
for monitoring and/or configuring L2L3VpnMCast. for monitoring and/or configuring L2L3VpnMCast network.
" "
REFERENCE REFERENCE
"RFC6514, Section 5" "RFC6514, Section 5"
::= { l2L3VpnMcastStates 1 } ::= { l2L3VpnMcastStates 1 }
l2L3VpnMcastPmsiTunnelAttributeEntry OBJECT-TYPE l2L3VpnMcastPmsiTunnelAttributeEntry OBJECT-TYPE
SYNTAX L2L3VpnMcastPmsiTunnelAttributeEntry SYNTAX L2L3VpnMcastPmsiTunnelAttributeEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
skipping to change at page 11, line 33 skipping to change at page 11, line 36
REFERENCE REFERENCE
"RFC6514, Section 5" "RFC6514, Section 5"
INDEX { INDEX {
l2L3VpnMcastPmsiTunnelAttributeType, l2L3VpnMcastPmsiTunnelAttributeType,
l2L3VpnMcastPmsiTunnelAttributeId l2L3VpnMcastPmsiTunnelAttributeId
} }
::= { l2L3VpnMcastPmsiTunnelAttributeTable 1 } ::= { l2L3VpnMcastPmsiTunnelAttributeTable 1 }
L2L3VpnMcastPmsiTunnelAttributeEntry ::= L2L3VpnMcastPmsiTunnelAttributeEntry ::=
SEQUENCE { SEQUENCE {
l2L3VpnMcastPmsiTunnelAttributeFlags
OCTET STRING,
l2L3VpnMcastPmsiTunnelAttributeAddlFlags
OCTET STRING,
l2L3VpnMcastPmsiTunnelAttributeType l2L3VpnMcastPmsiTunnelAttributeType
L2L3VpnMcastProviderTunnelType, L2L3VpnMcastProviderTunnelType,
l2L3VpnMcastPmsiTunnelAttributeLabel
MplsLabel,
l2L3VpnMcastPmsiTunnelAttributeId l2L3VpnMcastPmsiTunnelAttributeId
L2L3VpnMcastProviderTunnelId, L2L3VpnMcastProviderTunnelId,
l2L3VpnMcastPmsiTunnelAttributeFlags
OCTET STRING,
l2L3VpnMcastPmsiTunnelAttributeMplsLabel
MplsLabel,
l2L3VpnMcastPmsiTunnelPointer l2L3VpnMcastPmsiTunnelPointer
RowPointer, RowPointer,
l2L3VpnMcastPmsiTunnelIf l2L3VpnMcastPmsiTunnelIf
RowPointer RowPointer,
l2L3VpnMcastPmsiTunnelAttributeAddlFlags
OCTET STRING
} }
l2L3VpnMcastPmsiTunnelAttributeType OBJECT-TYPE
SYNTAX L2L3VpnMcastProviderTunnelType
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This object indicates the type of the tunneling technology
used to establish the P-tunnel corresponding to this entry.
When BGP-based PMSI signaling is used, the value of
this object corresponds to the Tunnel Type field
in the PMSI Tunnel attribute advertised/received
in an PMSI auto-discovery (A-D) route.
"
REFERENCE
"RFC6514, Section 5"
::= { l2L3VpnMcastPmsiTunnelAttributeEntry 1 }
l2L3VpnMcastPmsiTunnelAttributeId OBJECT-TYPE
SYNTAX L2L3VpnMcastProviderTunnelId
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This object represents the Tunnel Identifier field, which
uniquely identifies a P-tunnel, in the PMSI Tunnel attribute
of the P-tunnel corresponding to this entry.
The size of the identifier depends on the address family
(IPv4 or IPv6) and the value of the corresponding
l2L3VpnMcastPmsiTunnelAttributeType object i.e., the type of
the tunneling technology used to establish the P-tunnel.
"
REFERENCE
"RFC6514, Section 5"
::= { l2L3VpnMcastPmsiTunnelAttributeEntry 2 }
l2L3VpnMcastPmsiTunnelAttributeFlags OBJECT-TYPE l2L3VpnMcastPmsiTunnelAttributeFlags OBJECT-TYPE
SYNTAX OCTET STRING (SIZE (1)) SYNTAX OCTET STRING (SIZE (1))
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object represents the Flags field in the PMSI Tunnel "This object represents the Flags field in the PMSI Tunnel
attribute. The Flags field has the following format. attribute of the P-tunnel corresponding to this entry.
The Flags field has the following format.
0 1 2 3 4 5 6 7 0 1 2 3 4 5 6 7
+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+
|U|E| U |L| |U|E| U |L|
+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+
E: Extension flag [RFC7902] E: Extension flag [RFC7902]
U: Unassigned U: Unassigned
L: Leaf Information Required flag [RFC6514] L: Leaf Information Required flag [RFC6514]
When BGP-based PMSI signaling is used, the value of When BGP-based PMSI signaling is used, the PMSI Tunnel
this object corresponds to the Flags field in attribute of the P-tunnel will be advertised/received
an advertised/received PMSI auto-discovery (A-D) route. in an PMSI auto-discovery (A-D) route. The value of
this object corresponds to the Flags field in the attribute.
When UDP-based S-PMSI signaling is used, the value of When the P-tunnel does not have a correspondent PMSI tunnel
this object is zero. attribute, the value of this object will be 0.
These flags are registered at IANA. These flags are registered at IANA.
A current list of assignments can be found at A current list of assignments can be found at
<https://www.iana.org/assignments/bgp-parameters/ <https://www.iana.org/assignments/bgp-parameters/
bgp-parameters.xhtml#pmsi-tunnel-attributes>. bgp-parameters.xhtml#pmsi-tunnel-attributes>.
" "
REFERENCE REFERENCE
"RFC6514, Section 5 "RFC6514, Section 5
RFC7902 RFC7902, Section 3
"
::= { l2L3VpnMcastPmsiTunnelAttributeEntry 1 }
l2L3VpnMcastPmsiTunnelAttributeAddlFlags OBJECT-TYPE
SYNTAX OCTET STRING (SIZE (6))
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object represents BGP Additional PMSI
Tunnel Attribute Flags Extended Community
defined in [RFC7902].
Additional PMSI Tunnel Attribute Flags is
48 one-bit Flags and has the following format.
0 1 2
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
3 4
4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
When BGP-based PMSI signaling is used, and the
Extension flag of l2L3VpnMcastPmsiTunnelAttributeFlags
object is set, the value of this object corresponds to
the value of Additional PMSI Tunnel Attribute Flags
Extended Community in an advertised/received PMSI
auto-discovery (A-D) route.
When UDP-based S-PMSI signaling is used, the value of
this object is zero.
These flags are registered at IANA.
A current list of assignments can be found at
<https://www.iana.org/assignments/bgp-extended-communities/
bgp-extended-communities.xhtml
#additional-pmsi-tunnel-attribute-flags>.
"
REFERENCE
"RFC6514, Section 5
RFC7902
"
::= { l2L3VpnMcastPmsiTunnelAttributeEntry 2 }
l2L3VpnMcastPmsiTunnelAttributeType OBJECT-TYPE
SYNTAX L2L3VpnMcastProviderTunnelType
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The Tunnel Type field that identifies
the type of the tunneling technology used to
establish the provider tunnel (P-tunnel), in a
PMSI Tunnel attribute.
When BGP-based PMSI signaling is used, the value of
this object corresponds to the Tunnel Type field in
an advertised/received PMSI auto-discovery (A-D) route.
When UDP-based S-PMSI signaling is used, the value of
this object will be one of pimAsm (3), pimSsm (4), or
pimBidir (5).
" "
REFERENCE
"RFC6514, Section 5"
::= { l2L3VpnMcastPmsiTunnelAttributeEntry 3 } ::= { l2L3VpnMcastPmsiTunnelAttributeEntry 3 }
l2L3VpnMcastPmsiTunnelAttributeLabel OBJECT-TYPE l2L3VpnMcastPmsiTunnelAttributeMplsLabel OBJECT-TYPE
SYNTAX MplsLabel SYNTAX MplsLabel
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The MPLS Label field in a PMSI Tunnel attribute. "This object represents the MPLS Label in the PMSI Tunnel
attribute of the P-tunnel corresponding to this entry.
When BGP-based PMSI signaling is used, the value of When BGP-based PMSI signaling is used, the PMSI Tunnel
this object corresponds to the MPLS Label field in attribute of the P-tunnel will be advertised/received
an advertised/received PMSI A-D route. in an PMSI auto-discovery (A-D) route. The value of
this object corresponds to the MPLS Label in the attribute.
When UDP-based S-PMSI signaling is used, the value of When the P-tunnel does not have correspondent PMSI tunnel
this object is zero that indicates the absence of MPLS attribute, the value of this object will be 0 that
Label. indicates the absence of any MPLS Label.
"
REFERENCE
"RFC6514, Section 5"
::= { l2L3VpnMcastPmsiTunnelAttributeEntry 4 }
l2L3VpnMcastPmsiTunnelAttributeId OBJECT-TYPE
SYNTAX L2L3VpnMcastProviderTunnelId
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The Tunnel Identifier field that uniquely
identifies a tunnel, in a PMSI Tunnel attribute.
The size of the identifier depends on the address family
(IPv4 or IPv6) and the value of the corresponding
l2L3VpnMcastPmsiTunnelAttributeType object i.e., the type of
the tunneling technology used to establish the provider
tunnel.
" "
REFERENCE REFERENCE
"RFC6514, Section 5" "RFC6514, Section 5"
::= { l2L3VpnMcastPmsiTunnelAttributeEntry 5 } ::= { l2L3VpnMcastPmsiTunnelAttributeEntry 4 }
l2L3VpnMcastPmsiTunnelPointer OBJECT-TYPE l2L3VpnMcastPmsiTunnelPointer OBJECT-TYPE
SYNTAX RowPointer SYNTAX RowPointer
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The tunnel identified by l2L3VpnMcastPmsiTunnelAttributeId "The P-tunnel identified by
may be represented as an entry in some other table, e.g., l2L3VpnMcastPmsiTunnelAttributeId may be represented
as an entry in some other table, e.g.,
mplsTunnelTable [RFC3812]. This object specifies mplsTunnelTable [RFC3812]. This object specifies
the pointer to the row pertaining to the entry. the pointer to the row pertaining to the entry.
If such an entry does not exist, the value of this object If such an entry does not exist, the value of this object
MUST be zeroDotZero. MUST be zeroDotZero.
" "
REFERENCE
"RFC3812, Section 6.1 and Section 11"
DEFVAL { zeroDotZero } DEFVAL { zeroDotZero }
::= { l2L3VpnMcastPmsiTunnelAttributeEntry 6 }
::= { l2L3VpnMcastPmsiTunnelAttributeEntry 5 }
l2L3VpnMcastPmsiTunnelIf OBJECT-TYPE l2L3VpnMcastPmsiTunnelIf OBJECT-TYPE
SYNTAX RowPointer SYNTAX RowPointer
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"If the tunnel identified by l2L3VpnMcastPmsiTunnelAttributeId "If the P-tunnel identified by
has a corresponding entry in the ifXTable [RFC2863], l2L3VpnMcastPmsiTunnelAttributeId has a corresponding
this object will point to the row pertaining to the entry entry in the ifXTable [RFC2863], this object will
in the ifXTable. Otherwise, this object MUST be set to point to the row pertaining to the entry in the ifXTable.
zeroDotZero." Otherwise, this object MUST be set to zeroDotZero.
"
REFERENCE
"RFC2863, Section 6"
DEFVAL { zeroDotZero } DEFVAL { zeroDotZero }
::= { l2L3VpnMcastPmsiTunnelAttributeEntry 6 }
l2L3VpnMcastPmsiTunnelAttributeAddlFlags OBJECT-TYPE
SYNTAX OCTET STRING (SIZE (6))
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object represents BGP Additional PMSI Tunnel
Attribute Flags Extended Community defined in [RFC7902].
The Additional PMSI Tunnel Attribute Flags is a string
of 48 one-bit Flags and has the following format.
0 1 2
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
3 4
4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
When BGP-based PMSI signaling is used, the PMSI Tunnel
attribute of the P-tunnel will be advertised/received
in an PMSI auto-discovery (A-D) route.
When the Extension flag of
l2L3VpnMcastPmsiTunnelAttributeFlags object is set,
the value of this object corresponds to the value of
Additional PMSI Tunnel Attribute Flags Extended
Community in the advertised/received PMSI
auto-discovery (A-D) route.
When the Extension flag of
l2L3VpnMcastPmsiTunnelAttributeFlags object is not set,
the value of this object will be 0.
These flags are registered at IANA.
A current list of assignments can be found at
<https://www.iana.org/assignments/bgp-extended-communities/
bgp-extended-communities.xhtml
#additional-pmsi-tunnel-attribute-flags>.
"
REFERENCE
"RFC6514, Section 5
RFC7902, Section 2
"
::= { l2L3VpnMcastPmsiTunnelAttributeEntry 7 } ::= { l2L3VpnMcastPmsiTunnelAttributeEntry 7 }
-- Conformance Information -- Conformance Information
l2L3VpnMcastCompliances OBJECT IDENTIFIER l2L3VpnMcastCompliances OBJECT IDENTIFIER
::= { l2L3VpnMcastConformance 1 } ::= { l2L3VpnMcastConformance 1 }
l2L3VpnMcastGroups OBJECT IDENTIFIER l2L3VpnMcastGroups OBJECT IDENTIFIER
::= { l2L3VpnMcastConformance 2 } ::= { l2L3VpnMcastConformance 2 }
-- Compliance Statements -- Compliance Statements
l2L3VpnMcastCompliance MODULE-COMPLIANCE l2L3VpnMcastCoreCompliance MODULE-COMPLIANCE
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The compliance statement for SNMP entities which implement "The core compliance statement for SNMP entities
this L2L3-VPN-MCAST-MIB Module." which implement this L2L3-VPN-MCAST-MIB Module."
MODULE -- this module MODULE -- this module
MANDATORY-GROUPS { MANDATORY-GROUPS {
l2L3VpnMcastPmsiFieldGroup l2L3VpnMcastPmsiFieldGroup
} }
GROUP l2L3VpnMcastOptionalGroup
DESCRIPTION
"This group is optional."
::= { l2L3VpnMcastCompliances 1 } ::= { l2L3VpnMcastCompliances 1 }
l2L3VpnMcastFullCompliance MODULE-COMPLIANCE
STATUS current
DESCRIPTION
"The full compliance statement for SNMP entities
which implement this L2L3-VPN-MCAST-MIB Module."
MODULE -- this module
MANDATORY-GROUPS {
l2L3VpnMcastPmsiFieldGroup,
l2L3VpnMcastOptionalGroup
}
::= { l2L3VpnMcastCompliances 2 }
-- units of conformance -- units of conformance
l2L3VpnMcastPmsiFieldGroup OBJECT-GROUP l2L3VpnMcastPmsiFieldGroup OBJECT-GROUP
OBJECTS { OBJECTS {
l2L3VpnMcastPmsiTunnelAttributeFlags, l2L3VpnMcastPmsiTunnelAttributeFlags,
l2L3VpnMcastPmsiTunnelAttributeAddlFlags, l2L3VpnMcastPmsiTunnelAttributeAddlFlags,
l2L3VpnMcastPmsiTunnelAttributeLabel l2L3VpnMcastPmsiTunnelAttributeMplsLabel
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Support of these objects is required." "Support of these objects is required."
::= { l2L3VpnMcastGroups 1 } ::= { l2L3VpnMcastGroups 1 }
l2L3VpnMcastOptionalGroup OBJECT-GROUP l2L3VpnMcastOptionalGroup OBJECT-GROUP
OBJECTS { OBJECTS {
l2L3VpnMcastPmsiTunnelPointer, l2L3VpnMcastPmsiTunnelPointer,
l2L3VpnMcastPmsiTunnelIf l2L3VpnMcastPmsiTunnelIf
skipping to change at page 16, line 50 skipping to change at page 17, line 38
sensitivity/vulnerability: sensitivity/vulnerability:
o the l2L3VpnMcastPmsiTunnelAttributeTable collectively shows the o the l2L3VpnMcastPmsiTunnelAttributeTable collectively shows the
P-tunnel network topology and its performance characteristics. P-tunnel network topology and its performance characteristics.
For instance, l2L3VpnMcastPmsiTunnelAttributeId in this table will For instance, l2L3VpnMcastPmsiTunnelAttributeId in this table will
contain the identifier that uniquely identifies a created contain the identifier that uniquely identifies a created
P-tunnel. This identifier may be composed of source and multicast P-tunnel. This identifier may be composed of source and multicast
group IP addresses. l2L3VpnMcastPmsiTunnelPointer and group IP addresses. l2L3VpnMcastPmsiTunnelPointer and
l2L3VpnMcastPmsiTunnelIf will point to the corresponding entries l2L3VpnMcastPmsiTunnelIf will point to the corresponding entries
in other tables containing configuration and/or performance in other tables containing configuration and/or performance
information of a tunnel and an interface. If an Administrator information of a P-tunnel and its interface. If an Administrator
does not want to reveal this information, then these objects does not want to reveal this information, then these objects
should be considered sensitive/vulnerable. should be considered sensitive/vulnerable.
SNMP versions prior to SNMPv3 did not include adequate security. SNMP versions prior to SNMPv3 did not include adequate security.
Even if the network itself is secure (for example by using IPsec), Even if the network itself is secure (for example by using IPsec),
there is no control as to who on the secure network is allowed to there is no control as to who on the secure network is allowed to
access and GET/SET (read/change/create/delete) the objects in this access and GET/SET (read/change/create/delete) the objects in this
MIB module. MIB module.
Implementations SHOULD provide the security features described by the Implementations SHOULD provide the security features described by the
skipping to change at page 18, line 48 skipping to change at page 19, line 34
RFC4087, June 2005, <https://www.rfc-editor.org/info/ RFC4087, June 2005, <https://www.rfc-editor.org/info/
rfc4087>. rfc4087>.
[RFC4875] Aggarwal, R., Ed., Papadimitriou, D., Ed., and S. [RFC4875] Aggarwal, R., Ed., Papadimitriou, D., Ed., and S.
Yasukawa, Ed., "Extensions to Resource Reservation Yasukawa, Ed., "Extensions to Resource Reservation
Protocol - Traffic Engineering (RSVP-TE) for Point-to- Protocol - Traffic Engineering (RSVP-TE) for Point-to-
Multipoint TE Label Switched Paths (LSPs)", RFC 4875, DOI Multipoint TE Label Switched Paths (LSPs)", RFC 4875, DOI
10.17487/RFC4875, May 2007, <https://www.rfc- 10.17487/RFC4875, May 2007, <https://www.rfc-
editor.org/info/rfc4875>. editor.org/info/rfc4875>.
[RFC5015] Handley, M., Kouvelas, I., Speakman, T., and L. Vicisano,
"Bidirectional Protocol Independent Multicast (BIDIR-
PIM)", RFC 5015, DOI 10.17487/RFC5015, October 2007,
<https://www.rfc-editor.org/info/rfc5015>.
[RFC5591] Harrington, D. and W. Hardaker, "Transport Security Model [RFC5591] Harrington, D. and W. Hardaker, "Transport Security Model
for the Simple Network Management Protocol (SNMP)", STD for the Simple Network Management Protocol (SNMP)", STD
78, RFC 5591, DOI 10.17487/RFC5591, June 2009, 78, RFC 5591, DOI 10.17487/RFC5591, June 2009,
<https://www.rfc-editor.org/info/rfc5591>. <https://www.rfc-editor.org/info/rfc5591>.
[RFC5592] Harrington, D., Salowey, J., and W. Hardaker, "Secure [RFC5592] Harrington, D., Salowey, J., and W. Hardaker, "Secure
Shell Transport Model for the Simple Network Management Shell Transport Model for the Simple Network Management
Protocol (SNMP)", RFC 5592, DOI 10.17487/RFC5592, June Protocol (SNMP)", RFC 5592, DOI 10.17487/RFC5592, June
2009, <https://www.rfc-editor.org/info/rfc5592>. 2009, <https://www.rfc-editor.org/info/rfc5592>.
skipping to change at page 20, line 5 skipping to change at page 20, line 42
Point-to-Multipoint (P2MP) Segmented Label Switched Paths Point-to-Multipoint (P2MP) Segmented Label Switched Paths
(LSPs)", RFC 7524, DOI 10.17487/RFC7524, May 2015, (LSPs)", RFC 7524, DOI 10.17487/RFC7524, May 2015,
<https://www.rfc-editor.org/info/rfc7524>. <https://www.rfc-editor.org/info/rfc7524>.
[RFC7761] Fenner, B., Handley, M., Holbrook, H., Kouvelas, I., [RFC7761] Fenner, B., Handley, M., Holbrook, H., Kouvelas, I.,
Parekh, R., Zhang, Z., and L. Zheng, "Protocol Independent Parekh, R., Zhang, Z., and L. Zheng, "Protocol Independent
Multicast - Sparse Mode (PIM-SM): Protocol Specification Multicast - Sparse Mode (PIM-SM): Protocol Specification
(Revised)", STD 83, RFC 7761, DOI 10.17487/RFC7761, March (Revised)", STD 83, RFC 7761, DOI 10.17487/RFC7761, March
2016, <https://www.rfc-editor.org/info/rfc7761>. 2016, <https://www.rfc-editor.org/info/rfc7761>.
[RFC7902] Rosen, E. and T. Morin, "Registry and Extensions for
P-Multicast Service Interface Tunnel Attribute Flags", RFC
7902, DOI 10.17487/RFC7902, June 2016, <https://www.rfc-
editor.org/info/rfc7902>.
7.2. Informative References 7.2. Informative References
[RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart, [RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart,
"Introduction and Applicability Statements for Internet- "Introduction and Applicability Statements for Internet-
Standard Management Framework", RFC 3410, DOI 10.17487/ Standard Management Framework", RFC 3410, DOI 10.17487/
RFC3410, December 2002, <https://www.rfc-editor.org/info/ RFC3410, December 2002, <https://www.rfc-editor.org/info/
rfc3410>. rfc3410>.
Authors' Addresses Authors' Addresses
 End of changes. 71 change blocks. 
211 lines changed or deleted 231 lines changed or added

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