idnits 2.17.1 draft-ietf-pwe3-pw-mpls-mib-11.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, updated by RFC 4748 on line 1413. -- Found old boilerplate from RFC 3979, Section 5, paragraph 1 on line 1424. -- Found old boilerplate from RFC 3979, Section 5, paragraph 2 on line 1431. -- Found old boilerplate from RFC 3979, Section 5, paragraph 3 on line 1437. 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 : ---------------------------------------------------------------------------- -- The document has examples using IPv4 documentation addresses according to RFC6890, but does not use any IPv6 documentation addresses. Maybe there should be IPv6 examples, too? Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust Copyright Line does not match the current year == Line 223 has weird spacing: '...N |PWin inSeg...' == Line 227 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 (February 26, 2007) is 6266 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) -- Possible downref: Non-RFC (?) normative reference: ref. 'PWMIB' -- Possible downref: Non-RFC (?) normative reference: ref. 'PWTC' ** Obsolete normative reference: RFC 4447 (Obsoleted by RFC 8077) Summary: 2 errors (**), 0 flaws (~~), 4 warnings (==), 10 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: August 30, 2007 Cisco Systems, Inc. 6 February 26, 2007 8 Pseudo-Wire (PW) over MPLS PSN Management Information Base 9 draft-ietf-pwe3-pw-mpls-mib-11 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 August 30, 2007. 36 Copyright Notice 38 Copyright (C) The IETF Trust (2007). 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. The Internet-Standard Management Framework . . . . . . . . . . 3 52 3. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3 53 4. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 54 5. Features Checklist . . . . . . . . . . . . . . . . . . . . . . 5 55 6. MIB Module Usage . . . . . . . . . . . . . . . . . . . . . . . 5 56 7. PW MPLS MIB Example . . . . . . . . . . . . . . . . . . . . . 7 57 8. Object Definitions . . . . . . . . . . . . . . . . . . . . . . 8 58 9. Security Considerations . . . . . . . . . . . . . . . . . . . 27 59 10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 29 60 11. References . . . . . . . . . . . . . . . . . . . . . . . . . . 29 61 11.1. Normative References . . . . . . . . . . . . . . . . . . 29 62 11.2. Informative References . . . . . . . . . . . . . . . . . 30 63 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 30 64 Intellectual Property and Copyright Statements . . . . . . . . . . 32 66 1. Introduction 68 This document describes a model for managing pseudo-wire services for 69 transmission over different flavors of MPLS tunnels. The general PW 70 MIB module [PWMIB] defines the parameters global to the PW regardless 71 of underlying PSN and emulated service. Indicating the MPLS PSN type 72 in PW-MIB references this module. 74 This document describes the MIB objects that define pseudo-wire 75 association to the MPLS PSN, in a way that is not specific to the 76 carried service. 78 Together, [RFC3811] and [RFC3812], describe the modeling of an MPLS 79 Tunnel, and a Tunnel's underlying cross-connects. This MIB module 80 supports MPLS-TE PSN, Non TE MPLS PSN (an outer tunnel created by LDP 81 or manually), and MPLS PW label only (no outer tunnel). 83 Comments should be made directly to the PWE3 mailing list at 84 pwe3@ietf.org. 86 2. The Internet-Standard Management Framework 88 For a detailed overview of the documents that describe the current 89 Internet-Standard Management Framework, please refer to section 7 of 90 [RFC3410]. 92 Managed objects are accessed via a virtual information store, termed 93 the Management Information Base or MIB. MIB objects are generally 94 accessed through the Simple Network Management Protocol (SNMP). 95 Objects in the MIB are defined using the mechanisms defined in the 96 Structure of Management Information (SMI). This memo specifies a MIB 97 module that is compliant to the SMIv2, which is described in STD 98 58,[RFC2578], STD 58, [RFC2579] and STD 58, [RFC2580]. 100 3. Terminology 102 This document uses terminology from the document describing the PW 103 architecture [RFC3985], [RFC3916] and [RFC4447]. 105 The terms "Outbound" and "Inbound" in this MIB module are based on 106 the common practice in the MPLS standards, i.e. "outbound" is toward 107 the PSN. However, where these terms are used in an object name, the 108 object description clarifies the exact packet direction to prevent 109 confusion with these terms in other documents. 111 "PSN Tunnel" is a general term indicating a virtual connection 112 between the two PWE3 edge devices. Each tunnel may potentially carry 113 multiple PWs inside. In the scope of this document, it is an MPLS 114 tunnel. 116 This document uses terminology from the document describing the MPLS 117 architecture [RFC3031] for MPLS PSN. A Label Switched Path (LSP) is 118 modeled as described in [RFC3811] and [RFC3812] via a series of 119 cross-connects through 1 or more Label Switch Routers (LSR). 121 In MPLS PSN, a PW connection typically uses a PW Label within a 122 Tunnel Label [RFC4447]. Multiple pseudo-wires each with a unique PW 123 Label can share the same Tunnel. For PW transport over MPLS, the 124 Tunnel Label is known as the "outer" Label, while the PW Label is 125 known as the "inner" Label. An exception to this is with adjacent 126 LSRs or the use of PHP. In this case, there is an option for PWs to 127 connect directly without an outer Label. 129 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 130 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 131 document are to be interpreted as described in RFC-2119 [BCP14]. 133 4. Overview 135 The MIB module structure for defining a PW service is composed of 136 three layers of MIB modules functioning together. This general model 137 is defined in the PWE3 architecture [RFC3985]. The layering model is 138 intended to sufficiently isolate PW services from the underlying PSN 139 layer that carries the emulated service. This is done at the same 140 time as providing a standard means for connecting any supported 141 services to any supported PSNs. 143 The first layer, known as the service layer, contains service- 144 specific modules These modules define service-specific management 145 objects that interface or collaborate with existing MIB modules for 146 the native version of the service. The service-specific module 147 "glues" the standard modules to the PWE3 MIB modules. 149 The next layer of the PWE3 MIB framework is the PW MIB module 150 [PWMIB]. This module is used to configure general parameters of PWs 151 that are common to all types of emulated services and PSNs. This 152 layer is connected to the service-specific layer above, and the PSN 153 layer below. 155 The PSN layer provides PSN-specific modules for each type of PSN. 156 These modules associate the PW with one or more "tunnels" that carry 157 the service over the PSN. These modules are used to "glue" the PW 158 service to the underlying PSN-specific MIB modules. This document 159 defines the MIB module for PW over MPLS PSN. 161 [PWTC] defines some of the object types used in these modules. 163 5. Features Checklist 165 The PW-MPLS-STD-MIB module is designed to satisfy the following 166 requirements and constraints: 168 - The MIB module supports both manually configured and signaled PWs. 170 - The MIB module supports point-to-point PW connections. 172 - The MIB module enables the use of any emulated service. 174 - The MIB module supports MPLS-TE outer tunnel, Non TE MPLS outer 175 tunnel (an outer tunnel signaled by LDP or set-up manually), and 176 no outer tunnel (where the PW label is the only label in the MPLS 177 stack). The later case is applicable for manual configuration of 178 PW over a single hop, as for signaled MPLS PSN even across a 179 single hop there is an MPLS tunnel even though the actual packet 180 may not contain the MPLS tunnel label due to PHP. 182 The MIB module uses TCs from [RFC2578], [RFC2579], [RFC2580], 183 [RFC2863], [RFC3811], [RFC3813], [PWTC] and [PWMIB]. 185 6. 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 tunnels A and B formed by cross- 211 connects (XCs) Ax and Bx continuing through LSR-N to LSR-P. The 212 concatenations of XCs create the tunnels. Note: 'X' denotes a 213 tunnel's cross-connect. 215 Tunnel-A 216 <- - - - - - - - - - - - - - - - - - - - - - - - - - - - 218 +---- (edge) LSR-M ---+ +--------- LSR-N ---------+ + LSR-P 219 |---+ | | | | 220 | | XC | | XC | | 221 + | A1 (M<-N) +----+ +----+ A2 (M<-P) +----+ +----+ 222 | | <------| | | |<--------------| | | | 223 <-->| N |PWin inSeg |MPLS| |MPLS| outSeg inSeg |MPLS| |MPLS| 224 N S | | <---X<-----| IF | | IF |<------X<------| IF | | IF | 225 A E | S | | |<-->| | | |<-->| | | 226 T R | | --->X----->| | | |------>X------>| | | | 227 I V | P |PWout outSeg| | | | inSeg outSeg | | | | 228 V I | | ------>| | | |-------------->| | | | 229 E C + | XC +----+ +----+ XC +----+ +----+ 230 E |---+ B1 (M->N) | | B2 (M->P) | | 231 | | | | | 232 +---------------------+ +-------------------------+ +----- 234 - - - - - - - - - - - - - - - - - - - - - - - - - - - -> 235 Tunnel-B 237 Figure 1: PW modeling over MPLS 239 The PW-MPLS-STD-MIB supports three options for MPLS network: 241 (1) In the MPLS-TE case, tunnels A and B are created via the MPLS- 242 TE-STD-MIB [RFC3812]. The tunnels are associated (in each peer 243 independently) to the PW by the four indexes that uniquely 244 identify the tunnel at the MPLS-TE-STD-MIB. 246 (2) In the Non-TE case, tunnels A1 and B1 are either manually 247 configured or set up with LDP. The tunnels are associated to 248 the PW by the XC index in the MPLS-LSR-STD-MIB [RFC3813]. 250 (3) In the PW label only case, there is no outer tunnel on top of 251 the PW label. This case is useful in case of adjacent PEs in 252 manual configuration mode. Note that for signaled tunnels, when 253 LSR-N acts as PHP for the outer tunnel label, there are still 254 entries for the outer tunnel in the relevant MPLS MIB modules, 255 so even for the case of adjacent LSRs, the relevant mode is 256 either MPLS-TE or non-TE. 258 A combination of MPLS-TE outer tunnel(s) and LDP outer tunnel for the 259 same PW is allowed through the pwMplsOutboundTunnel. The current 260 tunnel that is used to forward traffic is indicated in the object 261 pwMplsOutboundTunnelTypeInUse. 263 The PW MPLS MIB module reports through the inbound table the XC entry 264 in the LDP-STD-MIB [RFC3815] of the PW that were signaled through 265 LDP. 267 This MIB module assumes that a PW can be associated to one MPLS-TE 268 tunnel at a time. This tunnel may be composed of multiple instances 269 (i.e. LSP), each represented by a separate instance index. The 270 selection of the active LSP out of the possible LSPs in the tunnel is 271 out of the scope of this MIB module as it is part of the MPLS PSN 272 functionality. The current active LSP is reported through this MIB 273 module. 275 It is worth noting that inbound (tunnel originated in the remote PE) 276 mapping is not configured nor reported through the PW-MPLS-STD-MIB 277 module since the local PE does not know the inbound association 278 between specific PW and MPLS tunnels. 280 7. PW MPLS MIB Example 282 In this example (following the example provided in [PWMIB]) a PW has 283 been configured in the pwTbale in [PWMIB] with pwPsnType equal 284 'mpls', and we assume that the implementation in this example has 285 already an LDP tunnel to the peer node. 287 The agent creates an entry in pwMplsTable with the following 288 parameters: 290 pwMplsMplsType mplsNonTe(1), -- LDP tunnel 291 pwMplsExpBitsMode outerTunnel(1), -- Default 292 pwMplsExpBits 0, -- Default 293 pwMplsTtl 2, -- Default 294 pwMplsLocalLdpID 192.0.2.200:0, 295 pwMplsLocalLdpEntityIndex 1, 296 pwMplsPeerLdpID 192.0.2.5:0, 297 pwMplsStorageType nonVolatile(3) 299 The agent also creates an entry in pwMplsOutboundTable for reporting 300 the mapping of the PW on the LDP tunnel: 302 pwMplsOutboundLsrXcIndex 100, - The XC number for the 303 -- LDP Tunnel 304 pwMplsOutboundTunnelIndex 0, -- No TE tunnel 305 pwMplsOutboundTunnelInstance 0, -- No TE tunnel 306 pwMplsOutboundTunnelLclLSR 0, -- No TE tunnel 307 pwMplsOutboundTunnelPeerLSR 0, -- No TE tunnel 308 pwMplsOutboundIfIndex 0, -- Not applicable 309 pwMplsOutboundTunnelTypeInUse mplsNonTe(3) 311 The agent now creates entries for the PW in the following tables: 313 - pwMplsInboundTable 315 - pwMplsNonTeMappingTable (2 entries) 317 To create an MPLS TE tunnel to carry this PW, the operator make the 318 following steps: 320 - Set pwMplsMplsType in pwMplsTable to both mplsNonTe(1) and 321 mplsTe(0). 323 - Set pwMplsOutboundTunnelIndex, pwMplsOutboundTunnelInstance, 324 pwMplsOutboundTunnelLclLSR and pwMplsOutboundTunnelPeerLSR in 325 pwMplsOutboundTable to the MPLS TE tunnel that will carry this PW. 327 The agent will report the tunnel which the PW is currently using 328 through pwMplsOutboundTunnelTypeInUse, and will report the PW to MPLS 329 TE tunnel/LSP mapping in pwMplsTeMappingTable. 331 8. Object Definitions 333 PW-MPLS-STD-MIB DEFINITIONS ::= BEGIN 335 IMPORTS 336 MODULE-IDENTITY, OBJECT-TYPE, Unsigned32, transmission 337 FROM SNMPv2-SMI -- [RFC2578] 339 MODULE-COMPLIANCE, OBJECT-GROUP 340 FROM SNMPv2-CONF -- [RFC2580] 342 StorageType 343 FROM SNMPv2-TC -- [RFC2579] 345 InterfaceIndexOrZero 346 FROM IF-MIB -- [RFC2863] 348 MplsTunnelIndex, MplsTunnelInstanceIndex, 349 MplsLdpIdentifier, MplsLsrIdentifier 350 FROM MPLS-TC-STD-MIB -- [RFC3811] 352 MplsIndexType 353 FROM MPLS-LSR-STD-MIB -- [RFC3813] 355 PwIndexType 356 FROM PW-TC-STD-MIB -- [PWTC] 357 -- RFC Editor: Please replace PWTC with the RFC number and remove 358 -- this note. 360 pwIndex -- [PWMIB] 361 -- RFC Editor: Please replace PWMIB with the RFC number and remove 362 -- this note. 363 FROM PW-STD-MIB 365 ; 367 pwMplsStdMIB MODULE-IDENTITY 368 LAST-UPDATED "200701311200Z" -- 31 January 2007 12:00:00 GMT 369 ORGANIZATION "Pseudo Wire Edge-to-Edge Emulation (PWE3) Working 370 Group." 371 CONTACT-INFO 372 " 373 David Zelig, Editor 374 E-mail: davidz@corrigent.com 376 Thomas D. Nadeau, Editor 377 Email: tnadeau@cisco.com 379 The PWE3 Working Group (email distribution pwe3@ietf.org, 380 http://www.ietf.org/html.charters/pwe3-charter.html) 381 " 382 DESCRIPTION 383 "This MIB module complements the PW-STD-MIB module for PW 384 operation over MPLS. 386 Copyright (C) The IETF Trust (2007). This version 387 of this MIB module is part of RFC yyyy; see the RFC 388 itself for full legal notices. 389 -- RFC Ed.: replace yyyy with actual RFC number & remove 390 -- this note 391 " 392 -- Revision history. 393 REVISION "200701311200Z" -- 31 January 2007 12:00:00 GMT 394 DESCRIPTION 395 "First published as RFCWXYZ. " 396 -- RFC Editor: Please replace WXYZ with the correct # and remove this 397 -- note 399 ::= { transmission XXXX } 400 -- RFC Editor: To be assigned by IANA. Please replace XXXX 401 -- with the assigned value and remove this note. 403 -- Top-level components of this MIB. 405 -- Notifications 406 pwMplsNotifications OBJECT IDENTIFIER 407 ::= { pwMplsStdMIB 0 } 409 -- Tables, Scalars 410 pwMplsObjects OBJECT IDENTIFIER 411 ::= { pwMplsStdMIB 1 } 412 -- Conformance 413 pwMplsConformance OBJECT IDENTIFIER 414 ::= { pwMplsStdMIB 2 } 416 -- PW MPLS table 418 pwMplsTable OBJECT-TYPE 419 SYNTAX SEQUENCE OF PwMplsEntry 420 MAX-ACCESS not-accessible 421 STATUS current 422 DESCRIPTION 423 "This table controls MPLS specific parameters when the PW is 424 going to be carried over MPLS PSN." 425 ::= { pwMplsObjects 1 } 427 pwMplsEntry OBJECT-TYPE 428 SYNTAX PwMplsEntry 429 MAX-ACCESS not-accessible 430 STATUS current 431 DESCRIPTION 432 "A row in this table represents parameters specific to MPLS 433 PSN for a pseudo-wire (PW). The row is created 434 automatically by the local agent if the pwPsnType is 435 MPLS. It is indexed by pwIndex, which uniquely 436 identifying a singular PW. 437 Manual entries in this table SHOULD be preserved after a 438 re-boot, the agent MUST ensure the integrity of those 439 entries. 440 If the set of entries of a specific row were found to be 441 non consistent after reboot, the PW pwOperStatus MUST be 442 declared as down(2). 443 Any read-write object in this table MAY be changed at any 444 time, however change of some objects (for example 445 pwMplsMplsType) during PW forwarding state MAY cause traffic 446 disruption." 448 INDEX { pwIndex } 450 ::= { pwMplsTable 1 } 452 PwMplsEntry ::= SEQUENCE { 453 pwMplsMplsType BITS, 454 pwMplsExpBitsMode INTEGER, 455 pwMplsExpBits Unsigned32, 456 pwMplsTtl Unsigned32, 457 pwMplsLocalLdpID MplsLdpIdentifier, 458 pwMplsLocalLdpEntityIndex Unsigned32, 459 pwMplsPeerLdpID MplsLdpIdentifier, 460 pwMplsStorageType StorageType 461 } 463 pwMplsMplsType OBJECT-TYPE 464 SYNTAX BITS { 465 mplsTe (0), 466 mplsNonTe (1), 467 pwOnly (2) 468 } 469 MAX-ACCESS read-write 470 STATUS current 471 DESCRIPTION 472 "This object is set by the operator to indicate the outer 473 tunnel types, if exists. mplsTe(0) is used if the outer 474 tunnel is set up by MPLS-TE, and mplsNonTe(1) is used if the 475 outer tunnel is set up by LDP or manually. Combination of 476 mplsTe(0) and mplsNonTe(1) MAY exist together. 477 pwOnly(2) is used if there is no outer tunnel label, i.e. 478 in static provisioning without an MPLS tunnel. pwOnly(2) 479 cannot be combined with mplsNonTe(1) or mplsTe(0). 480 An implementation that can identify automatically that the 481 peer node is directly connected, MAY support the bit 482 pwOnly(2) as read-only. 483 " 484 DEFVAL { { mplsNonTe } } 485 ::= { pwMplsEntry 1 } 487 pwMplsExpBitsMode OBJECT-TYPE 488 SYNTAX INTEGER { 489 outerTunnel (1), 490 specifiedValue (2), 491 serviceDependant (3) 492 } 494 MAX-ACCESS read-write 495 STATUS current 496 DESCRIPTION 497 "This object is set by the operator to determine the PW shim 498 label EXP bits. The value of outerTunnel(1) is used where 499 there is an outer tunnel - pwMplsMplsType equals to 500 mplsTe(0) or mplsNonTe(1). Note that in this case there 501 is no need to mark the PW label with the EXP bits, since the 502 PW label is not visible to the intermediate nodes. 503 If there is no outer tunnel, specifiedValue(2) indicates 504 that the value is specified by pwMplsExpBits, and 505 serviceDependant(3) indicates that the EXP bits are set 506 based on a rule which is implementation specific." 508 DEFVAL { outerTunnel } 509 ::= { pwMplsEntry 2 } 511 pwMplsExpBits OBJECT-TYPE 512 SYNTAX Unsigned32 (0..7) 513 MAX-ACCESS read-write 514 STATUS current 515 DESCRIPTION 516 "This object is set by the operator to indicate the MPLS EXP 517 bits to be used on the PW shim label if pwMplsExpBitsMode is 518 specifiedValue(2), zero otherwise." 519 DEFVAL { 0 } 520 ::= { pwMplsEntry 3 } 522 pwMplsTtl OBJECT-TYPE 523 SYNTAX Unsigned32 (0..255) 524 MAX-ACCESS read-write 525 STATUS current 526 DESCRIPTION 527 "This object is set by the operator to indicate the PW TTL 528 value to be used on the PW shim label." 529 DEFVAL { 2 } 530 ::= { pwMplsEntry 4 } 532 pwMplsLocalLdpID OBJECT-TYPE 533 SYNTAX MplsLdpIdentifier 534 MAX-ACCESS read-write 535 STATUS current 536 DESCRIPTION 537 "The local LDP identifier of the LDP entity creating 538 this PW in the local node. As the PW labels are always 539 set from the per-platform label space, the last two octets 540 in the LDP ID MUST always both be zeros." 541 REFERENCE 542 "'LDP specifications', RFC 3036 section 2.2.2." 543 ::= { pwMplsEntry 5 } 545 pwMplsLocalLdpEntityIndex OBJECT-TYPE 546 SYNTAX Unsigned32 (1..4294967295) 547 MAX-ACCESS read-write 548 STATUS current 549 DESCRIPTION 550 "The local node LDP Entity Index of the LDP entity creating 551 this PW." 552 ::= { pwMplsEntry 6 } 554 pwMplsPeerLdpID OBJECT-TYPE 555 SYNTAX MplsLdpIdentifier 556 MAX-ACCESS read-only 557 STATUS current 558 DESCRIPTION 559 "The peer LDP identifier as identified from the LDP 560 session. Should return the value of zero if not applicable 561 or not known yet." 562 ::= { pwMplsEntry 7 } 564 pwMplsStorageType OBJECT-TYPE 565 SYNTAX StorageType 566 MAX-ACCESS read-write 567 STATUS current 568 DESCRIPTION 569 "This variable indicates the storage type for this row." 570 DEFVAL { nonVolatile } 571 ::= { pwMplsEntry 8 } 573 -- End of PW MPLS Table 575 -- Pseudo-Wire MPLS Outbound Tunnel Table 577 pwMplsOutboundTable OBJECT-TYPE 578 SYNTAX SEQUENCE OF PwMplsOutboundEntry 579 MAX-ACCESS not-accessible 580 STATUS current 581 DESCRIPTION 582 "This table reports and configures the current outbound MPLS 583 tunnels (i.e. toward the PSN) or the physical interface in 584 the case of a PW label only that carries the PW traffic. It 585 also reports the current outer tunnel and LSP which forward 586 the PW traffic." 587 ::= { pwMplsObjects 2 } 589 pwMplsOutboundEntry OBJECT-TYPE 590 SYNTAX PwMplsOutboundEntry 591 MAX-ACCESS not-accessible 592 STATUS current 593 DESCRIPTION 594 "A row in this table configures the outer tunnel used for 595 carrying the PW traffic toward the PSN. 596 In the case of PW labels only, it configures the interface 597 that will carry the PW traffic. 599 An entry in this table augments the pwMplsEntry, and is 600 created automatically when the corresponding row has been 601 created by the agent in the pwMplsEntry. 603 This table points to the appropriate MPLS MIB module. 604 In the MPLS-TE case, the three variables relevant to the 605 indexing of a TE tunnel head-end (as used in the 606 MPLS-TE-STD-MIB) are to be configured, and the tunnel 607 instance indicates the LSP that is currently in use for 608 forwarding the traffic. 610 In case of signaled Non-TE MPLS (an outer tunnel label 611 assigned by LDP) the table points to the XC entry in the 612 LSR-STD-MIB. If the Non-TE MPLS tunnel is manually 613 configured, the operator configures the XC pointer to this 614 tunnel. 616 In case of PW label only (no outer tunnel) the ifIndex of 617 the port to carry the PW is configured here. 619 It is possible to associate a PW to one TE tunnel head-end 620 and a non-TE tunnel together. An indication in this table 621 will report the currently active one. In addition, in the 622 TE case the table reports the active tunnel instance 623 (i.e. the specific LSP in use). 624 Any read-write object in this table MAY be changed at any 625 time, however change of some objects (for example 626 MPLS-TE indexes) during PW forwarding state MAY cause traffic 627 disruption." 629 AUGMENTS { pwMplsEntry } 630 ::= { pwMplsOutboundTable 1 } 632 PwMplsOutboundEntry ::= SEQUENCE { 633 pwMplsOutboundLsrXcIndex MplsIndexType, 634 pwMplsOutboundTunnelIndex MplsTunnelIndex, 635 pwMplsOutboundTunnelInstance MplsTunnelInstanceIndex, 636 pwMplsOutboundTunnelLclLSR MplsLsrIdentifier, 637 pwMplsOutboundTunnelPeerLSR MplsLsrIdentifier, 638 pwMplsOutboundIfIndex InterfaceIndexOrZero, 639 pwMplsOutboundTunnelTypeInUse INTEGER 640 } 642 pwMplsOutboundLsrXcIndex OBJECT-TYPE 643 SYNTAX MplsIndexType 644 MAX-ACCESS read-write 645 STATUS current 646 DESCRIPTION 647 "This object is applicable if pwMplsMplsType mplsNonTe(1) 648 bit is set, and MUST return a value of zero otherwise. 649 If the outer tunnel is signaled, the object is read-only 650 and indicates the XC index in the MPLS-LSR-STD-MIB of the 651 outer tunnel toward the peer. Otherwise (tunnel is set up 652 manually) the operator defines the XC index of the manually- 653 created outer tunnel through this object. 654 " 655 ::= { pwMplsOutboundEntry 1 } 657 pwMplsOutboundTunnelIndex OBJECT-TYPE 658 SYNTAX MplsTunnelIndex 659 MAX-ACCESS read-write 660 STATUS current 661 DESCRIPTION 662 "This object is applicable if pwMplsMplsType mplsTe(0) 663 bit is set, and MUST return a value of zero otherwise. 664 It is part of the set of indexes for the outbound tunnel. 665 The operator sets this object to represent the desired 666 tunnel head-end toward the peer for carrying the PW 667 traffic. 668 " 669 ::= { pwMplsOutboundEntry 2 } 671 pwMplsOutboundTunnelInstance OBJECT-TYPE 672 SYNTAX MplsTunnelInstanceIndex 673 MAX-ACCESS read-only 674 STATUS current 675 DESCRIPTION 676 "This object is applicable if pwMplsMplsType mplsTe(0) 677 bit is set, and MUST return a value of zero otherwise. 678 It indicates the actual tunnel instance that is currently 679 active and carrying the PW traffic. It SHOULD return the 680 value of zero if the information from the MPLS-TE 681 application is not yet known. 682 " 683 ::= { pwMplsOutboundEntry 3 } 685 pwMplsOutboundTunnelLclLSR OBJECT-TYPE 686 SYNTAX MplsLsrIdentifier 687 MAX-ACCESS read-write 688 STATUS current 689 DESCRIPTION 690 "This object is applicable if pwMplsMplsType mplsTe(0) 691 bit is set, and MUST return a value of all zeros otherwise. 692 It is part of the set of indexes for the outbound tunnel. 693 The operator sets this object to represent the desired 694 tunnel head-end toward the peer for carrying the PW 695 traffic. 696 " 697 ::= { pwMplsOutboundEntry 4 } 699 pwMplsOutboundTunnelPeerLSR OBJECT-TYPE 700 SYNTAX MplsLsrIdentifier 701 MAX-ACCESS read-write 702 STATUS current 703 DESCRIPTION 704 "This object is applicable if pwMplsMplsType mplsTe(0) 705 bit is set, and MUST return a value of zero otherwise. 706 It is part of the set of indexes for the outbound tunnel. 707 It is typically equals to pwPeerAddr. 708 " 709 ::= { pwMplsOutboundEntry 5 } 711 pwMplsOutboundIfIndex OBJECT-TYPE 712 SYNTAX InterfaceIndexOrZero 713 MAX-ACCESS read-write 714 STATUS current 715 DESCRIPTION 716 "This object is applicable if pwMplsMplsType pwOnly(0) 717 bit is set, and MUST return a value of zero otherwise. 718 The operator configures the ifIndex of the outbound port 719 in this case. 720 " 721 ::= { pwMplsOutboundEntry 6 } 723 pwMplsOutboundTunnelTypeInUse OBJECT-TYPE 724 SYNTAX INTEGER { 725 notYetKnown (1), 726 mplsTe (2), 727 mplsNonTe (3), 728 pwOnly (4) 729 } 730 MAX-ACCESS read-only 731 STATUS current 732 DESCRIPTION 733 "This object indicates the current tunnel that is carrying 734 the PW traffic. 735 The value of notYetKnown(1) should be used if the agent is 736 currently unable to determine which tunnel or interface is 737 carrying the PW, for example because both tunnels are in 738 operational status down. 739 " 740 ::= { pwMplsOutboundEntry 7 } 742 -- End of PW MPLS Outbound Tunnel table 744 -- PW MPLS inbound table 746 pwMplsInboundTable OBJECT-TYPE 747 SYNTAX SEQUENCE OF PwMplsInboundEntry 748 MAX-ACCESS not-accessible 749 STATUS current 750 DESCRIPTION 751 "This table indicates the PW LDP XC entry in the 752 MPLS-LSR-STD-MIB for signaled PWs. 753 " 754 ::= { pwMplsObjects 3 } 756 pwMplsInboundEntry OBJECT-TYPE 757 SYNTAX PwMplsInboundEntry 758 MAX-ACCESS not-accessible 759 STATUS current 760 DESCRIPTION 761 "A row in this table is created by the agent 762 for each signaled PW, and shows the XC index related to 763 the PW signaling in the inbound direction in the 764 MPLS-LSR-STD-MIB that controls and display the information 765 for all the LDP signaling processes in the local node. 766 " 767 INDEX { pwIndex } 769 ::= { pwMplsInboundTable 1 } 771 PwMplsInboundEntry ::= SEQUENCE { 772 pwMplsInboundXcIndex MplsIndexType 773 } 775 pwMplsInboundXcIndex OBJECT-TYPE 776 SYNTAX MplsIndexType 777 MAX-ACCESS read-only 778 STATUS current 779 DESCRIPTION 780 "The XC index representing this PW in the inbound 781 direction. It MUST return the value of zero if the 782 information is not yet known." 783 ::= { pwMplsInboundEntry 1 } 785 -- End of PW MPLS inbound table 787 -- PW to Non-TE mapping Table. 789 pwMplsNonTeMappingTable OBJECT-TYPE 790 SYNTAX SEQUENCE OF PwMplsNonTeMappingEntry 791 MAX-ACCESS not-accessible 792 STATUS current 793 DESCRIPTION 794 "This table indicates the PW association to the outbound 795 Tunnel in non-TE applications, maps the PW to it's (inbound) 796 XC entry, and indicates the PW-to-physical interface mapping 797 for a PW without an outer tunnel. 798 " 799 ::= { pwMplsObjects 4 } 801 pwMplsNonTeMappingEntry OBJECT-TYPE 802 SYNTAX PwMplsNonTeMappingEntry 803 MAX-ACCESS not-accessible 804 STATUS current 805 DESCRIPTION 806 "A row in this table displays the association 807 between the PW and 808 - its non-TE MPLS outbound outer Tunnel or, 809 - its XC entry in the MPLS-LSR-STD-MIB, 810 - its physical interface if there is no outer tunnel 811 (PW label only) and manual configuration. 813 Rows are created in this table by the agent depending on 814 the setting of pwMplsMplsType: 816 - If pwMplsMplsType mplsNonTe(1) bit is set, the agent 817 creates a row for the outbound direction 818 (pwMplsNonTeMappingDirection set to psnBound(1)). 819 The pwMplsNonTeMappingXcIndex holds the XC index in the 820 MPLS-LSR-STD-MIB of the PSN bound outer tunnel. 821 pwMplsNonTeMappingIfIndex MUST be zero for this row. 823 - If pwMplsMplsType pwOnly(2) bit is set, the agent 824 creates a row for the outbound direction 825 (pwMplsNonTeMappingDirection set to psnBound(1)). 826 The pwMplsNonTeMappingIfIndex holds the ifIndex of the 827 physical port this PW will use in the outbound direction. 828 pwMplsNonTeMappingXcIndex MUST be zero for this row. 830 - If the PW has been set up by a signaling protocol (i.e. 831 pwOwner equal pwIdFecSignaling(2) or 832 genFecSignaling(3)), the agent creates a row for the 833 inbound direction (pwMplsNonTeMappingDirection set to 834 fromPsn(2)). 835 The pwMplsNonTeMappingXcIndex holds the XC index in the 836 MPLS-LSR-STD-MIB of the PW LDP generated XC entry. 837 pwMplsNonTeMappingIfIndex MUST be zero for this row. 839 An application can use this table to quickly retrieve the 840 PW carried over specific non-TE MPLS outer tunnel or 841 physical interface. 842 " 844 INDEX { pwMplsNonTeMappingDirection, 845 pwMplsNonTeMappingXcIndex, 846 pwMplsNonTeMappingIfIndex, 847 pwMplsNonTeMappingPwIndex } 849 ::= { pwMplsNonTeMappingTable 1 } 851 PwMplsNonTeMappingEntry ::= SEQUENCE { 852 pwMplsNonTeMappingDirection INTEGER, 853 pwMplsNonTeMappingXcIndex MplsIndexType, 854 pwMplsNonTeMappingIfIndex InterfaceIndexOrZero, 855 pwMplsNonTeMappingPwIndex PwIndexType 856 } 858 pwMplsNonTeMappingDirection OBJECT-TYPE 859 SYNTAX INTEGER { 860 psnBound (1), 861 fromPsn (2) 862 } 863 MAX-ACCESS not-accessible 864 STATUS current 865 DESCRIPTION 866 "Index for the conceptual XC row identifying the tunnel-to-PW 867 mappings, indicating the direction of the packet flow for 868 this entry. 869 psnBound(1) indicates that the entry is related to 870 packets toward the PSN. 871 fromPsn(2) indicates that the entry is related to 872 packets coming from the PSN. 873 " 874 ::= { pwMplsNonTeMappingEntry 1 } 876 pwMplsNonTeMappingXcIndex OBJECT-TYPE 877 SYNTAX MplsIndexType 878 MAX-ACCESS not-accessible 879 STATUS current 880 DESCRIPTION 881 "See the description clause of pwMplsNonTeMappingEntry for 882 the usage guidelines of this object." 883 ::= { pwMplsNonTeMappingEntry 2 } 885 pwMplsNonTeMappingIfIndex OBJECT-TYPE 886 SYNTAX InterfaceIndexOrZero 887 MAX-ACCESS not-accessible 888 STATUS current 889 DESCRIPTION 890 "See the description clause of pwMplsNonTeMappingEntry for 891 the usage guidelines of this object." 892 ::= { pwMplsNonTeMappingEntry 3 } 894 pwMplsNonTeMappingPwIndex OBJECT-TYPE 895 SYNTAX PwIndexType 896 MAX-ACCESS read-only 897 STATUS current 898 DESCRIPTION 899 "The value that represent the PW in the pwTable." 900 ::= { pwMplsNonTeMappingEntry 4 } 902 -- End of PW to Non-TE mapping Table. 904 -- PW to TE MPLS tunnels mapping Table. 906 pwMplsTeMappingTable OBJECT-TYPE 907 SYNTAX SEQUENCE OF PwMplsTeMappingEntry 908 MAX-ACCESS not-accessible 909 STATUS current 910 DESCRIPTION 911 "This table reports the PW association to the 912 outbound MPLS tunnel for MPLS-TE applications." 913 ::= { pwMplsObjects 5 } 915 pwMplsTeMappingEntry OBJECT-TYPE 916 SYNTAX PwMplsTeMappingEntry 917 MAX-ACCESS not-accessible 918 STATUS current 919 DESCRIPTION 920 "A row in this table represents the association 921 between a PW and its MPLS-TE outer (head-end) Tunnel. 923 An application can use this table to quickly retrieve the 924 list of the PWs that are configured on a specific MPLS TE 925 outer tunnel. 927 The pwMplsTeMappingTunnelInstance reports the actual 928 LSP out of the tunnel head-end that is currently 929 forwarding the traffic. 931 The table in indexed by the head-end indexes of a TE 932 tunnel and the PW index. 933 " 935 INDEX { pwMplsTeMappingTunnelIndex, 936 pwMplsTeMappingTunnelInstance, 937 pwMplsTeMappingTunnelPeerLsrID, 938 pwMplsTeMappingTunnelLocalLsrID, 939 pwMplsTeMappingPwIndex } 941 ::= { pwMplsTeMappingTable 1 } 943 PwMplsTeMappingEntry ::= SEQUENCE { 944 pwMplsTeMappingTunnelIndex MplsTunnelIndex, 945 pwMplsTeMappingTunnelInstance MplsTunnelInstanceIndex, 946 pwMplsTeMappingTunnelPeerLsrID MplsLsrIdentifier, 947 pwMplsTeMappingTunnelLocalLsrID MplsLsrIdentifier, 948 pwMplsTeMappingPwIndex PwIndexType 949 } 951 pwMplsTeMappingTunnelIndex OBJECT-TYPE 952 SYNTAX MplsTunnelIndex 953 MAX-ACCESS not-accessible 954 STATUS current 955 DESCRIPTION 956 "Primary index for the conceptual row identifying the 957 MPLS-TE tunnel that is carrying the PW traffic." 958 ::= { pwMplsTeMappingEntry 1 } 960 pwMplsTeMappingTunnelInstance OBJECT-TYPE 961 SYNTAX MplsTunnelInstanceIndex 962 MAX-ACCESS not-accessible 963 STATUS current 964 DESCRIPTION 965 "This object identifies the MPLS-TE LSP that is carrying the 966 PW traffic. It MUST return the value of zero if the 967 information of the specific LSP is not yet known. 968 Note that based on the recommendation in the 969 MPLS-TC-STD-MIB, instance index 0 should refer to the 970 configured tunnel interface." 971 ::= { pwMplsTeMappingEntry 2 } 973 pwMplsTeMappingTunnelPeerLsrID OBJECT-TYPE 974 SYNTAX MplsLsrIdentifier 975 MAX-ACCESS not-accessible 976 STATUS current 977 DESCRIPTION 978 "This object identifies the Peer LSR when the outer tunnel 979 is MPLS-TE." 980 ::= { pwMplsTeMappingEntry 3 } 982 pwMplsTeMappingTunnelLocalLsrID OBJECT-TYPE 983 SYNTAX MplsLsrIdentifier 984 MAX-ACCESS not-accessible 985 STATUS current 986 DESCRIPTION 987 "This object identifies the local LSR." 988 ::= { pwMplsTeMappingEntry 4 } 990 pwMplsTeMappingPwIndex OBJECT-TYPE 991 SYNTAX PwIndexType 992 MAX-ACCESS read-only 993 STATUS current 994 DESCRIPTION 995 "This object returns the value that represents the PW in the 996 pwTable." 997 ::= { pwMplsTeMappingEntry 5 } 999 -- End of PW to TE MPLS tunnels mapping Table. 1001 -- conformance information 1003 pwMplsGroups OBJECT IDENTIFIER ::= { pwMplsConformance 1 } 1004 pwMplsCompliances OBJECT IDENTIFIER ::= { pwMplsConformance 2 } 1006 -- Compliance requirement for fully compliant implementations. 1008 pwMplsModuleFullCompliance MODULE-COMPLIANCE 1009 STATUS current 1010 DESCRIPTION 1011 "The compliance statement for agents that provide full 1012 support for PW-MPLS MIB Module. Such devices can 1013 then be monitored and also be configured using 1014 this MIB module." 1016 MODULE -- this module 1017 MANDATORY-GROUPS { pwMplsGroup, 1018 pwMplsOutboundMainGroup, 1019 pwMplsInboundGroup, 1020 pwMplsMappingGroup 1021 } 1023 GROUP pwMplsOutboundTeGroup 1024 DESCRIPTION "This group MUST be supported if the implementation 1025 allows MPLS TE tunnels to carry PW traffic. 1026 " 1028 OBJECT pwMplsMplsType 1029 DESCRIPTION "Support of pwOnly(2) is not required. At least one 1030 of mplsTe(0) or mplsNonTe(1) MUST be supported if 1031 signaling of PW is supported. 1032 " 1034 OBJECT pwMplsExpBitsMode 1035 DESCRIPTION "Support of specifiedValue(2) and 1036 serviceDependant(3) is optional. 1037 " 1039 OBJECT pwMplsLocalLdpID 1040 MIN-ACCESS read-only 1041 DESCRIPTION "A read-write access is required if the 1042 implementation supports more than one LDP entity 1043 identifier for PW signaling. 1044 " 1046 OBJECT pwMplsLocalLdpEntityIndex 1047 MIN-ACCESS read-only 1048 DESCRIPTION "A read-write access is required if the 1049 implementation supports more than one LDP entity 1050 index for PW signaling. 1051 " 1053 OBJECT pwMplsOutboundLsrXcIndex 1054 MIN-ACCESS read-only 1055 DESCRIPTION "A value other than zero MUST be supported if the 1056 implementation supports non-TE signaling of the 1057 outer tunnel. 1058 A read-write access MUST be supported if the 1059 implementation supports PW label manual setting 1060 and carrying them over non-TE tunnels. 1061 " 1063 OBJECT pwMplsOutboundIfIndex 1064 MIN-ACCESS read-only 1065 DESCRIPTION "A value other than zero and read-write operations 1066 MUST be supported if the implementation supports 1067 manually configured PW without MPLS outer tunnel. 1068 " 1069 ::= { pwMplsCompliances 1 } 1071 -- Compliance requirement for Read Only compliant implementations. 1073 pwMplsModuleReadOnlyCompliance MODULE-COMPLIANCE 1074 STATUS current 1075 DESCRIPTION 1076 "The compliance statement for agents that provide read- 1077 only support for the PW-MPLS-STD-MIB Module. Such 1078 devices can then be monitored but cannot be configured 1079 using this MIB module." 1081 MODULE -- this module 1082 MANDATORY-GROUPS { pwMplsGroup, 1083 pwMplsOutboundMainGroup, 1084 pwMplsInboundGroup, 1085 pwMplsMappingGroup 1086 } 1088 GROUP pwMplsOutboundTeGroup 1089 DESCRIPTION "This group MUST be supported if the implementation 1090 allows MPLS TE tunnels to carry PW traffic. 1091 " 1093 OBJECT pwMplsMplsType 1094 MIN-ACCESS read-only 1095 DESCRIPTION "Write access is not required. 1096 Support of pwOnly(2) is not required. At least one 1097 of mplsTe(0) or mplsNonTe(1) MUST be supported if 1098 signaling of PW is supported. 1099 " 1101 OBJECT pwMplsExpBitsMode 1102 MIN-ACCESS read-only 1103 DESCRIPTION "Write access is not required. 1104 Support of specifiedValue(2) and serviceDependant(3) 1105 is optional. 1106 " 1108 OBJECT pwMplsExpBits 1109 MIN-ACCESS read-only 1110 DESCRIPTION "Write access is not required. 1111 " 1112 OBJECT pwMplsTtl 1113 MIN-ACCESS read-only 1114 DESCRIPTION "Write access is not required. 1115 " 1117 OBJECT pwMplsLocalLdpID 1118 MIN-ACCESS read-only 1119 DESCRIPTION "Write access is not required. 1120 " 1122 OBJECT pwMplsLocalLdpEntityIndex 1123 MIN-ACCESS read-only 1124 DESCRIPTION "Write access is not required. 1125 " 1127 OBJECT pwMplsStorageType 1128 MIN-ACCESS read-only 1129 DESCRIPTION "Write access is not required. 1130 " 1132 OBJECT pwMplsOutboundLsrXcIndex 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 non-TE signaling of the 1137 outer tunnel. 1138 " 1140 OBJECT pwMplsOutboundTunnelIndex 1141 MIN-ACCESS read-only 1142 DESCRIPTION "Write access is not required. 1143 " 1145 OBJECT pwMplsOutboundTunnelLclLSR 1146 MIN-ACCESS read-only 1147 DESCRIPTION "Write access is not required. 1148 " 1150 OBJECT pwMplsOutboundTunnelPeerLSR 1151 MIN-ACCESS read-only 1152 DESCRIPTION "Write access is not required. 1153 " 1155 OBJECT pwMplsOutboundIfIndex 1156 MIN-ACCESS read-only 1157 DESCRIPTION "Write access is not required. 1158 A value other than zero MUST be supported if the 1159 implementation supports manually configured PW 1160 without MPLS outer tunnel. 1161 " 1162 ::= { pwMplsCompliances 2 } 1164 -- Units of conformance. 1166 pwMplsGroup OBJECT-GROUP 1167 OBJECTS { 1168 pwMplsMplsType, 1169 pwMplsExpBitsMode, 1170 pwMplsExpBits, 1171 pwMplsTtl, 1172 pwMplsLocalLdpID, 1173 pwMplsLocalLdpEntityIndex, 1174 pwMplsPeerLdpID, 1175 pwMplsStorageType 1176 } 1178 STATUS current 1179 DESCRIPTION 1180 "Collection of objects needed for PW over MPLS PSN 1181 configuration." 1182 ::= { pwMplsGroups 1 } 1184 pwMplsOutboundMainGroup OBJECT-GROUP 1185 OBJECTS { 1186 pwMplsOutboundLsrXcIndex, 1187 pwMplsOutboundIfIndex, 1188 pwMplsOutboundTunnelTypeInUse 1189 } 1191 STATUS current 1192 DESCRIPTION 1193 "Collection of objects needed for outbound association of 1194 PW and MPLS tunnel." 1195 ::= { pwMplsGroups 2 } 1197 pwMplsOutboundTeGroup OBJECT-GROUP 1198 OBJECTS { 1199 pwMplsOutboundTunnelIndex, 1200 pwMplsOutboundTunnelInstance, 1201 pwMplsOutboundTunnelLclLSR, 1202 pwMplsOutboundTunnelPeerLSR 1203 } 1205 STATUS current 1206 DESCRIPTION 1207 "Collection of objects needed for outbound association of 1208 PW and MPLS TE tunnel." 1209 ::= { pwMplsGroups 3 } 1211 pwMplsInboundGroup OBJECT-GROUP 1212 OBJECTS { 1213 pwMplsInboundXcIndex 1214 } 1216 STATUS current 1217 DESCRIPTION 1218 "Collection of objects needed for inbound PW presentation. 1219 This group MUST be supported if PW signaling through LDP is 1220 used." 1221 ::= { pwMplsGroups 4 } 1223 pwMplsMappingGroup OBJECT-GROUP 1224 OBJECTS { 1225 pwMplsNonTeMappingPwIndex, 1226 pwMplsTeMappingPwIndex 1227 } 1229 STATUS current 1230 DESCRIPTION 1231 "Collection of objects needed for mapping association of 1232 PW and MPLS tunnel." 1233 ::= { pwMplsGroups 5 } 1235 END 1237 9. Security Considerations 1239 It is clear that this MIB module is potentially useful for monitoring 1240 PW-capable PEs. This MIB module can also be used for configuration 1241 of certain objects, and anything that can be configured can be 1242 incorrectly configured, with potentially disastrous results. 1244 There are number of management objects defined in this MIB module 1245 with a MAX-ACCESS clause of read-write and/or read-create. Such 1246 objects may be considered sensitive or vulnerable in some network 1247 environments. The support for SET operations in a non-secure 1248 environment without proper protection can have a negative effect on 1249 network operations. These are the tables and objects and their 1250 sensitivity/vulnerability: 1252 o the pwMplsTable, pwMplsNonTeMappingTable and pwMplsTeMappingTable 1253 collectively contain objects to provision PW over MPLS tunnels. 1254 Unauthorized access to objects in these tables, could result in 1255 disruption of traffic on the network. The use of stronger 1256 mechanisms such as SNMPv3 security should be considered where 1257 possible. Specifically, SNMPv3 VACM and USM MUST be used with any 1258 v3 agent which implements this MIB module. Administrators should 1259 consider whether read access to these objects should be allowed, 1260 since read access may be undesirable under certain circumstances. 1262 Some of the readable objects in this MIB module, i.e., objects with a 1263 MAX-ACCESS other than not-accessible, may be considered sensitive or 1264 vulnerable in some network environments. It is thus important to 1265 control even GET and/or NOTIFY access to these objects and possibly 1266 to even encrypt the values of these objects when sending them over 1267 the network via SNMP. These are the tables and objects and their 1268 sensitivity/vulnerability: 1270 o the pwMplsTable, pwMplsNonTeMappingTable, pwMplsTeMappingTable and 1271 pwMplsOutboundTable collectively show the PW over MPLS 1272 association. If an Administrator does not want to reveal this 1273 information, then these tables should be considered sensitive/ 1274 vulnerable. 1276 SNMP versions prior to SNMPv3 did not include adequate security. 1277 Even if the network itself is secure "for example by using IPSec", 1278 even then, there is no control as to who on the secure network is 1279 allowed to access and GET/SET "read/change/create/delete" the objects 1280 in this MIB module. 1282 It is RECOMMENDED that implementers consider the security features as 1283 provided by the SNMPv3 framework "see [RFC3410], section 8", 1284 including full support for the SNMPv3 cryptographic mechanisms "for 1285 authentication and privacy". 1287 Further, deployment of SNMP versions prior to SNMPv3 is NOT 1288 RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to 1289 enable cryptographic security. It is then a customer/operator 1290 responsibility to ensure that the SNMP entity giving access to an 1291 instance of this MIB module, is properly configured to give access to 1292 the objects only to those principals "users" that have legitimate 1293 rights to indeed GET or SET "change/create/delete" them. 1295 10. IANA Considerations 1297 The MIB module in this document uses the following IANA-assigned 1298 OBJECT IDENTIFIER values recorded in the SMI Numbers registry: 1300 Descriptor OBJECT IDENTIFIER value 1301 ---------- ----------------------- 1303 pwMplsStdMIB { transmission XXX } 1305 Editor's Note (to be removed prior to publication): The IANA is 1306 requested to assign a value for "XXX" under the 'transmission' 1307 subtree and to record the assignment in the SMI Numbers registry. 1308 When the assignment has been made, the RFC Editor is asked to replace 1309 "XXX" (here and in the MIB module) with the assigned value and to 1310 remove this note. 1312 11. References 1314 11.1. Normative References 1316 [BCP14] Bradner, S., "Key words for use in RFCs to Indicate 1317 requirement Levels", BCP 14, RFC 2119, March 1997. 1319 [PWMIB] Zelig, D. and T. Nadeau, "Pseudo-Wire (PW) Management 1320 Information Base", work-in-progress . 1322 [PWTC] Nadeau, T. and D. Zelig, "Definitions for Textual 1323 Conventions and OBJECT-IDENTITIES for Pseudo-Wires 1324 Management", work-in-progress . 1326 [RFC2578] McCloghrie, K., Ed., Perkins, D., Ed., and J. 1327 Schoenwaelder, Ed., "Structure of Management Information 1328 Version 2 (SMIv2)", STD 58, RFC 2578, April 1999. 1330 [RFC2579] McCloghrie, K., Ed., Perkins, D., Ed., and J. 1331 Schoenwaelder, Ed., "Textual Conventions for SMIv2", 1332 STD 58, RFC 2579, April 1999. 1334 [RFC2580] McCloghrie, K., Perkins, D., and J. Schoenwaelder, 1335 "Conformance Statements for SMIv2", STD 58, RFC 2580, 1336 April 1999. 1338 [RFC2863] McCloghrie, K. and F. Kastenholz, "The Interfaces Group 1339 MIB", RFC 2863, June 2000. 1341 [RFC3031] Rosen, E., Viswanathan, A., and R. Callon, "Multiprotocol 1342 Label Switching Architecture", RFC 3031, January 2001. 1344 [RFC3811] Nadeau, T. and J. Cucchiara, "Definitions of Textual 1345 Conventions (TCs) for Multiprotocol Label Switching (MPLS) 1346 Management", RFC 3811, June 2004. 1348 [RFC3812] Srinivasan, C., Viswanathan, A., and T. Nadeau, 1349 "Multiprotocol Label Switching (MPLS) Traffic Engineering 1350 (TE) Management Information Base (MIB)", RFC 3812, 1351 June 2004. 1353 [RFC3813] Srinivasan, C., Viswanathan, A., and T. Nadeau, 1354 "Multiprotocol Label Switching (MPLS) Label Switching 1355 Router (LSR) Management Information Base (MIB)", RFC 3813, 1356 June 2004. 1358 [RFC4447] Martini, L., Rosen, E., El-Aawar, N., Smith, T., and G. 1359 Heron, "Pseudowire Setup and Maintenance Using the Label 1360 Distribution Protocol (LDP)", RFC 4447, April 2006. 1362 11.2. Informative References 1364 [RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart, 1365 "Introduction and Applicability Statements for Internet- 1366 Standard Management Framework", RFC 3410, December 2002. 1368 [RFC3815] Cucchiara, J., Sjostrand, H., and J. Luciani, "Definitions 1369 of Managed Objects for the Multiprotocol Label Switching 1370 (MPLS), Label Distribution Protocol (LDP)", RFC 3815, 1371 June 2004. 1373 [RFC3916] Xiao, X., McPherson, D., and P. Pate, "Requirements for 1374 Pseudo-Wire Emulation Edge-to-Edge (PWE3)", RFC 3916, 1375 September 2004. 1377 [RFC3985] Bryant, S. and P. Pate, "Pseudo Wire Emulation Edge-to- 1378 Edge (PWE3) Architecture", RFC 3985, March 2005. 1380 Authors' Addresses 1382 David Zelig (editor) 1383 Corrigent Systems 1384 126, Yigal Alon St. 1385 Tel Aviv, 1386 Israel 1388 Phone: +972 3 6945 273 1389 Email: davidz@corrigent.com 1391 Thomas D. Nadeau (editor) 1392 Cisco Systems, Inc. 1393 250 Apollo Drive 1394 Chelmsford, MA 01824 1395 USA 1397 Email: tnadeau@cisco.com 1399 Full Copyright Statement 1401 Copyright (C) The IETF Trust (2007). 1403 This document is subject to the rights, licenses and restrictions 1404 contained in BCP 78, and except as set forth therein, the authors 1405 retain all their rights. 1407 This document and the information contained herein are provided on an 1408 "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS 1409 OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND 1410 THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS 1411 OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF 1412 THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED 1413 WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 1415 Intellectual Property 1417 The IETF takes no position regarding the validity or scope of any 1418 Intellectual Property Rights or other rights that might be claimed to 1419 pertain to the implementation or use of the technology described in 1420 this document or the extent to which any license under such rights 1421 might or might not be available; nor does it represent that it has 1422 made any independent effort to identify any such rights. Information 1423 on the procedures with respect to rights in RFC documents can be 1424 found in BCP 78 and BCP 79. 1426 Copies of IPR disclosures made to the IETF Secretariat and any 1427 assurances of licenses to be made available, or the result of an 1428 attempt made to obtain a general license or permission for the use of 1429 such proprietary rights by implementers or users of this 1430 specification can be obtained from the IETF on-line IPR repository at 1431 http://www.ietf.org/ipr. 1433 The IETF invites any interested party to bring to its attention any 1434 copyrights, patents or patent applications, or other proprietary 1435 rights that may cover technology that may be required to implement 1436 this standard. Please address the information to the IETF at 1437 ietf-ipr@ietf.org. 1439 Acknowledgment 1441 Funding for the RFC Editor function is provided by the IETF 1442 Administrative Support Activity (IASA).