idnits 2.17.1 draft-ietf-pwe3-pw-mpls-mib-04.txt: ** The Abstract section seems to be numbered Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** Looks like you're using RFC 2026 boilerplate. This must be updated to follow RFC 3978/3979, as updated by RFC 4748. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- == There are 3 instances of lines with non-ascii characters in the document. == No 'Intended status' indicated for this document; assuming Proposed Standard Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack a Security Considerations section. (A line matching the expected section header was found, but with an unexpected indentation: ' 8 Security Considerations' ) ** The document seems to lack an IANA Considerations section. (See Section 2.2 of https://www.ietf.org/id-info/checklist for how to handle the case when there are no actions for IANA.) (A line matching the expected section header was found, but with an unexpected indentation: ' 9 IANA considerations' ) Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the RFC 3978 Section 5.4 Copyright Line does not match the current year == Line 231 has weird spacing: '...N |PWin inSeg...' == Line 235 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 (December 2003) is 7432 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: 'PWCNTRL' is mentioned on line 106, but not defined == Missing Reference: 'TRANS' is mentioned on line 125, but not defined == Missing Reference: 'CEPMIB' is mentioned on line 184, but not defined == Missing Reference: 'PWTCMIB' is mentioned on line 1091, but not defined == Unused Reference: 'IF-MIB' is defined on line 1113, but no explicit reference was found in the text == Unused Reference: 'LblStk' is defined on line 1120, but no explicit reference was found in the text == Unused Reference: 'MPLSTCMIB' is defined on line 1135, but no explicit reference was found in the text == Unused Reference: 'LDP' is defined on line 1141, but no explicit reference was found in the text -- Possible downref: Non-RFC (?) normative reference: ref. 'PWARCH' -- Possible downref: Non-RFC (?) normative reference: ref. 'PWREQ' -- Possible downref: Non-RFC (?) normative reference: ref. 'PWTC' -- Possible downref: Non-RFC (?) normative reference: ref. 'PW-MIB' -- Possible downref: Non-RFC (?) normative reference: ref. 'LSRMIB' -- Possible downref: Non-RFC (?) normative reference: ref. 'TEMIB' -- Possible downref: Non-RFC (?) normative reference: ref. 'MPLSTCMIB' ** Obsolete normative reference: RFC 3036 (ref. 'LDP') (Obsoleted by RFC 5036) Summary: 5 errors (**), 0 flaws (~~), 14 warnings (==), 9 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 Internet Draft David Zelig 2 Expires: June 2004 Corrigent Systems 4 A. Malis Thomas D. Nadeau 5 Tellabs, Inc. Cisco Systems, Inc. 7 Sharon Mantin Dave Danenberg 8 AxONLinks Litchfield Communications, Inc. 10 December 2003 12 Pseudo Wire (PW) over MPLS PSN Management Information Base 14 draft-ietf-pwe3-pw-mpls-mib-04.txt 16 Status of this Memo 18 This document is an Internet-Draft and is in full conformance 19 with all provisions of Section 10 of RFC2026. 21 Internet-Drafts are working documents of the Internet Engineering 22 Task Force (IETF), its areas, and its working groups. Note that 23 other groups may also distribute working documents as Internet- 24 Drafts. 26 Internet-Drafts are draft documents valid for a maximum of six 27 months and may be updated, replaced, or obsoleted by other 28 documents at any time. It is inappropriate to use Internet-Drafts 29 as reference material or to cite them other than as "work in 30 progress." 32 The list of current Internet-Drafts can be accessed at 33 http://www.ietf.org/ietf/1id-abstracts.txt 34 The list of Internet-Draft Shadow Directories can be accessed at 35 http://www.ietf.org/shadow.html. 37 Copyright (C) The Internet Society (2001). All rights reserved. 39 1 Abstract 41 This memo defines an experimental portion of the Management 42 Information Base (MIB) for use with network management protocols in 43 the Internet community. In particular, it describes a MIB module 44 for PW operation over Multi-Protocol Label Switching (MPLS) Label 45 Switch Router (LSR). 47 Pseudo Wire (PW) Over MPLS December 2003 48 Management Information Base 50 Table of Contents 52 1 Abstract.......................................................1 53 2 Introduction...................................................2 54 3 Terminology....................................................3 55 4 The Internet-Standard Management Framework.....................3 56 5 Feature Checklist..............................................4 57 6 MIB module usage...............................................4 58 6.1 PW-MPLS-MIB usage............................................4 59 6.2 Example of MIB module usage..................................6 60 7 Object definitions.............................................7 61 8 Security Considerations.......................................20 62 9 IANA considerations...........................................22 63 10 References..................................................22 64 10.1 Normative references........................................22 65 10.2 Informative references......................................23 66 11 Author's Addresses..........................................23 67 12 Full Copyright Statement....................................24 68 13 Intellectual Property Notice................................25 70 2 Introduction 72 This document describes a model for managing pseudo wire services 73 for transmission over different flavors of MPLS tunnels. The 74 general PW MIB module [PW-MIB] defines the parameters global to the 75 PW regardless of underlying PSN and emulated service. Indicating 76 PSN type of MPLS in PW-MIB references this module. 78 This document describes the MIB objects that define pseudo wire 79 association to the MPLS PSN, in a way that is not specific to the 80 carried service. 82 Together, [TEMIB and LSRMIB], describe the modeling of an MPLS 83 Tunnel, and a Tunnel's underlying cross-connects. The defined MIB 84 support MPLS-TE PSN, Non TE MPLS PSN (an outer tunnel created by 85 LDP or manually), and MPLS PW label only (no outer tunnel). 87 Some flavors of MPLS, such as carrying PW in MPLS in IP and MPLS in 88 GRE are not defined here, waiting to the WG documents that will 89 describe the exact MPLS functionality. It still for further study 90 whether this functionality will be treated in this MIB module or in 91 another one specific to IP PSN. 93 Pseudo Wire (PW) Over MPLS December 2003 94 Management Information Base 96 Conventions used in this document 98 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 99 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in 100 this document are to be interpreted as described in RFC-2119 101 [BCP14]. 103 3 Terminology 105 This document uses terminology from the document describing the PW 106 architecture [PWARCH], [PWREQ] and [PWCNTRL]. 108 The terms "Outbound" and "Inbound" in this MIB module are based on 109 the common practice in the MPLS standards, i.e. "outbound" are 110 toward the PSN. However, where these terms are used in an object 111 name, the object description clarifies the exact packet direction 112 to prevent confusion with these terms in other documents. 114 "PSN Tunnel" is a general term indicating a virtual connection 115 between the two PWE3 edge devices. Each tunnel may potentially 116 carry multiple PWs inside. In the scope of this document, it is 117 MPLS tunnel. 119 This document uses terminology from the document describing the 120 MPLS architecture [MPLSArch] for MPLS PSN. A Label Switched Path 121 (LSP) is modeled as described in [LSRMIB and TEMIB] via a series of 122 cross-connects through 1 or more Label switch routers (LSR). 124 In MPLS PSN, a PW connection typically uses a PW Label within a 125 Tunnel Label [TRANS]. Multiple pseudo wires each with a unique PW 126 Label can share the same Tunnel. For PW transport over MPLS, the 127 Tunnel Label is known as the "outer" Label, while the PW Label is 128 known as the "inner" Label. An exception to this is with adjacent 129 LSRs or the use of PHP. In this case, there is an option for PWs to 130 connect directly without an outer Label. 132 4 The Internet-Standard Management Framework 134 For a detailed overview of the documents that describe the current 135 Internet-Standard Management Framework, please refer to section 7 136 of RFC 3410 [RFC3410]. 138 Managed objects are accessed via a virtual information store, 139 termed the Management Information Base or MIB. MIB objects are 140 generally accessed through the Simple Network Management Protocol 141 (SNMP). Objects in the MIB are defined using the mechanisms defined 142 in the Structure of Management Information (SMI). This memo 143 specifies a MIB module that is compliant to the SMIv2, which is 144 Pseudo Wire (PW) Over MPLS December 2003 145 Management Information Base 147 described in STD 58,RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] 148 and STD 58, RFC 2580 [RFC2580]. 150 5 Feature Checklist 152 The PW MPLS MIB module is designed to satisfy the following 153 requirements and constraints: 155 - The MIB module supports both manually configured and signaled 156 PWs. 158 - The MIB module supports point-to-point PW connections. 160 - The MIB module enables the use of any emulated service. 162 - The MIB supports MPLS-TE outer tunnel, Non TE MPLS outer tunnel 163 (an outer tunnel signaled by LDP or set-up manually), and no 164 outer tunnel (where the PW label is the only label in the 165 incoming MPLS stack). The later case is applicable for manual 166 configuration of PW over a single hop (in multiple hops case, it 167 is required to have an outer MPLS tunnel). 169 6 MIB module usage 171 The MIB module structure for defining a PW service is composed from 172 three types of modules. 174 The first type is the PW-MIB module [PW-MIB], which configures 175 general parameters of the PW that are common to all types of 176 emulated services and PSN. 178 The second type of modules is per PSN module. There is a different 179 module for each type of PSN. This document defines the MIB module 180 for MPLS (PW-MPLS-MIB). 182 The third type of modules is service-specific module, which is 183 emulated signal type dependent. These modules are defined in other 184 documents; see for example [CEPMIB]. 186 [PWTC] defines some of the object types used in this module. 188 6.1 PW-MPLS-MIB usage 190 - The PW table (pwVcTable) in [PW-MIB] is used for all PW types 191 (ATM, FR, Ethernet, SONET, etc.). This table contains high level 192 generic parameters related to the PW creation. A row is created by 193 the operator for each PW service. 195 Pseudo Wire (PW) Over MPLS December 2003 196 Management Information Base 198 - If the PSN type in pwVcTable is MPLS, the agent create a row in 199 the MPLS specific parameters table (pwMplsVcTable) in PW MPLS MIB, 200 which contain MPLS specific parameters such as EXP bits handling 201 and outer tunnel types. 203 - The operator configure the association to the desired MPLS 204 tunnel or tunnels through either the pwMplsTeMappingTable, 205 pwMplsNonTeMappingTable or both, depending on the desired outer 206 tunnel type. Each of the above tables may contain multiple entries 207 for the same PW, for example in protection configuration. 209 - The agent creates rows in the MPLS outbound tunnels table 210 (pwVcMplsOutboundTable) based on the configuration above. This 211 table allows quick access to the association tables through 212 pwVcIndex ordering. 214 The relation to the MPLS network is by configuration of the edge 215 LSR only - that is to say, the LSR providing the PW function. Since 216 Tunnels are uni-directional, a pair of tunnels must exist (one for 217 inbound, one for outbound). The following graphic depicts a VC that 218 originates and terminates at LSR-M. It uses LSPs A and B formed by 219 Tunnels Ax and Bx continuing through LSR-N to LSR-P. The 220 concatenations of Tunnels create the LSPs. Note: 'X' denotes a 221 Tunnel's cross-connect. 223 LSP-A 224 <- - - - - - - - - - - - - - - - - - - - - - - - - - - - 226 +---- (edge) LSR-M ---+ +--------- LSR-N ---------+ + LSR-P 227 |---+ | | | | 228 | | Tunnel | | Tunnel | | 229 + | A1 (M<-N) +----+ +----+ A2 (M<-P) +----+ +----+ 230 | | <------| | | |<--------------| | | | 231 <-->| N |PWin inSeg |MPLS| |MPLS| outSeg inSeg |MPLS| |MPLS| 232 N S | | <---X<-----| IF | | IF |<------X<------| IF | | IF | 233 A E | S | | |<-->| | | |<-->| | | 234 T R | | --->X----->| | | |------>X------>| | | | 235 I V | P |PWout outSeg| | | | inSeg outSeg | | | | 236 V I | | ------>| | | |-------------->| | | | 237 E C + | Tunnel +----+ +----+ Tunnel +----+ +----+ 238 E |---+ B1 (M->N) | | B2 (M->P) | | 239 | | | | | 240 +---------------------+ +-------------------------+ +----- 242 - - - - - - - - - - - - - - - - - - - - - - - - - - - -> 243 LSP-B 245 The PW-MPLS-MIB supports three options for MPLS network: 247 Pseudo Wire (PW) Over MPLS December 2003 248 Management Information Base 250 - In the MPLS-TE case, Tunnel A1 and B1 are created via the MPLS-TE 251 MIB [TEMIB]. The tunnels are associated to the PW by the (4) 252 indexes that uniquely identify the Tunnel at the TE-MIB. 254 - In the Non TE case, Tunnel A1 and B1 are either manually 255 configured or set up with LDP. The tunnels are associated to the PW 256 by the XC index in the MPLS-LSR-MIB [LSRMIB]. 258 - In the PW label only case, there is no outer tunnel on top of the 259 PW label. This case is useful in case of adjacent PE only in manual 260 configuration. Note that when LSR-N acts as PHP for the outer 261 tunnel label, there are still entries for the outer tunnel in the 262 relevant MPLS MIB modules. 264 A combination of MPLS-TE outer tunnel(s) and LDP outer tunnel for 265 the same VC is allowed by creating the rows with the same pwVcIndex 266 with different MPLS tunnel indexes types. 268 It is worth noting that inbound (tunnel originated in the remote 269 PE) mapping is nor configured nor reported through the PW MPLS MIB 270 module since the local PE does not know the inbound association 271 between specific PW and MPLS tunnels. 273 6.2 Example of MIB module usage 275 Please see [PW-MIB] for detailed MIB usage example. 277 Pseudo Wire (PW) Over MPLS December 2003 278 Management Information Base 280 7 Object definitions 282 PW-MPLS-DRAFT04-MIB DEFINITIONS ::= BEGIN 284 IMPORTS 285 MODULE-IDENTITY, OBJECT-TYPE, 286 Unsigned32 287 FROM SNMPv2-SMI 289 MODULE-COMPLIANCE, OBJECT-GROUP 290 FROM SNMPv2-CONF 292 RowStatus, StorageType 293 FROM SNMPv2-TC 295 InterfaceIndexOrZero 296 FROM IF-MIB 298 MplsTunnelIndex, MplsTunnelInstanceIndex, 299 MplsLdpIdentifier, MplsLsrIdentifier 300 FROM MPLS-TC-STD-MIB 302 PwVcIndexType, pwStdMIB 303 FROM PW-TC-DRAFT04-MIB 305 pwVcIndex 306 FROM PW-DRAFT04-MIB 308 ; 310 pwVcMplsMIB MODULE-IDENTITY 311 LAST-UPDATED "200311301200Z" -- 30 November 2003 12:00:00 EST 312 ORGANIZATION "Pseudo Wire Edge to Edge Emulation (PWE3) Working 313 Group" 314 CONTACT-INFO 315 " 316 David Zelig 317 Postal: Corrigent Systems 318 126, Yigal Alon St. 319 Tel Aviv, ISRAEL 320 Phone: +972-3-6945273 321 E-mail: davidz@corrigent.com 323 Thomas D. Nadeau 324 Postal: Cisco Systems, Inc. 325 250 Apollo Drive 326 Chelmsford, MA 01824 327 Tel: +1-978-497-3051 328 Email: tnadeau@cisco.com 330 Dave Danenberg 331 Pseudo Wire (PW) Over MPLS December 2003 332 Management Information Base 334 Postal: Litchfield Communications, Inc. 335 76 Westbury Park Rd 336 Princeton Building East 337 Watertown, CT 06795 338 Tel: +1-860-945-1573 x3180 339 Email: dave_danenberg@litchfieldcomm.com 341 Sharon Mantin 342 Postal: AxONLink (Israel) Ltd 343 9 Bareket St. 344 Petah Tikva 49517, Israel 345 Tel: +972-3-9263972 346 Email: sharon.mantin@axonlink.com 348 The PWE3 Working Group (email distribution pwe3@ietf.org, 349 http://www.ietf.org/html.charters/pwe3-charter.html) 350 " 351 DESCRIPTION 352 "This MIB complements the PW-STD-MIB for PW operation 353 over MPLS. 355 Copyright (C) The Internet Society (date). This version 356 of this MIB module is part of RFC yyyy; see the RFC 357 itself for full legal notices. 358 -- RFC Ed.: replace yyyy with actual RFC number & remove this note 359 " 361 -- Revision history. 363 REVISION 364 "200311301200Z" -- 30 November 2003 12:00:00 EST 365 DESCRIPTION 366 "Draft-ietf-pwe3-pw-mpls-mib-04 version. Changes from 367 previous version: 368 1) Adapting description to MIB boilerplate. 369 2) Module OID changed to PWE3 tree. 370 3) Sync descriptions of various items to table structure and 371 removing unnecessary references. 372 " 373 REVISION 374 "200307291200Z" -- 29 July 2003 12:00:00 EST 375 DESCRIPTION 376 "Draft-ietf-pwe3-pw-mpls-mib-02 version. Changes from 377 previous version: 378 1) Removing inbound table (no strict mode and no knowledge 379 of inbound tunnel). 380 2) Provisioning (i.e. RowCreate) done via mapping tables. 381 Outbound table is now read only for sorted search for 382 pwVcIndex. 383 " 384 Pseudo Wire (PW) Over MPLS December 2003 385 Management Information Base 387 REVISION 388 "200206021200Z" -- 02 June 2002 12:00:00 EST 389 DESCRIPTION 390 "Draft-ietf-pwe3-pw-mpls-mib-00 version. Changes from 391 previous version: 392 1) Spliting the mapping table into two tables, one for 393 Non TE application and one for TE application. 394 2) Object types alignment with MPLS MIBs. 395 " 396 REVISION 397 "200201291200Z" -- 29 January 2002 12:00:00 EST 398 DESCRIPTION 399 "Changes from previous version: 400 1) Add LDP entity association. 401 2) Clarify inbound/outbound directions. 402 3) Simplify indexing of outbound and inbound tables 403 and providing get next variables. 404 " 405 REVISION 406 "200111071200Z" -- 7 November 2001 12:00:00 EST 407 DESCRIPTION 408 "Changes from previous version: 409 1) Remove Vc instance from table indexing. 410 2) Update descriptions of indexing and protection. 411 3) Remove the need for MPLS-LSR in case of VC only. 412 4) Change pwVcMplsMplsType to BITS in order to enable 413 multiple types of outer tunnel. 414 5) Add ifindex to outer tunnel tables to support vcOnly 415 option. 416 6) change naming of outbound, inbound and mapping tables to 417 reflect addition of VC only port ifindexes. 418 7) Adapt order of items in mapping table to SNMP convention. 419 " 420 REVISION 421 "200107111200Z" -- July 11 2001 12:00:00 EST 422 DESCRIPTION 423 "draft-zelig-pw-mib-00.txt - initial version" 425 ::= { pwStdMIB 3 } -- To be assigned by IANA 427 -- Top-level components of this MIB. 429 -- Tables, Scalars 430 pwVcMplsObjects OBJECT IDENTIFIER 431 ::= { pwVcMplsMIB 1 } 432 -- Conformance 433 pwVcMplsConformance OBJECT IDENTIFIER 434 ::= { pwVcMplsMIB 2 } 436 -- PW MPLS table 437 Pseudo Wire (PW) Over MPLS December 2003 438 Management Information Base 440 pwVcMplsTable OBJECT-TYPE 441 SYNTAX SEQUENCE OF PwVcMplsEntry 442 MAX-ACCESS not-accessible 443 STATUS current 444 DESCRIPTION 445 "This table controls MPLS specific parameters when the PW is 446 going to be carried over MPLS PSN." 447 ::= { pwVcMplsObjects 1 } 449 pwVcMplsEntry OBJECT-TYPE 450 SYNTAX PwVcMplsEntry 451 MAX-ACCESS not-accessible 452 STATUS current 453 DESCRIPTION 454 "A row in this table represents parameters specific to MPLS 455 PSN for a pseudo wire (PW). The row is created 456 automatically by the local agent if the pwVcPsnType is 457 MPLS. It is indexed by pwVcIndex, which uniquely 458 identifying a singular PW. 459 " 461 INDEX { pwVcIndex } 463 ::= { pwVcMplsTable 1 } 465 PwVcMplsEntry ::= SEQUENCE { 466 pwVcMplsMplsType BITS, 467 pwVcMplsExpBitsMode INTEGER, 468 pwVcMplsExpBits Unsigned32, 469 pwVcMplsTtl Unsigned32, 470 pwVcMplsLocalLdpID MplsLdpIdentifier, 471 pwVcMplsLocalLdpEntityID Unsigned32, 472 pwVcMplsPeerLdpID MplsLdpIdentifier, 473 pwVcMplsStorageType StorageType 474 } 476 pwVcMplsMplsType OBJECT-TYPE 477 SYNTAX BITS { 478 mplsTe (0), 479 mplsNonTe (1), 480 vcOnly (2) 481 } 482 MAX-ACCESS read-write 483 STATUS current 484 DESCRIPTION 485 "Set by the operator to indicate the outer tunnel types, if 486 exists. mplsTe is used if the outer tunnel was set-up by 487 MPLS-TE, and mplsNonTe is used the outer tunnel was set up 488 by LDP or manually. Combination of mplsTe and mplsNonTe 489 may exist in case of outer tunnel protection. 490 vcOnly is used if there is no outer tunnel label, i.e. in 491 Pseudo Wire (PW) Over MPLS December 2003 492 Management Information Base 494 static provisioning without MPLS tunnel. vcOnly 495 cannot be combined with mplsNonTe or mplsTe." 496 ::= { pwVcMplsEntry 1 } 498 pwVcMplsExpBitsMode OBJECT-TYPE 499 SYNTAX INTEGER { 500 outerTunnel (1), 501 specifiedValue (2), 502 serviceDependant (3) 503 } 505 MAX-ACCESS read-write 506 STATUS current 507 DESCRIPTION 508 "Set by the operator to indicate the way the PW shim label 509 EXP bits are to be determined. The value of outerTunnel(1) 510 is used where there is an outer tunnel - pwVcMplsMplsType 511 is mplsTe or mplsNonTe. Note that in this case there is no 512 need to mark the PW label with the EXP bits since the PW 513 label is not visible to the intermediate nodes. 514 If there is no outer tunnel, specifiedValue(2) indicate 515 that the value is specified by pwVcMplsExpBits, and 516 serviceDependant(3) indicate that the EXP bits are setup 517 based on a rule specified in the emulated service specific 518 tables, for example when the EXP bits are a function of 519 802.1p marking for Ethernet emulated service." 521 DEFVAL { outerTunnel } 522 ::= { pwVcMplsEntry 2 } 524 pwVcMplsExpBits OBJECT-TYPE 525 SYNTAX Unsigned32 (0..7) 526 MAX-ACCESS read-write 527 STATUS current 528 DESCRIPTION 529 "Set by the operator to indicate the MPLS EXP bits to be 530 used on the PW shim label if pwVcMplsExpBitsMode is 531 specifiedValue(2), zero otherwise." 532 DEFVAL { 0 } 533 ::= { pwVcMplsEntry 3 } 535 pwVcMplsTtl OBJECT-TYPE 536 SYNTAX Unsigned32 (0..255) 537 MAX-ACCESS read-write 538 STATUS current 539 DESCRIPTION 540 "Set by the operator to indicate the PW TTL bits to be used 541 on the PW shim label." 542 DEFVAL { 2 } 543 ::= { pwVcMplsEntry 4 } 544 Pseudo Wire (PW) Over MPLS December 2003 545 Management Information Base 547 pwVcMplsLocalLdpID OBJECT-TYPE 548 SYNTAX MplsLdpIdentifier 549 MAX-ACCESS read-write 550 STATUS current 551 DESCRIPTION 552 "The local LDP identifier of the LDP entity creating 553 this PW in the local node. As the PW labels are always 554 set from the per platform label space, the last two octets 555 in the LDP ID MUST be always both zeros." 556 REFERENCE 557 "'LDP specifications', RFC 3036 section 2.2.2." 558 ::= { pwVcMplsEntry 5 } 560 pwVcMplsLocalLdpEntityID OBJECT-TYPE 561 SYNTAX Unsigned32 562 MAX-ACCESS read-write 563 STATUS current 564 DESCRIPTION 565 "The local node LDP Entity index of the LDP entity creating 566 this PW. Should be set to all zeros if not used." 567 ::= { pwVcMplsEntry 6 } 569 pwVcMplsPeerLdpID OBJECT-TYPE 570 SYNTAX MplsLdpIdentifier 571 MAX-ACCESS read-only 572 STATUS current 573 DESCRIPTION 574 "The peer LDP identifier as identified from the LDP 575 session. Should be zero if not relevant or not known yet." 576 ::= { pwVcMplsEntry 7 } 578 pwVcMplsStorageType OBJECT-TYPE 579 SYNTAX StorageType 580 MAX-ACCESS read-write 581 STATUS current 582 DESCRIPTION 583 "This variable indicates the storage type for this row." 584 ::= { pwVcMplsEntry 8 } 586 -- End of PW MPLS table 588 -- Pseudo Wire MPLS Outbound Tunnel table 590 pwVcMplsOutboundTable OBJECT-TYPE 591 SYNTAX SEQUENCE OF PwVcMplsOutboundEntry 592 MAX-ACCESS not-accessible 593 STATUS current 594 DESCRIPTION 595 "This table reports the association between PWs and the 596 outbound MPLS tunnels (i.e. toward the PSN) or the physical 597 Pseudo Wire (PW) Over MPLS December 2003 598 Management Information Base 600 interface in case of PW label only. The configuration of 601 the association is done in other tables." 602 ::= { pwVcMplsObjects 2 } 604 pwVcMplsOutboundEntry OBJECT-TYPE 605 SYNTAX PwVcMplsOutboundEntry 606 MAX-ACCESS not-accessible 607 STATUS current 608 DESCRIPTION 609 "A row in this table indicate association between a PW (that 610 require MPLS tunnels) and MPLS tunnel toward the PSN. 611 In the case of PW only, it associates the PW with the 612 interface that shall carry the PW. 613 This table is indexed by the pwVcIndex and an additional 614 index enabling multiple rows (i.e. tunnels) for the same 615 pwVcindex. 617 At least one entry is created in this table by the agent 618 for each PW that requires MPLS PSN. 620 This table points to the appropriate MPLS MIB. In the case 621 of MPLS-TE, the 4 variables relevant to the indexing of 622 a TE MPLS tunnel are set as in Srinivasan, et al, . 624 In case of Non-TE MPLS (an outer tunnel label assigned by 625 LDP or manually) the table points to the XC entry in the 626 LSR MIB as in Srinivasan, et al, . 627 In case of PW label only (no outer tunnel) the ifIndex of 628 the port to carry the PW is configured. 630 Each PW may have multiple rows in this tables if protection 631 is available at the outer tunnel level. For a specific PW, 632 each row may be of different type except for PW lable only, 633 on which only rows with ifIndex of the port are allowed. 634 " 636 INDEX { pwVcIndex, pwVcMplsOutboundIndex } 638 ::= { pwVcMplsOutboundTable 1 } 640 PwVcMplsOutboundEntry ::= SEQUENCE { 641 pwVcMplsOutboundIndex Unsigned32, 642 pwVcMplsOutboundLsrXcIndex Unsigned32, 643 pwVcMplsOutboundTunnelIndex MplsTunnelIndex, 644 pwVcMplsOutboundTunnelInstance MplsTunnelInstanceIndex, 645 pwVcMplsOutboundTunnelLclLSR MplsLsrIdentifier, 646 pwVcMplsOutboundTunnelPeerLSR MplsLsrIdentifier, 647 pwVcMplsOutboundIfIndex InterfaceIndexOrZero 648 } 650 pwVcMplsOutboundIndex OBJECT-TYPE 651 Pseudo Wire (PW) Over MPLS December 2003 652 Management Information Base 654 SYNTAX Unsigned32 (0..4294967295) 655 MAX-ACCESS not-accessible 656 STATUS current 657 DESCRIPTION 658 "Arbitrary index for enabling multiple rows per PW in 659 this table. The numbering method is implementation 660 specific. 661 " 662 ::= { pwVcMplsOutboundEntry 1 } 664 pwVcMplsOutboundLsrXcIndex OBJECT-TYPE 665 SYNTAX Unsigned32 666 MAX-ACCESS read-only 667 STATUS current 668 DESCRIPTION 669 "This object will be set by the operator. If the outer 670 label is defined in the MPLS-LSR-STD-MIB, i.e. set by LDP 671 or manually, this object points to the XC index 672 of the outer tunnel. Otherwise, it returns the value zero." 673 ::= { pwVcMplsOutboundEntry 2 } 675 pwVcMplsOutboundTunnelIndex OBJECT-TYPE 676 SYNTAX MplsTunnelIndex 677 MAX-ACCESS read-only 678 STATUS current 679 DESCRIPTION 680 "Part of set of indexes for outbound tunnel in the case of 681 MPLS-TE outer tunnel, otherwise returns the value zero." 682 ::= { pwVcMplsOutboundEntry 3 } 684 pwVcMplsOutboundTunnelInstance OBJECT-TYPE 685 SYNTAX MplsTunnelInstanceIndex 686 MAX-ACCESS read-only 687 STATUS current 688 DESCRIPTION 689 "Part of set of indexes for outbound tunnel in the case of 690 MPLS-TE outer tunnel, otherwise returns the value zero." 691 ::= { pwVcMplsOutboundEntry 4 } 693 pwVcMplsOutboundTunnelLclLSR OBJECT-TYPE 694 SYNTAX MplsLsrIdentifier 695 MAX-ACCESS read-only 696 STATUS current 697 DESCRIPTION 698 "Part of set of indexes for outbound tunnel in the case of 699 MPLS-TE outer tunnel, otherwise returns the value zero." 700 ::= { pwVcMplsOutboundEntry 5 } 702 pwVcMplsOutboundTunnelPeerLSR OBJECT-TYPE 703 SYNTAX MplsLsrIdentifier 704 Pseudo Wire (PW) Over MPLS December 2003 705 Management Information Base 707 MAX-ACCESS read-only 708 STATUS current 709 DESCRIPTION 710 "Part of set of indexes for outbound tunnel in the case of 711 MPLS-TE outer tunnel, otherwise returns the value zero." 712 ::= { pwVcMplsOutboundEntry 6 } 714 pwVcMplsOutboundIfIndex OBJECT-TYPE 715 SYNTAX InterfaceIndexOrZero 716 MAX-ACCESS read-only 717 STATUS current 718 DESCRIPTION 719 "In case of PW label only (no outer tunnel), this object 720 holds the ifIndex of the outbound port, otherwise returns 721 the value zero." 722 ::= { pwVcMplsOutboundEntry 7 } 724 -- End of Pseudo Wire MPLS Outbound Tunnel table 726 -- PW to Non-TE MPLS tunnels configuration Table. 727 pwVcMplsNonTeMappingTable OBJECT-TYPE 728 SYNTAX SEQUENCE OF PwVcMplsNonTeMappingEntry 729 MAX-ACCESS not-accessible 730 STATUS current 731 DESCRIPTION 732 "This table maps an outbound Tunnel to a PW in non- 733 TE applications." 734 ::= { pwVcMplsObjects 3 } 736 pwVcMplsNonTeMappingEntry OBJECT-TYPE 737 SYNTAX PwVcMplsNonTeMappingEntry 738 MAX-ACCESS not-accessible 739 STATUS current 740 DESCRIPTION 741 "A row in this table configure the association 742 between the PW and it's non TE MPLS outer Tunnel or 743 it's physical interface if there is no outer tunnel 744 (PW label only). 746 If the operator (or the agent, based on local policy) 747 want to associate the PW with a non TE tunnel, it create 748 a row in this table with the tunnel parameters and the 749 relevant pwVcIndex. 751 An application can use this table to quickly retrieve the 752 PW carried over specific non-TE MPLS outer tunnel or 753 physical interface. 755 The table in indexed by the XC index for MPLS Non-TE 756 tunnel, or ifIndex of the port in PW label only case, and 757 the PW index. 759 Pseudo Wire (PW) Over MPLS December 2003 760 Management Information Base 762 " 764 INDEX { pwVcMplsNonTeMappingXcTunnelIndex, 765 pwVcMplsNonTeMappingIfIndex, 766 pwVcMplsNonTeMappingVcIndex } 768 ::= { pwVcMplsNonTeMappingTable 1 } 770 PwVcMplsNonTeMappingEntry ::= SEQUENCE { 771 pwVcMplsNonTeMappingXcTunnelIndex Unsigned32, 772 pwVcMplsNonTeMappingIfIndex InterfaceIndexOrZero, 773 pwVcMplsNonTeMappingVcIndex PwVcIndexType, 774 pwVcMplsNonTeMappingRowStatus RowStatus, 775 pwVcMplsNonTeMappingStorageType StorageType 776 } 778 pwVcMplsNonTeMappingXcTunnelIndex OBJECT-TYPE 779 SYNTAX Unsigned32 (0..4294967295) 780 MAX-ACCESS not-accessible 781 STATUS current 782 DESCRIPTION 783 "Index for the conceptual XC row identifying Tunnel to PW 784 mappings when the outer tunnel is created by the MPLS-LSR- 785 STD-MIB, zero otherwise." 786 ::= { pwVcMplsNonTeMappingEntry 1 } 788 pwVcMplsNonTeMappingIfIndex OBJECT-TYPE 789 SYNTAX InterfaceIndexOrZero 790 MAX-ACCESS not-accessible 791 STATUS current 792 DESCRIPTION 793 "In cases where there is PW label without outer tunnel, 794 this item indicate the ifIndex of the interface this PW 795 would use. In all other cases, this object should be set to 796 zero." 797 ::= { pwVcMplsNonTeMappingEntry 2 } 799 pwVcMplsNonTeMappingVcIndex OBJECT-TYPE 800 SYNTAX PwVcIndexType 801 MAX-ACCESS not-accessible 802 STATUS current 803 DESCRIPTION 804 "The value that represent the PW in the pwVcTable." 805 ::= { pwVcMplsNonTeMappingEntry 3 } 807 pwVcMplsNonTeMappingRowStatus OBJECT-TYPE 808 SYNTAX RowStatus 809 MAX-ACCESS read-create 810 STATUS current 811 DESCRIPTION 812 "For creating, modifying, and deleting this row." 813 Pseudo Wire (PW) Over MPLS December 2003 814 Management Information Base 816 ::= { pwVcMplsNonTeMappingEntry 4 } 818 pwVcMplsNonTeMappingStorageType OBJECT-TYPE 819 SYNTAX StorageType 820 MAX-ACCESS read-create 821 STATUS current 822 DESCRIPTION 823 "This variable indicates the storage type for this object." 824 ::= { pwVcMplsNonTeMappingEntry 5 } 826 -- End of PW to Non-TE MPLS tunnels configuration Table. 828 -- PW to TE MPLS tunnels configuration Table. 830 pwVcMplsTeMappingTable OBJECT-TYPE 831 SYNTAX SEQUENCE OF PwVcMplsTeMappingEntry 832 MAX-ACCESS not-accessible 833 STATUS current 834 DESCRIPTION 835 "This table enable the configuration and retrieval of a PW 836 association to and outbound MPLS tunnel for MPLS-TE 837 applications." 838 ::= { pwVcMplsObjects 4 } 840 pwVcMplsTeMappingEntry OBJECT-TYPE 841 SYNTAX PwVcMplsTeMappingEntry 842 MAX-ACCESS not-accessible 843 STATUS current 844 DESCRIPTION 845 "A row in this table represents the association 846 between a PW and it's MPLS-TE outer Tunnel. 848 If the operator (or the agent, based on local policy) 849 want to associate the PW with a TE tunnel, it create 850 a row in this table with the tunnel parameters and the 851 relevant pwVcIndex. 853 An application can use this table to quickly retrieve the 854 PW carried over specific TE MPLS outer tunnel. 856 The table in indexed by the 4 indexes of a TE tunnel 857 and the PW index. 858 " 860 INDEX { pwVcMplsTeMappingTunnelIndex, 861 pwVcMplsTeMappingTunnelInstance, 862 pwVcMplsTeMappingTunnelPeerLsrID, 863 pwVcMplsTeMappingTunnelLocalLsrID, 864 pwVcMplsTeMappingVcIndex } 866 ::= { pwVcMplsTeMappingTable 1 } 867 Pseudo Wire (PW) Over MPLS December 2003 868 Management Information Base 870 PwVcMplsTeMappingEntry ::= SEQUENCE { 871 pwVcMplsTeMappingTunnelIndex MplsTunnelIndex, 872 pwVcMplsTeMappingTunnelInstance MplsTunnelInstanceIndex, 873 pwVcMplsTeMappingTunnelPeerLsrID MplsLsrIdentifier, 874 pwVcMplsTeMappingTunnelLocalLsrID MplsLsrIdentifier, 875 pwVcMplsTeMappingVcIndex PwVcIndexType, 876 pwVcMplsTeMappingRowStatus RowStatus, 877 pwVcMplsTeMappingStorageType StorageType 879 } 881 pwVcMplsTeMappingTunnelIndex OBJECT-TYPE 882 SYNTAX MplsTunnelIndex 883 MAX-ACCESS not-accessible 884 STATUS current 885 DESCRIPTION 886 "Primary index for the conceptual row identifying the 887 MPLS-TE tunnel." 888 ::= { pwVcMplsTeMappingEntry 1 } 890 pwVcMplsTeMappingTunnelInstance OBJECT-TYPE 891 SYNTAX MplsTunnelInstanceIndex 892 MAX-ACCESS not-accessible 893 STATUS current 894 DESCRIPTION 895 "Identifies an instance of the MPLS-TE tunnel." 896 ::= { pwVcMplsTeMappingEntry 2 } 898 pwVcMplsTeMappingTunnelPeerLsrID OBJECT-TYPE 899 SYNTAX MplsLsrIdentifier 900 MAX-ACCESS not-accessible 901 STATUS current 902 DESCRIPTION 903 "Identifies the Peer LSR when the outer tunnel is MPLS-TE 904 based." 905 ::= { pwVcMplsTeMappingEntry 3 } 907 pwVcMplsTeMappingTunnelLocalLsrID OBJECT-TYPE 908 SYNTAX MplsLsrIdentifier 909 MAX-ACCESS not-accessible 910 STATUS current 911 DESCRIPTION 912 "Identifies the local LSR." 913 ::= { pwVcMplsTeMappingEntry 4 } 915 pwVcMplsTeMappingVcIndex OBJECT-TYPE 916 SYNTAX PwVcIndexType 917 MAX-ACCESS not-accessible 918 STATUS current 919 DESCRIPTION 920 Pseudo Wire (PW) Over MPLS December 2003 921 Management Information Base 923 "The value that represent the PW in the pwVcTable." 924 ::= { pwVcMplsTeMappingEntry 5 } 926 pwVcMplsTeMappingRowStatus OBJECT-TYPE 927 SYNTAX RowStatus 928 MAX-ACCESS read-create 929 STATUS current 930 DESCRIPTION 931 "For creating, modifying, and deleting this row." 932 ::= { pwVcMplsTeMappingEntry 6 } 934 pwVcMplsTeMappingStorageType OBJECT-TYPE 935 SYNTAX StorageType 936 MAX-ACCESS read-create 937 STATUS current 938 DESCRIPTION 939 "This variable indicates the storage type for this object." 940 ::= { pwVcMplsTeMappingEntry 7 } 942 -- End of PW to TE MPLS tunnels configuration Table. 944 -- conformance information 946 -- Note: Conformance at the object access and values level is 947 -- still FFS, therefore current conformance is defined at the 948 -- object existence level only. 950 pwVcMplsGroups OBJECT IDENTIFIER ::= { pwVcMplsConformance 1 } 951 pwVcMplsCompliances OBJECT IDENTIFIER ::= { pwVcMplsConformance 2 } 953 pwMplsModuleCompliance MODULE-COMPLIANCE 954 STATUS current 955 DESCRIPTION 956 "The compliance statement for agent that support PW 957 over MPLS PSN operation." 959 MODULE -- this module 960 MANDATORY-GROUPS { pwVcMplsGroup, 961 pwVcMplsOutboundGroup, 962 pwVcMplsMappingGroup 963 } 965 ::= { pwVcMplsCompliances 1 } 967 -- Units of conformance. 969 pwVcMplsGroup OBJECT-GROUP 970 OBJECTS { 971 Pseudo Wire (PW) Over MPLS December 2003 972 Management Information Base 974 pwVcMplsMplsType, 975 pwVcMplsExpBitsMode, 976 pwVcMplsExpBits, 977 pwVcMplsTtl, 978 pwVcMplsLocalLdpID, 979 pwVcMplsLocalLdpEntityID, 980 pwVcMplsPeerLdpID, 981 pwVcMplsStorageType 982 } 984 STATUS current 985 DESCRIPTION 986 "Collection of objects needed for PW 987 over MPLS PSN configuration." 988 ::= { pwVcMplsGroups 1 } 990 pwVcMplsOutboundGroup OBJECT-GROUP 991 OBJECTS { 992 pwVcMplsOutboundLsrXcIndex, 993 pwVcMplsOutboundTunnelIndex, 994 pwVcMplsOutboundTunnelInstance, 995 pwVcMplsOutboundTunnelLclLSR, 996 pwVcMplsOutboundTunnelPeerLSR, 997 pwVcMplsOutboundIfIndex 998 } 1000 STATUS current 1001 DESCRIPTION 1002 "Collection of objects needed for outbound association of 1003 PW and MPLS tunnel." 1004 ::= { pwVcMplsGroups 2 } 1006 pwVcMplsMappingGroup OBJECT-GROUP 1007 OBJECTS { 1008 pwVcMplsNonTeMappingRowStatus, 1009 pwVcMplsNonTeMappingStorageType, 1010 pwVcMplsTeMappingRowStatus, 1011 pwVcMplsTeMappingStorageType 1012 } 1014 STATUS current 1015 DESCRIPTION 1016 "Collection of objects used for mapping of tunnels and PW 1017 labels to PW index." 1018 ::= { pwVcMplsGroups 4 } 1020 END -- of PW-MPLS-STD-MIB 1022 8 Security Considerations 1023 Pseudo Wire (PW) Over MPLS December 2003 1024 Management Information Base 1026 It is clear that this MIB module is potentially useful for 1027 monitoring of PW capable PEs. This MIB module can also be used for 1028 configuration of certain objects, and anything that can be 1029 configured can be incorrectly configured, with potentially 1030 disastrous results. 1032 There are a number of management objects defined in this MIB module 1033 with a MAX-ACCESS clause of read-write and/or read-create. Such 1034 objects may be considered sensitive or vulnerable in some network 1035 environments. The support for SET operations in a non-secure 1036 environment without proper protection can have a negative effect on 1037 network operations. These are the tables and objects and their 1038 sensitivity/vulnerability: 1040 o the pwVcMplsTable, pwVcMplsNonTeMappingTable and 1041 pwVcMplsTeMappingTable collectively contain objects to 1042 provision PW over MPLS tunnels. Unauthorized access to 1043 objects in these tables, could result in disruption of 1044 traffic on the network. The use of stronger mechanisms 1045 such as SNMPv3 security should be considered where 1046 possible. Specifically, SNMPv3 VACM and USM MUST be used 1047 with any v3 agent which implements this MIB module. 1048 Administrators should consider whether read access to these 1049 objects should be allowed, since read access may be 1050 undesirable under certain circumstances. 1052 Some of the readable objects in this MIB module "i.e., objects with 1053 a MAX-ACCESS other than not-accessible" may be considered sensitive 1054 or vulnerable in some network environments. It is thus important 1055 to control even GET and/or NOTIFY access to these objects and 1056 possibly to even encrypt the values of these objects when sending 1057 them over the network via SNMP. These are the tables and objects 1058 and their sensitivity/vulnerability: 1060 o the pwVcMplsTable, pwVcMplsNonTeMappingTable, 1061 pwVcMplsTeMappingTable and pwVcMplsOutboundTable 1062 collectively show the PW over MPLS association. 1063 If an Administrator does not want to reveal this 1064 information, then these tables should be 1065 considered sensitive/vulnerable. 1067 SNMP versions prior to SNMPv3 did not include adequate security. 1068 Even if the network itself is secure "for example by using IPSec", 1069 even then, there is no control as to who on the secure network is 1070 allowed to access and GET/SET "read/change/create/delete" the 1071 objects in this MIB module. 1073 It is RECOMMENDED that implementers consider the security features 1074 as provided by the SNMPv3 framework "see [RFC3410], section 8", 1075 Pseudo Wire (PW) Over MPLS December 2003 1076 Management Information Base 1078 including full support for the SNMPv3 cryptographic mechanisms "for 1079 authentication and privacy". 1081 Further, deployment of SNMP versions prior to SNMPv3 is NOT 1082 RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to 1083 enable cryptographic security. It is then a customer/operator 1084 responsibility to ensure that the SNMP entity giving access to an 1085 instance of this MIB module, is properly configured to give access 1086 to the objects only to those principals "users" that have 1087 legitimate rights to indeed GET or SET "change/create/delete" them. 1089 9 IANA considerations 1091 As requested in the PW-TC-STD-MIB [PWTCMIB], PWE3 related standards 1092 track MIB modules should be rooted under the pwStdMIB subtree. The 1093 IANA is requested to assign { pwStdMIB 3 } to the PW-MPLS-STD-MIB 1094 module specified in this document. 1096 10 References 1098 10.1 Normative references 1100 [PWARCH] Bryant, S., et al, "PWE3 Architecture", work-in- 1101 progress. 1103 [PWREQ] Xiao, X., et al, "Requirements for Pseudo Wire 1104 Emulation Edge-to-Edge (PWE3)", work-in-progress. 1106 [PWTC] Nadeau, T., et al, "Definitions for Textual Conventions 1107 and OBJECT-IDENTITIES for Pseudo-Wires Management", 1108 work-in-progress. 1110 [PW-MIB] Zelig, D., et al, "Pseudo Wire (PW) Management 1111 Information Base", work-in-progress. 1113 [IF-MIB] McCloghrie, K., Kastenholz, F., �The Interfaces Group 1114 MIB�, RFC 2863, June 2000. 1116 [MPLSArch] Rosen, E., Viswanathan, A., and R. Callon, 1117 "Multiprotocol Label Switching Architecture", RFC 3031, 1118 Jan 2001. 1120 [LblStk] Rosen, E., Rekhter, Y., Tappan, D., Farinacci, D., 1121 Federokow, G., Li, T., and A. Conta, "MPLS Label Stack 1122 Encoding", RFC 3032, January 2001. 1124 [LSRMIB] Srinivasan, C., Viswanathan, A., and Nadeau, T., "MPLS 1125 Label Switch Router Management Information Base Using 1126 SMIv2", work-in-progress. 1128 Pseudo Wire (PW) Over MPLS December 2003 1129 Management Information Base 1131 [TEMIB] Srinivasan, C., Viswanathan, A., and Nadeau, T., "MPLS 1132 Traffic Engineering Management Information Base Using 1133 SMIv2", work-in-progress. 1135 [MPLSTCMIB] Nadeau, T., Cucchiara, J., Srinivasan, C., Viswanathan, 1136 A., Sjostrand, H. and K. Kompella, "Definition of 1137 Textual Conventions and OBJECT-IDENTITIES for Multi- 1138 Protocol Label Switching (MPLS) Management", work-in- 1139 progress. 1141 [LDP] Andersson, L., et al, "LDP specification�, RFC 3036, 1142 January 2001. 1144 [BCP14] Bradner, S., "Key words for use in RFCs to Indicate 1145 requirement Levels", BCP 14, RFC 2119, March 1997. 1147 [RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, 1148 J.,Rose, M. and S. Waldbusser, "Structure of Management 1149 Information Version 2 (SMIv2)", STD 58, RFC 2578, April 1150 1999. 1152 [RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, 1153 J., Rose, M. and S. Waldbusser, "Textual Conventions 1154 for SMIv2", STD 58, RFC 2579, April 1999. 1156 [RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, 1157 J., Rose, M. and S. Waldbusser, "Conformance Statements 1158 for SMIv2", STD 58, RFC 2580, April 1999. 1160 10.2 Informative references 1162 [RFC3410] Case, J., Mundy, R., Partain, D. and B. Stewart, 1163 Introduction and Applicability Statements for Internet- 1164 Standard Management Framework", RFC 3410, December 1165 2002. 1167 11 Author's Addresses 1169 David Zelig 1170 Corrigent Systems 1171 126, Yigal Alon st. 1172 Tel Aviv, ISRAEL 1173 Phone: +972-3-6945273 1174 Email: davidz@corrigent.com 1176 Thomas D. Nadeau 1177 Cisco Systems, Inc. 1178 250 Apollo Drive 1179 Pseudo Wire (PW) Over MPLS December 2003 1180 Management Information Base 1182 Chelmsford, MA 01824 1183 Email: tnadeau@cisco.com 1185 Dave Danenberg 1186 Litchfield Communications, Inc. 1187 76 Westbury Park Rd 1188 Princeton Building East 1189 Watertown, CT 06795 1190 Email: dave_danenberg@litchfieldcomm.com 1192 Andrew G. Malis 1193 Tellabs, Inc. 1194 2730 Orchard Parkway 1195 San Jose, CA 95134 1196 Email: Andy.Malis@tellabs.com 1198 Sharon Mantin 1199 AxONLink (Israel) Ltd 1200 9 Bareket St. 1201 Petah Tikva 49517, Israel 1202 Phone: +972-3-9263972 1203 Email: sharon.mantin@axonlink.com 1205 12 Full Copyright Statement 1207 Copyright (C) The Internet Society (2000). All Rights Reserved. 1209 This document and translations of it may be copied and furnished to 1210 others, and derivative works that comment on or otherwise explain 1211 it or assist in its implementation may be prepared, copied, 1212 published and distributed, in whole or in part, without restriction 1213 of any kind, provided that the above copyright notice and this 1214 paragraph are included on all such copies and derivative works. 1215 However, this document itself may not be modified in any way, such 1216 as by removing the copyright notice or references to the Internet 1217 Society or other Internet organizations, except as needed for the 1218 purpose of developing Internet standards in which case the 1219 procedures for copyrights defined in the Internet Standards process 1220 must be followed, or as required to translate it into languages 1221 other than English. 1223 The limited permissions granted above are perpetual and will not be 1224 revoked by the Internet Society or its successors or assigns. This 1225 document and the information contained herein is provided on an "AS 1226 IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING 1227 TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING 1228 BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION 1229 HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF 1230 MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 1232 Pseudo Wire (PW) Over MPLS December 2003 1233 Management Information Base 1235 13 Intellectual Property Notice 1237 The IETF takes no position regarding the validity or scope of any 1238 intellectual property or other rights that might be claimed to 1239 pertain to the implementation or use of the technology described in 1240 this document or the extent to which any license under such rights 1241 might or might not be available; neither does it represent that it 1242 has made any effort to identify any such rights. Information on 1243 the IETF's procedures with respect to rights in standards-track and 1244 standards-related documentation can be found in BCP-11 [RFC2028]. 1245 Copies of claims of rights made available for publication and any 1246 assurances of licenses to be made available, or the result of an 1247 attempt made to obtain a general license or permission for the use 1248 of such proprietary rights by implementors or users of this 1249 specification can be obtained from the IETF Secretariat. 1250 The IETF invites any interested party to bring to its attention any 1251 copyrights, patents or patent applications, or other proprietary 1252 rights that may cover technology that may be required to practice 1253 this standard. Please address the information to the IETF 1254 Executive Director.