draft-ietf-bess-l2l3-vpn-mcast-mib-14.txt   draft-ietf-bess-l2l3-vpn-mcast-mib-15.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: September 1, 2018 Tohoku Institute of Technology Expires: February 12, 2019 Tohoku Institute of Technology
February 28, 2018 August 11, 2018
L2L3 VPN Multicast MIB L2L3 VPN Multicast MIB
draft-ietf-bess-l2l3-vpn-mcast-mib-14 draft-ietf-bess-l2l3-vpn-mcast-mib-15
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 September 1, 2018. This Internet-Draft will expire on February 12, 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
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 . . . . . . . . . 3 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-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 . . . . . . . . . . . . . . . . . . . 15 5. Security Considerations . . . . . . . . . . . . . . . . . . . 15
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 16 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 16
7. References . . . . . . . . . . . . . . . . . . . . . . . . . 17 7. Acknowledgement . . . . . . . . . . . . . . . . . . . . . . . 17
7.1. Normative References . . . . . . . . . . . . . . . . . . 17 8. References . . . . . . . . . . . . . . . . . . . . . . . . . 17
7.2. Informative References . . . . . . . . . . . . . . . . . 19 8.1. Normative References . . . . . . . . . . . . . . . . . . 17
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 19 8.2. Informative References . . . . . . . . . . . . . . . . . 19
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 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
skipping to change at page 3, line 44 skipping to change at page 3, line 44
There are two kinds of PMSIs: "Inclusive PMSI (I-PMSI)" and There are two kinds of PMSIs: "Inclusive PMSI (I-PMSI)" and
"Selective PMSI (S-PMSI)" [RFC6513]. An I-PMSI is a PMSI that "Selective PMSI (S-PMSI)" [RFC6513]. An I-PMSI is a PMSI that
enables a PE attached to a particular Multicast VPN to transmit a enables a PE attached to a particular Multicast VPN to transmit a
message to all PEs in the same VPN. An S-PMSI is a PMSI that enables message to all PEs in the same VPN. An S-PMSI is a PMSI that enables
a PE attached to a particular Multicast VPN to transmit a message to a PE attached to a particular Multicast VPN to transmit a message to
some of the PEs in the same VPN. some of the PEs in the same VPN.
Throughout this document, we will use the term "PMSI" to refer both Throughout this document, we will use the term "PMSI" to refer both
"I-PMSI" and "S-PMSI." "I-PMSI" and "S-PMSI."
The key words "MUST", "SHOULD", "RECOMMENDED", and "MAY" in this The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
document are to be interpreted as described in [RFC2119]. "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
"OPTIONAL" in this document are to be interpreted as described in BCP
14 [RFC2119] [RFC8174] when, and only when, they appear in all
capitals, as shown here.
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).
skipping to change at page 4, line 52 skipping to change at page 5, line 9
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 "201802281200Z" -- 28th February, 2018 LAST-UPDATED "201808101200Z" -- 10th August, 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 28 skipping to change at page 5, line 34
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 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 (2017). Copyright (C) The Internet Society (2018).
" "
-- Revision history. -- Revision history.
REVISION "201802281200Z" -- 28th February, 2018 REVISION "201808101200Z" -- 10th August, 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 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 "201712121200Z" -- 12th December, 2017 LAST-UPDATED "201808101200Z" -- 10th August, 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 13 skipping to change at page 10, line 13
" "
DESCRIPTION DESCRIPTION
"This MIB module defines a table representing the attribute "This MIB module defines a table representing the attribute
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 (2018).
" "
-- Revision history. -- Revision history.
REVISION "201712121200Z" -- 12th December, 2017 REVISION "201808101200Z" -- 10th August, 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 17, line 7 skipping to change at page 17, line 7
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 Descriptor OBJECT IDENTIFIER value
---------- ----------------------- ---------- -----------------------
l2L3VpnMcastTCMIB { mib-2 AAA } l2L3VpnMcastTCMIB { mib-2 AAAA }
l2L3VpnMcastMIB { mib-2 BBB } l2L3VpnMcastMIB { 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 "AAA" and "BBB" 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
"AAA" and "BBB" (here and in the MIB module) with the assigned value "AAAA" and "BBBB" (here and in the MIB module) with the assigned
and to remove this note. value and to remove this note.
7. References 7. Acknowledgement
7.1. Normative References Glenn Mansfield Keeni did the MIB Doctor review and provided valuable
comments.
8. References
8.1. Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, DOI 10.17487/ Requirement Levels", BCP 14, RFC 2119, DOI 10.17487/
RFC2119, March 1997, <https://www.rfc-editor.org/info/ RFC2119, March 1997, <https://www.rfc-editor.org/info/
rfc2119>. rfc2119>.
[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, DOI 10.17487/ Version 2 (SMIv2)", STD 58, RFC 2578, DOI 10.17487/
RFC2578, April 1999, <https://www.rfc-editor.org/info/ RFC2578, April 1999, <https://www.rfc-editor.org/info/
skipping to change at page 19, line 37 skipping to change at page 19, 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>.
7.2. Informative References [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC
2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174,
May 2017, <https://www.rfc-editor.org/info/rfc8174>.
8.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
Zhaohui (Jeffrey) Zhang Zhaohui (Jeffrey) 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
Tohoku Institute of Technology Tohoku Institute of Technology
 End of changes. 19 change blocks. 
25 lines changed or deleted 39 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/