idnits 2.17.1 draft-ietf-pwe3-pw-mpls-mib-07.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 1324. -- Found old boilerplate from RFC 3979, Section 5, paragraph 1 on line 1295. -- Found old boilerplate from RFC 3979, Section 5, paragraph 2 on line 1302. -- Found old boilerplate from RFC 3979, Section 5, paragraph 3 on line 1308. ** 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 : ---------------------------------------------------------------------------- ** There is 1 instance of too long lines in the document, the longest one being 3 characters in excess of 72. ** The document seems to lack a both a reference to RFC 2119 and the recommended RFC 2119 boilerplate, even if it appears to use RFC 2119 keywords. RFC 2119 keyword, line 431: '... in the LDP ID MUST be always both z...' RFC 2119 keyword, line 537: '... bit is set, and MUST return a value o...' RFC 2119 keyword, line 552: '... bit is set, and MUST return a value o...' RFC 2119 keyword, line 566: '... bit is set, and MUST return a value o...' RFC 2119 keyword, line 580: '... bit is set, and MUST return a value o...' (18 more instances...) Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the RFC 3978 Section 5.4 Copyright Line does not match the current year == Line 189 has weird spacing: '...N |PWin inSeg...' == Line 193 has weird spacing: '...| inSeg outSe...' -- 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 (July 2005) is 6860 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: 'RFC3810' is mentioned on line 256, but not defined == Missing Reference: 'RFC2434' is mentioned on line 1331, but not defined ** Obsolete undefined reference: RFC 2434 (Obsoleted by RFC 5226) == Unused Reference: 'RFC3811' is defined on line 1222, but no explicit reference was found in the text ** Downref: Normative reference to an Informational RFC: RFC 2985 (ref. 'RFC3985') -- Possible downref: Non-RFC (?) normative reference: ref. 'PWTC' -- Possible downref: Non-RFC (?) normative reference: ref. 'PWMIB' ** Obsolete normative reference: RFC 3036 (Obsoleted by RFC 5036) Summary: 8 errors (**), 0 flaws (~~), 7 warnings (==), 9 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 Internet Draft David Zelig, Ed. 2 Expires: February 2006 Corrigent Systems 4 Thomas D. Nadeau, Ed. 5 Cisco Systems, Inc. 7 July 2005 9 Pseudo Wire (PW) over MPLS PSN Management Information Base 11 draft-ietf-pwe3-pw-mpls-mib-07.txt 13 Status of this Memo 15 By submitting this Internet-Draft, each author represents that 16 any applicable patent or other IPR claims of which he or she is 17 aware have been or will be disclosed, and any of which he or she 18 becomes aware will be disclosed, in accordance with Section 6 of 19 BCP 79. 21 Internet-Drafts are working documents of the Internet Engineering 22 Task Force (IETF), its areas, and its working groups. Note that other 23 groups may also distribute working documents as Internet-Drafts. 25 Internet-Drafts are draft documents valid for a maximum of six months 26 and may be updated, replaced, or obsoleted by other documents at any 27 time. It is inappropriate to use Internet-Drafts as reference 28 material or to cite them other than as "work in progress." 30 The list of current Internet-Drafts can be accessed at 31 http://www.ietf.org/1id-abstracts.html 33 The list of Internet-Draft Shadow Directories can be accessed at 34 http://www.ietf.org/shadow.html. 36 Abstract 38 This memo defines an experimental portion of the Management 39 Information Base for use with network management protocols in 40 the Internet community. In particular, it describes managed 41 objects for modeling of Pseudo Wires over an MPLS transport 42 network. 44 Table of Contents 46 Abstract.......................................................1 47 1 Introduction...................................................2 48 2 Terminology....................................................3 49 3 The Internet-Standard Management Framework.....................3 50 4 PWE3 MIB modules Architecture ................................4 51 4.1 PW-MPLS-STD-MIB Module Usage .................................4 52 5 PWE3 MPLS MIB Module Definitions..............................7 53 6 Security Considerations......................................26 54 7 References...................................................27 55 7.1 Normative references.........................................27 56 7.2 Informative references.......................................29 57 8 Editors' Addresses...........................................29 58 9 Contributor's Addresses......................................29 59 10 Intellectual Property Notice.................................30 60 11 Full Copyright Statement.....................................29 61 12 IANA considerations..........................................27 63 1. Introduction 65 This memo defines a portion of the Management Information Base 66 (MIB) for use with network management protocols in the Internet 67 community. In particular, it defines a MIB module which can be 68 used to manage pseudo wire (PW) services transmitted over 69 different types of MPLS packet Switched Network (PSN) 70 tunnels. 72 The general PW-STD-MIB module [PWMIB] defines the global parameters 73 for PWs, regardless of underlying PSN or emulated service type. 74 This document describes the MIB objects that define pseudo wire 75 association to the MPLS PSN, in a way that is not specific to the 76 carried service. 78 Together, [RFC3814] and [RFC3813], describe the modeling of an MPLS 79 Tunnel, and a Tunnel's underlying cross-connects. The defined MIB 80 support MPLS-TE as a PSN, Non-TE MPLS PSN (an outer tunnel created 81 by The Label Distribution Protocol (LDP) [RFC3036] or manually), 82 and MPLS PW label only (no outer tunnel). 84 2. Terminology 86 This document adopts the definitions, acronyms and mechanisms 87 described in [RFC3985]. Unless otherwise stated, the mechanisms of 88 [RFC3985] apply and will not be re-described here. 90 The terms "Outbound" and "Inbound" in this MIB module are based on 91 the common practice in the MPLS standards, i.e. "outbound" are 92 toward the PSN. However, where these terms are used in an object 93 name, the object description clarifies the exact packet direction 94 to prevent confusion with these terms in other documents. 96 "PSN Tunnel" is a general term indicating a virtual connection 97 between the two PWE3 edge devices. Each tunnel may potentially 98 carry multiple PWs inside. In the scope of this document, it is 99 MPLS tunnel. 101 This document uses terminology from the document describing the 102 MPLS architecture [RFC3031] for MPLS PSN. A Label Switched Path 103 (LSP) is modeled as described in [RFC3813] and [RFC3814] via 104 a series of cross-connects through 1 or more Label switching 105 routers (LSR). 107 In MPLS PSN, a PW connection typically uses a PW Label within a 108 Tunnel Label [PWCNTRL]. Multiple pseudo wires each with a unique PW 109 Label can share the same Tunnel. For PW transport over MPLS, the 110 Tunnel Label is known as the "outer" Label, while the PW Label is 111 known as the "inner" Label. An exception to this is with adjacent 112 LSRs or the use of PHP. In this case, there is an option for PWs to 113 connect directly without an outer Label. 115 3. The Internet-Standard Management Framework 117 For a detailed overview of the documents that describe the current 118 Internet-Standard Management Framework, please refer to section 7 of 119 RFC 3410 [RFC3410]. 121 Managed objects are accessed via a virtual information store, termed 122 the Management Information Base or MIB. MIB objects are generally 123 accessed through the Simple Network Management Protocol (SNMP). 124 Objects in the MIB are defined using the mechanisms defined in the 125 Structure of Management Information (SMI). This memo specifies a MIB 126 module that is compliant to the SMIv2, which is described in STD 58, 127 RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580 128 [RFC2580]. 130 4. PWE3 MIB modules Architecture 132 The MIB structure for defining a PW service is composed from three 133 types of MIB modules. 135 The first type is the PW MIB module, which configures general 136 parameters of the PW that are common to all types of emulated 137 services and PSN types. 139 The second type of modules is PSN type specific module. There is a 140 different module for each type of PSN. These modules associate the 141 PW with one or more "tunnels" that carry the service over the PSN. 142 These modules are defined in other documents. 144 The third type of modules is service-specific module, which is 145 emulated signal type dependent. These modules are defined in other 146 documents. 148 [PWTC] defines some of the object types used in these modules. 150 4.1 PW-MPLS-STD-MIB Module Usage 152 - The PW table (pwTable) in [PWMIB] is used for all PW types 153 (ATM, FR, Ethernet, SONET, etc.). This table contains high level 154 generic parameters related to the PW creation. The operator or the 155 agent for each PW service creates a row. 157 - If the PSN type in pwTable is MPLS, the agent creates a row in 158 the MPLS specific parameters table (pwMplsVcTable) in this module, 160 which contain MPLS specific parameters such as EXP bits handling 161 and outer tunnel configuration. 163 - The operator configures the association to the desired MPLS 164 tunnel (require for MPLS TE tunnels or manually configured PWs) 165 through the pwMplsTeOutbaoundTable. For LDP based outer tunnel, 166 there is no need for manula configuration since there is only a 167 single tunnel toward the peer. 169 - The agent creates rows in the MPLS mapping table in order to 170 allow quick retrieval of information based on the tunnel indexes. 172 The relation to the MPLS network is by configuration of the edge 173 LSR only - that is to say, the LSR providing the PW function. Since 174 Tunnels are uni-directional, a pair of tunnels must exist (one for 175 inbound, one for outbound). The following graphic depicts a VC that 176 originates and terminates at LSR-M. It uses LSPs A and B formed by 177 Tunnels Ax and Bx continuing through LSR-N to LSR-P. The 178 concatenations of Tunnels create the LSPs. Note: 'X' denotes a 179 Tunnel's cross-connect. 181 LSP-A 182 <- - - - - - - - - - - - - - - - - - - - - - - - - - - - 184 +---- (edge) LSR-M ---+ +--------- LSR-N ---------+ + LSR-P 185 |---+ | | | | 186 | | Tunnel | | Tunnel | | 187 + | A1 (M<-N) +----+ +----+ A2 (M<-P) +----+ +----+ 188 | | <------| | | |<--------------| | | | 189 <-->| N |PWin inSeg |MPLS| |MPLS| outSeg inSeg |MPLS| |MPLS| 190 N S | | <---X<-----| IF | | IF |<------X<------| IF | | IF | 191 A E | S | | |<-->| | | |<-->| | | 192 T R | | --->X----->| | | |------>X------>| | | | 193 I V | P |PWout outSeg| | | | inSeg outSeg | | | | 194 V I | | ------>| | | |-------------->| | | | 195 E C + | Tunnel +----+ +----+ Tunnel +----+ +----+ 196 E |---+ B1 (M->N) | | B2 (M->P) | | 197 | | | | | 198 +---------------------+ +-------------------------+ +----- 199 - - - - - - - - - - - - - - - - - - - - - - - - - - - -> 200 LSP-B 202 The PW-MPLS-MIB supports three options for MPLS network: 204 - In the MPLS-TE case, Tunnel A1 and B1 are created via the MPLS-TE 205 MIB [RFC3814]. The tunnels are associated to the PW by the (4) 206 indexes that uniquely identify the Tunnel at the TE-MIB. 208 - In the Non TE case, Tunnel A1 and B1 are either manually 209 configured or set up with LDP. The tunnels are associated to the PW 210 by the XC index in the MPLS-LSR-MIB [RFC3813]. 212 - In the PW label only case, there is no outer tunnel on top of the 213 PW label. This case is useful in case of adjacent PEs in manual 214 configuration mode. Note that when LSR-N acts as PHP for the outer 215 tunnel label, there are still entries for the outer tunnel in the 216 relevant MPLS MIB modules. 218 A combination of MPLS-TE outer tunnel(s) and LDP outer tunnel for 219 the same PW is allowed through the pwMplsOutboundTunnel. The 220 current tunnel that is used to forward traffic is indicated in the 221 object pwMplsOutboundTunnelTypeInUse. 223 The PW MPLS MIB module reports through the inbound table the XC 224 entry in the LDP-STD_MIB of the PW that were signaled through LDP. 226 This MIB module assumes that a single PW can be associated to one 227 MPLS-TE tunnel at a time. This tunnel may be composed of multiple 228 instances (i.e. LSP), each represented by a separate instance 229 index. The current active LSP is reported through this MIB module. 231 It is worth noting that inbound (tunnel originated in the remote 232 PE) mapping is nor configured nor reported through the PW MPLS MIB 233 module since the local PE does not know the inbound association 234 between specific PW and MPLS tunnels. 236 5. PWE3 MPLS MIB Module Definitions 238 PW-MPLS-STD-MIB DEFINITIONS ::= BEGIN 240 IMPORTS 241 MODULE-IDENTITY, OBJECT-TYPE, 242 Unsigned32 243 FROM SNMPv2-SMI -- [RFC2578] 245 MODULE-COMPLIANCE, OBJECT-GROUP 246 FROM SNMPv2-CONF -- [RFC2580] 248 StorageType 249 FROM SNMPv2-TC -- [RFC2579] 251 InterfaceIndexOrZero 252 FROM IF-MIB -- [RFC2863] 254 MplsTunnelIndex, MplsTunnelInstanceIndex, 255 MplsLdpIdentifier, MplsLsrIdentifier 256 FROM MPLS-TC-STD-MIB -- [RFC3810] 258 MplsIndexType 259 FROM MPLS-LSR-STD-MIB -- [RFC3813] 261 PwIndexType, pwMIB 262 FROM PW-TC-STD-MIB 264 pwIndex 265 FROM PW-STD-MIB 267 ; 269 pwMplsStdMIB MODULE-IDENTITY 270 LAST-UPDATED "200507041200Z" -- 4 July 2005 12:00:00 GMT 271 ORGANIZATION "Pseudo Wire Edge to Edge Emulation (PWE3) Working 272 Group." 273 CONTACT-INFO 274 " 275 David Zelig, Editor 276 E-mail: davidz@corrigent.com 278 Thomas D. Nadeau, Editor 279 Email: tnadeau@cisco.com 281 The PWE3 Working Group (email distribution pwe3@ietf.org, 282 http://www.ietf.org/html.charters/pwe3-charter.html) 283 " 284 DESCRIPTION 285 "This MIB module complements the PW MIB module for PW 286 operation over MPLS. 288 Copyright (C) The Internet Society (2005). This version 289 of this MIB module is part of RFC yyyy; see the RFC 290 itself for full legal notices. 291 -- RFC Ed.: replace yyyy with actual RFC number & remove this note 292 " 293 -- Revision history. 294 REVISION 295 "200507041200Z" -- 4 July 2005 12:00:00 GMT 296 DESCRIPTION 297 " First published as RFCWXYZ. " 298 -- RFC Editor: Please replace 299 -- WXYZ with correct # 301 ::= { pwMIB 4 } -- RFC Editor: To be assigned by IANA 302 -- the value 4 is requested for this 303 -- specific Module. Please replace XXX 304 -- with the assigned value. 306 -- Top-level components of this MIB. 308 -- Notifications 309 pwMplsNotifications OBJECT IDENTIFIER 310 ::= { pwMplsStdMIB 0 } 312 -- Tables, Scalars 313 pwMplsObjects OBJECT IDENTIFIER 314 ::= { pwMplsStdMIB 1 } 315 -- Conformance 316 pwMplsConformance OBJECT IDENTIFIER 317 ::= { pwMplsStdMIB 2 } 319 -- PW MPLS table 321 pwMplsTable OBJECT-TYPE 322 SYNTAX SEQUENCE OF PwMplsEntry 323 MAX-ACCESS not-accessible 324 STATUS current 325 DESCRIPTION 326 "This table controls MPLS specific parameters when the PW is 327 going to be carried over MPLS PSN." 328 ::= { pwMplsObjects 1 } 330 pwMplsEntry OBJECT-TYPE 331 SYNTAX PwMplsEntry 332 MAX-ACCESS not-accessible 333 STATUS current 334 DESCRIPTION 335 "A row in this table represents parameters specific to MPLS 336 PSN for a pseudo wire (PW). The row is created 337 automatically by the local agent if the pwPsnType is 338 MPLS. It is indexed by pwIndex, which uniquely 339 identifying a singular PW. 340 " 341 INDEX { pwIndex } 343 ::= { pwMplsTable 1 } 345 PwMplsEntry ::= SEQUENCE { 346 pwMplsMplsType BITS, 347 pwMplsExpBitsMode INTEGER, 348 pwMplsExpBits Unsigned32, 349 pwMplsTtl Unsigned32, 350 pwMplsLocalLdpID MplsLdpIdentifier, 351 pwMplsLocalLdpEntityID MplsLsrIdentifier, 352 pwMplsPeerLdpID MplsLdpIdentifier, 353 pwMplsStorageType StorageType 354 } 356 pwMplsMplsType OBJECT-TYPE 357 SYNTAX BITS { 358 mplsTe (0), 359 mplsNonTe (1), 360 vcOnly (2) 361 } 362 MAX-ACCESS read-write 363 STATUS current 364 DESCRIPTION 365 "Set by the operator to indicate the outer tunnel types, if 366 exists. mplsTe(0) is used if the outer tunnel was set-up 367 by MPLS-TE, and mplsNonTe(1) is used the outer tunnel was 368 set up by LDP or manually. Combination of mplsTe(0) and 369 mplsNonTe(1) may exist together. 370 vcOnly(2) is used if there is no outer tunnel label, i.e. 371 in static provisioning without MPLS tunnel. vcOnly(2) 372 cannot be combined with mplsNonTe(1) or mplsTe(0)." 373 DEFVAL { { mplsNonTe } } 374 ::= { pwMplsEntry 1 } 376 pwMplsExpBitsMode OBJECT-TYPE 377 SYNTAX INTEGER { 378 outerTunnel (1), 379 specifiedValue (2), 380 serviceDependant (3) 381 } 383 MAX-ACCESS read-write 384 STATUS current 385 DESCRIPTION 386 "Set by the operator to indicate the way the PW shim label 387 EXP bits are to be determined. The value of outerTunnel(1) 388 is used where there is an outer tunnel - pwMplsMplsType 389 is mplsTe(0) or mplsNonTe(1). Note that in this case there 390 is no need to mark the PW label with the EXP bits since the 391 PW label is not visible to the intermediate nodes. 392 If there is no outer tunnel, specifiedValue(2) indicates 393 that the value is specified by pwMplsExpBits, and 394 serviceDependant(3) indicates that the EXP bits are setup 395 based on a rule specified in the emulated service specific 396 tables, for example when the EXP bits are a function of 397 802.1p marking for Ethernet emulated service." 399 DEFVAL { outerTunnel } 400 ::= { pwMplsEntry 2 } 402 pwMplsExpBits OBJECT-TYPE 403 SYNTAX Unsigned32 (0..7) 404 MAX-ACCESS read-write 405 STATUS current 406 DESCRIPTION 407 "Set by the operator to indicate the MPLS EXP bits to be 408 used on the PW shim label if pwMplsExpBitsMode is 409 specifiedValue(2), zero otherwise." 410 DEFVAL { 0 } 411 ::= { pwMplsEntry 3 } 413 pwMplsTtl OBJECT-TYPE 414 SYNTAX Unsigned32 (0..255) 415 MAX-ACCESS read-write 416 STATUS current 417 DESCRIPTION 418 "Set by the operator to indicate the PW TTL value to be 419 used on the PW shim label." 420 DEFVAL { 2 } 421 ::= { pwMplsEntry 4 } 423 pwMplsLocalLdpID OBJECT-TYPE 424 SYNTAX MplsLdpIdentifier 425 MAX-ACCESS read-write 426 STATUS current 427 DESCRIPTION 428 "The local LDP identifier of the LDP entity creating 429 this PW in the local node. As the PW labels are always 430 set from the per platform label space, the last two octets 431 in the LDP ID MUST be always both zeros." 432 REFERENCE 433 "'LDP specifications', RFC 3036 section 2.2.2." 434 ::= { pwMplsEntry 5 } 436 pwMplsLocalLdpEntityID OBJECT-TYPE 437 SYNTAX MplsLsrIdentifier 438 MAX-ACCESS read-write 439 STATUS current 440 DESCRIPTION 441 "The local node LDP Entity ID of the LDP entity creating 442 this PW. Should return the value of all zeros if not 443 used." 444 ::= { pwMplsEntry 6 } 446 pwMplsPeerLdpID OBJECT-TYPE 447 SYNTAX MplsLdpIdentifier 448 MAX-ACCESS read-only 449 STATUS current 450 DESCRIPTION 451 "The peer LDP identifier as identified from the LDP 452 session. Should return the value of zero if not applicable 453 or not known yet." 454 ::= { pwMplsEntry 7 } 456 pwMplsStorageType OBJECT-TYPE 457 SYNTAX StorageType 458 MAX-ACCESS read-write 459 STATUS current 460 DESCRIPTION 461 "This variable indicates the storage type for this row." 462 ::= { pwMplsEntry 8 } 464 -- End of PW MPLS table 466 -- Pseudo Wire MPLS Outbound Tunnel table 468 pwMplsOutboundTable OBJECT-TYPE 469 SYNTAX SEQUENCE OF PwMplsOutboundEntry 470 MAX-ACCESS not-accessible 471 STATUS current 472 DESCRIPTION 473 "This table reports and configure the current outbound MPLS 474 tunnels (i.e. toward the PSN) or the physical interface in 475 case of PW label only that carry the PW traffic. It also 476 reports the current outer tunnel and LSP which forward the 477 PW traffic." 478 ::= { pwMplsObjects 2 } 480 pwMplsOutboundEntry OBJECT-TYPE 481 SYNTAX PwMplsOutboundEntry 482 MAX-ACCESS not-accessible 483 STATUS current 484 DESCRIPTION 485 "A row in this table configured the outer tunnel used for 486 carrying the PW traffic toward the PSN. 487 In the case of PW label only, it configures the interface 488 that will carry the PW traffic. 490 An entry in this table augments the pwMplsEntry, and is 491 created automatically when the corresponding row has been 492 created by the agent in the pwMplsEntry. 494 This table points to the appropriate MPLS MIB module. 495 In the MPLS-TE case, the 3 variables relevant to the 496 indexing of a TE tunnel head-end are used as in 497 MPLS-TE-STD-MIB are to be configured, and the tunnel 498 instance indicates the LSP that is currently in use for 499 forwarding the traffic. 501 In case of signaled Non-TE MPLS (an outer tunnel label 502 assigned by LDP) the table points to the XC entry in the 503 LSR-STD-MIB. If the Non-TE MPLS tunnel is manually 504 configured, the operator configure the XC pointer to this 505 tunnel. 507 In case of PW label only (no outer tunnel) the ifIndex of 508 the port to carry the PW is configured here. 510 It is possible to associate a PW to one TE tunnel head-end 511 and a non-TE tunnel together. An indication in this table 512 will report the currently active one, In addition, in the 513 TE case the table reports the active tunnel instance 514 (i.e. the specific LSP in use). 515 " 517 AUGMENTS { pwMplsEntry } 519 ::= { pwMplsOutboundTable 1 } 521 PwMplsOutboundEntry ::= SEQUENCE { 522 pwMplsOutboundLsrXcIndex MplsIndexType, 523 pwMplsOutboundTunnelIndex MplsTunnelIndex, 524 pwMplsOutboundTunnelInstance MplsTunnelInstanceIndex, 525 pwMplsOutboundTunnelLclLSR MplsLsrIdentifier, 526 pwMplsOutboundTunnelPeerLSR MplsLsrIdentifier, 527 pwMplsOutboundIfIndex InterfaceIndexOrZero, 528 pwMplsOutboundTunnelTypeInUse INTEGER 529 } 531 pwMplsOutboundLsrXcIndex OBJECT-TYPE 532 SYNTAX MplsIndexType 533 MAX-ACCESS read-write 534 STATUS current 535 DESCRIPTION 536 "This object is applicable if pwMplsMplsType mplsNonTe(1) 537 bit is set, and MUST return a value of zero otherwise. 538 If the outer tunnel is signaled, the object is read-only 539 and indicate the XC index in the MPLS-LSR-STD-MIB of the 540 outer tunnel toward the peer. Otherwise (tunnel is set-up 541 manually) the operator define the XC index of the manually 542 created outer tunnel through this object. 543 " 544 ::= { pwMplsOutboundEntry 1 } 546 pwMplsOutboundTunnelIndex OBJECT-TYPE 547 SYNTAX MplsTunnelIndex 548 MAX-ACCESS read-write 549 STATUS current 550 DESCRIPTION 551 "This object is applicable if pwMplsMplsType mplsTe(0) 552 bit is set, and MUST return a value of zero otherwise. 553 It is Part of set of indexes for outbound tunnel. 554 The operator set this object to represent the desired 555 tunnel head-end toward the peer for carrying the PW 556 traffic. 557 " 558 ::= { pwMplsOutboundEntry 2 } 560 pwMplsOutboundTunnelInstance OBJECT-TYPE 561 SYNTAX MplsTunnelInstanceIndex 562 MAX-ACCESS read-only 563 STATUS current 564 DESCRIPTION 565 "This object is applicable if pwMplsMplsType mplsTe(0) 566 bit is set, and MUST return a value of zero otherwise. 567 It indicates the actual tunnel instance that is currently 568 active and carrying the PW traffic - it should return the 569 value of zero until if the information from the MPLS-TE 570 application is not yet known. 571 " 572 ::= { pwMplsOutboundEntry 3 } 574 pwMplsOutboundTunnelLclLSR OBJECT-TYPE 575 SYNTAX MplsLsrIdentifier 576 MAX-ACCESS read-write 577 STATUS current 578 DESCRIPTION 579 "This object is applicable if pwMplsMplsType mplsTe(0) 580 bit is set, and MUST return a value of all zeros otherwise. 581 It is part of set of indexes for outbound tunnel. 582 The operator set this object to represent the desired 583 tunnel head-end toward the peer for carrying the PW 584 traffic. 585 " 586 ::= { pwMplsOutboundEntry 4 } 588 pwMplsOutboundTunnelPeerLSR OBJECT-TYPE 589 SYNTAX MplsLsrIdentifier 590 MAX-ACCESS read-write 591 STATUS current 592 DESCRIPTION 593 "This object is applicable if pwMplsMplsType mplsTe(0) 594 bit is set, and MUST return a value of zero otherwise. 595 It is part of set of indexes for outbound tunnel. It is 596 typically equal to pwPeerAddr. 597 " 598 ::= { pwMplsOutboundEntry 5 } 600 pwMplsOutboundIfIndex OBJECT-TYPE 601 SYNTAX InterfaceIndexOrZero 602 MAX-ACCESS read-write 603 STATUS current 604 DESCRIPTION 605 "This object is applicable if pwMplsMplsType mplsTe(0) 606 bit is set, and MUST return a value of zero otherwise. 607 The operator configure the ifIndex of the outbound port 608 in this case. 609 " 610 ::= { pwMplsOutboundEntry 6 } 612 pwMplsOutboundTunnelTypeInUse OBJECT-TYPE 613 SYNTAX INTEGER { 614 notYetKnown (1), 615 mplsTe (2), 616 mplsNonTe (3), 617 vcOnly (4) 618 } 619 MAX-ACCESS read-only 620 STATUS current 621 DESCRIPTION 622 "This object indicates the current tunnel that is carrying 623 the PW traffic. 624 The value of notYetKnown(1) should be used if the agent is 625 currently unable to determine which tunnel or interface is 626 carrying the PW, for example because both tunnels are in 627 operational status down. 628 " 629 ::= { pwMplsOutboundEntry 7 } 631 -- End of PW MPLS Outbound Tunnel table 633 -- PW MPLS inbound table 635 pwMplsInboundTable OBJECT-TYPE 636 SYNTAX SEQUENCE OF PwMplsInboundEntry 637 MAX-ACCESS not-accessible 638 STATUS current 639 DESCRIPTION 640 "This table indicates the PW LDP XC entry in the 641 MPLS-LSR-STD-MIB for signaled PWs. 642 " 643 ::= { pwMplsObjects 3 } 645 pwMplsInboundEntry OBJECT-TYPE 646 SYNTAX PwMplsInboundEntry 647 MAX-ACCESS not-accessible 648 STATUS current 649 DESCRIPTION 650 "A row in this table is created by the agent 651 for each signaled PW, and shows the XC index related to 652 the PW signaling in the inbound direction in the 653 MPLS-LSR-STD-MIB that controls and display the information 654 for all the LDP signaling processes in the local node. 655 " 657 INDEX { pwIndex } 659 ::= { pwMplsInboundTable 1 } 661 PwMplsInboundEntry ::= SEQUENCE { 662 pwMplsInboundXcIndex MplsIndexType 663 } 665 pwMplsInboundXcIndex OBJECT-TYPE 666 SYNTAX MplsIndexType 667 MAX-ACCESS read-only 668 STATUS current 669 DESCRIPTION 670 "The XC index representing this PW in the inbound 671 direction. Should return the value of zero if the 672 information is not yet known." 673 ::= { pwMplsInboundEntry 1 } 675 -- End of PW MPLS inbound table 677 -- PW to Non-TE mapping Table. 679 pwMplsNonTeMappingTable OBJECT-TYPE 680 SYNTAX SEQUENCE OF PwMplsNonTeMappingEntry 681 MAX-ACCESS not-accessible 682 STATUS current 683 DESCRIPTION 684 "This table indicates outbound Tunnel to a PW in non-TE 685 applications, maps the PW to it's (inbound) XC entry, and 686 indicates the PW to physical interface mapping for a PW 687 label to physical interface a PW label is in use without 688 outer tunnel. 689 " 690 ::= { pwMplsObjects 4 } 692 pwMplsNonTeMappingEntry OBJECT-TYPE 693 SYNTAX PwMplsNonTeMappingEntry 694 MAX-ACCESS not-accessible 695 STATUS current 696 DESCRIPTION 697 "A row in this table displays the association 698 between the PW and 699 - it's non-TE MPLS outbound outer Tunnel or, 700 - it's XC entry in the MPLS-LSR-STD-MIB, 701 - it's physical interface if there is no outer tunnel 702 (PW label only) and manual configuration. 704 Rows are created in this table by the by the 705 agent depending on the setting of pwMplsMplsType: 707 - If pwMplsMplsType mplsNonTe(1) bit is set, the agent 708 creates a row for the outbound direction 709 (pwMplsNonTeMappingDirection set to psnBound(1)). 710 The pwMplsNonTeMappingXcIndex holds the XC index in the 711 MPLS-LSR-STD-MIB of the PSN bound outer tunnel. 712 pwMplsNonTeMappingIfIndex MUST be zero for this row. 714 - If pwMplsMplsType vcOnly(2) bit is set, the agent 715 creates a row for the outbound direction 716 (pwMplsNonTeMappingDirection set to psnBound(1)). 717 The pwMplsNonTeMappingIfIndex holds the ifIndex of the 718 physical port this PW will use in the outbound direction. 719 pwMplsNonTeMappingXcIndex MUST be zero for this row. 721 - If the PW has been set-up by signaling protocol (i.e. 722 pwOwner equal pwIdFecSignaling(2) or 723 genFecSignaling(3)), the agent creates a row for the 724 inbound direction (pwMplsNonTeMappingDirection set to 725 fromPsn(2)). 726 The pwMplsNonTeMappingXcIndex holds the XC index in the 727 MPLS-LSR-STD-MIB of the PW LDP generated XC entry. 728 pwMplsNonTeMappingIfIndex MUST be zero for this row. 730 An application can use this table to quickly retrieve the 731 PW carried over specific non-TE MPLS outer tunnel or 732 physical interface. 733 " 735 INDEX { pwMplsNonTeMappingDirection, 736 pwMplsNonTeMappingXcIndex, 737 pwMplsNonTeMappingIfIndex, 738 pwMplsNonTeMappingVcIndex } 740 ::= { pwMplsNonTeMappingTable 1 } 742 PwMplsNonTeMappingEntry ::= SEQUENCE { 743 pwMplsNonTeMappingDirection INTEGER, 744 pwMplsNonTeMappingXcIndex MplsIndexType, 745 pwMplsNonTeMappingIfIndex InterfaceIndexOrZero, 746 pwMplsNonTeMappingVcIndex PwIndexType 747 } 749 pwMplsNonTeMappingDirection OBJECT-TYPE 750 SYNTAX INTEGER { 751 psnBound (1), 752 fromPsn (2) 753 } 754 MAX-ACCESS not-accessible 755 STATUS current 756 DESCRIPTION 757 "Index for the conceptual XC row identifying Tunnel to PW 758 mappings, indicating the direction of packet flow the entry 759 is related too. 760 psnBound(1) indicates that the entry is related to 761 packets toward the PSN. 762 fromPsn(2) indicates that the entry is related to 763 packets coming from the PSN. 764 " 765 ::= { pwMplsNonTeMappingEntry 1 } 767 pwMplsNonTeMappingXcIndex OBJECT-TYPE 768 SYNTAX MplsIndexType 769 MAX-ACCESS not-accessible 770 STATUS current 771 DESCRIPTION 772 "See the description clause of pwMplsNonTeMappingEntry for 773 the usage guidelines of this object." 774 ::= { pwMplsNonTeMappingEntry 2 } 776 pwMplsNonTeMappingIfIndex OBJECT-TYPE 777 SYNTAX InterfaceIndexOrZero 778 MAX-ACCESS not-accessible 779 STATUS current 780 DESCRIPTION 781 "See the description clause of pwMplsNonTeMappingEntry for 782 the usage guidelines of this object." 783 ::= { pwMplsNonTeMappingEntry 3 } 785 pwMplsNonTeMappingVcIndex OBJECT-TYPE 786 SYNTAX PwIndexType 787 MAX-ACCESS read-only 788 STATUS current 789 DESCRIPTION 790 "The value that represent the PW in the pwTable." 791 ::= { pwMplsNonTeMappingEntry 4 } 793 -- End of PW to Non-TE mapping Table. 795 -- PW to TE MPLS tunnels mapping Table. 797 pwMplsTeMappingTable OBJECT-TYPE 798 SYNTAX SEQUENCE OF PwMplsTeMappingEntry 799 MAX-ACCESS not-accessible 800 STATUS current 801 DESCRIPTION 802 "This table enable the retrieval of a PW association to the 803 outbound MPLS tunnel for MPLS-TE applications." 804 ::= { pwMplsObjects 5 } 806 pwMplsTeMappingEntry OBJECT-TYPE 807 SYNTAX PwMplsTeMappingEntry 808 MAX-ACCESS not-accessible 809 STATUS current 810 DESCRIPTION 811 "A row in this table represents the association 812 between a PW and it's MPLS-TE outer (head-end) Tunnel. 814 An application can use this table to quickly retrieve the 815 list of the PWs that are configured on a specific MPLS TE 816 outer tunnel. 818 The pwMplsTeMappingTunnelInstance reports the actual 819 LSP out of the tunnel head-end that is currently 820 forwarding the traffic. 822 The table in indexed by the head-end indexes of a TE 823 tunnel and the PW index. 824 " 826 INDEX { pwMplsTeMappingTunnelIndex, 827 pwMplsTeMappingTunnelInstance, 828 pwMplsTeMappingTunnelPeerLsrID, 829 pwMplsTeMappingTunnelLocalLsrID, 830 pwMplsTeMappingVcIndex } 832 ::= { pwMplsTeMappingTable 1 } 834 PwMplsTeMappingEntry ::= SEQUENCE { 835 pwMplsTeMappingTunnelIndex MplsTunnelIndex, 836 pwMplsTeMappingTunnelInstance MplsTunnelInstanceIndex, 837 pwMplsTeMappingTunnelPeerLsrID MplsLsrIdentifier, 838 pwMplsTeMappingTunnelLocalLsrID MplsLsrIdentifier, 839 pwMplsTeMappingVcIndex PwIndexType 840 } 842 pwMplsTeMappingTunnelIndex OBJECT-TYPE 843 SYNTAX MplsTunnelIndex 844 MAX-ACCESS not-accessible 845 STATUS current 846 DESCRIPTION 847 "Primary index for the conceptual row identifying the 848 MPLS-TE tunnel that is carrying the PW traffic." 849 ::= { pwMplsTeMappingEntry 1 } 851 pwMplsTeMappingTunnelInstance OBJECT-TYPE 852 SYNTAX MplsTunnelInstanceIndex 853 MAX-ACCESS not-accessible 854 STATUS current 855 DESCRIPTION 856 "This object identify the MPLS-TE LSP that is carrying the 857 PW traffic. Should return the value of zero if the 858 information of the specific LSP is not yet known. 859 Note that based on the recommendation in the 860 MPLS-TC-STD-MIB, instance index 0 should refer to the 861 configured tunnel interface." 862 ::= { pwMplsTeMappingEntry 2 } 864 pwMplsTeMappingTunnelPeerLsrID OBJECT-TYPE 865 SYNTAX MplsLsrIdentifier 866 MAX-ACCESS not-accessible 867 STATUS current 868 DESCRIPTION 869 "Identifies the Peer LSR when the outer tunnel is MPLS-TE 870 based." 871 ::= { pwMplsTeMappingEntry 3 } 873 pwMplsTeMappingTunnelLocalLsrID OBJECT-TYPE 874 SYNTAX MplsLsrIdentifier 875 MAX-ACCESS not-accessible 876 STATUS current 877 DESCRIPTION 878 "Identifies the local LSR." 879 ::= { pwMplsTeMappingEntry 4 } 881 pwMplsTeMappingVcIndex OBJECT-TYPE 882 SYNTAX PwIndexType 883 MAX-ACCESS read-only 884 STATUS current 885 DESCRIPTION 886 "The value that represent the PW in the pwTable." 887 ::= { pwMplsTeMappingEntry 5 } 889 -- End of PW to TE MPLS tunnels mapping Table. 891 -- conformance information 893 pwMplsGroups OBJECT IDENTIFIER ::= { pwMplsConformance 1 } 894 pwMplsCompliances OBJECT IDENTIFIER ::= { pwMplsConformance 2 } 895 -- Compliance requirement for fully compliant implementations. 897 pwMplsModuleFullCompliance MODULE-COMPLIANCE 898 STATUS current 899 DESCRIPTION 900 "The compliance statement for agents that provide full 901 support for PW-MPLS MIB Module. Such devices can 902 then be monitored and also be configured using 903 this MIB module." 905 MODULE -- this module 906 MANDATORY-GROUPS { pwMplsGroup, 907 pwMplsOutboundMainGroup, 908 pwMplsInboundGroup, 909 pwMplsMappingGroup 910 } 912 GROUP pwMplsOutboundTeGroup 913 DESCRIPTION "This group MUST be supported if the implementation 914 allows MPLS TE tunnels to carry PW traffic. 915 " 917 OBJECT pwMplsMplsType 918 DESCRIPTION "Support of vcOnly(2) is not required. At least one 919 of mplsTe(0) or mplsNonTe(1) MUST be supported if 920 signaling of PW is supported. 921 " 923 OBJECT pwMplsExpBitsMode 924 DESCRIPTION "Support of specifiedValue(2) and 925 serviceDependant(3) 926 is optional. 927 " 929 OBJECT pwMplsLocalLdpID 930 MIN-ACCESS read-only 931 DESCRIPTION "A read-write access is required if the 932 implementation supports more than one LDP entity 933 identifier for PW signaling. 934 " 936 OBJECT pwMplsLocalLdpEntityID 937 MIN-ACCESS read-only 938 DESCRIPTION "A read-write access is required if the 939 implementation supports more than one LDP entity 940 index for PW signaling. 941 " 943 OBJECT pwMplsOutboundLsrXcIndex 944 MIN-ACCESS read-only 945 DESCRIPTION "A value other than zero MUST be supported if the 946 implementation support non TE signaling of the 947 outer tunnel. 948 A read-write access MUST be supported if the 949 implementation supports manually setting of the PW 950 labels and carrying them over non-TE tunnels. 951 " 952 OBJECT pwMplsOutboundIfIndex 953 MIN-ACCESS read-only 954 DESCRIPTION "A value other than zero and read-write operations 955 MUST be supported if the implementation supports 956 manully configured PW without MPLS outer tunnel. 957 " 958 ::= { pwMplsCompliances 1 } 960 -- Compliance requirement for Read Only compliant implementations. 962 pwMplsModuleReadOnlyCompliance MODULE-COMPLIANCE 963 STATUS current 964 DESCRIPTION 965 "The compliance statement for agents that provide read 966 only support for PW-MPLS MIB Module. Such devices can 967 then be monitored but cannot be configured using this 968 MIB module." 970 MODULE -- this module 971 MANDATORY-GROUPS { pwMplsGroup, 972 pwMplsOutboundMainGroup, 973 pwMplsInboundGroup, 974 pwMplsMappingGroup 975 } 977 GROUP pwMplsOutboundTeGroup 978 DESCRIPTION "This group MUST be supported if the implementation 979 allows MPLS TE tunnels to carry PW traffic. 980 " 982 OBJECT pwMplsMplsType 983 MIN-ACCESS read-only 984 DESCRIPTION "Write access is not required. 985 Support of vcOnly(2) is not required. At least one 986 of mplsTe(0) or mplsNonTe(1) MUST be supported if 987 signaling of PW is supported. 988 " 990 OBJECT pwMplsExpBitsMode 991 MIN-ACCESS read-only 992 DESCRIPTION "Write access is not required. 993 Support of specifiedValue(2) and 995 serviceDependant(3) 996 is optional. 997 " 999 OBJECT pwMplsExpBits 1000 MIN-ACCESS read-only 1001 DESCRIPTION "Write access is not required. 1002 " 1003 OBJECT pwMplsTtl 1004 MIN-ACCESS read-only 1005 DESCRIPTION "Write access is not required. 1006 " 1008 OBJECT pwMplsLocalLdpID 1009 MIN-ACCESS read-only 1010 DESCRIPTION "Write access is not required. 1011 " 1013 OBJECT pwMplsLocalLdpEntityID 1014 MIN-ACCESS read-only 1015 DESCRIPTION "Write access is not required. 1016 " 1018 OBJECT pwMplsStorageType 1019 MIN-ACCESS read-only 1020 DESCRIPTION "Write access is not required. 1021 " 1023 OBJECT pwMplsOutboundLsrXcIndex 1024 MIN-ACCESS read-only 1025 DESCRIPTION "Write access is not required. 1026 A value other than zero MUST be supported if the 1027 implementation support non TE signaling of the 1028 outer tunnel. 1029 " 1031 OBJECT pwMplsOutboundTunnelIndex 1032 MIN-ACCESS read-only 1033 DESCRIPTION "Write access is not required. 1034 " 1036 OBJECT pwMplsOutboundTunnelLclLSR 1037 MIN-ACCESS read-only 1038 DESCRIPTION "Write access is not required. 1039 " 1041 OBJECT pwMplsOutboundTunnelPeerLSR 1042 MIN-ACCESS read-only 1043 DESCRIPTION "Write access is not required. 1044 " 1046 OBJECT pwMplsOutboundIfIndex 1047 MIN-ACCESS read-only 1048 DESCRIPTION "Write access is not required. 1049 A value other than zero MUST be supported if the 1050 implementation supports manually configured PW 1051 without MPLS outer tunnel. 1052 " 1053 ::= { pwMplsCompliances 2 } 1055 -- Units of conformance. 1057 pwMplsGroup OBJECT-GROUP 1058 OBJECTS { 1059 pwMplsMplsType, 1060 pwMplsExpBitsMode, 1061 pwMplsExpBits, 1062 pwMplsTtl, 1063 pwMplsLocalLdpID, 1064 pwMplsLocalLdpEntityID, 1065 pwMplsPeerLdpID, 1066 pwMplsStorageType 1067 } 1069 STATUS current 1070 DESCRIPTION 1071 "Collection of objects needed for PW over MPLS PSN 1072 configuration." 1073 ::= { pwMplsGroups 1 } 1075 pwMplsOutboundMainGroup OBJECT-GROUP 1076 OBJECTS { 1077 pwMplsOutboundLsrXcIndex, 1078 pwMplsOutboundIfIndex, 1079 pwMplsOutboundTunnelTypeInUse 1080 } 1082 STATUS current 1083 DESCRIPTION 1084 "Collection of objects needed for outbound association of 1085 PW and MPLS tunnel." 1086 ::= { pwMplsGroups 2 } 1088 pwMplsOutboundTeGroup OBJECT-GROUP 1089 OBJECTS { 1090 pwMplsOutboundTunnelIndex, 1091 pwMplsOutboundTunnelInstance, 1092 pwMplsOutboundTunnelLclLSR, 1093 pwMplsOutboundTunnelPeerLSR 1094 } 1096 STATUS current 1097 DESCRIPTION 1098 "Collection of objects needed for outbound association of 1099 PW and MPLS TE tunnel." 1100 ::= { pwMplsGroups 3 } 1102 pwMplsInboundGroup OBJECT-GROUP 1103 OBJECTS { 1104 pwMplsInboundXcIndex 1105 } 1107 STATUS current 1108 DESCRIPTION 1109 "Collection of objects needed for inbound PW presentation. 1110 This group MUST be supported if PW signaling through LDP is 1111 used." 1112 ::= { pwMplsGroups 4 } 1114 pwMplsMappingGroup OBJECT-GROUP 1115 OBJECTS { 1116 pwMplsNonTeMappingVcIndex, 1117 pwMplsTeMappingVcIndex 1118 } 1120 STATUS current 1121 DESCRIPTION 1122 "Collection of objects needed for mapping association of 1123 PW and MPLS tunnel." 1124 ::= { pwMplsGroups 5 } 1126 END 1128 6. Security Considerations 1130 It is clear that this MIB module is potentially useful for 1131 monitoring of PW capable PEs. This MIB module can also be used for 1132 configuration of certain objects, and anything that can be 1133 configured can be incorrectly configured, with potentially 1134 disastrous results. 1136 There are a number of management objects defined in this MIB module 1137 with a MAX-ACCESS clause of read-write and/or read-create. Such 1138 objects may be considered sensitive or vulnerable in some network 1139 environments. The support for SET operations in a non-secure 1140 environment without proper protection can have a negative effect on 1141 network operations. These are the tables and objects and their 1142 sensitivity/vulnerability: 1144 o the pwMplsTable, pwMplsNonTeMappingTable and 1145 pwMplsTeMappingTable collectively contain objects to 1146 provision PW over MPLS tunnels. Unauthorized access to 1147 objects in these tables, could result in disruption of 1148 traffic on the network. The use of stronger mechanisms 1149 such as SNMPv3 security should be considered where 1150 possible. Specifically, SNMPv3 VACM and USM MUST be used 1151 with any v3 agent which implements this MIB module. 1152 Administrators should consider whether read access to these 1153 objects should be allowed, since read access may be 1154 undesirable under certain circumstances. 1156 Some of the readable objects in this MIB module "i.e., objects with 1157 a MAX-ACCESS other than not-accessible" may be considered sensitive 1158 or vulnerable in some network environments. It is thus important 1159 to control even GET and/or NOTIFY access to these objects and 1160 possibly to even encrypt the values of these objects when sending 1161 them over the network via SNMP. These are the tables and objects 1162 and their sensitivity/vulnerability: 1164 o the pwMplsTable, pwMplsNonTeMappingTable, 1165 pwMplsTeMappingTable and pwMplsOutboundTable 1166 collectively show the PW over MPLS association. 1167 If an Administrator does not want to reveal this 1168 information, then these tables should be 1169 considered sensitive/vulnerable. 1171 SNMP versions prior to SNMPv3 did not include adequate security. 1172 Even if the network itself is secure "for example by using IPSec", 1173 even then, there is no control as to who on the secure network is 1174 allowed to access and GET/SET "read/change/create/delete" the 1175 objects in this MIB module. 1177 It is RECOMMENDED that implementers consider the security features 1178 as provided by the SNMPv3 framework "see [RFC3410], section 8", 1179 including full support for the SNMPv3 cryptographic mechanisms "for 1180 authentication and privacy". 1182 Further, deployment of SNMP versions prior to SNMPv3 is NOT 1183 RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to 1184 enable cryptographic security. It is then a customer/operator 1185 responsibility to ensure that the SNMP entity giving access to an 1186 instance of this MIB module, is properly configured to give access 1187 to the objects only to those principals "users" that have 1188 legitimate rights to indeed GET or SET "change/create/delete" them. 1190 7 References 1191 7.1 Normative references 1193 [PWCNTRL] Martini et al, "Pseudowire Setup and Maintenance using 1194 LDP", draft-ietf-pwe3-control-protocol-17.txt, 1195 June 2005. 1197 [RFC3985] Bryant, S., et al, "PWE3 Architecture",RFC2985, 1198 March 2005 1200 [PWTC] Nadeau, T., et al, "Definitions for Textual Conventions 1201 and OBJECT-IDENTITIES for Pseudo-Wires Management", 1202 work-in-progress. 1204 [PWMIB] Zelig, D., et al, "Pseudo Wire (PW) Management 1205 Information Base", work-in-progress. 1207 [RFC2863] McCloghrie, K., Kastenholz, F., "The Interfaces Group 1208 MIB", RFC 2863, June 2000. 1210 [RFC3031] Rosen, E., Viswanathan, A., and R. Callon, 1211 "Multiprotocol Label Switching Architecture", RFC 3031, 1212 Jan 2001. 1214 [RFC3813] Srinivasan, C., Viswanathan, A., and Nadeau, T., "MPLS 1215 Label Switch Router Management Information Base Using 1216 SMIv2", work-in-progress. 1218 [RFC3814] Srinivasan, C., Viswanathan, A., and Nadeau, T., "MPLS 1219 Traffic Engineering Management Information Base Using 1220 SMIv2", RFC3812. 1222 [RFC3811] Nadeau, T., Cucchiara, J., "Definition of Textual 1223 Conventions and OBJECT-IDENTITIES for Multi-Protocol 1224 Label Switching (MPLS) Management", RFC 3811, June 1225 2004. 1227 [RFC3036] Andersson, L., et al, "LDP specification", RFC 3036, 1228 January 2001. 1230 [RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, 1231 J.,Rose, M. and S. Waldbusser, "Structure of Management 1232 Information Version 2 (SMIv2)", STD 58, RFC 2578, April 1233 1999. 1235 [RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, 1236 J., Rose, M. and S. Waldbusser, "Textual Conventions 1237 for SMIv2", STD 58, RFC 2579, April 1999. 1239 [RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, 1240 J., Rose, M. and S. Waldbusser, "Conformance Statements 1241 for SMIv2", STD 58, RFC 2580, April 1999. 1243 7.2 Informative references 1245 [RFC3036] Andersson, L., Doolan, P., Feldman, N., Fredette, A., and 1246 B. Thomas, "LDP Specification", RFC 3036, January 2001. 1248 [RFC3410] Case, J., Mundy, R., Partain, D. and B. Stewart, 1249 Introduction and Applicability Statements for Internet- 1250 Standard Management Framework", RFC 3410, December 1251 2002. 1253 8. Editors' Addresses 1255 David Zelig 1256 Corrigent Systems 1257 126, Yigal Alon st. 1258 Tel Aviv, ISRAEL 1259 Phone: +972-3-6945273 1260 Email: davidz@corrigent.com 1262 Thomas D. Nadeau 1263 Cisco Systems, Inc. 1264 250 Apollo Drive 1265 Chelmsford, MA 01824 1266 Email: tnadeau@cisco.com 1268 9. Contributors' Addresses 1270 Dave Danenberg 1271 Email: dave_danenberg@yahoo.com 1273 Andrew G. Malis 1274 Tellabs, Inc. 1275 2730 Orchard Parkway 1276 San Jose, CA 95134 1277 Email: Andy.Malis@tellabs.com 1279 Sharon Mantin 1280 AxONLink (Israel) Ltd 1281 9 Bareket St. 1282 Petah Tikva 49517, Israel 1283 Phone: +972-3-9263972 1284 Email: sharon.mantin@axonlink.com 1286 10. Intellectual Property Statement 1288 The IETF takes no position regarding the validity or scope of any 1289 Intellectual Property Rights or other rights that might be claimed to 1290 pertain to the implementation or use of the technology described in 1291 this document or the extent to which any license under such rights 1292 might or might not be available; nor does it represent that it has 1293 made any independent effort to identify any such rights. Information 1294 on the procedures with respect to rights in RFC documents can be 1295 found in BCP 78 and BCP 79. 1297 Copies of IPR disclosures made to the IETF Secretariat and any 1298 assurances of licenses to be made available, or the result of an 1299 attempt made to obtain a general license or permission for the use of 1300 such proprietary rights by implementers or users of this 1301 specification can be obtained from the IETF on-line IPR repository at 1302 http://www.ietf.org/ipr. 1304 The IETF invites any interested party to bring to its attention any 1305 copyrights, patents or patent applications, or other proprietary 1306 rights that may cover technology that may be required to implement 1307 this standard. Please address the information to the IETF at ietf- 1308 ipr@ietf.org. 1310 11. Full Copyright Statement 1312 Copyright (C) The Internet Society (2005). This document is 1313 subject to the rights, licenses and restrictions contained in BCP 1314 78, and except as set forth therein, the authors retain all their 1315 rights. 1317 This document and the information contained herein are provided 1318 on an "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE 1319 REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND 1320 THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, 1321 EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT 1322 THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR 1323 ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A 1324 PARTICULAR PURPOSE. 1326 12. IANA Considerations 1328 PWE3 related standards track PW modules should be 1329 rooted under the pwMIB subtree. The IANA is requested to manage 1330 that namespace. New assignments can only be made via a Standards 1331 Action as specified in [RFC2434]. 1333 IANA is requested to make a MIB OID assignment under the 1334 pwMIB branch as specified in section 11.1. 1336 12.1 IANA Considerations for PW-MPLS-STD-MIB 1338 This document also requests IANA to assign { pwMIB 4 } to the 1339 PW-MPLS-STD-MIB module specified in this document. 1341 Acknowledgement 1343 Funding for the RFC Editor function is currently provided by the 1344 Internet Society.