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