idnits 2.17.1 draft-ietf-pwe3-pw-mpls-mib-08.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 19. -- Found old boilerplate from RFC 3978, Section 5.5 on line 1414. -- Found old boilerplate from RFC 3979, Section 5, paragraph 1 on line 1425. -- Found old boilerplate from RFC 3979, Section 5, paragraph 2 on line 1432. -- Found old boilerplate from RFC 3979, Section 5, paragraph 3 on line 1438. ** This document has an original RFC 3978 Section 5.4 Copyright Line, instead of the newer IETF Trust Copyright according to RFC 4748. ** This document has an original RFC 3978 Section 5.5 Disclaimer, instead of the newer disclaimer which includes the IETF Trust according to RFC 4748. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- == No 'Intended status' indicated for this document; assuming Proposed Standard Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack an Introduction section. (A line matching the expected section header was found, but with an unexpected indentation: ' 1 Introduction' ) ** The document seems to lack a Security Considerations section. (A line matching the expected section header was found, but with an unexpected indentation: ' 7 Security Considerations' ) ** The document seems to lack an IANA Considerations section. (See Section 2.2 of https://www.ietf.org/id-info/checklist for how to handle the case when there are no actions for IANA.) (A line matching the expected section header was found, but with an unexpected indentation: ' an IANA Considerations Section in RFCs", BCP: 26, RFC' ) Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the RFC 3978 Section 5.4 Copyright Line does not match the current year == Line 221 has weird spacing: '...N |PWin inSeg...' == Line 225 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 2006) is 6635 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) -- Missing reference section? 'PW-MIB' on line 1307 looks like a reference -- Missing reference section? 'BCP14' on line 1316 looks like a reference -- Missing reference section? 'RFC3985' on line 1297 looks like a reference -- Missing reference section? 'RFC3916' on line 1300 looks like a reference -- Missing reference section? 'PWCNTRL' on line 117 looks like a reference -- Missing reference section? 'RFC3031' on line 1335 looks like a reference -- Missing reference section? 'RFC3812' on line 1343 looks like a reference -- Missing reference section? 'RFC3813' on line 1348 looks like a reference -- Missing reference section? 'RFC3410' on line 1359 looks like a reference -- Missing reference section? 'RFC2578' on line 1319 looks like a reference -- Missing reference section? 'RFC2579' on line 1324 looks like a reference -- Missing reference section? 'RFC2580' on line 1328 looks like a reference -- Missing reference section? 'CEPMIB' on line 176 looks like a reference -- Missing reference section? 'PWTC' on line 1303 looks like a reference -- Missing reference section? 'RFC2863' on line 1332 looks like a reference -- Missing reference section? 'RFC3810' on line 291 looks like a reference -- Missing reference section? 'LDP' on line 1313 looks like a reference -- Missing reference section? 'RFC3811' on line 1339 looks like a reference -- Missing reference section? 'RFC2434' on line 1355 looks like a reference Summary: 6 errors (**), 0 flaws (~~), 5 warnings (==), 26 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Internet Draft David Zelig (Ed.) 3 Expires: August 2006 Corrigent Systems 5 Thomas D. Nadeau (Ed.) 6 Cisco Systems, Inc. 8 February 2006 10 Pseudo Wire (PW) over MPLS PSN Management Information Base 12 draft-ietf-pwe3-pw-mpls-mib-08.txt 14 Status of this Memo 16 By submitting this Internet-Draft, each author represents that any 17 applicable patent or other IPR claims of which he or she is aware 18 have been or will be disclosed, and any of which he or she becomes 19 aware will be disclosed, in accordance with Section 6 of BCP 79. 21 Internet-Drafts are working documents of the Internet Engineering 22 Task Force (IETF), its areas, and its working groups. Note that 23 other groups may also distribute working documents as Internet- 24 Drafts. 26 Internet-Drafts are draft documents valid for a maximum of six 27 months and may be updated, replaced, or obsoleted by other 28 documents at any time. It is inappropriate to use Internet-Drafts 29 as reference material or to cite them other than as "work in 30 progress." 32 The list of current Internet-Drafts can be accessed at 33 http://www.ietf.org/ietf/1id-abstracts.txt 34 The list of Internet-Draft Shadow Directories can be accessed at 35 http://www.ietf.org/shadow.html. 37 Abstract 39 This memo defines an experimental portion of the Management 40 Information Base (MIB) for use with network management protocols in 41 the Internet community. In particular, it describes a MIB module 42 for PW operation over Multi-Protocol Label Switching (MPLS) Label 43 Switch Router (LSR). 45 Pseudo Wire (PW) Over MPLS February 2006 46 Management Information Base 48 Table of Contents 50 Abstract..........................................................1 51 1 Introduction...................................................2 52 2 Terminology....................................................3 53 3 The Internet-Standard Management Framework.....................3 54 4 Feature Checklist..............................................4 55 5 MIB module usage...............................................4 56 5.1 PW MPLS MIB module usage.....................................4 57 6 Object definitions.............................................6 58 7 Security Considerations.......................................24 59 8 IANA considerations...........................................25 60 9 References....................................................25 61 9.1 Normative references........................................25 62 9.2 Informative references......................................26 63 10 Author's Addresses..........................................27 64 11 Full Copyright Statement....................................28 65 12 Intellectual Property Notice................................28 67 1 Introduction 69 This document describes a model for managing pseudo wire services 70 for transmission over different flavors of MPLS tunnels. The 71 general PW MIB module [PW-MIB] defines the parameters global to the 72 PW regardless of underlying PSN and emulated service. Indicating 73 PSN type of MPLS in PW-MIB references this module. 75 This document describes the MIB objects that define pseudo wire 76 association to the MPLS PSN, in a way that is not specific to the 77 carried service. 79 Together, [TEMIB and LSRMIB], describe the modeling of an MPLS 80 Tunnel, and a Tunnel's underlying cross-connects. The defined MIB 81 support MPLS-TE PSN, Non TE MPLS PSN (an outer tunnel created by 82 LDP or manually), and MPLS PW label only (no outer tunnel). 84 Pseudo Wire (PW) Over MPLS February 2006 85 Management Information Base 87 Conventions used in this document 89 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 90 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in 91 this document are to be interpreted as described in RFC-2119 92 [BCP14]. 94 2 Terminology 96 This document uses terminology from the document describing the PW 97 architecture [RFC3985], [RFC3916] and [PWCNTRL]. 99 The terms "Outbound" and "Inbound" in this MIB module are based on 100 the common practice in the MPLS standards, i.e. "outbound" are 101 toward the PSN. However, where these terms are used in an object 102 name, the object description clarifies the exact packet direction 103 to prevent confusion with these terms in other documents. 105 "PSN Tunnel" is a general term indicating a virtual connection 106 between the two PWE3 edge devices. Each tunnel may potentially 107 carry multiple PWs inside. In the scope of this document, it is 108 MPLS tunnel. 110 This document uses terminology from the document describing the 111 MPLS architecture [RFC3031] for MPLS PSN. A Label Switched Path 112 (LSP) is modeled as described in [RFC3812] and [RFC3813] via a 113 series of cross-connects through 1 or more Label switch routers 114 (LSR). 116 In MPLS PSN, a PW connection typically uses a PW Label within a 117 Tunnel Label [PWCNTRL]. Multiple pseudo wires each with a unique PW 118 Label can share the same Tunnel. For PW transport over MPLS, the 119 Tunnel Label is known as the "outer" Label, while the PW Label is 120 known as the "inner" Label. An exception to this is with adjacent 121 LSRs or the use of PHP. In this case, there is an option for PWs to 122 connect directly without an outer Label. 124 3 The Internet-Standard Management Framework 126 For a detailed overview of the documents that describe the current 127 Internet-Standard Management Framework, please refer to section 7 128 of RFC 3410 [RFC3410]. 130 Managed objects are accessed via a virtual information store, 131 termed the Management Information Base or MIB. MIB objects are 132 generally accessed through the Simple Network Management Protocol 133 (SNMP). Objects in the MIB are defined using the mechanisms defined 134 in the Structure of Management Information (SMI). This memo 135 specifies a MIB module that is compliant to the SMIv2, which is 136 Pseudo Wire (PW) Over MPLS February 2006 137 Management Information Base 139 described in STD 58,RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] 140 and STD 58, RFC 2580 [RFC2580]. 142 4 Feature Checklist 144 The PW MPLS MIB module is designed to satisfy the following 145 requirements and constraints: 147 - The MIB module supports both manually configured and signaled 148 PWs. 150 - The MIB module supports point-to-point PW connections. 152 - The MIB module enables the use of any emulated service. 154 - The MIB module supports MPLS-TE outer tunnel, Non TE MPLS outer 155 tunnel (an outer tunnel signaled by LDP or set-up manually), and 156 no outer tunnel (where the PW label is the only label in the 157 incoming MPLS stack). The later case is applicable for manual 158 configuration of PW over a single hop (in multiple hops case, it 159 is required to have an outer MPLS tunnel). 161 5 MIB module usage 163 The MIB module structure for defining a PW service is composed from 164 three types of modules. 166 The first type is the PW MIB module [PW-MIB], which configures 167 general parameters of the PW that are common to all types of 168 emulated services and PSN. 170 The second type of modules is per PSN module. There is a separate 171 module for each type of PSN. This document defines the MIB module 172 for MPLS (PW-MPLS-MIB). 174 The third type of modules is service-specific module, which is 175 emulated signal type dependent. These modules are defined in other 176 documents; see for example [CEPMIB]. 178 [PWTC] defines some of the object types used in this module. 180 5.1 PW MPLS MIB module usage 182 - The PW table (pwVcTable) in [PW-MIB] is used for all PW types 183 (ATM, FR, Ethernet, SONET, etc.). This table contains high level 184 generic parameters related to the PW creation. The operator or the 185 agent create a row for each PW. 187 Pseudo Wire (PW) Over MPLS February 2006 188 Management Information Base 190 - If the selected PSN type in pwVcTable is MPLS, the agent creates 191 a row in the MPLS specific parameters table (pwMplsVcTable) in 192 this module, which contains MPLS specific parameters such as EXP 193 bits handling and outer tunnel configuration. 195 - The operator configures the association to the desired MPLS 196 tunnel (require for MPLS TE tunnels or manually configured PWs) 197 through the pwMplsTeOutbaoundTable. For LDP based outer tunnel, 198 there is no need for manual configuration since there is only a 199 single tunnel toward the peer. 201 - The agent creates rows in the MPLS mapping table in order to 202 allow quick retrieval of information based on the tunnel indexes. 204 The relation to the MPLS network is by configuration of the edge 205 LSR only - that is to say, the LSR providing the PW function. Since 206 Tunnels are uni-directional, a pair of tunnels must exist (one for 207 inbound, one for outbound). The following graphic depicts a VC that 208 originates and terminates at LSR-M. It uses LSPs A and B formed by 209 Tunnels Ax and Bx continuing through LSR-N to LSR-P. The 210 concatenations of Tunnels create the LSPs. Note: 'X' denotes a 211 Tunnel's cross-connect. 213 LSP-A 214 <- - - - - - - - - - - - - - - - - - - - - - - - - - - - 216 +---- (edge) LSR-M ---+ +--------- LSR-N ---------+ + LSR-P 217 |---+ | | | | 218 | | Tunnel | | Tunnel | | 219 + | A1 (M<-N) +----+ +----+ A2 (M<-P) +----+ +----+ 220 | | <------| | | |<--------------| | | | 221 <-->| N |PWin inSeg |MPLS| |MPLS| outSeg inSeg |MPLS| |MPLS| 222 N S | | <---X<-----| IF | | IF |<------X<------| IF | | IF | 223 A E | S | | |<-->| | | |<-->| | | 224 T R | | --->X----->| | | |------>X------>| | | | 225 I V | P |PWout outSeg| | | | inSeg outSeg | | | | 226 V I | | ------>| | | |-------------->| | | | 227 E C + | Tunnel +----+ +----+ Tunnel +----+ +----+ 228 E |---+ B1 (M->N) | | B2 (M->P) | | 229 | | | | | 230 +---------------------+ +-------------------------+ +----- 232 - - - - - - - - - - - - - - - - - - - - - - - - - - - -> 233 LSP-B 235 The PW-MPLS-STD-MIB supports three options for MPLS network: 237 - In the MPLS-TE case, Tunnel A1 and B1 are created via the MPLS- 238 TE-STD-MIB [RFC3812]. The tunnels are associated to the PW by the 239 (4) indexes that uniquely identify the Tunnel at the TE-MIB. 241 Pseudo Wire (PW) Over MPLS February 2006 242 Management Information Base 244 - In the Non TE case, Tunnel A1 and B1 are either manually 245 configured or set up with LDP. The tunnels are associated to the PW 246 by the XC index in the MPLS-LSR-STD-MIB [RFC3813]. 248 - In the PW label only case, there is no outer tunnel on top of the 249 PW label. This case is useful in case of adjacent PEs in manual 250 configuration mode. Note that when LSR-N acts as PHP for the outer 251 tunnel label, there are still entries for the outer tunnel in the 252 relevant MPLS MIB modules. 254 A combination of MPLS-TE outer tunnel(s) and LDP outer tunnel for 255 the same PW is allowed through the pwVcMplsOutboundTunnel. The 256 current tunnel that is used to forward traffic is indicated in the 257 object pwVcMplsOutboundTunnelTypeInUse. 259 The PW MPLS MIB module reports through the inbound table the XC 260 entry in the LDP-STD-MIB of the PW that were signaled through LDP. 262 This MIB module assumes that a PW can be associated to one MPLS-TE 263 tunnel at a time. This tunnel may be composed of multiple instances 264 (i.e. LSP), each represented by a separate instance index. The 265 current active LSP is reported through this MIB module. 267 It is worth noting that inbound (tunnel originated in the remote 268 PE) mapping is nor configured nor reported through the PW MPLS MIB 269 module since the local PE does not know the inbound association 270 between specific PW and MPLS tunnels. 272 6 Object definitions 274 PW-MPLS-STD-MIB DEFINITIONS ::= BEGIN 276 IMPORTS 277 MODULE-IDENTITY, OBJECT-TYPE, Unsigned32, transmission 278 FROM SNMPv2-SMI -- [RFC2578] 280 MODULE-COMPLIANCE, OBJECT-GROUP 281 FROM SNMPv2-CONF -- [RFC2580] 283 StorageType 284 FROM SNMPv2-TC -- [RFC2579] 286 InterfaceIndexOrZero 287 FROM IF-MIB -- [RFC2863] 289 MplsTunnelIndex, MplsTunnelInstanceIndex, 290 MplsLdpIdentifier, MplsLsrIdentifier 291 FROM MPLS-TC-STD-MIB -- [RFC3810] 293 MplsIndexType 294 Pseudo Wire (PW) Over MPLS February 2006 295 Management Information Base 297 FROM MPLS-LSR-STD-MIB -- [RFC3813] 299 PwIndexType 300 FROM PW-TC-STD-MIB 302 pwIndex 303 FROM PW-STD-MIB 305 ; 307 pwMplsStdMIB MODULE-IDENTITY 308 LAST-UPDATED "200602011200Z" -- 1 February 2006 12:00:00 GMT 309 ORGANIZATION "Pseudo Wire Edge to Edge Emulation (PWE3) Working 310 Group." 311 CONTACT-INFO 312 " 313 David Zelig, Editor 314 E-mail: davidz@corrigent.com 316 Thomas D. Nadeau, Editor 317 Email: tnadeau@cisco.com 319 The PWE3 Working Group (email distribution pwe3@ietf.org, 320 http://www.ietf.org/html.charters/pwe3-charter.html) 321 " 322 DESCRIPTION 323 "This MIB module complements the PW-STD-MIB module for PW 324 operation over MPLS. 326 Copyright (C) The Internet Society (2006). This version 327 of this MIB module is part of RFC yyyy; see the RFC 328 itself for full legal notices. 329 -- RFC Ed.: replace yyyy with actual RFC number & remove 330 -- this note 331 " 332 -- Revision history. 333 REVISION "200602011200Z" -- 1 February 2006 12:00:00 GMT 334 DESCRIPTION 335 " First published as RFCWXYZ. " 336 -- RFC Editor: Please replace WXYZ with correct # and remove this - 337 -- note 339 ::= { transmission XXXX } 341 -- RFC Editor: To be assigned by IANA. Please replace XXX 342 -- with the assigned value and remove this note. 344 -- Top-level components of this MIB. 346 -- Notifications 347 pwMplsNotifications OBJECT IDENTIFIER 348 Pseudo Wire (PW) Over MPLS February 2006 349 Management Information Base 351 ::= { pwMplsStdMIB 0 } 353 -- Tables, Scalars 354 pwMplsObjects OBJECT IDENTIFIER 355 ::= { pwMplsStdMIB 1 } 356 -- Conformance 357 pwMplsConformance OBJECT IDENTIFIER 358 ::= { pwMplsStdMIB 2 } 360 -- PW MPLS table 362 pwMplsTable OBJECT-TYPE 363 SYNTAX SEQUENCE OF PwMplsEntry 364 MAX-ACCESS not-accessible 365 STATUS current 366 DESCRIPTION 367 "This table controls MPLS specific parameters when the PW is 368 going to be carried over MPLS PSN." 369 ::= { pwMplsObjects 1 } 371 pwMplsEntry OBJECT-TYPE 372 SYNTAX PwMplsEntry 373 MAX-ACCESS not-accessible 374 STATUS current 375 DESCRIPTION 376 "A row in this table represents parameters specific to MPLS 377 PSN for a pseudo wire (PW). The row is created 378 automatically by the local agent if the pwPsnType is 379 MPLS. It is indexed by pwIndex, which uniquely 380 identifying a singular PW. 381 " 382 INDEX { pwIndex } 384 ::= { pwMplsTable 1 } 386 PwMplsEntry ::= SEQUENCE { 387 pwMplsMplsType BITS, 388 pwMplsExpBitsMode INTEGER, 389 pwMplsExpBits Unsigned32, 390 pwMplsTtl Unsigned32, 391 pwMplsLocalLdpID MplsLdpIdentifier, 392 pwMplsLocalLdpEntityID MplsLsrIdentifier, 393 pwMplsPeerLdpID MplsLdpIdentifier, 394 pwMplsStorageType StorageType 395 } 397 pwMplsMplsType OBJECT-TYPE 398 SYNTAX BITS { 399 mplsTe (0), 400 mplsNonTe (1), 401 pwOnly (2) 402 Pseudo Wire (PW) Over MPLS February 2006 403 Management Information Base 405 } 406 MAX-ACCESS read-write 407 STATUS current 408 DESCRIPTION 409 "Set by the operator to indicate the outer tunnel types, if 410 exists. mplsTe(0) is used if the outer tunnel was set-up 411 by MPLS-TE, and mplsNonTe(1) is used the outer tunnel was 412 set up by LDP or manually. Combination of mplsTe(0) and 413 mplsNonTe(1) may exist together. 414 pwOnly(2) is used if there is no outer tunnel label, i.e. 415 in static provisioning without MPLS tunnel. pwOnly(2) 416 cannot be combined with mplsNonTe(1) or mplsTe(0)." 417 DEFVAL { { mplsNonTe } } 418 ::= { pwMplsEntry 1 } 420 pwMplsExpBitsMode OBJECT-TYPE 421 SYNTAX INTEGER { 422 outerTunnel (1), 423 specifiedValue (2), 424 serviceDependant (3) 425 } 427 MAX-ACCESS read-write 428 STATUS current 429 DESCRIPTION 430 "Set by the operator to indicate the way the PW shim label 431 EXP bits are to be determined. The value of outerTunnel(1) 432 is used where there is an outer tunnel - pwMplsMplsType 433 is mplsTe(0) or mplsNonTe(1). Note that in this case there 434 is no need to mark the PW label with the EXP bits since the 435 PW label is not visible to the intermediate nodes. 436 If there is no outer tunnel, specifiedValue(2) indicates 437 that the value is specified by pwMplsExpBits, and 438 serviceDependant(3) indicates that the EXP bits are set 439 based on a rule which is implementation specific." 441 DEFVAL { outerTunnel } 442 ::= { pwMplsEntry 2 } 444 pwMplsExpBits OBJECT-TYPE 445 SYNTAX Unsigned32 (0..7) 446 MAX-ACCESS read-write 447 STATUS current 448 DESCRIPTION 449 "Set by the operator to indicate the MPLS EXP bits to be 450 used on the PW shim label if pwMplsExpBitsMode is 451 specifiedValue(2), zero otherwise." 452 DEFVAL { 0 } 453 ::= { pwMplsEntry 3 } 455 pwMplsTtl OBJECT-TYPE 456 Pseudo Wire (PW) Over MPLS February 2006 457 Management Information Base 459 SYNTAX Unsigned32 (0..255) 460 MAX-ACCESS read-write 461 STATUS current 462 DESCRIPTION 463 "Set by the operator to indicate the PW TTL value to be 464 used on the PW shim label." 465 DEFVAL { 2 } 466 ::= { pwMplsEntry 4 } 468 pwMplsLocalLdpID OBJECT-TYPE 469 SYNTAX MplsLdpIdentifier 470 MAX-ACCESS read-write 471 STATUS current 472 DESCRIPTION 473 "The local LDP identifier of the LDP entity creating 474 this PW in the local node. As the PW labels are always 475 set from the per platform label space, the last two octets 476 in the LDP ID MUST be always both zeros." 477 REFERENCE 478 "'LDP specifications', RFC 3036 section 2.2.2." 479 ::= { pwMplsEntry 5 } 481 pwMplsLocalLdpEntityID OBJECT-TYPE 482 SYNTAX MplsLsrIdentifier 483 MAX-ACCESS read-write 484 STATUS current 485 DESCRIPTION 486 "The local node LDP Entity ID of the LDP entity creating 487 this PW. Should return the value of all zeros if not 488 used." 489 ::= { pwMplsEntry 6 } 491 pwMplsPeerLdpID OBJECT-TYPE 492 SYNTAX MplsLdpIdentifier 493 MAX-ACCESS read-only 494 STATUS current 495 DESCRIPTION 496 "The peer LDP identifier as identified from the LDP 497 session. Should return the value of zero if not applicable 498 or not known yet." 499 ::= { pwMplsEntry 7 } 501 pwMplsStorageType OBJECT-TYPE 502 SYNTAX StorageType 503 MAX-ACCESS read-write 504 STATUS current 505 DESCRIPTION 506 "This variable indicates the storage type for this row." 507 ::= { pwMplsEntry 8 } 508 Pseudo Wire (PW) Over MPLS February 2006 509 Management Information Base 511 -- End of PW MPLS table 513 -- Pseudo Wire MPLS Outbound Tunnel table 515 pwMplsOutboundTable OBJECT-TYPE 516 SYNTAX SEQUENCE OF PwMplsOutboundEntry 517 MAX-ACCESS not-accessible 518 STATUS current 519 DESCRIPTION 520 "This table reports and configure the current outbound MPLS 521 tunnels (i.e. toward the PSN) or the physical interface in 522 case of PW label only that carry the PW traffic. It also 523 reports the current outer tunnel and LSP which forward the 524 PW traffic." 525 ::= { pwMplsObjects 2 } 527 pwMplsOutboundEntry OBJECT-TYPE 528 SYNTAX PwMplsOutboundEntry 529 MAX-ACCESS not-accessible 530 STATUS current 531 DESCRIPTION 532 "A row in this table configures the outer tunnel used for 533 carrying the PW traffic toward the PSN. 534 In the case of PW label only, it configures the interface 535 that will carry the PW traffic. 537 An entry in this table augments the pwMplsEntry, and is 538 created automatically when the corresponding row has been 539 created by the agent in the pwMplsEntry. 541 This table points to the appropriate MPLS MIB module. 542 In the MPLS-TE case, the 3 variables relevant to the 543 indexing of a TE tunnel head-end are used as in 544 MPLS-TE-STD-MIB are to be configured, and the tunnel 545 instance indicates the LSP that is currently in use for 546 forwarding the traffic. 548 In case of signaled Non-TE MPLS (an outer tunnel label 549 assigned by LDP) the table points to the XC entry in the 550 LSR-STD-MIB. If the Non-TE MPLS tunnel is manually 551 configured, the operator configures the XC pointer to this 552 tunnel. 554 In case of PW label only (no outer tunnel) the ifIndex of 555 the port to carry the PW is configured here. 557 It is possible to associate a PW to one TE tunnel head-end 558 and a non-TE tunnel together. An indication in this table 559 will report the currently active one, In addition, in the 560 TE case the table reports the active tunnel instance 561 (i.e. the specific LSP in use). 563 Pseudo Wire (PW) Over MPLS February 2006 564 Management Information Base 566 " 568 AUGMENTS { pwMplsEntry } 570 ::= { pwMplsOutboundTable 1 } 572 PwMplsOutboundEntry ::= SEQUENCE { 573 pwMplsOutboundLsrXcIndex MplsIndexType, 574 pwMplsOutboundTunnelIndex MplsTunnelIndex, 575 pwMplsOutboundTunnelInstance MplsTunnelInstanceIndex, 576 pwMplsOutboundTunnelLclLSR MplsLsrIdentifier, 577 pwMplsOutboundTunnelPeerLSR MplsLsrIdentifier, 578 pwMplsOutboundIfIndex InterfaceIndexOrZero, 579 pwMplsOutboundTunnelTypeInUse INTEGER 580 } 582 pwMplsOutboundLsrXcIndex OBJECT-TYPE 583 SYNTAX MplsIndexType 584 MAX-ACCESS read-write 585 STATUS current 586 DESCRIPTION 587 "This object is applicable if pwMplsMplsType mplsNonTe(1) 588 bit is set, and MUST return a value of zero otherwise. 589 If the outer tunnel is signaled, the object is read-only 590 and indicates the XC index in the MPLS-LSR-STD-MIB of the 591 outer tunnel toward the peer. Otherwise (tunnel is set-up 592 manually) the operator defines the XC index of the manually 593 created outer tunnel through this object. 594 " 595 ::= { pwMplsOutboundEntry 1 } 597 pwMplsOutboundTunnelIndex OBJECT-TYPE 598 SYNTAX MplsTunnelIndex 599 MAX-ACCESS read-write 600 STATUS current 601 DESCRIPTION 602 "This object is applicable if pwMplsMplsType mplsTe(0) 603 bit is set, and MUST return a value of zero otherwise. 604 It is Part of set of indexes for outbound tunnel. 605 The operator set this object to represent the desired 606 tunnel head-end toward the peer for carrying the PW 607 traffic. 608 " 609 ::= { pwMplsOutboundEntry 2 } 611 pwMplsOutboundTunnelInstance OBJECT-TYPE 612 SYNTAX MplsTunnelInstanceIndex 613 MAX-ACCESS read-only 614 STATUS current 615 DESCRIPTION 616 Pseudo Wire (PW) Over MPLS February 2006 617 Management Information Base 619 "This object is applicable if pwMplsMplsType mplsTe(0) 620 bit is set, and MUST return a value of zero otherwise. 621 It indicates the actual tunnel instance that is currently 622 active and carrying the PW traffic - it should return the 623 value of zero until if the information from the MPLS-TE 624 application is not yet known. 625 " 626 ::= { pwMplsOutboundEntry 3 } 628 pwMplsOutboundTunnelLclLSR OBJECT-TYPE 629 SYNTAX MplsLsrIdentifier 630 MAX-ACCESS read-write 631 STATUS current 632 DESCRIPTION 633 "This object is applicable if pwMplsMplsType mplsTe(0) 634 bit is set, and MUST return a value of all zeros otherwise. 635 It is part of set of indexes for outbound tunnel. 636 The operator set this object to represent the desired 637 tunnel head-end toward the peer for carrying the PW 638 traffic. 639 " 640 ::= { pwMplsOutboundEntry 4 } 642 pwMplsOutboundTunnelPeerLSR OBJECT-TYPE 643 SYNTAX MplsLsrIdentifier 644 MAX-ACCESS read-write 645 STATUS current 646 DESCRIPTION 647 "This object is applicable if pwMplsMplsType mplsTe(0) 648 bit is set, and MUST return a value of zero otherwise. 649 It is part of set of indexes for outbound tunnel. It is 650 typically equal to pwPeerAddr. 651 " 652 ::= { pwMplsOutboundEntry 5 } 654 pwMplsOutboundIfIndex OBJECT-TYPE 655 SYNTAX InterfaceIndexOrZero 656 MAX-ACCESS read-write 657 STATUS current 658 DESCRIPTION 659 "This object is applicable if pwMplsMplsType pwOnly(0) 660 bit is set, and MUST return a value of zero otherwise. 661 The operator configure the ifIndex of the outbound port 662 in this case. 663 " 664 ::= { pwMplsOutboundEntry 6 } 666 pwMplsOutboundTunnelTypeInUse OBJECT-TYPE 667 SYNTAX INTEGER { 668 notYetKnown (1), 669 mplsTe (2), 670 Pseudo Wire (PW) Over MPLS February 2006 671 Management Information Base 673 mplsNonTe (3), 674 pwOnly (4) 675 } 676 MAX-ACCESS read-only 677 STATUS current 678 DESCRIPTION 679 "This object indicates the current tunnel that is carrying 680 the PW traffic. 681 The value of notYetKnown(1) should be used if the agent is 682 currently unable to determine which tunnel or interface is 683 carrying the PW, for example because both tunnels are in 684 operational status down. 685 " 686 ::= { pwMplsOutboundEntry 7 } 688 -- End of PW MPLS Outbound Tunnel table 690 -- PW MPLS inbound table 692 pwMplsInboundTable OBJECT-TYPE 693 SYNTAX SEQUENCE OF PwMplsInboundEntry 694 MAX-ACCESS not-accessible 695 STATUS current 696 DESCRIPTION 697 "This table indicates the PW LDP XC entry in the 698 MPLS-LSR-STD-MIB for signaled PWs. 699 " 700 ::= { pwMplsObjects 3 } 702 pwMplsInboundEntry OBJECT-TYPE 703 SYNTAX PwMplsInboundEntry 704 MAX-ACCESS not-accessible 705 STATUS current 706 DESCRIPTION 707 "A row in this table is created by the agent 708 for each signaled PW, and shows the XC index related to 709 the PW signaling in the inbound direction in the 710 MPLS-LSR-STD-MIB that controls and display the information 711 for all the LDP signaling processes in the local node. 712 " 713 INDEX { pwIndex } 715 ::= { pwMplsInboundTable 1 } 717 PwMplsInboundEntry ::= SEQUENCE { 718 pwMplsInboundXcIndex MplsIndexType 719 } 721 pwMplsInboundXcIndex OBJECT-TYPE 722 SYNTAX MplsIndexType 723 Pseudo Wire (PW) Over MPLS February 2006 724 Management Information Base 726 MAX-ACCESS read-only 727 STATUS current 728 DESCRIPTION 729 "The XC index representing this PW in the inbound 730 direction. Should return the value of zero if the 731 information is not yet known." 732 ::= { pwMplsInboundEntry 1 } 734 -- End of PW MPLS inbound table 736 -- PW to Non-TE mapping Table. 738 pwMplsNonTeMappingTable OBJECT-TYPE 739 SYNTAX SEQUENCE OF PwMplsNonTeMappingEntry 740 MAX-ACCESS not-accessible 741 STATUS current 742 DESCRIPTION 743 "This table indicates outbound Tunnel to a PW in non-TE 744 applications, maps the PW to it's (inbound) XC entry, and 745 indicates the PW to physical interface mapping for a PW 746 label to physical interface a PW label is in use without 747 outer tunnel. 748 " 749 ::= { pwMplsObjects 4 } 751 pwMplsNonTeMappingEntry OBJECT-TYPE 752 SYNTAX PwMplsNonTeMappingEntry 753 MAX-ACCESS not-accessible 754 STATUS current 755 DESCRIPTION 756 "A row in this table displays the association 757 between the PW and 758 - it's non-TE MPLS outbound outer Tunnel or, 759 - it's XC entry in the MPLS-LSR-STD-MIB, 760 - it's physical interface if there is no outer tunnel 761 (PW label only) and manual configuration. 763 Rows are created in this table by the by the 764 agent depending on the setting of pwMplsMplsType: 766 - If pwMplsMplsType mplsNonTe(1) bit is set, the agent 767 creates a row for the outbound direction 768 (pwMplsNonTeMappingDirection set to psnBound(1)). 769 The pwMplsNonTeMappingXcIndex holds the XC index in the 770 MPLS-LSR-STD-MIB of the PSN bound outer tunnel. 771 pwMplsNonTeMappingIfIndex MUST be zero for this row. 773 - If pwMplsMplsType pwOnly(2) bit is set, the agent 774 creates a row for the outbound direction 775 (pwMplsNonTeMappingDirection set to psnBound(1)). 776 The pwMplsNonTeMappingIfIndex holds the ifIndex of the 777 Pseudo Wire (PW) Over MPLS February 2006 778 Management Information Base 780 physical port this PW will use in the outbound direction. 781 pwMplsNonTeMappingXcIndex MUST be zero for this row. 783 - If the PW has been set-up by signaling protocol (i.e. 784 pwOwner equal pwIdFecSignaling(2) or 785 genFecSignaling(3)), the agent creates a row for the 786 inbound direction (pwMplsNonTeMappingDirection set to 787 fromPsn(2)). 788 The pwMplsNonTeMappingXcIndex holds the XC index in the 789 MPLS-LSR-STD-MIB of the PW LDP generated XC entry. 790 pwMplsNonTeMappingIfIndex MUST be zero for this row. 792 An application can use this table to quickly retrieve the 793 PW carried over specific non-TE MPLS outer tunnel or 794 physical interface. 795 " 797 INDEX { pwMplsNonTeMappingDirection, 798 pwMplsNonTeMappingXcIndex, 799 pwMplsNonTeMappingIfIndex, 800 pwMplsNonTeMappingVcIndex } 802 ::= { pwMplsNonTeMappingTable 1 } 804 PwMplsNonTeMappingEntry ::= SEQUENCE { 805 pwMplsNonTeMappingDirection INTEGER, 806 pwMplsNonTeMappingXcIndex MplsIndexType, 807 pwMplsNonTeMappingIfIndex InterfaceIndexOrZero, 808 pwMplsNonTeMappingVcIndex PwIndexType 809 } 811 pwMplsNonTeMappingDirection OBJECT-TYPE 812 SYNTAX INTEGER { 813 psnBound (1), 814 fromPsn (2) 815 } 816 MAX-ACCESS not-accessible 817 STATUS current 818 DESCRIPTION 819 "Index for the conceptual XC row identifying Tunnel to PW 820 mappings, indicating the direction of packet flow the entry 821 is related too. 822 psnBound(1) indicates that the entry is related to 823 packets toward the PSN. 824 fromPsn(2) indicates that the entry is related to 825 packets coming from the PSN. 826 " 827 ::= { pwMplsNonTeMappingEntry 1 } 829 pwMplsNonTeMappingXcIndex OBJECT-TYPE 830 SYNTAX MplsIndexType 831 Pseudo Wire (PW) Over MPLS February 2006 832 Management Information Base 834 MAX-ACCESS not-accessible 835 STATUS current 836 DESCRIPTION 837 "See the description clause of pwMplsNonTeMappingEntry for 838 the usage guidelines of this object." 839 ::= { pwMplsNonTeMappingEntry 2 } 841 pwMplsNonTeMappingIfIndex OBJECT-TYPE 842 SYNTAX InterfaceIndexOrZero 843 MAX-ACCESS not-accessible 844 STATUS current 845 DESCRIPTION 846 "See the description clause of pwMplsNonTeMappingEntry for 847 the usage guidelines of this object." 848 ::= { pwMplsNonTeMappingEntry 3 } 850 pwMplsNonTeMappingVcIndex OBJECT-TYPE 851 SYNTAX PwIndexType 852 MAX-ACCESS read-only 853 STATUS current 854 DESCRIPTION 855 "The value that represent the PW in the pwTable." 856 ::= { pwMplsNonTeMappingEntry 4 } 858 -- End of PW to Non-TE mapping Table. 860 -- PW to TE MPLS tunnels mapping Table. 862 pwMplsTeMappingTable OBJECT-TYPE 863 SYNTAX SEQUENCE OF PwMplsTeMappingEntry 864 MAX-ACCESS not-accessible 865 STATUS current 866 DESCRIPTION 867 "This table enable the retrieval of a PW association to the 868 outbound MPLS tunnel for MPLS-TE applications." 869 ::= { pwMplsObjects 5 } 871 pwMplsTeMappingEntry OBJECT-TYPE 872 SYNTAX PwMplsTeMappingEntry 873 MAX-ACCESS not-accessible 874 STATUS current 875 DESCRIPTION 876 "A row in this table represents the association 877 between a PW and it's MPLS-TE outer (head-end) Tunnel. 879 An application can use this table to quickly retrieve the 880 list of the PWs that are configured on a specific MPLS TE 881 outer tunnel. 883 The pwMplsTeMappingTunnelInstance reports the actual 884 Pseudo Wire (PW) Over MPLS February 2006 885 Management Information Base 887 LSP out of the tunnel head-end that is currently 888 forwarding the traffic. 890 The table in indexed by the head-end indexes of a TE 891 tunnel and the PW index. 892 " 894 INDEX { pwMplsTeMappingTunnelIndex, 895 pwMplsTeMappingTunnelInstance, 896 pwMplsTeMappingTunnelPeerLsrID, 897 pwMplsTeMappingTunnelLocalLsrID, 898 pwMplsTeMappingVcIndex } 900 ::= { pwMplsTeMappingTable 1 } 902 PwMplsTeMappingEntry ::= SEQUENCE { 903 pwMplsTeMappingTunnelIndex MplsTunnelIndex, 904 pwMplsTeMappingTunnelInstance MplsTunnelInstanceIndex, 905 pwMplsTeMappingTunnelPeerLsrID MplsLsrIdentifier, 906 pwMplsTeMappingTunnelLocalLsrID MplsLsrIdentifier, 907 pwMplsTeMappingVcIndex PwIndexType 908 } 910 pwMplsTeMappingTunnelIndex OBJECT-TYPE 911 SYNTAX MplsTunnelIndex 912 MAX-ACCESS not-accessible 913 STATUS current 914 DESCRIPTION 915 "Primary index for the conceptual row identifying the 916 MPLS-TE tunnel that is carrying the PW traffic." 917 ::= { pwMplsTeMappingEntry 1 } 919 pwMplsTeMappingTunnelInstance OBJECT-TYPE 920 SYNTAX MplsTunnelInstanceIndex 921 MAX-ACCESS not-accessible 922 STATUS current 923 DESCRIPTION 924 "This object identify the MPLS-TE LSP that is carrying the 925 PW traffic. Should return the value of zero if the 926 information of the specific LSP is not yet known. 927 Note that based on the recommendation in the 928 MPLS-TC-STD-MIB, instance index 0 should refer to the 929 configured tunnel interface." 930 ::= { pwMplsTeMappingEntry 2 } 932 pwMplsTeMappingTunnelPeerLsrID OBJECT-TYPE 933 SYNTAX MplsLsrIdentifier 934 MAX-ACCESS not-accessible 935 STATUS current 936 DESCRIPTION 937 "Identifies the Peer LSR when the outer tunnel is MPLS-TE 938 Pseudo Wire (PW) Over MPLS February 2006 939 Management Information Base 941 based." 942 ::= { pwMplsTeMappingEntry 3 } 944 pwMplsTeMappingTunnelLocalLsrID OBJECT-TYPE 945 SYNTAX MplsLsrIdentifier 946 MAX-ACCESS not-accessible 947 STATUS current 948 DESCRIPTION 949 "Identifies the local LSR." 950 ::= { pwMplsTeMappingEntry 4 } 952 pwMplsTeMappingVcIndex OBJECT-TYPE 953 SYNTAX PwIndexType 954 MAX-ACCESS read-only 955 STATUS current 956 DESCRIPTION 957 "The value that represent the PW in the pwTable." 958 ::= { pwMplsTeMappingEntry 5 } 960 -- End of PW to TE MPLS tunnels mapping Table. 962 -- conformance information 964 pwMplsGroups OBJECT IDENTIFIER ::= { pwMplsConformance 1 } 965 pwMplsCompliances OBJECT IDENTIFIER ::= { pwMplsConformance 2 } 967 -- Compliance requirement for fully compliant implementations. 969 pwMplsModuleFullCompliance MODULE-COMPLIANCE 970 STATUS current 971 DESCRIPTION 972 "The compliance statement for agents that provide full 973 support for PW-MPLS MIB Module. Such devices can 974 then be monitored and also be configured using 975 this MIB module." 977 MODULE -- this module 978 MANDATORY-GROUPS { pwMplsGroup, 979 pwMplsOutboundMainGroup, 980 pwMplsInboundGroup, 981 pwMplsMappingGroup 982 } 984 GROUP pwMplsOutboundTeGroup 985 DESCRIPTION "This group MUST be supported if the implementation 986 allows MPLS TE tunnels to carry PW traffic. 987 " 989 OBJECT pwMplsMplsType 990 DESCRIPTION "Support of pwOnly(2) is not required. At least one 991 of mplsTe(0) or mplsNonTe(1) MUST be supported if 992 Pseudo Wire (PW) Over MPLS February 2006 993 Management Information Base 995 signaling of PW is supported. 996 " 998 OBJECT pwMplsExpBitsMode 999 DESCRIPTION "Support of specifiedValue(2) and 1000 serviceDependant(3) is optional. 1001 " 1003 OBJECT pwMplsLocalLdpID 1004 MIN-ACCESS read-only 1005 DESCRIPTION "A read-write access is required if the 1006 implementation supports more than one LDP entity 1007 identifier for PW signaling. 1008 " 1010 OBJECT pwMplsLocalLdpEntityID 1011 MIN-ACCESS read-only 1012 DESCRIPTION "A read-write access is required if the 1013 implementation supports more than one LDP entity 1014 index for PW signaling. 1015 " 1017 OBJECT pwMplsOutboundLsrXcIndex 1018 MIN-ACCESS read-only 1019 DESCRIPTION "A value other than zero MUST be supported if the 1020 implementation support non TE signaling of the 1021 outer tunnel. 1022 A read-write access MUST be supported if the 1023 implementation supports manually setting of the PW 1024 labels and carrying them over non-TE tunnels. 1025 " 1027 OBJECT pwMplsOutboundIfIndex 1028 MIN-ACCESS read-only 1029 DESCRIPTION "A value other than zero and read-write operations 1030 MUST be supported if the implementation supports 1031 manully configured PW without MPLS outer tunnel. 1032 " 1033 ::= { pwMplsCompliances 1 } 1035 -- Compliance requirement for Read Only compliant implementations. 1037 pwMplsModuleReadOnlyCompliance MODULE-COMPLIANCE 1038 STATUS current 1039 DESCRIPTION 1040 "The compliance statement for agents that provide read 1041 only support for PW-MPLS MIB Module. Such devices can 1042 then be monitored but cannot be configured using this 1043 MIB module." 1045 MODULE -- this module 1046 Pseudo Wire (PW) Over MPLS February 2006 1047 Management Information Base 1049 MANDATORY-GROUPS { pwMplsGroup, 1050 pwMplsOutboundMainGroup, 1051 pwMplsInboundGroup, 1052 pwMplsMappingGroup 1053 } 1055 GROUP pwMplsOutboundTeGroup 1056 DESCRIPTION "This group MUST be supported if the implementation 1057 allows MPLS TE tunnels to carry PW traffic. 1058 " 1060 OBJECT pwMplsMplsType 1061 MIN-ACCESS read-only 1062 DESCRIPTION "Write access is not required. 1063 Support of pwOnly(2) is not required. At least one 1064 of mplsTe(0) or mplsNonTe(1) MUST be supported if 1065 signaling of PW is supported. 1066 " 1068 OBJECT pwMplsExpBitsMode 1069 MIN-ACCESS read-only 1070 DESCRIPTION "Write access is not required. 1071 Support of specifiedValue(2) and 1072 serviceDependant(3) 1073 is optional. 1074 " 1076 OBJECT pwMplsExpBits 1077 MIN-ACCESS read-only 1078 DESCRIPTION "Write access is not required. 1079 " 1080 OBJECT pwMplsTtl 1081 MIN-ACCESS read-only 1082 DESCRIPTION "Write access is not required. 1083 " 1085 OBJECT pwMplsLocalLdpID 1086 MIN-ACCESS read-only 1087 DESCRIPTION "Write access is not required. 1088 " 1090 OBJECT pwMplsLocalLdpEntityID 1091 MIN-ACCESS read-only 1092 DESCRIPTION "Write access is not required. 1093 " 1095 OBJECT pwMplsStorageType 1096 MIN-ACCESS read-only 1097 DESCRIPTION "Write access is not required. 1098 " 1099 Pseudo Wire (PW) Over MPLS February 2006 1100 Management Information Base 1102 OBJECT pwMplsOutboundLsrXcIndex 1103 MIN-ACCESS read-only 1104 DESCRIPTION "Write access is not required. 1105 A value other than zero MUST be supported if the 1106 implementation support non TE signaling of the 1107 outer tunnel. 1108 " 1110 OBJECT pwMplsOutboundTunnelIndex 1111 MIN-ACCESS read-only 1112 DESCRIPTION "Write access is not required. 1113 " 1115 OBJECT pwMplsOutboundTunnelLclLSR 1116 MIN-ACCESS read-only 1117 DESCRIPTION "Write access is not required. 1118 " 1120 OBJECT pwMplsOutboundTunnelPeerLSR 1121 MIN-ACCESS read-only 1122 DESCRIPTION "Write access is not required. 1123 " 1125 OBJECT pwMplsOutboundIfIndex 1126 MIN-ACCESS read-only 1127 DESCRIPTION "Write access is not required. 1128 A value other than zero MUST be supported if the 1129 implementation supports manually configured PW 1130 without MPLS outer tunnel. 1131 " 1132 ::= { pwMplsCompliances 2 } 1134 -- Units of conformance. 1136 pwMplsGroup OBJECT-GROUP 1137 OBJECTS { 1138 pwMplsMplsType, 1139 pwMplsExpBitsMode, 1140 pwMplsExpBits, 1141 pwMplsTtl, 1142 pwMplsLocalLdpID, 1143 pwMplsLocalLdpEntityID, 1144 pwMplsPeerLdpID, 1145 pwMplsStorageType 1146 } 1148 STATUS current 1149 DESCRIPTION 1150 "Collection of objects needed for PW over MPLS PSN 1151 configuration." 1152 ::= { pwMplsGroups 1 } 1153 Pseudo Wire (PW) Over MPLS February 2006 1154 Management Information Base 1156 pwMplsOutboundMainGroup OBJECT-GROUP 1157 OBJECTS { 1158 pwMplsOutboundLsrXcIndex, 1159 pwMplsOutboundIfIndex, 1160 pwMplsOutboundTunnelTypeInUse 1161 } 1163 STATUS current 1164 DESCRIPTION 1165 "Collection of objects needed for outbound association of 1166 PW and MPLS tunnel." 1167 ::= { pwMplsGroups 2 } 1169 pwMplsOutboundTeGroup OBJECT-GROUP 1170 OBJECTS { 1171 pwMplsOutboundTunnelIndex, 1172 pwMplsOutboundTunnelInstance, 1173 pwMplsOutboundTunnelLclLSR, 1174 pwMplsOutboundTunnelPeerLSR 1175 } 1177 STATUS current 1178 DESCRIPTION 1179 "Collection of objects needed for outbound association of 1180 PW and MPLS TE tunnel." 1181 ::= { pwMplsGroups 3 } 1183 pwMplsInboundGroup OBJECT-GROUP 1184 OBJECTS { 1185 pwMplsInboundXcIndex 1186 } 1188 STATUS current 1189 DESCRIPTION 1190 "Collection of objects needed for inbound PW presentation. 1191 This group MUST be supported if PW signaling through LDP is 1192 used." 1193 ::= { pwMplsGroups 4 } 1195 pwMplsMappingGroup OBJECT-GROUP 1196 OBJECTS { 1197 pwMplsNonTeMappingVcIndex, 1198 pwMplsTeMappingVcIndex 1199 } 1201 STATUS current 1202 DESCRIPTION 1203 "Collection of objects needed for mapping association of 1204 PW and MPLS tunnel." 1205 ::= { pwMplsGroups 5 } 1206 Pseudo Wire (PW) Over MPLS February 2006 1207 Management Information Base 1209 END 1211 7 Security Considerations 1213 It is clear that this MIB module is potentially useful for 1214 monitoring of PW capable PEs. This MIB module can also be used for 1215 configuration of certain objects, and anything that can be 1216 configured can be incorrectly configured, with potentially 1217 disastrous results. 1219 There are a number of management objects defined in this MIB module 1220 with a MAX-ACCESS clause of read-write and/or read-create. Such 1221 objects may be considered sensitive or vulnerable in some network 1222 environments. The support for SET operations in a non-secure 1223 environment without proper protection can have a negative effect on 1224 network operations. These are the tables and objects and their 1225 sensitivity/vulnerability: 1227 o the pwVcMplsTable, pwVcMplsNonTeMappingTable and 1228 pwVcMplsTeMappingTable collectively contain objects to 1229 provision PW over MPLS tunnels. Unauthorized access to 1230 objects in these tables, could result in disruption of 1231 traffic on the network. The use of stronger mechanisms 1232 such as SNMPv3 security should be considered where 1233 possible. Specifically, SNMPv3 VACM and USM MUST be used 1234 with any v3 agent which implements this MIB module. 1235 Administrators should consider whether read access to these 1236 objects should be allowed, since read access may be 1237 undesirable under certain circumstances. 1239 Some of the readable objects in this MIB module "i.e., objects with 1240 a MAX-ACCESS other than not-accessible" may be considered sensitive 1241 or vulnerable in some network environments. It is thus important 1242 to control even GET and/or NOTIFY access to these objects and 1243 possibly to even encrypt the values of these objects when sending 1244 them over the network via SNMP. These are the tables and objects 1245 and their sensitivity/vulnerability: 1247 o the pwVcMplsTable, pwVcMplsNonTeMappingTable, 1248 pwVcMplsTeMappingTable and pwVcMplsOutboundTable 1249 collectively show the PW over MPLS association. 1250 If an Administrator does not want to reveal this 1251 information, then these tables should be 1252 considered sensitive/vulnerable. 1254 SNMP versions prior to SNMPv3 did not include adequate security. 1255 Even if the network itself is secure "for example by using IPSec", 1256 even then, there is no control as to who on the secure network is 1257 Pseudo Wire (PW) Over MPLS February 2006 1258 Management Information Base 1260 allowed to access and GET/SET "read/change/create/delete" the 1261 objects in this MIB module. 1263 It is RECOMMENDED that implementers consider the security features 1264 as provided by the SNMPv3 framework "see [RFC3410], section 8", 1265 including full support for the SNMPv3 cryptographic mechanisms "for 1266 authentication and privacy". 1268 Further, deployment of SNMP versions prior to SNMPv3 is NOT 1269 RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to 1270 enable cryptographic security. It is then a customer/operator 1271 responsibility to ensure that the SNMP entity giving access to an 1272 instance of this MIB module, is properly configured to give access 1273 to the objects only to those principals "users" that have 1274 legitimate rights to indeed GET or SET "change/create/delete" them. 1276 8 IANA considerations 1278 The MIB module in this document uses the following IANA-assigned 1279 OBJECT IDENTIFIER values recorded in the SMI Numbers registry: 1281 Descriptor OBJECT IDENTIFIER value 1282 ---------- ----------------------- 1284 pwMplsStdMIB { transmission XXXX } 1286 Editor's Note (to be removed prior to publication): the IANA is 1287 requested to assign a value for "XXXX" under the 'transmission' 1288 subtree and to record the assignment in the SMI Numbers registry. 1289 When the assignment has been made, the RFC Editor is asked to 1290 replace "XXXX" (here and in the MIB module) with the assigned value 1291 and to remove this note. 1293 9 References 1295 9.1 Normative references 1297 [RFC3985] Bryant, S., and Pate, P., "Pseudo Wire Emulation Edge- 1298 to-Edge (PWE3) Architecture", RFC 3985, March 2005. 1300 [RFC3916] Xio, X., et al, "Requirements for Pseudo-Wire Emulation 1301 Edge-to-Edge (PWE3)", RFC 3916, September 2004. 1303 [PWTC] Nadeau, T., et al, "Definitions for Textual Conventions 1304 and OBJECT-IDENTITIES for Pseudo-Wires Management", 1305 work-in-progress. 1307 [PW-MIB] Zelig, D., et al, "Pseudo Wire (PW) Management 1308 Information Base", work-in-progress. 1310 Pseudo Wire (PW) Over MPLS February 2006 1311 Management Information Base 1313 [LDP] Andersson, L., et al, "LDP specification", RFC 3036, 1314 January 2001. 1316 [BCP14] Bradner, S., "Key words for use in RFCs to Indicate 1317 requirement Levels", BCP 14, RFC 2119, March 1997. 1319 [RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, 1320 J.,Rose, M. and S. Waldbusser, "Structure of Management 1321 Information Version 2 (SMIv2)", STD 58, RFC 2578, April 1322 1999. 1324 [RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, 1325 J., Rose, M. and S. Waldbusser, "Textual Conventions 1326 for SMIv2", STD 58, RFC 2579, April 1999. 1328 [RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, 1329 J., Rose, M. and S. Waldbusser, "Conformance Statements 1330 for SMIv2", STD 58, RFC 2580, April 1999. 1332 [RFC2863] McCloghrie, K., F. Kastenholz, "The Interfaces Group 1333 MIB using SMIv2", RFC 2863, June 2000. 1335 [RFC3031] Rosen, E., Viswanathan, A., and R. Callon, 1336 "Multiprotocol Label Switching Architecture", RFC 3031, 1337 Jan 2001. 1339 [RFC3811] Nadeau, T., Cucchiara, J., "Definitions of Textual 1340 Conventions (TCs) for Multiprotocol Label Switching 1341 (MPLS) Management", RFC 3811, June 2004. 1343 [RFC3812] Srinivasan, C., Viswanathan, A., and Nadeau, T., 1344 "Multiprotocol Label Switching (MPLS) Traffic 1345 Engineering (TE) Management Information Base (MIB)", 1346 RFC 3812, June 2004. 1348 [RFC3813] Srinivasan, C., Viswanathan, A., and Nadeau, T., 1349 "Multiprotocol Label Switching (MPLS) Label Switching 1350 Router (LSR) Management Information Base (MIB)", RFC 1351 3813, June 2004. 1353 9.2 Informative references 1355 [RFC2434] Narten, T. and H. Alvestrand, "Guidelines for Writing 1356 an IANA Considerations Section in RFCs", BCP: 26, RFC 1357 2434, October 1998. 1359 [RFC3410] Case, J., Mundy, R., Partain, D. and B. Stewart, 1360 "Introduction and Applicability Statements for 1361 Pseudo Wire (PW) Over MPLS February 2006 1362 Management Information Base 1364 Internet-Standard Management Framework", RFC 3410, 1365 December 2002. 1367 10 Author's Addresses 1369 David Zelig 1370 Corrigent Systems 1371 126, Yigal Alon st. 1372 Tel Aviv, ISRAEL 1373 Phone: +972-3-6945273 1374 Email: davidz@corrigent.com 1376 Thomas D. Nadeau 1377 Cisco Systems, Inc. 1378 250 Apollo Drive 1379 Chelmsford, MA 01824 1380 Email: tnadeau@cisco.com 1382 Dave Danenberg 1383 Email: dave_danenberg@yahoo.com 1385 Andrew G. Malis 1386 Tellabs, Inc. 1387 2730 Orchard Parkway 1388 San Jose, CA 95134 1389 Email: Andy.Malis@tellabs.com 1391 Sharon Mantin 1392 Corrigent Systems 1393 126, Yigal Alon st. 1394 Tel Aviv, ISRAEL 1395 Phone: +972-3-6948615 1396 Email: sharonma@corrigent.com m 1397 Pseudo Wire (PW) Over MPLS February 2006 1398 Management Information Base 1400 11 Full Copyright Statement 1402 Copyright (C) The Internet Society (2006). This document is 1403 subject to the rights, licenses and restrictions contained in BCP 1404 78, and except as set forth therein, the authors retain all their 1405 rights. 1407 This document and the information contained herein are provided on 1408 an "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE 1409 REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND 1410 THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, 1411 EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT 1412 THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR 1413 ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A 1414 PARTICULAR PURPOSE. 1416 12 Intellectual Property Notice 1418 The IETF takes no position regarding the validity or scope of any 1419 Intellectual Property Rights or other rights that might be claimed 1420 to pertain to the implementation or use of the technology described 1421 in this document or the extent to which any license under such 1422 rights might or might not be available; nor does it represent that 1423 it has made any independent effort to identify any such rights. 1424 Information on the procedures with respect to rights in RFC 1425 documents can be found in BCP 78 and BCP 79. 1427 Copies of IPR disclosures made to the IETF Secretariat and any 1428 assurances of licenses to be made available, or the result of an 1429 attempt made to obtain a general license or permission for the use 1430 of such proprietary rights by implementers or users of this 1431 specification can be obtained from the IETF on-line IPR repository 1432 at http://www.ietf.org/ipr. 1434 The IETF invites any interested party to bring to its attention any 1435 copyrights, patents or patent applications, or other proprietary 1436 rights that may cover technology that may be required to implement 1437 this standard. Please address the information to the IETF at 1438 ietf-ipr@ietf.org.