draft-ietf-bess-l2l3-vpn-mcast-mib-11.txt   draft-ietf-bess-l2l3-vpn-mcast-mib-12.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: April 23, 2018 Tohoku Institute of Technology Expires: May 31, 2018 Tohoku Institute of Technology
October 20, 2017 November 27, 2017
L2L3 VPN Multicast MIB L2L3 VPN Multicast MIB
draft-ietf-bess-l2l3-vpn-mcast-mib-11 draft-ietf-bess-l2l3-vpn-mcast-mib-12
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 April 23, 2018. This Internet-Draft will expire on May 31, 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
skipping to change at page 2, line 16 skipping to change at page 2, line 16
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 . . . . . . . . . 3 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 . . . . . . . . 4 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 . . . . . . . . . . . . . . . . . . . 17 5. Security Considerations . . . . . . . . . . . . . . . . . . . 15
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 18 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 16
7. References . . . . . . . . . . . . . . . . . . . . . . . . . 18 7. References . . . . . . . . . . . . . . . . . . . . . . . . . 17
7.1. Normative References . . . . . . . . . . . . . . . . . . 18 7.1. Normative References . . . . . . . . . . . . . . . . . . 17
7.2. Informative References . . . . . . . . . . . . . . . . . 20 7.2. Informative References . . . . . . . . . . . . . . . . . 19
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 21 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 19
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 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 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
service provider networks. These transport mechanisms are abstracted service provider networks. These transport mechanisms are abstracted
as provider tunnels (P-tunnels). The type of a P-tunnel indicates 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 type of the tunneling technology used to establish the P-tunnel.
The syntax and semantics of an identifier of the established are The syntax and semantics of a Tunnel identifier is determined by the
determined by the type of the P-tunnel [RFC6514]. The P-tunnel type corresponding P-tunnel type [RFC6514]. P-tunnel type and P-tunnel
and the P-tunnel identifier together identify a 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. The P-tunnel type and the P-tunnel identifier are tunnel attribute. P-tunnel type and the P-tunnel identifier are
in a PMSI tunnel attribute. included in the corresponding PMSI tunnel attribute.
This document describes textual conventions (TCs) and common managed This document describes textual conventions (TCs) and common managed
objects (MOs) which will be used by other Management Information Base objects (MOs) which will be used by other Management Information Base
(MIB) modules for monitoring and/or configuring L2L3VpnMCast network. (MIB) modules for monitoring and/or configuring L2L3VpnMCast
networks.
This document defines two TCs to represent This document defines two TCs to represent
(a) the 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.
The document also defines MOs that will provide the information The document also defines MOs that will provide the information
contained in a PMSI tunnel attribute and corresponding P-tunnel contained in a PMSI tunnel attribute and corresponding P-tunnel
skipping to change at page 4, line 52 skipping to change at page 4, line 52
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 "201710041200Z" -- 4th October, 2017 LAST-UPDATED "201711071200Z" -- 7th November, 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 25 skipping to change at page 5, line 25
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 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 Networks
that support multicast (L2L3VpnMCast network). that support multicast (L2L3VpnMCast networks).
Copyright (C) The Internet Society (2017). Copyright (C) The Internet Society (2017).
" "
-- Revision history. -- Revision history.
REVISION "201710041200Z" -- 4th October, 2017 REVISION "201711071200Z" -- 7th November, 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.
skipping to change at page 6, line 12 skipping to change at page 6, line 12
-- 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 network. used for L2L3VpnMCast networks.
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 P-tunnel type The enumerated values and the corresponding P-tunnel types
are as follows: are as follows:
noTunnelInfo (0) : no tunnel information present noTunnelInfo (0) : no tunnel information present
[RFC6514] [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]
skipping to change at page 7, line 50 skipping to change at page 7, line 50
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
Tunnel type is set to 'No tunnel information present' Tunnel type is set to 'No tunnel information present'
when the PMSI Tunnel attribute carries no tunnel when the PMSI Tunnel attribute carries no tunnel
information (no Tunnel Identifier). information (there is no 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.
For tunnel type rsvpP2mp(1), the corresponding Tunnel For tunnel type rsvpP2mp(1), the corresponding Tunnel
Identifier is composed of Extended Tunnel ID (4 octets in IPv4, Identifier is composed of Extended Tunnel ID (4 octets in IPv4,
16 octets in IPv6), Reserved (2 octets), Tunnel ID (2 octets), 16 octets in IPv6), Reserved (2 octets), Tunnel ID (2 octets),
and P2MP ID (4 octets). and 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.
skipping to change at page 9, line 29 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 "201710041200Z" -- 4th October, 2017 LAST-UPDATED "201711271200Z" -- 27th November, 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 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 (2017). Copyright (C) The Internet Society (2017).
" "
-- Revision history. -- Revision history.
REVISION "201710041200Z" -- 4th October, 2017 REVISION "201711271200Z" -- 27th November, 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 12 skipping to change at page 11, line 12
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 network. for monitoring and/or configuring L2L3VpnMCast networks.
" "
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 40 skipping to change at page 11, line 40
l2L3VpnMcastPmsiTunnelAttributeId l2L3VpnMcastPmsiTunnelAttributeId
} }
::= { l2L3VpnMcastPmsiTunnelAttributeTable 1 } ::= { l2L3VpnMcastPmsiTunnelAttributeTable 1 }
L2L3VpnMcastPmsiTunnelAttributeEntry ::= L2L3VpnMcastPmsiTunnelAttributeEntry ::=
SEQUENCE { SEQUENCE {
l2L3VpnMcastPmsiTunnelAttributeType l2L3VpnMcastPmsiTunnelAttributeType
L2L3VpnMcastProviderTunnelType, L2L3VpnMcastProviderTunnelType,
l2L3VpnMcastPmsiTunnelAttributeId l2L3VpnMcastPmsiTunnelAttributeId
L2L3VpnMcastProviderTunnelId, L2L3VpnMcastProviderTunnelId,
l2L3VpnMcastPmsiTunnelAttributeFlags l2L3VpnMCastPmsiTunnelLeafInfoRequired
OCTET STRING, INTEGER,
l2L3VpnMcastPmsiTunnelAttributeMplsLabel l2L3VpnMcastPmsiTunnelAttributeMplsLabel
MplsLabel, MplsLabel,
l2L3VpnMcastPmsiTunnelPointer l2L3VpnMcastPmsiTunnelPointer
RowPointer, RowPointer,
l2L3VpnMcastPmsiTunnelIf l2L3VpnMcastPmsiTunnelIf
RowPointer, RowPointer
l2L3VpnMcastPmsiTunnelAttributeAddlFlags
OCTET STRING
} }
l2L3VpnMcastPmsiTunnelAttributeType OBJECT-TYPE l2L3VpnMcastPmsiTunnelAttributeType OBJECT-TYPE
SYNTAX L2L3VpnMcastProviderTunnelType SYNTAX L2L3VpnMcastProviderTunnelType
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object indicates the type of the tunneling technology "This object indicates the type of the tunneling technology
used to establish the P-tunnel corresponding to this entry. used to establish 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 value of
this object corresponds to the Tunnel Type field this object corresponds to the Tunnel Type field
in the PMSI Tunnel attribute advertised/received in the PMSI Tunnel attribute advertised/received
in an PMSI auto-discovery (A-D) route. in a PMSI auto-discovery (A-D) route.
" "
REFERENCE REFERENCE
"RFC6514, Section 5" "RFC6514, Section 5"
::= { l2L3VpnMcastPmsiTunnelAttributeEntry 1 } ::= { l2L3VpnMcastPmsiTunnelAttributeEntry 1 }
l2L3VpnMcastPmsiTunnelAttributeId OBJECT-TYPE l2L3VpnMcastPmsiTunnelAttributeId OBJECT-TYPE
SYNTAX L2L3VpnMcastProviderTunnelId SYNTAX L2L3VpnMcastProviderTunnelId
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
skipping to change at page 12, line 40 skipping to change at page 12, line 37
The size of the identifier depends on the address family The size of the identifier depends on the address family
(IPv4 or IPv6) and the value of the corresponding (IPv4 or IPv6) and the value of the corresponding
l2L3VpnMcastPmsiTunnelAttributeType object i.e., the type of l2L3VpnMcastPmsiTunnelAttributeType object i.e., the type of
the tunneling technology used to establish the P-tunnel. the tunneling technology used to establish the P-tunnel.
" "
REFERENCE REFERENCE
"RFC6514, Section 5" "RFC6514, Section 5"
::= { l2L3VpnMcastPmsiTunnelAttributeEntry 2 } ::= { l2L3VpnMcastPmsiTunnelAttributeEntry 2 }
l2L3VpnMcastPmsiTunnelAttributeFlags OBJECT-TYPE l2L3VpnMCastPmsiTunnelLeafInfoRequired OBJECT-TYPE
SYNTAX OCTET STRING (SIZE (1)) SYNTAX INTEGER {
false (0),
true (1),
notAvailable (2)
}
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object represents the Flags field in the PMSI Tunnel "When the value of this object is set to 1 (true),
attribute of the P-tunnel corresponding to this entry. it indicates that the PE which originated the
The Flags field has the following format. PMSI Tunnel attribute of the P-tunnel corresponding
to this entry requests receivers to originate
0 1 2 3 4 5 6 7 a new Leaf A-D (Auto-Discovery) route.
+-+-+-+-+-+-+-+-+
|U|E| U |L|
+-+-+-+-+-+-+-+-+
E: Extension flag [RFC7902]
U: Unassigned
L: Leaf Information Required flag [RFC6514]
When BGP-based PMSI signaling is used, the PMSI Tunnel A value of 0 (false) indicates that there is no such
attribute of the P-tunnel will be advertised/received request.
in an PMSI auto-discovery (A-D) route. The value of
this object corresponds to the Flags field in the attribute.
When the P-tunnel does not have a correspondent PMSI tunnel When the P-tunnel does not have a corresponding PMSI
attribute, the value of this object will be 0. tunnel attribute, the value of this object will be
2 (notAvailable).
These flags are registered at IANA. In the case of Multicast in MPLS/BGP IP VPNs,
A current list of assignments can be found at this object represents the 'Leaf Information Required flag'
<https://www.iana.org/assignments/bgp-parameters/ [RFC6514] in the Flags field in the PMSI Tunnel attribute
bgp-parameters.xhtml#pmsi-tunnel-attributes>. of the P-tunnel corresponding to this entry.
" "
REFERENCE REFERENCE
"RFC6514, Section 5 "RFC6514, Section 5
RFC7902, Section 3
" "
::= { l2L3VpnMcastPmsiTunnelAttributeEntry 3 } ::= { l2L3VpnMcastPmsiTunnelAttributeEntry 3 }
l2L3VpnMcastPmsiTunnelAttributeMplsLabel OBJECT-TYPE l2L3VpnMcastPmsiTunnelAttributeMplsLabel OBJECT-TYPE
SYNTAX MplsLabel SYNTAX MplsLabel
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object represents the MPLS Label in the PMSI Tunnel "This object represents the MPLS Label in the PMSI Tunnel
attribute of the P-tunnel corresponding to this entry. attribute of the P-tunnel corresponding to this entry.
skipping to change at page 14, line 46 skipping to change at page 14, line 30
l2L3VpnMcastPmsiTunnelAttributeId has a corresponding l2L3VpnMcastPmsiTunnelAttributeId has a corresponding
entry in the ifXTable [RFC2863], this object will entry in the ifXTable [RFC2863], this object will
point to the row pertaining to the entry in the ifXTable. point to the row pertaining to the entry in the ifXTable.
Otherwise, this object MUST be set to zeroDotZero. Otherwise, this object MUST be set to zeroDotZero.
" "
REFERENCE REFERENCE
"RFC2863, Section 6" "RFC2863, Section 6"
DEFVAL { zeroDotZero } DEFVAL { zeroDotZero }
::= { l2L3VpnMcastPmsiTunnelAttributeEntry 6 } ::= { 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 }
-- 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
l2L3VpnMcastCoreCompliance MODULE-COMPLIANCE l2L3VpnMcastCoreCompliance MODULE-COMPLIANCE
STATUS current STATUS current
DESCRIPTION DESCRIPTION
skipping to change at page 16, line 19 skipping to change at page 14, line 47
-- 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 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 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 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, l2L3VpnMcastCoreGroup,
l2L3VpnMcastOptionalGroup l2L3VpnMcastOptionalGroup
} }
::= { l2L3VpnMcastCompliances 2 } ::= { l2L3VpnMcastCompliances 2 }
-- units of conformance -- units of conformance
l2L3VpnMcastPmsiFieldGroup OBJECT-GROUP l2L3VpnMcastCoreGroup OBJECT-GROUP
OBJECTS { OBJECTS {
l2L3VpnMcastPmsiTunnelAttributeFlags, l2L3VpnMCastPmsiTunnelLeafInfoRequired,
l2L3VpnMcastPmsiTunnelAttributeAddlFlags,
l2L3VpnMcastPmsiTunnelAttributeMplsLabel 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,
 End of changes. 31 change blocks. 
110 lines changed or deleted 56 lines changed or added

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