idnits 2.17.1 draft-ietf-pwe3-pw-mpls-mib-13.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 1418. -- Found old boilerplate from RFC 3979, Section 5, paragraph 1 on line 1429. -- Found old boilerplate from RFC 3979, Section 5, paragraph 2 on line 1436. -- Found old boilerplate from RFC 3979, Section 5, paragraph 3 on line 1442. 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 (November 18, 2007) is 5975 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 Pseudowire Edge-to-Edge Emulation D. Zelig, Ed. 3 Internet-Draft Corrigent Systems 4 Intended status: Standards Track T. Nadeau, Ed. 5 Expires: May 21, 2008 BT 6 November 18, 2007 8 Pseudowire (PW) over MPLS PSN Management Information Base (MIB) 9 draft-ietf-pwe3-pw-mpls-mib-13 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 May 21, 2008. 36 Copyright Notice 38 Copyright (C) The IETF Trust (2007). 40 Abstract 42 This memo defines a portion of the Management Information Base (MIB) 43 for use with network management protocols in the Internet community. 44 In particular, it describes a MIB module for PW operation over Multi- 45 Protocol Label Switching (MPLS) Label Switch Router (LSR). 47 Table of Contents 49 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 50 2. The Internet-Standard Management Framework . . . . . . . . . . 3 51 3. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3 52 4. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 53 5. Features Checklist . . . . . . . . . . . . . . . . . . . . . . 5 54 6. MIB Module Usage . . . . . . . . . . . . . . . . . . . . . . . 5 55 7. PW-MPLS-STD-MIB Example . . . . . . . . . . . . . . . . . . . 7 56 8. Object Definitions . . . . . . . . . . . . . . . . . . . . . . 8 57 9. Security Considerations . . . . . . . . . . . . . . . . . . . 27 58 10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 29 59 11. References . . . . . . . . . . . . . . . . . . . . . . . . . . 29 60 11.1. Normative References . . . . . . . . . . . . . . . . . . 29 61 11.2. Informative References . . . . . . . . . . . . . . . . . 30 62 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 30 63 Intellectual Property and Copyright Statements . . . . . . . . . . 32 65 1. Introduction 67 This document describes a model for managing pseudowire services for 68 transmission over different flavors of MPLS tunnels. The general PW 69 MIB module [PWMIB] defines the parameters global to the PW regardless 70 of underlying PSN and emulated service. Indicating the MPLS PSN type 71 in PW-STD-MIB references this module. 73 This document describes the MIB objects that define pseudowire 74 association to the MPLS PSN, in a way that is not specific to the 75 carried service. 77 Together, [RFC3811] and [RFC3812], describe the modeling of an MPLS 78 Tunnel, and a Tunnel's underlying cross-connects. This MIB module 79 supports MPLS-TE PSN, Non-TE MPLS PSN (an outer tunnel created by LDP 80 or manually), and MPLS PW label only (no outer tunnel). 82 Comments should be made directly to the PWE3 mailing list at 83 pwe3@ietf.org. 85 2. The Internet-Standard Management Framework 87 For a detailed overview of the documents that describe the current 88 Internet-Standard Management Framework, please refer to section 7 of 89 RFC 3410 [RFC3410]. 91 Managed objects are accessed via a virtual information store, termed 92 the Management Information Base or MIB. MIB objects are generally 93 accessed through the Simple Network Management Protocol (SNMP). 94 Objects in the MIB are defined using the mechanisms defined in the 95 Structure of Management Information (SMI). This memo specifies a MIB 96 module that is compliant to the SMIv2, which is described in STD 58, 97 RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580 98 [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 one 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 pseudowires 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 consists of three 136 layers of MIB modules functioning together. This general model is 137 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 structure 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 for manually configured PWs) 199 through the pwMplsTeOutbaoundTable. For LDP based outer tunnel, 200 there is no need for manual configuration since there is only a 201 single 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-STD-MIB module reports through the inbound table the XC 264 entry in the LDP-STD-MIB [RFC3815] of the PW that were signaled 265 through 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 important to note that inbound (tunnel originated in the remote 276 PE) mapping is not configured nor reported through the PW-MPLS-STD- 277 MIB module since the local PE does not know the inbound association 278 between specific PW and MPLS tunnels. 280 7. PW-MPLS-STD-MIB Example 282 The following example (supplement the example provided in [PWMIB]) 283 assumes that the node has already established LDP tunnel to the peer 284 node and that a PW has been configured in the pwTbale in [PWMIB] with 285 pwPsnType equal 'mpls'. 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 329 MPLS-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 "200711121200Z" -- 12 November 2007 12:00:00 GMT 369 ORGANIZATION "Pseudowire 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: thomas.nadeau@bt.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 "200711121200Z" -- 12 November 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 pseudowire (PW). The row is created 434 automatically by the local agent if the pwPsnType is 435 mpls(1). It is indexed by pwIndex, which uniquely 436 identifying a singular PW. 437 Manual entries in this table SHOULD be preserved after a 438 reboot, 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) SHOULD be used 504 to indicate that the value is specified by pwMplsExpBits. 505 Setting serviceDependant(3) indicates that the EXP bits are 506 set 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 if pwMplsExpBitsMode is 517 set to specifiedValue(2) to indicate the MPLS EXP bits to 518 be used on the PW shim label. Otherwise, it SHOULD be set 519 to zero." 520 DEFVAL { 0 } 521 ::= { pwMplsEntry 3 } 523 pwMplsTtl OBJECT-TYPE 524 SYNTAX Unsigned32 (0..255) 525 MAX-ACCESS read-write 526 STATUS current 527 DESCRIPTION 528 "This object is set by the operator to indicate the PW TTL 529 value to be used on the PW shim label." 530 DEFVAL { 2 } 531 ::= { pwMplsEntry 4 } 533 pwMplsLocalLdpID OBJECT-TYPE 534 SYNTAX MplsLdpIdentifier 535 MAX-ACCESS read-write 536 STATUS current 537 DESCRIPTION 538 "The LDP identifier of the LDP entity that creates 539 this PW in the local node. As the PW labels are always 540 set from the per-platform label space, the last two octets 541 in the LDP ID MUST always both be zeros." 542 REFERENCE 543 "'LDP specifications', RFC 3036 section 2.2.2." 544 ::= { pwMplsEntry 5 } 546 pwMplsLocalLdpEntityIndex OBJECT-TYPE 547 SYNTAX Unsigned32 (1..4294967295) 548 MAX-ACCESS read-write 549 STATUS current 550 DESCRIPTION 551 "The local node LDP Entity Index of the LDP entity creating 552 this PW." 553 ::= { pwMplsEntry 6 } 555 pwMplsPeerLdpID OBJECT-TYPE 556 SYNTAX MplsLdpIdentifier 557 MAX-ACCESS read-only 558 STATUS current 559 DESCRIPTION 560 "The peer LDP identifier of the LDP session. This object 561 SHOULD return the value zero if LDP is not used or if the 562 value is not yet known." 563 ::= { pwMplsEntry 7 } 565 pwMplsStorageType OBJECT-TYPE 566 SYNTAX StorageType 567 MAX-ACCESS read-write 568 STATUS current 569 DESCRIPTION 570 "This variable indicates the storage type for this row." 571 DEFVAL { nonVolatile } 572 ::= { pwMplsEntry 8 } 574 -- End of PW MPLS Table 576 -- Pseudowire MPLS Outbound Tunnel Table 578 pwMplsOutboundTable OBJECT-TYPE 579 SYNTAX SEQUENCE OF PwMplsOutboundEntry 580 MAX-ACCESS not-accessible 581 STATUS current 582 DESCRIPTION 583 "This table reports and configures the current outbound MPLS 584 tunnels (i.e. toward the PSN) or the physical interface in 585 the case of a PW label only that carries the PW traffic. It 586 also reports the current outer tunnel and LSP which forward 587 the PW traffic." 588 ::= { pwMplsObjects 2 } 590 pwMplsOutboundEntry OBJECT-TYPE 591 SYNTAX PwMplsOutboundEntry 592 MAX-ACCESS not-accessible 593 STATUS current 594 DESCRIPTION 595 "A row in this table configures the outer tunnel used for 596 carrying the PW traffic toward the PSN. 597 In the case of PW labels only, it configures the interface 598 that will carry the PW traffic. 600 An entry in this table augments the pwMplsEntry, and is 601 created automatically when the corresponding row has been 602 created by the agent in the pwMplsEntry. 604 This table points to the appropriate MPLS MIB module: 606 In the MPLS-TE case, the three objects relevant to the 607 indexing of a TE tunnel head-end (as used in the 608 MPLS-TE-STD-MIB) are to be configured, and the tunnel 609 instance indicates the LSP that is currently in use for 610 forwarding the traffic. 612 In case of signaled Non-TE MPLS (an outer tunnel label 613 assigned by LDP) the table points to the XC entry in the 614 LSR-STD-MIB. If the Non-TE MPLS tunnel is manually 615 configured, the operator configures the XC pointer to this 616 tunnel. 618 In case of PW label only (no outer tunnel) the ifIndex of 619 the port to carry the PW is configured here. 621 It is possible to associate a PW to one TE tunnel head-end 622 and a non-TE tunnel together. An indication in this table 623 will report the currently active one. In addition, in the 624 TE case the table reports the active tunnel instance 625 (i.e. the specific LSP in use). 626 Any read-write object in this table MAY be changed at any 627 time, however change of some objects (for example 628 MPLS-TE indexes) during PW forwarding state MAY cause traffic 629 disruption." 631 AUGMENTS { pwMplsEntry } 633 ::= { pwMplsOutboundTable 1 } 635 PwMplsOutboundEntry ::= SEQUENCE { 636 pwMplsOutboundLsrXcIndex MplsIndexType, 637 pwMplsOutboundTunnelIndex MplsTunnelIndex, 638 pwMplsOutboundTunnelInstance MplsTunnelInstanceIndex, 639 pwMplsOutboundTunnelLclLSR MplsLsrIdentifier, 640 pwMplsOutboundTunnelPeerLSR MplsLsrIdentifier, 641 pwMplsOutboundIfIndex InterfaceIndexOrZero, 642 pwMplsOutboundTunnelTypeInUse INTEGER 643 } 645 pwMplsOutboundLsrXcIndex OBJECT-TYPE 646 SYNTAX MplsIndexType 647 MAX-ACCESS read-write 648 STATUS current 649 DESCRIPTION 650 "This object is applicable if pwMplsMplsType mplsNonTe(1) 651 bit is set, and MUST return a value zero otherwise. 652 If the outer tunnel is signaled, the object is read-only 653 and indicates the XC index in the MPLS-LSR-STD-MIB of the 654 outer tunnel toward the peer. Otherwise (tunnel is set up 655 manually) the operator defines the XC index of the manually- 656 created outer tunnel through this object. 657 " 658 ::= { pwMplsOutboundEntry 1 } 660 pwMplsOutboundTunnelIndex OBJECT-TYPE 661 SYNTAX MplsTunnelIndex 662 MAX-ACCESS read-write 663 STATUS current 664 DESCRIPTION 665 "This object is applicable if pwMplsMplsType mplsTe(0) 666 bit is set, and MUST return a value zero otherwise. 667 It is part of the set of indexes for the outbound tunnel. 668 The operator sets this object to represent the desired 669 tunnel head-end toward the peer for carrying the PW 670 traffic. 671 " 672 ::= { pwMplsOutboundEntry 2 } 674 pwMplsOutboundTunnelInstance OBJECT-TYPE 675 SYNTAX MplsTunnelInstanceIndex 676 MAX-ACCESS read-only 677 STATUS current 678 DESCRIPTION 679 "This object is applicable if pwMplsMplsType mplsTe(0) 680 bit is set, and MUST return a value zero otherwise. 681 It indicates the actual tunnel instance that is currently 682 active and carrying the PW traffic. It SHOULD return the 683 value zero if the information from the MPLS-TE 684 application is not yet known. 685 " 686 ::= { pwMplsOutboundEntry 3 } 688 pwMplsOutboundTunnelLclLSR OBJECT-TYPE 689 SYNTAX MplsLsrIdentifier 690 MAX-ACCESS read-write 691 STATUS current 692 DESCRIPTION 693 "This object is applicable if pwMplsMplsType mplsTe(0) 694 bit is set, and MUST return a value of all zeros otherwise. 695 It is part of the set of indexes for the outbound tunnel. 696 The operator sets this object to represent the desired 697 tunnel head-end toward the peer for carrying the PW 698 traffic. 699 " 700 ::= { pwMplsOutboundEntry 4 } 702 pwMplsOutboundTunnelPeerLSR OBJECT-TYPE 703 SYNTAX MplsLsrIdentifier 704 MAX-ACCESS read-write 705 STATUS current 706 DESCRIPTION 707 "This object is applicable if pwMplsMplsType mplsTe(0) 708 bit is set, and MUST return a value zero otherwise. 709 It is part of the set of indexes for the outbound tunnel. 710 Note that in most cases it equals to pwPeerAddr. 711 " 712 ::= { pwMplsOutboundEntry 5 } 714 pwMplsOutboundIfIndex OBJECT-TYPE 715 SYNTAX InterfaceIndexOrZero 716 MAX-ACCESS read-write 717 STATUS current 718 DESCRIPTION 719 "This object is applicable if pwMplsMplsType pwOnly(0) 720 bit is set, and MUST return a value zero otherwise. 721 The operator configures the ifIndex of the outbound port 722 in this case. 723 " 724 ::= { pwMplsOutboundEntry 6 } 726 pwMplsOutboundTunnelTypeInUse OBJECT-TYPE 727 SYNTAX INTEGER { 728 notYetKnown (1), 729 mplsTe (2), 730 mplsNonTe (3), 731 pwOnly (4) 732 } 733 MAX-ACCESS read-only 734 STATUS current 735 DESCRIPTION 736 "This object indicates the current tunnel that is carrying 737 the PW traffic. 738 The value of notYetKnown(1) should be used if the agent is 739 currently unable to determine which tunnel or interface is 740 carrying the PW, for example because both tunnels are in 741 operational status down. 742 " 743 ::= { pwMplsOutboundEntry 7 } 745 -- End of PW MPLS Outbound Tunnel table 747 -- PW MPLS inbound table 749 pwMplsInboundTable OBJECT-TYPE 750 SYNTAX SEQUENCE OF PwMplsInboundEntry 751 MAX-ACCESS not-accessible 752 STATUS current 753 DESCRIPTION 754 "This table indicates the PW LDP XC entry in the 755 MPLS-LSR-STD-MIB for signaled PWs. 756 " 757 ::= { pwMplsObjects 3 } 759 pwMplsInboundEntry OBJECT-TYPE 760 SYNTAX PwMplsInboundEntry 761 MAX-ACCESS not-accessible 762 STATUS current 763 DESCRIPTION 764 "A row in this table is created by the agent 765 for each signaled PW, and shows the XC index related to 766 the PW signaling in the inbound direction in the 767 MPLS-LSR-STD-MIB that controls and display the information 768 for all the LDP signaling processes in the local node. 769 " 770 INDEX { pwIndex } 772 ::= { pwMplsInboundTable 1 } 774 PwMplsInboundEntry ::= SEQUENCE { 775 pwMplsInboundXcIndex MplsIndexType 776 } 778 pwMplsInboundXcIndex OBJECT-TYPE 779 SYNTAX MplsIndexType 780 MAX-ACCESS read-only 781 STATUS current 782 DESCRIPTION 783 "The XC index representing this PW in the inbound 784 direction. It MUST return the value zero if the 785 information is not yet known." 786 ::= { pwMplsInboundEntry 1 } 788 -- End of PW MPLS inbound table 790 -- PW to Non-TE mapping Table. 792 pwMplsNonTeMappingTable OBJECT-TYPE 793 SYNTAX SEQUENCE OF PwMplsNonTeMappingEntry 794 MAX-ACCESS not-accessible 795 STATUS current 796 DESCRIPTION 797 "This table indicates the PW association to the outbound 798 Tunnel in non-TE applications, maps the PW to it's (inbound) 799 XC entry, and indicates the PW-to-physical interface mapping 800 for a PW without an outer tunnel. 801 " 802 ::= { pwMplsObjects 4 } 804 pwMplsNonTeMappingEntry OBJECT-TYPE 805 SYNTAX PwMplsNonTeMappingEntry 806 MAX-ACCESS not-accessible 807 STATUS current 808 DESCRIPTION 809 "A row in this table displays the association 810 between the PW and 811 - its non-TE MPLS outbound outer Tunnel or, 812 - its XC entry in the MPLS-LSR-STD-MIB, 813 - its physical interface if there is no outer tunnel 814 (PW label only) and manual configuration. 816 Rows are created in this table by the agent depending on 817 the setting of pwMplsMplsType: 819 - If pwMplsMplsType mplsNonTe(1) bit is set, the agent 820 creates a row for the outbound direction 821 (pwMplsNonTeMappingDirection set to psnBound(1)). 823 The pwMplsNonTeMappingXcIndex holds the XC index in the 824 MPLS-LSR-STD-MIB of the PSN bound outer tunnel. 825 pwMplsNonTeMappingIfIndex MUST be zero for this row. 827 - If pwMplsMplsType pwOnly(2) bit is set, the agent 828 creates a row for the outbound direction 829 (pwMplsNonTeMappingDirection set to psnBound(1)). 830 The pwMplsNonTeMappingIfIndex holds the ifIndex of the 831 physical port this PW will use in the outbound direction. 832 pwMplsNonTeMappingXcIndex MUST be zero for this row. 834 - If the PW has been set up by a signaling protocol (i.e. 835 pwOwner equal pwIdFecSignaling(2) or 836 genFecSignaling(3)), the agent creates a row for the 837 inbound direction (pwMplsNonTeMappingDirection set to 838 fromPsn(2)). 839 The pwMplsNonTeMappingXcIndex holds the XC index in the 840 MPLS-LSR-STD-MIB of the PW LDP generated XC entry. 841 pwMplsNonTeMappingIfIndex MUST be zero for this row. 843 An application can use this table to quickly retrieve the 844 PW carried over specific non-TE MPLS outer tunnel or 845 physical interface. 846 " 848 INDEX { pwMplsNonTeMappingDirection, 849 pwMplsNonTeMappingXcIndex, 850 pwMplsNonTeMappingIfIndex, 851 pwMplsNonTeMappingPwIndex } 853 ::= { pwMplsNonTeMappingTable 1 } 855 PwMplsNonTeMappingEntry ::= SEQUENCE { 856 pwMplsNonTeMappingDirection INTEGER, 857 pwMplsNonTeMappingXcIndex MplsIndexType, 858 pwMplsNonTeMappingIfIndex InterfaceIndexOrZero, 859 pwMplsNonTeMappingPwIndex PwIndexType 860 } 862 pwMplsNonTeMappingDirection OBJECT-TYPE 863 SYNTAX INTEGER { 864 psnBound (1), 865 fromPsn (2) 866 } 867 MAX-ACCESS not-accessible 868 STATUS current 869 DESCRIPTION 870 "Index for the conceptual XC row identifying the tunnel-to-PW 871 mappings, indicating the direction of the packet flow for 872 this entry. 873 psnBound(1) indicates that the entry is related to 874 packets toward the PSN. 875 fromPsn(2) indicates that the entry is related to 876 packets coming from the PSN. 877 " 878 ::= { pwMplsNonTeMappingEntry 1 } 880 pwMplsNonTeMappingXcIndex OBJECT-TYPE 881 SYNTAX MplsIndexType 882 MAX-ACCESS not-accessible 883 STATUS current 884 DESCRIPTION 885 "See the description clause of pwMplsNonTeMappingEntry for 886 the usage guidelines of this object." 887 ::= { pwMplsNonTeMappingEntry 2 } 889 pwMplsNonTeMappingIfIndex OBJECT-TYPE 890 SYNTAX InterfaceIndexOrZero 891 MAX-ACCESS not-accessible 892 STATUS current 893 DESCRIPTION 894 "See the description clause of pwMplsNonTeMappingEntry for 895 the usage guidelines of this object." 896 ::= { pwMplsNonTeMappingEntry 3 } 898 pwMplsNonTeMappingPwIndex OBJECT-TYPE 899 SYNTAX PwIndexType 900 MAX-ACCESS read-only 901 STATUS current 902 DESCRIPTION 903 "The value that represent the PW in the pwTable." 904 ::= { pwMplsNonTeMappingEntry 4 } 906 -- End of PW to Non-TE mapping Table. 908 -- PW to TE MPLS tunnels mapping Table. 910 pwMplsTeMappingTable OBJECT-TYPE 911 SYNTAX SEQUENCE OF PwMplsTeMappingEntry 912 MAX-ACCESS not-accessible 913 STATUS current 914 DESCRIPTION 915 "This table reports the PW association to the 916 outbound MPLS tunnel for MPLS-TE applications." 917 ::= { pwMplsObjects 5 } 919 pwMplsTeMappingEntry OBJECT-TYPE 920 SYNTAX PwMplsTeMappingEntry 921 MAX-ACCESS not-accessible 922 STATUS current 923 DESCRIPTION 924 "A row in this table represents the association 925 between a PW and its MPLS-TE outer (head-end) Tunnel. 927 An application can use this table to quickly retrieve the 928 list of the PWs that are configured on a specific MPLS-TE 929 outer tunnel. 931 The pwMplsTeMappingTunnelInstance reports the actual 932 LSP out of the tunnel head-end that is currently 933 forwarding the traffic. 935 The table in indexed by the head-end indexes of a TE 936 tunnel and the PW index. 937 " 939 INDEX { pwMplsTeMappingTunnelIndex, 940 pwMplsTeMappingTunnelInstance, 941 pwMplsTeMappingTunnelPeerLsrID, 942 pwMplsTeMappingTunnelLocalLsrID, 943 pwMplsTeMappingPwIndex } 945 ::= { pwMplsTeMappingTable 1 } 947 PwMplsTeMappingEntry ::= SEQUENCE { 948 pwMplsTeMappingTunnelIndex MplsTunnelIndex, 949 pwMplsTeMappingTunnelInstance MplsTunnelInstanceIndex, 950 pwMplsTeMappingTunnelPeerLsrID MplsLsrIdentifier, 951 pwMplsTeMappingTunnelLocalLsrID MplsLsrIdentifier, 952 pwMplsTeMappingPwIndex PwIndexType 953 } 955 pwMplsTeMappingTunnelIndex OBJECT-TYPE 956 SYNTAX MplsTunnelIndex 957 MAX-ACCESS not-accessible 958 STATUS current 959 DESCRIPTION 960 "Primary index for the conceptual row identifying the 961 MPLS-TE tunnel that is carrying the PW traffic." 962 ::= { pwMplsTeMappingEntry 1 } 964 pwMplsTeMappingTunnelInstance OBJECT-TYPE 965 SYNTAX MplsTunnelInstanceIndex 966 MAX-ACCESS not-accessible 967 STATUS current 968 DESCRIPTION 969 "This object identifies the MPLS-TE LSP that is carrying the 970 PW traffic. It MUST return the value zero if the 971 information of the specific LSP is not yet known. 972 Note that based on the recommendation in the 973 MPLS-TC-STD-MIB, instance index 0 should refer to the 974 configured tunnel interface." 975 ::= { pwMplsTeMappingEntry 2 } 977 pwMplsTeMappingTunnelPeerLsrID OBJECT-TYPE 978 SYNTAX MplsLsrIdentifier 979 MAX-ACCESS not-accessible 980 STATUS current 981 DESCRIPTION 982 "This object identifies the Peer LSR when the outer tunnel 983 is MPLS-TE." 984 ::= { pwMplsTeMappingEntry 3 } 986 pwMplsTeMappingTunnelLocalLsrID OBJECT-TYPE 987 SYNTAX MplsLsrIdentifier 988 MAX-ACCESS not-accessible 989 STATUS current 990 DESCRIPTION 991 "This object identifies the local LSR." 992 ::= { pwMplsTeMappingEntry 4 } 994 pwMplsTeMappingPwIndex OBJECT-TYPE 995 SYNTAX PwIndexType 996 MAX-ACCESS read-only 997 STATUS current 998 DESCRIPTION 999 "This object returns the value that represents the PW in the 1000 pwTable." 1001 ::= { pwMplsTeMappingEntry 5 } 1003 -- End of PW to TE MPLS tunnels mapping Table. 1005 -- conformance information 1007 pwMplsGroups OBJECT IDENTIFIER ::= { pwMplsConformance 1 } 1008 pwMplsCompliances OBJECT IDENTIFIER ::= { pwMplsConformance 2 } 1010 -- Compliance requirement for fully compliant implementations. 1012 pwMplsModuleFullCompliance MODULE-COMPLIANCE 1013 STATUS current 1014 DESCRIPTION 1015 "The compliance statement for agents that provide full 1016 support for PW-MPLS-STD-MIB Module. Such devices can 1017 then be monitored and also be configured using 1018 this MIB module." 1020 MODULE -- this module 1021 MANDATORY-GROUPS { pwMplsGroup, 1022 pwMplsOutboundMainGroup, 1023 pwMplsInboundGroup, 1024 pwMplsMappingGroup 1025 } 1027 GROUP pwMplsOutboundTeGroup 1028 DESCRIPTION "This group MUST be supported if the implementation 1029 allows MPLS-TE tunnels to carry PW traffic. 1030 " 1032 OBJECT pwMplsMplsType 1033 DESCRIPTION "Support of pwOnly(2) is not required. At least one 1034 of mplsTe(0) or mplsNonTe(1) MUST be supported if 1035 signaling of PW is supported. 1036 " 1038 OBJECT pwMplsExpBitsMode 1039 DESCRIPTION "Support of specifiedValue(2) and 1040 serviceDependant(3) is optional. 1041 " 1043 OBJECT pwMplsLocalLdpID 1044 MIN-ACCESS read-only 1045 DESCRIPTION "A read-write access is required if the 1046 implementation supports more than one LDP entity 1047 identifier for PW signaling. 1048 " 1050 OBJECT pwMplsLocalLdpEntityIndex 1051 MIN-ACCESS read-only 1052 DESCRIPTION "A read-write access is required if the 1053 implementation supports more than one LDP entity 1054 index for PW signaling. 1055 " 1057 OBJECT pwMplsOutboundLsrXcIndex 1058 MIN-ACCESS read-only 1059 DESCRIPTION "A value other than zero MUST be supported if the 1060 implementation supports non-TE signaling of the 1061 outer tunnel. 1062 A read-write access MUST be supported if the 1063 implementation supports PW label manual setting 1064 and carrying them over non-TE tunnels. 1065 " 1067 OBJECT pwMplsOutboundIfIndex 1068 MIN-ACCESS read-only 1069 DESCRIPTION "A value other than zero and read-write operations 1070 MUST be supported if the implementation supports 1071 manually configured PW without MPLS outer tunnel. 1072 " 1073 ::= { pwMplsCompliances 1 } 1075 -- Compliance requirement for Read Only compliant implementations. 1077 pwMplsModuleReadOnlyCompliance MODULE-COMPLIANCE 1078 STATUS current 1079 DESCRIPTION 1080 "The compliance statement for agents that provide read- 1081 only support for the PW-MPLS-STD-MIB Module. Such 1082 devices can then be monitored but cannot be configured 1083 using this MIB module." 1085 MODULE -- this module 1086 MANDATORY-GROUPS { pwMplsGroup, 1087 pwMplsOutboundMainGroup, 1088 pwMplsInboundGroup, 1089 pwMplsMappingGroup 1090 } 1092 GROUP pwMplsOutboundTeGroup 1093 DESCRIPTION "This group MUST be supported if the implementation 1094 allows MPLS-TE tunnels to carry PW traffic. 1095 " 1097 OBJECT pwMplsMplsType 1098 MIN-ACCESS read-only 1099 DESCRIPTION "Write access is not required. 1100 Support of pwOnly(2) is not required. At least one 1101 of mplsTe(0) or mplsNonTe(1) MUST be supported if 1102 signaling of PW is supported. 1103 " 1105 OBJECT pwMplsExpBitsMode 1106 MIN-ACCESS read-only 1107 DESCRIPTION "Write access is not required. 1108 Support of specifiedValue(2) and serviceDependant(3) 1109 is optional. 1110 " 1112 OBJECT pwMplsExpBits 1113 MIN-ACCESS read-only 1114 DESCRIPTION "Write access is not required. 1115 " 1116 OBJECT pwMplsTtl 1117 MIN-ACCESS read-only 1118 DESCRIPTION "Write access is not required. 1119 " 1121 OBJECT pwMplsLocalLdpID 1122 MIN-ACCESS read-only 1123 DESCRIPTION "Write access is not required. 1124 " 1126 OBJECT pwMplsLocalLdpEntityIndex 1127 MIN-ACCESS read-only 1128 DESCRIPTION "Write access is not required. 1129 " 1131 OBJECT pwMplsStorageType 1132 MIN-ACCESS read-only 1133 DESCRIPTION "Write access is not required. 1134 " 1136 OBJECT pwMplsOutboundLsrXcIndex 1137 MIN-ACCESS read-only 1138 DESCRIPTION "Write access is not required. 1139 A value other than zero MUST be supported if the 1140 implementation supports non-TE signaling of the 1141 outer tunnel. 1142 " 1144 OBJECT pwMplsOutboundTunnelIndex 1145 MIN-ACCESS read-only 1146 DESCRIPTION "Write access is not required. 1147 " 1149 OBJECT pwMplsOutboundTunnelLclLSR 1150 MIN-ACCESS read-only 1151 DESCRIPTION "Write access is not required. 1152 " 1154 OBJECT pwMplsOutboundTunnelPeerLSR 1155 MIN-ACCESS read-only 1156 DESCRIPTION "Write access is not required. 1157 " 1159 OBJECT pwMplsOutboundIfIndex 1160 MIN-ACCESS read-only 1161 DESCRIPTION "Write access is not required. 1162 A value other than zero MUST be supported if the 1163 implementation supports manually configured PW 1164 without MPLS outer tunnel. 1165 " 1166 ::= { pwMplsCompliances 2 } 1168 -- Units of conformance. 1170 pwMplsGroup OBJECT-GROUP 1171 OBJECTS { 1172 pwMplsMplsType, 1173 pwMplsExpBitsMode, 1174 pwMplsExpBits, 1175 pwMplsTtl, 1176 pwMplsLocalLdpID, 1177 pwMplsLocalLdpEntityIndex, 1178 pwMplsPeerLdpID, 1179 pwMplsStorageType 1180 } 1182 STATUS current 1183 DESCRIPTION 1184 "Collection of objects needed for PW over MPLS PSN 1185 configuration." 1186 ::= { pwMplsGroups 1 } 1188 pwMplsOutboundMainGroup OBJECT-GROUP 1189 OBJECTS { 1190 pwMplsOutboundLsrXcIndex, 1191 pwMplsOutboundIfIndex, 1192 pwMplsOutboundTunnelTypeInUse 1193 } 1195 STATUS current 1196 DESCRIPTION 1197 "Collection of objects needed for outbound association of 1198 PW and MPLS tunnel." 1199 ::= { pwMplsGroups 2 } 1201 pwMplsOutboundTeGroup OBJECT-GROUP 1202 OBJECTS { 1203 pwMplsOutboundTunnelIndex, 1204 pwMplsOutboundTunnelInstance, 1205 pwMplsOutboundTunnelLclLSR, 1206 pwMplsOutboundTunnelPeerLSR 1207 } 1209 STATUS current 1210 DESCRIPTION 1211 "Collection of objects needed for outbound association of 1212 PW and MPLS-TE tunnel." 1213 ::= { pwMplsGroups 3 } 1215 pwMplsInboundGroup OBJECT-GROUP 1216 OBJECTS { 1217 pwMplsInboundXcIndex 1218 } 1220 STATUS current 1221 DESCRIPTION 1222 "Collection of objects needed for inbound PW presentation. 1223 This group MUST be supported if PW signaling through LDP is 1224 used." 1225 ::= { pwMplsGroups 4 } 1227 pwMplsMappingGroup OBJECT-GROUP 1228 OBJECTS { 1229 pwMplsNonTeMappingPwIndex, 1230 pwMplsTeMappingPwIndex 1231 } 1233 STATUS current 1234 DESCRIPTION 1235 "Collection of objects needed for mapping association of 1236 PW and MPLS tunnel." 1237 ::= { pwMplsGroups 5 } 1239 END 1241 9. Security Considerations 1243 It is clear that this MIB module is potentially useful for monitoring 1244 PW-capable PEs. This MIB module can also be used for configuration 1245 of certain objects, and anything that can be configured can be 1246 incorrectly configured, with potentially disastrous results. 1248 There are number of management objects defined in this MIB module 1249 with a MAX-ACCESS clause of read-write and/or read-create. Such 1250 objects may be considered sensitive or vulnerable in some network 1251 environments. The support for SET operations in a non-secure 1252 environment without proper protection can have a negative effect on 1253 network operations. These are the tables and objects and their 1254 sensitivity/vulnerability: 1256 o the pwMplsTable, pwMplsNonTeMappingTable and pwMplsTeMappingTable 1257 collectively contain objects to provision PW over MPLS tunnels. 1258 Unauthorized access to objects in these tables, could result in 1259 disruption of traffic on the network. The use of stronger 1260 mechanisms such as SNMPv3 security should be considered where 1261 possible. Specifically, SNMPv3 VACM and USM MUST be used with any 1262 v3 agent which implements this MIB module. Administrators should 1263 consider whether read access to these objects should be allowed, 1264 since read access may be undesirable under certain circumstances. 1266 Some of the readable objects in this MIB module (i.e., objects with a 1267 MAX-ACCESS other than not-accessible) may be considered sensitive or 1268 vulnerable in some network environments. It is thus important to 1269 control even GET and/or NOTIFY access to these objects and possibly 1270 to even encrypt the values of these objects when sending them over 1271 the network via SNMP. These are the tables and objects and their 1272 sensitivity/vulnerability: 1274 o the pwMplsTable, pwMplsNonTeMappingTable, pwMplsTeMappingTable and 1275 pwMplsOutboundTable collectively show the PW over MPLS 1276 association. If an Administrator does not want to reveal this 1277 information, then these tables should be considered sensitive/ 1278 vulnerable. 1280 SNMP versions prior to SNMPv3 did not include adequate security. 1281 Even if the network itself is secure (for example by using IPsec), 1282 even then, there is no control as to who on the secure network is 1283 allowed to access and GET/SET (read/change/create/delete) the objects 1284 in this MIB module. 1286 It is RECOMMENDED that implementers consider the security features as 1287 provided by the SNMPv3 framework (see [RFC3410], section 8), 1288 including full support for the SNMPv3 cryptographic mechanisms (for 1289 authentication and privacy). 1291 Further, deployment of SNMP versions prior to SNMPv3 is NOT 1292 RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to 1293 enable cryptographic security. It is then a customer/operator 1294 responsibility to ensure that the SNMP entity giving access to an 1295 instance of this MIB module, is properly configured to give access to 1296 the objects only to those principals (users) that have legitimate 1297 rights to indeed GET or SET (change/create/delete) them. 1299 10. IANA Considerations 1301 The MIB module in this document uses the following IANA-assigned 1302 OBJECT IDENTIFIER values recorded in the SMI Numbers registry: 1304 Descriptor OBJECT IDENTIFIER value 1305 ---------- ----------------------- 1307 pwMplsStdMIB { transmission XXX } 1309 Editor's Note (to be removed prior to publication): The IANA is 1310 requested to assign a value for "XXX" under the 'transmission' 1311 subtree and to record the assignment in the SMI Numbers registry. 1312 When the assignment has been made, the RFC Editor is asked to replace 1313 "XXX" (here and in the MIB module) with the assigned value and to 1314 remove this note. 1316 11. References 1318 11.1. Normative References 1320 [BCP14] Bradner, S., "Key words for use in RFCs to Indicate 1321 requirement Levels", BCP 14, RFC 2119, March 1997. 1323 [PWMIB] Zelig, D. and T. Nadeau, "Pseudowire (PW) Management 1324 Information Base", work-in-progress . 1326 [PWTC] Nadeau, T. and D. Zelig, "Definitions for Textual 1327 Conventions and OBJECT-IDENTITIES for Pseudowires 1328 Management", work-in-progress . 1330 [RFC2578] McCloghrie, K., Ed., Perkins, D., Ed., and J. 1331 Schoenwaelder, Ed., "Structure of Management Information 1332 Version 2 (SMIv2)", STD 58, RFC 2578, April 1999. 1334 [RFC2579] McCloghrie, K., Ed., Perkins, D., Ed., and J. 1335 Schoenwaelder, Ed., "Textual Conventions for SMIv2", 1336 STD 58, RFC 2579, April 1999. 1338 [RFC2580] McCloghrie, K., Perkins, D., and J. Schoenwaelder, 1339 "Conformance Statements for SMIv2", STD 58, RFC 2580, 1340 April 1999. 1342 [RFC2863] McCloghrie, K. and F. Kastenholz, "The Interfaces Group 1343 MIB", RFC 2863, June 2000. 1345 [RFC3031] Rosen, E., Viswanathan, A., and R. Callon, "Multiprotocol 1346 Label Switching Architecture", RFC 3031, January 2001. 1348 [RFC3811] Nadeau, T. and J. Cucchiara, "Definitions of Textual 1349 Conventions (TCs) for Multiprotocol Label Switching (MPLS) 1350 Management", RFC 3811, June 2004. 1352 [RFC3812] Srinivasan, C., Viswanathan, A., and T. Nadeau, 1353 "Multiprotocol Label Switching (MPLS) Traffic Engineering 1354 (TE) Management Information Base (MIB)", RFC 3812, 1355 June 2004. 1357 [RFC3813] Srinivasan, C., Viswanathan, A., and T. Nadeau, 1358 "Multiprotocol Label Switching (MPLS) Label Switching 1359 Router (LSR) Management Information Base (MIB)", RFC 3813, 1360 June 2004. 1362 [RFC4447] Martini, L., Rosen, E., El-Aawar, N., Smith, T., and G. 1363 Heron, "Pseudowire Setup and Maintenance Using the Label 1364 Distribution Protocol (LDP)", RFC 4447, April 2006. 1366 11.2. Informative References 1368 [RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart, 1369 "Introduction and Applicability Statements for Internet- 1370 Standard Management Framework", RFC 3410, December 2002. 1372 [RFC3815] Cucchiara, J., Sjostrand, H., and J. Luciani, "Definitions 1373 of Managed Objects for the Multiprotocol Label Switching 1374 (MPLS), Label Distribution Protocol (LDP)", RFC 3815, 1375 June 2004. 1377 [RFC3916] Xiao, X., McPherson, D., and P. Pate, "Requirements for 1378 Pseudo-Wire Emulation Edge-to-Edge (PWE3)", RFC 3916, 1379 September 2004. 1381 [RFC3985] Bryant, S. and P. Pate, "Pseudo Wire Emulation Edge-to- 1382 Edge (PWE3) Architecture", RFC 3985, March 2005. 1384 Authors' Addresses 1386 David Zelig (editor) 1387 Corrigent Systems 1388 126, Yigal Alon St. 1389 Tel Aviv, 1390 Israel 1392 Phone: +972 3 6945 273 1393 Email: davidz@corrigent.com 1395 Thomas D. Nadeau (editor) 1396 BT 1397 BT Centre 1398 81 Newgate Street 1399 London EC1A 7AJ 1400 United Kingdom 1402 Email: thomas.nadeau@bt.com 1404 Full Copyright Statement 1406 Copyright (C) The IETF Trust (2007). 1408 This document is subject to the rights, licenses and restrictions 1409 contained in BCP 78, and except as set forth therein, the authors 1410 retain all their rights. 1412 This document and the information contained herein are provided on an 1413 "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS 1414 OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND 1415 THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS 1416 OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF 1417 THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED 1418 WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 1420 Intellectual Property 1422 The IETF takes no position regarding the validity or scope of any 1423 Intellectual Property Rights or other rights that might be claimed to 1424 pertain to the implementation or use of the technology described in 1425 this document or the extent to which any license under such rights 1426 might or might not be available; nor does it represent that it has 1427 made any independent effort to identify any such rights. Information 1428 on the procedures with respect to rights in RFC documents can be 1429 found in BCP 78 and BCP 79. 1431 Copies of IPR disclosures made to the IETF Secretariat and any 1432 assurances of licenses to be made available, or the result of an 1433 attempt made to obtain a general license or permission for the use of 1434 such proprietary rights by implementers or users of this 1435 specification can be obtained from the IETF on-line IPR repository at 1436 http://www.ietf.org/ipr. 1438 The IETF invites any interested party to bring to its attention any 1439 copyrights, patents or patent applications, or other proprietary 1440 rights that may cover technology that may be required to implement 1441 this standard. Please address the information to the IETF at 1442 ietf-ipr@ietf.org. 1444 Acknowledgment 1446 Funding for the RFC Editor function is provided by the IETF 1447 Administrative Support Activity (IASA).