idnits 2.17.1 draft-ietf-pwe3-pw-mpls-mib-03.txt: ** The Abstract section seems to be numbered Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** Looks like you're using RFC 2026 boilerplate. This must be updated to follow RFC 3978/3979, as updated by RFC 4748. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- == No 'Intended status' indicated for this document; assuming Proposed Standard == The page length should not exceed 58 lines per page, but there was 1 longer page, the longest (page 1) being 1310 lines Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack an Abstract section. (A line matching the expected section header was found, but with an unexpected indentation: ' 1 Abstract' ) ** The document seems to lack an Introduction section. (A line matching the expected section header was found, but with an unexpected indentation: ' 2 Introduction 2' ) ** The document seems to lack a Security Considerations section. (A line matching the expected section header was found, but with an unexpected indentation: ' 8 Security Considerations 28' ) ** The document seems to lack an IANA Considerations section. (See Section 2.2 of https://www.ietf.org/id-info/checklist for how to handle the case when there are no actions for IANA.) ** There are 16 instances of lines with control characters in the document. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the RFC 3978 Section 5.4 Copyright Line does not match the current year == Line 243 has weird spacing: '...N |PWin inSeg...' == Line 247 has weird spacing: '...| inSeg outSe...' == Line 313 has weird spacing: '...rolWord notK...' -- 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 section? 'PW-MIB' on line 1120 looks like a reference -- Missing reference section? 'BCP14' on line 1160 looks like a reference -- Missing reference section? 'PWARCH' on line 106 looks like a reference -- Missing reference section? 'PWREQ' on line 1116 looks like a reference -- Missing reference section? 'PWCNTRL' on line 286 looks like a reference -- Missing reference section? 'MPLSArch' on line 1109 looks like a reference -- Missing reference section? 'TRANS' on line 125 looks like a reference -- Missing reference section? 'RFC3410' on line 136 looks like a reference -- Missing reference section? 'RFC2578' on line 1177 looks like a reference -- Missing reference section? 'RFC2579' on line 1182 looks like a reference -- Missing reference section? 'RFC2580' on line 1186 looks like a reference -- Missing reference section? 'CEPMIB' on line 1123 looks like a reference -- Missing reference section? 'PWTC' on line 1131 looks like a reference -- Missing reference section? 'TEMIB' on line 1135 looks like a reference -- Missing reference section? 'LSRMIB' on line 1127 looks like a reference -- Missing reference section? 'RFC2574' on line 1207 looks like a reference -- Missing reference section? 'RFC2575' on line 1219 looks like a reference -- Missing reference section? 'CEP' on line 1113 looks like a reference -- Missing reference section? 'LDPMIB' on line 1139 looks like a reference -- Missing reference section? 'LblStk' on line 1143 looks like a reference -- Missing reference section? 'Assigned' on line 1147 looks like a reference -- Missing reference section? 'IFMIB' on line 1157 looks like a reference -- Missing reference section? 'RFC2571' on line 1163 looks like a reference -- Missing reference section? 'RFC1155' on line 1167 looks like a reference -- Missing reference section? 'RFC1212' on line 1171 looks like a reference -- Missing reference section? 'RFC1215' on line 1174 looks like a reference -- Missing reference section? 'RFC1157' on line 1190 looks like a reference -- Missing reference section? 'RFC1901' on line 1194 looks like a reference -- Missing reference section? 'RFC1906' on line 1198 looks like a reference -- Missing reference section? 'RFC2572' on line 1202 looks like a reference -- Missing reference section? 'RFC1905' on line 1211 looks like a reference -- Missing reference section? 'RFC2573' on line 1216 looks like a reference -- Missing reference section? 'RFC2570' on line 1223 looks like a reference Summary: 7 errors (**), 0 flaws (~~), 6 warnings (==), 35 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Internet Draft David 3 Zelig 4 Expires: April 2004 Corrigent 5 Systems 7 Thomas D. 8 Nadeau 9 Cisco Systems, 10 Inc. 12 Editors 14 October 15 2003 17 Pseudo Wire (PW) over MPLS PSN Management Information Base 19 draft-ietf-pwe3-pw-mpls-mib-03.txt 21 Status of this Memo 23 This document is an Internet-Draft and is in full conformance 24 with all provisions of Section 10 of RFC2026. 26 Internet-Drafts are working documents of the Internet Engineering 27 Task Force (IETF), its areas, and its working groups. Note that 28 other groups may also distribute working documents as Internet- 29 Drafts. 31 Internet-Drafts are draft documents valid for a maximum of six 32 months and may be updated, replaced, or obsoleted by other 33 documents at any time. It is inappropriate to use Internet-Drafts 34 as reference material or to cite them other than as "work in 35 progress." 37 The list of current Internet-Drafts can be accessed at 38 http://www.ietf.org/ietf/1id-abstracts.txt 39 The list of Internet-Draft Shadow Directories can be accessed at 40 http://www.ietf.org/shadow.html. 42 Copyright (C) The Internet Society (2001). All rights reserved. 44 1 Abstract 46 This memo defines an experimental portion of the Management 47 Information Base (MIB) for use with network management protocols in 48 the Internet community. In particular, it describes a MIB module 49 for PW operation over Multi-Protocol Label Switching (MPLS) Label 50 Switch Router (LSR). 52 Table of Contents 54 1 Abstract 1 55 2 Introduction 2 56 3 Terminology 3 57 4 The SNMP Management Framework 3 58 4.1 Object Definitions 4 59 5 Feature Checklist 5 60 6 MIB usage 5 61 6.1 PW-MPLS-MIB usage 5 62 6.2 Example of MIB usage 7 63 7 Object definitions 10 64 8 Security Considerations 28 65 9 References 28 66 10 Author's Addresses 31 67 11 Full Copyright Statement 32 69 2 Introduction 71 This document describes a model for managing pseudo wire services 72 for transmission over different flavors of MPLS tunnels. The 73 general PW MIB module [PW-MIB] defines the parameters global to the 74 PW regardless of underlying PSN and emulated service. Indicating 75 PSN type of MPLS in PW-MIB references this module. 77 This document describes the MIB objects that define pseudo wire 78 association to the MPLS PSN, in a way that is not specific to the 79 carried service. 81 Together, [TEMIB and LSRMIB], describe the modeling of an MPLS 82 Tunnel, and a Tunnel's underlying cross-connects. The defined MIB 83 support MPLS-TE PSN, Non TE MPLS PSN (an outer tunnel created by 84 LDP or manually), and MPLS PW label only (no outer tunnel). 86 Some flavors of MPLS, such as carrying PW in MPLS in IP and MPLS in 87 GRE are not defined here, waiting to the WG documents that will 88 describe the exact MPLS functionality. It still for further study 89 whether this functionality will be treated in this MIB module or in 90 another one specific to IP PSN. 92 PW level protection is for further study. Protection is currently 93 assumed at the outer tunnel level only, on bulk of PWs. Future 94 revision of this document will control the behavior of such 95 protection in more details. 96 Conventions used in this document 98 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 99 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in 100 this document are to be interpreted as described in RFC-2119 101 [BCP14]. 103 3 Terminology 105 This document uses terminology from the document describing the PW 106 architecture [PWARCH], [PWREQ] and [PWCNTRL]. 108 The terms "Outbound" and "Inbound" in this MIB module are based on 109 the common practice in the MPLS standards, i.e. "outbound" are 110 toward the PSN. However, where these terms are used in an object 111 name, the object description clarifies the exact packet direction 112 to prevent confusion with these terms in other documents. 114 "PSN Tunnel" is a general term indicating a virtual connection 115 between the two PWE3 edge devices. Each tunnel may potentially 116 carry multiple PWs inside. In the scope of this document, it is 117 MPLS tunnel. 119 This document uses terminology from the document describing the 120 MPLS architecture [MPLSArch] for MPLS PSN. A Label Switched Path 121 (LSP) is modeled as described in [LSRMIB and TEMIB] via a series of 122 cross-connects through 1 or more Label switch routers (LSR). 124 In MPLS PSN, a PW connection typically uses a PW Label within a 125 Tunnel Label [TRANS]. Multiple pseudo wires each with a unique PW 126 Label can share the same Tunnel. For PW transport over MPLS, the 127 Tunnel Label is known as the "outer" Label, while the PW Label is 128 known as the "inner" Label. An exception to this is with adjacent 129 LSRs or the use of PHP. In this case, there is an option for PWs to 130 connect directly without an outer Label. 132 4 The SNMP Management Framework 134 For a detailed overview of the documents that describe the current 135 Internet-Standard Management Framework, please refer to section 7 of 136 RFC 3410 [RFC3410]. 138 Managed objects are accessed via a virtual information store, termed 139 the Management Information Base or MIB. MIB objects are generally 140 accessed through the Simple Network Management Protocol (SNMP). 141 Objects in the MIB are defined using the mechanisms defined in the 142 Structure of Management Information (SMI). This memo specifies a MIB 143 module that is compliant to the SMIv2, which is described in STD 58, 144 RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580 145 [RFC2580]. 147 4.1 Object Definitions 149 Managed objects are accessed via a virtual information store, 150 termed the Management Information Base or MIB. Objects in the MIB 151 are defined using the subset of Abstract Syntax Notation One 152 (ASN.1) defined in the SMI. In particular, an OBJECT IDENTIFIER, an 153 administratively assigned name, names each object type. The object 154 type together with an object instance serves to uniquely identify a 155 specific instantiation of the object. For human convenience, we 156 often use a textual string, termed the descriptor, to also refer to 157 the object type. 159 5 Feature Checklist 161 The PW MPLS MIB module (PW-MPLS-MIB) is designed to satisfy the 162 following requirements and constraints: 164 - The MIB module supports both manually configured and signaled 165 PWs. 167 - The MIB module supports point-to-point PW connections. 169 - The MIB module enables the use of any emulated service. 171 - The MIB supports MPLS-TE outer tunnel, Non TE MPLS outer tunnel 172 (an outer tunnel signaled by LDP or set-up manually), and no 173 outer tunnel (where the PW label is the only label in the 174 incoming MPLS stack). 176 6 MIB module usage 178 The MIB module structure for defining a PW service is composed from 179 three types of modules. 181 The first type is the PW-MIB module [PW-MIB], which configures 182 general parameters of the PW that are common to all types of 183 emulated services and PSNs. 185 The second type of modules is per PSN module. There is a different 186 module for each type of PSN. This document defines the MIB module 187 for MPLS (PW-MPLS-MIB). 189 The third type of modules is service-specific module, which is 190 emulated signal type dependent. These modules are defined in other 191 documents; see for example [CEPMIB]. 193 [PWTC] defines some of the object types used in this module. 195 6.1 PW-MPLS-MIB usage 197 - The PW table (pwVcTable) in [PW-MIB] is used for all PW types 198 (ATM, FR, Ethernet, SONET, etc.). This table contains high level 199 generic parameters related to the PW creation. A row is created by 200 the operator for each PW service. 202 - If the PSN type in pwVcTable is MPLS, the agent create a row in 203 the MPLS specific parameters table (pwMplsVcTable) in PW-MPLS-MIB, 204 which contain MPLS specific parameters such as EXP bits handling 205 and outer tunnel selection. 207 - A row is created by the agent in the MPLS outbound tunnels table 208 (pwVcMplsOutboundTable), which associates the VC to one or more 209 (in a case of backup tunnels) MPLS tunnels. This table simply 210 associates the VC with the entries at the relevant MPLS MIBs. 211 Additional rows in this table may be created manually, if more 212 than one outer tunnel is required (for example for protection 213 purposes). 215 - The MPLS inbound tunnel table (pwVcMplsInboundTable) associates 216 the VC to the incoming tunnel. This (optional) table can be used 217 for restricting the packet reception for a specific PW from pre- 218 defined tunnels, bringing better security and better miss- 219 configuration error immunity. 221 - The MPLS tunnels mapping tabled (pwMplsTeMappingTable and 222 pwMplsNonTeMappingTable) associate the tunnel and the VC label to 223 the VC index. This table is used for easy lookup process when 224 searching VC information. 226 The relation to the MPLS network is by configuration of the edge 227 LSR only - that is to say, the LSR providing the PW function. Since 228 Tunnels are uni-directional, a pair of tunnels must exist (one for 229 inbound, one for outbound). The following graphic depicts a VC that 230 originates and terminates at LSR-M. It uses LSPs A and B formed by 231 Tunnels Ax and Bx continuing through LSR-N to LSR-P. The 232 concatenations of Tunnels create the LSPs. Note: 'X' denotes a 233 Tunnel's cross-connect. 235 LSP-A 236 <- - - - - - - - - - - - - - - - - - - - - - - - - - - - 238 +---- (edge) LSR-M ---+ +--------- LSR-N ---------+ + LSR-P 239 |---+ | | | | 240 | | Tunnel | | Tunnel | | 241 + | A1 (M<-N) +----+ +----+ A2 (M<-P) +----+ +----+ 242 | | <------| | | |<--------------| | | | 243 <-->| N |PWin inSeg |MPLS| |MPLS| outSeg inSeg |MPLS| |MPLS| 244 N S | | <---X<-----| IF | | IF |<------X<------| IF | | IF | 245 A E | S | | |<-->| | | |<-->| | | 246 T R | | --->X----->| | | |------>X------>| | | | 247 I V | P |PWout outSeg| | | | inSeg outSeg | | | | 248 V I | | ------>| | | |-------------->| | | | 249 E C + | Tunnel +----+ +----+ Tunnel +----+ +----+ 250 E |---+ B1 (M->N) | | B2 (M->P) | | 251 | | | | | 252 +---------------------+ +-------------------------+ +----- 254 - - - - - - - - - - - - - - - - - - - - - - - - - - - -> 255 LSP-B 257 The PW-MPLS-MIB supports three options for MPLS network: 259 - In the MPLS-TE case, Tunnel A1 and B1 are created via the MPLS-TE 260 MIB [TEMIB]. The tunnels are associated to the PW by the (4) 261 indexes that uniquely identify the Tunnel at the TE-MIB. 263 - In the Non TE case, Tunnel A1 and B1 are either manually 264 configured or set up with LDP. The tunnels are associated to the PW 265 by the XC index in the MPLS-LSR-MIB [LSRMIB]. 267 - In the PW label only case, there is no outer Tunnel on top of the 268 PW label. This case is useful in case of adjacent PE (see 269 [PWCNTRL]) only. Note that when LSR-N acts as PHP for the outer 270 tunnel label, there are still entries for the outer tunnel in the 271 relevant MPLS MIB modules. 273 A combination of MPLS-TE outer tunnel(s) and LDP outer tunnel for 274 the same VC is allowed by creating the rows with the same pwVcIndex 275 with different MPLS tunnel indexes types. 277 6.2 Example of MIB module usage 279 In this section we provide an example of using the MIB objects for 280 setting up a PW over MPLS. While this example is not meant to 281 illustrate every permutation of the MIB module, it is intended as 282 an aid to understanding some of the key concepts. It is meant to be 283 read after going through the MIB module itself. 285 In this example a PW service for CEP is configured over an MPLS-TE 286 tunnel. It uses LDP as in [PWCNTRL] for service set-up. 288 In PW-MIB: 290 In pwVcTable: 291 { 292 pwVcIndex 5, 294 pwVcType cep, 295 pwVcOwner maintenanceProtocol, 296 pwVcPsnType mpls, 297 pwVcSetUpPriority 0, 298 pwVcHoldingPriority 0, 299 pwVcInboundMode loose, 301 pwVcPeerAddrType ipv4(2), 302 pwVcPeerAddr 1.4.3.2, -- In this case equal to the 303 -- peer tunnel IP address 304 pwVcID 10, 305 pwVcLocalGroupID 12, 307 pwVcControlWord false, -- Control word not to be sent 308 pwVcLocalIfMtu 0, -- Do not send ifMtu parameter 309 pwVcLocalIfString false, -- Do not signal if string 311 pwVcRemoteGroupID 0xFFFF, -- Will be received by 312 -- maintenance protocol 313 pwVcRemoteControlWord notKnownYet, 314 pwVcRemoteIfMtu 0, 315 pwVcRemoteIfString "", 317 pwVcOutboundVcLabel 0xFFFF, -- Will be received by 318 -- maintenance protocol 319 pwVcInboundVcLabel 0xFFFF, -- Will be set by signaling 321 pwVcName "Example of CEP VC", 322 pwVcDescr "", 323 .. 325 pwVcAdminStatus up, 326 .. 327 } 329 The operator now create a row in pwVcMplsTable based on the 330 VcIndex, that is configured with MPLS specific values: 332 In pwVcMplsTable: 333 { 334 pwVcMplsMplsType mplsTe, 335 pwVcMplsExpBitsMode outerTunnel, 336 pwVcMplsExpBits 0, 337 pwVcMplsTtl 2, 338 pwVcMplsLocalLdpID 1.2.3.4.0.0 -- Global label space 339 pwVcMplsLocalLdpEntityID 0, 340 pwVcMplsPeerLdpID 0, -- Not known yet 341 ... 342 } 344 The operator now associates the VC with an outgoing TE tunnel: 346 In pwVcMplsOutboundTable: 348 { 349 pwVcMplsOutboundIndex 0, -- The first row 350 --for this VCIndex. 351 pwVcMplsOutBoundLsrXcIndex 0, -- MPLS-TE 352 pwVcMplsOutboundTunnelIndex 500, 353 pwVcMplsOutboundTunnelInstance 0, 354 pwVcMplsOutboundTunnelLclLSR 1.2.3.4, -- Always 355 -- the LSR ID of the current node. 356 pwVcMplsOutboundTunnelPeerLSR 1.4.3.2 357 pwVcMplsOutboundIfIndex 0, -- MPLS-TE 359 .. 360 } 362 pwVcMplsInboundTable is not used because loose LDP set-up is used. 364 pwVcMplsTeMappingTable entry will be created by the agent once the 365 outbound table is configured and will enable easy lookup for the 366 VcIndex from knowledge of the outer tunnel indexes. 368 7 369 Object definitions 371 PW-MPLS-MIB DEFINITIONS ::= BEGIN 373 IMPORTS 374 MODULE-IDENTITY, OBJECT-TYPE, 375 experimental, Unsigned32 376 FROM SNMPv2-SMI 378 MODULE-COMPLIANCE, OBJECT-GROUP 379 FROM SNMPv2-CONF 381 RowStatus, StorageType 382 FROM SNMPv2-TC 384 InterfaceIndexOrZero 385 FROM IF-MIB 387 MplsTunnelIndex, MplsTunnelInstanceIndex, 388 MplsLdpIdentifier, MplsLsrIdentifier 389 FROM MPLS-TC-MIB 391 PwVcIndexType 392 FROM PW-TC-MIB 394 pwVcIndex 395 FROM PW-MIB 397 ; 399 pwVcMplsMIB MODULE-IDENTITY 400 LAST-UPDATED "200307291200Z" -- 29 July 2003 12:00:00 EST 401 ORGANIZATION "Pseudo Wire Edge to Edge Emulation (PWE3) Working 402 Group" 403 CONTACT-INFO 404 " 405 David Zelig 406 Postal: Corrigent Systems 407 126, Yigal Alon St. 408 Tel Aviv, ISRAEL 409 Phone: +972-3-6945273 410 E-mail: davidz@corrigent.com 412 Thomas D. Nadeau 413 Postal: Cisco Systems, Inc. 414 250 Apollo Drive 415 Chelmsford, MA 01824 416 Tel: +1-978-497-3051 417 Email: tnadeau@cisco.com 419 Dave Danenberg 420 Postal: Litchfield Communications, Inc. 421 76 Westbury Park Rd 422 Princeton Building East 423 Watertown, CT 06795 424 Tel: +1-860-945-1573 x3180 425 Email: dave_danenberg@litchfieldcomm.com 427 Sharon Mantin 428 Postal: AxONLink (Israel) Ltd 429 9 Bareket St. 430 Petah Tikva 49517, Israel 431 Tel: +972-3-9263972 432 Email: sharon.mantin@axonlink.com 434 The PWE3 Working Group (email distribution pwe3@ietf.org) " 436 DESCRIPTION 437 "This MIB complements the PW-MIB for PW operation over MPLS. 438 " 440 -- Revision history. 441 REVISION 442 "200307291200Z" -- 29 July 2003 12:00:00 EST 443 DESCRIPTION 444 "Draft-ietf-pwe3-pw-mpls-mib-02 version. Changes from 445 previous version: 446 1) Removing inbound table (no srict mode and no knowledge 447 of inbound tunnel). 448 2) Provisoning (i.e. RowCreate) done via mapping tables. 449 Outbound table is now read only for sorted search for 450 pwVcIndex. 451 " 453 REVISION 454 "0206021200Z" -- 02 June 2002 12:00:00 EST 455 DESCRIPTION 456 "Draft-ietf-pwe3-pw-mpls-mib-00 version. Changes from 457 previous version: 458 1) Spliting the mapping table into two tables, one for 459 Non TE application and one for TE application. 460 2) Object types alignment with MPLS MIBs. 461 " 462 REVISION 463 "0201291200Z" -- 29 January 2002 12:00:00 EST 464 DESCRIPTION 465 "Changes from previous version: 466 1) Add LDP entity association. 467 2) Clarify inbound/outbound directions. 468 3) Simplify indexing of outbound and inbound tables 469 and providing get next variables. 470 " 471 REVISION 472 "0107111200Z" -- 7 November 2001 12:00:00 EST 473 DESCRIPTION 474 "Changes from previous version: 475 1) Remove Vc instance from table indexing. 476 2) Update descriptions of indexing and protection. 477 3) Remove the need for MPLS-LSR in case of VC only. 478 4) Change pwVcMplsMplsType to BITS in order to enable 479 multiple types of outer tunnel. 480 5) Add ifindex to outer tunnel tables to support vcOnly 481 option. 482 6) change naming of outbound, inbound and mapping tables to 483 reflect addition of VC only port ifindexes. 484 7) Adapt order of items in mapping table to SNMP convention. 485 " 486 REVISION 487 "0107111200Z" -- July 11 2001 12:00:00 EST 488 DESCRIPTION 489 "draft-zelig-pw-mib-00.txt - initial version" 491 ::= { experimental 888 } -- To be assigned by IANA 493 -- Top-level components of this MIB. 495 -- Traps 496 pwVcMplsNotifications OBJECT IDENTIFIER 497 ::= { pwVcMplsMIB 0 } 498 pwVcMplsNotifyPrefix OBJECT IDENTIFIER 499 ::= { pwVcMplsNotifications 0 } 500 -- Tables, Scalars 501 pwVcMplsObjects OBJECT IDENTIFIER 502 ::= { pwVcMplsMIB 1 } 504 -- Conformance 505 pwVcMplsConformance OBJECT IDENTIFIER 506 ::= { pwVcMplsMIB 2 } 508 -- PW VC MPLS table 510 pwVcMplsTable OBJECT-TYPE 511 SYNTAX SEQUENCE OF PwVcMplsEntry 512 MAX-ACCESS not-accessible 513 STATUS current 514 DESCRIPTION 515 "This table specifies information for VC to be carried over 516 MPLS PSN." 517 ::= { pwVcMplsObjects 1 } 519 pwVcMplsEntry OBJECT-TYPE 520 SYNTAX PwVcMplsEntry 521 MAX-ACCESS not-accessible 522 STATUS current 523 DESCRIPTION 524 "A row in this table represents parameters specific to MPLS 525 PSN for a pseudo wire connection (VC). The row is created 526 automatically by the local agent if the pwVcPsnType is 527 MPLS. It is indexed by pwVcIndex, which uniquely 528 identifying a singular connection. 529 " 531 INDEX { pwVcIndex } 533 ::= { pwVcMplsTable 1 } 535 PwVcMplsEntry ::= SEQUENCE { 536 pwVcMplsMplsType BITS, 537 pwVcMplsExpBitsMode INTEGER, 538 pwVcMplsExpBits Unsigned32, 539 pwVcMplsTtl Unsigned32, 540 pwVcMplsLocalLdpID MplsLdpIdentifier, 541 pwVcMplsLocalLdpEntityID Unsigned32, 542 pwVcMplsPeerLdpID MplsLdpIdentifier, 543 pwVcMplsStorageType StorageType 544 } 546 pwVcMplsMplsType OBJECT-TYPE 547 SYNTAX BITS { 548 mplsTe (0), 549 mplsNonTe (1), 550 vcOnly (2) 551 } 552 MAX-ACCESS read-write 553 STATUS current 554 DESCRIPTION 555 "Set by the operator to indicate the outer tunnel types, if 556 exists. mplsTe is used if the outer tunnel was set-up by 557 MPLS-TE, and mplsNonTe is used the outer tunnel was set up 558 by LDP or manually. Combination of mplsTe and mplsNonTe 559 may exist in case of outer tunnel protection. 560 vcOnly is used if there is no outer tunnel label. vcOnly 561 cannot be combined with mplsNonTe or mplsTe." 562 ::= { pwVcMplsEntry 1 } 564 pwVcMplsExpBitsMode OBJECT-TYPE 565 SYNTAX INTEGER { 566 outerTunnel (1), 567 specifiedValue (2), 568 serviceDependant (3) 569 } 571 MAX-ACCESS read-write 572 STATUS current 573 DESCRIPTION 574 "Set by the operator to indicate the way the VC shim label 575 EXP bits are to be determined. The value of outerTunnel(1) 576 is used where there is an outer tunnel - pwVcMplsMplsType 577 is mplsTe or mplsNonTe. Note that in this case there is no 578 need to mark the VC label with the EXP bits since the VC 579 label is not visible to the intermediate nodes. 580 If there is no outer tunnel, specifiedValue(2) indicate 581 that the value is specified by pwVcMplsExpBits, and 582 serviceDependant(3) indicate that the EXP bits are setup 583 based on a rule specified in the emulated service specific 584 tables, for example when the EXP bits are a function of 585 802.1p marking for Ethernet emulated service." 586 REFERENCE 587 "martini et al, " 588 DEFVAL { outerTunnel } 589 ::= { pwVcMplsEntry 2 } 591 pwVcMplsExpBits OBJECT-TYPE 592 SYNTAX Unsigned32 (0..7) 593 MAX-ACCESS read-write 594 STATUS current 595 DESCRIPTION 596 "Set by the operator to indicate the MPLS EXP bits to be 597 used on the VC shim label if pwVcMplsExpBitsMode is 598 specifiedValue(2), zero otherwise." 599 DEFVAL { 0 } 600 ::= { pwVcMplsEntry 3 } 602 pwVcMplsTtl OBJECT-TYPE 603 SYNTAX Unsigned32 (0..255) 604 MAX-ACCESS read-write 605 STATUS current 606 DESCRIPTION 607 "Set by the operator to indicate the VC TTL bits to be used 608 on the VC shim label." 609 REFERENCE 610 "martini et al, " 611 DEFVAL { 2 } 612 ::= { pwVcMplsEntry 4 } 614 pwVcMplsLocalLdpID OBJECT-TYPE 615 SYNTAX MplsLdpIdentifier 616 MAX-ACCESS read-write 617 STATUS current 618 DESCRIPTION 619 "The local LDP identifier of the LDP entity creating 620 this VC in the local node. As the VC labels are always 621 set from the per platform label space, the last two octets 622 in the LDP ID MUST be always both zeros." 623 REFERENCE 624 ", 625 . 626 " 627 ::= { pwVcMplsEntry 5 } 629 pwVcMplsLocalLdpEntityID OBJECT-TYPE 630 SYNTAX Unsigned32 631 MAX-ACCESS read-write 632 STATUS current 633 DESCRIPTION 634 "The local LDP Entity index of the LDP entity to be used 635 for this VC on the local node. Should be set to all zeros 636 if not used." 637 REFERENCE 638 " 639 " 640 ::= { pwVcMplsEntry 6 } 642 pwVcMplsPeerLdpID OBJECT-TYPE 643 SYNTAX MplsLdpIdentifier 644 MAX-ACCESS read-only 645 STATUS current 646 DESCRIPTION 647 "The peer LDP identifier as identified from the LDP 648 session. Should be zero if not relevant or not known yet." 649 REFERENCE 650 ", 651 . 652 " 653 ::= { pwVcMplsEntry 7 } 655 pwVcMplsStorageType OBJECT-TYPE 656 SYNTAX StorageType 657 MAX-ACCESS read-write 658 STATUS current 659 DESCRIPTION 660 "This variable indicates the storage type for this row." 661 ::= { pwVcMplsEntry 8 } 663 -- End of PW MPLS VC table 665 -- Pseudo Wire VC MPLS Outbound Tunnel table 667 pwVcMplsOutboundTable OBJECT-TYPE 668 SYNTAX SEQUENCE OF PwVcMplsOutboundEntry 669 MAX-ACCESS not-accessible 670 STATUS current 671 DESCRIPTION 672 "This table associates VCs using MPLS PSN with the outbound 673 MPLS tunnels (i.e. toward the PSN) or the physical 674 interface in case of VC only." 675 ::= { pwVcMplsObjects 2 } 677 pwVcMplsOutboundEntry OBJECT-TYPE 678 SYNTAX PwVcMplsOutboundEntry 679 MAX-ACCESS not-accessible 680 STATUS current 681 DESCRIPTION 682 "A row in this table represents a link between PW VC (that 683 require MPLS tunnels) and MPLS tunnel toward the PSN. 684 In the case of VC only, it associate the VC with the 685 interface that shall carry the VC. 686 This table is indexed by the pwVcIndex and an additional 687 index enabling multiple rows for the same VC index. 689 At least one entry is created in this table by the agent 690 for each PW VC that requires MPLS PSN. Note that the first 691 entry for each VC can be indexed by pwVcMplsOutboundIndex 692 equal zero without a need for retrieval of 693 pwVcMplsOutboundIndexNext. 695 This table points to the appropriate MPLS MIB. In the case 696 of MPLS-TE, the 4 variables relevant to the indexing of 697 a TE MPLS tunnel are set as in Srinivasan, et al, . 699 In case of Non-TE MPLS (an outer tunnel label assigned by 700 LDP or manually) the table points to the XC entry in the 701 LSR MIB as in Srinivasan, et al, . 702 In case of VC only (no outer tunnel) the ifIndex of the 703 port to carry the VC is configured. 705 Each VC may have multiple rows in this tables if protection 706 is available at the outer tunnel level, each row may be of 707 different type except for VC only, on which only rows with 708 ifIndex of the port are allowed. 709 " 711 INDEX { pwVcIndex, pwVcMplsOutboundIndex } 713 ::= { pwVcMplsOutboundTable 1 } 715 PwVcMplsOutboundEntry ::= SEQUENCE { 716 pwVcMplsOutboundIndex Unsigned32, 717 pwVcMplsOutboundLsrXcIndex Unsigned32, 718 pwVcMplsOutboundTunnelIndex MplsTunnelIndex, 719 pwVcMplsOutboundTunnelInstance MplsTunnelInstanceIndex, 720 pwVcMplsOutboundTunnelLclLSR MplsLsrIdentifier, 721 pwVcMplsOutboundTunnelPeerLSR MplsLsrIdentifier, 722 pwVcMplsOutboundIfIndex InterfaceIndexOrZero 723 } 725 pwVcMplsOutboundIndex OBJECT-TYPE 726 SYNTAX Unsigned32 (0..4294967295) 727 MAX-ACCESS not-accessible 728 STATUS current 729 DESCRIPTION 730 "Arbitrary index for enabling multiple rows per VC in 731 this table. Next available free index can be retrieved 732 using pwVcMplsOutboundIndexNext. 733 " 734 ::= { pwVcMplsOutboundEntry 1 } 736 pwVcMplsOutboundLsrXcIndex OBJECT-TYPE 737 SYNTAX Unsigned32 738 MAX-ACCESS read-only 739 STATUS current 740 DESCRIPTION 741 "This object will be set by the operator. If the outer 742 label is defined in the MPL-LSR-MIB, i.e. set by LDP 743 or manually, this object points to the XC index 744 of the outer tunnel. Otherwise, it is set to zero." 745 ::= { pwVcMplsOutboundEntry 2 } 747 pwVcMplsOutboundTunnelIndex OBJECT-TYPE 748 SYNTAX MplsTunnelIndex 749 MAX-ACCESS read-only 750 STATUS current 751 DESCRIPTION 752 "Part of set of indexes for outbound tunnel in the case of 753 MPLS-TE outer tunnel, otherwise set to zero." 754 ::= { pwVcMplsOutboundEntry 3 } 756 pwVcMplsOutboundTunnelInstance OBJECT-TYPE 757 SYNTAX MplsTunnelInstanceIndex 758 MAX-ACCESS read-only 759 STATUS current 760 DESCRIPTION 761 "Part of set of indexes for outbound tunnel in the case of 762 MPLS-TE outer tunnel, otherwise set to zero." 763 ::= { pwVcMplsOutboundEntry 4 } 765 pwVcMplsOutboundTunnelLclLSR OBJECT-TYPE 766 SYNTAX MplsLsrIdentifier 767 MAX-ACCESS read-only 768 STATUS current 769 DESCRIPTION 770 "Part of set of indexes for outbound tunnel in the case of 771 MPLS-TE outer tunnel, otherwise set to zero." 772 ::= { pwVcMplsOutboundEntry 5 } 774 pwVcMplsOutboundTunnelPeerLSR OBJECT-TYPE 775 SYNTAX MplsLsrIdentifier 776 MAX-ACCESS read-only 777 STATUS current 778 DESCRIPTION 779 "Part of set of indexes for outbound tunnel in the case of 780 MPLS-TE outer tunnel, otherwise set to zero." 781 ::= { pwVcMplsOutboundEntry 6 } 783 pwVcMplsOutboundIfIndex OBJECT-TYPE 784 SYNTAX InterfaceIndexOrZero 785 MAX-ACCESS read-only 786 STATUS current 787 DESCRIPTION 788 "In case of VC only (no outer tunnel), this object holds 789 the ifIndex of the outbound port, otherwise set to zero." 790 ::= { pwVcMplsOutboundEntry 7 } 792 -- End of Pseudo Wire VC MPLS Outbound Tunnel table 794 -- MPLS to VC Mapping Tables. 796 pwVcMplsNonTeMappingTable OBJECT-TYPE 797 SYNTAX SEQUENCE OF PwVcMplsNonTeMappingEntry 798 MAX-ACCESS not-accessible 799 STATUS current 800 DESCRIPTION 801 "This table maps an outbound Tunnel to a VC in non- 802 TE applications." 803 ::= { pwVcMplsObjects 3 } 805 pwVcMplsNonTeMappingEntry OBJECT-TYPE 806 SYNTAX PwVcMplsNonTeMappingEntry 807 MAX-ACCESS not-accessible 808 STATUS current 809 DESCRIPTION 810 "A row in this table represents the association 811 between the PW VC and it's non TE MPLS outer Tunnel 812 it's physical interface if there is no outer tunnel 813 (VC only). 815 If the operator (or the agent, based on local policy) 816 want to associate the PW with a non TE tunnel, it 817 create 818 a row in this table with the tunnel parameters and the 819 relevant pwVcIndex. 821 An application can use this table to quickly retrieve the 822 PW carried over specific non-TE MPLS outer tunnel or 823 physical interface. 825 The table in indexed by the XC index for MPLS Non-TE 826 tunnel, or ifIndex of the port in VC only case, the 827 direction of the VC in the specific entry and the VCIndex. 828 " 830 INDEX { pwVcMplsNonTeMappingXcTunnelIndex, 831 pwVcMplsNonTeMappingIfIndex, 832 pwVcMplsNonTeMappingVcIndex } 834 ::= { pwVcMplsNonTeMappingTable 1 } 836 PwVcMplsNonTeMappingEntry ::= SEQUENCE { 837 pwVcMplsNonTeMappingXcTunnelIndex Unsigned32, 838 pwVcMplsNonTeMappingIfIndex 839 InterfaceIndexOrZero, 840 pwVcMplsNonTeMappingVcIndex PwVcIndexType, 841 pwVcMplsNonTeMappingRowStatus RowStatus, 842 pwVcMplsNonTeMappingStorageType StorageType 843 } 845 pwVcMplsNonTeMappingXcTunnelIndex OBJECT-TYPE 846 SYNTAX Unsigned32 (0..4294967295) 847 MAX-ACCESS not-accessible 848 STATUS current 849 DESCRIPTION 850 "Index for the conceptual XC row identifying Tunnel to VC 851 mappings when the outer tunnel is created by the MPLS-LSR- 852 MIB, Zero otherwise." 853 ::= { pwVcMplsNonTeMappingEntry 1 } 855 pwVcMplsNonTeMappingIfIndex OBJECT-TYPE 856 SYNTAX InterfaceIndexOrZero 857 MAX-ACCESS not-accessible 858 STATUS current 859 DESCRIPTION 860 "In cases where there is only VC label without outer tunnel, 861 this item indicate the ifIndex of the interface this VC 862 would use. In all other cases, this object shgould be set to 863 zero." 864 ::= { pwVcMplsNonTeMappingEntry 2 } 866 pwVcMplsNonTeMappingVcIndex OBJECT-TYPE 867 SYNTAX PwVcIndexType 868 MAX-ACCESS read-create 869 STATUS current 870 DESCRIPTION 871 "The value that represent the VC in the pwVcTable." 872 ::= { pwVcMplsNonTeMappingEntry 3 } 874 pwVcMplsNonTeMappingRowStatus OBJECT-TYPE 875 SYNTAX RowStatus 876 MAX-ACCESS read-create 877 STATUS current 878 DESCRIPTION 879 "For creating, modifying, and deleting this row." 880 ::= { pwVcMplsNonTeMappingEntry 4 } 882 pwVcMplsNonTeMappingStorageType OBJECT-TYPE 883 SYNTAX StorageType 884 MAX-ACCESS read-create 885 STATUS current 886 DESCRIPTION 887 "This variable indicates the storage type for this object." 888 ::= { pwVcMplsNonTeMappingEntry 5 } 890 -- End of Non-TE MPLS Tunnel to VC Mapping Table 892 pwVcMplsTeMappingTable OBJECT-TYPE 893 SYNTAX SEQUENCE OF PwVcMplsTeMappingEntry 894 MAX-ACCESS not-accessible 895 STATUS current 896 DESCRIPTION 897 "This table maps an inbound/outbound Tunnel to a VC in 898 MPLS-TE applications." 899 ::= { pwVcMplsObjects 4 } 901 pwVcMplsTeMappingEntry OBJECT-TYPE 902 SYNTAX PwVcMplsTeMappingEntry 903 MAX-ACCESS not-accessible 904 STATUS current 905 DESCRIPTION 906 "A row in this table represents the association 907 between a PW VC and it's MPLS-TE outer Tunnel. 909 If the operator (or the agent, based on local policy) 910 want to associate the PW with a non TE tunnel, it 911 create 912 a row in this table with the tunnel parameters and the 913 relevant pwVcIndex. 915 An application can use this table to quickly retrieve the 916 PW carried over specific TE MPLS outer tunnel. 918 The table in indexed by the 4 indexes of a TE tunnel, 919 the direction of the VC specific entry and the VcIndex. 920 " 922 INDEX { pwVcMplsTeMappingTunnelIndex, 923 pwVcMplsTeMappingTunnelInstance, 924 pwVcMplsTeMappingTunnelPeerLsrID, 925 pwVcMplsTeMappingTunnelLocalLsrID, 926 pwVcMplsTeMappingVcIndex } 928 ::= { pwVcMplsTeMappingTable 1 } 930 PwVcMplsTeMappingEntry ::= SEQUENCE { 931 pwVcMplsTeMappingTunnelIndex MplsTunnelIndex, 932 pwVcMplsTeMappingTunnelInstance MplsTunnelInstanceIndex, 933 pwVcMplsTeMappingTunnelPeerLsrID MplsLsrIdentifier, 934 pwVcMplsTeMappingTunnelLocalLsrID MplsLsrIdentifier, 935 pwVcMplsTeMappingVcIndex PwVcIndexType, 936 pwVcMplsTeMappingRowStatus RowStatus, 937 pwVcMplsTeMappingStorageType StorageType 939 } 941 pwVcMplsTeMappingTunnelIndex OBJECT-TYPE 942 SYNTAX MplsTunnelIndex 943 MAX-ACCESS not-accessible 944 STATUS current 945 DESCRIPTION 946 "Primary index for the conceptual row identifying the 947 MPLS-TE tunnel." 948 ::= { pwVcMplsTeMappingEntry 1 } 950 pwVcMplsTeMappingTunnelInstance OBJECT-TYPE 951 SYNTAX MplsTunnelInstanceIndex 952 MAX-ACCESS not-accessible 953 STATUS current 954 DESCRIPTION 955 "Identifies an instance of the MPLS-TE tunnel." 956 ::= { pwVcMplsTeMappingEntry 2 } 958 pwVcMplsTeMappingTunnelPeerLsrID OBJECT-TYPE 959 SYNTAX MplsLsrIdentifier 960 MAX-ACCESS not-accessible 961 STATUS current 962 DESCRIPTION 963 "Identifies an Peer LSR when the outer tunnel is MPLS-TE 964 based." 965 ::= { pwVcMplsTeMappingEntry 3 } 967 pwVcMplsTeMappingTunnelLocalLsrID OBJECT-TYPE 968 SYNTAX MplsLsrIdentifier 969 MAX-ACCESS not-accessible 970 STATUS current 971 DESCRIPTION 972 "Identifies the local LSR." 973 ::= { pwVcMplsTeMappingEntry 4 } 975 pwVcMplsTeMappingVcIndex OBJECT-TYPE 976 SYNTAX PwVcIndexType 977 MAX-ACCESS read-create 978 STATUS current 979 DESCRIPTION 980 "The value that represent the VC in the pwVcTable." 981 ::= { pwVcMplsTeMappingEntry 5 } 983 pwVcMplsTeMappingRowStatus OBJECT-TYPE 984 SYNTAX RowStatus 985 MAX-ACCESS read-create 986 STATUS current 987 DESCRIPTION 988 "For creating, modifying, and deleting this row." 989 ::= { pwVcMplsTeMappingEntry 6 } 991 pwVcMplsTeMappingStorageType OBJECT-TYPE 992 SYNTAX StorageType 993 MAX-ACCESS read-create 994 STATUS current 995 DESCRIPTION 996 "This variable indicates the storage type for this object." 997 ::= { pwVcMplsTeMappingEntry 7 } 999 -- End of TE MPLS Tunnel to VC Mapping Table 1001 -- conformance information 1003 -- Note: Conformance at the object access and values level is 1004 -- still FFS, therefore current conformance is defined at the 1005 -- object existence level only. 1007 pwVcMplsGroups OBJECT IDENTIFIER ::= { pwVcMplsConformance 1 } 1008 pwVcMplsCompliances OBJECT IDENTIFIER ::= { pwVcMplsConformance 2 } 1010 pwMplsModuleCompliance MODULE-COMPLIANCE 1011 STATUS current 1012 DESCRIPTION 1013 "The compliance statement for agent that support PW 1014 over MPLS PSN operation." 1016 MODULE -- this module 1017 MANDATORY-GROUPS { pwVcMplsGroup, 1018 pwVcMplsOutboundGroup, 1019 pwVcMplsMappingGroup 1020 } 1022 ::= { pwVcMplsCompliances 1 } 1024 -- Units of conformance. 1026 pwVcMplsGroup OBJECT-GROUP 1027 OBJECTS { 1028 pwVcMplsMplsType, 1029 pwVcMplsExpBitsMode, 1030 pwVcMplsExpBits, 1031 pwVcMplsTtl, 1032 pwVcMplsLocalLdpID, 1033 pwVcMplsLocalLdpEntityID, 1034 pwVcMplsPeerLdpID, 1035 pwVcMplsStorageType 1036 } 1038 STATUS current 1039 DESCRIPTION 1040 "Collection of objects needed for PW VC 1041 over MPLS PSN configuration." 1042 ::= { pwVcMplsGroups 1 } 1044 pwVcMplsOutboundGroup OBJECT-GROUP 1045 OBJECTS { 1046 pwVcMplsOutboundLsrXcIndex, 1047 pwVcMplsOutboundTunnelIndex, 1048 pwVcMplsOutboundTunnelInstance, 1049 pwVcMplsOutboundTunnelLclLSR, 1050 pwVcMplsOutboundTunnelPeerLSR, 1051 pwVcMplsOutboundIfIndex 1052 } 1054 STATUS current 1055 DESCRIPTION 1056 "Collection of objects needed for outbound association of 1057 VC and MPLS tunnel." 1058 ::= { pwVcMplsGroups 2 } 1060 pwVcMplsMappingGroup OBJECT-GROUP 1061 OBJECTS { 1062 pwVcMplsNonTeMappingVcIndex, 1063 pwVcMplsNonTeMappingRowStatus, 1064 pwVcMplsNonTeMappingStorageType, 1065 pwVcMplsTeMappingVcIndex, 1066 pwVcMplsTeMappingRowStatus, 1067 pwVcMplsTeMappingStorageType 1068 } 1070 STATUS current 1071 DESCRIPTION 1072 "Collection of objects used for mapping of tunnels and VC 1073 labels to VC index." 1074 ::= { pwVcMplsGroups 4 } 1076 END -- of PW-MPLS-MIB 1078 8 Security Considerations 1080 There are a number of management objects defined in this MIB that 1081 have a MAX-ACCESS clause of read-write and/or read-create. Such 1082 objects may be considered sensitive or vulnerable in some network 1083 environments. The support for SET operations in a non-secure 1084 environment without proper protection can have a negative effect on 1085 network operations. 1087 SNMPv1 by itself is not a secure environment. Even if the network 1088 itself is secure (for example by using IPSec), even then, there is 1089 no control as to who on the secure network is allowed to access and 1090 GET/SET (read/change/create/delete) the objects in this MIB. 1092 It is recommended that the implementers consider the security 1093 features as provided by the SNMPv3 framework. Specifically, the 1094 use of the User-based Security Model RFC 2574 [RFC2574] and the 1095 View-based Access Control Model RFC 2575 [RFC2575] is recommended. 1097 It is then a customer/user responsibility to ensure that the SNMP 1098 entity giving access to an instance of this MIB, is properly 1099 configured to give access to the objects only to those principals 1100 (users) that have legitimate rights to indeed GET or SET 1101 (change/create/delete) them. 1103 The use of strict inbound VC lookup the security problems related 1104 to a global VC space in a node is greatly reduced, by limiting the 1105 accepted packets to a small set of controlled tunnels. 1107 9 References 1109 [MPLSArch] Rosen, E., Viswanathan, A., and R. Callon, 1110 "Multiprotocol Label Switching Architecture", RFC 3031, 1111 Jan 2001. 1113 [CEP] Malis, A., et al, "SONET/SDH Circuit Emulation over 1114 Packet (CEP)", work-in-progress. 1116 [PWREQ] Xiao et al, "Requirements for Pseudo Wire Emulation 1117 Edge-to-Edge (PWE3)", , November 2001. 1120 [PW-MIB] Zelig et al, "Pseudo Wire (PW) Management Information 1121 Base", , June 2002. 1123 [CEPMIB] Danenberg et al, "SONET/SDH Circuit Emulation Service 1124 Over MPLS (CEP) Management Information Base Using 1125 SMIv2", work-in-progress. 1127 [LSRMIB] Srinivasan, C., Viswanathan, A., and Nadeau, T. "MPLS 1128 Label Switch Router Management Information Base Using 1129 SMIv2", work-in-progress. 1131 [PWTC] Nadeau, T., et al, "Definitions for Textual Conventions 1132 and OBJECT-IDENTITIES for Pseudo-Wires Management", 1133 work-in-progress. 1135 [TEMIB] Srinivasan, C., Viswanathan, A., and Nadeau, T. "MPLS 1136 Traffic Engineering Management Information Base Using 1137 SMIv2", work-in-progress. 1139 [LDPMIB] J. Cucchiara et al, "Definitions of Managed Objects for 1140 the Multiprotocol Label Switching, Label Distribution 1141 Protocol (LDP), work-in-progress. 1143 [LblStk] Rosen, E., Rekhter, Y., Tappan, D., Farinacci, D., 1144 Federokow, G., Li, T., and A. Conta, "MPLS Label Stack 1145 Encoding", RFC 3032, January 2001. 1147 [Assigned] Reynolds, J., and J. Postel, "Assigned Numbers", RFC 1148 1700, October 1994. See also: http://www.isi.edu/in- 1149 notes/iana/assignments/smi-numbers 1151 [IANAFamily]Internet Assigned Numbers Authority (IANA), ADDRESS 1152 FAMILY NUMBERS,(http://www.isi.edu/in- 1153 notes/iana/assignements/address-family-numbers), for 1154 MIB see: 1155 ftp://ftp.isi.edu/mib/ianaaddressfamilynumbers.mib 1157 [IFMIB] McCloghrie, K., and F. Kastenholtz, "The Interfaces 1158 Group MIB using SMIv2", RFC 2863, January 2000. 1160 [BCP14] Bradner, S., "Key words for use in RFCs to Indicate 1161 requirement Levels", BCP 14, RFC 2119, March 1997. 1163 [RFC2571] Harrington, D., Presuhn, R., and B. Wijnen, "An 1164 Architecture for Describing SNMP Management 1165 Frameworks", RFC 2571, April 1999. 1167 [RFC1155] Rose, M., and K. McCloghrie, "Structure and 1168 Identification of Management Information for TCP/IP- 1169 based Internets", STD 16, RFC 1155, May 1990. 1171 [RFC1212] Rose, M., and K. McCloghrie, "Concise MIB Definitions", 1172 STD 16, RFC 1212, March 1991. 1174 [RFC1215] M. Rose, "A Convention for Defining Traps for use with 1175 the SNMP", RFC 1215, March 1991. 1177 [RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, 1178 J, Rose, M., and S. Waldbusser, "Structure of 1179 Management Information Version 2 (SMIv2)", STD 58, RFC 1180 2578, April 1999. 1182 [RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, 1183 J, Rose, M., and S. Waldbusser, "Textual Conventions 1184 for SMIv2", STD 58, RFC 2579, April 1999. 1186 [RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, 1187 J, Rose, M., and S. Waldbusser, "Conformance Statements 1188 for SMIv2", STD 58, RFC 2580, April 1999. 1190 [RFC1157] Case, J., Fedor, M., Schoffstall, M., and J. Davin, 1191 "Simple Network Management Protocol", STD 15, RFC 1157, 1192 May 1990. 1194 [RFC1901] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 1195 "Introduction to Community-based SNMPv2", RFC 1901, 1196 January 1996. 1198 [RFC1906] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 1199 "Transport Mappings for Version 2 of the Simple Network 1200 Management Protocol (SNMPv2)", RFC 1906, January 1996. 1202 [RFC2572] Case, J., Harrington D., Presuhn R., and B. Wijnen, 1203 "Message Processing and Dispatching for the Simple 1204 Network Management Protocol (SNMP)", RFC 2572, April 1205 1999. 1207 [RFC2574] Blumenthal, U., and B. Wijnen, "User-based Security 1208 Model (USM) for version 3 of the Simple Network 1209 Management Protocol (SNMPv3)", RFC 2574, April 1999. 1211 [RFC1905] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 1212 "Protocol Operations for Version 2 of the Simple 1213 Network Management Protocol (SNMPv2)", RFC 1905, 1214 January 1996. 1216 [RFC2573] Levi, D., Meyer, P., and B. Stewart, "SNMPv3 1217 Applications", RFC 2573, April 1999. 1219 [RFC2575] Wijnen, B., Presuhn, R., and K. McCloghrie, "View-based 1220 Access Control Model (VACM) for the Simple Network 1221 Management Protocol (SNMP)", RFC 2575, April 1999. 1223 [RFC2570] Case, J., Mundy, R., Partain, D., and B. Stewart, 1224 "Introduction to Version 3 of the Internet-standard 1225 Network Management Framework", RFC 2570, April 1999. 1227 10 Author's Addresses 1229 David Zelig 1230 Corrigent Systems 1231 126, Yigal Alon st. 1232 Tel Aviv, ISRAEL 1233 Phone: +972-3-6945273 1234 Email: davidz@corrigent.com 1236 Thomas D. Nadeau 1237 Cisco Systems, Inc. 1238 250 Apollo Drive 1239 Chelmsford, MA 01824 1240 Email: tnadeau@cisco.com 1242 Dave Danenberg 1243 Litchfield Communications, Inc. 1244 76 Westbury Park Rd 1245 Princeton Building East 1246 Watertown, CT 06795 1247 Email: dave_danenberg@litchfieldcomm.com 1249 Andrew G. Malis 1250 Tellabs, Inc. 1251 2730 Orchard Parkway 1252 San Jose, CA 95134 1253 Email: Andy.Malis@tellabs.com 1255 Sharon Mantin 1256 AxONLink (Israel) Ltd 1257 9 Bareket St. 1258 Petah Tikva 49517, Israel 1259 Phone: +972-3-9263972 1260 Email: sharon.mantin@axonlink.com 1262 11 Full Copyright Statement 1264 Copyright (C) The Internet Society (2000). All Rights Reserved. 1266 This document and translations of it may be copied and furnished to 1267 others, and derivative works that comment on or otherwise explain 1268 it or assist in its implementation may be prepared, copied, 1269 published and distributed, in whole or in part, without restriction 1270 of any kind, provided that the above copyright notice and this 1271 paragraph are included on all such copies and derivative works. 1272 However, this document itself may not be modified in any way, such 1273 as by removing the copyright notice or references to the Internet 1274 Society or other Internet organizations, except as needed for the 1275 purpose of developing Internet standards in which case the 1276 procedures for copyrights defined in the Internet Standards process 1277 must be followed, or as required to translate it into languages 1278 other than English. 1280 The limited permissions granted above are perpetual and will not be 1281 revoked by the Internet Society or its successors or assigns. This 1282 document and the information contained herein is provided on an "AS 1283 IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING 1284 TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING 1285 BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION 1286 HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF 1287 MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.