idnits 2.17.1 draft-ietf-pwe3-pw-mib-14.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** It looks like you're using RFC 3978 boilerplate. You should update this to the boilerplate described in the IETF Trust License Policy document (see https://trustee.ietf.org/license-info), which is required now. -- Found old boilerplate from RFC 3978, Section 5.1 on line 16. -- Found old boilerplate from RFC 3978, Section 5.5, updated by RFC 4748 on line 3133. -- Found old boilerplate from RFC 3979, Section 5, paragraph 1 on line 3144. -- Found old boilerplate from RFC 3979, Section 5, paragraph 2 on line 3151. -- Found old boilerplate from RFC 3979, Section 5, paragraph 3 on line 3157. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- -- The document has examples using IPv4 documentation addresses according to RFC6890, but does not use any IPv6 documentation addresses. Maybe there should be IPv6 examples, too? Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust Copyright Line does not match the current year == Line 306 has weird spacing: '...ilities notYe...' == Line 1842 has weird spacing: '... column insta...' == 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 (January 9, 2008) is 5946 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) -- Possible downref: Non-RFC (?) normative reference: ref. 'PWTC' ** Obsolete normative reference: RFC 4447 (Obsoleted by RFC 8077) -- Obsolete informational reference (is this intentional?): RFC 2434 (Obsoleted by RFC 5226) Summary: 2 errors (**), 0 flaws (~~), 4 warnings (==), 10 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Pseudowire Edge-to-Edge Emulation T. Nadeau, Ed. 3 Internet-Draft BT 4 Intended status: Standards Track D. Zelig, Ed. 5 Expires: July 12, 2008 Corrigent Systems 6 January 9, 2008 8 Pseudowire (PW) Management Information Base (MIB) 9 draft-ietf-pwe3-pw-mib-14 11 Status of this Memo 13 By submitting this Internet-Draft, each author represents that any 14 applicable patent or other IPR claims of which he or she is aware 15 have been or will be disclosed, and any of which he or she becomes 16 aware will be disclosed, in accordance with Section 6 of BCP 79. 18 Internet-Drafts are working documents of the Internet Engineering 19 Task Force (IETF), its areas, and its working groups. Note that 20 other groups may also distribute working documents as Internet- 21 Drafts. 23 Internet-Drafts are draft documents valid for a maximum of six months 24 and may be updated, replaced, or obsoleted by other documents at any 25 time. It is inappropriate to use Internet-Drafts as reference 26 material or to cite them other than as "work in progress." 28 The list of current Internet-Drafts can be accessed at 29 http://www.ietf.org/ietf/1id-abstracts.txt. 31 The list of Internet-Draft Shadow Directories can be accessed at 32 http://www.ietf.org/shadow.html. 34 This Internet-Draft will expire on July 12, 2008. 36 Copyright Notice 38 Copyright (C) The IETF Trust (2008). 40 Abstract 42 This memo defines an experimental portion of the Management 43 Information Base for use with network management protocols in the 44 Internet community. In particular, it describes managed objects for 45 modeling of Pseudowire Edge-to-Edge services carried over a general 46 Packet Switched Network. 48 Table of Contents 50 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 51 2. The Internet-Standard Management Framework . . . . . . . . . . 3 52 3. Conventions . . . . . . . . . . . . . . . . . . . . . . . . . 3 53 4. Co-Authors . . . . . . . . . . . . . . . . . . . . . . . . . . 3 54 5. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 55 6. Structure of the MIB Module . . . . . . . . . . . . . . . . . 4 56 7. PW-STD-MIB Module Usage . . . . . . . . . . . . . . . . . . . 5 57 8. Relations to Other PWE3 MIB Modules . . . . . . . . . . . . . 5 58 9. Relations to the IF-MIB . . . . . . . . . . . . . . . . . . . 6 59 10. PW Notifications . . . . . . . . . . . . . . . . . . . . . . . 6 60 11. Example of the PW MIB Modules Usage . . . . . . . . . . . . . 7 61 12. IANA PWE3 MIB Module . . . . . . . . . . . . . . . . . . . . . 9 62 13. Object Definitions . . . . . . . . . . . . . . . . . . . . . . 11 63 14. Security Considerations . . . . . . . . . . . . . . . . . . . 62 64 15. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 63 65 15.1. ifType for PW . . . . . . . . . . . . . . . . . . . . . . 63 66 15.2. PW MIB Modules OBJECT IDENTIFIER values . . . . . . . . . 64 67 15.3. IANA Considerations for PW-STD-MIB . . . . . . . . . . . 64 68 15.4. IANA Considerations for IANA-PWE3-MIB . . . . . . . . . . 64 69 16. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 65 70 17. References . . . . . . . . . . . . . . . . . . . . . . . . . . 65 71 17.1. Normative References . . . . . . . . . . . . . . . . . . 65 72 17.2. Informative References . . . . . . . . . . . . . . . . . 66 73 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 67 74 Intellectual Property and Copyright Statements . . . . . . . . . . 68 76 1. Introduction 78 This memo defines a portion of the Management Information Base (MIB) 79 for use with network management protocols in the Internet community. 80 In particular, it defines a MIB module that can be used to manage 81 pseudowire (PW) services for transmission over a packet Switched 82 Network (PSN) [RFC3931] [RFC4447]. This MIB module provides generic 83 management of PWs which is common to all types of PSN and PW services 84 defined by the IETF PWE3 Working Group. 86 Comments should be made directly to the PWE3 mailing list at 87 pwe3@ietf.org. 89 2. The Internet-Standard Management Framework 91 For a detailed overview of the documents that describe the current 92 Internet-Standard Management Framework, please refer to section 7 of 93 RFC 3410 [RFC3410]. 95 Managed objects are accessed via a virtual information store, termed 96 the Management Information Base or MIB. MIB objects are generally 97 accessed through the Simple Network Management Protocol (SNMP). 98 Objects in the MIB are defined using the mechanisms defined in the 99 Structure of Management Information (SMI). This memo specifies a MIB 100 module that is compliant to the SMIv2, which is described in STD 58, 101 RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580 102 [RFC2580]. 104 3. Conventions 106 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 107 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 108 document are to be interpreted as described in RFC 2119 [BCP14]. 110 This document adopts the definitions, acronyms and mechanisms 111 described in [RFC3985] and [RFC3916]. Unless otherwise stated, the 112 mechanisms of [RFC3985] apply and will not be re-described here. 114 4. Co-Authors 116 The individuals listed below are co-authors of this document. 118 Dave Danenberg - Litchfield Communications 119 Sharon Mantin - Corrigent Systems 121 5. Overview 123 The PWE3 MIB Modules architecture provides a layered modular model 124 into which any supported emulated service can be connected to any 125 supported PSN type. This specific MIB module provides the glue for 126 mapping between the emulated service onto the native PSN service. As 127 such the defining of a PW emulated service requires the use of at 128 least three types of MIB modules. 130 Starting from the emulated service, the first type is service- 131 specific module, which is emulated signal type dependent. These 132 modules are defined in other documents. 134 The second type is this module, the PW-STD-MIB module, which 135 configures general parameters of the PW that are common to all types 136 of emulated services and PSN types. 138 The third type of modules is PSN-specific module. There is a 139 different module for each type of PSN. These modules associate the 140 PW with one or more "tunnels" that carry the service over the PSN. 141 These modules are defined in other documents. 143 6. Structure of the MIB Module 145 The MIB Module consists of five tables; 147 - The generic configuration and status monitoring objects which are 148 common to all service types and PSN types (pwTable). 150 - The PW Performance Current Table (pwPerfCurrentTable) contains PW 151 statistics for the current 15-minute period. 153 - The PW Performance Interval Table (pwPerfIntervalTable) contains PW 154 statistics for historical intervals (usually 96 15-minute entries to 155 cover a 24 hour period). 157 - The PW Performance one day Interval Table (pwPerf1DayIntervalTable) 158 contains PW statistics for historical intervals accumulated per day. 159 Usually 30 1-Day entries to cover a monthly period. 161 - The mapping table (pwIndexMappingTable) enables the reverse mapping 162 of unique PWid parameters [peer IP, PW type and PW ID] and the 163 pwIndex. 165 - The mapping table (pwGenFecIndexMappingTable) enables the reverse 166 mapping of unique PWid parameters used in genFecSignaling 167 [pwGroupAttachmentID, pwLocalAttachmentID and pwPeerAttachmentID] and 168 the pwIndex. 170 This MIB module uses TCs from [RFC2578], [RFC2579], [RFC2580], 171 [RFC2863], [RFC3411], [RFC3593], [RFC3705], [RFC4001] and [PWTC], and 172 references [RFC3413], [RFC4623] and [RFC4720]. 174 7. PW-STD-MIB Module Usage 176 An entry in the PW table (pwTable) MUST exist for all PW types (ATM, 177 FR, Ethernet, SONET, etc.). This table holds generic parameters 178 related to the PW creation and monitoring. 180 A conceptual row can be created in the pwTable in one of the 181 following ways: 183 1) The operator creates a row in the PwTable when configuring the 184 node for a new service. This mode MUST be supported by the agent, 185 and MUST be used when creating a non-signaled (manually assigned) PW. 187 2) The agent MAY create a row in the PwTable if a signaling message 188 has been received from a peer node for a combination of signaling 189 identifications parameters already unknown to the local node. This 190 mode is OPTIONAL. 192 3) The agent MAY create a row in the PwTable automatically due to 193 some auto discovery application, or based on configuration that is 194 done through non-SNMP applications. This mode is OPTIONAL. 196 - The agent than creates the rows in the (locally supported) 197 performance tables and reverse mapping tables in PW-STD-MIB module. 199 8. Relations to Other PWE3 MIB Modules 201 - Based on the PSN type defined for the PW, a row is created in PSN 202 specific module (for example [PWMPLSMIB]) and associated to the PW 203 table by the common pwIndex. 205 - Based on the PW type defined for the PW, a row is created in 206 service-specific module (for example [CEPMIB]) and associated to the 207 PW table by the common pwIndex. 209 - Unless all the necessary entries in the applicable tables have been 210 created and all the parameters have been consistently configured in 211 those tables, signaling cannot be performed from the local node, and 212 the pwVcOperStatus should report 'notPresent'. 214 9. Relations to the IF-MIB 216 The PW in general is not an ifIndex [RFC2863] on its own, for agent 217 scalability reasons. The PW is typically associated via the PWE3 MIB 218 modules to an ifIndex the PW is emulating. This ifIndex may 219 represent a physical entity - for example a PW emulating a SONET path 220 as in CEP: The PW itself is not an ifIndex, however the PW-STD-CEP- 221 MIB module associates the PW to the ifIndex of the path to be 222 emulated. In some cases, the PW will be associated to an ifIndex 223 representing a virtual interface. An example is VPLS service where 224 the PW emulates a logical interface of a (logical) bridge. The 225 physical ports association to the VPLS service instance is defined in 226 non-PW MIB modules in this case. 228 Exception to the above MAY exist in some implementations, where it is 229 convenient to manage the PW as an ifIndex in the ifTable. A special 230 ifType to represent a PW virtual interface (exact number to be 231 assigned by IANA) will be used in the ifTable in this case. 233 When the PW is managed as an ifIndex, by default it SHOULD NOT be 234 stacked, i.e. this ifIndex SHOULD NOT be layered above the respective 235 PSN tunnel ifIndex or the attachment circuit ifIndex or the interface 236 carrying the attachment circuit. 238 Note that the ifIndex that carries the PW toward/from the PSN is in 239 general not explicitly configured via PWE3 MIB modules except in rare 240 cases. In most cases the PW is carried inside a PSN tunnel, and the 241 interfaces carrying the tunnel are specified in the related MIB 242 modules that control the PSN tunnels. 244 10. PW Notifications 246 This MIB module includes notifications for PW entering the up or down 247 state, in accordance with the guidelines for interface notifications 248 as described in [RFC2863]. Implementers should be aware that in many 249 systems it is desired to correlate notifications, such that 250 notifications will not be emitted if higher hierarchy (such as ports 251 or tunnels) notifications are already in effect. Specifically for 252 PWs, it is anticipated that most network's equipment failures turn 253 into lowerLayerDown state at the PW level, where higher hierarchy 254 level notification has already been emitted. 256 When a PW is represented as an ifIndex, it is RECOMMENDED that PW 257 notifications will be turned off, to avoid duplication with the 258 ifIndex status change notifications. 260 11. Example of the PW MIB Modules Usage 262 In this section we provide an example of using the MIB objects 263 described in section 7 to set up a CEP PW over MPLS PSN. While this 264 example is not meant to illustrate every permutation of the MIB, it 265 is intended as an aid to understanding some of the key concepts. It 266 is meant to be read after going through the MIB itself. 268 In this example a PW service for CEP is configured over an MPLS PSN 269 (MPLS-TE tunnel). It uses LDP as in [RFC4447] for service set-up. 271 For the operation in the service specific MIB modules and the PSN 272 specific MIB modules, see the specific MIB module memo. This example 273 is continued in the memo describing the PW-CEP-STD-MIB module (for 274 example [CEPMIB]) and the PW-MPLS-STD-MIB module [PWMPLSMIB]). 276 In the PW-STD-MIB module: 278 In pwTable: 279 { 280 pwIndex 5, 282 pwType cep, 283 pwOwner pwIdFecSignaling, 284 pwPsnType mpls, 285 pwSetUpPriority 0, -- Highest 286 pwHoldingPriority 0, -- Highest 287 pwInboundMode loose, 289 pwPeerAddrType ipv4, 290 pwPeerAddr 192.0.2.5, -- In this case equal to the 291 -- peer LDP entity IP addr 292 pwID 10, 293 pwLocalGroupID 12, 294 .. 296 pwCwPreference true, -- Actually ignored for CEP 297 pwLocalIfMtu 0, -- Do not send ifMtu parameter 298 pwLocalIfString false, -- Do not send interface string 299 pwCapabAdvert 0, -- Does not support status 300 -- report to the peer. 301 pwRemoteGroupID 0xFFFF, -- Will be received by 302 -- signaling protocol 303 pwRemoteCwStatus notKnownYet, 304 pwRemoteIfMtu 0, 305 pwRemoteIfString "", 306 pwRemoteCapabilities notYetKnown, 307 .. 308 pwOutboundVcLabel 0xFFFF, -- Will be received by 309 -- signaling protocol 310 pwInboundVcLabel 0xFFFF, -- Will be set by signaling 311 -- protocol 312 pwName "Example of CEP PW", 313 pwDescr "", 314 .. 316 pwAdminStatus up, 317 .. 318 } 320 12. IANA PWE3 MIB Module 322 This section contains the initial version of the IANA-PWE3-MIB. IANA 323 is requested to update this MIB module based on expert review as 324 defined in [RFC2434]. Each new assignment of PW type or PW PSN type 325 made by IANA based on the procedures described in [RFC4446] should be 326 documented in the online version of IANA-PWE3-MIB. The current IANA- 327 PWE3-MIB contains PW types as requested in [RFC4446] and [RFC4863]. 329 IANA-PWE3-MIB DEFINITIONS ::= BEGIN 331 IMPORTS 332 MODULE-IDENTITY, mib-2 333 FROM SNMPv2-SMI -- [RFC2578] 335 TEXTUAL-CONVENTION 336 FROM SNMPv2-TC; -- [RFC2579] 338 ianaPwe3MIB MODULE-IDENTITY 339 LAST-UPDATED "200712091200Z" -- 9 December 2007 12:00:00 GMT 340 ORGANIZATION "IANA" 341 CONTACT-INFO 342 "Internet Assigned Numbers Authority 343 Internet Corporation for Assigned Names and Numbers 344 4676 Admiralty Way, Suite 330 345 Marina del Rey, CA 90292-6601 347 Phone: +1 310 823 9358 348 EMail: iana@iana.org" 349 DESCRIPTION 350 "This MIB module defines the IANAPwTypeTC and 351 IANAPwPsnTypeTC textual conventions for use in PWE3 352 MIB modules. 354 Any additions or changes to the contents of this MIB 355 module require either publication of an RFC, Designated 356 Expert Review as defined in RFC 2434, Guidelines for 357 Writing an IANA Considerations Section in RFCs, and should 358 be based on the procedures defined in [RFC4446]. The 359 Designated Expert will be selected by the IESG Area 360 Director(s) of the internet Area. 362 Copyright (C) The IETF Trust (2008). The initial 363 version of this MIB module was published in RFC yyyy; 364 for full legal notices see the RFC itself. Supplementary 365 information may be available at: 367 http://www.ietf.org/copyrights/ianamib.html." 368 -- RFC Ed.: replace yyyy with actual RFC number & remove this note 370 REVISION "200712091200Z" -- 9 December 2007 12:00:00 GMT 371 DESCRIPTION "Original version, published as part of RFC yyyy." 372 -- RFC Editor: please fill the yyyy and remove this note. 374 ::= { mib-2 XXXX } 375 -- RFC Editor: please fill the XXXX based on the IANA allocation 376 -- and remove this note. 378 IANAPwTypeTC ::= TEXTUAL-CONVENTION 379 STATUS current 380 DESCRIPTION 381 "Indicates the PW type (i.e. the carried service). " 382 SYNTAX INTEGER { 383 other(0), 384 frameRelayDlciMartiniMode(1), 385 atmAal5SduVcc(2), 386 atmTransparent(3), 387 ethernetTagged(4), 388 ethernet(5), 389 hdlc(6), 390 ppp(7), 391 cem(8), -- Historic type 392 atmCellNto1Vcc(9), 393 atmCellNto1Vpc(10), 394 ipLayer2Transport(11), 395 atmCell1to1Vcc(12), 396 atmCell1to1Vpc(13), 397 atmAal5PduVcc(14), 398 frameRelayPortMode(15), 399 cep(16), 400 e1Satop(17), 401 t1Satop(18), 402 e3Satop(19), 403 t3Satop(20), 404 basicCesPsn(21), 405 basicTdmIp(22), 406 tdmCasCesPsn(23), 407 tdmCasTdmIp(24), 408 frDlci(25), 409 wildcard (32767) 410 } 412 IANAPwPsnTypeTC ::= TEXTUAL-CONVENTION 413 STATUS current 414 DESCRIPTION 415 "Identifies the PSN type which the PW will use over the 416 network." 417 SYNTAX INTEGER { 418 mpls (1), 419 l2tp (2), 420 udpOverIp (3), 421 mplsOverIp (4), 422 mplsOverGre (5), 423 other (6) 424 } 426 IANAPwCapabilities ::= TEXTUAL-CONVENTION 427 STATUS current 428 DESCRIPTION 429 "This TC describes a collection of capabilities related to 430 a specific PW. 431 Values may be added in the future based on new capabilities 432 introduced in IETF documents. 433 " 434 SYNTAX BITS { 435 pwStatusIndication (0), -- Applicable only if maintenance 436 -- protocol is in use. 437 pwVCCV (1) 438 } 440 END 442 13. Object Definitions 444 PW-STD-MIB DEFINITIONS ::= BEGIN 446 IMPORTS 447 NOTIFICATION-TYPE, MODULE-IDENTITY, OBJECT-TYPE, 448 Integer32, Unsigned32, Counter32, Counter64, TimeTicks, 449 transmission 450 FROM SNMPv2-SMI -- [RFC2578] 452 MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP 453 FROM SNMPv2-CONF -- [RFC2580] 455 TruthValue, RowStatus, StorageType, 456 TimeStamp 457 FROM SNMPv2-TC -- [RFC2579] 459 SnmpAdminString 460 FROM SNMP-FRAMEWORK-MIB -- [RFC3411] 462 InterfaceIndexOrZero 463 FROM IF-MIB -- [RFC2863] 465 InetAddressType, InetAddress 466 FROM INET-ADDRESS-MIB -- [RFC4001] 468 PerfCurrentCount, PerfIntervalCount 469 FROM PerfHist-TC-MIB -- [RFC3593] 471 HCPerfCurrentCount, HCPerfIntervalCount, HCPerfTimeElapsed, 472 HCPerfValidIntervals 473 FROM HC-PerfHist-TC-MIB -- [RFC3705] 475 PwIndexType, PwIndexOrZeroType, PwGroupID, PwIDType, 476 PwOperStatusTC, PwAttachmentIdentifierType, PwCwStatusTC, 477 PwStatus, PwFragSize, PwFragStatus, PwGenIdType 478 FROM PW-TC-STD-MIB -- [PWTC] 479 -- RFC Editor: Please replace [PWTC] with RFC number and remove this 480 -- note. 482 IANAPwTypeTC, IANAPwPsnTypeTC, IANAPwCapabilities 483 FROM IANA-PWE3-MIB -- Reference will be added 484 -- When IANA will create the 485 -- MIB module 486 ; 488 pwStdMIB MODULE-IDENTITY 489 LAST-UPDATED "200711121200Z" -- 12 November 2007 12:00:00 GMT 490 ORGANIZATION "Pseudowire Edge-to-Edge Emulation (PWE3) Working 491 Group" 492 CONTACT-INFO 493 " 494 David Zelig 495 E-mail: davidz@corrigent.com 497 Thomas D. Nadeau 498 Email: thomas.nadeau@bt.com 500 The PWE3 Working Group (email distribution pwe3@ietf.org, 501 http://www.ietf.org/html.charters/pwe3-charter.html) 502 " 504 DESCRIPTION 505 "This MIB module contains managed object definitions for 506 pseudowire operation as in Bryant, S. and P. Pate, 'Pseudo 507 Wire Emulation Edge-to-Edge (PWE3) Architecture' [RFC3985], 508 Martini, L., et al, 'Pseudowire Setup and Maintenance Using 509 the Label Distribution Protocol (LDP)' [RFC4447], and 510 Townsley, M., et al, 'Layer Two Tunneling Protocol 511 (Version 3)' [RFC3931]. 513 This MIB module enables the use of any underlying packet 514 switched network (PSN). MIB nodules that will support 515 PW operations over specific PSN types are defined in 516 separate memos. 518 The indexes for this MIB module are also used to index the 519 PSN-specific tables and the PW-specific tables. The PW Type 520 dictates which PW-specific MIB module to use. 522 Copyright (C) The IETF Trust (2008). This version 523 of this MIB module is part of RFC XXX; 524 For full legal notices see the RFC itself or 525 http://www.ietf.org/copyrights/ianamib.html 526 -- RFC Ed.: replace XXX with actual RFC number & remove this note 527 " 529 -- Revision history. 531 REVISION 532 "200711121200Z" -- 12 November 2007 12:00:00 GMT 533 DESCRIPTION "Initial version published as part of RFC YYYY." 534 -- RFC Editor: please replace YYYY with IANA assigned value, and 535 -- delete this note. 537 ::= { transmission ZZZZ } 538 -- RFC Editor: please replace ZZZZ with IANA assigned value, and 539 -- delete this note. 541 -- Top-level components of this MIB. 543 -- Notifications 544 pwNotifications OBJECT IDENTIFIER 545 ::= { pwStdMIB 0 } 546 -- Tables, Scalars 547 pwObjects OBJECT IDENTIFIER 548 ::= { pwStdMIB 1 } 549 -- Conformance 550 pwConformance OBJECT IDENTIFIER 551 ::= { pwStdMIB 2 } 553 -- PW Virtual Connection Table 555 pwIndexNext OBJECT-TYPE 556 SYNTAX Unsigned32 557 MAX-ACCESS read-only 558 STATUS current 559 DESCRIPTION 560 "This object contains an appropriate value to be used 561 for pwIndex when creating entries in the 562 pwTable. The value 0 indicates that no 563 unassigned entries are available. To obtain the 564 value of pwIndex for a new entry in the 565 pwTable, the manager issues a management 566 protocol retrieval operation. The agent will determine 567 through its local policy when this index value will be made 568 available for reuse." 569 ::= { pwObjects 1 } 571 pwTable OBJECT-TYPE 572 SYNTAX SEQUENCE OF PwEntry 573 MAX-ACCESS not-accessible 574 STATUS current 575 DESCRIPTION 576 "This table specifies information for configuring and 577 status monitoring which are common to all service types 578 and PSN types." 579 ::= { pwObjects 2 } 581 pwEntry OBJECT-TYPE 582 SYNTAX PwEntry 583 MAX-ACCESS not-accessible 584 STATUS current 585 DESCRIPTION 586 "A row in this table represents a pseudowire (PW) virtual 587 connection across a packet network. It is indexed by 588 pwIndex, which uniquely identifies a singular 589 connection. 590 A row can be created by an operator command from a 591 management plan of a PE, by signaling or due to autodiscovery 592 process. Operator's command can be issued via non SNMP 593 application; in such case a row will be created implicitly 594 by the agent. 595 The read-create objects in this tables are divided into 596 three categories: 597 1) Objects that MUST NOT be changed after row activation. 598 These are objects that define basic properties of the 599 PW (for example type, destination, etc.). 600 2) Objects that MAY be changed when the PW is 601 defined as not active. A change of these objects involves 602 re-signaling of the PW or it might be traffic affecting. 603 PW not active is defined as one of the following 604 conditions: 605 a) The pwRowStatus is notInService(2). 606 b) The pwRowStatus is notReady(3). 607 c) The pwAdminStatus is down(2). 608 If the operator needs to change one of the values for an 609 active row, the operator can either set the pwRowStatus to 610 notInService(2) or set pwAdminStatus to down(2). 611 Signaling (or traffic) is initiated again upon setting 612 the pwRowStatus to active(1) or setting the pwAdminStatus 613 to up(1) or testing(3) respectively. 614 3) Objects that MAY be changed at any time. 616 A PW MAY have an entry in the ifTable in addition to the 617 entry in this table. In this case a special ifType for PW 618 will be set in the ifTable, and the ifIndex in the ifTable 619 of the PW will be set in the pwIfIndex object in this table. 621 By default, all the read-create objects MUST NOT be 622 changed after row activation, unless specifically indicated 623 in the individual object description. 625 Manual entries in this table SHOULD be preserved after a 626 reboot, the agent MUST ensure the integrity of those 627 entries. If the set of entries of a specific row are found to 628 be non consistent after reboot, the PW pwOperStatus MUST be 629 declared as notPresent(5). 630 " 631 INDEX { pwIndex } 633 ::= { pwTable 1 } 635 PwEntry ::= SEQUENCE { 636 pwIndex PwIndexType, 637 pwType IANAPwTypeTC, 638 pwOwner INTEGER, 639 pwPsnType IANAPwPsnTypeTC, 640 pwSetUpPriority Integer32, 641 pwHoldingPriority Integer32, 642 pwPeerAddrType InetAddressType, 643 pwPeerAddr InetAddress, 644 pwAttachedPwIndex PwIndexOrZeroType, 645 pwIfIndex InterfaceIndexOrZero, 647 pwID PwIDType, 648 pwLocalGroupID PwGroupID, 649 pwGroupAttachmentID PwAttachmentIdentifierType, 650 pwLocalAttachmentID PwAttachmentIdentifierType, 651 pwRemoteAttachmentID PwAttachmentIdentifierType, 653 pwCwPreference TruthValue, 654 pwLocalIfMtu Unsigned32, 656 pwLocalIfString TruthValue, 657 pwLocalCapabAdvert IANAPwCapabilities, 658 pwRemoteGroupID PwGroupID, 659 pwCwStatus PwCwStatusTC, 660 pwRemoteIfMtu Unsigned32, 661 pwRemoteIfString SnmpAdminString, 662 pwRemoteCapabilities IANAPwCapabilities, 664 pwFragmentCfgSize PwFragSize, 665 pwRmtFragCapability PwFragStatus, 666 pwFcsRetentionCfg INTEGER, 667 pwFcsRetentionStatus BITS, 669 pwOutboundLabel Unsigned32, 670 pwInboundLabel Unsigned32, 672 pwName SnmpAdminString, 673 pwDescr SnmpAdminString, 674 pwCreateTime TimeStamp, 675 pwUpTime TimeTicks, 676 pwLastChange TimeTicks, 677 pwAdminStatus INTEGER, 678 pwOperStatus PwOperStatusTC, 679 pwLocalStatus PwStatus, 680 pwRemoteStatusCapable INTEGER, 681 pwRemoteStatus PwStatus, 682 pwTimeElapsed HCPerfTimeElapsed, 683 pwValidIntervals HCPerfValidIntervals, 684 pwRowStatus RowStatus, 685 pwStorageType StorageType, 686 pwOamEnable TruthValue, 687 pwGenAGIType PwGenIdType, 688 pwGenLocalAIIType PwGenIdType, 689 pwGenRemoteAIIType PwGenIdType 690 } 692 pwIndex OBJECT-TYPE 693 SYNTAX PwIndexType 694 MAX-ACCESS not-accessible 695 STATUS current 696 DESCRIPTION 697 "A unique index for the conceptual row identifying a PW within 698 this table." 699 ::= { pwEntry 1 } 701 pwType OBJECT-TYPE 702 SYNTAX IANAPwTypeTC 703 MAX-ACCESS read-create 704 STATUS current 705 DESCRIPTION 706 "This value indicates the emulated service to be carried over 707 this PW. 708 " 709 ::= { pwEntry 2 } 711 pwOwner OBJECT-TYPE 712 SYNTAX INTEGER { 713 manual (1), 714 pwIdFecSignaling (2), -- PW signaling with PW ID FEC 715 genFecSignaling (3), -- Generalized attachment FEC 716 l2tpControlProtocol (4), 717 other (5) 718 } 719 MAX-ACCESS read-create 720 STATUS current 721 DESCRIPTION 722 "This object is set by the operator to indicate the protocol 723 responsible for establishing this PW. 724 'manual' is used in all cases where no maintenance 725 protocol (PW signaling) is used to set-up the PW, i.e. 726 require configuration of entries in the PW tables including 727 PW labels, etc. 728 'pwIdFecSignaling' is used in case of signaling with the 729 Pwid FEC element with LDP signaling. 730 'genFecSignaling' is used in case of LDP signaling with 731 the generalized FEC. 732 'l2tpControlProtocol' indicates the use of L2TP 733 control protocol. 734 'other' is used for other types of signaling." 735 ::= { pwEntry 3 } 737 pwPsnType OBJECT-TYPE 738 SYNTAX IANAPwPsnTypeTC 739 MAX-ACCESS read-create 740 STATUS current 741 DESCRIPTION 742 "This object is set by the operator to indicate the PSN type. 743 Based on this object, the relevant PSN table's entry is 744 created in the PSN specific MIB modules. 745 " 746 ::= { pwEntry 4 } 748 pwSetUpPriority OBJECT-TYPE 749 SYNTAX Integer32 (0..7) 750 MAX-ACCESS read-create 751 STATUS current 752 DESCRIPTION 753 "This object defines the relative priority of the PW 754 during set-up in a lowest-to-highest fashion, where 0 755 is the highest priority. PWs with the same priority 756 are treated with equal priority. PW that have not yet 757 succeeded to set-up will report 'dormant' in the 758 pwOperStatus. 759 This value is significant if there are competing resources 760 among PWs and the implementation support this feature. 761 Equal priority handling with competing resources is 762 implementation specific. 763 This object MAY be changed at any time." 764 DEFVAL { 0 } 765 ::= { pwEntry 5 } 767 pwHoldingPriority OBJECT-TYPE 768 SYNTAX Integer32 (0..7) 769 MAX-ACCESS read-create 770 STATUS current 771 DESCRIPTION 772 "This object defines the relative holding priority of the 773 PW in a lowest-to-highest fashion, where 0 is the highest 774 priority. PWs with the same priority are treated equally. 775 This value is significant if there are competing resources 776 among PWs and the implementation support this feature. 777 Equal priority handling with competing resources is 778 implementation specific. 779 This object MAY be changed only if the PW is not active." 780 DEFVAL { 0 } 781 ::= { pwEntry 6 } 783 pwPeerAddrType OBJECT-TYPE 784 SYNTAX InetAddressType 785 MAX-ACCESS read-create 786 STATUS current 787 DESCRIPTION 788 "Denotes the address type of the peer node. It should be 789 set to 'unknown' if PE/PW maintenance protocol is not used 790 and the address is unknown." 791 DEFVAL { ipv4 } 792 ::= { pwEntry 8 } 794 pwPeerAddr OBJECT-TYPE 795 SYNTAX InetAddress 796 MAX-ACCESS read-create 797 STATUS current 798 DESCRIPTION 799 "This object contains the value of the peer node address 800 of the PW/PE maintenance protocol entity. This object 801 SHOULD contain a value of all zeroes if not applicable 802 (pwPeerAddrType is 'unknown')." 803 ::= { pwEntry 9 } 805 pwAttachedPwIndex OBJECT-TYPE 806 SYNTAX PwIndexOrZeroType 807 MAX-ACCESS read-create 808 STATUS current 809 DESCRIPTION 810 "If the PW is attached to another PW instead of a local 811 native service, this item indicates the pwIndex of the 812 attached PW. Otherwise, this object MUST 813 be set to zero. Attachment to another PW will have no 814 PW specific entry in any of the service MIB modules. " 815 DEFVAL { 0 } 816 ::= { pwEntry 10 } 818 pwIfIndex OBJECT-TYPE 819 SYNTAX InterfaceIndexOrZero 820 MAX-ACCESS read-create 821 STATUS current 822 DESCRIPTION 823 "This object indicates the ifIndex of the PW if the PW is 824 represented in the ifTable. Otherwise, it MUST be set 825 to zero." 826 DEFVAL { 0 } 827 ::= { pwEntry 11 } 829 pwID OBJECT-TYPE 830 SYNTAX PwIDType 831 MAX-ACCESS read-create 832 STATUS current 833 DESCRIPTION 834 "Pseudowire identifier. 836 If the pwOwner object is 'pwIdFecSignaling' or 837 'l2tpControlProtocol', then this object is signaled in the 838 outgoing PW ID field within the 'Virtual Circuit FEC 839 Element'. For other values of pwOwner, this object is not 840 signaled and it MAY be set to zero. 842 For implementations that support the pwIndexMappingTable, 843 a non-zero value is RECOMMENDED, even if this 844 identifier is not signaled. This is so that reverse 845 mappings can be provided by pwIndexMappingTable and 846 pwPeerMappingTable. It is therefore RECOMMENDED that the 847 value of this pwID be unique (or if pwPeerAddrType is not 848 'unknown', at least [pwType,pwID,pwPeerAddrType,pwPeerAddr] 849 is unique.)" 850 REFERENCE 851 "Martini, et al, 'Pseudowire Setup and Maintenance using 852 the Label Distribution Protocol', RFC 4447." 853 ::= { pwEntry 12 } 855 pwLocalGroupID OBJECT-TYPE 856 SYNTAX PwGroupID 857 MAX-ACCESS read-create 858 STATUS current 859 DESCRIPTION 860 "Used in the Group ID field sent to the peer PWES 861 within the maintenance protocol used for PW setup. 862 It SHOULD be set to zero if maintenance protocol is 863 not used." 864 REFERENCE 865 "Martini, et al, 'Pseudowire Setup and Maintenance using 866 the Label Distribution Protocol', RFC 4447." 867 ::= { pwEntry 13 } 869 pwGroupAttachmentID OBJECT-TYPE 870 SYNTAX PwAttachmentIdentifierType 871 MAX-ACCESS read-create 872 STATUS current 873 DESCRIPTION 874 "This object is an octet string representing the attachment 875 group identifier (AGI) that this PW belongs too, which 876 typically identifies the VPN ID. 877 Applicable if pwOwner equal 'genFecSignaling'." 878 REFERENCE 879 "Martini, et al, 'Pseudowire Setup and Maintenance using 880 the Label Distribution Protocol', RFC 4447." 881 ::= { pwEntry 14 } 883 pwLocalAttachmentID OBJECT-TYPE 884 SYNTAX PwAttachmentIdentifierType 885 MAX-ACCESS read-create 886 STATUS current 887 DESCRIPTION 888 "This object is an octet string representing the local 889 forwarder attachment individual identifier (AII) to be 890 used by this PW. It is used as the SAII for outgoing 891 signaling messages and the TAII in the incoming messages 892 from the peer. 893 Applicable if pwOwner equal 'genFecSignaling'." 894 REFERENCE 895 "Martini, et al, 'Pseudowire Setup and Maintenance using 896 the Label Distribution Protocol', RFC 4447." 897 ::= { pwEntry 15 } 899 pwRemoteAttachmentID OBJECT-TYPE 900 SYNTAX PwAttachmentIdentifierType 901 MAX-ACCESS read-create 902 STATUS current 903 DESCRIPTION 904 "This object is an octet string representing the remote 905 forwarder attachment individual identifier (AII) to be 906 used by this PW. It is used as the TAII for outgoing 907 signaling messages and the SAII in the incoming messages 908 from the peer. 909 Applicable if pwOwner equal 'genFecSignaling'." 910 REFERENCE 911 "Martini, et al, 'Pseudowire Setup and Maintenance using 912 the Label Distribution Protocol', RFC 4447." 913 ::= { pwEntry 16 } 915 pwCwPreference OBJECT-TYPE 916 SYNTAX TruthValue 917 MAX-ACCESS read-create 918 STATUS current 919 DESCRIPTION 920 "Defines if the control word will be sent with each packet 921 by the local node. Some PW types mandate the use of a 922 control word, and in such cases the value configured for 923 this object has no effect on the existence of the control 924 word. 925 This object MAY be changed only if the PW is not active." 926 REFERENCE 927 "Martini, et al, 'Pseudowire Setup and Maintenance using 928 the Label Distribution Protocol.', RFC 4447." 929 DEFVAL { false } 930 ::= { pwEntry 17 } 932 pwLocalIfMtu OBJECT-TYPE 933 SYNTAX Unsigned32 (0..65535) 934 MAX-ACCESS read-create 935 STATUS current 936 DESCRIPTION 937 "If not equal to zero, the optional IfMtu object in the 938 signaling protocol will be sent with this value, which 939 represents the locally-supported MTU size over the 940 interface (or the virtual interface) associated with the 941 PW. 942 This object MAY be changed only if the PW is not active." 943 REFERENCE 944 "Martini, et al, 'Pseudowire Setup and Maintenance using 945 the Label Distribution Protocol', RFC 4447." 946 DEFVAL { 0 } 947 ::= { pwEntry 18 } 949 pwLocalIfString OBJECT-TYPE 950 SYNTAX TruthValue 951 MAX-ACCESS read-create 952 STATUS current 953 DESCRIPTION 954 "A PW MAY be associated to an interface (or a virtual 955 interface) in the ifTable of the node as part of the 956 service configuration. This object defines if the 957 maintenance protocol will send the interface's name 958 (ifAlias) as appears in the ifTable. If set to false, 959 the optional element will not be sent. 960 This object MAY be changed only if the PW is not active." 961 REFERENCE 962 "Martini, et al, 'Pseudowire Setup and Maintenance using 963 the Label Distribution Protocol', RFC 4447, section 5.5." 964 DEFVAL { false } 965 ::= { pwEntry 19 } 967 pwLocalCapabAdvert OBJECT-TYPE 968 SYNTAX IANAPwCapabilities 969 MAX-ACCESS read-create 970 STATUS current 971 DESCRIPTION 972 "If maintenance protocol is used, it indicates the 973 capabilities the local node will advertise to the 974 peer. The operator MAY selectively assign partial set 975 of capabilities. In case of manual configuration of the PW, 976 the operator SHOULD set non conflicting options (for example 977 only a single type of OAM) out of the available options 978 in the implementation. 979 It is possible to change the value of this object when the 980 PW is not active. The agent MUST reject any attempt to set 981 a capability that is not supported. 983 The default value MUST be the full set of local node 984 capabilities." 985 REFERENCE 986 "Martini, et al, 'Pseudowire Setup and Maintenance using 987 the Label Distribution Protocol', RFC 4447." 988 ::= { pwEntry 20 } 990 pwRemoteGroupID OBJECT-TYPE 991 SYNTAX PwGroupID 992 MAX-ACCESS read-only 993 STATUS current 994 DESCRIPTION 995 "This object is obtained from the Group ID field as 996 received via the maintenance protocol used for PW setup. 997 Value zero will be reported if not used. 998 Value of 0xFFFFFFFF shall be used if the object is yet to be 999 defined by the PW maintenance protocol." 1000 REFERENCE 1001 "Martini, et al, 'Pseudowire Setup and Maintenance using 1002 the Label Distribution Protocol', RFC 4447." 1003 ::= { pwEntry 21 } 1005 pwCwStatus OBJECT-TYPE 1006 SYNTAX PwCwStatusTC 1007 MAX-ACCESS read-only 1008 STATUS current 1009 DESCRIPTION 1010 "If signaling is used for PW establishment, this object 1011 indicates the status of the control word negotiation, 1012 and in both; signaling or manual configuration it indicates 1013 if CW is to be present for this PW." 1014 REFERENCE 1015 "Martini, et al, 'Pseudowire Setup and Maintenance using 1016 the Label Distribution Protocol', RFC 4447." 1017 ::= { pwEntry 22 } 1019 pwRemoteIfMtu OBJECT-TYPE 1020 SYNTAX Unsigned32 1021 MAX-ACCESS read-only 1022 STATUS current 1023 DESCRIPTION 1024 "The remote interface MTU as (optionally) received from the 1025 remote node via the maintenance protocol. The object SHOULD 1026 report zero if MTU is not available." 1027 REFERENCE 1028 "Martini, et al, 'Pseudowire Setup and Maintenance using 1029 the Label Distribution Protocol', RFC 4447." 1030 ::= { pwEntry 23 } 1032 pwRemoteIfString OBJECT-TYPE 1033 SYNTAX SnmpAdminString (SIZE (0..80)) 1034 MAX-ACCESS read-only 1035 STATUS current 1036 DESCRIPTION 1037 "Indicates the interface description string as received by 1038 the maintenance protocol. It MUST be a NULL string if 1039 maintenance protocol is not used or the value is not known 1040 yet." 1041 REFERENCE 1042 "Martini, et al, 'Pseudowire Setup and Maintenance using 1043 the Label Distribution Protocol', RFC 4447, section 5.5." 1044 ::= { pwEntry 24 } 1046 pwRemoteCapabilities OBJECT-TYPE 1047 SYNTAX IANAPwCapabilities 1048 MAX-ACCESS read-only 1049 STATUS current 1050 DESCRIPTION 1051 "Indicates the capabilities as received from the peer." 1052 REFERENCE 1053 "Martini, et al, 'Pseudowire Setup and Maintenance using 1054 the Label Distribution Protocol', RFC 4447." 1055 ::= { pwEntry 25 } 1057 pwFragmentCfgSize OBJECT-TYPE 1058 SYNTAX PwFragSize 1059 UNITS "bytes" 1060 MAX-ACCESS read-create 1061 STATUS current 1062 DESCRIPTION 1063 "If set to a value other than zero, indicates that 1064 fragmentation is desired for this PW. 1065 This object MAY be changed only if the PW is not active." 1066 REFERENCE 1067 "Malis A., Townsley M., 'PWE3 Fragmentation and Reassembly', 1068 RFC 4623." 1069 DEFVAL { 0 } -- i.e. fragmentation not desired 1070 ::= { pwEntry 26 } 1072 pwRmtFragCapability OBJECT-TYPE 1073 SYNTAX PwFragStatus 1074 MAX-ACCESS read-only 1075 STATUS current 1076 DESCRIPTION 1077 "The status of the fragmentation based on the local 1078 configuration and the peer capabilities as received from 1079 the peer when control protocol is used." 1081 REFERENCE 1082 "Malis A., Townsley M., 'PWE3 Fragmentation and Reassembly', 1083 RFC 4623." 1084 ::= { pwEntry 27 } 1086 pwFcsRetentionCfg OBJECT-TYPE 1087 SYNTAX INTEGER { 1088 fcsRetentionDisable (1), 1089 fcsRetentionEnable (2) 1090 } 1091 MAX-ACCESS read-create 1092 STATUS current 1093 DESCRIPTION 1094 "The local configuration of FCS retention for this PW. FCS 1095 retention can be configured for PW types HDLC, PPP and 1096 Ethernet only. If the implementation does not support 1097 FCS retention, error MUST be reported in pwFcsRetentionStatus. 1098 This object MAY be changed only if the PW is not active." 1099 REFERENCE 1100 "Malis A., et al., 'PWE3 Frame Check Sequence Retention', 1101 RFC 4720." 1102 DEFVAL { fcsRetentionDisable } 1103 ::= { pwEntry 28 } 1105 pwFcsRetentionStatus OBJECT-TYPE 1106 SYNTAX BITS { 1107 remoteIndicationUnknown (0), 1108 remoteRequestFcsRetention (1), 1109 fcsRetentionEnabled (2), 1110 fcsRetentionDisabled (3), 1111 localFcsRetentionCfgErr (4), 1112 fcsRetentionFcsSizeMismatch (5) 1113 } 1114 MAX-ACCESS read-only 1115 STATUS current 1116 DESCRIPTION 1117 "The status of the FCS retention negotiation process based on 1118 local configuration and the remote advertisement. 1120 remoteIndicationUnknown - set if a FEC has not been received 1121 from the remote. 1123 remoteRequestFcsRetention - indicates that the peer has 1124 requested for FCS retention. FCS retention will be used if 1125 the local node is capable and configured to use it for this 1126 PW. 1128 fcsRetentionEnabled - FCS retention is enabled (both peers 1129 were configured for FCS retention for signaled PW, or the 1130 local node is configured and capable for FCS retention for 1131 manually assigned PW). 1133 fcsRetentionDisabled - FCS retention is disabled (not 1134 configured locally or not advertised by the peer). 1136 localFcsRetentionCfgErr - Set if the local node has been 1137 configured for FCS retention but is not capable to support 1138 it. 1140 fcsRetentionFcsSizeMismatch - Set if there is an FCS size 1141 mismatch between the local and the peer node. 1142 " 1143 REFERENCE 1144 "Malis A., et al., 'PWE3 Frame Check Sequence Retention', 1145 RFC 4720" 1146 ::= { pwEntry 29 } 1148 pwOutboundLabel OBJECT-TYPE 1149 SYNTAX Unsigned32 1150 MAX-ACCESS read-create 1151 STATUS current 1152 DESCRIPTION 1153 "The PW label used in the outbound direction (i.e. toward 1154 the PSN). It might be set manually if pwOwner is 'manual', 1155 otherwise setting done automatically. 1156 For MPLS, MPLS over IP or MPLS over GRE PSN, it represents 1157 the 20 bits of PW tag, for L2TP it represents the 32 bits 1158 Session ID and for IP PSN it represents the destination 1159 UDP port number. 1160 If the label is not yet known (signaling in process), the 1161 object SHOULD return a value of 0xFFFFFFFF. 1162 For manual configuration, this object MAY be changed only 1163 if the PW is not active." 1164 ::= { pwEntry 30 } 1166 pwInboundLabel OBJECT-TYPE 1167 SYNTAX Unsigned32 1168 MAX-ACCESS read-create 1169 STATUS current 1170 DESCRIPTION 1171 "The PW label used in the inbound direction (i.e. packets 1172 received from the PSN). It may be set manually if pwOwner 1173 is 'manual',otherwise setting done automatically. 1174 For MPLS, MPLS over IP or MPLS over GRE PSN, it represents 1175 the 20 bits of PW tag, for L2TP it represents the 32 bits 1176 Session ID and for IP PSN it represents the source 1177 UDP port number. 1178 If the label is not yet known (signaling in process), the 1179 object SHOULD return a value of 0xFFFFFFFF. 1180 For manual configuration, this object MAY be changed only 1181 if the PW is not active." 1182 ::= { pwEntry 31 } 1184 pwName OBJECT-TYPE 1185 SYNTAX SnmpAdminString 1186 MAX-ACCESS read-create 1187 STATUS current 1188 DESCRIPTION 1189 "The canonical name assigned to the PW. This object MAY be 1190 changed at any time." 1191 ::= { pwEntry 32 } 1193 pwDescr OBJECT-TYPE 1194 SYNTAX SnmpAdminString 1195 MAX-ACCESS read-create 1196 STATUS current 1197 DESCRIPTION 1198 "A textual string containing information about the PW. 1199 If there is no description this object contains a zero 1200 length string. This object MAY be changed at any time." 1201 ::= { pwEntry 33 } 1203 pwCreateTime OBJECT-TYPE 1204 SYNTAX TimeStamp 1205 MAX-ACCESS read-only 1206 STATUS current 1207 DESCRIPTION 1208 "The value of sysUpTime at the time this PW was created." 1209 ::= { pwEntry 34 } 1211 pwUpTime OBJECT-TYPE 1212 SYNTAX TimeTicks 1213 MAX-ACCESS read-only 1214 STATUS current 1215 DESCRIPTION 1216 "Specifies the time since last change of pwOperStatus to 1217 Up(1)." 1218 ::= { pwEntry 35 } 1220 pwLastChange OBJECT-TYPE 1221 SYNTAX TimeTicks 1222 MAX-ACCESS read-only 1223 STATUS current 1224 DESCRIPTION 1225 "The value of sysUpTime at the time the PW entered 1226 its current operational state. If the current state was 1227 entered prior to the last re-initialization of the local 1228 network management subsystem, then this object contains a 1229 zero value." 1230 ::= { pwEntry 36 } 1232 pwAdminStatus OBJECT-TYPE 1233 SYNTAX INTEGER { 1234 up(1), -- ready to pass packets 1235 down(2), 1236 testing(3) -- in a test mode 1237 } 1238 MAX-ACCESS read-create 1239 STATUS current 1240 DESCRIPTION 1241 "The desired operational status of this PW. This object MAY 1242 be set at any time." 1243 ::= { pwEntry 37 } 1245 pwOperStatus OBJECT-TYPE 1246 SYNTAX PwOperStatusTC 1247 MAX-ACCESS read-only 1248 STATUS current 1249 DESCRIPTION 1250 "This object indicates the operational status of the PW, it 1251 does not reflect the status of the CE bound interface. 1252 It is set to down only if pwNotForwarding, 1253 psnFacingPwRxFault, or psnFacingPwTxFault indications are 1254 set in pwLocalStatus or pwRemoteStatus. 1255 It indicates 'lowerLayerDown' if the only reason for 1256 not being in the 'up' state is either outer tunnel 1257 or physical layer down of the network side is in the down 1258 state. 1259 All other states are declared based on the description in 1260 the textual convention. 1261 " 1262 ::= { pwEntry 38 } 1264 pwLocalStatus OBJECT-TYPE 1265 SYNTAX PwStatus 1266 MAX-ACCESS read-only 1267 STATUS current 1268 DESCRIPTION 1269 "Indicates the status of the PW in the local node. 1270 The various indications in this object SHOULD be 1271 available independent of the ability of the local node to 1272 advertise them or the remote node to accept these status 1273 indications through the control protocol. 1274 " 1275 ::= { pwEntry 39 } 1277 pwRemoteStatusCapable OBJECT-TYPE 1278 SYNTAX INTEGER { 1279 notApplicable (1), 1280 notYetKnown (2), 1281 remoteCapable (3), 1282 remoteNotCapable (4) 1283 } 1284 MAX-ACCESS read-only 1285 STATUS current 1286 DESCRIPTION 1287 "Indicates the remote node capability to advertise the 1288 PW status notification. 1289 notAppicable SHOULD be reported for manually set PW, or 1290 if the local node is not capable of accepting the status 1291 notification object. 1292 notYetKnown SHOULD be reported if the signaling protocol 1293 has not yet finished the process of capability 1294 determination. 1295 remoteCapable and remoteNotcapable SHOULD be reported 1296 based on the initial signaling exchange that has 1297 determined the remote node capability. 1298 " 1299 ::= { pwEntry 40 } 1301 pwRemoteStatus OBJECT-TYPE 1302 SYNTAX PwStatus 1303 MAX-ACCESS read-only 1304 STATUS current 1305 DESCRIPTION 1306 "Indicates the status of the PW as was advertised by the 1307 remote. If the remote is not capable of advertising the 1308 status object, or the local node is not able to accept 1309 the status object through signaling, then the applicable 1310 bit is 'pwNotForwarding' which is set if the remote has 1311 sent label release or label withdraw for this PW. 1312 " 1313 ::= { pwEntry 41 } 1315 pwTimeElapsed OBJECT-TYPE 1316 SYNTAX HCPerfTimeElapsed 1317 MAX-ACCESS read-only 1318 STATUS current 1319 DESCRIPTION 1320 "The number of seconds, including partial seconds, 1321 that have elapsed since the beginning of the current 1322 interval measurement period." 1323 ::= { pwEntry 42 } 1325 pwValidIntervals OBJECT-TYPE 1326 SYNTAX HCPerfValidIntervals 1327 MAX-ACCESS read-only 1328 STATUS current 1329 DESCRIPTION 1330 "The number of previous 15-minute intervals 1331 for which data was collected." 1332 ::= { pwEntry 43 } 1334 pwRowStatus OBJECT-TYPE 1335 SYNTAX RowStatus 1336 MAX-ACCESS read-create 1337 STATUS current 1338 DESCRIPTION 1339 "For creating, modifying, and deleting this row. 1340 This object MAY be changed at any time." 1341 ::= { pwEntry 44 } 1343 pwStorageType OBJECT-TYPE 1344 SYNTAX StorageType 1345 MAX-ACCESS read-create 1346 STATUS current 1347 DESCRIPTION 1348 "This variable indicates the storage type for this 1349 object." 1350 DEFVAL { nonVolatile } 1351 ::= { pwEntry 45 } 1353 pwOamEnable OBJECT-TYPE 1354 SYNTAX TruthValue 1355 MAX-ACCESS read-create 1356 STATUS current 1357 DESCRIPTION 1358 "This variable indicates if OAM is enabled for this 1359 PW. It MAY be changed at any time." 1360 DEFVAL { true } 1361 ::= { pwEntry 46 } 1363 pwGenAGIType OBJECT-TYPE 1364 SYNTAX PwGenIdType 1365 MAX-ACCESS read-create 1366 STATUS current 1367 DESCRIPTION 1368 "This variable indicates the AGI type if generalized FEC 1369 (129) is used for PW signaling or configuration. It SHOULD 1370 return the value of zero otherwise." 1371 DEFVAL { 0 } 1372 ::= { pwEntry 47 } 1374 pwGenLocalAIIType OBJECT-TYPE 1375 SYNTAX PwGenIdType 1376 MAX-ACCESS read-create 1377 STATUS current 1378 DESCRIPTION 1379 "This object is the type of the local forwarder 1380 attachment individual identifier (AII) to be used 1381 by this PW if generalized FEC (129) is used for PW 1382 signaling or configuration." 1383 DEFVAL { 0 } 1384 ::= { pwEntry 48 } 1386 pwGenRemoteAIIType OBJECT-TYPE 1387 SYNTAX PwGenIdType 1388 MAX-ACCESS read-create 1389 STATUS current 1390 DESCRIPTION 1391 "This object is the type of the remote forwarder 1392 attachment individual identifier (AII) to be used 1393 by this PW if generalized FEC (129) is used for PW 1394 signaling or configuration." 1395 DEFVAL { 0 } 1396 ::= { pwEntry 49 } 1398 -- End of PW Virtual Connection Table 1400 -- PW Performance Table. 1402 pwPerfCurrentTable OBJECT-TYPE 1403 SYNTAX SEQUENCE OF PwPerfCurrentEntry 1404 MAX-ACCESS not-accessible 1405 STATUS current 1406 DESCRIPTION 1407 "This table provides per-PW performance information for 1408 the current interval." 1409 ::= { pwObjects 3 } 1411 pwPerfCurrentEntry OBJECT-TYPE 1412 SYNTAX PwPerfCurrentEntry 1413 MAX-ACCESS not-accessible 1414 STATUS current 1415 DESCRIPTION 1416 "An entry in this table is created by the agent for 1417 every PW." 1418 INDEX { pwIndex } 1419 ::= { pwPerfCurrentTable 1 } 1421 PwPerfCurrentEntry ::= SEQUENCE { 1422 pwPerfCurrentInHCPackets HCPerfCurrentCount, 1423 pwPerfCurrentInHCBytes HCPerfCurrentCount, 1424 pwPerfCurrentOutHCPackets HCPerfCurrentCount, 1425 pwPerfCurrentOutHCBytes HCPerfCurrentCount, 1426 pwPerfCurrentInPackets PerfCurrentCount, 1427 pwPerfCurrentInBytes PerfCurrentCount, 1428 pwPerfCurrentOutPackets PerfCurrentCount, 1429 pwPerfCurrentOutBytes PerfCurrentCount 1430 } 1432 pwPerfCurrentInHCPackets OBJECT-TYPE 1433 SYNTAX HCPerfCurrentCount 1434 MAX-ACCESS read-only 1435 STATUS current 1436 DESCRIPTION 1437 "High capacity counter for number of packets received by 1438 the PW (from the PSN) in the current 15-minute interval. 1439 This is the 64 bit version of pwPerfCurrentInPackets, 1440 if pwPerfCurrentInHCPackets is supported according to 1441 the rules spelled out in RFC2863." 1442 ::= { pwPerfCurrentEntry 1 } 1444 pwPerfCurrentInHCBytes OBJECT-TYPE 1445 SYNTAX HCPerfCurrentCount 1446 MAX-ACCESS read-only 1447 STATUS current 1448 DESCRIPTION 1449 "High capacity counter for number of bytes received by the 1450 PW (from the PSN) in the current 15-minute interval. 1451 This is the 64 bit version of pwPerfCurrentInBytes, if 1452 pwPerfCurrentInHCBytes is supported according to the 1453 rules spelled out in RFC2863." 1454 ::= { pwPerfCurrentEntry 2 } 1456 pwPerfCurrentOutHCPackets OBJECT-TYPE 1457 SYNTAX HCPerfCurrentCount 1458 MAX-ACCESS read-only 1459 STATUS current 1460 DESCRIPTION 1461 "High capacity counter for number of packets forwarded by 1462 the PW (to the PSN) in the current 15-minute interval. 1464 This is the 64 bit version of pwPerfCurrentOutPackets, 1465 if pwPerfCurrentOutHCPackets is supported according to 1466 the rules spelled out in RFC2863." 1467 ::= { pwPerfCurrentEntry 3 } 1469 pwPerfCurrentOutHCBytes OBJECT-TYPE 1470 SYNTAX HCPerfCurrentCount 1471 MAX-ACCESS read-only 1472 STATUS current 1473 DESCRIPTION 1474 "High capacity counter for number of bytes forwarded by 1475 the PW (to the PSN) in the current 15-minute interval. 1476 This is the 64 bit version of pwPerfCurrentOutBytes, 1477 if pwPerfCurrentOutHCBytes is supported according to 1478 the rules spelled out in RFC2863." 1479 ::= { pwPerfCurrentEntry 4 } 1481 pwPerfCurrentInPackets OBJECT-TYPE 1482 SYNTAX PerfCurrentCount 1483 MAX-ACCESS read-only 1484 STATUS current 1485 DESCRIPTION 1486 "The counter for number of packets received by the PW (from 1487 the PSN) in the current 15-minute interval. 1488 This is the 32 bit version of pwPerfCurrentInHCPackets, 1489 if pwPerfCurrentInHCPackets is supported according to 1490 the rules spelled out in RFC2863." 1491 ::= { pwPerfCurrentEntry 5 } 1493 pwPerfCurrentInBytes OBJECT-TYPE 1494 SYNTAX PerfCurrentCount 1495 MAX-ACCESS read-only 1496 STATUS current 1497 DESCRIPTION 1498 "The counter for number of bytes received by the 1499 PW (from the PSN) in the current 15-minute interval. 1500 It MUST be equal to the least significant 32 bits of 1501 pwPerfCurrentInHCBytes, if pwPerfCurrentInHCBytes is 1502 supported according to the rules spelled out in RFC2863." 1503 ::= { pwPerfCurrentEntry 6 } 1505 pwPerfCurrentOutPackets OBJECT-TYPE 1506 SYNTAX PerfCurrentCount 1507 MAX-ACCESS read-only 1508 STATUS current 1509 DESCRIPTION 1510 "The counter for number of packets forwarded by 1511 the PW (to the PSN) in the current 15-minute interval. 1513 It MUST be equal to the least significant 32 bits of 1514 pwPerfCurrentOutHCPackets, if 1515 pwPerfCurrentOutHCPackets is supported according to the 1516 rules spelled out in RFC2863." 1517 ::= { pwPerfCurrentEntry 7 } 1519 pwPerfCurrentOutBytes OBJECT-TYPE 1520 SYNTAX PerfCurrentCount 1521 MAX-ACCESS read-only 1522 STATUS current 1523 DESCRIPTION 1524 "The counter for number of bytes forwarded by 1525 the PW (to the PSN) in the current 15-minute interval. 1526 It MUST be equal to the least significant 32 bits of 1527 pwPerfCurrentOutHCBytes, if pwPerfCurrentOutHCBytes is 1528 supported according to the rules spelled out in RFC2863." 1529 ::= { pwPerfCurrentEntry 8 } 1531 -- End of PW Perf current Table 1533 -- PW Performance Interval Table. 1535 pwPerfIntervalTable OBJECT-TYPE 1536 SYNTAX SEQUENCE OF PwPerfIntervalEntry 1537 MAX-ACCESS not-accessible 1538 STATUS current 1539 DESCRIPTION 1540 "This table provides per-PW performance information for 1541 each interval." 1542 ::= { pwObjects 4 } 1544 pwPerfIntervalEntry OBJECT-TYPE 1545 SYNTAX PwPerfIntervalEntry 1546 MAX-ACCESS not-accessible 1547 STATUS current 1548 DESCRIPTION 1549 "An entry in this table is created by the agent for every 1550 PW." 1551 INDEX { pwIndex, pwPerfIntervalNumber } 1552 ::= { pwPerfIntervalTable 1 } 1554 PwPerfIntervalEntry ::= SEQUENCE { 1555 pwPerfIntervalNumber Integer32, 1556 pwPerfIntervalValidData TruthValue, 1557 pwPerfIntervalTimeElapsed HCPerfTimeElapsed, 1558 pwPerfIntervalInHCPackets HCPerfIntervalCount, 1559 pwPerfIntervalInHCBytes HCPerfIntervalCount, 1560 pwPerfIntervalOutHCPackets HCPerfIntervalCount, 1561 pwPerfIntervalOutHCBytes HCPerfIntervalCount, 1562 pwPerfIntervalInPackets PerfIntervalCount, 1563 pwPerfIntervalInBytes PerfIntervalCount, 1564 pwPerfIntervalOutPackets PerfIntervalCount, 1565 pwPerfIntervalOutBytes PerfIntervalCount 1566 } 1568 pwPerfIntervalNumber OBJECT-TYPE 1569 SYNTAX Integer32 (1..96) 1570 MAX-ACCESS not-accessible 1571 STATUS current 1572 DESCRIPTION 1573 "A number N, between 1 and 96, which identifies the 1574 interval for which the set of statistics is available. 1575 The interval identified by 1 is the most recently 1576 completed 15 minute interval, and the interval identified 1577 by N is the interval immediately preceding the one 1578 identified by N-1. 1579 The minimum range of N is 1 through 4. The default range 1580 is 1 to 32. The maximum range of N is 1 through 96. " 1581 REFERENCE 1582 "Tesink, K. 'Definitions of Managed Objects for the 1583 SONET/SDH Interface Type', RFC 2558" 1584 ::= { pwPerfIntervalEntry 1 } 1586 pwPerfIntervalValidData OBJECT-TYPE 1587 SYNTAX TruthValue 1588 MAX-ACCESS read-only 1589 STATUS current 1590 DESCRIPTION 1591 "This variable indicates if the data for this interval 1592 is valid." 1593 ::= { pwPerfIntervalEntry 2 } 1595 pwPerfIntervalTimeElapsed OBJECT-TYPE 1596 SYNTAX HCPerfTimeElapsed 1597 MAX-ACCESS read-only 1598 STATUS current 1599 DESCRIPTION 1600 "The duration of this interval in seconds." 1601 ::= { pwPerfIntervalEntry 3 } 1603 pwPerfIntervalInHCPackets OBJECT-TYPE 1604 SYNTAX HCPerfIntervalCount 1605 MAX-ACCESS read-only 1606 STATUS current 1607 DESCRIPTION 1608 "High capacity counter for number of packets received by 1609 the PW (from the PSN) during the interval. This is the 64 1610 bit version of pwPerfIntervalInPackets, if 1611 pwPerfIntervalInHCPackets is supported according to the 1612 rules spelled out in RFC2863." 1613 ::= { pwPerfIntervalEntry 4 } 1615 pwPerfIntervalInHCBytes OBJECT-TYPE 1616 SYNTAX HCPerfIntervalCount 1617 MAX-ACCESS read-only 1618 STATUS current 1619 DESCRIPTION 1620 "High capacity counter for number of bytes received by the 1621 PW (from the PSN) during the interval. 1622 This is the 64 bit version of pwPerfIntervalInBytes, if 1623 pwPerfIntervalInHCBytes is supported according to the 1624 rules spelled out in RFC2863." 1625 ::= { pwPerfIntervalEntry 5 } 1627 pwPerfIntervalOutHCPackets OBJECT-TYPE 1628 SYNTAX HCPerfIntervalCount 1629 MAX-ACCESS read-only 1630 STATUS current 1631 DESCRIPTION 1632 "High capacity counter for number of packets forwarded by 1633 the PW (to the PSN) during the interval. 1634 This is the 64 bit version of pwPerfIntervalOutPackets, 1635 if pwPerfIntervalOutHCPackets is supported according to 1636 the rules spelled out in RFC2863." 1637 ::= { pwPerfIntervalEntry 6 } 1639 pwPerfIntervalOutHCBytes OBJECT-TYPE 1640 SYNTAX HCPerfIntervalCount 1641 MAX-ACCESS read-only 1642 STATUS current 1643 DESCRIPTION 1644 "High capacity counter for number of bytes forwarded by 1645 the PW (to the PSN) during the interval. 1646 This is the 64 bit version of pwPerfIntervalOutBytes, 1647 if pwPerfIntervalOutHCBytes is supported according to 1648 the rules spelled out in RFC2863." 1649 ::= { pwPerfIntervalEntry 7 } 1651 pwPerfIntervalInPackets OBJECT-TYPE 1652 SYNTAX PerfIntervalCount 1653 MAX-ACCESS read-only 1654 STATUS current 1655 DESCRIPTION 1656 "This value represents the number of packets received 1657 by this PW during the interval. 1658 It MUST be equal to the least significant 32 bits of 1659 pwPerfIntervalInHCPackets if pwPerfIntervalInHCPackets 1660 is supported according to the rules spelled out in 1661 RFC2863." 1662 ::= { pwPerfIntervalEntry 8 } 1664 pwPerfIntervalInBytes OBJECT-TYPE 1665 SYNTAX PerfIntervalCount 1666 MAX-ACCESS read-only 1667 STATUS current 1668 DESCRIPTION 1669 "This value represents the number of bytes received 1670 by this PW during the interval. 1671 It MUST be equal to the least significant 32 bits of 1672 if pwPerfIntervalInHCBytes is supported according to 1673 the rules spelled out in RFC2863." 1674 ::= { pwPerfIntervalEntry 9 } 1676 pwPerfIntervalOutPackets OBJECT-TYPE 1677 SYNTAX PerfIntervalCount 1678 MAX-ACCESS read-only 1679 STATUS current 1680 DESCRIPTION 1681 "This value represents the number of packets sent by this 1682 PW during the interval. 1683 It MUST be equal to the least significant 32 bits of 1684 pwPerfIntervalOutHCPackets if 1685 pwPerfIntervalOutHCPackets is supported according to the 1686 rules spelled out in RFC2863." 1687 ::= { pwPerfIntervalEntry 10 } 1689 pwPerfIntervalOutBytes OBJECT-TYPE 1690 SYNTAX PerfIntervalCount 1691 MAX-ACCESS read-only 1692 STATUS current 1693 DESCRIPTION 1694 "This value represents the number of bytes sent by this 1695 PW during the interval. 1696 It MUST be equal to the least significant 32 1697 bits of pwPerfIntervalOutHCBytes 1698 if pwPerfIntervalOutHCBytes is supported according to 1699 the rules spelled out in RFC2863." 1700 ::= { pwPerfIntervalEntry 11 } 1702 -- End of PW Performance Interval Table 1703 -- PW Performance 1 Day Interval Table. 1705 pwPerf1DayIntervalTable OBJECT-TYPE 1706 SYNTAX SEQUENCE OF PwPerf1DayIntervalEntry 1707 MAX-ACCESS not-accessible 1708 STATUS current 1709 DESCRIPTION 1710 "This table provides per-PW Performance information for 1711 the current day measurement and the previous days interval." 1712 ::= { pwObjects 5 } 1714 pwPerf1DayIntervalEntry OBJECT-TYPE 1715 SYNTAX PwPerf1DayIntervalEntry 1716 MAX-ACCESS not-accessible 1717 STATUS current 1718 DESCRIPTION 1719 "An entry in this table is created by the agent for every 1720 PW." 1721 INDEX { pwIndex, pwPerf1DayIntervalNumber } 1723 ::= { pwPerf1DayIntervalTable 1 } 1725 PwPerf1DayIntervalEntry ::= SEQUENCE { 1726 pwPerf1DayIntervalNumber Unsigned32, 1727 pwPerf1DayIntervalValidData TruthValue, 1728 pwPerf1DayIntervalTimeElapsed HCPerfTimeElapsed, 1729 pwPerf1DayIntervalInHCPackets Counter64, 1730 pwPerf1DayIntervalInHCBytes Counter64, 1731 pwPerf1DayIntervalOutHCPackets Counter64, 1732 pwPerf1DayIntervalOutHCBytes Counter64 1733 } 1735 pwPerf1DayIntervalNumber OBJECT-TYPE 1736 SYNTAX Unsigned32(1..31) 1737 MAX-ACCESS not-accessible 1738 STATUS current 1739 DESCRIPTION 1740 "History Data Interval number. Interval 1 is the current day 1741 measurement period, interval 2 is the most recent previous 1742 day, and interval 30 is 31 days ago. Intervals 3..31 are 1743 optional." 1744 ::= { pwPerf1DayIntervalEntry 1 } 1746 pwPerf1DayIntervalValidData OBJECT-TYPE 1747 SYNTAX TruthValue 1748 MAX-ACCESS read-only 1749 STATUS current 1750 DESCRIPTION 1751 "This variable indicates if the data for this interval 1752 is valid." 1753 ::= { pwPerf1DayIntervalEntry 2 } 1755 pwPerf1DayIntervalTimeElapsed OBJECT-TYPE 1756 SYNTAX HCPerfTimeElapsed 1757 UNITS "seconds" 1758 MAX-ACCESS read-only 1759 STATUS current 1760 DESCRIPTION 1761 "The number of seconds in the 1-day interval over which the 1762 performance monitoring information is actually counted. 1763 This value will be the same as the interval duration except 1764 in a situation where performance monitoring data could not 1765 be collected for any reason or agent clock adjustments." 1766 ::= { pwPerf1DayIntervalEntry 3 } 1768 pwPerf1DayIntervalInHCPackets OBJECT-TYPE 1769 SYNTAX Counter64 1770 MAX-ACCESS read-only 1771 STATUS current 1772 DESCRIPTION 1773 "High capacity counter for the total number of packets 1774 received by the PW (from the PSN)." 1775 ::= { pwPerf1DayIntervalEntry 4 } 1777 pwPerf1DayIntervalInHCBytes OBJECT-TYPE 1778 SYNTAX Counter64 1779 MAX-ACCESS read-only 1780 STATUS current 1781 DESCRIPTION 1782 "High capacity counter for the total number of bytes 1783 received by the PW (from the PSN)." 1784 ::= { pwPerf1DayIntervalEntry 5 } 1786 pwPerf1DayIntervalOutHCPackets OBJECT-TYPE 1787 SYNTAX Counter64 1788 MAX-ACCESS read-only 1789 STATUS current 1790 DESCRIPTION 1791 "High capacity counter for the total number of packets 1792 forwarded by the PW (to the PSN)." 1793 ::= { pwPerf1DayIntervalEntry 6 } 1795 pwPerf1DayIntervalOutHCBytes OBJECT-TYPE 1796 SYNTAX Counter64 1797 MAX-ACCESS read-only 1798 STATUS current 1799 DESCRIPTION 1800 "High capacity counter for the total number of bytes 1801 forwarded by the PW (to the PSN)." 1802 ::= { pwPerf1DayIntervalEntry 7 } 1804 -- End of PW Perf 1 Day Interval Table 1806 -- Error counter scalar 1808 pwPerfTotalErrorPackets OBJECT-TYPE 1809 SYNTAX Counter32 1810 MAX-ACCESS read-only 1811 STATUS current 1812 DESCRIPTION 1813 "Counter for number of error at the PW processing level, 1814 for example packets received with unknown PW label." 1815 ::= { pwObjects 6 } 1817 -- Reverse mapping tables 1819 -- The PW ID mapping table 1820 pwIndexMappingTable OBJECT-TYPE 1821 SYNTAX SEQUENCE OF PwIndexMappingEntry 1822 MAX-ACCESS not-accessible 1823 STATUS current 1824 DESCRIPTION 1825 "This table enables the reverse mapping the unique PWid 1826 parameters [peer IP, PW type and PW ID] and the 1827 pwIndex. The table is not applicable for PW created 1828 manually or by using the generalized FEC." 1829 ::= { pwObjects 7 } 1831 pwIndexMappingEntry OBJECT-TYPE 1832 SYNTAX PwIndexMappingEntry 1833 MAX-ACCESS not-accessible 1834 STATUS current 1835 DESCRIPTION 1836 "An entry in this table MUST be created by the agent for 1837 every PW created by the pwTable for which pwOwner 1838 equals pwIdFecSignaling and pwID is not zero. 1840 Implementers need to be aware that if the value of 1841 the pwIndexMappingPeerAddr (an OID) has more than 1842 113 sub-identifiers, then OIDs of column instances 1843 in this table will have more than 128 sub-identifiers 1844 and cannot be accessed using SNMPv1, SNMPv2c, or SNMPv3." 1845 INDEX { pwIndexMappingPwType, pwIndexMappingPwID, 1846 pwIndexMappingPeerAddrType, pwIndexMappingPeerAddr 1847 } 1848 ::= { pwIndexMappingTable 1 } 1850 PwIndexMappingEntry ::= SEQUENCE { 1851 pwIndexMappingPwType IANAPwTypeTC, 1852 pwIndexMappingPwID PwIDType, 1853 pwIndexMappingPeerAddrType InetAddressType, 1854 pwIndexMappingPeerAddr InetAddress, 1855 pwIndexMappingPwIndex PwIndexType 1856 } 1858 pwIndexMappingPwType OBJECT-TYPE 1859 SYNTAX IANAPwTypeTC 1860 MAX-ACCESS not-accessible 1861 STATUS current 1862 DESCRIPTION 1863 "The PW type (indicates the service) of this PW." 1864 ::= { pwIndexMappingEntry 1 } 1866 pwIndexMappingPwID OBJECT-TYPE 1867 SYNTAX PwIDType 1868 MAX-ACCESS not-accessible 1869 STATUS current 1870 DESCRIPTION 1871 "The PW ID of this PW. Zero if the PW is configured 1872 manually." 1873 ::= { pwIndexMappingEntry 2 } 1875 pwIndexMappingPeerAddrType OBJECT-TYPE 1876 SYNTAX InetAddressType 1877 MAX-ACCESS not-accessible 1878 STATUS current 1879 DESCRIPTION 1880 "IP address type of the peer node." 1881 ::= { pwIndexMappingEntry 3 } 1883 pwIndexMappingPeerAddr OBJECT-TYPE 1884 SYNTAX InetAddress 1885 MAX-ACCESS not-accessible 1886 STATUS current 1887 DESCRIPTION 1888 "IP address of the peer node." 1889 ::= { pwIndexMappingEntry 4 } 1891 pwIndexMappingPwIndex OBJECT-TYPE 1892 SYNTAX PwIndexType 1893 MAX-ACCESS read-only 1894 STATUS current 1895 DESCRIPTION 1896 "The value that represents the PW in the pwTable." 1897 ::= { pwIndexMappingEntry 5 } 1899 -- End of the PW ID mapping table 1901 -- The peer mapping table 1903 pwPeerMappingTable OBJECT-TYPE 1904 SYNTAX SEQUENCE OF PwPeerMappingEntry 1905 MAX-ACCESS not-accessible 1906 STATUS current 1907 DESCRIPTION 1908 "This table provides reverse mapping of the existing PW 1909 based on PW type and PW ID ordering. This table is 1910 typically useful for EMS ordered query of existing PWs." 1911 ::= { pwObjects 8 } 1913 pwPeerMappingEntry OBJECT-TYPE 1914 SYNTAX PwPeerMappingEntry 1915 MAX-ACCESS not-accessible 1916 STATUS current 1917 DESCRIPTION 1918 "An entry in this table is created by the agent for every 1919 PW entry in pwTable. 1921 Implementers need to be aware that if the value of the 1922 pwPeerMappingPeerAddr (an OID) has more than 113 1923 sub-identifiers, then OIDs of column instances in this 1924 table will have more than 128 sub-identifiers and cannot 1925 be accessed using SNMPv1, SNMPv2c, or SNMPv3." 1926 INDEX { pwPeerMappingPeerAddrType, pwPeerMappingPeerAddr, 1927 pwPeerMappingPwType, pwPeerMappingPwID } 1929 ::= { pwPeerMappingTable 1 } 1931 PwPeerMappingEntry ::= SEQUENCE { 1932 pwPeerMappingPeerAddrType InetAddressType, 1933 pwPeerMappingPeerAddr InetAddress, 1934 pwPeerMappingPwType IANAPwTypeTC, 1935 pwPeerMappingPwID PwIDType, 1936 pwPeerMappingPwIndex PwIndexType 1937 } 1939 pwPeerMappingPeerAddrType OBJECT-TYPE 1940 SYNTAX InetAddressType 1941 MAX-ACCESS not-accessible 1942 STATUS current 1943 DESCRIPTION 1944 "IP address type of the peer node." 1945 ::= { pwPeerMappingEntry 1 } 1947 pwPeerMappingPeerAddr OBJECT-TYPE 1948 SYNTAX InetAddress 1949 MAX-ACCESS not-accessible 1950 STATUS current 1951 DESCRIPTION 1952 "IP address of the peer node." 1953 ::= { pwPeerMappingEntry 2 } 1955 pwPeerMappingPwType OBJECT-TYPE 1956 SYNTAX IANAPwTypeTC 1957 MAX-ACCESS not-accessible 1958 STATUS current 1959 DESCRIPTION 1960 "The PW type (indicates the emulated service) of this PW." 1961 ::= { pwPeerMappingEntry 3 } 1963 pwPeerMappingPwID OBJECT-TYPE 1964 SYNTAX PwIDType 1965 MAX-ACCESS not-accessible 1966 STATUS current 1967 DESCRIPTION 1968 "The PW ID of this PW. Zero if the PW is configured 1969 manually." 1970 ::= { pwPeerMappingEntry 4 } 1972 pwPeerMappingPwIndex OBJECT-TYPE 1973 SYNTAX PwIndexType 1974 MAX-ACCESS read-only 1975 STATUS current 1976 DESCRIPTION 1977 "The value that represents the PW in the pwTable." 1978 ::= { pwPeerMappingEntry 5 } 1980 -- End of the peer mapping table 1982 -- End of reverse mapping tables 1984 pwUpDownNotifEnable OBJECT-TYPE 1985 SYNTAX TruthValue 1986 MAX-ACCESS read-write 1987 STATUS current 1988 DESCRIPTION 1989 "If this object is set to true(1), then it enables 1990 the emission of pwUp and pwDown 1991 notifications; otherwise these notifications are not 1992 emitted." 1993 REFERENCE 1994 "See also [RFC3413] for explanation that 1995 notifications are under the ultimate control of the 1996 MIB module in this document." 1997 DEFVAL { false } 1998 ::= { pwObjects 9 } 2000 pwDeletedNotifEnable OBJECT-TYPE 2001 SYNTAX TruthValue 2002 MAX-ACCESS read-write 2003 STATUS current 2004 DESCRIPTION 2005 "If this object is set to true(1), then it enables the 2006 emission of pwDeleted notification; otherwise this 2007 notification is not emitted." 2008 REFERENCE 2009 "See also [RFC3413] for explanation that 2010 notifications are under the ultimate control of the 2011 MIB module in this document." 2012 DEFVAL { false } 2013 ::= { pwObjects 10 } 2015 pwNotifRate OBJECT-TYPE 2016 SYNTAX Unsigned32 2017 MAX-ACCESS read-write 2018 STATUS current 2019 DESCRIPTION 2020 "This object defines the maximum number of PW notifications 2021 that can be emitted from the device per second." 2022 ::= { pwObjects 11 } 2024 -- The Gen Fec PW ID mapping table 2026 pwGenFecIndexMappingTable OBJECT-TYPE 2027 SYNTAX SEQUENCE OF PwGenFecIndexMappingEntry 2028 MAX-ACCESS not-accessible 2029 STATUS current 2030 DESCRIPTION 2031 "This table enables the reverse mapping the unique PWid 2032 parameters [GroupAttachmentID, LocalAttachmentID and 2033 PeerAttachmentID] and the pwIndex. The table is only 2034 applicable for PW using the generalized FEC." 2035 ::= { pwObjects 12 } 2037 pwGenFecIndexMappingEntry OBJECT-TYPE 2038 SYNTAX PwGenFecIndexMappingEntry 2039 MAX-ACCESS not-accessible 2040 STATUS current 2041 DESCRIPTION 2042 "An entry in this table MUST be created by the agent for 2043 every PW created by the pwTable for which pwOwner 2044 equals genFecSignaling. 2046 Implementors need to be aware that if the combined value 2047 of pwGenFecIndexMappingAGI, pwGenFecIndexMappingLocalAII, 2048 and pwGenFecIndexMappingRemoteAII (OIDs) has more than 2049 113 sub-identifiers, then OIDs of column instances 2050 in this table will have more than 128 sub-identifiers 2051 and cannot be accessed using SNMPv1, SNMPv2c, or SNMPv3." 2052 INDEX { pwGenFecIndexMappingAGIType, 2053 pwGenFecIndexMappingAGI, 2054 pwGenFecIndexMappingLocalAIIType, 2055 pwGenFecIndexMappingLocalAII, 2056 pwGenFecIndexMappingRemoteAIIType, 2057 pwGenFecIndexMappingRemoteAII 2058 } 2059 ::= { pwGenFecIndexMappingTable 1 } 2061 PwGenFecIndexMappingEntry ::= SEQUENCE { 2062 pwGenFecIndexMappingAGIType PwGenIdType, 2063 pwGenFecIndexMappingAGI PwAttachmentIdentifierType, 2064 pwGenFecIndexMappingLocalAIIType PwGenIdType, 2065 pwGenFecIndexMappingLocalAII PwAttachmentIdentifierType, 2066 pwGenFecIndexMappingRemoteAIIType PwGenIdType, 2067 pwGenFecIndexMappingRemoteAII PwAttachmentIdentifierType, 2068 pwGenFecIndexMappingPwIndex PwIndexType 2069 } 2071 pwGenFecIndexMappingAGIType OBJECT-TYPE 2072 SYNTAX PwGenIdType 2073 MAX-ACCESS not-accessible 2074 STATUS current 2075 DESCRIPTION 2076 "This object is the type of the attachment 2077 group identifier (AGI) that this PW belongs too." 2078 ::= { pwGenFecIndexMappingEntry 1 } 2080 pwGenFecIndexMappingAGI OBJECT-TYPE 2081 SYNTAX PwAttachmentIdentifierType 2082 MAX-ACCESS not-accessible 2083 STATUS current 2084 DESCRIPTION 2085 "This object is an octet string representing the attachment 2086 group identifier (AGI) that this PW belongs too, 2087 which typically identifies the VPN ID." 2088 ::= { pwGenFecIndexMappingEntry 2 } 2090 pwGenFecIndexMappingLocalAIIType OBJECT-TYPE 2091 SYNTAX PwGenIdType 2092 MAX-ACCESS not-accessible 2093 STATUS current 2094 DESCRIPTION 2095 "this object is the type of the local forwarder 2096 attachment individual identifier (AII) to be used 2097 by this PW." 2098 ::= { pwGenFecIndexMappingEntry 3 } 2100 pwGenFecIndexMappingLocalAII OBJECT-TYPE 2101 SYNTAX PwAttachmentIdentifierType 2102 MAX-ACCESS not-accessible 2103 STATUS current 2104 DESCRIPTION 2105 "This object is an octet string representing the local 2106 forwarder attachment individual identifier (AII) to be used 2107 by this PW. It is used as the SAII for outgoing signaling 2108 messages and the TAII in the incoming messages from the 2109 peer." 2110 ::= { pwGenFecIndexMappingEntry 4 } 2112 pwGenFecIndexMappingRemoteAIIType OBJECT-TYPE 2113 SYNTAX PwGenIdType 2114 MAX-ACCESS not-accessible 2115 STATUS current 2116 DESCRIPTION 2117 "This object is the type of the the remote forwarder 2118 attachment individual identifier (AII) to be used 2119 by this PW." 2120 ::= { pwGenFecIndexMappingEntry 5 } 2122 pwGenFecIndexMappingRemoteAII OBJECT-TYPE 2123 SYNTAX PwAttachmentIdentifierType 2124 MAX-ACCESS not-accessible 2125 STATUS current 2126 DESCRIPTION 2127 "This object is an octet string representing the peer 2128 forwarder attachment individual identifier (AII) to be used 2129 by this PW. It is used as the TAII for outgoing signaling 2130 messages and the SAII in the incoming messages from the 2131 peer." 2132 ::= { pwGenFecIndexMappingEntry 6 } 2134 pwGenFecIndexMappingPwIndex OBJECT-TYPE 2135 SYNTAX PwIndexType 2136 MAX-ACCESS read-only 2137 STATUS current 2138 DESCRIPTION 2139 "The value that represents the PW in the pwTable." 2140 ::= { pwGenFecIndexMappingEntry 7 } 2142 -- End of the Gen Fec PW ID mapping table 2144 -- Notifications - PW 2146 pwDown NOTIFICATION-TYPE 2147 OBJECTS { pwOperStatus, --start of range 2148 pwOperStatus --end of range 2149 } 2150 STATUS current 2151 DESCRIPTION 2152 "This notification is generated when the pwOperStatus 2153 object for one or more contiguous entries in pwTable are 2154 about to enter the down(2) or lowerLayerDown(6) state from 2155 any other state, except for transition from the 2156 notPresent(5) state. For the purpose of deciding when 2157 these notifications occur, the lowerLayerDown(6) state 2158 and the down(2) state are considered to be equivalent, 2159 i.e., there is no notification on transition from 2160 lowerLayerDown(6) into down(2), and there is a trap on 2161 transition from any other state except down(2) (and 2162 notPresent) into lowerLayerDown(6). 2164 The included values of pwOperStatus MUST all equal to this 2165 down(2) or lowerLayerDown(6). The two instances of 2166 pwOperStatus in this notification indicate the range of 2167 indexes that are affected. Note that all the indexes of 2168 the two ends of the range can be derived from the 2169 instance identifiers of these two objects. For cases 2170 where a contiguous range of cross-connects have 2171 transitioned into the down(2) and lowerLayerDown(6) state 2172 at roughly the same time, the device SHOULD issue a single 2173 notification for each range of contiguous indexes in an 2174 effort to minimize the emission of a large number of 2175 of notifications. If a notification has to be issued for 2176 just a single cross-connect entry, then the instance 2177 identifier (and values) of the two pwOperStatus objects 2178 MUST be identical." 2179 ::= { pwNotifications 1 } 2181 pwUp NOTIFICATION-TYPE 2182 OBJECTS { pwOperStatus, --start of range 2183 pwOperStatus --end of range 2184 } 2185 STATUS current 2186 DESCRIPTION 2187 "This notification is generated when the pwOperStatus 2188 object for one or more contiguous entries in pwTable are 2189 about to enter the up(1) state from some other state 2190 except the notPresent(5) state and given that the pwDown 2191 notification been issued for these entries. The included 2192 values of pwOperStatus MUST both be set equal to this 2193 new state (i.e: up(1)). The two instances of pwOperStatus 2194 in this notification indicate the range of indexes that 2195 are affected. Note that all the indexes of the two ends 2196 of the range can be derived from the instance identifiers 2197 of these two objects. For cases where a contiguous range 2198 of cross-connects have transitioned into the up(1) state 2199 at roughly the same time, the device SHOULD issue a single 2200 notification for each range of contiguous indexes in an 2201 effort to minimize the emission of a large number of 2202 notifications. If a notification has to be issued for 2203 just a single cross-connect entry, then the instance 2204 identifier (and values) of the two pwOperStatus objects 2205 MUST be the identical." 2206 ::= { pwNotifications 2 } 2208 pwDeleted NOTIFICATION-TYPE 2209 OBJECTS { pwType, 2210 pwID, 2211 pwPeerAddrType, 2212 pwPeerAddr 2213 } 2214 STATUS current 2215 DESCRIPTION 2216 "This notification is generated when the PW has been 2217 deleted, i.e. when the pwRowStatus has been set to 2218 destroy(6), the PW has been deleted by a non-MIB 2219 application or due to auto-discovery process. 2220 " 2221 ::= { pwNotifications 3 } 2223 -- End of notifications. 2225 -- Conformance information 2227 pwGroups OBJECT IDENTIFIER ::= { pwConformance 1 } 2228 pwCompliances OBJECT IDENTIFIER ::= { pwConformance 2 } 2230 -- Compliance requirement for fully compliant implementations. 2232 pwModuleFullCompliance MODULE-COMPLIANCE 2233 STATUS current 2234 DESCRIPTION 2235 "The compliance statement for agents that provide full 2236 support for PW MIB Module. Such devices can 2237 then be monitored and configured using 2238 this MIB module." 2240 MODULE -- this module 2241 MANDATORY-GROUPS { pwBasicGroup, 2242 pwPerformanceGeneralGroup 2243 } 2245 GROUP pwNotificationGroup 2246 DESCRIPTION "This group is only mandatory for implementations 2247 which can efficiently implement the notifications 2248 contained in this group. 2249 " 2251 GROUP pwPwIdGroup 2252 DESCRIPTION "This group is only mandatory for implementations 2253 that support the PW ID FEC. 2254 " 2256 GROUP pwGeneralizedFecGroup 2257 DESCRIPTION "This group is only mandatory for implementations 2258 that support the generalized PW FEC. 2259 " 2261 GROUP pwFcsGroup 2262 DESCRIPTION "This group is only mandatory for implementations 2263 that support FCS retention." 2265 GROUP pwFragGroup 2266 DESCRIPTION "This group is only mandatory for implementations 2267 that support PW fragmentation. 2268 " 2270 GROUP pwPwStatusGroup 2271 DESCRIPTION "This group is only mandatory for implementations 2272 that support PW status notification. 2273 " 2275 GROUP pwGetNextGroup 2276 DESCRIPTION "This group is only mandatory for implementations 2277 where the pwIndex may be any arbitrary value 2278 and the EMS would require retrieval of the next 2279 free index." 2281 GROUP pwPriorityGroup 2282 DESCRIPTION "This group is only mandatory for implementations 2283 that support the controlling the PW setup and 2284 holding priority." 2286 GROUP pwAttachmentGroup 2287 DESCRIPTION "This group is only mandatory for implementations 2288 that support attachment of two PWs (PW stitching)." 2290 GROUP pwPeformance1DayIntervalGroup 2291 DESCRIPTION "This group is only mandatory for implementations 2292 that support PW performance gathering in 1 day 2293 intervals." 2295 GROUP pwPerformanceIntervalGeneralGroup 2296 DESCRIPTION "This group is only mandatory for implementations 2297 that support PW performance gathering in 15 2298 minute intervals." 2300 GROUP pwPeformanceIntervalGroup 2301 DESCRIPTION "This group is only mandatory for implementations 2302 that support PW performance gathering in 15 2303 minute intervals." 2305 GROUP pwHCPeformanceIntervalGroup 2306 DESCRIPTION "This group is only mandatory for implementations 2307 where at least one of the interval performance 2308 counters wraps around too quickly based on the 2309 criteria specified in RFC 2863 for high-capacity 2310 counters." 2312 GROUP pwMappingTablesGroup 2313 DESCRIPTION "This group is only mandatory for implementations 2314 that support reverse mapping of PW indexes to 2315 the pwIndex and the peer mapping table." 2317 GROUP pwSignalingGroup 2318 DESCRIPTION "This group is only mandatory for implementations 2319 that support the PW signaling." 2321 GROUP pwNotificationControlGroup 2322 DESCRIPTION "This group is only mandatory for implementations 2323 that support the PW notifications." 2325 OBJECT pwAdminStatus 2326 SYNTAX INTEGER { up(1), down(2) } 2327 DESCRIPTION "The support of the value testing(3) is not 2328 required." 2330 OBJECT pwOperStatus 2331 SYNTAX INTEGER { up(1), down(2), notPresent(5), 2332 lowerLayerDown(6) } 2333 DESCRIPTION "The support of the values testing(3) and dormant(4) 2334 is not required." 2336 OBJECT pwRowStatus 2337 SYNTAX RowStatus { active(1), notInService(2), 2338 notReady(3) } 2339 WRITE-SYNTAX RowStatus { active(1), notInService(2), 2340 createAndGo(4), destroy(6) 2341 } 2342 DESCRIPTION "Support for createAndWait is not required. Support 2343 of notReady is not required for implementations 2344 that do not support signaling, or if it is 2345 guaranteed that the conceptual row has all the 2346 required information to create the PW when the 2347 row has been created by the agent or written by 2348 the operator." 2350 OBJECT pwPeerAddrType 2351 SYNTAX InetAddressType { unknown(0), ipv4(1) } 2352 MIN-ACCESS read-only 2353 DESCRIPTION "Only unknown(0) and ipv4(1) is required. 2354 Implementation that support only IPv4 MAY support 2355 read-only access." 2357 OBJECT pwPeerAddr 2358 SYNTAX InetAddress (SIZE(0|4)) 2359 DESCRIPTION "An implementation is only required to support 2360 0, 4 address sizes." 2362 OBJECT pwStorageType 2363 MIN-ACCESS read-only 2364 DESCRIPTION "Write access is not required." 2366 OBJECT pwNotifRate 2367 MIN-ACCESS read-only 2368 DESCRIPTION "Write access is not required." 2370 ::= { pwCompliances 1 } 2372 -- Compliance requirement for read-only compliant implementations. 2374 pwModuleReadOnlyCompliance MODULE-COMPLIANCE 2375 STATUS current 2376 DESCRIPTION 2377 "The compliance statement for agents that provide read- 2378 only support for PW MIB Module. Such devices can 2379 then be monitored but cannot be configured using this 2380 MIB module." 2382 MODULE -- this module 2383 MANDATORY-GROUPS { pwBasicGroup 2384 } 2386 GROUP pwNotificationGroup 2387 DESCRIPTION "This group is only mandatory for implementations 2388 which can efficiently implement the notifications 2389 contained in this group." 2391 GROUP pwPwIdGroup 2392 DESCRIPTION "This group is only mandatory for implementations 2393 that support the PW ID FEC. 2394 " 2396 GROUP pwGeneralizedFecGroup 2397 DESCRIPTION "This group is only mandatory for implementations 2398 that support the generalized PW FEC. 2399 " 2401 GROUP pwFcsGroup 2402 DESCRIPTION "This group is only mandatory for implementations 2403 that support FCS retention." 2405 GROUP pwFragGroup 2406 DESCRIPTION "This group is only mandatory for implementations 2407 that support PW fragmentation. 2408 " 2410 GROUP pwPwStatusGroup 2411 DESCRIPTION "This group is only mandatory for implementations 2412 that support PW status notification. 2413 " 2415 GROUP pwGetNextGroup 2416 DESCRIPTION "This group is only mandatory for implementations 2417 where the pwIndex may be any arbitrary value 2418 and the EMS would require retrieval of the next 2419 free index." 2421 GROUP pwPriorityGroup 2422 DESCRIPTION "This group is only mandatory for implementations 2423 that support the controlling the PW setup and 2424 holding priority." 2426 GROUP pwAttachmentGroup 2427 DESCRIPTION "This group is only mandatory for implementations 2428 that support attachment of two PWs (PW stitching)." 2430 GROUP pwPeformance1DayIntervalGroup 2431 DESCRIPTION "This group is only mandatory for implementations 2432 that support PW performance gathering in 1 Day 2433 intervals." 2435 GROUP pwPerformanceIntervalGeneralGroup 2436 DESCRIPTION "This group is only mandatory for implementations 2437 that support PW performance gathering in 15 2438 minute intervals." 2440 GROUP pwPeformanceIntervalGroup 2441 DESCRIPTION "This group is only mandatory for implementations 2442 that support PW performance gathering in 15 2443 minute intervals." 2445 GROUP pwHCPeformanceIntervalGroup 2446 DESCRIPTION "This group is only mandatory for implementations 2447 where at least one of the interval performance 2448 counters wraps around too quickly based on the 2449 criteria specified in RFC 2863 for high-capacity 2450 counters." 2452 GROUP pwMappingTablesGroup 2453 DESCRIPTION "This group is only mandatory for implementations 2454 that support reverse mapping of PW indexes to 2455 the pwIndex and the peer mapping table." 2457 GROUP pwSignalingGroup 2458 DESCRIPTION "This group is only mandatory for implementations 2459 that support the PW signaling." 2461 GROUP pwNotificationControlGroup 2462 DESCRIPTION "This group is only mandatory for implementations 2463 that support the PW notifications." 2465 OBJECT pwType 2466 MIN-ACCESS read-only 2467 DESCRIPTION "Write access is not required." 2469 OBJECT pwOwner 2470 MIN-ACCESS read-only 2471 DESCRIPTION "Write access is not required." 2473 OBJECT pwPsnType 2474 MIN-ACCESS read-only 2475 DESCRIPTION "Write access is not required." 2477 OBJECT pwSetUpPriority 2478 MIN-ACCESS read-only 2479 DESCRIPTION "Write access is not required." 2481 OBJECT pwHoldingPriority 2482 MIN-ACCESS read-only 2483 DESCRIPTION "Write access is not required." 2485 OBJECT pwPeerAddrType 2486 SYNTAX InetAddressType { unknown(0), ipv4(1) } 2487 MIN-ACCESS read-only 2488 DESCRIPTION "Write access is not required. Only unknown(0) and 2489 ipv4(1) is required." 2491 OBJECT pwPeerAddr 2492 SYNTAX InetAddress (SIZE(0|4)) 2493 MIN-ACCESS read-only 2494 DESCRIPTION "Write access is not required. An implementation 2495 is only required to support 0, 4 address sizes." 2497 OBJECT pwAttachedPwIndex 2498 MIN-ACCESS read-only 2499 DESCRIPTION "Write access is not required." 2501 OBJECT pwIfIndex 2502 MIN-ACCESS read-only 2503 DESCRIPTION "Write access is not required." 2505 OBJECT pwID 2506 MIN-ACCESS read-only 2507 DESCRIPTION "Write access is not required." 2509 OBJECT pwLocalGroupID 2510 MIN-ACCESS read-only 2511 DESCRIPTION "Write access is not required." 2513 OBJECT pwGroupAttachmentID 2514 MIN-ACCESS read-only 2515 DESCRIPTION "Write access is not required." 2517 OBJECT pwLocalAttachmentID 2518 MIN-ACCESS read-only 2519 DESCRIPTION "Write access is not required." 2521 OBJECT pwRemoteAttachmentID 2522 MIN-ACCESS read-only 2523 DESCRIPTION "Write access is not required." 2525 OBJECT pwCwPreference 2526 MIN-ACCESS read-only 2527 DESCRIPTION "Write access is not required." 2529 OBJECT pwLocalIfMtu 2530 MIN-ACCESS read-only 2531 DESCRIPTION "Write access is not required." 2533 OBJECT pwLocalIfString 2534 MIN-ACCESS read-only 2535 DESCRIPTION "Write access is not required." 2537 OBJECT pwLocalCapabAdvert 2538 MIN-ACCESS read-only 2539 DESCRIPTION "Write access is not required." 2541 OBJECT pwFragmentCfgSize 2542 MIN-ACCESS read-only 2543 DESCRIPTION "Write access is not required." 2545 OBJECT pwFcsRetentionCfg 2546 MIN-ACCESS read-only 2547 DESCRIPTION "Write access is not required." 2549 OBJECT pwOutboundLabel 2550 MIN-ACCESS read-only 2551 DESCRIPTION "Write access is not required." 2553 OBJECT pwInboundLabel 2554 MIN-ACCESS read-only 2555 DESCRIPTION "Write access is not required." 2557 OBJECT pwName 2558 MIN-ACCESS read-only 2559 DESCRIPTION "Write access is not required." 2561 OBJECT pwDescr 2562 MIN-ACCESS read-only 2563 DESCRIPTION "Write access is not required." 2565 OBJECT pwAdminStatus 2566 SYNTAX INTEGER { up(1), down(2) } 2567 MIN-ACCESS read-only 2568 DESCRIPTION "Write access is not required. The support of value 2569 testing(3) is not required." 2571 OBJECT pwOperStatus 2572 SYNTAX INTEGER { up(1), down(2), notPresent(5), 2573 lowerLayerDown(6) } 2574 DESCRIPTION "The support of the values testing(3) and dormant(4) 2575 is not required." 2577 OBJECT pwRowStatus 2578 SYNTAX RowStatus { active(1) } 2579 MIN-ACCESS read-only 2580 DESCRIPTION "Write access is not required." 2582 OBJECT pwStorageType 2583 MIN-ACCESS read-only 2584 DESCRIPTION "Write access is not required." 2586 OBJECT pwOamEnable 2587 MIN-ACCESS read-only 2588 DESCRIPTION "Write access is not required." 2590 OBJECT pwGenAGIType 2591 MIN-ACCESS read-only 2592 DESCRIPTION "Write access is not required." 2594 OBJECT pwGenLocalAIIType 2595 MIN-ACCESS read-only 2596 DESCRIPTION "Write access is not required." 2598 OBJECT pwGenRemoteAIIType 2599 MIN-ACCESS read-only 2600 DESCRIPTION "Write access is not required." 2602 OBJECT pwUpDownNotifEnable 2603 MIN-ACCESS read-only 2604 DESCRIPTION "Write access is not required." 2606 OBJECT pwDeletedNotifEnable 2607 MIN-ACCESS read-only 2608 DESCRIPTION "Write access is not required." 2610 OBJECT pwNotifRate 2611 MIN-ACCESS read-only 2612 DESCRIPTION "Write access is not required." 2614 ::= { pwCompliances 2 } 2616 -- Units of conformance. 2618 pwBasicGroup OBJECT-GROUP 2619 OBJECTS { 2620 pwType, 2621 pwOwner, 2622 pwPsnType, 2623 pwIfIndex, 2624 pwCwPreference, 2625 pwLocalIfMtu, 2626 pwOutboundLabel, 2627 pwInboundLabel, 2628 pwName, 2629 pwDescr, 2630 pwCreateTime, 2631 pwUpTime, 2632 pwLastChange, 2633 pwAdminStatus, 2634 pwOperStatus, 2635 pwLocalStatus, 2636 pwRowStatus, 2637 pwStorageType, 2638 pwOamEnable 2639 } 2641 STATUS current 2642 DESCRIPTION 2643 "Collection of objects that are required in all 2644 implementations that support the PW MIB module." 2645 ::= { pwGroups 1 } 2647 pwPwIdGroup OBJECT-GROUP 2648 OBJECTS { 2649 pwID 2650 } 2652 STATUS current 2653 DESCRIPTION 2654 "Collection of objects required for PW ID configuration 2655 and signaling." 2656 ::= { pwGroups 2 } 2658 pwGeneralizedFecGroup OBJECT-GROUP 2659 OBJECTS { 2660 pwGroupAttachmentID, 2661 pwLocalAttachmentID, 2662 pwRemoteAttachmentID, 2663 pwGenAGIType, 2664 pwGenLocalAIIType, 2665 pwGenRemoteAIIType 2666 } 2668 STATUS current 2669 DESCRIPTION 2670 "Collection of objects required for generalized FEC 2671 configuration and signaling." 2672 ::= { pwGroups 3 } 2674 pwFcsGroup OBJECT-GROUP 2675 OBJECTS { 2676 pwFcsRetentionCfg, 2677 pwFcsRetentionStatus 2678 } 2680 STATUS current 2681 DESCRIPTION 2682 "Collection of objects required for FCS retention 2683 configuration and signaling." 2684 ::= { pwGroups 4 } 2686 pwFragGroup OBJECT-GROUP 2687 OBJECTS { 2688 pwFragmentCfgSize, 2689 pwRmtFragCapability 2690 } 2692 STATUS current 2693 DESCRIPTION 2694 "Collection of objects required for fragmentation 2695 configuration and signaling." 2696 ::= { pwGroups 5 } 2698 pwPwStatusGroup OBJECT-GROUP 2699 OBJECTS { 2700 pwRemoteCapabilities, 2701 pwRemoteStatusCapable, 2702 pwRemoteStatus 2703 } 2705 STATUS current 2706 DESCRIPTION 2707 "Collection of objects required for PW status configuration 2708 and signaling." 2709 ::= { pwGroups 6 } 2711 pwGetNextGroup OBJECT-GROUP 2712 OBJECTS { 2713 pwIndexNext 2714 } 2716 STATUS current 2717 DESCRIPTION 2718 "Collection of objects for getting the next available 2719 index." 2720 ::= { pwGroups 7 } 2722 pwPriorityGroup OBJECT-GROUP 2723 OBJECTS { 2724 pwSetUpPriority, 2725 pwHoldingPriority 2726 } 2728 STATUS current 2729 DESCRIPTION 2730 "Collection of objects for controlling the PW setup and 2731 holding priority." 2732 ::= { pwGroups 8 } 2734 pwAttachmentGroup OBJECT-GROUP 2735 OBJECTS { 2736 pwAttachedPwIndex 2737 } 2739 STATUS current 2740 DESCRIPTION 2741 "Collection of objects for PW configuration as ifIndex" 2742 ::= { pwGroups 9 } 2744 pwPerformanceGeneralGroup OBJECT-GROUP 2745 OBJECTS { 2746 pwPerfTotalErrorPackets 2747 } 2749 STATUS current 2750 DESCRIPTION 2751 "Collection of general objects needed for managing the 2752 total running performance parameters." 2753 ::= { pwGroups 10 } 2755 pwPeformance1DayIntervalGroup OBJECT-GROUP 2756 OBJECTS { 2757 pwPerf1DayIntervalValidData, 2758 pwPerf1DayIntervalTimeElapsed, 2759 pwPerf1DayIntervalInHCPackets, 2760 pwPerf1DayIntervalInHCBytes, 2761 pwPerf1DayIntervalOutHCPackets, 2762 pwPerf1DayIntervalOutHCBytes 2763 } 2765 STATUS current 2766 DESCRIPTION 2767 "Collection of objects needed for PW running 1 day interval 2768 performance collection." 2769 ::= { pwGroups 11 } 2771 pwPerformanceIntervalGeneralGroup OBJECT-GROUP 2772 OBJECTS { 2773 pwTimeElapsed, 2774 pwValidIntervals, 2775 pwPerfIntervalValidData, 2776 pwPerfIntervalTimeElapsed 2777 } 2779 STATUS current 2780 DESCRIPTION 2781 "Collection of general objects needed for managing the 2782 interval performance parameters." 2783 ::= { pwGroups 12 } 2785 pwPeformanceIntervalGroup OBJECT-GROUP 2786 OBJECTS { 2787 pwPerfCurrentInPackets, 2788 pwPerfCurrentInBytes, 2789 pwPerfCurrentOutPackets, 2790 pwPerfCurrentOutBytes, 2792 pwPerfIntervalInPackets, 2793 pwPerfIntervalInBytes, 2794 pwPerfIntervalOutPackets, 2795 pwPerfIntervalOutBytes 2796 } 2798 STATUS current 2799 DESCRIPTION 2800 "Collection of 32 bits objects needed for PW performance 2801 collection in 15 minutes intervals." 2802 ::= { pwGroups 13 } 2804 pwHCPeformanceIntervalGroup OBJECT-GROUP 2805 OBJECTS { 2806 pwPerfCurrentInHCPackets, 2807 pwPerfCurrentInHCBytes, 2808 pwPerfCurrentOutHCPackets, 2809 pwPerfCurrentOutHCBytes, 2811 pwPerfIntervalInHCPackets, 2812 pwPerfIntervalInHCBytes, 2813 pwPerfIntervalOutHCPackets, 2814 pwPerfIntervalOutHCBytes 2815 } 2817 STATUS current 2818 DESCRIPTION 2819 "Collection of HC objects needed for PW performance 2820 collection in 15 minutes intervals." 2821 ::= { pwGroups 14 } 2823 pwMappingTablesGroup OBJECT-GROUP 2824 OBJECTS { 2825 pwIndexMappingPwIndex, 2826 pwPeerMappingPwIndex, 2827 pwGenFecIndexMappingPwIndex 2828 } 2830 STATUS current 2831 DESCRIPTION 2832 "Collection of objects contained in the reverse 2833 mapping tables." 2834 ::= { pwGroups 15 } 2836 pwNotificationControlGroup OBJECT-GROUP 2837 OBJECTS { 2838 pwUpDownNotifEnable, 2839 pwDeletedNotifEnable, 2840 pwNotifRate 2841 } 2843 STATUS current 2844 DESCRIPTION 2845 "Collection of objects for controlling the PW 2846 notifications." 2847 ::= { pwGroups 16 } 2849 pwNotificationGroup NOTIFICATION-GROUP 2850 NOTIFICATIONS { 2851 pwUp, 2852 pwDown, 2853 pwDeleted 2854 } 2856 STATUS current 2857 DESCRIPTION 2858 "Collection PW notifications objects." 2859 ::= { pwGroups 17 } 2861 pwSignalingGroup OBJECT-GROUP 2862 OBJECTS { 2863 pwPeerAddrType, 2864 pwPeerAddr, 2865 pwLocalGroupID, 2866 pwLocalIfString, 2867 pwLocalCapabAdvert, 2868 pwRemoteGroupID, 2869 pwCwStatus, 2870 pwRemoteIfMtu, 2871 pwRemoteIfString 2872 } 2874 STATUS current 2875 DESCRIPTION 2876 "Collection of objects for use in implementations that 2877 support the PW signaling." 2878 ::= { pwGroups 18 } 2880 END 2882 14. Security Considerations 2884 It is clear that this MIB module is potentially useful for monitoring 2885 PW capable PEs. This MIB module can also be used for configuration 2886 of certain objects, and anything that can be configured can be 2887 incorrectly configured, with potentially disastrous results. 2889 There are number of management objects defined in this MIB module 2890 with a MAX-ACCESS clause of read-write and/or read-create. Such 2891 objects may be considered sensitive or vulnerable in some network 2892 environments. The support for SET operations in a non-secure 2893 environment without proper protection can have a negative effect on 2894 network operations. These are the tables and objects and their 2895 sensitivity/vulnerability: 2897 o the pwTable contains objects to configure PW parameters on a 2898 Provider Edge (PE) device. Unauthorized access to objects in this 2899 table, could result in disruption of traffic on the network. The 2900 objects pwUpDownNotifEnable and pwNotifRate control the reports 2901 from the network element to the EMS. Unauthorized access to these 2902 objects could result in disruption of configuration and status 2903 change reporting, resulting mis-view of the network conditions. 2904 The use of stronger mechanisms such as SNMPv3 security should be 2905 considered where possible. Specifically, SNMPv3 VACM and USM MUST 2906 be used with any v3 agent which implements this MIB module. 2907 Administrators should consider whether read access to these 2908 objects should be allowed, since read access may be undesirable 2909 under certain circumstances. 2911 Some of the readable objects in this MIB module (i.e., objects with a 2912 MAX-ACCESS other than not-accessible) may be considered sensitive or 2913 vulnerable in some network environments. It is thus important to 2914 control even GET and/or NOTIFY access to these objects and possibly 2915 to even encrypt the values of these objects when sending them over 2916 the network via SNMP. These are the tables and objects and their 2917 sensitivity/vulnerability: 2919 o the pwTable, pwPerfCurrentTable, pwPerfIntervalTable, 2920 pwPerf1DayIntervalTable, pwIndexMappingTable, pwPeerMappingTable 2921 and pwGenFecIndexMappingTable collectively show the pseudowire 2922 connectivity topology and its performance characteristics. If an 2923 Administrator does not want to reveal this information, then these 2924 tables should be considered sensitive/vulnerable. 2926 SNMP versions prior to SNMPv3 did not include adequate security. 2927 Even if the network itself is secure (for example by using IPsec), 2928 even then, there is no control as to who on the secure network is 2929 allowed to access and GET/SET (read/change/create/delete) the objects 2930 in this MIB module. 2932 It is RECOMMENDED that implementers consider the security features as 2933 provided by the SNMPv3 framework (see [RFC3410], section 8), 2934 including full support for the SNMPv3 cryptographic mechanisms (for 2935 authentication and privacy). 2937 Further, deployment of SNMP versions prior to SNMPv3 is NOT 2938 RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to 2939 enable cryptographic security. It is then a customer/operator 2940 responsibility to ensure that the SNMP entity giving access to an 2941 instance of this MIB module, is properly con8figured to give access 2942 to the objects only to those principals (users) that have legitimate 2943 rights to indeed GET or SET (change/create/delete) them. 2945 15. IANA Considerations 2947 15.1. ifType for PW 2949 IANA has beeen requested to register a value for PW in the 2950 IANAifType-MIB called ifPwType. When the assignment has been made, 2951 the RFC Editor is asked to document the value here. 2953 15.2. PW MIB Modules OBJECT IDENTIFIER values 2955 A PW may appear as ifIndex in the ifTable, and therefore it is 2956 requested below that the pwStdMIB OBJECT IDENTIFIER will be assigned 2957 under the 'transmission' subtree, as the common practice in assigning 2958 OBJECT IDENTIFIERs for MIB modules representing entities in the 2959 ifTable. 2961 All other MIB modules related to PW management SHOULD be assigned 2962 under the 'mib-2' subtree, individual request will appear in the MIB 2963 module memo IANA Considerations section. 2965 15.3. IANA Considerations for PW-STD-MIB 2967 The MIB module in this document uses the following IANA-assigned 2968 OBJECT IDENTIFIER values recorded in the SMI Numbers registry: 2970 Descriptor OBJECT IDENTIFIER value 2971 ---------- ----------------------- 2973 pwStdMIB { transmission ZZZZ } 2975 Editor's Note (to be removed prior to publication): The IANA is 2976 requested to assign a value for "ZZZZ" under the 'transmission' 2977 subtree and to record the assignment in the SMI Numbers registry. 2978 This value SHOULD be the same value assigned for the PW ifType for 2979 representation of the PW in the ifTable. When the assignment has 2980 been made, the RFC Editor is asked to replace "ZZZZ" (here and in the 2981 MIB module) with the assigned value and to remove this note. 2983 15.4. IANA Considerations for IANA-PWE3-MIB 2985 The MIB module in this document uses the following IANA-assigned 2986 OBJECT IDENTIFIER values recorded in the SMI Numbers registry: 2988 Descriptor OBJECT IDENTIFIER value 2989 ---------- ----------------------- 2991 ianaPwe3MIB { mib-2 XXXX } 2993 Editor's Note (to be removed prior to publication): The IANA is 2994 requested to assign a value for "XXXX" under the 'mib-2' subtree and 2995 to record the assignment in the SMI Numbers registry. When the 2996 assignment has been made, the RFC Editor is asked to replace "XXXX" 2997 (here and in the MIB module) with the assigned value and to remove 2998 this note. 3000 16. Acknowledgements 3002 We thank Orly Nicklass for her dedicated review and significant edit 3003 at various sections of the document, and Kiran Koushik for his 3004 contribution. 3006 17. References 3008 17.1. Normative References 3010 [BCP14] Bradner, S., "Key words for use in RFCs to Indicate 3011 requirement Levels", BCP 14, RFC 2119, March 1997. 3013 [PWTC] Nadeau, T. and D. Zelig, "Definitions for Textual 3014 Conventions and OBJECT-IDENTITIES for Pseudowires 3015 Management", work-in-progress . 3017 [RFC2578] McCloghrie, K., Ed., Perkins, D., Ed., and J. 3018 Schoenwaelder, Ed., "Structure of Management Information 3019 Version 2 (SMIv2)", STD 58, RFC 2578, April 1999. 3021 [RFC2579] McCloghrie, K., Ed., Perkins, D., Ed., and J. 3022 Schoenwaelder, Ed., "Textual Conventions for SMIv2", 3023 STD 58, RFC 2579, April 1999. 3025 [RFC2580] McCloghrie, K., Perkins, D., and J. Schoenwaelder, 3026 "Conformance Statements for SMIv2", STD 58, RFC 2580, 3027 April 1999. 3029 [RFC2863] McCloghrie, K. and F. Kastenholz, "The Interfaces Group 3030 MIB", RFC 2863, June 2000. 3032 [RFC3411] Harrington, D., Presuhn, R., and B. Wijnen, "An 3033 Architecture for Describing Simple Network Management 3034 Protocol (SNMP) Management Frameworks", STD 62, RFC 3411, 3035 December 2002. 3037 [RFC3413] Levi, D., Meyer, P., and B. Stewart, "Simple Network 3038 Management Protocol (SNMP) Applications", STD 62, 3039 RFC 3413, December 2002. 3041 [RFC3593] Tesink, K., "Textual Conventions for MIB Modules Using 3042 Performance History Based on 15 Minute Intervals", 3043 RFC 3593, September 2003. 3045 [RFC3705] Ray, B. and R. Abbi, "High Capacity Textual Conventions 3046 for MIB Modules Using Performance History Based on 15 3047 Minute Intervals", RFC 3705, February 2004. 3049 [RFC3931] Lau, J., Townsley, M., and I. Goyret, "Layer Two Tunneling 3050 Protocol - Version 3 (L2TPv3)", RFC 3931, March 2005. 3052 [RFC4001] Daniele, M., Haberman, B., Routhier, S., and J. 3053 Schoenwaelder, "Textual Conventions for Internet Network 3054 Addresses", RFC 4001, February 2005. 3056 [RFC4446] Martini, L., "IANA Allocations for Pseudowire Edge to Edge 3057 Emulation (PWE3)", BCP 116, RFC 4446, April 2006. 3059 [RFC4447] Martini, L., Rosen, E., El-Aawar, N., Smith, T., and G. 3060 Heron, "Pseudowire Setup and Maintenance Using the Label 3061 Distribution Protocol (LDP)", RFC 4447, April 2006. 3063 [RFC4623] Malis, A. and M. Townsley, "Pseudowire Emulation Edge-to- 3064 Edge (PWE3) Fragmentation and Reassembly", RFC 4623, 3065 August 2006. 3067 [RFC4720] Malis, A., Allan, D., and N. Del Regno, "Pseudowire 3068 Emulation Edge-to-Edge (PWE3) Frame Check Sequence 3069 Retention", RFC 4720, November 2006. 3071 [RFC4863] Martini, L. and G. Swallow, "Wildcard Pseudowire Type", 3072 RFC 4863, May 2007. 3074 17.2. Informative References 3076 [CEPMIB] Zelig, D., Nadeau, T., and R. Cohen, "SONET/SDH Circuit 3077 Emulation Service Over Packet (CEP) Management Information 3078 Base Using SMIv2", work-in-progress . 3080 [PWMPLSMIB] 3081 Zelig, D. and T. Nadeau, "Pseudowire (PW) Over MPLS PSN 3082 Management Information Base", work-in-progress . 3084 [RFC2434] Narten, T. and H. Alvestrand, "Guidelines for Writing an 3085 IANA Considerations Section in RFCs", BCP 26, RFC 2434, 3086 October 1998. 3088 [RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart, 3089 "Introduction and Applicability Statements for Internet- 3090 Standard Management Framework", RFC 3410, December 2002. 3092 [RFC3916] Xiao, X., McPherson, D., and P. Pate, "Requirements for 3093 Pseudo-Wire Emulation Edge-to-Edge (PWE3)", RFC 3916, 3094 September 2004. 3096 [RFC3985] Bryant, S. and P. Pate, "Pseudo Wire Emulation Edge-to- 3097 Edge (PWE3) Architecture", RFC 3985, March 2005. 3099 Authors' Addresses 3101 Thomas D. Nadeau (editor) 3102 BT 3103 BT Centre 3104 81 Newgate Street 3105 London EC1A 7AJ 3106 United Kingdom 3108 Email: thomas.nadeau@bt.com 3110 David Zelig (editor) 3111 Corrigent Systems 3112 126, Yigal Alon St. 3113 Tel Aviv, 3114 Israel 3116 Phone: +972 3 6945 273 3117 Email: davidz@corrigent.com 3119 Full Copyright Statement 3121 Copyright (C) The IETF Trust (2008). 3123 This document is subject to the rights, licenses and restrictions 3124 contained in BCP 78, and except as set forth therein, the authors 3125 retain all their rights. 3127 This document and the information contained herein are provided on an 3128 "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS 3129 OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND 3130 THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS 3131 OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF 3132 THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED 3133 WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 3135 Intellectual Property 3137 The IETF takes no position regarding the validity or scope of any 3138 Intellectual Property Rights or other rights that might be claimed to 3139 pertain to the implementation or use of the technology described in 3140 this document or the extent to which any license under such rights 3141 might or might not be available; nor does it represent that it has 3142 made any independent effort to identify any such rights. Information 3143 on the procedures with respect to rights in RFC documents can be 3144 found in BCP 78 and BCP 79. 3146 Copies of IPR disclosures made to the IETF Secretariat and any 3147 assurances of licenses to be made available, or the result of an 3148 attempt made to obtain a general license or permission for the use of 3149 such proprietary rights by implementers or users of this 3150 specification can be obtained from the IETF on-line IPR repository at 3151 http://www.ietf.org/ipr. 3153 The IETF invites any interested party to bring to its attention any 3154 copyrights, patents or patent applications, or other proprietary 3155 rights that may cover technology that may be required to implement 3156 this standard. Please address the information to the IETF at 3157 ietf-ipr@ietf.org. 3159 Acknowledgment 3161 Funding for the RFC Editor function is provided by the IETF 3162 Administrative Support Activity (IASA).