idnits 2.17.1 draft-ietf-hubmib-ether-chipsets-02.txt: 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: ---------------------------------------------------------------------------- ** Missing expiration date. The document expiration date should appear on the first and last page. ** The document seems to lack a 1id_guidelines paragraph about Internet-Drafts being working documents. ** The document seems to lack a 1id_guidelines paragraph about 6 months document validity -- however, there's a paragraph with a matching beginning. Boilerplate error? == No 'Intended status' indicated for this document; assuming Proposed Standard == It seems as if not all pages are separated by form feeds - found 0 form feeds but 18 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. ** The abstract seems to contain references ([16]), which it shouldn't. Please replace those with straight textual mentions of the documents in question. 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 (May 1999) is 9113 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) ** Obsolete normative reference: RFC 2571 (ref. '1') (Obsoleted by RFC 3411) ** Downref: Normative reference to an Informational RFC: RFC 1215 (ref. '4') ** Downref: Normative reference to an Historic RFC: RFC 1157 (ref. '8') ** Downref: Normative reference to an Historic RFC: RFC 1901 (ref. '9') ** Obsolete normative reference: RFC 1906 (ref. '10') (Obsoleted by RFC 3417) ** Obsolete normative reference: RFC 2572 (ref. '11') (Obsoleted by RFC 3412) ** Obsolete normative reference: RFC 2574 (ref. '12') (Obsoleted by RFC 3414) ** Obsolete normative reference: RFC 1905 (ref. '13') (Obsoleted by RFC 3416) ** Obsolete normative reference: RFC 2573 (ref. '14') (Obsoleted by RFC 3413) ** Obsolete normative reference: RFC 2575 (ref. '15') (Obsoleted by RFC 3415) == Outdated reference: A later version (-04) exists of draft-ietf-hubmib-etherif-mib-v2-02 Summary: 17 errors (**), 0 flaws (~~), 4 warnings (==), 2 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 Hub MIB Working Group J. Flick 2 INTERNET DRAFT Hewlett-Packard Company 3 May 1999 5 Definitions of Object Identifiers for 6 Identifying Ethernet Chip Sets 8 10 Status of this Memo 12 This document is an Internet-Draft and is in full conformance with 13 all provisions of Section 10 of RFC2026. Internet-Drafts are working 14 documents of the Internet Engineering Task Force (IETF), its areas, 15 and its working groups. Note that other groups may also distribute 16 working documents as Internet-Drafts. 18 Internet-Drafts are draft documents valid for a maximum of six months 19 and may be updated, replaced, or obsoleted by other documents at any 20 time. It is inappropriate to use Internet- Drafts as reference 21 material or to cite them other than as "work in progress." 23 The list of current Internet-Drafts can be accessed at 24 http://www.ietf.org/ietf/1id-abstracts.txt 26 The list of Internet-Draft Shadow Directories can be accessed at 27 http://www.ietf.org/shadow.html. 29 Copyright Notice 31 Copyright (C) The Internet Society (1999). All Rights Reserved. 33 Abstract 35 This memo defines OBJECT IDENTIFIER values for use with network 36 management protocols in the Internet community. In particular, it 37 contains registered OID values for use with the dot3StatsEtherChipSet 38 object in the EtherLike-MIB [16]. These registrations have been 39 split from [16] into a separate document for maintenance purposes. 41 Distribution of this memo is unlimited. Please forward comments to 42 hubmib@hprnd.rose.hp.com. 44 Table of Contents 46 1. Introduction ............................................... 2 47 2. The SNMP Management Framework .............................. 2 48 3. Definitions ................................................ 3 49 4. Intellectual Property ...................................... 14 50 5. Acknowledgements ........................................... 15 51 6. References ................................................. 15 52 7. Security Considerations .................................... 17 53 8. Author's Address ........................................... 17 54 9. Full Copyright Statement ................................... 17 56 1. Introduction 58 This memo defines OBJECT IDENTIFIER values for use with network 59 management protocols in the Internet community. In particular, it 60 contains registered OID values for use with the dot3StatsEtherChipSet 61 object in the EtherLike-MIB [16]. These registrations have been 62 split from [16] into a separate document for maintenance purposes. 64 The dot3StatsEtherChipSet object has recently been deprecated. The 65 purpose of this document is to capture historic assignments made by 66 the various IETF working groups that have been responsible for 67 maintaining the EtherLike-MIB. Implementations which support the 68 dot3StatsEtherChipSet object for backwards compatability may continue 69 to use the OBJECT IDENTIFIER values assigned in this document. 71 For those chipsets not represented in this document, implementors 72 should assign OBJECT IDENTIFIER values within that part of the 73 registration tree delegated to individual enterprises. 75 2. The SNMP Management Framework 77 The SNMP Management Framework presently consists of five major 78 components: 80 o An overall architecture, described in RFC 2571 [1]. 82 o Mechanisms for describing and naming objects and events for the 83 purpose of management. The first version of this Structure of 84 Management Information (SMI) is called SMIv1 and described in 85 RFC 1155 [2], RFC 1212 [3] and RFC 1215 [4]. The second version, 86 called SMIv2, is described in RFC 2578 [5], RFC 2579 [6] and RFC 87 2580 [7]. 89 o Message protocols for transferring management information. The 90 first version of the SNMP message protocol is called SNMPv1 and 91 described in RFC 1157 [8]. A second version of the SNMP message 92 protocol, which is not an Internet standards track protocol, is 93 called SNMPv2c and described in RFC 1901 [9] and RFC 1906 [10]. 94 The third version of the message protocol is called SNMPv3 and 95 described in RFC 1906 [10], RFC 2572 [11] and RFC 2574 [12]. 97 o Protocol operations for accessing management information. The 98 first set of protocol operations and associated PDU formats is 99 described in RFC 1157 [8]. A second set of protocol operations 100 and associated PDU formats is described in RFC 1905 [13]. 102 o A set of fundamental applications described in RFC 2573 [14] and 103 the view-based access control mechanism described in RFC 2575 104 [15]. 106 Managed objects are accessed via a virtual information store, termed 107 the Management Information Base or MIB. Objects in the MIB are 108 defined using the mechanisms defined in the SMI. 110 This memo specifies a MIB module that is compliant to the SMIv2. A 111 MIB conforming to the SMIv1 can be produced through the appropriate 112 translations. The resulting translated MIB must be semantically 113 equivalent, except where objects or events are omitted because no 114 translation is possible (use of Counter64). Some machine readable 115 information in SMIv2 will be converted into textual descriptions in 116 SMIv1 during the translation process. However, this loss of machine 117 readable information is not considered to change the semantics of the 118 MIB. 120 3. Definitions 122 ETHER-CHIPSET-MIB DEFINITIONS ::= BEGIN 124 IMPORTS 125 MODULE-IDENTITY, OBJECT-IDENTITY, mib-2 126 FROM SNMPv2-SMI 127 dot3 128 FROM EtherLike-MIB; 130 etherChipsetMIB MODULE-IDENTITY 131 LAST-UPDATED "9901280202Z" -- January 28, 1999 132 ORGANIZATION "IETF 802.3 Hub MIB Working Group" 133 CONTACT-INFO 134 "WG E-mail: hubmib@hprnd.rose.hp.com 135 To subscribe: hubmib-request@hprnd.rose.hp.com 137 Chair: Dan Romascanu 138 Postal: Lucent Technologies 139 Atidum Technology Park, Bldg. 3 140 Tel Aviv 61131 141 Israel 142 Tel: +972 3 645 8414 143 E-mail: dromasca@lucent.com 145 Editor: John Flick 146 Postal: Hewlett-Packard Company 147 8000 Foothills Blvd. M/S 5556 148 Roseville, CA 95747-5556 149 USA 150 Tel: +1 916 785 4018 151 Fax: +1 916 785 3583 152 E-mail: johnf@rose.hp.com" 154 DESCRIPTION "This MIB module contains registered values for 155 use by the dot3StatsEtherChipSet object in 156 the EtherLike-MIB. This object is used to 157 identify the MAC hardware used to communicate 158 on an interface. 160 Note that the dot3StatsEtherChipSet object 161 has been deprecated. The primary purpose of 162 this module is to capture historic assignments 163 made by the various IETF working groups that 164 have been responsible for maintaining the 165 EtherLike-MIB. Implementations which support 166 the dot3StatsEtherChipSet object for backwards 167 compatability may continue to use these values. 168 For those chipsets not represented in this 169 module, registration is required in other 170 documentation, e.g., assignment within that 171 part of the registration tree delegated to 172 individual enterprises (see RFC 1155 and RFC 173 1902)." 175 REVISION "9901280031Z" -- January 28, 1999 176 DESCRIPTION "Initial version of this module created by 177 splitting the chipset registration information 178 out from the EtherLike-MIB." 179 ::= { mib-2 XX } 180 -- NOTE TO RFC EDITOR: When this document is published as 181 -- an RFC, change XX to next available mib-2 branch, 182 -- assigned by IANA, and delete this comment. 184 dot3ChipSets OBJECT IDENTIFIER ::= { dot3 8 } 186 dot3ChipSetAMD OBJECT IDENTIFIER ::= { dot3ChipSets 1 } 188 dot3ChipSetAMD7990 OBJECT-IDENTITY 189 STATUS current 190 DESCRIPTION "The authoritative identifier for the Advanced 191 Micro Devices Am7990 Local Area Network 192 Controller for Ethernet (LANCE)." 193 ::= { dot3ChipSetAMD 1 } 195 dot3ChipSetAMD79900 OBJECT-IDENTITY 196 STATUS current 197 DESCRIPTION "The authoritative identifier for the Advanced 198 Micro Devices Am79900 chip." 199 ::= { dot3ChipSetAMD 2 } 201 dot3ChipSetAMD79C940 OBJECT-IDENTITY 202 STATUS current 203 DESCRIPTION "The authoritative identifier for the Advanced 204 Micro Devices Am79C940 Media Access Controller 205 for Ethernet (MACE)." 206 ::= { dot3ChipSetAMD 3 } 208 dot3ChipSetAMD79C90 OBJECT-IDENTITY 209 STATUS current 210 DESCRIPTION "The authoritative identifier for the Advanced 211 Micro Devices Am79C90 CMOS Local Area Network 212 Controller for Ethernet (C-LANCE)." 213 ::= { dot3ChipSetAMD 4 } 215 dot3ChipSetAMD79C960 OBJECT-IDENTITY 216 STATUS current 217 DESCRIPTION "The authoritative identifier for the Advanced 218 Micro Devices Am79C960 PCnet-ISA Single Chip 219 Ethernet Controller for ISA." 220 ::= { dot3ChipSetAMD 5 } 222 dot3ChipSetAMD79C961 OBJECT-IDENTITY 223 STATUS current 224 DESCRIPTION "The authoritative identifier for the Advanced 225 Micro Devices Am79C961 PCnet-ISA+ Single Chip 226 Plug & Play Full-Duplex Ethernet Controller 227 for ISA." 228 ::= { dot3ChipSetAMD 6 } 230 dot3ChipSetAMD79C961A OBJECT-IDENTITY 231 STATUS current 232 DESCRIPTION "The authoritative identifier for the Advanced 233 Micro Devices Am79C961A PCnet-ISA II Single Chip 234 Plug & Play Full-Duplex Ethernet Controller 235 for ISA." 236 ::= { dot3ChipSetAMD 7 } 238 dot3ChipSetAMD79C965 OBJECT-IDENTITY 239 STATUS current 240 DESCRIPTION "The authoritative identifier for the Advanced 241 Micro Devices Am79C965 PCnet-32 Single Chip 242 Ethernet Controller for PCI." 243 ::= { dot3ChipSetAMD 8 } 245 dot3ChipSetAMD79C970 OBJECT-IDENTITY 246 STATUS current 247 DESCRIPTION "The authoritative identifier for the Advanced 248 Micro Devices Am79C970 PCnet PCI Single Chip 249 Ethernet Controller for PCI Local Bus." 250 ::= { dot3ChipSetAMD 9 } 252 dot3ChipSetAMD79C970A OBJECT-IDENTITY 253 STATUS current 254 DESCRIPTION "The authoritative identifier for the Advanced 255 Micro Devices AM79C970A PCnet PCI II Single Chip 256 Full-Duplex Ethernet Controller for PCI Local 257 Bus." 258 ::= { dot3ChipSetAMD 10 } 260 dot3ChipSetAMD79C971 OBJECT-IDENTITY 261 STATUS current 262 DESCRIPTION "The authoritative identifier for the Advanced 263 Micro Devices Am79C971 PCnet-FAST Single Chip 264 Full-Duplex 10/100 Mbps Ethernet Controller for 265 PCI Local Bus." 266 ::= { dot3ChipSetAMD 11 } 268 dot3ChipSetAMD79C972 OBJECT-IDENTITY 269 STATUS current 270 DESCRIPTION "The authoritative identifier for the Advanced 271 Micro Devices Am79C972 PCnet-FAST+ Enhanced 272 10/100 Mbps PCI Ethernet Controller with OnNow 273 Support." 274 ::= { dot3ChipSetAMD 12 } 276 dot3ChipSetIntel OBJECT IDENTIFIER ::= { dot3ChipSets 2 } 278 dot3ChipSetIntel82586 OBJECT-IDENTITY 279 STATUS current 280 DESCRIPTION "The authoritative identifier for the Intel 281 82586 IEEE 802.3 Ethernet LAN Coprocessor." 282 ::= { dot3ChipSetIntel 1 } 284 dot3ChipSetIntel82596 OBJECT-IDENTITY 285 STATUS current 286 DESCRIPTION "The authoritative identifier for the Intel 287 82596 High-Performance 32-Bit Local Area Network 288 Coprocessor." 289 ::= { dot3ChipSetIntel 2 } 291 dot3ChipSetIntel82595 OBJECT-IDENTITY 292 STATUS current 293 DESCRIPTION "The authoritative identifier for the Intel 294 82595 High Integration Ethernet Controller." 295 ::= { dot3ChipSetIntel 3 } 297 dot3ChipSetIntel82557 OBJECT-IDENTITY 298 STATUS current 299 DESCRIPTION "The authoritative identifier for the Intel 300 82557 Fast Ethernet PCI Bus Lan Controller." 301 ::= { dot3ChipSetIntel 4 } 303 dot3ChipSetIntel82558 OBJECT-IDENTITY 304 STATUS current 305 DESCRIPTION "The authoritative identifier for the Intel 306 82558 Fast Ethernet PCI Bus LAN Controller with 307 Integrated PHY." 308 ::= { dot3ChipSetIntel 5 } 310 dot3ChipSetSeeq OBJECT IDENTIFIER ::= { dot3ChipSets 3 } 312 dot3ChipSetSeeq8003 OBJECT-IDENTITY 313 STATUS current 314 DESCRIPTION "The authoritative identifier for the SEEQ 315 8003 chip set." 316 ::= { dot3ChipSetSeeq 1 } 318 dot3ChipSetSeeq80C03 OBJECT-IDENTITY 319 STATUS current 320 DESCRIPTION "The authoritative identifier for the SEEQ 321 80C03 Full-Duplex CMOS Ethernet Data Link 322 Controller (MAC)." 323 ::= { dot3ChipSetSeeq 2 } 325 dot3ChipSetSeeq84C30 OBJECT-IDENTITY 326 STATUS current 327 DESCRIPTION "The authoritative identifier for the SEEQ 328 4-Port 84C30 Full-Duplex CMOS Ethernet 10 329 MBit/Sec Data Link Controller (MAC)." 330 ::= { dot3ChipSetSeeq 3 } 332 dot3ChipSetSeeq8431 OBJECT-IDENTITY 333 STATUS current 334 DESCRIPTION "The authoritative identifier for the SEEQ 335 4-Port 8431 Full-Duplex CMOS Ethernet 10 336 MBit/Sec Data Link Controller (MAC)." 337 ::= { dot3ChipSetSeeq 4 } 339 dot3ChipSetSeeq80C300 OBJECT-IDENTITY 340 STATUS current 341 DESCRIPTION "The authoritative identifier for the SEEQ 342 80C300 Full-Duplex CMOS Ethernet 10/100 343 Mbit/Sec Data Link Controller (MAC)." 344 ::= { dot3ChipSetSeeq 5 } 346 dot3ChipSetSeeq84C300 OBJECT-IDENTITY 347 STATUS current 348 DESCRIPTION "The authoritative identifier for the SEEQ 349 4-Port 84C300 Fast Ethernet Controller (MAC)." 350 ::= { dot3ChipSetSeeq 6 } 352 dot3ChipSetSeeq84301 OBJECT-IDENTITY 353 STATUS current 354 DESCRIPTION "The authoritative identifier for the SEEQ 355 4-Port 84301 Fast Ethernet Controller (MAC)." 356 ::= { dot3ChipSetSeeq 7 } 358 dot3ChipSetSeeq84302 OBJECT-IDENTITY 359 STATUS current 360 DESCRIPTION "The authoritative identifier for the SEEQ 361 4-Port 84302 Fast Ethernet Controller (MAC)." 362 ::= { dot3ChipSetSeeq 8 } 364 dot3ChipSetSeeq8100 OBJECT-IDENTITY 365 STATUS current 366 DESCRIPTION "The authoritative identifier for the SEEQ 367 8100 Gigabit Ethernet Controller (MAC & PCS)." 368 ::= { dot3ChipSetSeeq 9 } 370 dot3ChipSetNational OBJECT IDENTIFIER ::= { dot3ChipSets 4 } 372 dot3ChipSetNational8390 OBJECT-IDENTITY 373 STATUS current 374 DESCRIPTION "The authoritative identifier for the National 375 Semiconductor DP8390 Network Interface 376 Controller." 377 ::= { dot3ChipSetNational 1 } 379 dot3ChipSetNationalSonic OBJECT-IDENTITY 380 STATUS current 381 DESCRIPTION "The authoritative identifier for the National 382 Semiconductor DP83932 Systems-Oriented Network 383 Interface Controller (SONIC)." 384 ::= { dot3ChipSetNational 2 } 386 dot3ChipSetNational83901 OBJECT-IDENTITY 387 STATUS current 388 DESCRIPTION "The authoritative identifier for the National 389 Semiconductor DP83901 Serial Network Interface 390 Controller (SNIC)." 391 ::= { dot3ChipSetNational 3 } 393 dot3ChipSetNational83902 OBJECT-IDENTITY 394 STATUS current 395 DESCRIPTION "The authoritative identifier for the National 396 Semiconductor DP83902 Serial Network Interface 397 Controller for Twisted Pair (ST-NIC)." 398 ::= { dot3ChipSetNational 4 } 400 dot3ChipSetNational83905 OBJECT-IDENTITY 401 STATUS current 402 DESCRIPTION "The authoritative identifier for the National 403 Semiconductor DP83905 AT Local Area Network 404 Twisted-Pair Interface (AT/LANTIC)." 405 ::= { dot3ChipSetNational 5 } 407 dot3ChipSetNational83907 OBJECT-IDENTITY 408 STATUS current 409 DESCRIPTION "The authoritative identifier for the National 410 Semiconductor DP83907 AT Twisted-Pair Enhanced 411 Coaxial Network Interface Controller 412 (AT/LANTIC II)." 413 ::= { dot3ChipSetNational 6 } 415 dot3ChipSetNational83916 OBJECT-IDENTITY 416 STATUS current 417 DESCRIPTION "The authoritative identifier for the National 418 Semiconductor DP83916 Systems-Oriented Network 419 Interface Controller (SONIC-16)." 420 ::= { dot3ChipSetNational 7 } 422 dot3ChipSetNational83934 OBJECT-IDENTITY 423 STATUS current 424 DESCRIPTION "The authoritative identifier for the National 425 Semiconductor DP83934 Systems-Oriented Network 426 Interface Controller with Twisted Pair Interface 427 (SONIC-T)." 428 ::= { dot3ChipSetNational 8 } 430 dot3ChipSetNational83936 OBJECT-IDENTITY 431 STATUS current 432 DESCRIPTION "The authoritative identifier for the National 433 Semiconductor DP83936AVUL Full-Duplex Systems- 434 Oriented Network Interface Controller with 435 Twisted Pair Interface (SONIC-T)." 436 ::= { dot3ChipSetNational 9 } 438 dot3ChipSetFujitsu OBJECT IDENTIFIER ::= { dot3ChipSets 5 } 440 dot3ChipSetFujitsu86950 OBJECT-IDENTITY 441 STATUS current 442 DESCRIPTION "The authoritative identifier for the Fujitsu 443 86950 chip." 444 ::= { dot3ChipSetFujitsu 1 } 446 dot3ChipSetFujitsu86960 OBJECT-IDENTITY 447 STATUS current 448 DESCRIPTION "The authoritative identifier for the Fujitsu 449 MB86960 Network Interface Controller with 450 Encoder/Decoder (NICE)." 451 ::= { dot3ChipSetFujitsu 2 } 453 dot3ChipSetFujitsu86964 OBJECT-IDENTITY 454 STATUS current 455 DESCRIPTION "The authoritative identifier for the Fujitsu 456 MB86964 Ethernet Controller with 10BASE-T 457 Tranceiver." 458 ::= { dot3ChipSetFujitsu 3 } 460 dot3ChipSetFujitsu86965A OBJECT-IDENTITY 461 STATUS current 462 DESCRIPTION "The authoritative identifier for the Fujitsu 463 MB86965A EtherCoupler Single-Chip Ethernet 464 Controller." 465 ::= { dot3ChipSetFujitsu 4 } 467 dot3ChipSetFujitsu86965B OBJECT-IDENTITY 468 STATUS current 469 DESCRIPTION "The authoritative identifier for the Fujitsu 470 MB86965B EtherCoupler Single-Chip Ethernet 471 Controller (supports full-duplex)." 472 ::= { dot3ChipSetFujitsu 5 } 474 dot3ChipSetDigital OBJECT IDENTIFIER ::= { dot3ChipSets 6 } 476 dot3ChipSetDigitalDC21040 OBJECT-IDENTITY 477 STATUS current 478 DESCRIPTION "The authoritative identifier for the Digital 479 Semiconductor DC21040 chip." 480 ::= { dot3ChipSetDigital 1 } 482 dot3ChipSetDigital21041 OBJECT-IDENTITY 483 STATUS current 484 DESCRIPTION "The authoritative identifier for the Digital 485 Semiconductor 21041 PCI Ethernet LAN 486 Controller." 487 ::= { dot3ChipSetDigital 2 } 489 dot3ChipSetDigital21140 OBJECT-IDENTITY 490 STATUS current 491 DESCRIPTION "The authoritative identifier for the Digital 492 Semiconductor 21140 PCI Fast Ethernet LAN 493 Controller." 494 ::= { dot3ChipSetDigital 3 } 496 dot3ChipSetDigital21143 OBJECT-IDENTITY 497 STATUS current 498 DESCRIPTION "The authoritative identifier for the Digital 499 Semiconductor 21143 PCI/CardBus 10/100-Mb/s 500 Ethernet LAN Controller." 501 ::= { dot3ChipSetDigital 4 } 503 dot3ChipSetDigital21340 OBJECT-IDENTITY 504 STATUS current 505 DESCRIPTION "The authoritative identifier for the Digital 506 Semiconductor 21340 10/100-MB/s managed buffered 507 port switch." 508 ::= { dot3ChipSetDigital 5 } 510 dot3ChipSetDigital21440 OBJECT-IDENTITY 511 STATUS current 512 DESCRIPTION "The authoritative identifier for the Digital 513 Semiconductor 21440 Multiport 10/100Mbps 514 Ethernet Controller." 515 ::= { dot3ChipSetDigital 6 } 517 dot3ChipSetDigital21540 OBJECT-IDENTITY 518 STATUS current 519 DESCRIPTION "The authoritative identifier for the Digital 520 Semiconductor 21540 PCI/CardBus Ethernet LAN 521 Controller with Modem Interface." 522 ::= { dot3ChipSetDigital 7 } 524 dot3ChipSetTI OBJECT IDENTIFIER ::= { dot3ChipSets 7 } 526 dot3ChipSetTIE100 OBJECT-IDENTITY 527 STATUS current 528 DESCRIPTION "The authoritative identifier for the Texas 529 Instruments TNETE100 ThunderLAN PCI Fast 530 Ethernet Controller." 531 ::= { dot3ChipSetTI 1 } 533 dot3ChipSetTIE110 OBJECT-IDENTITY 534 STATUS current 535 DESCRIPTION "The authoritative identifier for the Texas 536 Instruments TNETE110 ThunderLAN PCI 10BASE-T 537 Ethernet Adapter." 538 ::= { dot3ChipSetTI 2 } 540 dot3ChipSetTIX3100 OBJECT-IDENTITY 541 STATUS current 542 DESCRIPTION "The authoritative identifier for the Texas 543 Instruments TNETX3100 Desktop ThunderSWITCH 544 8/2." 545 ::= { dot3ChipSetTI 3 } 547 dot3ChipSetTIX3150 OBJECT-IDENTITY 548 STATUS current 549 DESCRIPTION "The authoritative identifier for the Texas 550 Instruments TNETX3150 ThunderSWITCH 12/3." 551 ::= { dot3ChipSetTI 4 } 553 dot3ChipSetTIX3270 OBJECT-IDENTITY 554 STATUS current 555 DESCRIPTION "The authoritative identifier for the Texas 556 Instruments TNETX3270 ThunderSWITCH 24/3." 557 ::= { dot3ChipSetTI 5 } 559 dot3ChipSetToshiba OBJECT IDENTIFIER ::= { dot3ChipSets 8 } 561 dot3ChipSetToshibaTC35815F OBJECT-IDENTITY 562 STATUS current 563 DESCRIPTION "The authoritative identifier for the Toshiba 564 TC35815F PCI-Based 100/10Mbps Ethernet 565 Controller." 566 ::= { dot3ChipSetToshiba 1 } 568 dot3ChipSetLucent OBJECT IDENTIFIER ::= { dot3ChipSets 9 } 570 dot3ChipSetLucentATT1MX10 OBJECT-IDENTITY 571 STATUS current 572 DESCRIPTION "The authoritative identifier for the Lucent 573 Technologies ATT1MX10 (Spinnaker) Quad MAC and 574 Tranceiver for Ethernet Frame Switching." 576 ::= { dot3ChipSetLucent 1 } 578 dot3ChipSetLucentLUC3M08 OBJECT-IDENTITY 579 STATUS current 580 DESCRIPTION "The authoritative identifier for the Lucent 581 Technologies LUC3M08 Eight Ethernet MACs for 582 10/100 Mbits/s Frame Switching." 583 ::= { dot3ChipSetLucent 2 } 585 dot3ChipSetGalileo OBJECT IDENTIFIER ::= { dot3ChipSets 10 } 587 dot3ChipSetGalileoGT48001 OBJECT-IDENTITY 588 STATUS current 589 DESCRIPTION "The authoritative identifier for the Galileo 590 Technology GT-48001A Switched Ethernet 591 Controller." 592 ::= { dot3ChipSetGalileo 1 } 594 dot3ChipSetGalileoGT48002 OBJECT-IDENTITY 595 STATUS current 596 DESCRIPTION "The authoritative identifier for the Galileo 597 Technology GT-48002A Switched Fast Ethernet 598 Controller." 599 ::= { dot3ChipSetGalileo 2 } 601 dot3ChipSetGalileoGT48004 OBJECT-IDENTITY 602 STATUS current 603 DESCRIPTION "The authoritative identifier for the Galileo 604 Technology GT-48004A Four Port Fast Ethernet 605 Switch for Multiport 10/100BASE-X Systems." 606 ::= { dot3ChipSetGalileo 3 } 608 dot3ChipSetGalileoGT48207 OBJECT-IDENTITY 609 STATUS current 610 DESCRIPTION "The authoritative identifier for the Galileo 611 Technology GT-48207 Low-Cost 10 Port Switched 612 Ethernet Controller for 10+10/100BASE-X." 613 ::= { dot3ChipSetGalileo 4 } 615 dot3ChipSetGalileoGT48208 OBJECT-IDENTITY 616 STATUS current 617 DESCRIPTION "The authoritative identifier for the Galileo 618 Technology GT-48208 Advanced 10 Port Switched 619 Ethernet Controller for 10+10/100BASE-X." 620 ::= { dot3ChipSetGalileo 5 } 622 dot3ChipSetGalileoGT48212 OBJECT-IDENTITY 623 STATUS current 624 DESCRIPTION "The authoritative identifier for the Galileo 625 Technology GT-48212 Advanced 14 Port Switched 626 Ethernet Controller for 10+10/100BASE-X." 627 ::= { dot3ChipSetGalileo 6 } 629 dot3ChipSetJato OBJECT IDENTIFIER ::= { dot3ChipSets 11 } 631 dot3ChipSetJatoJT1001 OBJECT-IDENTITY 632 STATUS current 633 DESCRIPTION "The authoritative identifier for the Jato 634 Technologies JT1001 GigEMAC Server 635 10/100/1000Mbps Ethernet Controller with PCI 636 interface." 637 ::= { dot3ChipSetJato 1 } 639 dot3ChipSetXaQti OBJECT IDENTIFIER ::= { dot3ChipSets 12 } 641 dot3ChipSetXaQtiXQ11800FP OBJECT-IDENTITY 642 STATUS current 643 DESCRIPTION "The authoritative identifier for the XaQTI 644 XQ11800FP XMAC II Gigabit Ethernet Media Access 645 Controller." 646 ::= { dot3ChipSetXaQti 1 } 648 dot3ChipSetXaQtiXQ18110FP OBJECT-IDENTITY 649 STATUS current 650 DESCRIPTION "The authoritative identifier for the XaQTI 651 XQ18110FP GigaPower Protocol Accelerator." 652 ::= { dot3ChipSetXaQti 2 } 654 END 656 4. Intellectual Property 658 The IETF takes no position regarding the validity or scope of any 659 intellectual property or other rights that might be claimed to 660 pertain to the implementation or use of the technology described in 661 this document or the extent to which any license under such rights 662 might or might not be available; neither does it represent that it 663 has made any effort to identify any such rights. Information on the 664 IETF's procedures with respect to rights in standards-track and 665 standards-related documentation can be found in BCP-11. Copies of 666 claims of rights made available for publication and any assurances of 667 licenses to be made available, or the result of an attempt made to 668 obtain a general license or permission for the use of such 669 proprietary rights by implementors or users of this specification can 670 be obtained from the IETF Secretariat. 672 The IETF invites any interested party to bring to its attention any 673 copyrights, patents or patent applications, or other proprietary 674 rights which may cover technology that may be required to practice 675 this standard. Please address the information to the IETF Executive 676 Director. 678 5. Acknowledgements 680 This document was produced by the Ethernet Interfaces and Hub MIB 681 Working Group. 683 6. References 685 [1] Harrington, D., Presuhn, R., and B. Wijnen, "An Architecture for 686 Describing SNMP Management Frameworks", RFC 2571, Cabletron 687 Systems, Inc., BMC Software, Inc., IBM T. J. Watson Research, 688 May 1999 690 [2] Rose, M., and K. McCloghrie, "Structure and Identification of 691 Management Information for TCP/IP-based Internets", RFC 1155, 692 STD 16, Performance Systems International, Hughes LAN Systems, 693 May 1990 695 [3] Rose, M., and K. McCloghrie, "Concise MIB Definitions", RFC 696 1212, STD 16, Performance Systems International, Hughes LAN 697 Systems, March 1991 699 [4] M. Rose, "A Convention for Defining Traps for use with the 700 SNMP", RFC 1215, Performance Systems International, March 1991 702 [5] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, 703 M., and S Waldbusser, "Structure of Management Information 704 Version 2 (SMIv2)", RFC 2578, STD 58, Cisco Systems, SNMPInfo, 705 TU Braunschweig, SNMP Research, First Virtual Holdings, 706 International Network Services, April 1999. 708 [6] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, 709 M., and S Waldbusser, "Textual Conventions for SMIv2", RFC 2579, 710 STD 58, Cisco Systems, SNMPInfo, TU Braunschweig, SNMP Research, 711 First Virtual Holdings, International Network Services, 712 April 1999. 714 [7] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, 715 M., and S Waldbusser, "Conformance Statements for SMIv2", RFC 716 2580, STD 58, Cisco Systems, SNMPInfo, TU Braunschweig, SNMP 717 Research, First Virtual Holdings, International Network 718 Services, April 1999. 720 [8] Case, J., Fedor, M., Schoffstall, M., and J. Davin, "Simple 721 Network Management Protocol", STD 15, RFC 1157, SNMP Research, 722 Performance Systems International, Performance Systems 723 International, MIT Laboratory for Computer Science, May 1990. 725 [9] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 726 "Introduction to Community-based SNMPv2", RFC 1901, SNMP 727 Research, Inc., Cisco Systems, Inc., Dover Beach Consulting, 728 Inc., International Network Services, January 1996. 730 [10] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 731 "Transport Mappings for Version 2 of the Simple Network 732 Management Protocol (SNMPv2)", RFC 1906, SNMP Research, Inc., 733 Cisco Systems, Inc., Dover Beach Consulting, Inc., International 734 Network Services, January 1996. 736 [11] Case, J., Harrington D., Presuhn R., and B. Wijnen, "Message 737 Processing and Dispatching for the Simple Network Management 738 Protocol (SNMP)", RFC 2572, SNMP Research, Inc., Cabletron 739 Systems, Inc., BMC Software, Inc., IBM T. J. Watson Research, 740 May 1999. 742 [12] Blumenthal, U., and B. Wijnen, "User-based Security Model (USM) 743 for version 3 of the Simple Network Management Protocol 744 (SNMPv3)", RFC 2574, IBM T. J. Watson Research, May 1999. 746 [13] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Protocol 747 Operations for Version 2 of the Simple Network Management 748 Protocol (SNMPv2)", RFC 1905, SNMP Research, Inc., Cisco 749 Systems, Inc., Dover Beach Consulting, Inc., International 750 Network Services, January 1996. 752 [14] Levi, D., Meyer, P., and B. Stewart, "SNMPv3 Applications", RFC 753 2573, SNMP Research, Inc., Secure Computing Corporation, Cisco 754 Systems, May 1999 756 [15] Wijnen, B., Presuhn, R., and K. McCloghrie, "View-based Access 757 Control Model (VACM) for the Simple Network Management Protocol 758 (SNMP)", RFC 2575, IBM T. J. Watson Research, BMC Software, 759 Inc., Cisco Systems, Inc., May 1999 761 [16] Flick, J., and J. Johnson, "Definitions of Managed Objects for 762 the Ethernet-like Interface Types", work in progress, 763 draft-ietf-hubmib-etherif-mib-v2-02.txt, Hewlett-Packard 764 Company, RedBack Networks, January, 1999. 766 7. Security Considerations 768 There are no management objects actually defined in this MIB module. 769 It merely contains a list of OBJECT IDENTIFIER values for use in 770 other MIB modules. As such, it does not, by itself, have any effect 771 on the security of the Internet. 773 The values in this module are expected to be used only for backwards 774 compatability with the deprecated dot3StatsEtherChipSet object in the 775 EtherLike-MIB [16]. That object may be considered sensitive in some 776 environments, since it would allow an intruder to obtain information 777 about which vendor's equipment is in use on the network. 779 Therefore, it may be important in some environments, where the 780 dot3StatsEtherChipSet object is implemented for backwards 781 compatability, to control read access to that object and possibly to 782 even encrypt the values of that object when sending it over the 783 network via SNMP. Not all versions of SNMP provide features for such 784 a secure environment. 786 SNMPv1 by itself is such an insecure environment. Even if the 787 network itself is secure (for example by using IPSec), even then, 788 there is no control as to who on the secure network is allowed to 789 access and GET (read) the objects in this MIB. 791 It is recommended that the implementors consider the security 792 features as provided by the SNMPv3 framework. Specifically, the use 793 of the User-based Security Model RFC 2274 [12] and the View-based 794 Access Control Model RFC 2275 [15] is recommended. 796 It is then a customer/user responsibility to ensure that the SNMP 797 entity giving access to a managed object whose values are defined in 798 this MIB, is properly configured to give access to those objects only 799 to those principals (users) that have legitimate rights to access 800 them. 802 8. Author's Address 804 John Flick 805 Hewlett-Packard Company 806 8000 Foothills Blvd. M/S 5557 807 Roseville, CA 95747-5557 809 Phone: +1 916 785 4018 810 Email: johnf@rose.hp.com 812 9. Full Copyright Statement 813 This document and translations of it may be copied and furnished to 814 others, and derivative works that comment on or otherwise explain it 815 or assist in its implementation may be prepared, copied, published 816 and distributed, in whole or in part, without restriction of any 817 kind, provided that the above copyright notice and this paragraph are 818 included on all such copies and derivative works. However, this 819 document itself may not be modified in any way, such as by removing 820 the copyright notice or references to the Internet Society or other 821 Internet organizations, except as needed for the purpose of 822 developing Internet standards in which case the procedures for 823 copyrights defined in the Internet Standards process must be 824 followed, or as required to translate it into languages other than 825 English. 827 The limited permissions granted above are perpetual and will not be 828 revoked by the Internet Society or its successors or assigns. 830 This document and the information contained herein is provided on an 831 "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING 832 TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING 833 BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION 834 HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF 835 MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.