draft-ietf-bess-l2l3-vpn-mcast-mib-01.txt   draft-ietf-bess-l2l3-vpn-mcast-mib-02.txt 
L3 VPN Working Group Z. Zhang L3 VPN Working Group Z. Zhang
Internet-Draft Juniper Networks, Inc. Internet-Draft Juniper Networks, Inc.
Intended status: Standards Track August 11, 2015 Intended status: Standards Track March 14, 2016
Expires: February 12, 2016 Expires: September 15, 2016
L2L3 VPN Multicast MIB L2L3 VPN Multicast MIB
draft-ietf-bess-l2l3-vpn-mcast-mib-01 draft-ietf-bess-l2l3-vpn-mcast-mib-02
Abstract Abstract
This memo defines an experimental portion of the Management This memo defines a portion of the Management Information Base for
Information Base for use with network management protocols in the use with network management protocols in the Internet community.
Internet community.
In particular, it describes managed objects common to both VPLS and In particular, it describes managed objects common to both L2 and IP
VPN Multicast. VPN Multicast.
Status of This Memo Status of This Memo
This Internet-Draft is submitted in full conformance with the This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
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, 2016. This Internet-Draft will expire on September 15, 2016.
Copyright Notice Copyright Notice
Copyright (c) 2015 IETF Trust and the persons identified as the Copyright (c) 2016 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 . . . . . . . . . . . . . . . . . . . . . . . 2
2. The Internet-Standard Management Framework . . . . . . . . . 2 2. The Internet-Standard Management Framework . . . . . . . . . 2
3. Summary of MIB Module . . . . . . . . . . . . . . . . . . . . 2 3. Summary of MIB Module . . . . . . . . . . . . . . . . . . . . 3
4. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 3 4. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 3
5. Security Considerations . . . . . . . . . . . . . . . . . . . 8 5. Security Considerations . . . . . . . . . . . . . . . . . . . 7
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 8 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 8
7. References . . . . . . . . . . . . . . . . . . . . . . . . . 8 7. References . . . . . . . . . . . . . . . . . . . . . . . . . 8
7.1. Normative References . . . . . . . . . . . . . . . . . . 8 7.1. Normative References . . . . . . . . . . . . . . . . . . 8
7.2. Informative References . . . . . . . . . . . . . . . . . 9 7.2. Informative References . . . . . . . . . . . . . . . . . 8
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 9 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 9
1. Introduction 1. Introduction
Multicast in VPLS and VPN can be achieved by using provider tunnels Multicast in BGP/MPLS IP or L2 VPN (referred to MVPN and L2 VPN
to deliver to all or a subset of PEs. The signaling of provider Multicast respectively) can be achieved by using provider tunnels to
tunnel choice is very similar for both VPLS and VPN multicast (aka deliver to all or a subset of PEs. An example of L2 VPN is VPLS.
MVPN), and this memo describes managed objects common to both VPLS The signaling of provider tunnel choice is very similar for both
cases, and this memo describes managed objects common to both VPLS
Multicast [RFC7117] and MVPN [RFC6513, RFC6514]. Multicast [RFC7117] and MVPN [RFC6513, RFC6514].
1.1. Terminology
This document adopts the definitions, acronyms and mechanisms
described in [RFC6513, RFC6514, RFC 7117] and other documents that
they refer to. Familiarity with Multicast, MPLS, L3VPN, MVPN
concepts and/or mechanisms is assumed. Some of the terms are listed
below.
o PMSI: P-Multicast Service Interface
o I-PMSI: Inclusive PMSI
o S-PMSI: Selective PMSI
2. The Internet-Standard Management Framework 2. The Internet-Standard Management Framework
For a detailed overview of the documents that describe the current For a detailed overview of the documents that describe the current
Internet-Standard Management Framework, please refer to section 7 of Internet-Standard Management Framework, please refer to section 7 of
RFC 3410 [RFC3410]. RFC 3410 [RFC3410].
Managed objects are accessed via a virtual information store, termed Managed objects are accessed via a virtual information store, termed
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
skipping to change at page 3, line 32 skipping to change at page 3, line 43
FROM SNMP-FRAMEWORK-MIB FROM SNMP-FRAMEWORK-MIB
InetAddress, InetAddressType InetAddress, InetAddressType
FROM INET-ADDRESS-MIB FROM INET-ADDRESS-MIB
MplsLabel MplsLabel
FROM MPLS-TC-STD-MIB; FROM MPLS-TC-STD-MIB;
l2L3VpnMcastMIB MODULE-IDENTITY l2L3VpnMcastMIB MODULE-IDENTITY
LAST-UPDATED "201310141200Z" -- 14 October 2013 12:00:00 GMT LAST-UPDATED "201310141200Z" -- 14 October 2013 12:00:00 GMT
ORGANIZATION "IETF Layer-3 Virtual Private Networks Working Group." ORGANIZATION "IETF BESS Working Group."
CONTACT-INFO CONTACT-INFO
" "
Comments and discussion to l3vpn@ietf.org Comments and discussion to bess@ietf.org
Jeffrey (Zhaohui) Zhang Jeffrey (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
" "
DESCRIPTION DESCRIPTION
"This MIB contains common managed object definitions for "This MIB contains common managed object definitions for
skipping to change at page 4, line 15 skipping to change at page 4, line 27
REVISION "201310141200Z" -- 14 October 2013 12:00:00 GMT REVISION "201310141200Z" -- 14 October 2013 12:00:00 GMT
DESCRIPTION DESCRIPTION
"Initial version of the draft." "Initial version of the draft."
::= { experimental 99 } -- number to be assigned ::= { experimental 99 } -- number to be assigned
-- Texual convention -- Texual convention
L2L3VpnMcastProviderTunnelType ::= TEXTUAL-CONVENTION L2L3VpnMcastProviderTunnelType ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Types of provider tunnels used for multicast in a l2/l3vpn." "Types of provider tunnels used for multicast in
BGP/MPLS L2 or IP VPN."
SYNTAX INTEGER { unconfigured (0), SYNTAX INTEGER { unconfigured (0),
rsvp-p2mp (1), rsvp-p2mp (1),
ldp-p2mp (2), ldp-p2mp (2),
pim-asm (3), pim-asm (3),
pim-ssm (4), pim-ssm (4),
pim-bidir (5), pim-bidir (5),
ingress-replication (6), ingress-replication (6),
ldp-mp2mp (7) ldp-mp2mp (7)
} }
skipping to change at page 5, line 36 skipping to change at page 5, line 50
l2L3VpnMcastPmsiTunnelPointer RowPointer, l2L3VpnMcastPmsiTunnelPointer RowPointer,
l2L3VpnMcastPmsiTunnelIf RowPointer l2L3VpnMcastPmsiTunnelIf RowPointer
} }
l2L3VpnMcastPmsiTunnelAttributeFlags OBJECT-TYPE l2L3VpnMcastPmsiTunnelAttributeFlags OBJECT-TYPE
SYNTAX OCTET STRING (SIZE (1)) SYNTAX OCTET STRING (SIZE (1))
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"For UDP-based S-PMSI signaling for PIM-MVPN, this is 0. "For UDP-based S-PMSI signaling for PIM-MVPN, this is 0.
For BGP-based I/S-PMSI signaling, For BGP-based I/S-PMSI signaling, this is the Flags
per RFC 6514 section 5, 'PMSI Tunnel Attribute': field in PMSI Tunnel Attribute of the corresponding
I/S-PMSI A-D route."
The Flags field has the following format:
0 1 2 3 4 5 6 7
+-+-+-+-+-+-+-+-+
| reserved |L|
+-+-+-+-+-+-+-+-+
This document defines the following flags:
+ Leaf Information Required (L)"
::= { l2L3VpnMcastPmsiTunnelAttributeEntry 1 } ::= { l2L3VpnMcastPmsiTunnelAttributeEntry 1 }
l2L3VpnMcastPmsiTunnelAttributeType OBJECT-TYPE l2L3VpnMcastPmsiTunnelAttributeType OBJECT-TYPE
SYNTAX L2L3VpnMcastProviderTunnelType SYNTAX L2L3VpnMcastProviderTunnelType
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"For BGP-based I/S-PMSI signaling for either PIM or BGP-MVPN, "As defined for L2L3VpnMcastProviderTunnelType.
per RFC 6514 section 5, 'PMSI Tunnel Attribute': For UDP-based S-PMSI signaling for PIM-MVPN,
this is pim-asm (3), pim-ssm (4), or pim-bidir (5).
The Tunnel Type identifies the type of the tunneling technology used For BGP-based I/S-PMSI signaling, this is the Tunnel Type
to establish the PMSI tunnel. The type determines the syntax and field in PMSI Tunnel Attribute of the corresponding I/S-PMSI
semantics of the Tunnel Identifier field. This document defines the A-D or Leaf A-D route."
following Tunnel Types:
0 - No tunnel information present
1 - RSVP-TE P2MP LSP
2 - mLDP P2MP LSP
3 - PIM-SSM Tree
4 - PIM-SM Tree
5 - PIM-Bidir Tree
6 - Ingress Replication
7 - mLDP MP2MP LSP
For UDP-based S-PMSI signaling for PIM-MVPN, RFC 6513 does not
specify if a PIM provider tunnel is SSM, SM or Bidir,
and an agent can use either type 3, 4, or 5 based on its
best knowledge."
::= { l2L3VpnMcastPmsiTunnelAttributeEntry 2 } ::= { l2L3VpnMcastPmsiTunnelAttributeEntry 2 }
l2L3VpnMcastPmsiTunnelAttributeLabel OBJECT-TYPE l2L3VpnMcastPmsiTunnelAttributeLabel OBJECT-TYPE
SYNTAX MplsLabel SYNTAX MplsLabel
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"For BGP-based I/S-PMSI signaling, "For UDP-based I/S-PMSI signaling for PIM-MVPN, this is 0.
per RFC 6514 section 5, 'PMSI Tunnel Attribute': For BGP-based I/S-PMSI signaling, this is the MPLS Label
field in PMSI Tunnel Attribute of the corresponding
If the MPLS Label field is non-zero, then it contains an MPLS label I/S-PMSI A-D route."
encoded as 3 octets, where the high-order 20 bits contain the label
value. Absence of MPLS Label is indicated by setting the MPLS Label
field to zero.
For UDP-based S-PMSI signaling for PIM-MVPN, this is not
applicable for now, as RFC 6513 does not specify
mpls encapsulation and tunnel aggregation with UDP-based
signaling."
::= { l2L3VpnMcastPmsiTunnelAttributeEntry 3 } ::= { l2L3VpnMcastPmsiTunnelAttributeEntry 3 }
l2L3VpnMcastPmsiTunnelAttributeId OBJECT-TYPE l2L3VpnMcastPmsiTunnelAttributeId OBJECT-TYPE
SYNTAX OCTET STRING ( SIZE (0..37) ) SYNTAX OCTET STRING ( SIZE (0..37) )
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"For BGP-based signaling, as defined in RFC 6514 section 5, "For UDP-based S-PMSI signaling for PIM-MVPN, the first
'PMSI Tunnel Attribute'. four or sixteen octets of this attribute are filled with
the provider tunnel group address (IPv4 or IPv6)..
For UDP-based S-PMSI signaling for PIM-MVPN, RFC 6513 only For BGP-based I/S-PMSI signaling, this is the Tunnel Identifier
specifies the 'P-Group' address, and that is filled into Field in PMSI Tunnel Attribute of the corresponding I/S-PMSI
the first four octets of this field." A-D route."
::= { l2L3VpnMcastPmsiTunnelAttributeEntry 4 } ::= { 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
"If the tunnel exists in some MIB table, this is the "If the tunnel exists in some MIB table, this is the
row pointer to it." row pointer to it."
::= { l2L3VpnMcastPmsiTunnelAttributeEntry 5 } ::= { l2L3VpnMcastPmsiTunnelAttributeEntry 5 }
skipping to change at page 8, line 15 skipping to change at page 7, line 44
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Support of these object is not required." "Support of these object is not required."
::= { l2L3VpnMcastGroups 1 } ::= { l2L3VpnMcastGroups 1 }
END END
5. Security Considerations 5. Security Considerations
N/A This MIB contains some read-only objects that may be deemed senstive
by some though perhaps not all operators. Appropriate security
procedures related to SNMP in general but not specific to this MIB
need to be implemented by concerned operators.
6. IANA Considerations 6. IANA Considerations
IANA is requested to root MIB objects in the MIB module contained in IANA is requested to root MIB objects in the MIB module contained in
this document under the transmission subtree. this document under the mib-2 subtree.
.
7. References 7. References
7.1. Normative References 7.1. Normative References
[RFC2578] McCloghrie, K., Ed., Perkins, D., Ed., and J. [RFC2578] McCloghrie, K., Ed., Perkins, D., Ed., and J.
Schoenwaelder, Ed., "Structure of Management Information Schoenwaelder, Ed., "Structure of Management Information
Version 2 (SMIv2)", STD 58, RFC 2578, Version 2 (SMIv2)", STD 58, RFC 2578,
DOI 10.17487/RFC2578, April 1999, DOI 10.17487/RFC2578, April 1999,
<http://www.rfc-editor.org/info/rfc2578>. <http://www.rfc-editor.org/info/rfc2578>.
 End of changes. 21 change blocks. 
75 lines changed or deleted 59 lines changed or added

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