idnits 2.17.1 draft-ietf-pwe3-pw-mpls-mib-10.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** It looks like you're using RFC 3978 boilerplate. You should update this to the boilerplate described in the IETF Trust License Policy document (see https://trustee.ietf.org/license-info), which is required now. -- Found old boilerplate from RFC 3978, Section 5.1 on line 16. -- Found old boilerplate from RFC 3978, Section 5.5 on line 1390. -- Found old boilerplate from RFC 3979, Section 5, paragraph 1 on line 1401. -- Found old boilerplate from RFC 3979, Section 5, paragraph 2 on line 1408. -- Found old boilerplate from RFC 3979, Section 5, paragraph 3 on line 1414. ** This document has an original RFC 3978 Section 5.4 Copyright Line, instead of the newer IETF Trust Copyright according to RFC 4748. ** This document has an original RFC 3978 Section 5.5 Disclaimer, instead of the newer disclaimer which includes the IETF Trust according to RFC 4748. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- == There are 2 instances of lines with non-RFC6890-compliant IPv4 addresses in the document. If these are example addresses, they should be changed. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the RFC 3978 Section 5.4 Copyright Line does not match the current year == Line 222 has weird spacing: '...N |PWin inSeg...' == Line 226 has weird spacing: '...| inSeg outSe...' == The document seems to use 'NOT RECOMMENDED' as an RFC 2119 keyword, but does not include the phrase in its RFC 2119 key words list. -- The document seems to lack a disclaimer for pre-RFC5378 work, but may have content which was first submitted before 10 November 2008. If you have contacted all the original authors and they are all willing to grant the BCP78 rights to the IETF Trust, then this is fine, and you can ignore this comment. If not, you may need to add the pre-RFC5378 disclaimer. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- The document date (October 22, 2006) is 6368 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) == Missing Reference: 'RFCXXXX' is mentioned on line 353, but not defined -- Possible downref: Non-RFC (?) normative reference: ref. 'PWMIB' -- Possible downref: Non-RFC (?) normative reference: ref. 'PWTC' ** Downref: Normative reference to an Informational RFC: RFC 3916 ** Downref: Normative reference to an Informational RFC: RFC 3985 ** Obsolete normative reference: RFC 4447 (Obsoleted by RFC 8077) Summary: 6 errors (**), 0 flaws (~~), 6 warnings (==), 9 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Pseudo-Wire Edge-to-Edge Emulation D. Zelig, Ed. 3 Internet-Draft Corrigent Systems 4 Intended status: Standards Track T. Nadeau, Ed. 5 Expires: April 25, 2007 Cisco Systems, Inc. 6 October 22, 2006 8 Pseudo-Wire (PW) over MPLS PSN Management Information Base 9 draft-ietf-pwe3-pw-mpls-mib-10 11 Status of this Memo 13 By submitting this Internet-Draft, each author represents that any 14 applicable patent or other IPR claims of which he or she is aware 15 have been or will be disclosed, and any of which he or she becomes 16 aware will be disclosed, in accordance with Section 6 of BCP 79. 18 Internet-Drafts are working documents of the Internet Engineering 19 Task Force (IETF), its areas, and its working groups. Note that 20 other groups may also distribute working documents as Internet- 21 Drafts. 23 Internet-Drafts are draft documents valid for a maximum of six months 24 and may be updated, replaced, or obsoleted by other documents at any 25 time. It is inappropriate to use Internet-Drafts as reference 26 material or to cite them other than as "work in progress." 28 The list of current Internet-Drafts can be accessed at 29 http://www.ietf.org/ietf/1id-abstracts.txt. 31 The list of Internet-Draft Shadow Directories can be accessed at 32 http://www.ietf.org/shadow.html. 34 This Internet-Draft will expire on April 25, 2007. 36 Copyright Notice 38 Copyright (C) The Internet Society (2006). 40 Abstract 42 This memo defines an experimental portion of the Management 43 Information Base (MIB) for use with network management protocols in 44 the Internet community. In particular, it describes a MIB module for 45 PW operation over Multi-Protocol Label Switching (MPLS) Label Switch 46 Router (LSR). 48 Table of Contents 50 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 51 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3 52 3. The Internet-Standard Management Framework . . . . . . . . . . 4 53 4. Feature Checklist . . . . . . . . . . . . . . . . . . . . . . 4 54 5. MIB Module Usage . . . . . . . . . . . . . . . . . . . . . . . 4 55 5.1. PW MIB Modules Usage . . . . . . . . . . . . . . . . . . . 5 56 5.2. PW MPLS MIB Module Usage . . . . . . . . . . . . . . . . . 5 57 5.3. PW MPLS MIB Example . . . . . . . . . . . . . . . . . . . 7 58 6. Object Definitions . . . . . . . . . . . . . . . . . . . . . . 8 59 7. Security Considerations . . . . . . . . . . . . . . . . . . . 27 60 8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 28 61 9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 28 62 9.1. Normative References . . . . . . . . . . . . . . . . . . . 28 63 9.2. Informative References . . . . . . . . . . . . . . . . . . 30 64 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 30 65 Intellectual Property and Copyright Statements . . . . . . . . . . 31 67 1. Introduction 69 This document describes a model for managing pseudo-wire services for 70 transmission over different flavors of MPLS tunnels. The general PW 71 MIB module [PWMIB] defines the parameters global to the PW regardless 72 of underlying PSN and emulated service. Indicating PSN type of MPLS 73 in PW-MIB references this module. 75 This document describes the MIB objects that define pseudo-wire 76 association to the MPLS PSN, in a way that is not specific to the 77 carried service. 79 Together, [RFC3811] and [RFC3812], describe the modeling of an MPLS 80 Tunnel, and a Tunnel's underlying cross-connects. This MIB module 81 supports MPLS-TE PSN, Non TE MPLS PSN (an outer tunnel created by LDP 82 or manually), and MPLS PW label only (no outer tunnel). 84 Comments should be made directly to the PWE3 mailing list at 85 pwe3@ietf.org. 87 Conventions used in this document: 89 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 90 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 91 document are to be interpreted as described in RFC-2119 [BCP14]. 93 2. Terminology 95 This document uses terminology from the document describing the PW 96 architecture [RFC3985], [RFC3916] and [RFC4447]. 98 The terms "Outbound" and "Inbound" in this MIB module are based on 99 the common practice in the MPLS standards, i.e. "outbound" are toward 100 the PSN. However, where these terms are used in an object name, the 101 object description clarifies the exact packet direction to prevent 102 confusion with these terms in other documents. 104 "PSN Tunnel" is a general term indicating a virtual connection 105 between the two PWE3 edge devices. Each tunnel may potentially carry 106 multiple PWs inside. In the scope of this document, it is an MPLS 107 tunnel. 109 This document uses terminology from the document describing the MPLS 110 architecture [RFC3031] for MPLS PSN. A Label Switched Path (LSP) is 111 modeled as described in [RFC3811] and [RFC3812] via a series of 112 cross-connects through 1 or more Label Switch Routers (LSR). 114 In MPLS PSN, a PW connection typically uses a PW Label within a 115 Tunnel Label [RFC4447]. Multiple pseudo-wires each with a unique PW 116 Label can share the same Tunnel. For PW transport over MPLS, the 117 Tunnel Label is known as the "outer" Label, while the PW Label is 118 known as the "inner" Label. An exception to this is with adjacent 119 LSRs or the use of PHP. In this case, there is an option for PWs to 120 connect directly without an outer Label. 122 3. The Internet-Standard Management Framework 124 For a detailed overview of the documents that describe the current 125 Internet-Standard Management Framework, please refer to section 7 of 126 [RFC3410]. 128 Managed objects are accessed via a virtual information store, termed 129 the Management Information Base or MIB. MIB objects are generally 130 accessed through the Simple Network Management Protocol (SNMP). 131 Objects in the MIB are defined using the mechanisms defined in the 132 Structure of Management Information (SMI). This memo specifies a MIB 133 module that is compliant to the SMIv2, which is described in STD 134 58,[RFC2578], STD 58, [RFC2579] and STD 58, [RFC2580]. 136 4. Feature Checklist 138 The PW-MPLS-STD-MIB module is designed to satisfy the following 139 requirements and constraints: 141 - The MIB module supports both manually configured and signaled PWs. 143 - The MIB module supports point-to-point PW connections. 145 - The MIB module enables the use of any emulated service. 147 - The MIB module supports MPLS-TE outer tunnel, Non TE MPLS outer 148 tunnel (an outer tunnel signaled by LDP or set-up manually), and 149 no outer tunnel (where the PW label is the only label in the 150 incoming MPLS stack). The later case is applicable for manual 151 configuration of PW over a single hop (in multiple-hops cases, it 152 is required to have an outer MPLS tunnel). 154 5. MIB Module Usage 155 5.1. PW MIB Modules Usage 157 The MIB module structure for defining a PW service is composed of 158 three layers of MIB modules functioning together. This general model 159 is defined in the PWE3 architecture [RFC3985]. The layering model is 160 intended to sufficiently isolate PW services from the underlying PSN 161 layer that carries the emulated service. This is done at the same 162 time as providing a standard means for connecting any supported 163 services to any supported PSNs. 165 The first layer, known as the service layer, contains service- 166 specific modules These modules define service-specific management 167 objects that interface or collaborate with existing MIB modules for 168 the native version of the service. The service-specific module 169 "glues" the standard modules to the PWE3 MIB modules. 171 The next layer of the PWE3 MIB framework is the PW MIB module 172 [PWMIB]. This module is used to configure general parameters of PWs 173 that are common to all types of emulated services and PSNs. This 174 layer is connected to the service-specific layer above, and the PSN 175 layer below. 177 The PSN layer provides PSN-specific modules for each type of PSN. 178 These modules associate the PW with one or more "tunnels" that carry 179 the service over the PSN. These modules are used to "glue" the PW 180 service to the underlying PSN-specific MIB modules. This document 181 defines the MIB module for PW over MPLS PSN. 183 [PWTC] defines some of the object types used in these modules. 185 5.2. PW MPLS MIB Module Usage 187 - The PW table (pwTable) in [PWMIB] is used for all PW types (ATM, 188 FR, Ethernet, SONET, etc.). This table contains high level 189 generic parameters related to the PW creation. The operator or 190 the agent creates a row for each PW. 192 - If the selected PSN type in pwTable is MPLS, the agent creates a 193 row in the MPLS specific parameters table (pwMplsTable) in this 194 module, which contains MPLS specific parameters such as EXP bits 195 handling and outer tunnel configuration. 197 - The operator configures the association to the desired MPLS tunnel 198 (require for MPLS TE tunnels or manually configured PWs) through 199 the pwMplsTeOutbaoundTable. For LDP based outer tunnel, there is 200 no need for manual configuration since there is only a single 201 tunnel toward the peer. 203 - The agent creates rows in the MPLS mapping table in order to allow 204 quick retrieval of information based on the tunnel indexes. 206 The relation to the MPLS network is by configuration of the edge LSR 207 only - i.e. the LSR which provides the PW function. Since Tunnels 208 are uni-directional, a pair of tunnels must exist (one for inbound, 209 one for outbound). Figure 1 depicts a PW that originates and 210 terminates at LSR-M. It uses LSPs A and B formed by Tunnels Ax and 211 Bx continuing through LSR-N to LSR-P. The concatenations of Tunnels 212 create the LSPs. Note: 'X' denotes a Tunnel's cross-connect. 214 LSP-A 215 <- - - - - - - - - - - - - - - - - - - - - - - - - - - - 217 +---- (edge) LSR-M ---+ +--------- LSR-N ---------+ + LSR-P 218 |---+ | | | | 219 | | Tunnel | | Tunnel | | 220 + | A1 (M<-N) +----+ +----+ A2 (M<-P) +----+ +----+ 221 | | <------| | | |<--------------| | | | 222 <-->| N |PWin inSeg |MPLS| |MPLS| outSeg inSeg |MPLS| |MPLS| 223 N S | | <---X<-----| IF | | IF |<------X<------| IF | | IF | 224 A E | S | | |<-->| | | |<-->| | | 225 T R | | --->X----->| | | |------>X------>| | | | 226 I V | P |PWout outSeg| | | | inSeg outSeg | | | | 227 V I | | ------>| | | |-------------->| | | | 228 E C + | Tunnel +----+ +----+ Tunnel +----+ +----+ 229 E |---+ B1 (M->N) | | B2 (M->P) | | 230 | | | | | 231 +---------------------+ +-------------------------+ +----- 233 - - - - - - - - - - - - - - - - - - - - - - - - - - - -> 234 LSP-B 236 Figure 1: PW modeling over MPLS 238 The PW-MPLS-STD-MIB supports three options for MPLS network: 240 (1) In the MPLS-TE case, Tunnel A1 and B1 are created via the MPLS- 241 TE-STD-MIB [RFC3812]. The tunnels are associated to the PW by 242 the four indexes that uniquely identify the Tunnel at the MPLS- 243 TE-STD-MIB. 245 (2) In the Non-TE case, Tunnel A1 and B1 are either manually 246 configured or set up with LDP. The tunnels are associated to 247 the PW by the XC index in the MPLS-LSR-STD-MIB [RFC3813]. 249 (3) In the PW label only case, there is no outer tunnel on top of 250 the PW label. This case is useful in case of adjacent PEs in 251 manual configuration mode. Note that when LSR-N acts as PHP for 252 the outer tunnel label, there are still entries for the outer 253 tunnel in the relevant MPLS MIB modules. 255 A combination of MPLS-TE outer tunnel(s) and LDP outer tunnel for the 256 same PW is allowed through the pwMplsOutboundTunnel. The current 257 tunnel that is used to forward traffic is indicated in the object 258 pwMplsOutboundTunnelTypeInUse. 260 The PW MPLS MIB module reports through the inbound table the XC entry 261 in the LDP-STD-MIB [RFC3815] of the PW that were signaled through 262 LDP. 264 This MIB module assumes that a PW can be associated to one MPLS-TE 265 tunnel at a time. This tunnel may be composed of multiple instances 266 (i.e. LSP), each represented by a separate instance index. The 267 current active LSP is reported through this MIB module. 269 It is worth noting that inbound (tunnel originated in the remote PE) 270 mapping is not configured nor reported through the PW-MPLS-STD-MIB 271 module since the local PE does not know the inbound association 272 between specific PW and MPLS tunnels. 274 5.3. PW MPLS MIB Example 276 In this example, a PW has been configured in the pwTbale in [PWMIB] 277 with pwPsnType equal 'mpls', and we assume that the implementation in 278 this example has already an LDP tunnel to the peer node. 280 The agent creates an entry in pwMplsTable with the following 281 paramters: 283 pwMplsMplsType mplsNonTe(1), -- LDP tunnel 284 pwMplsExpBitsMode outerTunnel(1), -- Default 285 pwMplsExpBits 0, -- Default 286 pwMplsTtl 2, -- Default 287 pwMplsLocalLdpID 1.4.1.1:0, 288 pwMplsLocalLdpEntityIndex 1, 289 pwMplsPeerLdpID 1.4.3.2:0, 290 pwMplsStorageType StorageType 292 The agent also creats an entry in pwMplsOutboundTable for reporting 293 the mapping of the PW on the LDP tunnel: 295 pwMplsOutboundLsrXcIndex 100, - The XC number for the 296 -- LDP Tunnel 297 pwMplsOutboundTunnelIndex 0, -- No TE tunnel 298 pwMplsOutboundTunnelInstance 0, -- No TE tunnel 299 pwMplsOutboundTunnelLclLSR 0, -- No TE tunnel 300 pwMplsOutboundTunnelPeerLSR 0, -- No TE tunnel 301 pwMplsOutboundIfIndex 0, -- Not applicable 302 pwMplsOutboundTunnelTypeInUse mplsNonTe(3) 304 The agent now creates entries for the PW in the following tables: 306 - pwMplsInboundTable 308 - pwMplsNonTeMappingTable (2 entries) 310 To create an MPLS TE tunnel to carry this PW, the operator make the 311 following steps: 313 - Set pwMplsMplsType in pwMplsTable to both mplsNonTe(1) and 314 mplsTe(0). 316 - Set pwMplsOutboundTunnelIndex, pwMplsOutboundTunnelInstance, 317 pwMplsOutboundTunnelLclLSR and pwMplsOutboundTunnelPeerLSR in 318 pwMplsOutboundTable to the MPLS TE tunnel that will carry this PW. 320 The agent will report the tunnel which the PW is currently using 321 through pwMplsOutboundTunnelTypeInUse, and will report the PW to MPLS 322 TE tunnel/LSP mapping in pwMplsTeMappingTable. 324 6. Object Definitions 326 PW-MPLS-STD-MIB DEFINITIONS ::= BEGIN 328 IMPORTS 329 MODULE-IDENTITY, OBJECT-TYPE, Unsigned32, transmission 330 FROM SNMPv2-SMI -- [RFC2578] 332 MODULE-COMPLIANCE, OBJECT-GROUP 333 FROM SNMPv2-CONF -- [RFC2580] 335 StorageType 336 FROM SNMPv2-TC -- [RFC2579] 338 InterfaceIndexOrZero 339 FROM IF-MIB -- [RFC2863] 341 MplsTunnelIndex, MplsTunnelInstanceIndex, 342 MplsLdpIdentifier, MplsLsrIdentifier 343 FROM MPLS-TC-STD-MIB -- [RFC3811] 345 MplsIndexType 346 FROM MPLS-LSR-STD-MIB -- [RFC3813] 348 PwIndexType 349 FROM PW-TC-STD-MIB -- [RFCXXXX] 350 -- RFC Editor: Please replace XXXX with the RFC number and remove 351 -- this note. 353 pwIndex -- [RFCXXXX] 354 -- RFC Editor: Please replace XXXX with the RFC number and remove 355 -- this note. 356 FROM PW-STD-MIB 358 ; 360 pwMplsStdMIB MODULE-IDENTITY 361 LAST-UPDATED "200610221200Z" -- 22 October 2006 12:00:00 GMT 362 ORGANIZATION "Pseudo-Wire Edge-to-Edge Emulation (PWE3) Working 363 Group." 364 CONTACT-INFO 365 " 366 David Zelig, Editor 367 E-mail: davidz@corrigent.com 369 Thomas D. Nadeau, Editor 370 Email: tnadeau@cisco.com 372 The PWE3 Working Group (email distribution pwe3@ietf.org, 373 http://www.ietf.org/html.charters/pwe3-charter.html) 374 " 375 DESCRIPTION 376 "This MIB module complements the PW-STD-MIB module for PW 377 operation over MPLS. 379 Copyright (C) The Internet Society (2006). This version 380 of this MIB module is part of RFC yyyy; see the RFC 381 itself for full legal notices. 382 -- RFC Ed.: replace yyyy with actual RFC number & remove 383 -- this note 384 " 385 -- Revision history. 386 REVISION "200610221200Z" -- 22 October 2006 12:00:00 GMT 387 DESCRIPTION 388 "First published as RFCWXYZ. " 390 -- RFC Editor: Please replace WXYZ with the correct # and remove this 391 -- note 393 ::= { transmission XXX } 394 -- RFC Editor: To be assigned by IANA. Please replace XXX 395 -- with the assigned value and remove this note. 397 -- Top-level components of this MIB. 399 -- Notifications 400 pwMplsNotifications OBJECT IDENTIFIER 401 ::= { pwMplsStdMIB 0 } 403 -- Tables, Scalars 404 pwMplsObjects OBJECT IDENTIFIER 405 ::= { pwMplsStdMIB 1 } 406 -- Conformance 407 pwMplsConformance OBJECT IDENTIFIER 408 ::= { pwMplsStdMIB 2 } 410 -- PW MPLS table 412 pwMplsTable OBJECT-TYPE 413 SYNTAX SEQUENCE OF PwMplsEntry 414 MAX-ACCESS not-accessible 415 STATUS current 416 DESCRIPTION 417 "This table controls MPLS specific parameters when the PW is 418 going to be carried over MPLS PSN." 419 ::= { pwMplsObjects 1 } 421 pwMplsEntry OBJECT-TYPE 422 SYNTAX PwMplsEntry 423 MAX-ACCESS not-accessible 424 STATUS current 425 DESCRIPTION 426 "A row in this table represents parameters specific to MPLS 427 PSN for a pseudo-wire (PW). The row is created 428 automatically by the local agent if the pwPsnType is 429 MPLS. It is indexed by pwIndex, which uniquely 430 identifying a singular PW. 431 " 432 INDEX { pwIndex } 434 ::= { pwMplsTable 1 } 436 PwMplsEntry ::= SEQUENCE { 437 pwMplsMplsType BITS, 438 pwMplsExpBitsMode INTEGER, 439 pwMplsExpBits Unsigned32, 440 pwMplsTtl Unsigned32, 441 pwMplsLocalLdpID MplsLdpIdentifier, 442 pwMplsLocalLdpEntityIndex Unsigned32, 443 pwMplsPeerLdpID MplsLdpIdentifier, 444 pwMplsStorageType StorageType 445 } 447 pwMplsMplsType OBJECT-TYPE 448 SYNTAX BITS { 449 mplsTe (0), 450 mplsNonTe (1), 451 pwOnly (2) 452 } 453 MAX-ACCESS read-write 454 STATUS current 455 DESCRIPTION 456 "Set by the operator to indicate the outer tunnel types, if 457 exists. mplsTe(0) is used if the outer tunnel was set up 458 by MPLS-TE, and mplsNonTe(1) is used if the outer tunnel was 459 set up by LDP or manually. Combination of mplsTe(0) and 460 mplsNonTe(1) may exist together. 461 pwOnly(2) is used if there is no outer tunnel label, i.e. 462 in static provisioning without an MPLS tunnel. pwOnly(2) 463 cannot be combined with mplsNonTe(1) or mplsTe(0)." 464 DEFVAL { { mplsNonTe } } 465 ::= { pwMplsEntry 1 } 467 pwMplsExpBitsMode OBJECT-TYPE 468 SYNTAX INTEGER { 469 outerTunnel (1), 470 specifiedValue (2), 471 serviceDependant (3) 472 } 474 MAX-ACCESS read-write 475 STATUS current 476 DESCRIPTION 477 "Set by the operator to indicate the way the PW shim label 478 EXP bits are to be determined. The value of outerTunnel(1) 479 is used where there is an outer tunnel - pwMplsMplsType 480 is mplsTe(0) or mplsNonTe(1). Note that in this case there 481 is no need to mark the PW label with the EXP bits since the 482 PW label is not visible to the intermediate nodes. 483 If there is no outer tunnel, specifiedValue(2) indicates 484 that the value is specified by pwMplsExpBits, and 485 serviceDependant(3) indicates that the EXP bits are set 486 based on a rule which is implementation specific." 488 DEFVAL { outerTunnel } 489 ::= { pwMplsEntry 2 } 491 pwMplsExpBits OBJECT-TYPE 492 SYNTAX Unsigned32 (0..7) 493 MAX-ACCESS read-write 494 STATUS current 495 DESCRIPTION 496 "Set by the operator to indicate the MPLS EXP bits to be 497 used on the PW shim label if pwMplsExpBitsMode is 498 specifiedValue(2), zero otherwise." 499 DEFVAL { 0 } 500 ::= { pwMplsEntry 3 } 502 pwMplsTtl OBJECT-TYPE 503 SYNTAX Unsigned32 (0..255) 504 MAX-ACCESS read-write 505 STATUS current 506 DESCRIPTION 507 "Set by the operator to indicate the PW TTL value to be 508 used on the PW shim label." 509 DEFVAL { 2 } 510 ::= { pwMplsEntry 4 } 512 pwMplsLocalLdpID OBJECT-TYPE 513 SYNTAX MplsLdpIdentifier 514 MAX-ACCESS read-write 515 STATUS current 516 DESCRIPTION 517 "The local LDP identifier of the LDP entity creating 518 this PW in the local node. As the PW labels are always 519 set from the per-platform label space, the last two octets 520 in the LDP ID MUST always both be zeros." 521 REFERENCE 522 "'LDP specifications', RFC 3036 section 2.2.2." 523 ::= { pwMplsEntry 5 } 525 pwMplsLocalLdpEntityIndex OBJECT-TYPE 526 SYNTAX Unsigned32 (1..4294967295) 527 MAX-ACCESS read-write 528 STATUS current 529 DESCRIPTION 530 "The local node LDP Entity Index of the LDP entity creating 531 this PW." 532 ::= { pwMplsEntry 6 } 534 pwMplsPeerLdpID OBJECT-TYPE 535 SYNTAX MplsLdpIdentifier 536 MAX-ACCESS read-only 537 STATUS current 538 DESCRIPTION 539 "The peer LDP identifier as identified from the LDP 540 session. Should return the value of zero if not applicable 541 or not known yet." 542 ::= { pwMplsEntry 7 } 544 pwMplsStorageType OBJECT-TYPE 545 SYNTAX StorageType 546 MAX-ACCESS read-write 547 STATUS current 548 DESCRIPTION 549 "This variable indicates the storage type for this row." 550 ::= { pwMplsEntry 8 } 552 -- End of PW MPLS Table 554 -- Pseudo-Wire MPLS Outbound Tunnel Table 556 pwMplsOutboundTable OBJECT-TYPE 557 SYNTAX SEQUENCE OF PwMplsOutboundEntry 558 MAX-ACCESS not-accessible 559 STATUS current 560 DESCRIPTION 561 "This table reports and configures the current outbound MPLS 562 tunnels (i.e. toward the PSN) or the physical interface in 563 the case of a PW label only that carries the PW traffic. It 564 also reports the current outer tunnel and LSP which forward 565 the PW traffic." 566 ::= { pwMplsObjects 2 } 568 pwMplsOutboundEntry OBJECT-TYPE 569 SYNTAX PwMplsOutboundEntry 570 MAX-ACCESS not-accessible 571 STATUS current 572 DESCRIPTION 573 "A row in this table configures the outer tunnel used for 574 carrying the PW traffic toward the PSN. 575 In the case of PW labels only, it configures the interface 576 that will carry the PW traffic. 578 An entry in this table augments the pwMplsEntry, and is 579 created automatically when the corresponding row has been 580 created by the agent in the pwMplsEntry. 582 This table points to the appropriate MPLS MIB module. 583 In the MPLS-TE case, the three variables relevant to the 584 indexing of a TE tunnel head-end (as used in the 585 MPLS-TE-STD-MIB) are to be configured, and the tunnel 586 instance indicates the LSP that is currently in use for 587 forwarding the traffic. 589 In case of signaled Non-TE MPLS (an outer tunnel label 590 assigned by LDP) the table points to the XC entry in the 591 LSR-STD-MIB. If the Non-TE MPLS tunnel is manually 592 configured, the operator configures the XC pointer to this 593 tunnel. 595 In case of PW label only (no outer tunnel) the ifIndex of 596 the port to carry the PW is configured here. 598 It is possible to associate a PW to one TE tunnel head-end 599 and a non-TE tunnel together. An indication in this table 600 will report the currently active one. In addition, in the 601 TE case the table reports the active tunnel instance 602 (i.e. the specific LSP in use). 603 " 605 AUGMENTS { pwMplsEntry } 607 ::= { pwMplsOutboundTable 1 } 609 PwMplsOutboundEntry ::= SEQUENCE { 610 pwMplsOutboundLsrXcIndex MplsIndexType, 611 pwMplsOutboundTunnelIndex MplsTunnelIndex, 612 pwMplsOutboundTunnelInstance MplsTunnelInstanceIndex, 613 pwMplsOutboundTunnelLclLSR MplsLsrIdentifier, 614 pwMplsOutboundTunnelPeerLSR MplsLsrIdentifier, 615 pwMplsOutboundIfIndex InterfaceIndexOrZero, 616 pwMplsOutboundTunnelTypeInUse INTEGER 617 } 619 pwMplsOutboundLsrXcIndex OBJECT-TYPE 620 SYNTAX MplsIndexType 621 MAX-ACCESS read-write 622 STATUS current 623 DESCRIPTION 624 "This object is applicable if pwMplsMplsType mplsNonTe(1) 625 bit is set, and MUST return a value of zero otherwise. 626 If the outer tunnel is signaled, the object is read-only 627 and indicates the XC index in the MPLS-LSR-STD-MIB of the 628 outer tunnel toward the peer. Otherwise (tunnel is set up 629 manually) the operator defines the XC index of the manually- 630 created outer tunnel through this object. 631 " 632 ::= { pwMplsOutboundEntry 1 } 634 pwMplsOutboundTunnelIndex OBJECT-TYPE 635 SYNTAX MplsTunnelIndex 636 MAX-ACCESS read-write 637 STATUS current 638 DESCRIPTION 639 "This object is applicable if pwMplsMplsType mplsTe(0) 640 bit is set, and MUST return a value of zero otherwise. 641 It is part of the set of indexes for the outbound tunnel. 642 The operator sets this object to represent the desired 643 tunnel head-end toward the peer for carrying the PW 644 traffic. 645 " 646 ::= { pwMplsOutboundEntry 2 } 648 pwMplsOutboundTunnelInstance OBJECT-TYPE 649 SYNTAX MplsTunnelInstanceIndex 650 MAX-ACCESS read-only 651 STATUS current 652 DESCRIPTION 653 "This object is applicable if pwMplsMplsType mplsTe(0) 654 bit is set, and MUST return a value of zero otherwise. 655 It indicates the actual tunnel instance that is currently 656 active and carrying the PW traffic. It should return the 657 value of zero if the information from the MPLS-TE 658 application is not yet known. 659 " 660 ::= { pwMplsOutboundEntry 3 } 662 pwMplsOutboundTunnelLclLSR OBJECT-TYPE 663 SYNTAX MplsLsrIdentifier 664 MAX-ACCESS read-write 665 STATUS current 666 DESCRIPTION 667 "This object is applicable if pwMplsMplsType mplsTe(0) 668 bit is set, and MUST return a value of all zeros otherwise. 669 It is part of the set of indexes for the outbound tunnel. 670 The operator sets this object to represent the desired 671 tunnel head-end toward the peer for carrying the PW 672 traffic. 673 " 674 ::= { pwMplsOutboundEntry 4 } 676 pwMplsOutboundTunnelPeerLSR OBJECT-TYPE 677 SYNTAX MplsLsrIdentifier 678 MAX-ACCESS read-write 679 STATUS current 680 DESCRIPTION 681 "This object is applicable if pwMplsMplsType mplsTe(0) 682 bit is set, and MUST return a value of zero otherwise. 683 It is part of the set of indexes for the outbound tunnel. 684 It is typically equals to pwPeerAddr. 685 " 686 ::= { pwMplsOutboundEntry 5 } 688 pwMplsOutboundIfIndex OBJECT-TYPE 689 SYNTAX InterfaceIndexOrZero 690 MAX-ACCESS read-write 691 STATUS current 692 DESCRIPTION 693 "This object is applicable if pwMplsMplsType pwOnly(0) 694 bit is set, and MUST return a value of zero otherwise. 695 The operator configures the ifIndex of the outbound port 696 in this case. 697 " 698 ::= { pwMplsOutboundEntry 6 } 700 pwMplsOutboundTunnelTypeInUse OBJECT-TYPE 701 SYNTAX INTEGER { 702 notYetKnown (1), 703 mplsTe (2), 704 mplsNonTe (3), 705 pwOnly (4) 706 } 707 MAX-ACCESS read-only 708 STATUS current 709 DESCRIPTION 710 "This object indicates the current tunnel that is carrying 711 the PW traffic. 712 The value of notYetKnown(1) should be used if the agent is 713 currently unable to determine which tunnel or interface is 714 carrying the PW, for example because both tunnels are in 715 operational status down. 716 " 717 ::= { pwMplsOutboundEntry 7 } 719 -- End of PW MPLS Outbound Tunnel table 721 -- PW MPLS inbound table 723 pwMplsInboundTable OBJECT-TYPE 724 SYNTAX SEQUENCE OF PwMplsInboundEntry 725 MAX-ACCESS not-accessible 726 STATUS current 727 DESCRIPTION 728 "This table indicates the PW LDP XC entry in the 729 MPLS-LSR-STD-MIB for signaled PWs. 730 " 731 ::= { pwMplsObjects 3 } 733 pwMplsInboundEntry OBJECT-TYPE 734 SYNTAX PwMplsInboundEntry 735 MAX-ACCESS not-accessible 736 STATUS current 737 DESCRIPTION 738 "A row in this table is created by the agent 739 for each signaled PW, and shows the XC index related to 740 the PW signaling in the inbound direction in the 741 MPLS-LSR-STD-MIB that controls and display the information 742 for all the LDP signaling processes in the local node. 743 " 744 INDEX { pwIndex } 746 ::= { pwMplsInboundTable 1 } 748 PwMplsInboundEntry ::= SEQUENCE { 749 pwMplsInboundXcIndex MplsIndexType 750 } 752 pwMplsInboundXcIndex OBJECT-TYPE 753 SYNTAX MplsIndexType 754 MAX-ACCESS read-only 755 STATUS current 756 DESCRIPTION 757 "The XC index representing this PW in the inbound 758 direction. It MUST return the value of zero if the 759 information is not yet known." 760 ::= { pwMplsInboundEntry 1 } 762 -- End of PW MPLS inbound table 764 -- PW to Non-TE mapping Table. 766 pwMplsNonTeMappingTable OBJECT-TYPE 767 SYNTAX SEQUENCE OF PwMplsNonTeMappingEntry 768 MAX-ACCESS not-accessible 769 STATUS current 770 DESCRIPTION 771 "This table indicates the PW association to the outbound 772 Tunnel in non-TE applications, maps the PW to it's (inbound) 773 XC entry, and indicates the PW-to-physical interface mapping 774 for a PW without an outer tunnel. 775 " 776 ::= { pwMplsObjects 4 } 778 pwMplsNonTeMappingEntry OBJECT-TYPE 779 SYNTAX PwMplsNonTeMappingEntry 780 MAX-ACCESS not-accessible 781 STATUS current 782 DESCRIPTION 783 "A row in this table displays the association 784 between the PW and 785 - its non-TE MPLS outbound outer Tunnel or, 786 - its XC entry in the MPLS-LSR-STD-MIB, 787 - its physical interface if there is no outer tunnel 788 (PW label only) and manual configuration. 790 Rows are created in this table by the agent depending on 791 the setting of pwMplsMplsType: 793 - If pwMplsMplsType mplsNonTe(1) bit is set, the agent 794 creates a row for the outbound direction 795 (pwMplsNonTeMappingDirection set to psnBound(1)). 796 The pwMplsNonTeMappingXcIndex holds the XC index in the 797 MPLS-LSR-STD-MIB of the PSN bound outer tunnel. 798 pwMplsNonTeMappingIfIndex MUST be zero for this row. 800 - If pwMplsMplsType pwOnly(2) bit is set, the agent 801 creates a row for the outbound direction 802 (pwMplsNonTeMappingDirection set to psnBound(1)). 803 The pwMplsNonTeMappingIfIndex holds the ifIndex of the 804 physical port this PW will use in the outbound direction. 805 pwMplsNonTeMappingXcIndex MUST be zero for this row. 807 - If the PW has been set up by a signaling protocol (i.e. 808 pwOwner equal pwIdFecSignaling(2) or 809 genFecSignaling(3)), the agent creates a row for the 810 inbound direction (pwMplsNonTeMappingDirection set to 811 fromPsn(2)). 812 The pwMplsNonTeMappingXcIndex holds the XC index in the 813 MPLS-LSR-STD-MIB of the PW LDP generated XC entry. 814 pwMplsNonTeMappingIfIndex MUST be zero for this row. 816 An application can use this table to quickly retrieve the 817 PW carried over specific non-TE MPLS outer tunnel or 818 physical interface. 819 " 821 INDEX { pwMplsNonTeMappingDirection, 822 pwMplsNonTeMappingXcIndex, 823 pwMplsNonTeMappingIfIndex, 824 pwMplsNonTeMappingPwIndex } 826 ::= { pwMplsNonTeMappingTable 1 } 828 PwMplsNonTeMappingEntry ::= SEQUENCE { 829 pwMplsNonTeMappingDirection INTEGER, 830 pwMplsNonTeMappingXcIndex MplsIndexType, 831 pwMplsNonTeMappingIfIndex InterfaceIndexOrZero, 832 pwMplsNonTeMappingPwIndex PwIndexType 833 } 835 pwMplsNonTeMappingDirection OBJECT-TYPE 836 SYNTAX INTEGER { 837 psnBound (1), 838 fromPsn (2) 839 } 840 MAX-ACCESS not-accessible 841 STATUS current 842 DESCRIPTION 843 "Index for the conceptual XC row identifying the tunnel-to-PW 844 mappings, indicating the direction of the packet flow for 845 this entry. 846 psnBound(1) indicates that the entry is related to 847 packets toward the PSN. 848 fromPsn(2) indicates that the entry is related to 849 packets coming from the PSN. 850 " 851 ::= { pwMplsNonTeMappingEntry 1 } 853 pwMplsNonTeMappingXcIndex OBJECT-TYPE 854 SYNTAX MplsIndexType 855 MAX-ACCESS not-accessible 856 STATUS current 857 DESCRIPTION 858 "See the description clause of pwMplsNonTeMappingEntry for 859 the usage guidelines of this object." 860 ::= { pwMplsNonTeMappingEntry 2 } 862 pwMplsNonTeMappingIfIndex OBJECT-TYPE 863 SYNTAX InterfaceIndexOrZero 864 MAX-ACCESS not-accessible 865 STATUS current 866 DESCRIPTION 867 "See the description clause of pwMplsNonTeMappingEntry for 868 the usage guidelines of this object." 870 ::= { pwMplsNonTeMappingEntry 3 } 872 pwMplsNonTeMappingPwIndex OBJECT-TYPE 873 SYNTAX PwIndexType 874 MAX-ACCESS read-only 875 STATUS current 876 DESCRIPTION 877 "The value that represent the PW in the pwTable." 878 ::= { pwMplsNonTeMappingEntry 4 } 880 -- End of PW to Non-TE mapping Table. 882 -- PW to TE MPLS tunnels mapping Table. 884 pwMplsTeMappingTable OBJECT-TYPE 885 SYNTAX SEQUENCE OF PwMplsTeMappingEntry 886 MAX-ACCESS not-accessible 887 STATUS current 888 DESCRIPTION 889 "This table enable the retrieval of a PW association to the 890 outbound MPLS tunnel for MPLS-TE applications." 891 ::= { pwMplsObjects 5 } 893 pwMplsTeMappingEntry OBJECT-TYPE 894 SYNTAX PwMplsTeMappingEntry 895 MAX-ACCESS not-accessible 896 STATUS current 897 DESCRIPTION 898 "A row in this table represents the association 899 between a PW and its MPLS-TE outer (head-end) Tunnel. 901 An application can use this table to quickly retrieve the 902 list of the PWs that are configured on a specific MPLS TE 903 outer tunnel. 905 The pwMplsTeMappingTunnelInstance reports the actual 906 LSP out of the tunnel head-end that is currently 907 forwarding the traffic. 909 The table in indexed by the head-end indexes of a TE 910 tunnel and the PW index. 911 " 913 INDEX { pwMplsTeMappingTunnelIndex, 914 pwMplsTeMappingTunnelInstance, 915 pwMplsTeMappingTunnelPeerLsrID, 916 pwMplsTeMappingTunnelLocalLsrID, 917 pwMplsTeMappingPwIndex } 919 ::= { pwMplsTeMappingTable 1 } 921 PwMplsTeMappingEntry ::= SEQUENCE { 922 pwMplsTeMappingTunnelIndex MplsTunnelIndex, 923 pwMplsTeMappingTunnelInstance MplsTunnelInstanceIndex, 924 pwMplsTeMappingTunnelPeerLsrID MplsLsrIdentifier, 925 pwMplsTeMappingTunnelLocalLsrID MplsLsrIdentifier, 926 pwMplsTeMappingPwIndex PwIndexType 927 } 929 pwMplsTeMappingTunnelIndex OBJECT-TYPE 930 SYNTAX MplsTunnelIndex 931 MAX-ACCESS not-accessible 932 STATUS current 933 DESCRIPTION 934 "Primary index for the conceptual row identifying the 935 MPLS-TE tunnel that is carrying the PW traffic." 936 ::= { pwMplsTeMappingEntry 1 } 938 pwMplsTeMappingTunnelInstance OBJECT-TYPE 939 SYNTAX MplsTunnelInstanceIndex 940 MAX-ACCESS not-accessible 941 STATUS current 942 DESCRIPTION 943 "This object identify the MPLS-TE LSP that is carrying the 944 PW traffic. It MUST return the value of zero if the 945 information of the specific LSP is not yet known. 946 Note that based on the recommendation in the 947 MPLS-TC-STD-MIB, instance index 0 should refer to the 948 configured tunnel interface." 949 ::= { pwMplsTeMappingEntry 2 } 951 pwMplsTeMappingTunnelPeerLsrID OBJECT-TYPE 952 SYNTAX MplsLsrIdentifier 953 MAX-ACCESS not-accessible 954 STATUS current 955 DESCRIPTION 956 "Identifies the Peer LSR when the outer tunnel is MPLS-TE 957 based." 958 ::= { pwMplsTeMappingEntry 3 } 960 pwMplsTeMappingTunnelLocalLsrID OBJECT-TYPE 961 SYNTAX MplsLsrIdentifier 962 MAX-ACCESS not-accessible 963 STATUS current 964 DESCRIPTION 965 "Identifies the local LSR." 966 ::= { pwMplsTeMappingEntry 4 } 968 pwMplsTeMappingPwIndex OBJECT-TYPE 969 SYNTAX PwIndexType 970 MAX-ACCESS read-only 971 STATUS current 972 DESCRIPTION 973 "The value that represents the PW in the pwTable." 974 ::= { pwMplsTeMappingEntry 5 } 976 -- End of PW to TE MPLS tunnels mapping Table. 978 -- conformance information 980 pwMplsGroups OBJECT IDENTIFIER ::= { pwMplsConformance 1 } 981 pwMplsCompliances OBJECT IDENTIFIER ::= { pwMplsConformance 2 } 983 -- Compliance requirement for fully compliant implementations. 985 pwMplsModuleFullCompliance MODULE-COMPLIANCE 986 STATUS current 987 DESCRIPTION 988 "The compliance statement for agents that provide full 989 support for PW-MPLS MIB Module. Such devices can 990 then be monitored and also be configured using 991 this MIB module." 993 MODULE -- this module 994 MANDATORY-GROUPS { pwMplsGroup, 995 pwMplsOutboundMainGroup, 996 pwMplsInboundGroup, 997 pwMplsMappingGroup 998 } 1000 GROUP pwMplsOutboundTeGroup 1001 DESCRIPTION "This group MUST be supported if the implementation 1002 allows MPLS TE tunnels to carry PW traffic. 1003 " 1005 OBJECT pwMplsMplsType 1006 DESCRIPTION "Support of pwOnly(2) is not required. At least one 1007 of mplsTe(0) or mplsNonTe(1) MUST be supported if 1008 signaling of PW is supported. 1009 " 1011 OBJECT pwMplsExpBitsMode 1012 DESCRIPTION "Support of specifiedValue(2) and 1013 serviceDependant(3) is optional. 1014 " 1016 OBJECT pwMplsLocalLdpID 1017 MIN-ACCESS read-only 1018 DESCRIPTION "A read-write access is required if the 1019 implementation supports more than one LDP entity 1020 identifier for PW signaling. 1021 " 1023 OBJECT pwMplsLocalLdpEntityIndex 1024 MIN-ACCESS read-only 1025 DESCRIPTION "A read-write access is required if the 1026 implementation supports more than one LDP entity 1027 index for PW signaling. 1028 " 1030 OBJECT pwMplsOutboundLsrXcIndex 1031 MIN-ACCESS read-only 1032 DESCRIPTION "A value other than zero MUST be supported if the 1033 implementation supports non-TE signaling of the 1034 outer tunnel. 1035 A read-write access MUST be supported if the 1036 implementation supports PW label manuall setting 1037 and carrying them over non-TE tunnels. 1038 " 1040 OBJECT pwMplsOutboundIfIndex 1041 MIN-ACCESS read-only 1042 DESCRIPTION "A value other than zero and read-write operations 1043 MUST be supported if the implementation supports 1044 manully configured PW without MPLS outer tunnel. 1045 " 1046 ::= { pwMplsCompliances 1 } 1048 -- Compliance requirement for Read Only compliant implementations. 1050 pwMplsModuleReadOnlyCompliance MODULE-COMPLIANCE 1051 STATUS current 1052 DESCRIPTION 1053 "The compliance statement for agents that provide read- 1054 only support for the PW-MPLS-STD-MIB Module. Such 1055 devices can then be monitored but cannot be configured 1056 using this MIB module." 1058 MODULE -- this module 1059 MANDATORY-GROUPS { pwMplsGroup, 1060 pwMplsOutboundMainGroup, 1061 pwMplsInboundGroup, 1062 pwMplsMappingGroup 1063 } 1065 GROUP pwMplsOutboundTeGroup 1066 DESCRIPTION "This group MUST be supported if the implementation 1067 allows MPLS TE tunnels to carry PW traffic. 1068 " 1070 OBJECT pwMplsMplsType 1071 MIN-ACCESS read-only 1072 DESCRIPTION "Write access is not required. 1073 Support of pwOnly(2) is not required. At least one 1074 of mplsTe(0) or mplsNonTe(1) MUST be supported if 1075 signaling of PW is supported. 1076 " 1078 OBJECT pwMplsExpBitsMode 1079 MIN-ACCESS read-only 1080 DESCRIPTION "Write access is not required. 1081 Support of specifiedValue(2) and 1082 serviceDependant(3) is optional. 1083 " 1085 OBJECT pwMplsExpBits 1086 MIN-ACCESS read-only 1087 DESCRIPTION "Write access is not required. 1088 " 1089 OBJECT pwMplsTtl 1090 MIN-ACCESS read-only 1091 DESCRIPTION "Write access is not required. 1092 " 1094 OBJECT pwMplsLocalLdpID 1095 MIN-ACCESS read-only 1096 DESCRIPTION "Write access is not required. 1097 " 1099 OBJECT pwMplsLocalLdpEntityIndex 1100 MIN-ACCESS read-only 1101 DESCRIPTION "Write access is not required. 1102 " 1104 OBJECT pwMplsStorageType 1105 MIN-ACCESS read-only 1106 DESCRIPTION "Write access is not required. 1107 " 1109 OBJECT pwMplsOutboundLsrXcIndex 1110 MIN-ACCESS read-only 1111 DESCRIPTION "Write access is not required. 1112 A value other than zero MUST be supported if the 1113 implementation support non-TE signaling of the 1114 outer tunnel. 1115 " 1117 OBJECT pwMplsOutboundTunnelIndex 1118 MIN-ACCESS read-only 1119 DESCRIPTION "Write access is not required. 1120 " 1122 OBJECT pwMplsOutboundTunnelLclLSR 1123 MIN-ACCESS read-only 1124 DESCRIPTION "Write access is not required. 1125 " 1127 OBJECT pwMplsOutboundTunnelPeerLSR 1128 MIN-ACCESS read-only 1129 DESCRIPTION "Write access is not required. 1130 " 1132 OBJECT pwMplsOutboundIfIndex 1133 MIN-ACCESS read-only 1134 DESCRIPTION "Write access is not required. 1135 A value other than zero MUST be supported if the 1136 implementation supports manually configured PW 1137 without MPLS outer tunnel. 1138 " 1139 ::= { pwMplsCompliances 2 } 1141 -- Units of conformance. 1143 pwMplsGroup OBJECT-GROUP 1144 OBJECTS { 1145 pwMplsMplsType, 1146 pwMplsExpBitsMode, 1147 pwMplsExpBits, 1148 pwMplsTtl, 1149 pwMplsLocalLdpID, 1150 pwMplsLocalLdpEntityIndex, 1151 pwMplsPeerLdpID, 1152 pwMplsStorageType 1153 } 1155 STATUS current 1156 DESCRIPTION 1157 "Collection of objects needed for PW over MPLS PSN 1158 configuration." 1159 ::= { pwMplsGroups 1 } 1161 pwMplsOutboundMainGroup OBJECT-GROUP 1162 OBJECTS { 1163 pwMplsOutboundLsrXcIndex, 1164 pwMplsOutboundIfIndex, 1165 pwMplsOutboundTunnelTypeInUse 1166 } 1168 STATUS current 1169 DESCRIPTION 1170 "Collection of objects needed for outbound association of 1171 PW and MPLS tunnel." 1172 ::= { pwMplsGroups 2 } 1174 pwMplsOutboundTeGroup OBJECT-GROUP 1175 OBJECTS { 1176 pwMplsOutboundTunnelIndex, 1177 pwMplsOutboundTunnelInstance, 1178 pwMplsOutboundTunnelLclLSR, 1179 pwMplsOutboundTunnelPeerLSR 1180 } 1182 STATUS current 1183 DESCRIPTION 1184 "Collection of objects needed for outbound association of 1185 PW and MPLS TE tunnel." 1186 ::= { pwMplsGroups 3 } 1188 pwMplsInboundGroup OBJECT-GROUP 1189 OBJECTS { 1190 pwMplsInboundXcIndex 1191 } 1193 STATUS current 1194 DESCRIPTION 1195 "Collection of objects needed for inbound PW presentation. 1196 This group MUST be supported if PW signaling through LDP is 1197 used." 1198 ::= { pwMplsGroups 4 } 1200 pwMplsMappingGroup OBJECT-GROUP 1201 OBJECTS { 1202 pwMplsNonTeMappingPwIndex, 1203 pwMplsTeMappingPwIndex 1204 } 1206 STATUS current 1207 DESCRIPTION 1208 "Collection of objects needed for mapping association of 1209 PW and MPLS tunnel." 1210 ::= { pwMplsGroups 5 } 1212 END 1214 7. Security Considerations 1216 It is clear that this MIB module is potentially useful for monitoring 1217 PW-capable PEs. This MIB module can also be used for configuration 1218 of certain objects, and anything that can be configured can be 1219 incorrectly configured, with potentially disastrous results. 1221 There are number of management objects defined in this MIB module 1222 with a MAX-ACCESS clause of read-write and/or read-create. Such 1223 objects may be considered sensitive or vulnerable in some network 1224 environments. The support for SET operations in a non-secure 1225 environment without proper protection can have a negative effect on 1226 network operations. These are the tables and objects and their 1227 sensitivity/vulnerability: 1229 o the pwMplsTable, pwMplsNonTeMappingTable and pwMplsTeMappingTable 1230 collectively contain objects to provision PW over MPLS tunnels. 1231 Unauthorized access to objects in these tables, could result in 1232 disruption of traffic on the network. The use of stronger 1233 mechanisms such as SNMPv3 security should be considered where 1234 possible. Specifically, SNMPv3 VACM and USM MUST be used with any 1235 v3 agent which implements this MIB module. Administrators should 1236 consider whether read access to these objects should be allowed, 1237 since read access may be undesirable under certain circumstances. 1239 Some of the readable objects in this MIB module, i.e., objects with a 1240 MAX-ACCESS other than not-accessible, may be considered sensitive or 1241 vulnerable in some network environments. It is thus important to 1242 control even GET and/or NOTIFY access to these objects and possibly 1243 to even encrypt the values of these objects when sending them over 1244 the network via SNMP. These are the tables and objects and their 1245 sensitivity/vulnerability: 1247 o the pwMplsTable, pwMplsNonTeMappingTable, pwMplsTeMappingTable and 1248 pwMplsOutboundTable collectively show the PW over MPLS 1249 association. If an Administrator does not want to reveal this 1250 information, then these tables should be considered sensitive/ 1251 vulnerable. 1253 SNMP versions prior to SNMPv3 did not include adequate security. 1254 Even if the network itself is secure "for example by using IPSec", 1255 even then, there is no control as to who on the secure network is 1256 allowed to access and GET/SET "read/change/create/delete" the objects 1257 in this MIB module. 1259 It is RECOMMENDED that implementers consider the security features as 1260 provided by the SNMPv3 framework "see [RFC3410], section 8", 1261 including full support for the SNMPv3 cryptographic mechanisms "for 1262 authentication and privacy". 1264 Further, deployment of SNMP versions prior to SNMPv3 is NOT 1265 RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to 1266 enable cryptographic security. It is then a customer/operator 1267 responsibility to ensure that the SNMP entity giving access to an 1268 instance of this MIB module, is properly configured to give access to 1269 the objects only to those principals "users" that have legitimate 1270 rights to indeed GET or SET "change/create/delete" them. 1272 8. IANA Considerations 1274 The MIB module in this document uses the following IANA-assigned 1275 OBJECT IDENTIFIER values recorded in the SMI Numbers registry: 1277 Descriptor OBJECT IDENTIFIER value 1278 ---------- ----------------------- 1280 pwMplsStdMIB { transmission XXX } 1282 Editor's Note (to be removed prior to publication): The IANA is 1283 requested to assign a value for "XXX" under the 'transmission' 1284 subtree and to record the assignment in the SMI Numbers registry. 1285 When the assignment has been made, the RFC Editor is asked to replace 1286 "XXX" (here and in the MIB module) with the assigned value and to 1287 remove this note. 1289 9. References 1291 9.1. Normative References 1293 [BCP14] Bradner, S., "Key words for use in RFCs to Indicate 1294 requirement Levels", BCP 14, RFC 2119, March 1997. 1296 [PWMIB] Zelig, D. and T. Nadeau, "Pseudo-Wire (PW) Management 1297 Information Base", work-in-progress . 1299 [PWTC] Nadeau, T. and D. Zelig, "Definitions for Textual 1300 Conventions and OBJECT-IDENTITIES for Pseudo-Wires 1301 Management", work-in-progress . 1303 [RFC2578] McCloghrie, K., Ed., Perkins, D., Ed., and J. 1304 Schoenwaelder, Ed., "Structure of Management Information 1305 Version 2 (SMIv2)", STD 58, RFC 2578, April 1999. 1307 [RFC2579] McCloghrie, K., Ed., Perkins, D., Ed., and J. 1308 Schoenwaelder, Ed., "Textual Conventions for SMIv2", 1309 STD 58, RFC 2579, April 1999. 1311 [RFC2580] McCloghrie, K., Perkins, D., and J. Schoenwaelder, 1312 "Conformance Statements for SMIv2", STD 58, RFC 2580, 1313 April 1999. 1315 [RFC2863] McCloghrie, K. and F. Kastenholz, "The Interfaces Group 1316 MIB", RFC 2863, June 2000. 1318 [RFC3031] Rosen, E., Viswanathan, A., and R. Callon, "Multiprotocol 1319 Label Switching Architecture", RFC 3031, January 2001. 1321 [RFC3811] Nadeau, T. and J. Cucchiara, "Definitions of Textual 1322 Conventions (TCs) for Multiprotocol Label Switching (MPLS) 1323 Management", RFC 3811, June 2004. 1325 [RFC3812] Srinivasan, C., Viswanathan, A., and T. Nadeau, 1326 "Multiprotocol Label Switching (MPLS) Traffic Engineering 1327 (TE) Management Information Base (MIB)", RFC 3812, 1328 June 2004. 1330 [RFC3813] Srinivasan, C., Viswanathan, A., and T. Nadeau, 1331 "Multiprotocol Label Switching (MPLS) Label Switching 1332 Router (LSR) Management Information Base (MIB)", RFC 3813, 1333 June 2004. 1335 [RFC3916] Xiao, X., McPherson, D., and P. Pate, "Requirements for 1336 Pseudo-Wire Emulation Edge-to-Edge (PWE3)", RFC 3916, 1337 September 2004. 1339 [RFC3985] Bryant, S. and P. Pate, "Pseudo-Wire Emulation Edge-to- 1340 Edge (PWE3) Architecture", RFC 3985, March 2005. 1342 [RFC4447] Martini, L., Rosen, E., El-Aawar, N., Smith, T., and G. 1343 Heron, "Pseudowire Setup and Maintenance Using the Label 1344 Distribution Protocol (LDP)", RFC 4447, April 2006. 1346 9.2. Informative References 1348 [RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart, 1349 "Introduction and Applicability Statements for Internet- 1350 Standard Management Framework", RFC 3410, December 2002. 1352 [RFC3815] Cucchiara, J., Sjostrand, H., and J. Luciani, "Definitions 1353 of Managed Objects for the Multiprotocol Label Switching 1354 (MPLS), Label Distribution Protocol (LDP)", RFC 3815, 1355 June 2004. 1357 Authors' Addresses 1359 David Zelig (editor) 1360 Corrigent Systems 1361 126, Yigal Alon St. 1362 Tel Aviv, 1363 Israel 1365 Phone: +972 3 6945 273 1366 Email: davidz@corrigent.com 1368 Thomas D. Nadeau (editor) 1369 Cisco Systems, Inc. 1370 250 Apollo Drive 1371 Chelmsford, MA 01824 1372 USA 1374 Email: tnadeau@cisco.com 1376 Full Copyright Statement 1378 Copyright (C) The Internet Society (2006). 1380 This document is subject to the rights, licenses and restrictions 1381 contained in BCP 78, and except as set forth therein, the authors 1382 retain all their rights. 1384 This document and the information contained herein are provided on an 1385 "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS 1386 OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET 1387 ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, 1388 INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE 1389 INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED 1390 WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 1392 Intellectual Property 1394 The IETF takes no position regarding the validity or scope of any 1395 Intellectual Property Rights or other rights that might be claimed to 1396 pertain to the implementation or use of the technology described in 1397 this document or the extent to which any license under such rights 1398 might or might not be available; nor does it represent that it has 1399 made any independent effort to identify any such rights. Information 1400 on the procedures with respect to rights in RFC documents can be 1401 found in BCP 78 and BCP 79. 1403 Copies of IPR disclosures made to the IETF Secretariat and any 1404 assurances of licenses to be made available, or the result of an 1405 attempt made to obtain a general license or permission for the use of 1406 such proprietary rights by implementers or users of this 1407 specification can be obtained from the IETF on-line IPR repository at 1408 http://www.ietf.org/ipr. 1410 The IETF invites any interested party to bring to its attention any 1411 copyrights, patents or patent applications, or other proprietary 1412 rights that may cover technology that may be required to implement 1413 this standard. Please address the information to the IETF at 1414 ietf-ipr@ietf.org. 1416 Acknowledgment 1418 Funding for the RFC Editor function is provided by the IETF 1419 Administrative Support Activity (IASA).