Ethernet RFCs

Ethernet and IEEE 802.3 RFCs

Ethernet was a remarkable invention, not so much technically (though
there is no question that technically Ethernet is remarkable), but
rather because it was conceived and executed as an industry
standard. While vendors were building their own proprietary LAN
technologies, hoping to lock customers into each vendors’ own system,
Bob Metcalfe et al were building a technology that everyone could
use. The difference is that proprietary networks tend to not grow very
fast: you can only grow new applications and devices as fast as your
vendor (or its licensees) can introduce them. If you use an open
standard, such as Ethenet (or IP, for that matter), anyone can come up
with a better mousetrap, a more efficient NIC, or a better hub. And
customers can buy from anyone (meaning they can second-source their
networks if they want to) with confidence.

Ethernet was being developed about the same time as the early versions
of the Internet Protocol, and the two technologies have both achieved
extraordinary penetration into today’s computing and networking
markets. These RFCs provide a good introduction to the way Ethernet
and 802.3 networks work with IP; you can also check the href="http://www.ieee.org" TARGET="books">IEEE though you’ll have
to pay them to see the relevant standards for 802.3 networking.

Number Title More Info (Obs & Upd) Status
RFC0826 Ethernet Address Resolution Protocol    STANDARD
RFC0894 Standard for the transmission of IP datagrams over Ethernet networks    STANDARD
RFC0895 Standard for the transmission of IP datagrams over experimental Ethernet networks    STANDARD
RFC0948 Two methods for the transmission of IP datagrams over IEEE 802.3 networks  Obsoleted by RFC1042, STD0043  UNKNOWN
RFC1029 More fault tolerant approach to address resolution for a Multi-LAN system of Ethernets    UNKNOWN
RFC1089 SNMP over Ethernet    UNKNOWN
RFC1284 Definitions of Managed Objects for the Ethernet-like Interface Types  Obsoleted by RFC1398  PROPOSED STANDARD
RFC1368 Definition of Managed Objects for IEEE 802.3 Repeater Devices  Obsoleted by RFC1516  PROPOSED STANDARD
RFC1369 Implementation Notes and Experience for the Internet Ethernet MIB    PROPOSED STANDARD
RFC1398 Definitions of Managed Objects for the Ethernet-Like Interface Types  Obsoletes RFC1284, Obsoleted by RFC1643, RFC1623  DRAFT STANDARD
RFC1515 Definitions of Managed Objects for IEEE 802.3 Medium Attachment Units (MAUs)    PROPOSED STANDARD
RFC1516 Definitions of Managed Objects for IEEE 802.3 Repeater Devices  Obsoletes RFC1368, Obsoleted by RFC2108  DRAFT STANDARD
RFC1623 Definitions of Managed Objects for the Ethernet-like Interface Types  Obsoletes RFC1398, Obsoleted by RFC1643, STD0050  STANDARD
RFC1643 Definitions of Managed Objects for the Ethernet-like Interface Types  Obsoletes RFC1623, RFC1398  STANDARD
RFC1650 Definitions of Managed Objects for the Ethernet-like Interface Types using SMIv2  Obsoleted by RFC2358  PROPOSED STANDARD
RFC1972 A Method for the Transmission of IPv6 Packets over Ethernet Networks  Obsoleted by RFC2464  PROPOSED STANDARD
RFC2108 Definitions of Managed Objects for IEEE 802.3 Repeater Devices using SMIv2  Obsoletes RFC1516  PROPOSED STANDARD
RFC2239 Definitions of Managed Objects for IEEE 802.3 Medium Attachment Units (MAUs) using SMIv2  Obsoleted by RFC2668  PROPOSED STANDARD
RFC2358 Definitions of Managed Objects for the Ethernet-like Interface Types  Obsoletes RFC1650, Obsoleted by RFC2665  PROPOSED STANDARD
RFC2464 Transmission of IPv6 Packets over Ethernet Networks  Obsoletes RFC1972  PROPOSED STANDARD
RFC2516 Method for Transmitting PPP Over Ethernet (PPPoE)    INFORMATIONAL
RFC2665 Definitions of Managed Objects for the Ethernet-like Interface Types  Obsoletes RFC2358  PROPOSED STANDARD
RFC2666 Definitions of Object Identifiers for Identifying Ethernet Chip Sets    INFORMATIONAL
RFC2668 Definitions of Managed Objects for IEEE 802.3 Medium Attachment Units (MAUs)  Obsoletes RFC2239  PROPOSED STANDARD

Leave a Reply

Your email address will not be published. Required fields are marked *

*

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>