idnits 2.17.1 draft-ietf-pwe3-pw-mpls-mib-06.txt: ** The Abstract section seems to be numbered Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** Looks like you're using RFC 2026 boilerplate. This must be updated to follow RFC 3978/3979, as updated by RFC 4748. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- == There are 3 instances of lines with non-ascii characters in the document. == No 'Intended status' indicated for this document; assuming Proposed Standard Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack an Abstract section. (A line matching the expected section header was found, but with an unexpected indentation: ' 1 Abstract' ) ** The document seems to lack an Introduction section. (A line matching the expected section header was found, but with an unexpected indentation: ' Introduction and Applicability Statements for Internet-' ) ** The document seems to lack a Security Considerations section. (A line matching the expected section header was found, but with an unexpected indentation: ' 8 Security Considerations' ) ** The document seems to lack an IANA Considerations section. (See Section 2.2 of https://www.ietf.org/id-info/checklist for how to handle the case when there are no actions for IANA.) (A line matching the expected section header was found, but with an unexpected indentation: ' 9 IANA considerations' ) Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the RFC 3978 Section 5.4 Copyright Line does not match the current year == Line 219 has weird spacing: '...N |PWin inSeg...' == Line 223 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 (June 2004) is 7255 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 section? 'PW-MIB' on line 1385 looks like a reference -- Missing reference section? 'BCP14' on line 1415 looks like a reference -- Missing reference section? 'PWARCH' on line 1375 looks like a reference -- Missing reference section? 'PWREQ' on line 1378 looks like a reference -- Missing reference section? 'PWCNTRL' on line 117 looks like a reference -- Missing reference section? 'MPLSArch' on line 1391 looks like a reference -- Missing reference section? 'RFC3410' on line 1435 looks like a reference -- Missing reference section? 'RFC2578' on line 1418 looks like a reference -- Missing reference section? 'RFC2579' on line 1425 looks like a reference -- Missing reference section? 'RFC2580' on line 1429 looks like a reference -- Missing reference section? 'CEPMIB' on line 175 looks like a reference -- Missing reference section? 'PWTC' on line 1381 looks like a reference -- Missing reference section? 'TEMIB' on line 1403 looks like a reference -- Missing reference section? 'LSRMIB' on line 1399 looks like a reference -- Missing reference section? 'PWTCMIB' on line 1365 looks like a reference -- Missing reference section? 'IF-MIB' on line 1388 looks like a reference -- Missing reference section? 'LblStk' on line 1395 looks like a reference -- Missing reference section? 'MPLSTCMIB' on line 1407 looks like a reference -- Missing reference section? 'LDP' on line 1412 looks like a reference Summary: 6 errors (**), 0 flaws (~~), 6 warnings (==), 21 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 Internet Draft David Zelig 2 Expires: December 2004 Corrigent Systems 4 A. Malis Thomas D. Nadeau 5 Tellabs, Inc. Cisco Systems, Inc. 7 Sharon Mantin Dave Danenberg 8 AxONLinks 10 June 2004 12 Pseudo Wire (PW) over MPLS PSN Management Information Base 14 draft-ietf-pwe3-pw-mpls-mib-06.txt 16 Status of this Memo 18 This document is an Internet-Draft and is in full conformance 19 with all provisions of Section 10 of RFC2026. 21 Internet-Drafts are working documents of the Internet Engineering 22 Task Force (IETF), its areas, and its working groups. Note that 23 other groups may also distribute working documents as Internet- 24 Drafts. 26 Internet-Drafts are draft documents valid for a maximum of six 27 months and may be updated, replaced, or obsoleted by other 28 documents at any time. It is inappropriate to use Internet-Drafts 29 as reference material or to cite them other than as "work in 30 progress." 32 The list of current Internet-Drafts can be accessed at 33 http://www.ietf.org/ietf/1id-abstracts.txt 34 The list of Internet-Draft Shadow Directories can be accessed at 35 http://www.ietf.org/shadow.html. 37 Copyright (C) The Internet Society (2001). All rights reserved. 39 1 Abstract 41 This memo defines an experimental portion of the Management 42 Information Base (MIB) for use with network management protocols in 43 the Internet community. In particular, it describes a MIB module 44 for PW operation over Multi-Protocol Label Switching (MPLS) Label 45 Switch Router (LSR). 47 Management Information Base 49 Table of Contents 51 1 Abstract.......................................................1 52 2 Introduction...................................................2 53 3 Terminology....................................................3 54 4 The Internet-Standard Management Framework.....................3 55 5 Feature Checklist..............................................4 56 6 MIB module usage...............................................4 57 6.1 PW MPLS MIB module usage.....................................4 58 6.2 Example of MIB module usage..................................6 59 7 Object definitions.............................................7 60 8 Security Considerations.......................................26 61 9 IANA considerations...........................................27 62 10 References..................................................27 63 10.1 Normative references........................................27 64 10.2 Informative references......................................29 65 11 Author's Addresses..........................................29 66 12 Full Copyright Statement....................................29 67 13 Intellectual Property Notice................................30 69 2 Introduction 71 This document describes a model for managing pseudo wire services 72 for transmission over different flavors of MPLS tunnels. The 73 general PW MIB module [PW-MIB] defines the parameters global to the 74 PW regardless of underlying PSN and emulated service. Indicating 75 PSN type of MPLS in PW-MIB references this module. 77 This document describes the MIB objects that define pseudo wire 78 association to the MPLS PSN, in a way that is not specific to the 79 carried service. 81 Together, [TEMIB and LSRMIB], describe the modeling of an MPLS 82 Tunnel, and a Tunnel's underlying cross-connects. The defined MIB 83 support MPLS-TE PSN, Non TE MPLS PSN (an outer tunnel created by 84 LDP or manually), and MPLS PW label only (no outer tunnel). 86 Management Information Base 88 Conventions used in this document 90 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 91 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in 92 this document are to be interpreted as described in RFC-2119 93 [BCP14]. 95 3 Terminology 97 This document uses terminology from the document describing the PW 98 architecture [PWARCH], [PWREQ] and [PWCNTRL]. 100 The terms "Outbound" and "Inbound" in this MIB module are based on 101 the common practice in the MPLS standards, i.e. "outbound" are 102 toward the PSN. However, where these terms are used in an object 103 name, the object description clarifies the exact packet direction 104 to prevent confusion with these terms in other documents. 106 "PSN Tunnel" is a general term indicating a virtual connection 107 between the two PWE3 edge devices. Each tunnel may potentially 108 carry multiple PWs inside. In the scope of this document, it is 109 MPLS tunnel. 111 This document uses terminology from the document describing the 112 MPLS architecture [MPLSArch] for MPLS PSN. A Label Switched Path 113 (LSP) is modeled as described in [LSRMIB and TEMIB] via a series of 114 cross-connects through 1 or more Label switch routers (LSR). 116 In MPLS PSN, a PW connection typically uses a PW Label within a 117 Tunnel Label [PWCNTRL]. Multiple pseudo wires each with a unique PW 118 Label can share the same Tunnel. For PW transport over MPLS, the 119 Tunnel Label is known as the "outer" Label, while the PW Label is 120 known as the "inner" Label. An exception to this is with adjacent 121 LSRs or the use of PHP. In this case, there is an option for PWs to 122 connect directly without an outer Label. 124 4 The Internet-Standard Management Framework 126 For a detailed overview of the documents that describe the current 127 Internet-Standard Management Framework, please refer to section 7 128 of RFC 3410 [RFC3410]. 130 Managed objects are accessed via a virtual information store, 131 termed the Management Information Base or MIB. MIB objects are 132 generally accessed through the Simple Network Management Protocol 133 (SNMP). Objects in the MIB are defined using the mechanisms defined 134 in the Structure of Management Information (SMI). This memo 135 specifies a MIB module that is compliant to the SMIv2, which is 136 described in STD 58,RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] 137 and STD 58, RFC 2580 [RFC2580]. 139 Management Information Base 141 5 Feature Checklist 143 The PW MPLS MIB module is designed to satisfy the following 144 requirements and constraints: 146 - The MIB module supports both manually configured and signaled 147 PWs. 149 - The MIB module supports point-to-point PW connections. 151 - The MIB module enables the use of any emulated service. 153 - The MIB module supports MPLS-TE outer tunnel, Non TE MPLS outer 154 tunnel (an outer tunnel signaled by LDP or set-up manually), and 155 no outer tunnel (where the PW label is the only label in the 156 incoming MPLS stack). The later case is applicable for manual 157 configuration of PW over a single hop (in multiple hops case, it 158 is required to have an outer MPLS tunnel). 160 6 MIB module usage 162 The MIB module structure for defining a PW service is composed from 163 three types of modules. 165 The first type is the PW MIB module [PW-MIB], which configures 166 general parameters of the PW that are common to all types of 167 emulated services and PSN. 169 The second type of modules is per PSN module. There is a separate 170 module for each type of PSN. This document defines the MIB module 171 for MPLS (PW-MPLS-MIB). 173 The third type of modules is service-specific module, which is 174 emulated signal type dependent. These modules are defined in other 175 documents; see for example [CEPMIB]. 177 [PWTC] defines some of the object types used in this module. 179 6.1 PW MPLS MIB module usage 181 - The PW table (pwVcTable) in [PW-MIB] is used for all PW types 182 (ATM, FR, Ethernet, SONET, etc.). This table contains high level 183 generic parameters related to the PW creation. The operator or the 184 agent for each PW service creates a row. 186 - If the PSN type in pwVcTable is MPLS, the agent creates a row in 187 the MPLS specific parameters table (pwMplsVcTable) in this module, 188 Management Information Base 190 which contain MPLS specific parameters such as EXP bits handling 191 and outer tunnel configuration. 193 - The operator configures the association to the desired MPLS 194 tunnel (require for MPLS TE tunnels or manually configured PWs) 195 through the pwMplsTeOutbaoundTable. For LDP based outer tunnel, 196 there is no need for manula configuration since there is only a 197 single tunnel toward the peer. 199 - The agent creates rows in the MPLS mapping table in order to 200 allow quick retrieval of information based on the tunnel indexes. 202 The relation to the MPLS network is by configuration of the edge 203 LSR only - that is to say, the LSR providing the PW function. Since 204 Tunnels are uni-directional, a pair of tunnels must exist (one for 205 inbound, one for outbound). The following graphic depicts a VC that 206 originates and terminates at LSR-M. It uses LSPs A and B formed by 207 Tunnels Ax and Bx continuing through LSR-N to LSR-P. The 208 concatenations of Tunnels create the LSPs. Note: 'X' denotes a 209 Tunnel's cross-connect. 211 LSP-A 212 <- - - - - - - - - - - - - - - - - - - - - - - - - - - - 214 +---- (edge) LSR-M ---+ +--------- LSR-N ---------+ + LSR-P 215 |---+ | | | | 216 | | Tunnel | | Tunnel | | 217 + | A1 (M<-N) +----+ +----+ A2 (M<-P) +----+ +----+ 218 | | <------| | | |<--------------| | | | 219 <-->| N |PWin inSeg |MPLS| |MPLS| outSeg inSeg |MPLS| |MPLS| 220 N S | | <---X<-----| IF | | IF |<------X<------| IF | | IF | 221 A E | S | | |<-->| | | |<-->| | | 222 T R | | --->X----->| | | |------>X------>| | | | 223 I V | P |PWout outSeg| | | | inSeg outSeg | | | | 224 V I | | ------>| | | |-------------->| | | | 225 E C + | Tunnel +----+ +----+ Tunnel +----+ +----+ 226 E |---+ B1 (M->N) | | B2 (M->P) | | 227 | | | | | 228 +---------------------+ +-------------------------+ +----- 230 - - - - - - - - - - - - - - - - - - - - - - - - - - - -> 231 LSP-B 233 The PW-MPLS-MIB supports three options for MPLS network: 235 - In the MPLS-TE case, Tunnel A1 and B1 are created via the MPLS-TE 236 MIB [TEMIB]. The tunnels are associated to the PW by the (4) 237 indexes that uniquely identify the Tunnel at the TE-MIB. 239 Management Information Base 241 - In the Non TE case, Tunnel A1 and B1 are either manually 242 configured or set up with LDP. The tunnels are associated to the PW 243 by the XC index in the MPLS-LSR-MIB [LSRMIB]. 245 - In the PW label only case, there is no outer tunnel on top of the 246 PW label. This case is useful in case of adjacent PEs in manual 247 configuration mode. Note that when LSR-N acts as PHP for the outer 248 tunnel label, there are still entries for the outer tunnel in the 249 relevant MPLS MIB modules. 251 A combination of MPLS-TE outer tunnel(s) and LDP outer tunnel for 252 the same PW is allowed through the pwVcMplsOutboundTunnel. The 253 current tunnel that is used to forward traffic is indicated in the 254 object pwVcMplsOutboundTunnelTypeInUse. 256 The PW MPLS MIB module reports through the inbound table the XC 257 entry in the LDP-STD_MIB of the PW that were signaled through LDP. 259 This MIB module assumes that a single PW can be associated to one 260 MPLS-TE tunnel at a time. This tunnel may be composed of multiple 261 instances (i.e. LSP), each represented by a separate instance 262 index. The current active LSP is reported through this MIB module. 264 It is worth noting that inbound (tunnel originated in the remote 265 PE) mapping is nor configured nor reported through the PW MPLS MIB 266 module since the local PE does not know the inbound association 267 between specific PW and MPLS tunnels. 269 6.2 Example of MIB module usage 271 Please see [PW-MIB] for detailed MIB usage example. 273 Management Information Base 275 7 Object definitions 277 PW-MPLS-DRAFT06-MIB DEFINITIONS ::= BEGIN 279 IMPORTS 280 MODULE-IDENTITY, OBJECT-TYPE, 281 Unsigned32 282 FROM SNMPv2-SMI 284 MODULE-COMPLIANCE, OBJECT-GROUP 285 FROM SNMPv2-CONF 287 StorageType 288 FROM SNMPv2-TC 290 InterfaceIndexOrZero 291 FROM IF-MIB 293 MplsTunnelIndex, MplsTunnelInstanceIndex, 294 MplsLdpIdentifier, MplsLsrIdentifier 295 FROM MPLS-TC-STD-MIB 297 MplsIndexType 298 FROM MPLS-LSR-STD-MIB 300 PwVcIndexType, pwStdMIB 301 FROM PW-TC-DRAFT05-MIB 303 pwVcIndex 304 FROM PW-DRAFT05-MIB 306 ; 308 pwVcMplsMIB MODULE-IDENTITY 309 LAST-UPDATED "200406131200Z" -- 13 June 2004 12:00:00 GMT 310 ORGANIZATION "Pseudo Wire Edge to Edge Emulation (PWE3) Working 311 Group" 312 CONTACT-INFO 313 " 314 David Zelig 315 Postal: Corrigent Systems 316 126, Yigal Alon St. 317 Tel Aviv, ISRAEL 318 Phone: +972-3-6945273 319 E-mail: davidz@corrigent.com 321 Thomas D. Nadeau 322 Postal: Cisco Systems, Inc. 323 250 Apollo Drive 324 Chelmsford, MA 01824 325 Management Information Base 327 Tel: +1-978-497-3051 328 Email: tnadeau@cisco.com 330 Dave Danenberg 331 Email: dave_danenberg@yahoo.com 333 Sharon Mantin 334 Postal: AxONLink (Israel) Ltd 335 9 Bareket St. 336 Petah Tikva 49517, Israel 337 Tel: +972-3-9263972 338 Email: sharon.mantin@axonlink.com 340 The PWE3 Working Group (email distribution pwe3@ietf.org, 341 http://www.ietf.org/html.charters/pwe3-charter.html) 342 " 343 DESCRIPTION 344 "This MIB module complements the PW MIB module for PW 345 operation over MPLS. 347 Copyright (C) The Internet Society (date). This version 348 of this MIB module is part of RFC yyyy; see the RFC 349 itself for full legal notices. 350 -- RFC Ed.: replace yyyy with actual RFC number & remove this note 351 " 353 -- Revision history. 355 REVISION 356 "200406131200Z" -- 13 June 2004 12:00:00 GMT 357 DESCRIPTION 359 "Draft-ietf-pwe3-pw-mpls-mib-06 version. Changes from 360 previous version: 361 1) Compliance section details. 362 " 364 REVISION 365 "200402121200Z" -- 12 February 2004 12:00:00 GMT 366 DESCRIPTION 368 "Draft-ietf-pwe3-pw-mpls-mib-05 version. Changes from 369 previous version: 370 1) Add inbound/outbound index for the nonTe mapping table 371 2) Clarify the pwVcMplsTeMappingTunnelInstance usage in 372 pwVcMplsTeMappingTable. 373 3) Remove an index from pwVcMplsOutboundTable and adding 374 an indication of Te or non-TE usage. 375 4) Removing the RowStatus from the outbound tables since it 376 possible to configure a PW to a single TE tunnel head-end 377 and/or a single nonTE tunnel, so the agent can open the 378 Management Information Base 380 row automatically. 381 5) Adding a nonTe inbound table in order to enable a quick 382 search for a PW based on pwVcIndex. 383 " 384 REVISION 385 "200311301200Z" -- 30 November 2003 12:00:00 EST 386 DESCRIPTION 387 "Draft-ietf-pwe3-pw-mpls-mib-04 version. Changes from 388 previous version: 389 1) Adapting description to MIB boilerplate. 390 2) Module OID changed to PWE3 tree. 391 3) Sync descriptions of various items to table structure and 392 removing unnecessary references. 393 " 394 REVISION 395 "200307291200Z" -- 29 July 2003 12:00:00 EST 396 DESCRIPTION 397 "Draft-ietf-pwe3-pw-mpls-mib-02 version. Changes from 398 previous version: 399 1) Removing inbound table (no strict mode and no knowledge 400 of inbound tunnel). 401 2) Provisioning (i.e. RowCreate) done via mapping tables. 402 Outbound table is now read only for sorted search for 403 pwVcIndex. 404 " 406 REVISION 407 "200206021200Z" -- 02 June 2002 12:00:00 EST 408 DESCRIPTION 409 "Draft-ietf-pwe3-pw-mpls-mib-00 version. Changes from 410 previous version: 411 1) Splitting the mapping table into two tables, one for 412 Non TE application and one for TE application. 413 2) Object types alignment with MPLS MIBs. 414 " 415 REVISION 416 "200201291200Z" -- 29 January 2002 12:00:00 EST 417 DESCRIPTION 418 "Changes from previous version: 419 1) Add LDP entity association. 420 2) Clarify inbound/outbound directions. 421 3) Simplify indexing of outbound and inbound tables 422 and providing get next variables. 423 " 424 REVISION 425 "200111071200Z" -- 7 November 2001 12:00:00 EST 426 DESCRIPTION 427 "Changes from previous version: 428 1) Remove Vc instance from table indexing. 429 2) Update descriptions of indexing and protection. 430 3) Remove the need for MPLS-LSR in case of VC only. 432 Management Information Base 434 4) Change pwVcMplsMplsType to BITS in order to enable 435 multiple types of outer tunnel. 436 5) Add ifindex to outer tunnel tables to support vcOnly 437 option. 438 6) change naming of outbound, inbound and mapping tables to 439 reflect addition of VC only port ifindexes. 440 7) Adapt order of items in mapping table to SNMP convention. 441 " 442 REVISION 443 "200107111200Z" -- July 11 2001 12:00:00 EST 444 DESCRIPTION 445 "draft-zelig-pw-mib-00.txt - initial version" 447 ::= { pwStdMIB x } -- To be assigned by IANA 448 -- the value 3 is requested for this 449 -- specific Module. 451 -- Top-level components of this MIB. 453 -- Tables, Scalars 454 pwVcMplsObjects OBJECT IDENTIFIER 455 ::= { pwVcMplsMIB 1 } 456 -- Conformance 457 pwVcMplsConformance OBJECT IDENTIFIER 458 ::= { pwVcMplsMIB 2 } 460 -- PW MPLS table 462 pwVcMplsTable OBJECT-TYPE 463 SYNTAX SEQUENCE OF PwVcMplsEntry 464 MAX-ACCESS not-accessible 465 STATUS current 466 DESCRIPTION 467 "This table controls MPLS specific parameters when the PW is 468 going to be carried over MPLS PSN." 469 ::= { pwVcMplsObjects 1 } 471 pwVcMplsEntry OBJECT-TYPE 472 SYNTAX PwVcMplsEntry 473 MAX-ACCESS not-accessible 474 STATUS current 475 DESCRIPTION 476 "A row in this table represents parameters specific to MPLS 477 PSN for a pseudo wire (PW). The row is created 478 automatically by the local agent if the pwVcPsnType is 479 MPLS. It is indexed by pwVcIndex, which uniquely 480 identifying a singular PW. 481 " 482 INDEX { pwVcIndex } 484 ::= { pwVcMplsTable 1 } 485 Management Information Base 487 PwVcMplsEntry ::= SEQUENCE { 488 pwVcMplsMplsType BITS, 489 pwVcMplsExpBitsMode INTEGER, 490 pwVcMplsExpBits Unsigned32, 491 pwVcMplsTtl Unsigned32, 492 pwVcMplsLocalLdpID MplsLdpIdentifier, 493 pwVcMplsLocalLdpEntityID MplsLsrIdentifier, 494 pwVcMplsPeerLdpID MplsLdpIdentifier, 495 pwVcMplsStorageType StorageType 496 } 498 pwVcMplsMplsType OBJECT-TYPE 499 SYNTAX BITS { 500 mplsTe (0), 501 mplsNonTe (1), 502 vcOnly (2) 503 } 504 MAX-ACCESS read-write 505 STATUS current 506 DESCRIPTION 507 "Set by the operator to indicate the outer tunnel types, if 508 exists. mplsTe(0) is used if the outer tunnel was set-up 509 by MPLS-TE, and mplsNonTe(1) is used the outer tunnel was 510 set up by LDP or manually. Combination of mplsTe(0) and 511 mplsNonTe(1) may exist together. 512 vcOnly(2) is used if there is no outer tunnel label, i.e. 513 in static provisioning without MPLS tunnel. vcOnly(2) 514 cannot be combined with mplsNonTe(1) or mplsTe(0)." 515 DEFVAL { { mplsNonTe } } 516 ::= { pwVcMplsEntry 1 } 518 pwVcMplsExpBitsMode OBJECT-TYPE 519 SYNTAX INTEGER { 520 outerTunnel (1), 521 specifiedValue (2), 522 serviceDependant (3) 523 } 525 MAX-ACCESS read-write 526 STATUS current 527 DESCRIPTION 528 "Set by the operator to indicate the way the PW shim label 529 EXP bits are to be determined. The value of outerTunnel(1) 530 is used where there is an outer tunnel - pwVcMplsMplsType 531 is mplsTe(0) or mplsNonTe(1). Note that in this case there 532 is no need to mark the PW label with the EXP bits since the 533 PW label is not visible to the intermediate nodes. 534 If there is no outer tunnel, specifiedValue(2) indicates 535 that the value is specified by pwVcMplsExpBits, and 536 Management Information Base 538 serviceDependant(3) indicates that the EXP bits are setup 539 based on a rule specified in the emulated service specific 540 tables, for example when the EXP bits are a function of 541 802.1p marking for Ethernet emulated service." 543 DEFVAL { outerTunnel } 544 ::= { pwVcMplsEntry 2 } 546 pwVcMplsExpBits OBJECT-TYPE 547 SYNTAX Unsigned32 (0..7) 548 MAX-ACCESS read-write 549 STATUS current 550 DESCRIPTION 551 "Set by the operator to indicate the MPLS EXP bits to be 552 used on the PW shim label if pwVcMplsExpBitsMode is 553 specifiedValue(2), zero otherwise." 554 DEFVAL { 0 } 555 ::= { pwVcMplsEntry 3 } 557 pwVcMplsTtl OBJECT-TYPE 558 SYNTAX Unsigned32 (0..255) 559 MAX-ACCESS read-write 560 STATUS current 561 DESCRIPTION 562 "Set by the operator to indicate the PW TTL value to be 563 used on the PW shim label." 564 DEFVAL { 2 } 565 ::= { pwVcMplsEntry 4 } 567 pwVcMplsLocalLdpID OBJECT-TYPE 568 SYNTAX MplsLdpIdentifier 569 MAX-ACCESS read-write 570 STATUS current 571 DESCRIPTION 572 "The local LDP identifier of the LDP entity creating 573 this PW in the local node. As the PW labels are always 574 set from the per platform label space, the last two octets 575 in the LDP ID MUST be always both zeros." 576 REFERENCE 577 "'LDP specifications', RFC 3036 section 2.2.2." 578 ::= { pwVcMplsEntry 5 } 580 pwVcMplsLocalLdpEntityID OBJECT-TYPE 581 SYNTAX MplsLsrIdentifier 582 MAX-ACCESS read-write 583 STATUS current 584 DESCRIPTION 585 "The local node LDP Entity ID of the LDP entity creating 586 this PW. Should return the value of all zeros if not 587 used." 588 ::= { pwVcMplsEntry 6 } 589 Management Information Base 591 pwVcMplsPeerLdpID OBJECT-TYPE 592 SYNTAX MplsLdpIdentifier 593 MAX-ACCESS read-only 594 STATUS current 595 DESCRIPTION 596 "The peer LDP identifier as identified from the LDP 597 session. Should return the value of zero if not applicable 598 or not known yet." 599 ::= { pwVcMplsEntry 7 } 601 pwVcMplsStorageType OBJECT-TYPE 602 SYNTAX StorageType 603 MAX-ACCESS read-write 604 STATUS current 605 DESCRIPTION 606 "This variable indicates the storage type for this row." 607 ::= { pwVcMplsEntry 8 } 609 -- End of PW MPLS table 611 -- Pseudo Wire MPLS Outbound Tunnel table 613 pwVcMplsOutboundTable OBJECT-TYPE 614 SYNTAX SEQUENCE OF PwVcMplsOutboundEntry 615 MAX-ACCESS not-accessible 616 STATUS current 617 DESCRIPTION 618 "This table reports and configure the current outbound MPLS 619 tunnels (i.e. toward the PSN) or the physical interface in 620 case of PW label only that carry the PW traffic. It also 621 reports the current outer tunnel and LSP which forward the 622 PW traffic." 623 ::= { pwVcMplsObjects 2 } 625 pwVcMplsOutboundEntry OBJECT-TYPE 626 SYNTAX PwVcMplsOutboundEntry 627 MAX-ACCESS not-accessible 628 STATUS current 629 DESCRIPTION 630 "A row in this table configured the outer tunnel used for 631 carrying the PW traffic toward the PSN. 632 In the case of PW label only, it configures the interface 633 that will carry the PW traffic. 635 An entry in this table augments the pwVcMplsEntry, and is 636 created automatically when the corresponding row has been 637 created by the agent in the pwVcMplsEntry. 639 This table points to the appropriate MPLS MIB module. 640 In the MPLS-TE case, the 3 variables relevant to the 641 Management Information Base 643 indexing of a TE tunnel head-end are used as in 644 MPLS-TE-STD-MIB are to be configured, and the tunnel 645 instance indicates the LSP that is currently in use for 646 forwarding the traffic. 648 In case of signaled Non-TE MPLS (an outer tunnel label 649 assigned by LDP) the table points to the XC entry in the 650 LSR-STD-MIB. If the Non-TE MPLS tunnel is manually 651 configured, the operator configure the XC pointer to this 652 tunnel. 654 In case of PW label only (no outer tunnel) the ifIndex of 655 the port to carry the PW is configured here. 657 It is possible to associate a PW to one TE tunnel head-end 658 and a non-TE tunnel together. An indication in this table 659 will report the currently active one, In addition, in the 660 TE case the table reports the active tunnel instance 661 (i.e. the specific LSP in use). 662 " 664 AUGMENTS { pwVcMplsEntry } 666 ::= { pwVcMplsOutboundTable 1 } 668 PwVcMplsOutboundEntry ::= SEQUENCE { 669 pwVcMplsOutboundLsrXcIndex MplsIndexType, 670 pwVcMplsOutboundTunnelIndex MplsTunnelIndex, 671 pwVcMplsOutboundTunnelInstance MplsTunnelInstanceIndex, 672 pwVcMplsOutboundTunnelLclLSR MplsLsrIdentifier, 673 pwVcMplsOutboundTunnelPeerLSR MplsLsrIdentifier, 674 pwVcMplsOutboundIfIndex InterfaceIndexOrZero, 675 pwVcMplsOutboundTunnelTypeInUse INTEGER 676 } 678 pwVcMplsOutboundLsrXcIndex OBJECT-TYPE 679 SYNTAX MplsIndexType 680 MAX-ACCESS read-write 681 STATUS current 682 DESCRIPTION 683 "This object is applicable if pwVcMplsMplsType mplsNonTe(1) 684 bit is set, and MUST return a value of zero otherwise. 685 If the outer tunnel is signaled, the object is read-only 686 and indicate the XC index in the MPLS-LSR-STD-MIB of the 687 outer tunnel toward the peer. Otherwise (tunnel is set-up 688 manually) the operator define the XC index of the manually 689 created outer tunnel through this object. 690 " 691 ::= { pwVcMplsOutboundEntry 1 } 693 pwVcMplsOutboundTunnelIndex OBJECT-TYPE 694 Management Information Base 696 SYNTAX MplsTunnelIndex 697 MAX-ACCESS read-write 698 STATUS current 699 DESCRIPTION 700 "This object is applicable if pwVcMplsMplsType mplsTe(0) 701 bit is set, and MUST return a value of zero otherwise. 702 It is Part of set of indexes for outbound tunnel. 703 The operator set this object to represent the desired 704 tunnel head-end toward the peer for carrying the PW 705 traffic. 706 " 707 ::= { pwVcMplsOutboundEntry 2 } 709 pwVcMplsOutboundTunnelInstance OBJECT-TYPE 710 SYNTAX MplsTunnelInstanceIndex 711 MAX-ACCESS read-only 712 STATUS current 713 DESCRIPTION 714 "This object is applicable if pwVcMplsMplsType mplsTe(0) 715 bit is set, and MUST return a value of zero otherwise. 716 It indicates the actual tunnel instance that is currently 717 active and carrying the PW traffic - it should return the 718 value of zero until if the information from the MPLS-TE 719 application is not yet known. 720 " 721 ::= { pwVcMplsOutboundEntry 3 } 723 pwVcMplsOutboundTunnelLclLSR OBJECT-TYPE 724 SYNTAX MplsLsrIdentifier 725 MAX-ACCESS read-write 726 STATUS current 727 DESCRIPTION 728 "This object is applicable if pwVcMplsMplsType mplsTe(0) 729 bit is set, and MUST return a value of all zeros otherwise. 730 It is part of set of indexes for outbound tunnel. 731 The operator set this object to represent the desired 732 tunnel head-end toward the peer for carrying the PW 733 traffic. 734 " 735 ::= { pwVcMplsOutboundEntry 4 } 737 pwVcMplsOutboundTunnelPeerLSR OBJECT-TYPE 738 SYNTAX MplsLsrIdentifier 739 MAX-ACCESS read-write 740 STATUS current 741 DESCRIPTION 742 "This object is applicable if pwVcMplsMplsType mplsTe(0) 743 bit is set, and MUST return a value of zero otherwise. 744 It is part of set of indexes for outbound tunnel. It is 745 typically equal to pwVcPeerAddr. 746 " 747 Management Information Base 749 ::= { pwVcMplsOutboundEntry 5 } 751 pwVcMplsOutboundIfIndex OBJECT-TYPE 752 SYNTAX InterfaceIndexOrZero 753 MAX-ACCESS read-write 754 STATUS current 755 DESCRIPTION 756 "This object is applicable if pwVcMplsMplsType mplsTe(0) 757 bit is set, and MUST return a value of zero otherwise. 758 The operator configure the ifIndex of the outbound port 759 in this case. 760 " 761 ::= { pwVcMplsOutboundEntry 6 } 763 pwVcMplsOutboundTunnelTypeInUse OBJECT-TYPE 764 SYNTAX INTEGER { 765 notYetKnown (1), 766 mplsTe (2), 767 mplsNonTe (3), 768 vcOnly (4) 769 } 770 MAX-ACCESS read-only 771 STATUS current 772 DESCRIPTION 773 "This object indicates the current tunnel that is carrying 774 the PW traffic. 775 The value of notYetKnown(1) should be used if the agent is 776 currently unable to determine which tunnel or interface is 777 carrying the PW, for example because both tunnels are in 778 operational status down. 779 " 780 ::= { pwVcMplsOutboundEntry 7 } 782 -- End of PW MPLS Outbound Tunnel table 784 -- PW MPLS inbound table 786 pwVcMplsInboundTable OBJECT-TYPE 787 SYNTAX SEQUENCE OF PwVcMplsInboundEntry 788 MAX-ACCESS not-accessible 789 STATUS current 790 DESCRIPTION 791 "This table indicates the PW LDP XC entry in the 792 MPLS-LSR-STD-MIB for signaled PWs. 793 " 794 ::= { pwVcMplsObjects 3 } 796 pwVcMplsInboundEntry OBJECT-TYPE 797 SYNTAX PwVcMplsInboundEntry 798 MAX-ACCESS not-accessible 799 Management Information Base 801 STATUS current 802 DESCRIPTION 803 "A row in this table is created by the agent 804 for each signaled PW, and shows the XC index related to 805 the PW signaling in the inbound direction in the 806 MPLS-LSR-STD-MIB that controls and display the information 807 for all the LDP signaling processes in the local node. 808 " 810 INDEX { pwVcIndex } 812 ::= { pwVcMplsInboundTable 1 } 814 PwVcMplsInboundEntry ::= SEQUENCE { 815 pwVcMplsInboundXcIndex MplsIndexType 816 } 818 pwVcMplsInboundXcIndex OBJECT-TYPE 819 SYNTAX MplsIndexType 820 MAX-ACCESS read-only 821 STATUS current 822 DESCRIPTION 823 "The XC index representing this PW in the inbound 824 direction. Should return the value of zero if the 825 information is not yet known." 826 ::= { pwVcMplsInboundEntry 1 } 828 -- End of PW MPLS inbound table 830 -- PW to Non-TE mapping Table. 832 pwVcMplsNonTeMappingTable OBJECT-TYPE 833 SYNTAX SEQUENCE OF PwVcMplsNonTeMappingEntry 834 MAX-ACCESS not-accessible 835 STATUS current 836 DESCRIPTION 837 "This table indicates outbound Tunnel to a PW in non-TE 838 applications, maps the PW to it's (inbound) XC entry, and 839 indicates the PW to physical interface mapping for a PW 840 label to physical interface a PW label is in use without 841 outer tunnel. 842 " 843 ::= { pwVcMplsObjects 4 } 845 pwVcMplsNonTeMappingEntry OBJECT-TYPE 846 SYNTAX PwVcMplsNonTeMappingEntry 847 MAX-ACCESS not-accessible 848 STATUS current 849 DESCRIPTION 850 "A row in this table displays the association 851 between the PW and 852 Management Information Base 854 - it's non-TE MPLS outbound outer Tunnel or, 855 - it's XC entry in the MPLS-LSR-STD-MIB, 856 - it's physical interface if there is no outer tunnel 857 (PW label only) and manual configuration. 859 Rows are created in this table by the by the 860 agent depending on the setting of pwVcMplsMplsType: 862 - If pwVcMplsMplsType mplsNonTe(1) bit is set, the agent 863 creates a row for the outbound direction 864 (pwVcMplsNonTeMappingDirection set to psnBound(1)). 865 The pwVcMplsNonTeMappingXcIndex holds the XC index in the 866 MPLS-LSR-STD-MIB of the PSN bound outer tunnel. 867 pwVcMplsNonTeMappingIfIndex MUST be zero for this row. 869 - If pwVcMplsMplsType vcOnly(2) bit is set, the agent 870 creates a row for the outbound direction 871 (pwVcMplsNonTeMappingDirection set to psnBound(1)). 872 The pwVcMplsNonTeMappingIfIndex holds the ifIndex of the 873 physical port this PW will use in the outbound direction. 874 pwVcMplsNonTeMappingXcIndex MUST be zero for this row. 876 - If the PW has been set-up by signaling protocol (i.e. 877 pwVcOwner equal pwIdFecSignaling(2) or 878 genFecSignaling(3)), the agent creates a row for the 879 inbound direction (pwVcMplsNonTeMappingDirection set to 880 fromPsn(2)). 881 The pwVcMplsNonTeMappingXcIndex holds the XC index in the 882 MPLS-LSR-STD-MIB of the PW LDP generated XC entry. 883 pwVcMplsNonTeMappingIfIndex MUST be zero for this row. 885 An application can use this table to quickly retrieve the 886 PW carried over specific non-TE MPLS outer tunnel or 887 physical interface. 888 " 890 INDEX { pwVcMplsNonTeMappingDirection, 891 pwVcMplsNonTeMappingXcIndex, 892 pwVcMplsNonTeMappingIfIndex, 893 pwVcMplsNonTeMappingVcIndex } 895 ::= { pwVcMplsNonTeMappingTable 1 } 897 PwVcMplsNonTeMappingEntry ::= SEQUENCE { 898 pwVcMplsNonTeMappingDirection INTEGER, 899 pwVcMplsNonTeMappingXcIndex MplsIndexType, 900 pwVcMplsNonTeMappingIfIndex InterfaceIndexOrZero, 901 pwVcMplsNonTeMappingVcIndex PwVcIndexType 902 } 904 pwVcMplsNonTeMappingDirection OBJECT-TYPE 905 Management Information Base 907 SYNTAX INTEGER { 908 psnBound (1), 909 fromPsn (2) 910 } 911 MAX-ACCESS not-accessible 912 STATUS current 913 DESCRIPTION 914 "Index for the conceptual XC row identifying Tunnel to PW 915 mappings, indicating the direction of packet flow the entry 916 is related too. 917 psnBound(1) indicates that the entry is related to 918 packets toward the PSN. 919 fromPsn(2) indicates that the entry is related to 920 packets coming from the PSN. 921 " 922 ::= { pwVcMplsNonTeMappingEntry 1 } 924 pwVcMplsNonTeMappingXcIndex OBJECT-TYPE 925 SYNTAX MplsIndexType 926 MAX-ACCESS not-accessible 927 STATUS current 928 DESCRIPTION 929 "See the description clause of pwVcMplsNonTeMappingEntry for 930 the usage guidelines of this object." 931 ::= { pwVcMplsNonTeMappingEntry 2 } 933 pwVcMplsNonTeMappingIfIndex OBJECT-TYPE 934 SYNTAX InterfaceIndexOrZero 935 MAX-ACCESS not-accessible 936 STATUS current 937 DESCRIPTION 938 "See the description clause of pwVcMplsNonTeMappingEntry for 939 the usage guidelines of this object." 940 ::= { pwVcMplsNonTeMappingEntry 3 } 942 pwVcMplsNonTeMappingVcIndex OBJECT-TYPE 943 SYNTAX PwVcIndexType 944 MAX-ACCESS read-only 945 STATUS current 946 DESCRIPTION 947 "The value that represent the PW in the pwVcTable." 948 ::= { pwVcMplsNonTeMappingEntry 4 } 950 -- End of PW to Non-TE mapping Table. 952 -- PW to TE MPLS tunnels mapping Table. 954 pwVcMplsTeMappingTable OBJECT-TYPE 955 SYNTAX SEQUENCE OF PwVcMplsTeMappingEntry 956 MAX-ACCESS not-accessible 957 STATUS current 958 Management Information Base 960 DESCRIPTION 961 "This table enable the retrieval of a PW association to the 962 outbound MPLS tunnel for MPLS-TE applications." 963 ::= { pwVcMplsObjects 5 } 965 pwVcMplsTeMappingEntry OBJECT-TYPE 966 SYNTAX PwVcMplsTeMappingEntry 967 MAX-ACCESS not-accessible 968 STATUS current 969 DESCRIPTION 970 "A row in this table represents the association 971 between a PW and it's MPLS-TE outer (head-end) Tunnel. 973 An application can use this table to quickly retrieve the 974 list of the PWs that are configured on a specific MPLS TE 975 outer tunnel. 977 The pwVcMplsTeMappingTunnelInstance reports the actual 978 LSP out of the tunnel head-end that is currently 979 forwarding the traffic. 981 The table in indexed by the head-end indexes of a TE 982 tunnel and the PW index. 983 " 985 INDEX { pwVcMplsTeMappingTunnelIndex, 986 pwVcMplsTeMappingTunnelInstance, 987 pwVcMplsTeMappingTunnelPeerLsrID, 988 pwVcMplsTeMappingTunnelLocalLsrID, 989 pwVcMplsTeMappingVcIndex } 991 ::= { pwVcMplsTeMappingTable 1 } 993 PwVcMplsTeMappingEntry ::= SEQUENCE { 994 pwVcMplsTeMappingTunnelIndex MplsTunnelIndex, 995 pwVcMplsTeMappingTunnelInstance MplsTunnelInstanceIndex, 996 pwVcMplsTeMappingTunnelPeerLsrID MplsLsrIdentifier, 997 pwVcMplsTeMappingTunnelLocalLsrID MplsLsrIdentifier, 998 pwVcMplsTeMappingVcIndex PwVcIndexType 999 } 1001 pwVcMplsTeMappingTunnelIndex OBJECT-TYPE 1002 SYNTAX MplsTunnelIndex 1003 MAX-ACCESS not-accessible 1004 STATUS current 1005 DESCRIPTION 1006 "Primary index for the conceptual row identifying the 1007 MPLS-TE tunnel that is carrying the PW traffic." 1008 ::= { pwVcMplsTeMappingEntry 1 } 1010 pwVcMplsTeMappingTunnelInstance OBJECT-TYPE 1011 Management Information Base 1013 SYNTAX MplsTunnelInstanceIndex 1014 MAX-ACCESS not-accessible 1015 STATUS current 1016 DESCRIPTION 1017 "This object identify the MPLS-TE LSP that is carrying the 1018 PW traffic. Should return the value of zero if the 1019 information of the specific LSP is not yet known. 1020 Note that based on the recommendation in the 1021 MPLS-TC-STD-MIB, instance index 0 should refer to the 1022 configured tunnel interface." 1023 ::= { pwVcMplsTeMappingEntry 2 } 1025 pwVcMplsTeMappingTunnelPeerLsrID OBJECT-TYPE 1026 SYNTAX MplsLsrIdentifier 1027 MAX-ACCESS not-accessible 1028 STATUS current 1029 DESCRIPTION 1030 "Identifies the Peer LSR when the outer tunnel is MPLS-TE 1031 based." 1032 ::= { pwVcMplsTeMappingEntry 3 } 1034 pwVcMplsTeMappingTunnelLocalLsrID OBJECT-TYPE 1035 SYNTAX MplsLsrIdentifier 1036 MAX-ACCESS not-accessible 1037 STATUS current 1038 DESCRIPTION 1039 "Identifies the local LSR." 1040 ::= { pwVcMplsTeMappingEntry 4 } 1042 pwVcMplsTeMappingVcIndex OBJECT-TYPE 1043 SYNTAX PwVcIndexType 1044 MAX-ACCESS read-only 1045 STATUS current 1046 DESCRIPTION 1047 "The value that represent the PW in the pwVcTable." 1048 ::= { pwVcMplsTeMappingEntry 5 } 1050 -- End of PW to TE MPLS tunnels mapping Table. 1052 -- conformance information 1054 pwVcMplsGroups OBJECT IDENTIFIER ::= { pwVcMplsConformance 1 } 1055 pwVcMplsCompliances OBJECT IDENTIFIER ::= { pwVcMplsConformance 2 } 1057 -- Compliance requirement for fully compliant implementations. 1059 pwMplsModuleFullCompliance MODULE-COMPLIANCE 1060 STATUS current 1061 DESCRIPTION 1062 "The compliance statement for agents that provide full 1063 support for PW-MPLS MIB Module. Such devices can 1064 Management Information Base 1066 then be monitored and also be configured using 1067 this MIB module." 1069 MODULE -- this module 1070 MANDATORY-GROUPS { pwVcMplsGroup, 1071 pwVcMplsOutboundMainGroup, 1072 pwVcMplsInboundGroup, 1073 pwVcMplsMappingGroup 1074 } 1076 GROUP pwVcMplsOutboundTeGroup 1077 DESCRIPTION "This group MUST be supported if the implementation 1078 allows MPLS TE tunnels to carry PW traffic. 1079 " 1081 OBJECT pwVcMplsMplsType 1082 DESCRIPTION "Support of vcOnly(2) is not required. At least one 1083 of mplsTe(0) or mplsNonTe(1) MUST be supported if 1084 signaling of PW is supported. 1085 " 1087 OBJECT pwVcMplsExpBitsMode 1088 DESCRIPTION "Support of specifiedValue(2) and 1089 serviceDependant(3) 1090 is optional. 1091 " 1093 OBJECT pwVcMplsLocalLdpID 1094 MIN-ACCESS read-only 1095 DESCRIPTION "A read-write access is required if the 1096 implementation supports more than one LDP entity 1097 identifier for PW signaling. 1098 " 1100 OBJECT pwVcMplsLocalLdpEntityID 1101 MIN-ACCESS read-only 1102 DESCRIPTION "A read-write access is required if the 1103 implementation supports more than one LDP entity 1104 index for PW signaling. 1105 " 1107 OBJECT pwVcMplsOutboundLsrXcIndex 1108 MIN-ACCESS read-only 1109 DESCRIPTION "A value other than zero MUST be supported if the 1110 implementation support non TE signaling of the 1111 outer tunnel. 1112 A read-write access MUST be supported if the 1113 implementation supports manually setting of the PW 1114 labels and carrying them over non-TE tunnels. 1115 " 1116 Management Information Base 1118 OBJECT pwVcMplsOutboundIfIndex 1119 MIN-ACCESS read-only 1120 DESCRIPTION "A value other than zero and read-write operations 1121 MUST be supported if the implementation supports 1122 manully configured PW without MPLS outer tunnel. 1123 " 1124 ::= { pwVcMplsCompliances 1 } 1126 -- Compliance requirement for Read Only compliant implementations. 1128 pwMplsModuleReadOnlyCompliance MODULE-COMPLIANCE 1129 STATUS current 1130 DESCRIPTION 1131 "The compliance statement for agents that provide read 1132 only support for PW-MPLS MIB Module. Such devices can 1133 then be monitored but cannot be configured using this 1134 MIB module." 1136 MODULE -- this module 1137 MANDATORY-GROUPS { pwVcMplsGroup, 1138 pwVcMplsOutboundMainGroup, 1139 pwVcMplsInboundGroup, 1140 pwVcMplsMappingGroup 1141 } 1143 GROUP pwVcMplsOutboundTeGroup 1144 DESCRIPTION "This group MUST be supported if the implementation 1145 allows MPLS TE tunnels to carry PW traffic. 1146 " 1148 OBJECT pwVcMplsMplsType 1149 MIN-ACCESS read-only 1150 DESCRIPTION "Write access is not required. 1151 Support of vcOnly(2) is not required. At least one 1152 of mplsTe(0) or mplsNonTe(1) MUST be supported if 1153 signaling of PW is supported. 1154 " 1156 OBJECT pwVcMplsExpBitsMode 1157 MIN-ACCESS read-only 1158 DESCRIPTION "Write access is not required. 1159 Support of specifiedValue(2) and 1160 serviceDependant(3) 1161 is optional. 1162 " 1164 OBJECT pwVcMplsExpBits 1165 MIN-ACCESS read-only 1166 DESCRIPTION "Write access is not required. 1167 " 1168 Management Information Base 1170 OBJECT pwVcMplsTtl 1171 MIN-ACCESS read-only 1172 DESCRIPTION "Write access is not required. 1173 " 1175 OBJECT pwVcMplsLocalLdpID 1176 MIN-ACCESS read-only 1177 DESCRIPTION "Write access is not required. 1178 " 1180 OBJECT pwVcMplsLocalLdpEntityID 1181 MIN-ACCESS read-only 1182 DESCRIPTION "Write access is not required. 1183 " 1185 OBJECT pwVcMplsStorageType 1186 MIN-ACCESS read-only 1187 DESCRIPTION "Write access is not required. 1188 " 1190 OBJECT pwVcMplsOutboundLsrXcIndex 1191 MIN-ACCESS read-only 1192 DESCRIPTION "Write access is not required. 1193 A value other than zero MUST be supported if the 1194 implementation support non TE signaling of the 1195 outer tunnel. 1196 " 1198 OBJECT pwVcMplsOutboundTunnelIndex 1199 MIN-ACCESS read-only 1200 DESCRIPTION "Write access is not required. 1201 " 1203 OBJECT pwVcMplsOutboundTunnelLclLSR 1204 MIN-ACCESS read-only 1205 DESCRIPTION "Write access is not required. 1206 " 1208 OBJECT pwVcMplsOutboundTunnelPeerLSR 1209 MIN-ACCESS read-only 1210 DESCRIPTION "Write access is not required. 1211 " 1213 OBJECT pwVcMplsOutboundIfIndex 1214 MIN-ACCESS read-only 1215 DESCRIPTION "Write access is not required. 1216 A value other than zero MUST be supported if the 1217 implementation supports manually configured PW 1218 without MPLS outer tunnel. 1219 " 1220 Management Information Base 1222 ::= { pwVcMplsCompliances 2 } 1224 -- Units of conformance. 1226 pwVcMplsGroup OBJECT-GROUP 1227 OBJECTS { 1228 pwVcMplsMplsType, 1229 pwVcMplsExpBitsMode, 1230 pwVcMplsExpBits, 1231 pwVcMplsTtl, 1232 pwVcMplsLocalLdpID, 1233 pwVcMplsLocalLdpEntityID, 1234 pwVcMplsPeerLdpID, 1235 pwVcMplsStorageType 1236 } 1238 STATUS current 1239 DESCRIPTION 1240 "Collection of objects needed for PW over MPLS PSN 1241 configuration." 1242 ::= { pwVcMplsGroups 1 } 1244 pwVcMplsOutboundMainGroup OBJECT-GROUP 1245 OBJECTS { 1246 pwVcMplsOutboundLsrXcIndex, 1247 pwVcMplsOutboundIfIndex, 1248 pwVcMplsOutboundTunnelTypeInUse 1249 } 1251 STATUS current 1252 DESCRIPTION 1253 "Collection of objects needed for outbound association of 1254 PW and MPLS tunnel." 1255 ::= { pwVcMplsGroups 2 } 1257 pwVcMplsOutboundTeGroup OBJECT-GROUP 1258 OBJECTS { 1259 pwVcMplsOutboundTunnelIndex, 1260 pwVcMplsOutboundTunnelInstance, 1261 pwVcMplsOutboundTunnelLclLSR, 1262 pwVcMplsOutboundTunnelPeerLSR 1263 } 1265 STATUS current 1266 DESCRIPTION 1267 "Collection of objects needed for outbound association of 1268 PW and MPLS TE tunnel." 1269 ::= { pwVcMplsGroups 3 } 1270 Management Information Base 1272 pwVcMplsInboundGroup OBJECT-GROUP 1273 OBJECTS { 1274 pwVcMplsInboundXcIndex 1275 } 1277 STATUS current 1278 DESCRIPTION 1279 "Collection of objects needed for inbound PW presentation. 1280 This group MUST be supported if PW signaling through LDP is 1281 used." 1282 ::= { pwVcMplsGroups 4 } 1284 pwVcMplsMappingGroup OBJECT-GROUP 1285 OBJECTS { 1286 pwVcMplsNonTeMappingVcIndex, 1287 pwVcMplsTeMappingVcIndex 1288 } 1290 STATUS current 1291 DESCRIPTION 1292 "Collection of objects needed for mapping association of 1293 PW and MPLS tunnel." 1294 ::= { pwVcMplsGroups 5 } 1296 END -- of PW MPLS MIB Module 1298 8 Security Considerations 1300 It is clear that this MIB module is potentially useful for 1301 monitoring of PW capable PEs. This MIB module can also be used for 1302 configuration of certain objects, and anything that can be 1303 configured can be incorrectly configured, with potentially 1304 disastrous results. 1306 There are a number of management objects defined in this MIB module 1307 with a MAX-ACCESS clause of read-write and/or read-create. Such 1308 objects may be considered sensitive or vulnerable in some network 1309 environments. The support for SET operations in a non-secure 1310 environment without proper protection can have a negative effect on 1311 network operations. These are the tables and objects and their 1312 sensitivity/vulnerability: 1314 o the pwVcMplsTable, pwVcMplsNonTeMappingTable and 1315 pwVcMplsTeMappingTable collectively contain objects to 1316 provision PW over MPLS tunnels. Unauthorized access to 1317 objects in these tables, could result in disruption of 1318 traffic on the network. The use of stronger mechanisms 1319 such as SNMPv3 security should be considered where 1320 possible. Specifically, SNMPv3 VACM and USM MUST be used 1321 with any v3 agent which implements this MIB module. 1323 Management Information Base 1325 Administrators should consider whether read access to these 1326 objects should be allowed, since read access may be 1327 undesirable under certain circumstances. 1329 Some of the readable objects in this MIB module "i.e., objects with 1330 a MAX-ACCESS other than not-accessible" may be considered sensitive 1331 or vulnerable in some network environments. It is thus important 1332 to control even GET and/or NOTIFY access to these objects and 1333 possibly to even encrypt the values of these objects when sending 1334 them over the network via SNMP. These are the tables and objects 1335 and their sensitivity/vulnerability: 1337 o the pwVcMplsTable, pwVcMplsNonTeMappingTable, 1338 pwVcMplsTeMappingTable and pwVcMplsOutboundTable 1339 collectively show the PW over MPLS association. 1340 If an Administrator does not want to reveal this 1341 information, then these tables should be 1342 considered sensitive/vulnerable. 1344 SNMP versions prior to SNMPv3 did not include adequate security. 1345 Even if the network itself is secure "for example by using IPSec", 1346 even then, there is no control as to who on the secure network is 1347 allowed to access and GET/SET "read/change/create/delete" the 1348 objects in this MIB module. 1350 It is RECOMMENDED that implementers consider the security features 1351 as provided by the SNMPv3 framework "see [RFC3410], section 8", 1352 including full support for the SNMPv3 cryptographic mechanisms "for 1353 authentication and privacy". 1355 Further, deployment of SNMP versions prior to SNMPv3 is NOT 1356 RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to 1357 enable cryptographic security. It is then a customer/operator 1358 responsibility to ensure that the SNMP entity giving access to an 1359 instance of this MIB module, is properly configured to give access 1360 to the objects only to those principals "users" that have 1361 legitimate rights to indeed GET or SET "change/create/delete" them. 1363 9 IANA considerations 1365 As requested in the PW-TC-STD-MIB [PWTCMIB], PWE3 related standards 1366 track MIB modules should be rooted under the pwStdMIB subtree. The 1367 IANA is requested to assign { pwStdMIB 3 } to the PW-MPLS-STD-MIB 1368 module specified in this document. 1370 10 References 1372 0.1 Normative references 1373 Management Information Base 1375 [PWARCH] Bryant, S., et al, "PWE3 Architecture", work-in- 1376 progress. 1378 [PWREQ] Xiao, X., et al, "Requirements for Pseudo Wire 1379 Emulation Edge-to-Edge (PWE3)", work-in-progress. 1381 [PWTC] Nadeau, T., et al, "Definitions for Textual Conventions 1382 and OBJECT-IDENTITIES for Pseudo-Wires Management", 1383 work-in-progress. 1385 [PW-MIB] Zelig, D., et al, "Pseudo Wire (PW) Management 1386 Information Base", work-in-progress. 1388 [IF-MIB] McCloghrie, K., Kastenholz, F., �The Interfaces Group 1389 MIB�, RFC 2863, June 2000. 1391 [MPLSArch] Rosen, E., Viswanathan, A., and R. Callon, 1392 "Multiprotocol Label Switching Architecture", RFC 3031, 1393 Jan 2001. 1395 [LblStk] Rosen, E., Rekhter, Y., Tappan, D., Farinacci, D., 1396 Federokow, G., Li, T., and A. Conta, "MPLS Label Stack 1397 Encoding", RFC 3032, January 2001. 1399 [LSRMIB] Srinivasan, C., Viswanathan, A., and Nadeau, T., "MPLS 1400 Label Switch Router Management Information Base Using 1401 SMIv2", work-in-progress. 1403 [TEMIB] Srinivasan, C., Viswanathan, A., and Nadeau, T., "MPLS 1404 Traffic Engineering Management Information Base Using 1405 SMIv2", work-in-progress. 1407 [MPLSTCMIB] Nadeau, T., Cucchiara, J., "Definition of Textual 1408 Conventions and OBJECT-IDENTITIES for Multi-Protocol 1409 Label Switching (MPLS) Management", RFC 3811, June 1410 2004. 1412 [LDP] Andersson, L., et al, "LDP specification�, RFC 3036, 1413 January 2001. 1415 [BCP14] Bradner, S., "Key words for use in RFCs to Indicate 1416 requirement Levels", BCP 14, RFC 2119, March 1997. 1418 [RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, 1419 J.,Rose, M. and S. Waldbusser, "Structure of Management 1420 Information Version 2 (SMIv2)", STD 58, RFC 2578, April 1421 1999. 1423 Management Information Base 1425 [RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, 1426 J., Rose, M. and S. Waldbusser, "Textual Conventions 1427 for SMIv2", STD 58, RFC 2579, April 1999. 1429 [RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, 1430 J., Rose, M. and S. Waldbusser, "Conformance Statements 1431 for SMIv2", STD 58, RFC 2580, April 1999. 1433 0.2 Informative references 1435 [RFC3410] Case, J., Mundy, R., Partain, D. and B. Stewart, 1436 Introduction and Applicability Statements for Internet- 1437 Standard Management Framework", RFC 3410, December 1438 2002. 1440 11 Author's Addresses 1442 David Zelig 1443 Corrigent Systems 1444 126, Yigal Alon st. 1445 Tel Aviv, ISRAEL 1446 Phone: +972-3-6945273 1447 Email: davidz@corrigent.com 1449 Thomas D. Nadeau 1450 Cisco Systems, Inc. 1451 250 Apollo Drive 1452 Chelmsford, MA 01824 1453 Email: tnadeau@cisco.com 1455 Dave Danenberg 1456 Email: dave_danenberg@yahoo.com 1458 Andrew G. Malis 1459 Tellabs, Inc. 1460 2730 Orchard Parkway 1461 San Jose, CA 95134 1462 Email: Andy.Malis@tellabs.com 1464 Sharon Mantin 1465 AxONLink (Israel) Ltd 1466 9 Bareket St. 1467 Petah Tikva 49517, Israel 1468 Phone: +972-3-9263972 1469 Email: sharon.mantin@axonlink.com 1471 12 Full Copyright Statement 1472 Management Information Base 1474 Copyright (C) The Internet Society (2000). All Rights Reserved. 1476 This document and translations of it may be copied and furnished to 1477 others, and derivative works that comment on or otherwise explain 1478 it or assist in its implementation may be prepared, copied, 1479 published and distributed, in whole or in part, without restriction 1480 of any kind, provided that the above copyright notice and this 1481 paragraph are included on all such copies and derivative works. 1482 However, this document itself may not be modified in any way, such 1483 as by removing the copyright notice or references to the Internet 1484 Society or other Internet organizations, except as needed for the 1485 purpose of developing Internet standards in which case the 1486 procedures for copyrights defined in the Internet Standards process 1487 must be followed, or as required to translate it into languages 1488 other than English. 1490 The limited permissions granted above are perpetual and will not be 1491 revoked by the Internet Society or its successors or assigns. This 1492 document and the information contained herein is provided on an "AS 1493 IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING 1494 TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING 1495 BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION 1496 HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF 1497 MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 1499 13 Intellectual Property Notice 1501 The IETF takes no position regarding the validity or scope of any 1502 intellectual property or other rights that might be claimed to 1503 pertain to the implementation or use of the technology described in 1504 this document or the extent to which any license under such rights 1505 might or might not be available; neither does it represent that it 1506 has made any effort to identify any such rights. Information on 1507 the IETF's procedures with respect to rights in standards-track and 1508 standards-related documentation can be found in BCP-11 [RFC2028]. 1509 Copies of claims of rights made available for publication and any 1510 assurances of licenses to be made available, or the result of an 1511 attempt made to obtain a general license or permission for the use 1512 of such proprietary rights by implementors or users of this 1513 specification can be obtained from the IETF Secretariat. 1514 The IETF invites any interested party to bring to its attention any 1515 copyrights, patents or patent applications, or other proprietary 1516 rights that may cover technology that may be required to practice 1517 this standard. Please address the information to the IETF 1518 Executive Director.