idnits 2.17.1 draft-nadeau-l2vpn-vpls-mib-03.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 14. -- Found old boilerplate from RFC 3978, Section 5.5 on line 1933. -- Found old boilerplate from RFC 3978, Section 5.5, updated by RFC 4748 on line 1917. -- Found old boilerplate from RFC 3979, Section 5, paragraph 1 on line 1893. -- Found old boilerplate from RFC 3979, Section 5, paragraph 2 on line 1900. -- Found old boilerplate from RFC 3979, Section 5, paragraph 3 on line 1906. ** Found boilerplate matching RFC 3978, Section 5.4, paragraph 1, updated by RFC 4748 (on line 1921), which is fine, but *also* found old RFC 3978, Section 5.4, paragraph 1 text on line 1925. ** Found boilerplate matching RFC 3978, Section 5.5, updated by RFC 4748 (on line 1917), which is fine, but *also* found old RFC 3978, Section 5.5 text on line 1933. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- == No 'Intended status' indicated for this document; assuming Proposed Standard Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The abstract seems to contain references ([PWE3-PW-MIB]), which it shouldn't. Please replace those with straight textual mentions of the documents in question. Miscellaneous warnings: ---------------------------------------------------------------------------- == In addition to RFC 3978, Section 5.5 boilerplate, a section with a similar start was also found: This document and the information contained herein are provided on an "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. == In addition to RFC 3978, Section 5.5, updated by RFC 4748 boilerplate, a section with a similar start was also found: This document and the information contained herein are provided on an "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. == The copyright year in the RFC 3978 Section 5.4 Copyright Line does not match the current year == The copyright year in the IETF Trust Copyright Line does not match the current year -- 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.) -- Couldn't find a document date in the document -- date freshness check skipped. Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) == Missing Reference: 'RFC2119' is mentioned on line 94, but not defined == Missing Reference: 'BCP14' is mentioned on line 101, but not defined == Missing Reference: 'RFC3985' is mentioned on line 137, but not defined == Missing Reference: 'RFC2571' is mentioned on line 1072, but not defined ** Obsolete undefined reference: RFC 2571 (Obsoleted by RFC 3411) == Missing Reference: 'RFC3411' is mentioned on line 1072, but not defined == Missing Reference: 'RFC2863' is mentioned on line 1073, but not defined == Missing Reference: 'RFC4001' is mentioned on line 1073, but not defined == Missing Reference: 'RFC4265' is mentioned on line 1073, but not defined == Missing Reference: 'RFC3813' is mentioned on line 1073, but not defined == Missing Reference: 'RFC3413' is mentioned on line 823, but not defined == Missing Reference: 'RFC4364' is mentioned on line 1471, but not defined == Missing Reference: 'PW-STD-MIB' is mentioned on line 1768, but not defined -- Possible downref: Non-RFC (?) normative reference: ref. 'PWE3-PW-MIB' -- Possible downref: Non-RFC (?) normative reference: ref. 'L2VPN-VPLS-LDP' -- Possible downref: Non-RFC (?) normative reference: ref. 'L2VPN-VPLS-BGP' Summary: 5 errors (**), 0 flaws (~~), 17 warnings (==), 11 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 Internet Draft Thomas D. Nadeau (Ed.) 2 Expires: June 2007 A S Kiran Koushik (Ed.) 3 Cisco Systems, Inc. 5 Virtual Private Lan Services (VPLS) Management Information Base 7 draft-nadeau-l2vpn-vpls-mib-03.txt 9 Status of this Memo 11 By submitting this Internet-Draft, each author represents that any 12 applicable patent or other IPR claims of which he or she is aware 13 have been or will be disclosed, and any of which he or she becomes 14 aware will be disclosed, in accordance with Section 6 of BCP 79. 16 Internet-Drafts are working documents of the Internet Engineering 17 Task Force (IETF), its areas, and its working groups. Note that 18 other groups may also distribute working documents as 19 Internet-Drafts. 21 Internet-Drafts are draft documents valid for a maximum of six 22 months and may be updated, replaced, or obsoleted by other documents 23 at any time. It is inappropriate to use Internet-Drafts as 24 reference material or to cite them other than as "work in progress." 26 The list of current Internet-Drafts can be accessed at 27 http://www.ietf.org/ietf/1id-abstracts.txt. 29 The list of Internet-Draft Shadow Directories can be accessed at 30 http://www.ietf.org/shadow.html. 32 Copyright Notice 34 Copyright (C) The IETF Trust (2007). 36 Abstract 38 This memo defines an experimental portion of the Management 39 Information Base for use with network management protocols in the 40 Internet community. In particular, it describes managed objects 41 for modeling of Virtual Private LAN services. It needs to be used 42 in conjunction with Pswudo Wire (PW) Management Information Base 43 [PWE3-PW-MIB]. 45 Table of Contents 47 Abstract............................................................1 48 1 Introduction...................................................2 49 1.1 Changes from version 00 to 01..................................2 50 1.2 Changes from version 01 to 02..................................2 51 1.3 Changes from version 02 to 03..................................2 52 2 Terminology....................................................3 53 3 The Internet-Standard Management Framework.....................3 54 draft-nadeau-l2vpn-vpls-mib-03 L2-VPN-MIB Dec 22, 2006 56 4 VPLS MIB modules Architecture..................................4 57 4.1 VPLS-GENERIC-DRAFT-01-MIB Module Usage.........................4 58 4.2 VPLS-LDP-DRAFT-01-MIB Module Usage.............................4 59 4.3 VPLS-BGP-DRAFT-01-MIB Module Usage.............................4 60 4.4 Relations to other MIB modules.................................4 61 5 Example of the VPLS MIB modules usage .........................5 62 6 Object definitions.............................................6 63 6.1 VPLS-GENERIC-DRAFT-01-MIB......................................6 64 6.2 VPLS-LDP-DRAFT-01-MIB Object definitions......................19 65 6.3 VPLS-BGP-DRAFT-01-MIB Object definitions......................27 66 7 Security considerations.......................................36 67 8 IANA Considerations...........................................36 68 9 References....................................................37 69 9.1 Normative References..........................................37 70 9.2 Informative References........................................38 71 10 Acknowledgement ..............................................38 72 11 Author's Addresses............................................38 73 12 Intellectual Property Notice..................................38 74 13 Full Copyright Statement......................................39 76 1 Introduction 78 This memo defines a portion of the Management Information Base 79 (MIB) for use with network management protocols in the Internet 80 community. In particular, it defines a MIB module that can be 81 used to manage VPLS(Virtual Private LAN Services for transmission 82 over a packet Switched Network (PSN) using LDP [L2VPN-VPLS-LDP] or 83 BGP[L2VPN-VPLS-BGP] signalling. This MIB module provides generic 84 management of VPLS services as defined by the IETF L2VPN Working 85 Group. 87 Comments should be made directly to the L2VPN mailing list at 88 l2vpn@ietf.org. 90 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL 91 NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and 92 "OPTIONAL" in this document are to be interpreted as described in 93 [RFC2119]. 95 Conventions used in this document 97 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL 98 NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and 99 "OPTIONAL" in this document are to be interpreted as described in 100 RFC-2119 [BCP14]. 102 1.1. Changes from version 00 to 01 103 draft-nadeau-l2vpn-vpls-mib-03 L2-VPN-MIB Dec 22, 2006 105 [NOTE to RFC Editor: this section is to be removed before 106 publication.] 108 1.1.1. Split the MIB modules into VPLS-GENERIC-DRAFT-01-MIB, 109 VPLS-LDP-DRAFT-01-MIB, VPLS-BGP-DRAFT-01-MIB. 110 The generic MIB Module will contain information common 111 to both LDP and BGP signalled VPLS. 112 1.1.2. Moved certain objects from vplsConfigTable to 113 vplsStatusTable. 114 1.1.3. Added new objects to the vplsLdpPwBindTable. 115 1.1.4. Retained MAC related objects since there is specific 116 reference in [L2VPN-VPLS-LDP] and [L2VPN-VPLS-BGP]. 118 1.2. Changes from version 01 to 02 120 [NOTE to RFC Editor: this section is to be removed before 121 publication.] 123 1.2.1. Added new objects to the vplsConfigTable. 124 1.2.2. Editorial changes. 126 1.3. Changes from version 02 to 03 128 [NOTE to RFC Editor: this section is to be removed before 129 publication.] 131 1.3.1. Added the VPLS-BGP-DRAFT-01-MIB module. 133 2 Terminology 135 This document adopts the definitions, acronyms and mechanisms 136 described in [RFC3985]. Unless otherwise stated, the mechanisms of 137 [RFC3985] apply and will not be re-described here. 139 3 The Internet-Standard Management Framework 141 For a detailed overview of the documents that describe the current 142 Internet-Standard Management Framework, please refer to section 7 143 of RFC 3410 [RFC3410]. 145 Managed objects are accessed via a virtual information store, 146 termed the Management Information Base or MIB. MIB objects are 147 generally accessed through the Simple Network Management Protocol 148 (SNMP). Objects in the MIB are defined using the mechanisms 149 defined in the Structure of Management Information (SMI). This 150 memo specifies a MIB module that is compliant to the SMIv2, which 151 draft-nadeau-l2vpn-vpls-mib-03 L2-VPN-MIB Dec 22, 2006 153 is described in STD 58,RFC 2578 [RFC2578], STD 58, RFC 2579 154 [RFC2579] and STD 58, RFC 2580 [RFC2580]. 156 4. VPLS MIB Module Architecture 158 The MIB structure for defining a VPLS service is composed from four 159 types of MIB modules. 161 The first type is the VPLS-GENERIC-DRAFT-01-MIB module, which 162 configures general parameters of the VPLS service that are common 163 to all types of emulated services. 165 The second type is the VPLS-LDP-DRAFT-01-MIB module, which 166 configures VPLS-LDP[L2VPN-VPLS-LDP] specific parameters of the 167 VPLS service. 169 The third type is the VPLS-BGP-DRAFT-01-MIB module, which configures 170 VPLS-BGP[L2VPN-VPLS-BGP] specific parameters of the 171 VPLS service. 173 The fourth type of modules are service-specific modules, which are 174 defined in other documents. 176 -------- ----------------- 177 PW Mapping | | | | 178 -----> | PW-MIB |-->|PW-ENET/MPLS-MIB | 179 __________ / | | | | 180 | | / -------- ----------------- 181 | VPLS MIB | / ------------ 182 | |---------->| | 183 ----------- MAC addr. | BRIDGE-MIB | 184 mapping(TBD)| | 185 ------------ 187 4.1. VPLS-GENERIC-DRAFT-01-MIB Module Usage 188 An entry in the vplsConfigTable MUST exist for a VPLS service. 189 This table holds generic parameters which apply to a VPLS service 190 which can be signalled via LDP or BGP. 192 A conceptual row can be created in the vplsConfigTable in one of 193 the following ways: 195 1) The operator creates a row in the vplsConfigTable when 196 configuring the node for a new service. This mode MUST be 197 supported by the agent, and MUST be used when creating a 198 manually assigned VPLS service. 200 draft-nadeau-l2vpn-vpls-mib-03 L2-VPN-MIB Dec 22, 2006 202 2) The agent MAY create a row in the vplsConfigTable automatically 203 due to some auto discovery application, or based on 204 configuration that is done through non-SNMP applications. 205 This mode is OPTIONAL. 207 An entry in the vplsPwBindTable MUST exist for a VPLS service. 208 This binding table links one VPLS service with one or many 209 pseudo wires (defined in [PWE3-PW-MIB]). The pseudo wire may 210 be used as a spoke or a mesh based on the parameters defined 211 in this table. 213 The agent than creates the rows in the (locally supported) 214 performance tables and reverse mapping tables in 215 VPLS-GENERIC-DRAFT-01-MIB module. 217 4.2. VPLS-LDP-DRAFT-01-MIB Module Usage 219 An entry in the vplsLdpConfigTable MUST be created by the agent 220 for a VPLS service signalled using LDP. 222 4.3. VPLS-BGP-DRAFT-01-MIB Module Usage 224 An entry in the vplsBgpConfigTable MUST be created by the agent 225 for a VPLS service signalled using LDP. 227 4.4. Relations to other MIB modules 229 - The vplsPwBindTable links the VPLS entry to various entries in 230 the [PWE3-PW-MIB] 232 - The association of MAC addresses to VPLS entries is TBD. 233 Presentlyinvestigating BRIDGE-MIB to accomodate the same. 235 - Unless all the necessary entries in the applicable tables have 236 been created and all the parameters have been consistently 237 configured in those tables, signaling cannot be performed 238 from the local node, and the ??? should report 'notPresent'. 240 - Statistics can be gathered from the [PWE3-PW-MIB] - TBD 242 5 Example of the VPLS MIB modules usage 244 In this section we provide an example of using the MIB objects 245 described in section 7 to set up a VPLS service over MPLS. While 246 this example is not meant to illustrate every permutation of the 247 draft-nadeau-l2vpn-vpls-mib-03 L2-VPN-MIB Dec 22, 2006 249 MIB, it is intended as an aid to understanding some of the key 250 concepts. It is meant to be read after going through the MIB 251 itself. 253 In the VPLS-GENERIC-DRAFT-01-MIB module: 255 In vplsConfigTable: 256 { 257 vplsConfigIndex 10, 258 vplsConfigName "VPLS-A" 259 vplsConfigAdminStatus 1(up), 260 vplsConfigMacLearning 1(true), 261 vplsConfigDiscardUnknownDest 2(false), 262 vplsConfigMacAging 1(true), 263 vplsConfigVpnId "100:10" 264 vplsConfigRowStatus 1(active) 265 } 267 In vplsStatusTable: 268 { 269 vplsStatusOperStatus 1(up), 270 } 272 In the VPLS-LDP-DRAFT-01-MIB module: 274 In vplsLdpConfigTable: 275 { 276 vplsLdpConfigMacAddrWithdraw 1(true), 278 } 280 In vplsLdpPwBindTable: 281 { 282 vplsLdpPwBindType 1(mesh), 283 vplsLdpPwBindMacAddressLimit 100 284 } 286 6 Object definitions 288 6.1 VPLS-GENERIC-DRAFT-01-MIB 290 This MIB module makes references to the following documents. 291 [RFC2578], [RFC2579], [RFC2580], [RFC2571], [RFC3411], 292 [RFC2863], [RFC4001], [RFC4265] and [RFC3813]. 294 VPLS-GENERIC-DRAFT-01-MIB DEFINITIONS ::= BEGIN 295 draft-nadeau-l2vpn-vpls-mib-03 L2-VPN-MIB Dec 22, 2006 297 IMPORTS 298 NOTIFICATION-TYPE, MODULE-IDENTITY, OBJECT-TYPE, 299 Unsigned32, Counter32, transmission 300 FROM SNMPv2-SMI -- RFC2578 302 MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP 303 FROM SNMPv2-CONF -- RFC2580 305 TruthValue, RowStatus, StorageType 306 FROM SNMPv2-TC -- RFC2579 308 SnmpAdminString 309 FROM SNMP-FRAMEWORK-MIB -- RFC3411 311 PwIndexType 312 FROM PW-TC-STD-MIB 314 VPNIdOrZero 315 FROM VPN-TC-STD-MIB -- RFC4265 316 ; 318 vplsGenericDraft01MIB MODULE-IDENTITY 319 LAST-UPDATED "200608301200Z" -- 30 Aug 2006 12:00:00 GMT 320 ORGANIZATION "Layer 2 Virtual Private Networks (L2VPN) 321 Working Group" 322 CONTACT-INFO 323 " 324 Thomas D. Nadeau 325 Email: tnadeau@cisco.com 327 The L2VPN Working Group (email distribution l2vpn@ietf.org, 328 http://www.ietf.org/html.charters/l2vpn-charter.html) 329 " 331 DESCRIPTION 332 "Copyright (C) The Internet Society (2007). The initial 333 version of this MIB module was published in RFC XXXX. 334 -- RFC Editor: Please replace XXXX with RFC number & remove 335 -- this note. 337 For full legal notices see the RFC itself or see: 338 http://www.ietf.org/copyrights/ianamib.html 340 This MIB module contains generic managed object definitions 341 for Virtual Private LAN Services as in [L2VPN-VPLS-LDP] and 342 [L2VPN-VPLS-BGP] 344 draft-nadeau-l2vpn-vpls-mib-03 L2-VPN-MIB Dec 22, 2006 346 This MIB module enables the use of any underlying Pseudo Wire 347 network." 349 -- Revision history. 350 REVISION 351 "200608301200Z" -- 30 August 2006 12:00:00 GMT 352 DESCRIPTION 353 "Changes from previous version: 354 1) Moved LDP Specific information to VPLS-LDP-DRAFT-01-MIB 355 2) Created the vplsStatusTable to store status information. 356 3) 357 " 358 REVISION 359 "200606041200Z" -- 4 June 2006 12:00:00 GMT 361 DESCRIPTION "Initial version published as part of RFC YYYY." 362 -- RFC Editor: please replace YYYY with IANA assigned value, and 363 -- delete this note. 365 ::= { transmission XXXX } 366 -- RFC Editor: please replace XXXX with IANA assigne value, and 367 -- delete this note. 369 -- Top-level components of this MIB. 371 -- Notifications 372 vplsNotifications OBJECT IDENTIFIER 373 ::= { vplsGenericDraft01MIB 0 } 374 -- Tables, Scalars 375 vplsObjects OBJECT IDENTIFIER 376 ::= { vplsGenericDraft01MIB 1 } 377 -- Conformance 378 vplsConformance OBJECT IDENTIFIER 379 ::= { vplsGenericDraft01MIB 2 } 381 -- PW Virtual Connection Table 383 vplsConfigIndexNext OBJECT-TYPE 384 SYNTAX Unsigned32 385 MAX-ACCESS read-only 386 STATUS current 387 DESCRIPTION 388 "This object contains an appropriate value to be used 389 for vplsConfigIndex when creating entries in the 390 vplsConfigTable. The value 0 indicates that no 391 unassigned entries are available. To obtain the 392 value of vplsConfigIndex for a new entry in the 394 draft-nadeau-l2vpn-vpls-mib-03 L2-VPN-MIB Dec 22, 2006 396 vplsConfigTable, the manager issues a management 397 protocol retrieval operation to obtain the current 398 value of vplsConfigIndex. After each retrieval 399 operation, the agent should modify the value to 400 reflect the next unassigned index. After a manager 401 retrieves a value the agent will determine through 402 its local policy when this index value will be made 403 available for reuse." 404 ::= { vplsObjects 1 } 406 vplsConfigTable OBJECT-TYPE 407 SYNTAX SEQUENCE OF VplsConfigEntry 408 MAX-ACCESS not-accessible 409 STATUS current 410 DESCRIPTION 411 "This table specifies information for configuring 412 and monitoring Virtual Private Lan Services(VPLS). 413 " 414 ::= { vplsObjects 2 } 416 vplsConfigEntry OBJECT-TYPE 417 SYNTAX VplsConfigEntry 418 MAX-ACCESS not-accessible 419 STATUS current 420 DESCRIPTION 421 "A row in this table represents a Virtual Private Lan 422 Service(VPLS) in a packet network. It is indexed by 423 vplsConfigIndex, which uniquely identifies a single VPLS. 425 A row is created by the operator or by the agent if a 426 VPLS service is created by non-SNMP application or 427 due to autodiscovery process. 429 None of the read-create objects values can be 430 changed when vplsConfigRowStatus is in the active(1) 431 state. Changes are allowed when the vplsConfigRowStatus 432 is in notInService(2) or notReady(3) states only. 433 If the operator need to change one of the values 434 for an active row the vplsConfigRowStatus should be 435 first changed to notInService(2), the objects may 436 be changed now, and later to active(1) in order to 437 re-initiate the signaling process with the new 438 values in effect. 439 " 440 INDEX { vplsConfigIndex } 441 ::= { vplsConfigTable 1 } 443 VplsConfigEntry ::= 444 draft-nadeau-l2vpn-vpls-mib-03 L2-VPN-MIB Dec 22, 2006 446 SEQUENCE { 447 vplsConfigIndex Unsigned32, 448 vplsConfigName SnmpAdminString, 449 vplsConfigDescr SnmpAdminString, 450 vplsConfigAdminStatus INTEGER, 451 vplsConfigMacLearning TruthValue, 452 vplsConfigDiscardUnknownDest TruthValue, 453 vplsConfigMacAging TruthValue, 454 vplsConfigFwdFullHighWatermark Unsigned32, 455 vplsConfigFwdFullLowWatermark Unsigned32, 456 vplsConfigRowStatus RowStatus, 457 vplsConfigMtu Unsigned32, 458 vplsConfigVpnId VPNIdOrZero, 459 vplsConfigServiceType INTEGER, 460 vplsConfigStorageType StorageType 461 } 463 vplsConfigIndex OBJECT-TYPE 464 SYNTAX Unsigned32 (1.. 2147483647) 466 MAX-ACCESS not-accessible 467 STATUS current 468 DESCRIPTION 469 "Unique index for the conceptual row identifying 470 a VPLS service." 471 ::= { vplsConfigEntry 1 } 473 vplsConfigName OBJECT-TYPE 474 SYNTAX SnmpAdminString 475 MAX-ACCESS read-create 476 STATUS current 477 DESCRIPTION 478 "A textual name of the VPLS. 479 If there is no local name, or this object is 480 otherwise not applicable, then this object MUST 481 contain a zero-length octet string." 482 DEFVAL { "" } 483 ::= { vplsConfigEntry 2 } 485 vplsConfigDescr OBJECT-TYPE 486 SYNTAX SnmpAdminString 487 MAX-ACCESS read-create 488 STATUS current 489 DESCRIPTION 490 "A textual string containing information about the 491 VPLS service. If there is no information for this VPLS 492 service, then this object MUST contain a zero-length 494 draft-nadeau-l2vpn-vpls-mib-03 L2-VPN-MIB Dec 22, 2006 496 octet string." 497 DEFVAL { "" } 498 ::= { vplsConfigEntry 3 } 500 vplsConfigAdminStatus OBJECT-TYPE 501 SYNTAX INTEGER { 502 up(1), 503 down(2), 504 testing(3) -- in some test mode 506 } 507 MAX-ACCESS read-create 508 STATUS current 509 DESCRIPTION 510 "The desired administrative state of the VPLS 511 service. If the administrative status of the 512 Vpls service is changed to enable then this 513 service is able to utilize the pseudo wire to 514 perform the tasks of a VPLS service. 515 The testing(3) state indicates that no operational 516 packets can be passed. " 518 DEFVAL { down } 519 ::= { vplsConfigEntry 4 } 521 vplsConfigMacLearning OBJECT-TYPE 522 SYNTAX TruthValue 523 MAX-ACCESS read-create 524 STATUS current 525 DESCRIPTION 526 "This object specifies if MAC Learning is enabled 527 in this service. If this object is true then Mac 528 Learning is enabled. If false, then Mac Learning is 529 disabled." 530 DEFVAL { true } 531 ::= { vplsConfigEntry 6 } 533 vplsConfigDiscardUnknownDest OBJECT-TYPE 534 SYNTAX TruthValue 535 MAX-ACCESS read-create 536 STATUS current 537 DESCRIPTION 538 "If the value of this object is 'true', then frames 539 received with an unknown destination MAC are discarded 540 in this VPLS. If 'false', then the packets are 541 processed." 542 DEFVAL { false } 544 draft-nadeau-l2vpn-vpls-mib-03 L2-VPN-MIB Dec 22, 2006 546 ::= { vplsConfigEntry 7 } 548 vplsConfigMacAging OBJECT-TYPE 549 SYNTAX TruthValue 550 MAX-ACCESS read-create 551 STATUS current 552 DESCRIPTION 553 "If the value of this object is 'true' 554 then the MAC ageing process is enabled in 555 this VPLS. If 'false', then the MAC ageing process 556 is disabled" 557 DEFVAL { true } 558 ::= { vplsConfigEntry 8 } 560 vplsConfigFwdFullHighWatermark OBJECT-TYPE 561 SYNTAX Unsigned32 (0..100) 562 UNITS "percentage" 563 MAX-ACCESS read-create 564 STATUS current 565 DESCRIPTION 567 "This object specifies the utilization of the 568 forwarding database for this VPLS instance at 569 which the vplsFwdFullAlarmRaised notification 570 will be sent." 571 DEFVAL { 95 } 572 ::= { vplsConfigEntry 10 } 574 vplsConfigFwdFullLowWatermark OBJECT-TYPE 575 SYNTAX Unsigned32 (0..100) 576 UNITS "percentage" 577 MAX-ACCESS read-create 578 STATUS current 579 DESCRIPTION 580 "This object specifies the utilization of the 581 forwarding database for this VPLS instance 582 at which the vplsFwdFullAlarmCleared 583 notification will be sent." 584 DEFVAL { 90 } 585 ::= { vplsConfigEntry 11 } 587 vplsConfigRowStatus OBJECT-TYPE 588 SYNTAX RowStatus 589 MAX-ACCESS read-create 590 STATUS current 591 DESCRIPTION 592 "For creating, modifying, and deleting this row. 594 draft-nadeau-l2vpn-vpls-mib-03 L2-VPN-MIB Dec 22, 2006 596 None of the read-create objects in the 597 conceptual rows may be changed when this 598 object is in the active(1) state." 599 ::= { vplsConfigEntry 12 } 601 vplsConfigMtu OBJECT-TYPE 602 SYNTAX Unsigned32 (64..1518) 603 MAX-ACCESS read-create 604 STATUS current 605 DESCRIPTION 606 "The value of this object specifies the MTU of this 607 vpls instance." 608 DEFVAL { 1518 } 609 ::= { vplsConfigEntry 13 } 611 vplsConfigVpnId OBJECT-TYPE 612 SYNTAX VPNIdOrZero 613 MAX-ACCESS read-only 614 STATUS current 615 DESCRIPTION 616 "This objects indicates the IEEE 802-1990 617 VPN ID of the associated VPLS service." 618 -- Ed note: Should we import the VPNIdOrZero TC or 619 -- define a new TC? 620 ::= { vplsConfigEntry 14 } 622 vplsConfigServiceType OBJECT-TYPE 623 SYNTAX INTEGER { 624 vlan (1), 625 ethernet (2) 626 } 627 MAX-ACCESS read-create 628 STATUS current 629 DESCRIPTION 630 "The value of this object specifies the type of 631 service emulated by this vpls instance." 632 DEFVAL { vlan } 633 ::= { vplsConfigEntry 15 } 635 vplsConfigStorageType OBJECT-TYPE 636 SYNTAX StorageType 637 MAX-ACCESS read-create 638 STATUS current 639 DESCRIPTION 640 "This variable indicates the storage type for this row." 641 DEFVAL { volatile } 642 ::= { vplsConfigEntry 16 } 644 draft-nadeau-l2vpn-vpls-mib-03 L2-VPN-MIB Dec 22, 2006 646 -- VPLS Status table 648 vplsStatusTable OBJECT-TYPE 649 SYNTAX SEQUENCE OF VplsStatusEntry 650 MAX-ACCESS not-accessible 651 STATUS current 652 DESCRIPTION 654 "This table provides information for monitoring 655 Virtual Private Lan Services(VPLS). 656 " 657 ::= { vplsObjects 3 } 659 vplsStatusEntry OBJECT-TYPE 660 SYNTAX VplsStatusEntry 661 MAX-ACCESS not-accessible 662 STATUS current 663 DESCRIPTION 664 "A row in this table represents a Virtual Private Lan 665 Service(VPLS) in a packet network. It is indexed by 666 vplsConfigIndex, which uniquely identifies a single VPLS. 668 A row in this table is automatically created by the agent 669 when a VPLS service is configured. 670 " 671 INDEX { vplsConfigIndex } 672 ::= { vplsStatusTable 1 } 674 VplsStatusEntry ::= 675 SEQUENCE { 676 vplsStatusOperStatus INTEGER, 677 vplsStatusPeerCount Counter32 678 } 680 vplsStatusOperStatus OBJECT-TYPE 681 SYNTAX INTEGER { 682 other(0), 683 up(1), 684 down(2) 685 } 686 MAX-ACCESS read-only 687 STATUS current 688 DESCRIPTION 689 "The current operational state of this VPLS Service." 690 ::= { vplsStatusEntry 1 } 692 vplsStatusPeerCount OBJECT-TYPE 693 draft-nadeau-l2vpn-vpls-mib-03 L2-VPN-MIB Dec 22, 2006 695 SYNTAX Counter32 696 MAX-ACCESS read-only 697 STATUS current 698 DESCRIPTION 699 "This objects specifies the number of peers 700 present in this vpls instance." 701 ::= { vplsStatusEntry 2 } 703 -- VPLS PW Binding Table 705 vplsPwBindTable OBJECT-TYPE 706 SYNTAX SEQUENCE OF VplsPwBindEntry 707 MAX-ACCESS not-accessible 708 STATUS current 709 DESCRIPTION 710 "This table provides an association between a 711 VPLS service and the corresponding Pseudo 712 Wires. A service can have more than one Pseudo 713 Wire association. Pseudo Wires are defined in 714 the pwTable" 715 ::= { vplsObjects 4 } 717 vplsPwBindEntry OBJECT-TYPE 718 SYNTAX VplsPwBindEntry 719 MAX-ACCESS not-accessible 720 STATUS current 721 DESCRIPTION 722 "Each row represents an association between a 723 VPLS instance and one or more Pseudo Wires 724 defined in the pwTable. Each index is unique 725 in describing an entry in this table. However 726 both indexes are required to define the one 727 to many association of service to 728 pseudowire." 729 INDEX { vplsConfigIndex, vplsPwBindIndex } 730 ::= { vplsPwBindTable 1 } 732 VplsPwBindEntry ::= 733 SEQUENCE { 734 vplsPwBindIndex PwIndexType, 735 vplsPwBindConfigType INTEGER, 736 vplsPwBindType INTEGER, 737 vplsPwBindRowStatus RowStatus, 738 vplsPwBindStorageType StorageType 739 } 741 vplsPwBindIndex OBJECT-TYPE 742 draft-nadeau-l2vpn-vpls-mib-03 L2-VPN-MIB Dec 22, 2006 744 SYNTAX PwIndexType 745 MAX-ACCESS not-accessible 746 STATUS current 747 DESCRIPTION 748 "Secondary Index for the conceptual row identifying 749 a pseudowire within the PwEntry which MUST 750 match an entry from the PW-STD-MIB's PwTable 751 which represents an already-provisioned 752 pseuwowire that is then associated with this 753 VPLS instance." 754 ::= { vplsPwBindEntry 1 } 756 vplsPwBindConfigType OBJECT-TYPE 757 SYNTAX INTEGER { 758 manual (1), 759 autodiscovery (2) 760 } 761 MAX-ACCESS read-create 762 STATUS current 763 DESCRIPTION 764 "The value of this object indicates 765 whether the Pseudo Wire binding was created 766 manually or via autodiscovery. 768 The value of this object must be 769 specifed when the row is created and cannot 770 be changed while the row status is active(1)" 771 ::= { vplsPwBindEntry 2 } 773 vplsPwBindType OBJECT-TYPE 774 SYNTAX INTEGER { 775 mesh (1), 776 spoke (2) 777 } 778 MAX-ACCESS read-create 779 STATUS current 780 DESCRIPTION 781 "The value of this object indicates 782 whether the Pseudo Wire binding is of 783 type mesh or spoke. 785 The value of this object must be 786 specifed when the row is created and cannot 787 be changed while the row status is active(1)" 788 ::= { vplsPwBindEntry 3 } 790 vplsPwBindRowStatus OBJECT-TYPE 791 SYNTAX RowStatus 793 draft-nadeau-l2vpn-vpls-mib-03 L2-VPN-MIB Dec 22, 2006 795 MAX-ACCESS read-create 796 STATUS current 797 DESCRIPTION 798 "For creating, modifying, and deleting this row. 799 None of the read-create objects in the 800 conceptual rows may be changed when this 801 object is in the active(1) state" 802 ::= { vplsPwBindEntry 4 } 804 vplsPwBindStorageType OBJECT-TYPE 805 SYNTAX StorageType 806 MAX-ACCESS read-create 807 STATUS current 808 DESCRIPTION 809 "This variable indicates the storage type for this row." 810 DEFVAL { volatile } 811 ::= { vplsPwBindEntry 5 } 813 vplsStatusNotifEnable OBJECT-TYPE 814 SYNTAX TruthValue 815 MAX-ACCESS read-write 816 STATUS current 817 DESCRIPTION 818 "If this object is set to true(1), then it enables 819 the emission of vplsStatusChanged 820 notification; otherwise this notification is not 821 emitted." 822 REFERENCE 823 "See also [RFC3413] for explanation that 824 notifications are under the ultimate control of the 825 MIB module in this document." 826 DEFVAL { false } 827 ::= { vplsObjects 5 } 829 vplsNotificationMaxRate OBJECT-TYPE 830 SYNTAX Unsigned32 831 MAX-ACCESS read-write 832 STATUS current 833 DESCRIPTION 834 "This object indicates the maximum number of 835 notifications issued per second. If events occur 836 more rapidly, the implementation may simply fail to 837 emit these notifications during that period, or may 838 queue them until an appropriate time. A value of 0 839 means no throttling is applied and events may be 840 notified at the rate at which they occur." 841 DEFVAL { 0 } 842 ::= { vplsObjects 6 } 843 draft-nadeau-l2vpn-vpls-mib-03 L2-VPN-MIB Dec 22, 2006 845 -- VPLS Service Notifications 847 vplsStatusChanged NOTIFICATION-TYPE 848 OBJECTS { 849 vplsConfigVpnId, 850 vplsConfigAdminStatus, 851 vplsStatusOperStatus 852 } 853 STATUS current 854 DESCRIPTION 855 "The vplsStatusChanged notification is generated 856 when there is a change in the administrative or 857 operating status of a VPLS service." 858 ::= { vplsNotifications 1 } 860 vplsFwdFullAlarmRaised NOTIFICATION-TYPE 861 OBJECTS { 862 vplsConfigVpnId, 863 vplsConfigFwdFullHighWatermark, 864 vplsConfigFwdFullLowWatermark 865 } 866 STATUS current 867 DESCRIPTION 868 "The vplsFwdFullAlarmRaised notification is 869 generated when the utilization of the Forwarding 870 database is above the value specified by 871 vplsConfigFwdFullHighWatermark." 872 ::= { vplsNotifications 2 } 874 vplsFwdFullAlarmCleared NOTIFICATION-TYPE 875 OBJECTS { 876 vplsConfigVpnId, 877 vplsConfigFwdFullHighWatermark, 878 vplsConfigFwdFullLowWatermark 879 } 880 STATUS current 881 DESCRIPTION 882 "The vplsFwdFullAlarmCleared notification is 883 generated when the utilization of the Forwarding 884 database is below the value specified by 885 vplsConfigFwdFullLowWatermark." 886 ::= { vplsNotifications 3 } 888 -- Compliance requirement for read-only implementations. 890 vplsCompliances 891 OBJECT IDENTIFIER ::= { vplsConformance 1 } 892 draft-nadeau-l2vpn-vpls-mib-03 L2-VPN-MIB Dec 22, 2006 894 vplsModuleFullCompliance MODULE-COMPLIANCE 895 STATUS current 896 DESCRIPTION 897 "Compliance requirement for implementations that 898 provide full support for VPLS-GENERIC-DRAFT-01-MIB. 899 Such devices can then be monitored and configured using 900 this MIB module." 901 MODULE -- this module 903 MANDATORY-GROUPS { 904 vplsGroup, 905 vplsPwBindGroup, 906 vplsNotificationGroup 907 } 909 ::= { vplsCompliances 1 } 911 vplsModuleReadOnlyCompliance MODULE-COMPLIANCE 912 STATUS current 913 DESCRIPTION 914 "Compliance requirement for implementations that only 915 provide read-only support for VPLS-GENERIC-DRAFT-01-MIB. 916 Such devices can then be monitored but cannot be 917 configured using this MIB modules." 919 MODULE -- this module 921 MANDATORY-GROUPS { 922 vplsGroup, 923 vplsPwBindGroup, 924 vplsNotificationGroup 925 } 927 OBJECT vplsConfigName 928 MIN-ACCESS read-only 929 DESCRIPTION 930 "Write access is not required." 932 OBJECT vplsConfigDescr 933 MIN-ACCESS read-only 934 DESCRIPTION 935 "Write access is not required." 937 OBJECT vplsConfigAdminStatus 938 MIN-ACCESS read-only 940 draft-nadeau-l2vpn-vpls-mib-03 L2-VPN-MIB Dec 22, 2006 942 DESCRIPTION 943 "Write access is not required." 945 OBJECT vplsConfigMacLearning 946 MIN-ACCESS read-only 947 DESCRIPTION 948 "Write access is not required." 950 OBJECT vplsConfigDiscardUnknownDest 951 MIN-ACCESS read-only 952 DESCRIPTION 953 "Write access is not required." 955 OBJECT vplsConfigMacAging 956 MIN-ACCESS read-only 957 DESCRIPTION 958 "Write access is not required." 960 OBJECT vplsConfigFwdFullHighWatermark 961 MIN-ACCESS read-only 962 DESCRIPTION 963 "Write access is not required." 965 OBJECT vplsConfigFwdFullLowWatermark 966 MIN-ACCESS read-only 967 DESCRIPTION 968 "Write access is not required." 970 OBJECT vplsConfigRowStatus 971 MIN-ACCESS read-only 972 DESCRIPTION 973 "Write access is not required." 975 OBJECT vplsConfigMtu 976 MIN-ACCESS read-only 977 DESCRIPTION 978 "Write access is not required." 980 OBJECT vplsConfigServiceType 981 MIN-ACCESS read-only 982 DESCRIPTION 983 "Write access is not required." 985 OBJECT vplsPwBindConfigType 986 MIN-ACCESS read-only 987 DESCRIPTION 988 "Write access is not required." 990 draft-nadeau-l2vpn-vpls-mib-03 L2-VPN-MIB Dec 22, 2006 992 OBJECT vplsPwBindType 993 MIN-ACCESS read-only 994 DESCRIPTION 995 "Write access is not required." 997 OBJECT vplsPwBindRowStatus 998 MIN-ACCESS read-only 999 DESCRIPTION 1000 "Write access is not required." 1002 ::= { vplsCompliances 2 } 1004 -- Units of conformance. 1006 vplsGroups 1007 OBJECT IDENTIFIER ::= { vplsConformance 2 } 1009 vplsGroup OBJECT-GROUP 1010 OBJECTS { 1011 vplsConfigName, 1012 vplsConfigDescr, 1013 vplsConfigAdminStatus, 1014 vplsConfigMacLearning, 1015 vplsConfigDiscardUnknownDest, 1016 vplsConfigMacAging, 1017 vplsConfigVpnId, 1018 vplsConfigFwdFullHighWatermark, 1019 vplsConfigFwdFullLowWatermark, 1020 vplsConfigRowStatus, 1021 vplsConfigIndexNext, 1022 vplsConfigMtu, 1023 vplsConfigServiceType, 1024 vplsConfigStorageType, 1026 vplsStatusOperStatus, 1027 vplsStatusPeerCount, 1029 vplsStatusNotifEnable, 1030 vplsNotificationMaxRate 1031 } 1032 STATUS current 1033 DESCRIPTION 1034 "The group of objects supporting 1035 management of L2VPN VPLS services" 1036 ::= { vplsGroups 1 } 1038 vplsPwBindGroup OBJECT-GROUP 1039 draft-nadeau-l2vpn-vpls-mib-03 L2-VPN-MIB Dec 22, 2006 1041 OBJECTS { 1042 vplsPwBindConfigType, 1043 vplsPwBindType, 1044 vplsPwBindRowStatus, 1045 vplsPwBindStorageType 1046 } 1047 STATUS current 1048 DESCRIPTION 1049 "The group of objects supporting 1050 management of 1051 Pseudo Wire (PW) Binding to VPLS." 1052 ::= { vplsGroups 2 } 1054 vplsNotificationGroup NOTIFICATION-GROUP 1055 NOTIFICATIONS { 1056 vplsStatusChanged, 1057 vplsFwdFullAlarmRaised, 1058 vplsFwdFullAlarmCleared 1059 } 1060 STATUS current 1061 DESCRIPTION 1062 "The group of notifications supporting 1063 the Notifications generated for 1064 VPLS Services" 1065 ::= { vplsGroups 3 } 1067 END 1069 6.2 VPLS-LDP-DRAFT-01-MIB Object definitions 1071 This MIB module makes references to the following documents. 1072 [RFC2578], [RFC2579], [RFC2580], [RFC2571], [RFC3411], 1073 [RFC2863], [RFC4001], [RFC4265] and [RFC3813]. 1075 VPLS-LDP-DRAFT-01-MIB DEFINITIONS ::= BEGIN 1077 IMPORTS 1078 MODULE-IDENTITY, OBJECT-TYPE, 1079 Unsigned32, transmission 1080 FROM SNMPv2-SMI -- RFC2578 1082 MODULE-COMPLIANCE, OBJECT-GROUP 1083 FROM SNMPv2-CONF -- RFC2580 1085 TruthValue 1086 FROM SNMPv2-TC -- RFC2579 1088 draft-nadeau-l2vpn-vpls-mib-03 L2-VPN-MIB Dec 22, 2006 1090 vplsConfigIndex, vplsPwBindIndex 1091 FROM VPLS-GENERIC-DRAFT-01-MIB 1092 ; 1094 vplsLdpDraft01MIB MODULE-IDENTITY 1095 LAST-UPDATED "200608301200Z" -- 20 August 2006 12:00:00 GMT 1096 ORGANIZATION "Layer 2 Virtual Private Networks (L2VPN) 1097 Working Group" 1098 CONTACT-INFO 1099 " 1100 Thomas D. Nadeau 1101 Email: tnadeau@cisco.com 1103 The L2VPN Working Group (email distribution l2vpn@ietf.org, 1104 http://www.ietf.org/html.charters/l2vpn-charter.html) 1105 " 1107 DESCRIPTION 1108 "Copyright (C) The Internet Society (2007). The initial 1109 version of this MIB module was published in RFC XXXX. 1110 -- RFC Editor: Please replace XXXX with RFC number & remove 1111 -- this note. 1113 For full legal notices see the RFC itself or see: 1114 http://www.ietf.org/copyrights/ianamib.html 1116 This MIB module contains managed object definitions for 1117 LDP signalled Virtual Private LAN Services as in 1118 [L2VPN-VPLS-LDP] 1120 This MIB module enables the use of any underlying Pseudo Wire 1121 network. " 1123 -- Revision history. 1125 REVISION 1126 "200608301200Z" -- 30 Aug 2006 12:00:00 GMT 1127 DESCRIPTION "Initial version published as part of RFC YYYY." 1128 -- RFC Editor: please replace YYYY with IANA assigned value, and 1129 -- delete this note. 1131 ::= { transmission XXXX } 1132 -- RFC Editor: please replace XXXX with IANA assigne value, and 1133 -- delete this note. 1135 -- Top-level components of this MIB. 1137 draft-nadeau-l2vpn-vpls-mib-03 L2-VPN-MIB Dec 22, 2006 1139 -- Tables, Scalars 1140 vplsLdpObjects OBJECT IDENTIFIER 1141 ::= { vplsLdpDraft01MIB 1 } 1142 -- Conformance 1143 vplsLdpConformance OBJECT IDENTIFIER 1144 ::= { vplsLdpDraft01MIB 2 } 1146 vplsLdpConfigTable OBJECT-TYPE 1147 SYNTAX SEQUENCE OF VplsLdpConfigEntry 1148 MAX-ACCESS not-accessible 1149 STATUS current 1150 DESCRIPTION 1151 "This table specifies information for configuring 1152 and monitoring LDP specific parameters for 1153 Virtual Private Lan Services(VPLS)." 1154 ::= { vplsLdpObjects 1 } 1156 vplsLdpConfigEntry OBJECT-TYPE 1157 SYNTAX VplsLdpConfigEntry 1158 MAX-ACCESS not-accessible 1159 STATUS current 1160 DESCRIPTION 1161 "A row in this table represents LDP specific information 1162 for Virtual Private Lan Service(VPLS) in a packet network. 1163 It is indexed by vplsConfigIndex, which uniquely 1164 identifies a single VPLS. 1166 A row is automatically created when a VPLS service is 1167 configured using LDP signalling. 1169 None of the read-create objects values can be 1170 changed when vplsRowStatus is in the active(1) 1171 state. Changes are allowed when the vplsRowStatus 1172 is in notInService(2) or notReady(3) states only. 1173 If the operator need to change one of the values 1174 for an active row the vplsConfigRowStatus should be 1175 first changed to notInService(2), the objects may 1176 be changed now, and later to active(1) in order to 1177 re-initiate the signaling process with the new 1178 values in effect. 1179 " 1180 INDEX { vplsConfigIndex } 1181 ::= { vplsLdpConfigTable 1 } 1183 VplsLdpConfigEntry ::= 1184 SEQUENCE { 1185 vplsLdpConfigMacAddrWithdraw TruthValue 1186 } 1188 draft-nadeau-l2vpn-vpls-mib-03 L2-VPN-MIB Dec 22, 2006 1190 vplsLdpConfigMacAddrWithdraw OBJECT-TYPE 1191 SYNTAX TruthValue 1192 MAX-ACCESS read-create 1193 STATUS current 1194 DESCRIPTION 1195 "This object specifies if MAC address withdrawal 1196 is enabled in this service. If this object is true then 1197 Mac address withdrawl Learning is enabled. If false, 1198 then Mac Learning is disabled." 1199 DEFVAL { true } 1200 ::= { vplsLdpConfigEntry 1 } 1202 -- VPLS LDP PW Binding Table 1204 vplsLdpPwBindTable OBJECT-TYPE 1205 SYNTAX SEQUENCE OF VplsLdpPwBindEntry 1206 MAX-ACCESS not-accessible 1207 STATUS current 1208 DESCRIPTION 1209 "This table provides LDP specific information for 1210 an association between a VPLS service and the 1211 corresponding Pseudo Wires. A service can have more 1212 than one Pseudo Wire association. Pseudo Wires are 1213 defined in the pwTable." 1214 ::= { vplsLdpObjects 2 } 1216 vplsLdpPwBindEntry OBJECT-TYPE 1217 SYNTAX VplsLdpPwBindEntry 1218 MAX-ACCESS not-accessible 1219 STATUS current 1220 DESCRIPTION 1221 "Each row represents an association between a 1222 VPLS instance and one or more Pseudo Wires 1223 defined in the pwTable. Each index is unique 1224 in describing an entry in this table. However 1225 both indexes are required to define the one 1226 to many association of service to pseudowire. 1228 An entry in this table in instantiated only when 1229 LDP signalling is used to configure VPLS service. 1231 Each entry in this table provides LDP specific 1232 information for the VPlS represented by 1233 vplsConfigIndex." 1234 INDEX { vplsConfigIndex, vplsPwBindIndex } 1235 ::= { vplsLdpPwBindTable 1 } 1237 draft-nadeau-l2vpn-vpls-mib-03 L2-VPN-MIB Dec 22, 2006 1239 VplsLdpPwBindEntry ::= 1240 SEQUENCE { 1241 vplsLdpPwBindMacAddressLimit Unsigned32 1242 } 1244 vplsLdpPwBindMacAddressLimit OBJECT-TYPE 1245 SYNTAX Unsigned32 (0.. 4294967295) 1246 MAX-ACCESS read-create 1247 STATUS current 1248 DESCRIPTION 1249 "The value of this object specifies the maximum number 1250 of learned and static entries allowed in the 1251 Forwarding database for this PW Binding. The value 0 1252 means there is no limit for this PW Binding." 1253 DEFVAL { 0 } 1254 ::= { vplsLdpPwBindEntry 1 } 1256 -- Compliance requirement for read-only implementations. 1258 vplsLdpCompliances 1259 OBJECT IDENTIFIER ::= { vplsLdpConformance 1 } 1261 vplsLdpModuleFullCompliance MODULE-COMPLIANCE 1262 STATUS current 1263 DESCRIPTION 1264 "Compliance requirement for implementations that 1265 provide full support for VPLS-LDP-DRAFT-01-MIB. 1266 Such devices can then be monitored and configured using 1267 this MIB module." 1269 MODULE -- this module 1271 MANDATORY-GROUPS { 1272 vplsLdpGroup 1273 } 1275 ::= { vplsLdpCompliances 1 } 1277 vplsLdpModuleReadOnlyCompliance MODULE-COMPLIANCE 1278 STATUS current 1279 DESCRIPTION 1280 "Compliance requirement for implementations that only 1281 provide read-only support for VPLS-LDP-DRAFT-01-MIB. 1282 Such devices can then be monitored but cannot be 1283 configured using this MIB modules." 1285 MODULE -- this module 1286 draft-nadeau-l2vpn-vpls-mib-03 L2-VPN-MIB Dec 22, 2006 1288 MANDATORY-GROUPS { 1289 vplsLdpGroup 1290 } 1292 OBJECT vplsLdpConfigMacAddrWithdraw 1293 MIN-ACCESS read-only 1294 DESCRIPTION 1295 "Write access is not required." 1297 OBJECT vplsLdpPwBindMacAddressLimit 1298 MIN-ACCESS read-only 1299 DESCRIPTION 1300 "Write access is not required." 1302 ::= { vplsLdpCompliances 2 } 1304 -- Units of conformance. 1306 vplsLdpGroups 1307 OBJECT IDENTIFIER ::= { vplsLdpConformance 2 } 1309 vplsLdpGroup OBJECT-GROUP 1310 OBJECTS { 1311 vplsLdpConfigMacAddrWithdraw, 1312 vplsLdpPwBindMacAddressLimit 1313 } 1314 STATUS current 1315 DESCRIPTION 1316 "The group of objects supporting 1317 management of L2VPN VPLS services using LDP." 1318 ::= { vplsLdpGroups 1 } 1320 END 1322 6.3 VPLS-BGP-DRAFT-01-MIB Object definitions 1324 VPLS-BGP-DRAFT-01-MIB DEFINITIONS ::= BEGIN 1326 IMPORTS 1327 MODULE-IDENTITY, OBJECT-TYPE, 1328 Unsigned32, transmission 1329 FROM SNMPv2-SMI -- RFC2578 1331 MODULE-COMPLIANCE, OBJECT-GROUP 1332 FROM SNMPv2-CONF -- RFC2580 1334 RowStatus, StorageType, TEXTUAL-CONVENTION 1335 draft-nadeau-l2vpn-vpls-mib-03 L2-VPN-MIB Dec 22, 2006 1337 FROM SNMPv2-TC -- RFC2579 1339 SnmpAdminString 1340 FROM SNMP-FRAMEWORK-MIB -- RFC3411 1342 vplsConfigIndex, vplsPwBindIndex 1343 FROM VPLS-GENERIC-DRAFT-01-MIB 1344 ; 1346 vplsBgpDraft01MIB MODULE-IDENTITY 1347 LAST-UPDATED "200612061200Z" -- 06 Dec 2006 12:00:00 GMT 1348 ORGANIZATION "Layer 2 Virtual Private Networks (L2VPN) 1349 Working Group" 1350 CONTACT-INFO 1351 " 1352 V. J. Shah 1353 Email: vshah@juniper.net 1355 The L2VPN Working Group (email distribution l2vpn@ietf.org, 1356 http://www.ietf.org/html.charters/l2vpn-charter.html) 1357 " 1358 DESCRIPTION 1359 "Copyright (C) The Internet Society (2007). The initial 1360 version of this MIB module was published in RFC XXXX. 1361 -- RFC Editor: Please replace XXXX with RFC number & remove 1362 -- this note. 1364 For full legal notices see the RFC itself or see: 1365 http://www.ietf.org/copyrights/ianamib.html 1367 This MIB module contains managed object definitions for 1368 BGP signalled Virtual Private LAN Services as in 1369 [L2VPN-VPLS-BGP] 1371 This MIB module enables the use of any underlying Pseudo Wire 1372 network. " 1374 -- Revision history. 1375 REVISION 1376 "200612061200Z" -- 06 Dec 2006 12:00:00 GMT 1377 DESCRIPTION "Initial version published as part of RFC YYYY." 1378 -- RFC Editor: please replace YYYY with IANA assigned value, and 1379 -- delete this note. 1380 ::= { transmission XXXX } 1381 -- RFC Editor: please replace XXXX with IANA assigne value, and 1382 -- delete this note. 1384 -- VPLS BGP specific Textual Conventions. 1386 draft-nadeau-l2vpn-vpls-mib-03 L2-VPN-MIB Dec 22, 2006 1388 VplsBgpRouteDistinguisher ::= TEXTUAL-CONVENTION 1389 STATUS current 1390 DESCRIPTION 1391 "Syntax for a route distinguisher. For a complete 1392 definition of a route distinguisher, see [RFC4364]. 1393 For more details on use of a route distinguisher 1394 for a VPLS service, see [L2VPN-VPLS-BGP]" 1395 REFERENCE 1396 "[RFC4364]" 1397 SYNTAX OCTET STRING(SIZE (0..256)) 1399 VplsBgpRouteTarget ::= TEXTUAL-CONVENTION 1400 STATUS current 1401 DESCRIPTION 1402 "Syntax for a route target. For a complete 1403 definition of a route target, see [RFC4364]." 1404 REFERENCE 1405 "[RFC4364]" 1406 SYNTAX OCTET STRING(SIZE (0..256)) 1408 -- Top-level components of this MIB. 1410 -- Tables, Scalars 1411 vplsBgpObjects OBJECT IDENTIFIER 1412 ::= { vplsBgpDraft01MIB 1 } 1413 -- Conformance 1414 vplsBgpConformance OBJECT IDENTIFIER 1415 ::= { vplsBgpDraft01MIB 2 } 1417 -- Vpls Bgp Config Table 1419 vplsBgpConfigTable OBJECT-TYPE 1420 SYNTAX SEQUENCE OF VplsBgpConfigEntry 1421 MAX-ACCESS not-accessible 1422 STATUS current 1423 DESCRIPTION 1424 "This table specifies information for configuring 1425 and monitoring BGP specific parameters for 1426 Virtual Private Lan Services(VPLS)." 1427 ::= { vplsBgpObjects 1 } 1429 vplsBgpConfigEntry OBJECT-TYPE 1430 SYNTAX VplsBgpConfigEntry 1431 MAX-ACCESS not-accessible 1432 STATUS current 1433 DESCRIPTION 1434 "A row in this table represents BGP specific information 1435 for Virtual Private Lan Service(VPLS) in a packet network. 1437 draft-nadeau-l2vpn-vpls-mib-03 L2-VPN-MIB Dec 22, 2006 1439 It is indexed by vplsConfigIndex, which uniquely 1440 identifies a single instance of a VPLS service. 1442 A row is automatically created when a VPLS service is 1443 configured using BGP signalling. 1445 None of the read-create objects values can be 1446 changed when vplsRowStatus is in the active(1) 1447 state. Changes are allowed when the vplsRowStatus 1448 is in notInService(2) or notReady(3) states only. 1449 If the operator need to change one of the values 1450 for an active row the vplsConfigRowStatus should be 1451 first changed to notInService(2), the objects may 1452 be changed now, and later to active(1) in order to 1453 re-initiate the signaling process with the new 1454 values in effect. 1455 " 1456 INDEX { vplsConfigIndex } 1457 ::= { vplsBgpConfigTable 1 } 1459 VplsBgpConfigEntry ::= 1460 SEQUENCE { 1461 vplsBgpConfigRouteDistinguisher VplsBgpRouteDistinguisher, 1462 vplsBgpConfigRouteTarget VplsBgpRouteTarget, 1463 vplsBgpConfigVERangeSize Unsigned32 1464 } 1466 vplsBgpConfigRouteDistinguisher OBJECT-TYPE 1467 SYNTAX VplsBgpRouteDistinguisher 1468 MAX-ACCESS read-create 1469 STATUS current 1470 DESCRIPTION 1471 "The route distinguisher for this VPLS. See [RFC4364] 1472 for a complete definition of a route distinguisher. 1473 For more details on use of a route distinguisher 1474 for a VPLS service, see [L2VPN-VPLS-BGP]" 1475 DEFVAL { "" } 1476 ::= { vplsBgpConfigEntry 1 } 1478 vplsBgpConfigRouteTarget OBJECT-TYPE 1479 SYNTAX VplsBgpRouteTarget 1480 MAX-ACCESS read-create 1481 STATUS current 1482 DESCRIPTION 1483 "The route target associated with the VPLS service. 1484 For more details on use of route targets 1485 for a VPLS service, see [L2VPN-VPLS-BGP]" 1486 DEFVAL { "" } 1487 draft-nadeau-l2vpn-vpls-mib-03 L2-VPN-MIB Dec 22, 2006 1489 ::= { vplsBgpConfigEntry 2 } 1491 vplsBgpConfigVERangeSize OBJECT-TYPE 1492 SYNTAX Unsigned32 (0..65535) 1493 MAX-ACCESS read-create 1494 STATUS current 1495 DESCRIPTION 1496 "Specifies the size of the range of VE ids in this 1497 VPLS service. This number controls the size of the 1498 label block advertised for this VE by the PE. 1499 A value of 0 indicates that the range is not 1500 configured and the PE derives the range value 1501 from received advertisements from other PEs." 1502 DEFVAL { 0 } 1503 ::= { vplsBgpConfigEntry 3 } 1505 -- Vpls Edge Device (VE) Identifier Table 1507 vplsBgpVETable OBJECT-TYPE 1508 SYNTAX SEQUENCE OF VplsBgpVEEntry 1509 MAX-ACCESS not-accessible 1510 STATUS current 1511 DESCRIPTION 1512 "This table associates VPLS Edge devices to a VPLS service" 1513 ::= { vplsBgpObjects 3 } 1515 vplsBgpVEEntry OBJECT-TYPE 1516 SYNTAX VplsBgpVEEntry 1517 MAX-ACCESS not-accessible 1518 STATUS current 1519 DESCRIPTION 1520 "An entry in this table is created for each VE Id 1521 configured on a PE for a particular VPLS service 1522 instance." 1523 INDEX { vplsConfigIndex, vplsBgpVEId } 1524 ::= { vplsBgpVETable 1 } 1526 VplsBgpVEEntry ::= SEQUENCE { 1527 vplsBgpVEId Unsigned32, 1528 vplsBgpVEName SnmpAdminString, 1529 vplsBgpVEPreference Unsigned32, 1530 vplsBgpVERowStatus RowStatus, 1531 vplsBgpVEStorageType StorageType 1532 } 1534 vplsBgpVEId OBJECT-TYPE 1535 SYNTAX Unsigned32 (1..65535) 1536 MAX-ACCESS not-accessible 1537 draft-nadeau-l2vpn-vpls-mib-03 L2-VPN-MIB Dec 22, 2006 1539 STATUS current 1540 DESCRIPTION 1541 "A secondary index identifying a VE within an 1542 instance of a VPLS service." 1543 ::= { vplsBgpVEEntry 1 } 1545 vplsBgpVEName OBJECT-TYPE 1546 SYNTAX SnmpAdminString 1547 MAX-ACCESS read-create 1548 STATUS current 1549 DESCRIPTION 1550 "Descriptive name for the site or u-PE assciated with 1551 this VE Id." 1552 DEFVAL { "" } 1553 ::= { vplsBgpVEEntry 2 } 1555 vplsBgpVEPreference OBJECT-TYPE 1556 SYNTAX Unsigned32 (0..65535) 1557 MAX-ACCESS read-create 1558 STATUS current 1559 DESCRIPTION 1560 "Specifies the preference of the VE Id on this PE 1561 if the site is multi-homed and VE Id is re-used." 1562 DEFVAL { 0 } 1563 ::= { vplsBgpVEEntry 3 } 1565 vplsBgpVERowStatus OBJECT-TYPE 1566 SYNTAX RowStatus 1567 MAX-ACCESS read-create 1568 STATUS current 1569 DESCRIPTION 1570 "This variable is used to create, modify, and/or 1571 delete a row in this table. When a row in this 1572 table is in active(1) state, no objects in that row 1573 can be modified except vplsBgpSiteRowStatus." 1574 ::= { vplsBgpVEEntry 5 } 1576 vplsBgpVEStorageType OBJECT-TYPE 1577 SYNTAX StorageType 1578 MAX-ACCESS read-create 1579 STATUS current 1580 DESCRIPTION 1581 "This variable indicates the storage type for this row." 1582 DEFVAL { volatile } 1583 ::= { vplsBgpVEEntry 6 } 1585 -- VPLS BGP PW Binding Table 1586 draft-nadeau-l2vpn-vpls-mib-03 L2-VPN-MIB Dec 22, 2006 1588 vplsBgpPwBindTable OBJECT-TYPE 1589 SYNTAX SEQUENCE OF VplsBgpPwBindEntry 1590 MAX-ACCESS not-accessible 1591 STATUS current 1592 DESCRIPTION 1593 "This table provides BGP specific information for 1594 an association between a VPLS service and the 1595 corresponding Pseudo Wires. A service can have more 1596 than one Pseudo Wire association. Pseudo Wires are 1597 defined in the pwTable." 1598 ::= { vplsBgpObjects 4 } 1600 vplsBgpPwBindEntry OBJECT-TYPE 1601 SYNTAX VplsBgpPwBindEntry 1602 MAX-ACCESS not-accessible 1603 STATUS current 1604 DESCRIPTION 1605 "Each row represents an association between a 1606 VPLS instance and one or more Pseudo Wires 1607 defined in the pwTable. Each index is unique 1608 in describing an entry in this table. However 1609 both indexes are required to define the one 1610 to many association of service to pseudowire. 1612 An entry in this table in instantiated only when 1613 BGP signalling is used to configure VPLS service. 1615 Each entry in this table provides BGP specific 1616 information for the VPlS represented by 1617 vplsConfigIndex." 1618 INDEX { vplsConfigIndex, vplsPwBindIndex } 1619 ::= { vplsBgpPwBindTable 1 } 1621 VplsBgpPwBindEntry ::= 1622 SEQUENCE { 1623 vplsBgpPwBindLocalVEId Unsigned32, 1624 vplsBgpPwBindRemoteVEId Unsigned32 1625 } 1627 vplsBgpPwBindLocalVEId OBJECT-TYPE 1628 SYNTAX Unsigned32 (1..65535) 1629 MAX-ACCESS read-only 1630 STATUS current 1631 DESCRIPTION 1632 "Identifies the local VE that this Pseudo Wire 1633 is associated with." 1634 ::= { vplsBgpPwBindEntry 1 } 1636 vplsBgpPwBindRemoteVEId OBJECT-TYPE 1637 draft-nadeau-l2vpn-vpls-mib-03 L2-VPN-MIB Dec 22, 2006 1639 SYNTAX Unsigned32 (1..65535) 1640 MAX-ACCESS read-only 1641 STATUS current 1642 DESCRIPTION 1643 "Identifies the remote VE that this Pseudo Wire 1644 is associated with." 1645 ::= { vplsBgpPwBindEntry 2 } 1647 -- Compliance requirement for read-only implementations. 1649 vplsBgpCompliances 1650 OBJECT IDENTIFIER ::= { vplsBgpConformance 1 } 1652 vplsBgpModuleFullCompliance MODULE-COMPLIANCE 1653 STATUS current 1654 DESCRIPTION 1655 "Compliance requirement for implementations that 1656 provide full support for VPLS-BGP-DRAFT-01-MIB. 1657 Such devices can then be monitored and configured using 1658 this MIB module." 1660 MODULE -- this module 1662 MANDATORY-GROUPS { 1663 vplsBgpConfigGroup, 1664 vplsBgpVEGroup, 1665 vplsBgpPwBindGroup 1666 } 1667 ::= { vplsBgpCompliances 1 } 1669 vplsBgpModuleReadOnlyCompliance MODULE-COMPLIANCE 1670 STATUS current 1671 DESCRIPTION 1672 "Compliance requirement for implementations that only 1673 provide read-only support for VPLS-BGP-DRAFT-01-MIB. 1674 Such devices can then be monitored but cannot be 1675 configured using this MIB modules." 1677 MODULE -- this module 1679 MANDATORY-GROUPS { 1680 vplsBgpConfigGroup, 1681 vplsBgpVEGroup, 1682 vplsBgpPwBindGroup 1683 } 1685 OBJECT vplsBgpConfigRouteDistinguisher 1687 draft-nadeau-l2vpn-vpls-mib-03 L2-VPN-MIB Dec 22, 2006 1689 MIN-ACCESS read-only 1690 DESCRIPTION 1691 "Write access is not required." 1693 OBJECT vplsBgpConfigRouteTarget 1694 MIN-ACCESS read-only 1695 DESCRIPTION 1696 "Write access is not required." 1698 OBJECT vplsBgpConfigVERangeSize 1699 MIN-ACCESS read-only 1700 DESCRIPTION 1701 "Write access is not required." 1703 OBJECT vplsBgpVEName 1704 MIN-ACCESS read-only 1705 DESCRIPTION 1706 "Write access is not required." 1708 OBJECT vplsBgpVEPreference 1709 MIN-ACCESS read-only 1710 DESCRIPTION 1711 "Write access is not required." 1713 OBJECT vplsBgpVERowStatus 1714 MIN-ACCESS read-only 1715 DESCRIPTION 1716 "Write access is not required." 1718 ::= { vplsBgpCompliances 2 } 1720 -- Units of conformance. 1722 vplsBgpGroups 1723 OBJECT IDENTIFIER ::= { vplsBgpConformance 2 } 1725 vplsBgpConfigGroup OBJECT-GROUP 1726 OBJECTS { 1727 vplsBgpConfigRouteDistinguisher, 1728 vplsBgpConfigRouteTarget, 1729 vplsBgpConfigVERangeSize 1730 } 1731 STATUS current 1732 DESCRIPTION 1733 "The group of objects supporting configuration 1734 of L2VPN VPLS services using BGP" 1735 ::= { vplsBgpGroups 1 } 1737 draft-nadeau-l2vpn-vpls-mib-03 L2-VPN-MIB Dec 22, 2006 1739 vplsBgpVEGroup OBJECT-GROUP 1740 OBJECTS { 1741 vplsBgpVEName, 1742 vplsBgpVEPreference, 1743 vplsBgpVERowStatus, 1744 vplsBgpVEStorageType 1745 } 1746 STATUS current 1747 DESCRIPTION 1748 "The group of objects supporting management of VPLS 1749 Edge devices for L2VPN VPLS services using BGP" 1750 ::= { vplsBgpGroups 2 } 1752 vplsBgpPwBindGroup OBJECT-GROUP 1753 OBJECTS { 1754 vplsBgpPwBindLocalVEId, 1755 vplsBgpPwBindRemoteVEId 1756 } 1757 STATUS current 1758 DESCRIPTION 1759 "The group of objects supporting management of 1760 Pseudo Wires for L2VPN VPLS services using BGP" 1761 ::= { vplsBgpGroups 3 } 1763 END 1765 7. Security Considerations 1767 It is clear that the MIB modules described in this document in 1768 association with the PW-STD-MIB [PW-STD-MIB] are potentially 1769 useful for monitoring of GMPLS LSRs. These MIB modules can also be 1770 used for configuration of certain objects, and anything that can be 1771 configured can be incorrectly configured, with potentially disastrous 1772 results. 1774 There are a number of management objects defined in these MIB modules 1775 with a MAX-ACCESS clause of read-write and/or read-create. Such 1776 objects may be considered sensitive or vulnerable in some network 1777 environments. The support for SET operations in a non-secure 1778 environment without proper protection can have a negative effect on 1779 network operations. These are the tables and objects and their 1780 sensitivity/vulnerability: 1782 8. IANA Considerations 1784 -- (Note to RFC-Editor:) 1785 -- We request that you assign contiguous RFC numbers to the 1786 -- IANA is requested to root MIB objects in the MIB module 1787 draft-nadeau-l2vpn-vpls-mib-03 L2-VPN-MIB Dec 22, 2006 1789 -- contained in this document under the transmission subtree. 1790 -- 1792 9. References 1794 9.1 Normative References 1796 [PWE3-PW-MIB] Pseudo Wire (PW) Management Information Base. 1797 David Zelig, Thomas D. Nadeau, 1798 [L2VPN-VPLS-LDP] Virtual Private LAN Services over MPLS, 1799 Marc Lasserre, Vach Kompella, 1800 [L2VPN-VPLS-BGP] Virtual Private LAN Service (VPLS) Using BGP 1801 for Auto-discovery and Signaling, 1802 K. Kompella, Y. Rekhter, 1803 [RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, 1804 J., Rose, M., and S. Waldbusser, "Structure of 1805 Management Information Version 2 (SMIv2)", STD 58, RFC 1806 2578, April 1999. 1808 [RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, 1809 J., Rose, M., and S. Waldbusser, "Textual Conventions 1810 for SMIv2", STD 58, RFC 2579, April 1999. 1812 [RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, 1813 J., Rose, M., and S. Waldbusser, "Conformance Statements 1814 for SMIv2", STD 58, RFC 2580, April 1999. 1816 9.2. Informative References 1818 [RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart, 1819 "Introduction and Applicability Statements for 1820 Internet-Standard Management Framework", RFC 3410, 1821 December 2002. 1823 10. Acknowledgement 1825 We wish to thank Marcelo Mourier and Reva Bailey for their 1826 valuable feedback. Some portion of the work has been referenced 1827 from their original Timetra Enterprise MIB work. 1829 11. Authors' Addresses 1831 Thomas D. Nadeau 1832 Cisco Systems, Inc. 1833 1414 Massachusetts Ave. 1834 Boxborough, MA 01719 1835 Email: tnadeau@cisco.com 1836 draft-nadeau-l2vpn-vpls-mib-03 L2-VPN-MIB Dec 22, 2006 1838 A S Kiran Koushik 1839 Cisco Systems Inc. 1840 Email: kkoushik@cisco.com 1842 Rohit Mediratta 1843 Alcatel 1844 Email: rohit.mediratta@alcatel.com 1846 Praveen Muley 1847 Alcatel 1848 Email: praveen.muley@alcatel.com 1850 Reva Bailey 1851 Alcatel 1852 Email: reva.bailey@alcatel.com 1854 VJ Shah 1855 Juniper Networks 1856 Email: vshah@juniper.net 1858 Li Wentao 1859 ZTE Inc. 1860 CHINA 1861 Email: li.wentao@zte.com.cn 1863 Kong Yong 1864 ZTE Inc. 1865 CHINA 1866 Email: kong.yong@zte.com.cn 1868 Luo Jian 1869 ZTE Inc. 1870 CHINA 1871 Email: luo.jian@zte.com.cn 1873 Feng Jun 1874 ZTE Inc. 1875 CHINA 1876 Email: Feng.jun99@zte.com.cn 1878 Takeshi Usui 1879 KDDI Corpration 1880 Japan 1881 Email:ta-usui@kddi.com 1883 12. Intellectual Property Notice 1884 draft-nadeau-l2vpn-vpls-mib-03 L2-VPN-MIB Dec 22, 2006 1886 The IETF takes no position regarding the validity or scope of any 1887 Intellectual Property Rights or other rights that might be claimed to 1888 pertain to the implementation or use of the technology described in 1889 this document or the extent to which any license under such rights 1890 might or might not be available; nor does it represent that it has 1891 made any independent effort to identify any such rights. Information 1892 on the procedures with respect to rights in RFC documents can be 1893 found in BCP 78 and BCP 79. 1895 Copies of IPR disclosures made to the IETF Secretariat and any 1896 assurances of licenses to be made available, or the result of an 1897 attempt made to obtain a general license or permission for the use of 1898 such proprietary rights by implementers or users of this 1899 specification can be obtained from the IETF on-line IPR repository at 1900 http://www.ietf.org/ipr. 1902 The IETF invites any interested party to bring to its attention any 1903 copyrights, patents or patent applications, or other proprietary 1904 rights that may cover technology that may be required to implement 1905 this standard. Please address the information to the IETF at ietf- 1906 ipr@ietf.org. 1908 Disclaimer of Validity 1910 This document and the information contained herein are provided 1911 on an "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE 1912 REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE 1913 IETF TRUST AND THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL 1914 WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY 1915 WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE 1916 ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS 1917 FOR A PARTICULAR PURPOSE. 1919 13. Full Copyright Statement 1921 Copyright (C) The IETF Trust (2007). 1923 Copyright (C) The Internet Society (2007). This document is subject 1924 to the rights, licenses and restrictions contained in BCP 78, and 1925 except as set forth therein, the authors retain all their rights. 1927 This document and the information contained herein are provided on an 1928 "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS 1929 OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET 1930 ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, 1931 INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE 1932 INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED 1933 WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.