idnits 2.17.1 draft-zelig-pw-enet-mib-01.txt: ** The Abstract section seems to be numbered -(204): Line appears to be too long, but this could be caused by non-ascii characters in UTF-8 encoding -(907): Line appears to be too long, but this could be caused by non-ascii characters in UTF-8 encoding Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** Looks like you're using RFC 2026 boilerplate. This must be updated to follow RFC 3978/3979, as updated by RFC 4748. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- == There are 6 instances of lines with non-ascii characters in the document. == No 'Intended status' indicated for this document; assuming Proposed Standard == The page length should not exceed 58 lines per page, but there was 18 longer pages, the longest (page 3) being 59 lines == It seems as if not all pages are separated by form feeds - found 0 form feeds but 21 pages Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** 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.) ** The document seems to lack separate sections for Informative/Normative References. All references will be assumed normative when checking for downward references. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the RFC 3978 Section 5.4 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.) -- The document date (August 2002) is 7925 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) == Missing Reference: 'PW-ENET' is mentioned on line 91, but not defined == Missing Reference: 'PW-MIB' is mentioned on line 165, but not defined == Missing Reference: 'LDPMIB' is mentioned on line 219, but not defined == Missing Reference: 'TEMIB' is mentioned on line 219, but not defined == Missing Reference: 'PWLAYRES' is mentioned on line 262, but not defined == Unused Reference: 'ENETPW' is defined on line 880, but no explicit reference was found in the text == Unused Reference: 'PWREQ' is defined on line 888, but no explicit reference was found in the text == Unused Reference: 'PWLAYER' is defined on line 892, but no explicit reference was found in the text == Unused Reference: 'IANAFamily' is defined on line 914, but no explicit reference was found in the text == Unused Reference: 'IFMIB' is defined on line 919, but no explicit reference was found in the text -- Possible downref: Non-RFC (?) normative reference: ref. 'ENETPW' -- Possible downref: Non-RFC (?) normative reference: ref. 'FRMWK' -- Possible downref: Non-RFC (?) normative reference: ref. 'PWREQ' -- Possible downref: Non-RFC (?) normative reference: ref. 'PWLAYER' -- Possible downref: Non-RFC (?) normative reference: ref. 'VPLS' -- Possible downref: Non-RFC (?) normative reference: ref. 'PWTC' -- Possible downref: Non-RFC (?) normative reference: ref. 'PWMIB' -- Possible downref: Non-RFC (?) normative reference: ref. 'PWMPLSMIB' -- Possible downref: Non-RFC (?) normative reference: ref. 'ENETLIKE' -- Possible downref: Non-RFC (?) normative reference: ref. 'IANAFamily' ** Obsolete normative reference: RFC 2571 (Obsoleted by RFC 3411) ** Downref: Normative reference to an Informational RFC: RFC 1215 ** Downref: Normative reference to an Historic RFC: RFC 1157 ** Downref: Normative reference to an Historic RFC: RFC 1901 ** Obsolete normative reference: RFC 1906 (Obsoleted by RFC 3417) ** Obsolete normative reference: RFC 2572 (Obsoleted by RFC 3412) ** Obsolete normative reference: RFC 2574 (Obsoleted by RFC 3414) ** Obsolete normative reference: RFC 1905 (Obsoleted by RFC 3416) ** Obsolete normative reference: RFC 2573 (Obsoleted by RFC 3413) ** Obsolete normative reference: RFC 2575 (Obsoleted by RFC 3415) ** Obsolete normative reference: RFC 2570 (Obsoleted by RFC 3410) Summary: 15 errors (**), 0 flaws (~~), 15 warnings (==), 12 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Internet Draft David Zelig 3 Expires: February 2003 Corrigent Systems 5 Thomas D. Nadeau 6 Cisco Systems, Inc. 8 August 2002 10 Ethernet Pseudo Wire (PW) Management Information Base 12 draft-zelig-pw-enet-mib-01.txt 14 Status of this Memo 16 This document is an Internet-Draft and is in full conformance with 17 all provisions of Section 10 of RFC2026. 19 Internet-Drafts are working documents of the Internet Engineering 20 Task Force (IETF), its areas, and its working groups. Note that 21 other groups may also distribute working documents as Internet- 22 Drafts. 24 Internet-Drafts are draft documents valid for a maximum of six 25 months and may be updated, replaced, or obsoleted by other documents 26 at any time. It is inappropriate to use Internet-Drafts as 27 reference material or to cite them other than as "work in progress." 29 The list of current Internet-Drafts can be accessed at 30 http://www.ietf.org/ietf/1id-abstracts.txt 31 The list of Internet-Draft Shadow Directories can be accessed at 32 http://www.ietf.org/shadow.html. 34 Copyright (C) The Internet Society (2001). All rights reserved. 36 1 Abstract 38 This memo defines an experimental portion of the Management 39 Information Base (MIB) for use with network management protocols in 40 the Internet community. In particular, it describes managed objects 41 for modeling of Ethernet Pseudo Wire (PW) services. 43 Ethernet Pseudo Wire (PW) August 2002 44 Management Information Base 46 Table of Contents 48 1 Abstract.......................................................1 49 2 Introduction...................................................2 50 3 Terminology....................................................3 51 4 The SNMP Management Framework..................................3 52 4.1 Object Definitions...........................................4 53 5 Feature Checklist..............................................4 54 6 PW-MIB usage...................................................4 55 6.1 PW-ENET-MIB usage............................................5 56 6.2 PW-ENET management model.....................................6 57 6.3 Example of MIB usage.........................................7 58 7 Object definitions.............................................7 59 8 Security Considerations.......................................17 60 9 References....................................................18 61 10 Author's Addresses..........................................20 62 11 Full Copyright Statement....................................20 64 2 Introduction 66 This document describes a model for managing Ethernet pseudo wire 67 services for transmission over a packet Switched Network (PSN). This 68 MIB module is generic and common to all types of PSNs supported in 69 the PWE3 Framework [FRMWK], which describes the transport and 70 encapsulation of L1 and L2 services over supported PSN types. 72 In particular, the MIB module associates a whole port or specific 73 VLANs on top of a physical Ethernet port or a virtual Ethernet 74 interface (for VPLS service) to a point-to-point VC. It is 75 complementary to the [PWMIB], which is used to manage the generic PW 76 parameters common to all service, including all supported PSN types. 78 Conventions used in this document 80 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 81 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in 82 this document are to be interpreted as described in RFC-2119 83 [BCP14]. 85 Ethernet Pseudo Wire (PW) August 2002 86 Management Information Base 88 3 Terminology 90 This document uses terminology from the document describing the PW 91 framework [FRMWK] and from [PW-ENET]. 93 4 The SNMP Management Framework 95 The SNMP Management Framework presently consists of five major 96 components: 98 o An overall architecture, described in RFC 2571 [RFC2571]. 100 o Mechanisms for describing and naming objects and events for the 101 purpose of management. The first version of this Structure of 102 Management Information (SMI) is called SMIv1 and described in STD 103 16, RFC 1155 [RFC1155], STD 16, RFC 1212 [RFC1212] and RFC 1215 104 [RFC1215]. The second version, called SMIv2, is described in STD 105 58, RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 106 2580 [RFC2580]. 108 o Message protocols for transferring management information. The 109 first version of the SNMP message protocol is called SNMPv1 and 110 described in STD 15, RFC 1157 [RFC1157]. A second version of the 111 SNMP message protocol, which is not an Internet standards track 112 protocol, is called SNMPv2c and described in RFC 1901 [RFC1901] 113 and RFC 1906 [RFC1906]. The third version of the message protocol 114 is called SNMPv3 and described in RFC 1906 [RFC1906], RFC 2572 115 [RFC2572] and RFC 2574 [RFC2574]. 117 o Protocol operations for accessing management information. The 118 first set of protocol operations and associated PDU formats is 119 described in STD 15, RFC 1157 [RFC1157]. A second set of protocol 120 operations and associated PDU formats is described in RFC 1905 121 [RFC1905]. 123 o A set of fundamental applications described in RFC 2573 [RFC2573] 124 and the view-based access control mechanism described in RFC 2575 125 [RFC2575]. 127 A more detailed introduction to the current SNMP Management 128 Framework can be found in RFC 2570 [RFC2570]. 130 Managed objects are accessed via a virtual information store, termed 131 the Management Information Base or MIB. Objects in the MIB are 132 defined using the mechanisms defined in the SMI. 134 This memo specifies a MIB module that is compliant to the SMIv2. A 135 MIB conforming to the SMIv1 can be produced through the appropriate 136 translations. The resulting translated MIB must be semantically 137 equivalent, except where objects or events are omitted because no 139 Ethernet Pseudo Wire (PW) August 2002 140 Management Information Base 142 translation is possible (use of Counter64). Some machine-readable 143 information in SMIv2 will be converted into textual descriptions in 144 SMIv1 during the translation process. However, this loss of 145 machine-readable information is not considered to change the 146 semantics of the MIB. 148 4.1 Object Definitions 150 Managed objects are accessed via a virtual information store, termed 151 the Management Information Base or MIB. Objects in the MIB are 152 defined using the subset of Abstract Syntax Notation One (ASN.1) 153 defined in the SMI. In particular, an OBJECT IDENTIFIER, an 154 administratively assigned name, names each object type. The object 155 type together with an object instance serves to uniquely identify a 156 specific instantiation of the object. For human convenience, we 157 often use a textual string, termed the descriptor, to also refer to 158 the object type. 160 5 Feature Checklist 162 The PW Ethernet MIB (PW-ENET-MIB) is designed to satisfy the 163 following requirements and constraints: 165 - The MIB is designed to be work with the PW-MIB [PW-MIB]. 167 - The MIB is independent of the PSN type. 169 - The MIB supports various options for selecting Ethernet packets 170 into the PW. These include port-based PW, VLAN-based PW, VLAN 171 range PW, VLAN-change and adding or removing VLAN fields between 172 the port to be emulated and the VC. 174 - In the case of an MPLS PSN, the MIB support the use of multiple 175 VCs to carry the same Ethernet service. These VCs can be used to 176 support L-LSPs or single COS E-LSPs capable PSN, when mapping of 177 the Ethernet PRI bits to the PSN COS is required. 179 - The MIB enables both point-to-point Ethernet services and VPLS 180 services such as VPLS [VPLS]. 182 - The MIB allow modeling of the PW as an Ethernet virtual port to 183 be managed via existing Ethernet MIBs like Etherlike-MIB 184 [ENETLIKE]. 186 6 PW-MIB usage 188 The MIB structure for defining a PW service is composed of three 189 layers of MIB modules functioning together. This general model is 190 defined in the PWE3 Framework [FRMWK]. The layering model is 192 Ethernet Pseudo Wire (PW) August 2002 193 Management Information Base 195 intended to sufficiently isolate PW services from the underlying PSN 196 layer that carries the emulated service. This is done at the same 197 time as providing a standard means for connecting any supported 198 services to any supported PSNs. 200 The first layer known as the service layer contains service-specific 201 modules such as the one defined in this document. These modules 202 define service-specific management objects that interface or 203 collaborate with existing MIB modules for the native version of the 204 service. The service-specific module �glues� the standard module to 205 the PWE MIB framework. 207 The next layer of the PWE MIB framework is comprised of the PW-MIB 208 module [PWMIB]. This module is used to configure general parameters 209 of PW VCs that are common to all types of emulated services and 210 PSNs. This layer is connected to the service-specific layer above, 211 and the PSN layer below. 213 The PSN layer provides PSN-specific modules for each type of PSN. 214 These modules associate the VC with one or more "tunnels" that carry 215 the service over the PSN. These modules are defined in other 216 documents. This module is used to �glue� the PW service to the 217 underlying PSN-specific MIB modules. In the case of MPLS, for 218 example, the PW-MPLS MIB [PWMPLSMIB] is used to connect the PW 219 service to either the MPLS-LDP [LDPMIB] or MPLS-TE [TEMIB] MIBs. 221 [PWTC] defines some of the object types used in these modules. 223 The Etherlike-MIB [ENETLIKE] does not support virtual Ethernet port, 224 however it is sometimes desired to manage the PW VC as an Ethernet 225 port via the Etherlike-MIB. The MIB support an option to recognize 226 the VC as an ifIndex, enabling standard use of the Etherlike-MIB to 227 manage the VC. 229 6.1 PW-ENET-MIB usage 231 - The VC table (pwVcTable) is used for all VC types (ATM, FR, 232 Ethernet, SONET, etc.). This table contains high level generic 233 parameters related to the VC creation. A row is created by the 234 operator for each PW service. 236 - Based on the PSN type defined for the VC, rows are created in PSN 237 specific module (for example [PWMPLSMIB]) and associated to the 238 VC table by a common VC index. 240 - If the VC type is Ethernet, EthernetVLAN or EthernetVPLS a row is 241 created in pwVcEnetTable. 243 - When using a MPLS PSN, it may be required to separate the same 244 Ethernet services to multiple PW in order to support multiple COS 246 Ethernet Pseudo Wire (PW) August 2002 247 Management Information Base 249 on the same service. In this case, multiple VCs, each with the 250 appropriate COS will be created to the same destination, and 251 classification will be based also on the Ethernet PRI bits 252 marking. The MIB allow any combinations of multiple PRI setting 253 to PSN COS mapping (The exact PSN marking (EXP bits, DSCP etc.) 254 is out of scope of this MIB). In these cases, pwVcEnetTable will 255 hold multiple rows with the same Ethernet port and VLAN mapping, 256 each VC will need to be created separately by the signaling 257 process. 259 6.2 PW-ENET management model 261 The management model for the Ethernet PW VC is shown in figure 1, 262 and is based on the PW proposed layering [PWLAYRES]. 264 +--------------------------------------+ 265 | PE Device | 266 +--------------------------------------+ 267 Single | | | 268 PWES | | Single | PW Instance 269 <------>o Forwarder + PW IWF X<=========> 270 | | Instance | 271 +--------------------------------------+ 272 ^ 273 | 274 May be modeled as 275 ifIndex 277 Notation: 278 o A physical CE-bound PE port 279 + A PW IWF instance interface to the forwarder. 280 X A PE PSN-bound port. 282 Figure 1: A simple point-to-point service 284 In the typical point-to-point service, the object 285 pwVcEnetPortIfIndex associate the physical CE-bound PE port ('o') to 286 the PW (it is allowed to have multiple PWs associated to the same 287 physical port). The operations of the forwarder are also managed by 288 this MIB. 290 In some models it is convenient to model the forwarder virtual 291 interface to a PW IWF instance ('O') as an ifIndex - The object 292 pwVcEnetIfIndex indicate this relation in this case, and the PW 293 instance is managed as virtual Ethernet interface in the PE. 295 Ethernet Pseudo Wire (PW) August 2002 296 Management Information Base 298 The model for using the VC in non-point to point applications, such 299 as VPLS are done with the same principle in mind, but the details 300 are yet FFS. 302 6.3 Example of MIB usage 304 TBD 306 7 Object definitions 308 -- 309 -- Ethernet PW MIB 310 -- 312 PW-ENET-MIB DEFINITIONS ::= BEGIN 314 IMPORTS 315 OBJECT-TYPE, MODULE-IDENTITY, experimental, 316 Counter64 317 FROM SNMPv2-SMI 319 MODULE-COMPLIANCE, OBJECT-GROUP 320 FROM SNMPv2-CONF 322 StorageType, RowStatus 323 FROM SNMPv2-TC 325 InterfaceIndexOrZero 326 FROM IF-MIB 328 pwVcIndex 329 FROM PW-MIB 331 PwVcVlanCfg 332 FROM PW-TC-MIB; 334 pwVcEnetMIB MODULE-IDENTITY 335 LAST-UPDATED "200208201200Z" -- 20 August 2002 12:00:00 GMT 336 ORGANIZATION 337 "IETF PWE3 Working group" 338 CONTACT-INFO 339 "David Zelig 340 Postal: Corrigent Systems 341 126, Yigal Alon St. 342 Tel Aviv, ISRAEL 343 Phone: +972-3-6945273 344 E-mail: davidz@corrigent.com 346 Thomas D. Nadeau 347 Postal: Cisco Systems, Inc. 349 Ethernet Pseudo Wire (PW) August 2002 350 Management Information Base 352 250 Apollo Drive 353 Chelmsford, MA 01824 354 Tel: +1-978-497-3051 355 Email: tnadeau@cisco.com 356 " 357 DESCRIPTION 358 "This MIB describes a model for managing Ethernet 359 point-to-point pseudo wire services over a Packet 360 Switched Network (PSN)." 362 -- Revision history. 363 REVISION 364 "200208201200Z" -- 20 August 2002 12:00:00 GMT 365 DESCRIPTION 366 "Changes from previous version: 367 1) Add pwVcEnetVcIfIndex - Option for VC as ifIndex. 368 2) Change counters to 64 bits. 369 3) Add mode for adding/removing VLAN fields between PW and 370 CE bound interface. 371 4) Referencing draft-martini instead of draft-so. 372 5) Editorial changes for some description clauses. 373 6) MPLS PRI mapping table to be independent (not augmented). 374 7) Adapt descriptions and rules of use to 375 dratf-ietf-pw3ei-Ethernet-encap-00. 376 " 377 REVISION 378 "200202031200Z" -- 03 February 2002 12:00:00 GMT 379 DESCRIPTION 380 "initial revision as -00 draft" 382 ::= { experimental xxx } -- TBD: Get number from IANA 384 pwVcEnetNotifications OBJECT IDENTIFIER ::= { pwVcEnetMIB 0 } 385 pwVcEnetObjects OBJECT IDENTIFIER ::= { pwVcEnetMIB 1 } 386 pwVcEnetConformance OBJECT IDENTIFIER ::= { pwVcEnetMIB 2 } 388 -- 389 -- VC Ethernet table 390 -- 392 pwVcEnetTable OBJECT-TYPE 393 SYNTAX SEQUENCE OF PwVcEnetEntry 394 MAX-ACCESS not-accessible 395 STATUS current 396 DESCRIPTION 397 "This table contains the index to the Ethernet tables 398 associated with this ETH VC, the VLAN configuration and 399 VLAN mode." 400 ::= { pwVcEnetObjects 1 } 402 Ethernet Pseudo Wire (PW) August 2002 403 Management Information Base 405 pwVcEnetEntry OBJECT-TYPE 406 SYNTAX PwVcEnetEntry 407 MAX-ACCESS not-accessible 408 STATUS current 409 DESCRIPTION 410 "This table is indexed by the same index that was created 411 for the associated entry in the PW VC Table in the PW-MIB. 412 The PwVcIndex and the pwVcEnetPwVlan are used as indexes 413 to allow multiple VLANs to exist on the same PW. 415 An entry is created in this table by the agent for every 416 entry in the pwVc table with a VcType of 'ethernetVLAN', 417 'ethernet' or 'ethernetVPLS'. Additional rows may be 418 created by the operator or the agent if multiple entries 419 are required for the same VC. 421 This table provides Ethernet port mapping and VLAN 422 configuration for each Ethernet VC." 424 INDEX { pwVcIndex, pwVcEnetPwVlan } 425 ::= { pwVcEnetTable 1 } 427 PwVcEnetEntry ::= SEQUENCE { 428 pwVcEnetPwVlan PwVcVlanCfg, 429 pwVcEnetVlanMode INTEGER, 430 pwVcEnetMaxVlan PwVcVlanCfg, 431 pwVcEnetPortVlan PwVcVlanCfg, 433 pwVcEnetPortIfIndex InterfaceIndexOrZero, 434 pwVcEnetVcIfIndex InterfaceIndexOrZero, 436 pwVcEnetRowStatus RowStatus, 437 pwVcEnetStorageType StorageType 438 } 440 pwVcEnetPwVlan OBJECT-TYPE 441 SYNTAX PwVcVlanCfg 442 MAX-ACCESS not-accessible 443 STATUS current 444 DESCRIPTION 445 "This Object defines the VLAN on the VC. The value of 4097 446 is used if the object is not applicable, for example when 447 mapping all packets from an Ethernet port to this VC. 448 The value of 4096 is used to indicate untagged frames (at 449 least from the PW point of view), for example if 450 pwVcEnetVlanMode is equal 'removeVLAN' or when 451 pwVcEnetVlanMode equal 'noChange' and pwVcEnetPortVlan 452 is equal 4096." 453 ::= { pwVcEnetEntry 1 } 455 pwVcEnetVlanMode OBJECT-TYPE 457 Ethernet Pseudo Wire (PW) August 2002 458 Management Information Base 460 SYNTAX INTEGER { 461 portBased(0), 462 noChange(1), 463 changeVlan(2), 464 addVlan(3), 465 removeVlan(4), 466 rangeVlan(5) 467 } 468 MAX-ACCESS read-create 469 STATUS current 470 DESCRIPTION 471 "Indicate the mode of VLAN handling between the port 472 associated to the VC and the VC encapsulation itself. 474 - 'portBased' indicates that the forwarder will forward 475 packets to the PW independent of their structure, 476 based on the incoming port only. 478 - 'noChange' indicates that the VC contains the original 479 user VLAN, as specified in pwVcEnetPortVlan. 481 - 'changeVlan' indicates that the VLAN field on the VC 482 may be different than the VLAN field on the user's 483 port. 485 - 'removeVlan' indicates that the encapsulation on the 486 VC does not include the original VLAN field. Note 487 that PRI bits transparency is lost in this case. 489 - 'addVlan' indicate that a VLAN field will be added 490 on the PSN bound direction. pwVcEnetPwVlan indicate 491 the value that will be added. 493 - 'rangeVlan' indicate that all VLANs between 494 pwVcEnetPwVlan and pwVcEnetMaxVlan on the user port 495 will be associated to this VC. It is not possible to 496 change VLAN values on this mode. 498 - 'removeVlan', 'addVlan' and 'rangeVlan' implementation 499 is not required. 500 " 501 DEFVAL { noChange } 502 ::= { pwVcEnetEntry 2 } 504 pwVcEnetMaxVlan OBJECT-TYPE 505 SYNTAX PwVcVlanCfg 506 MAX-ACCESS read-create 507 STATUS current 508 DESCRIPTION 509 "This object is used to define the MAX value of VLAN range 510 for this VC, and is in effect if pwVcEnetVlanMode is equal 512 Ethernet Pseudo Wire (PW) August 2002 513 Management Information Base 515 to 'rangeVlan', and must be greater or equal to 516 pwVcEnetPwVlan. 517 If a range is not used the value must be set to 0." 518 DEFVAL { 0 } 519 ::= { pwVcEnetEntry 3 } 521 pwVcEnetPortVlan OBJECT-TYPE 522 SYNTAX PwVcVlanCfg 523 MAX-ACCESS read-create 524 STATUS current 525 DESCRIPTION 526 "This object define the VLAN value on the physical port (or 527 VPLS virtual port) if a change is required to the VLAN value 528 between the VC and the physical/virtual port. 530 This object MUST hold the value of 4097 (not relevant) if 531 the whole traffic from the port is forwarded to one VC 532 independent of the tagging on the port or if 533 pwVcEnetVlanMode is set to rangeVlan. 535 It MUST be equal to pwVcEnetPwVlan if 'noChange' mode 536 is used. 538 The value 4096 indicate that no VLAN (i.e. untagged 539 frames) on the port are associated to this VC. This 540 allows the same behaviors as assigning 'Default VLAN' 541 to un-tagged frames. 542 " 543 DEFVAL { 4097 } 544 ::= { pwVcEnetEntry 4 } 546 pwVcEnetVcIfIndex OBJECT-TYPE 547 SYNTAX InterfaceIndexOrZero 548 MAX-ACCESS read-create 549 STATUS current 550 DESCRIPTION 551 "It is sometimes convenient to model the VC PW as a 552 virtual interface in the ifTable. In these cases this 553 object hold the value of the ifIndex in the ifTable 554 representing this VC PW. A value of zero indicate no such 555 association or association is not yet known." 557 ::= { pwVcEnetEntry 5 } 559 pwVcEnetPortIfIndex OBJECT-TYPE 560 SYNTAX InterfaceIndexOrZero 561 MAX-ACCESS read-create 562 STATUS current 563 DESCRIPTION 564 "This object is used to specify the ifIndex of the ETHERNET 565 port associated with this VC for point-to-point Ethernet 567 Ethernet Pseudo Wire (PW) August 2002 568 Management Information Base 570 service, or the ifIndex of the virtual interface of the VPLS 571 instance associated with the PW if the service is VPLS. Two 572 rows in this table can point to the same ifIndex only if: 574 1) It is required to support multiple COS on a MPLS PSN 575 for the same service (i.e.: a combination of ports and 576 VLANs) by the use of multiple VC, each with a different 577 COS. 579 2) There is no overlap of VLAN values specified in 580 pwVcEnetPortVlan that are associated with this port. 582 A value of zero indicate that association to an ifIndex is 583 not yet known." 585 ::= { pwVcEnetEntry 6 } 587 pwVcEnetRowStatus OBJECT-TYPE 588 SYNTAX RowStatus 589 MAX-ACCESS read-create 590 STATUS current 591 DESCRIPTION 592 "Enable creating, deleting and modifying this row." 593 -- TBD: Need to specify exact interaction with other tables, and 594 -- when rows can/cannot be created/deleted/modified. 595 ::= { pwVcEnetEntry 7 } 597 pwVcEnetStorageType OBJECT-TYPE 598 SYNTAX StorageType 599 MAX-ACCESS read-create 600 STATUS current 601 DESCRIPTION 602 "Indicates the storage type of this row." 603 ::= { pwVcEnetEntry 8 } 605 -- 606 -- Ethernet Primary Mapping Table 607 -- 609 pwVcEnetMplsPriMappingTable OBJECT-TYPE 610 SYNTAX SEQUENCE OF PwVcEnetMplsPriMappingTableEntry 611 MAX-ACCESS not-accessible 612 STATUS current 613 DESCRIPTION 614 "This table may be used for MPLS PSNs if there is a need 615 to hold multiple VC, each with different COS, for the same 616 user service (port + PW VLAN). Such a need may arise if the 617 MPLS network is capable of L-LSP or E-LSP without multiple 618 COS capabilities. Each row is indexed by the pwVcIndex 619 and indicate the PRI bits on the packet recieved from the 621 Ethernet Pseudo Wire (PW) August 2002 622 Management Information Base 624 user port (or VPLS virtual port) that are 625 classified to this VC. Note that the EXP bit value of the VC 626 is configured in the PW-MPLS-MIB." 627 ::= { pwVcEnetObjects 2 } 629 pwVcEnetMplsPriMappingTableEntry OBJECT-TYPE 630 SYNTAX PwVcEnetMplsPriMappingTableEntry 631 MAX-ACCESS not-accessible 632 STATUS current 633 DESCRIPTION 634 "Each entry is created if special classification based on 635 the PRI bits is required for this VC." 637 INDEX { pwVcIndex } 639 ::= { pwVcEnetMplsPriMappingTable 1 } 641 PwVcEnetMplsPriMappingTableEntry ::= SEQUENCE { 642 pwVcEnetMplsPriMapping BITS, 643 pwVcEnetMplsPriMappingRowStatus RowStatus, 644 pwVcEnetMplsPriMappingStorageType StorageType 645 } 647 pwVcEnetMplsPriMapping OBJECT-TYPE 648 SYNTAX BITS { 649 pri000 (0), 650 pri001 (1), 651 pri010 (2), 652 pri011 (3), 653 pri100 (4), 654 pri101 (5), 655 pri110 (6), 656 pri111 (7), 657 untagged (8) 658 } 659 MAX-ACCESS read-create 660 STATUS current 661 DESCRIPTION 662 "This object defines the groups of user PRI mapped into 663 this VC. Each bit set indicates that this user priority 664 is assigned to this VC. 666 The value 'untagged' is used to indicate that untagged 667 frames are also associated to this VC. 669 This object allow the use of different PSN COS based on 670 user marking of PRI bits in MPLS PSN with L-LSP or 671 E-LSP without multiple COS support. In all other cases, 672 the default value MUST be used. 674 It is REQUIRED that there is no overlap on this object 676 Ethernet Pseudo Wire (PW) August 2002 677 Management Information Base 679 between rows serving the same service (port+ PW VLAN). 681 In case of missing BIT configuration between rows to 682 the same service, incoming packets with PRI marking not 683 configured should be handled by the VC with the lowest 684 COS. 685 " 686 REFERENCE 687 "See appendix A of 688 for mapping rules of the PRI bits to PSN COS." 690 ::= { pwVcEnetMplsPriMappingTableEntry 1 } 692 pwVcEnetMplsPriMappingRowStatus OBJECT-TYPE 693 SYNTAX RowStatus 694 MAX-ACCESS read-create 695 STATUS current 696 DESCRIPTION 697 "Enable creating, deleting and modifying this row." 698 -- TBD: Need to specify exact interaction with other tables, and 699 -- when rows can/cannot be created/deleted/modified. 700 ::= { pwVcEnetMplsPriMappingTableEntry 2 } 702 pwVcEnetMplsPriMappingStorageType OBJECT-TYPE 703 SYNTAX StorageType 704 MAX-ACCESS read-create 705 STATUS current 706 DESCRIPTION 707 "Indicates the storage type of this row." 708 ::= { pwVcEnetMplsPriMappingTableEntry 3 } 710 -- 711 -- VC Ethernet Statistics Table 712 -- 714 pwVcEnetStatsTable OBJECT-TYPE 715 SYNTAX SEQUENCE OF PwVcEnetStatsEntry 716 MAX-ACCESS not-accessible 717 STATUS current 718 DESCRIPTION 719 "This table contains statistical counters specific for 720 Ethernet PW." 721 ::= { pwVcEnetObjects 3 } 723 pwVcEnetStatsEntry OBJECT-TYPE 724 SYNTAX PwVcEnetStatsEntry 725 MAX-ACCESS not-accessible 726 STATUS current 727 DESCRIPTION 728 "Each entry represents the statistics gathered for the 730 Ethernet Pseudo Wire (PW) August 2002 731 Management Information Base 733 VC carrying the Ethernet packets since this VC was 734 first created in the pwVcEnetTable." 735 INDEX { pwVcIndex } 736 ::= { pwVcEnetStatsTable 1 } 738 PwVcEnetStatsEntry ::= SEQUENCE { 739 pwVcEnetStatsIllegalVlan Counter64, 740 pwVcEnetStatsIllegalLength Counter64 741 } 743 pwVcEnetStatsIllegalVlan OBJECT-TYPE 744 SYNTAX Counter64 745 MAX-ACCESS read-write 746 STATUS current 747 DESCRIPTION 748 "The number of packets received (from the PSN) on this VC with 749 an illegal VLAN field, missing VLAN field that was expected, or 750 A VLAN field when it was not expected. This counter is not 751 relevant if the VC type is 'ethernet' (i.e. raw mode), and 752 should be set to 0 by the agent to indicate this." 753 ::= { pwVcEnetStatsEntry 1 } 755 pwVcEnetStatsIllegalLength OBJECT-TYPE 756 SYNTAX Counter64 757 MAX-ACCESS read-write 758 STATUS current 759 DESCRIPTION 760 "The number of packets that were received with an illegal 761 Ethernet packet length on this VC. An illegal length is defined 762 as being greater than the value in the advertised maximum MTU 763 supported, or shorter than the allowed Ethernet packet size." 764 ::= { pwVcEnetStatsEntry 2 } 766 --- 767 --- Conformance description 768 --- In this version of the draft, only objects level conformance is 769 --- defined. More detailed conformance specifications is FFS. 770 --- 772 pwVcEnetGroups OBJECT IDENTIFIER ::= { pwVcEnetConformance 1 } 773 pwVcEnetCompliances OBJECT IDENTIFIER ::= { pwVcEnetConformance 2 } 775 pwVcEnetModuleCompliance MODULE-COMPLIANCE 776 STATUS current 777 DESCRIPTION 778 "The compliance statement for agent that support 779 Ethernet PW." 781 MODULE -- this module 782 MANDATORY-GROUPS { pwVcEnetGroup, 784 Ethernet Pseudo Wire (PW) August 2002 785 Management Information Base 787 pwVcStatsGroup 788 } 790 GROUP pwVcEnetMplsPriGroup 791 DESCRIPTION 792 "Collection of objects defining classification to 793 different PW based on the user's PRI bits mapping. 794 This group is optional, and should be implemented 795 only for MPLS PSN where only L-LSP or single OA 796 E-LSP, exists, and different PSN COS is required 797 based on the PRI mapping." 799 ::= { pwVcEnetCompliances 1 } 801 -- Units of conformance. 803 pwVcEnetGroup OBJECT-GROUP 804 OBJECTS { 805 pwVcEnetVlanMode, 806 pwVcEnetMaxVlan, 807 pwVcEnetPortVlan, 808 pwVcEnetPortIfIndex, 809 pwVcEnetVcIfIndex, 810 pwVcEnetRowStatus, 811 pwVcEnetStorageType 812 } 813 STATUS current 814 DESCRIPTION 815 "Collection of objects for basic Ethernet PW config." 816 ::= { pwVcEnetGroups 1 } 818 pwVcStatsGroup OBJECT-GROUP 819 OBJECTS { 820 pwVcEnetStatsIllegalVlan, 821 pwVcEnetStatsIllegalLength 822 } 823 STATUS current 824 DESCRIPTION 825 "Collection of objects counting various PW level errors." 826 ::= { pwVcEnetGroups 2 } 828 pwVcEnetMplsPriGroup OBJECT-GROUP 829 OBJECTS { 830 pwVcEnetMplsPriMapping, 831 pwVcEnetMplsPriMappingRowStatus, 832 pwVcEnetMplsPriMappingStorageType 833 } 834 STATUS current 835 DESCRIPTION 836 "Collection of objects defining classification to 837 different PW based on the user's PRI bits mapping. 839 Ethernet Pseudo Wire (PW) August 2002 840 Management Information Base 842 This group is optional, and should be implemented 843 only for MPLS PSN where only L-LSP or single OA 844 E-LSP exists, and different PSN COS is required 845 based on the PRI mapping." 846 ::= { pwVcEnetGroups 3 } 848 END 850 8 Security Considerations 852 There are a number of management objects defined in this MIB that 853 have a MAX-ACCESS clause of read-write and/or read-create. Such 854 objects may be considered sensitive or vulnerable in some network 855 environments. The support for SET operations in a non-secure 856 environment without proper protection can have a negative effect on 857 network operations. 859 SNMPv1 by itself is not a secure environment. Even if the network 860 itself is secure (for example by using IPSec), even then, there is 861 no control as to who on the secure network is allowed to access and 862 GET/SET (read/change/create/delete) the objects in this MIB. 864 It is recommended that the implementers consider the security 865 features as provided by the SNMPv3 framework. Specifically, the use 866 of the User-based Security Model RFC 2574 [RFC2574] and the View- 867 based Access Control Model RFC 2575 [RFC2575] is recommended. 869 It is then a customer/user responsibility to ensure that the SNMP 870 entity giving access to an instance of this MIB, is properly 871 configured to give access to the objects only to those principals 872 (users) that have legitimate rights to indeed GET or SET 873 (change/create/delete) them. 875 Ethernet Pseudo Wire (PW) August 2002 876 Management Information Base 878 9 References 880 [ENETPW] Martini et al, "Encapsulation Methods for Transport of 881 Ethernet Frames Over IP/MPLS Networks", , August 2002. 884 [FRMWK] Pate et al, "Framework for Pseudo Wire Emulation Edge- 885 to-Edge (PWE3)", , 886 June 2002. 888 [PWREQ] Xiao et al, "Requirements for Pseudo Wire Emulation 889 Edge-to-Edge (PWE3)", , June 2002. 892 [PWLAYER] Bryant, et al., "Protocol Layering in PWE3", , May 2002. 895 [VPLS] Augustyn et al, "Requirements for Virtual Private LAN 896 Services (VPLS)", , February 2002. 899 [PWTC] Nadeau, T., et al, "Definitions for Textual Conventions 900 and OBJECT-IDENTITIES for Pseudo-Wires Management", 901 , June 2002. 903 [PWMIB] Zelig et al, �Pseudo Wire (PW) Management Information 904 Base�, , June 2002. 906 [PWMPLSMIB] Zelig et al, �Pseudo Wire (PW) Over MPLS PSN Management 907 Information Base�, , 908 June 2002. 910 [ENETLIKE] Flick, J., "Definitions of Managed Objects for the 911 Ethernet-like Interface Types", , May 2002. 914 [IANAFamily] Internet Assigned Numbers Authority (IANA), ADDRESS 915 FAMILY NUMBERS, (http://www.isi.edu/in- 916 notes/iana/assignements/address-family-numbers), for MIB 917 see: ftp://ftp.isi.edu/mib/ianaaddressfamilynumbers.mib 919 [IFMIB] McCloghrie, K., and F. Kastenholtz, "The Interfaces 920 Group MIB using SMIv2", RFC 2863, January 2000. 922 [BCP14] Bradner, S., "Key words for use in RFCs to Indicate 923 requirement Levels", BCP 14, RFC 2119, March 1997. 925 [RFC2571] Harrington, D., Presuhn, R., and B. Wijnen, "An 926 Architecture for Describing SNMP Management Frameworks", 927 RFC 2571, April 1999. 929 Ethernet Pseudo Wire (PW) August 2002 930 Management Information Base 932 [RFC1155] Rose, M., and K. McCloghrie, "Structure and 933 Identification of Management Information for TCP/IP- 934 based Internets", STD 16, RFC 1155, May 1990. 936 [RFC1212] Rose, M., and K. McCloghrie, "Concise MIB Definitions", 937 STD 16, RFC 1212, March 1991. 939 [RFC1215] M. Rose, "A Convention for Defining Traps for use with 940 the SNMP", RFC 1215, March 1991. 942 [RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J, 943 Rose, M., and S. Waldbusser, "Structure of Management 944 Information Version 2 (SMIv2)", STD 58, RFC 2578, April 945 1999. 947 [RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J, 948 Rose, M., and S. Waldbusser, "Textual Conventions for 949 SMIv2", STD 58, RFC 2579, April 1999. 951 [RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J, 952 Rose, M., and S. Waldbusser, "Conformance Statements for 953 SMIv2", STD 58, RFC 2580, April 1999. 955 [RFC1157] Case, J., Fedor, M., Schoffstall, M., and J. Davin, 956 "Simple Network Management Protocol", STD 15, RFC 1157, 957 May 1990. 959 [RFC1901] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 960 "Introduction to Community-based SNMPv2", RFC 1901, 961 January 1996. 963 [RFC1906] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 964 "Transport Mappings for Version 2 of the Simple Network 965 Management Protocol (SNMPv2)", RFC 1906, January 1996. 967 [RFC2572] Case, J., Harrington D., Presuhn R., and B. Wijnen, 968 "Message Processing and Dispatching for the Simple 969 Network Management Protocol (SNMP)", RFC 2572, April 970 1999. 972 [RFC2574] Blumenthal, U., and B. Wijnen, "User-based Security 973 Model (USM) for version 3 of the Simple Network 974 Management Protocol (SNMPv3)", RFC 2574, April 1999. 976 [RFC1905] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 977 "Protocol Operations for Version 2 of the Simple Network 978 Management Protocol (SNMPv2)", RFC 1905, January 1996. 980 [RFC2573] Levi, D., Meyer, P., and B. Stewart, "SNMPv3 981 Applications", RFC 2573, April 1999. 983 Ethernet Pseudo Wire (PW) August 2002 984 Management Information Base 986 [RFC2575] Wijnen, B., Presuhn, R., and K. McCloghrie, "View-based 987 Access Control Model (VACM) for the Simple Network 988 Management Protocol (SNMP)", RFC 2575, April 1999. 990 [RFC2570] Case, J., Mundy, R., Partain, D., and B. Stewart, 991 "Introduction to Version 3 of the Internet-standard 992 Network Management Framework", RFC 2570, April 1999. 994 0 Author's Addresses 996 David Zelig 997 Corrigent Systems 998 126, Yigal Alon st. 999 Tel Aviv, ISRAEL 1000 Phone: +972-3-6945273 1001 Email: davidz@corrigent.com 1003 Thomas D. Nadeau 1004 Cisco Systems, Inc. 1005 250 Apollo Drive 1006 Chelmsford, MA 01824 1007 Email: tnadeau@cisco.com 1009 1 Full Copyright Statement 1011 Copyright (C) The Internet Society (2000). All Rights Reserved. 1013 This document and translations of it may be copied and furnished to 1014 others, and derivative works that comment on or otherwise explain it 1015 or assist in its implementation may be prepared, copied, published 1016 and distributed, in whole or in part, without restriction of any 1017 kind, provided that the above copyright notice and this paragraph 1018 are included on all such copies and derivative works. However, this 1019 document itself may not be modified in any way, such as by removing 1020 the copyright notice or references to the Internet Society or other 1021 Internet organizations, except as needed for the purpose of 1022 developing Internet standards in which case the procedures for 1023 copyrights defined in the Internet Standards process must be 1024 followed, or as required to translate it into languages other than 1025 English. 1027 The limited permissions granted above are perpetual and will not be 1028 revoked by the Internet Society or its successors or assigns. This 1029 document and the information contained herein is provided on an "AS 1030 IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK 1031 FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT 1032 NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN 1034 Ethernet Pseudo Wire (PW) August 2002 1035 Management Information Base 1037 WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF 1038 MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.