draft-ietf-mpls-tp-te-mib-00.txt | draft-ietf-mpls-tp-te-mib-01.txt | |||
---|---|---|---|---|
Network Working Group | Network Working Group | |||
INTERNET-DRAFT M.Venkatesan | INTERNET-DRAFT M.Venkatesan | |||
Intended Status: Standards Track Kannan KV Sampath | Intended Status: Standards Track Kannan KV Sampath | |||
Expires: December 17, 2011 Aricent | Expires: June 15, 2012 Aricent | |||
Sam K. Aldrin | Sam K. Aldrin | |||
Huawei Technologies | Huawei Technologies | |||
Thomas D. Nadeau | Thomas D. Nadeau | |||
CA Technologies | CA Technologies | |||
June 17, 2011 | December 15, 2011 | |||
MPLS-TP Traffic Engineering (TE) Management Information Base (MIB) | MPLS-TP Traffic Engineering (TE) Management Information Base (MIB) | |||
draft-ietf-mpls-tp-te-mib-00.txt | draft-ietf-mpls-tp-te-mib-01.txt | |||
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 managed objects of Tunnels, Identifiers, | In particular, it describes managed objects of Tunnels, Identifiers, | |||
Label Switch Router and Textual conventions for Multiprotocol Label | Label Switch Router and Textual conventions for Multiprotocol Label | |||
Switching (MPLS) based Transport Profile (TP). | Switching (MPLS) based Transport Profile (TP). | |||
Status of this Memo | Status of this Memo | |||
skipping to change at page 1, line 46 | skipping to change at page 1, line 46 | |||
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." | |||
The list of current Internet-Drafts can be accessed at | The list of current Internet-Drafts can be accessed at | |||
http://www.ietf.org/ietf/1id-abstracts.txt. | http://www.ietf.org/ietf/1id-abstracts.txt. | |||
The list of Internet-Draft Shadow Directories can be accessed at | The list of Internet-Draft Shadow Directories can be accessed at | |||
http://www.ietf.org/shadow.html. | http://www.ietf.org/shadow.html. | |||
This Internet-Draft will expire on December 17, 2011. | This Internet-Draft will expire on June 15, 2012. | |||
Copyright and License Notice | Copyright and License Notice | |||
Copyright (c) 2011 IETF Trust and the persons identified as the | Copyright (c) 2011 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 5, line 23 | skipping to change at page 5, line 23 | |||
with upper case letters. In the IP compatible mode, | with upper case letters. In the IP compatible mode, | |||
Global_Node_ID, is used to uniquely identify a node. | Global_Node_ID, is used to uniquely identify a node. | |||
Each ICC or Global_Node_ID contains one unique entry in the | Each ICC or Global_Node_ID contains one unique entry in the | |||
table representing a node. Every node is assigned a local identifier | table representing a node. Every node is assigned a local identifier | |||
within a range of 0 to 16777215. This local identifier is used for | within a range of 0 to 16777215. This local identifier is used for | |||
indexing into mplsTunnelTable as mplsTunnelIngressLSRId and | indexing into mplsTunnelTable as mplsTunnelIngressLSRId and | |||
mplsTunnelEgressLSRId. | mplsTunnelEgressLSRId. | |||
For IP compatible environment, MPLS-TP tunnel is indexed by Tunnel | For IP compatible environment, MPLS-TP tunnel is indexed by Tunnel | |||
Index, Tunnel Instance, Source Global_ID, Source Node_ID, | Index, Tunnel Instance, Source Global_ID, Source Node_ID, Destination | |||
Destination Global_ID and Destination Node_ID. | Global_ID and Destination Node_ID. | |||
For ICC based environment, MPLS-TP tunnel is indexed by Tunnel | For ICC based environment, MPLS-TP tunnel is indexed by Tunnel Index, | |||
Index, Tunnel Instance, Source ICC and Destination ICC. | Tunnel Instance, Source ICC and Destination ICC. | |||
As mplsTunnelTable is indexed by mplsTunnelIndex, | As mplsTunnelTable is indexed by mplsTunnelIndex, | |||
mplsTunnelInstance, mplsTunnelIngressLSRId, and | mplsTunnelInstance, mplsTunnelIngressLSRId, and | |||
mplsTunnelEgressLSRId, the MPLS-TP tunnel identifiers cannot be | mplsTunnelEgressLSRId, the MPLS-TP tunnel identifiers cannot be | |||
used directly. | used directly. | |||
The mplsNodeConfigTable will be used to store an entry for ICC or | The mplsNodeConfigTable will be used to store an entry for ICC or | |||
Global_Node_ID with a local identifier to be used as LSR ID | Global_Node_ID with a local identifier to be used as LSR ID | |||
in mplsTunnelTable. As the regular TE tunnels use IP address as LSR | in mplsTunnelTable. As the regular TE tunnels use IP address as LSR | |||
ID, the local identifier should be below the first valid IP address, | ID, the local identifier should be below the first valid IP address, | |||
skipping to change at page 8, line 24 | skipping to change at page 8, line 24 | |||
| | ^ | | | ^ | |||
| +---------+ | | | +---------+ | | |||
| | | | | | | | |||
| V V | | V V | |||
mplsTunnelTable ---->mplsXCTable | mplsTunnelTable ---->mplsXCTable | |||
^ | ^ | |||
| | | | |||
| | | | |||
mplsTunnelExtTable | mplsTunnelExtTable | |||
An existing mplsTunnelTable uses the new mplsNodeConfigTable table | An existing mplsTunnelTable uses the mplsNodeConfigTable table to map | |||
to map the Global_Node_ID and/or ICC with the local number in order | the Global_Node_ID and/or ICC with the local number in order to | |||
to accommodate in the existing tunnel table's ingress/egress LSR-id. | accommodate in the existing tunnel table's ingress/egress LSR-id. | |||
New mplsTunnelExtTable table provides the reverse direction LSP | New mplsTunnelExtTable table provides the reverse direction LSP | |||
information for the existing tunnel table in order to achieve | information for the existing tunnel table in order to achieve | |||
bidirectional LSPs. | bidirectional LSPs. | |||
mplsXCExtTable is extended from mplsLsrXCTable to provide | mplsXCExtTable is extended from mplsLsrXCTable to provide | |||
backward reference to tunnel entry. | backward reference to tunnel entry. | |||
9. Example of MPLS-TP tunnel setup | 9. Example of MPLS-TP tunnel setup | |||
skipping to change at page 14, line 18 | skipping to change at page 14, line 18 | |||
LAST-UPDATED | LAST-UPDATED | |||
"201106160000Z" -- June 16, 2011 | "201106160000Z" -- June 16, 2011 | |||
ORGANIZATION | ORGANIZATION | |||
"Multiprotocol Label Switching (MPLS) Working Group" | "Multiprotocol Label Switching (MPLS) Working Group" | |||
CONTACT-INFO | CONTACT-INFO | |||
" | " | |||
Venkatesan Mahalingam | Venkatesan Mahalingam | |||
Aricent, | Aricent, | |||
India | India | |||
Email: venkatesan.mahalingam@aricent.com | Email: venkat.mahalingams@gmail.com | |||
Kannan KV Sampath | Kannan KV Sampath | |||
Aricent, | Aricent, | |||
India | India | |||
Email: Kannan.Sampath@aricent.com | Email: Kannan.Sampath@aricent.com | |||
Sam Aldrin | Sam Aldrin | |||
Huawei Technologies | Huawei Technologies | |||
2330 Central Express Way, | 2330 Central Express Way, | |||
Santa Clara, CA 95051, USA | Santa Clara, CA 95051, USA | |||
skipping to change at page 15, line 37 | skipping to change at page 15, line 37 | |||
SYNTAX OCTET STRING (SIZE (4)) | SYNTAX OCTET STRING (SIZE (4)) | |||
MplsNodeId ::= TEXTUAL-CONVENTION | MplsNodeId ::= TEXTUAL-CONVENTION | |||
DISPLAY-HINT "d" | DISPLAY-HINT "d" | |||
STATUS current | STATUS current | |||
DESCRIPTION | DESCRIPTION | |||
"The Node_ID is assigned within the scope of the Global_ID. | "The Node_ID is assigned within the scope of the Global_ID. | |||
The value 0(or 0.0.0.0 in dotted decimal notation) is | The value 0(or 0.0.0.0 in dotted decimal notation) is | |||
reserved and MUST NOT be used. | reserved and MUST NOT be used. | |||
When IPv4 addresses are in use, the value of this object | When IPv4 addresses are in use, the value of this object can | |||
can be derived from the LSR's /32 IPv4 loop back address. | be derived from the LSR's /32 IPv4 loop back address. When | |||
IPv6 addresses are in use, the value of this object can be a | ||||
32-bit value unique within the scope of a Global_ID. | ||||
Note that, when IP reach ability is not needed, the 32-bit | Note that, when IP reach ability is not needed, the 32-bit | |||
Node_ID is not required to have any association | Node_ID is not required to have any association | |||
with the IPv4 address space." | with the IPv4 address space." | |||
SYNTAX Unsigned32 | SYNTAX Unsigned32 | |||
MplsIccId ::= TEXTUAL-CONVENTION | MplsIccId ::= TEXTUAL-CONVENTION | |||
STATUS current | STATUS current | |||
DESCRIPTION | DESCRIPTION | |||
"The ICC is a string of one to six characters, each | "The ICC is a string of one to six characters, each | |||
skipping to change at page 17, line 11 | skipping to change at page 17, line 14 | |||
"201106160000Z" -- June 16, 2011 | "201106160000Z" -- June 16, 2011 | |||
ORGANIZATION | ORGANIZATION | |||
"Multiprotocol Label Switching (MPLS) Working Group" | "Multiprotocol Label Switching (MPLS) Working Group" | |||
CONTACT-INFO | CONTACT-INFO | |||
" | " | |||
Venkatesan Mahalingam | Venkatesan Mahalingam | |||
Aricent, | Aricent, | |||
India | India | |||
Email: venkatesan.mahalingam@aricent.com | Email: venkat.mahalingams@gmail.com | |||
Kannan KV Sampath | Kannan KV Sampath | |||
Aricent, | Aricent, | |||
India | India | |||
Email: Kannan.Sampath@aricent.com | Email: Kannan.Sampath@aricent.com | |||
Sam Aldrin | Sam Aldrin | |||
Huawei Technologies | Huawei Technologies | |||
2330 Central Express Way, | 2330 Central Express Way, | |||
Santa Clara, CA 95051, USA | Santa Clara, CA 95051, USA | |||
skipping to change at page 18, line 38 | skipping to change at page 18, line 42 | |||
::= { mplsIdObjects 2 } | ::= { mplsIdObjects 2 } | |||
mplsNodeId OBJECT-TYPE | mplsNodeId OBJECT-TYPE | |||
SYNTAX MplsNodeId | SYNTAX MplsNodeId | |||
MAX-ACCESS read-write | MAX-ACCESS read-write | |||
STATUS current | STATUS current | |||
DESCRIPTION | DESCRIPTION | |||
"This object allows the operator or service provider to | "This object allows the operator or service provider to | |||
assign a unique MPLS-TP Node_ID. | assign a unique MPLS-TP Node_ID. | |||
The Node_ID is assigned within the scope of the | The Node_ID is assigned within the scope of the Global_ID." | |||
Global_ID." | ||||
REFERENCE | REFERENCE | |||
"MPLS-TP Identifiers [TPIDS]." | "MPLS-TP Identifiers [TPIDS]." | |||
::= { mplsIdObjects 3 } | ::= { mplsIdObjects 3 } | |||
-- Module compliance. | -- Module compliance. | |||
mplsIdGroups | mplsIdGroups | |||
OBJECT IDENTIFIER ::= { mplsIdConformance 1 } | OBJECT IDENTIFIER ::= { mplsIdConformance 1 } | |||
skipping to change at page 20, line 42 | skipping to change at page 20, line 47 | |||
mplsLsrExtStdMIB MODULE-IDENTITY | mplsLsrExtStdMIB MODULE-IDENTITY | |||
LAST-UPDATED | LAST-UPDATED | |||
"201106160000Z" -- June 16, 2011 | "201106160000Z" -- June 16, 2011 | |||
ORGANIZATION | ORGANIZATION | |||
"Multiprotocol Label Switching (MPLS) Working Group" | "Multiprotocol Label Switching (MPLS) Working Group" | |||
CONTACT-INFO | CONTACT-INFO | |||
" | " | |||
Venkatesan Mahalingam | Venkatesan Mahalingam | |||
Aricent, | Aricent, | |||
India | India | |||
Email: venkatesan.mahalingam@aricent.com | Email: venkat.mahalingams@gmail.com | |||
Kannan KV Sampath | Kannan KV Sampath | |||
Aricent, | Aricent, | |||
India | India | |||
Email: Kannan.Sampath@aricent.com | Email: Kannan.Sampath@aricent.com | |||
Sam Aldrin | Sam Aldrin | |||
Huawei Technologies | Huawei Technologies | |||
2330 Central Express Way, | 2330 Central Express Way, | |||
Santa Clara, CA 95051, USA | Santa Clara, CA 95051, USA | |||
Email: aldrin.ietf@gmail.com | Email: aldrin.ietf@gmail.com | |||
Thomas D. Nadeau | Thomas D. Nadeau | |||
CA Technologies | CA Technologies | |||
273 Corporate Drive, Portsmouth, NH, USA | 273 Corporate Drive, Portsmouth, NH, USA | |||
skipping to change at page 25, line 22 | skipping to change at page 25, line 29 | |||
mplsTeExtStdMIB MODULE-IDENTITY | mplsTeExtStdMIB MODULE-IDENTITY | |||
LAST-UPDATED | LAST-UPDATED | |||
"201106160000Z" -- June 16, 2011 | "201106160000Z" -- June 16, 2011 | |||
ORGANIZATION | ORGANIZATION | |||
"Multiprotocol Label Switching (MPLS) Working Group" | "Multiprotocol Label Switching (MPLS) Working Group" | |||
CONTACT-INFO | CONTACT-INFO | |||
" | " | |||
Venkatesan Mahalingam | Venkatesan Mahalingam | |||
Aricent, | Aricent, | |||
India | India | |||
Email: venkatesan.mahalingam@aricent.com | Email: venkat.mahalingams@gmail.com | |||
Kannan KV Sampath | Kannan KV Sampath | |||
Aricent, | Aricent, | |||
India | India | |||
Email: Kannan.Sampath@aricent.com | Email: Kannan.Sampath@aricent.com | |||
Sam Aldrin | Sam Aldrin | |||
Huawei Technologies | Huawei Technologies | |||
2330 Central Express Way, | 2330 Central Express Way, | |||
skipping to change at page 37, line 19 | skipping to change at page 37, line 35 | |||
these objects and possibly to even encrypt the values of these | these objects and possibly to even encrypt the values of these | |||
objects when sending them over the network via SNMP. These are | objects when sending them over the network via SNMP. These are | |||
the tables and objects and their sensitivity/vulnerability: | the tables and objects and their sensitivity/vulnerability: | |||
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), | |||
even then, there is no control as to who on the secure network is | even then, there is no control as to who on the secure network is | |||
allowed to access and GET/SET (read/change/create/delete) | allowed to access and GET/SET (read/change/create/delete) | |||
the objects in this MIB module. | the objects in this MIB module. | |||
It is RECOMMENDED that implementers consider the security | It is RECOMMENDED that implementers consider the security features | |||
features as provided by the SNMPv3 framework (see [RFC3410], | as provided by the SNMPv3 framework (see [RFC3410], section 8), | |||
section 8), including full supports for the SNMPv3 cryptographic | including full supports for the SNMPv3 cryptographic mechanisms | |||
mechanisms (for authentication and privacy). | (for authentication and privacy). | |||
Further, deployment of SNMP versions prior to SNMPv3 is NOT | Further, deployment of SNMP versions prior to SNMPv3 is NOT | |||
RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to | RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to | |||
enable cryptographic security. It is then a customer/operator | enable cryptographic security. It is then a customer/operator | |||
responsibility to ensure that the SNMP entity giving access to an | responsibility to ensure that the SNMP entity giving access to an | |||
instance of this MIB module is properly configured to give | instance of this MIB module is properly configured to give | |||
access to the objects only to those principles (users) that | access to the objects only to those principles (users) that | |||
have legitimate rights to indeed GET or SET (change/create/delete) | have legitimate rights to indeed GET or SET (change/create/delete) | |||
them. | them. | |||
skipping to change at page 39, line 4 | skipping to change at page 39, line 23 | |||
Sam Aldrin | Sam Aldrin | |||
Huawei Technologies | Huawei Technologies | |||
2330 Central Express Way, | 2330 Central Express Way, | |||
Santa Clara, CA 95051, USA | Santa Clara, CA 95051, USA | |||
Email: aldrin.ietf@gmail.com | Email: aldrin.ietf@gmail.com | |||
Thomas D. Nadeau | Thomas D. Nadeau | |||
CA Technologies | CA Technologies | |||
273 Corporate Drive, Portsmouth, NH, USA | 273 Corporate Drive, Portsmouth, NH, USA | |||
Email: thomas.nadeau@ca.com | Email: thomas.nadeau@ca.com | |||
Venkatesan Mahalingam | Venkatesan Mahalingam | |||
Aricent | Aricent | |||
India | India | |||
Email: venkatesan.mahalingam@aricent.com | Email: venkat.mahalingams@gmail.com | |||
Kannan KV Sampath | Kannan KV Sampath | |||
Aricent | Aricent | |||
India | India | |||
Email: Kannan.Sampath@aricent.com | Email: Kannan.Sampath@aricent.com | |||
End of changes. 17 change blocks. | ||||
25 lines changed or deleted | 26 lines changed or added | |||
This html diff was produced by rfcdiff 1.41. The latest version is available from http://tools.ietf.org/tools/rfcdiff/ |