RFC 1972 PROPOSED STANDARD IPV6 · ETHERNET

IPv6 over Ethernet: A Method for the Transmission of IPv6 Packets over Ethernet Networks

Sending IPv6 messages across Ethernet cables

On rfc-editor.org ↗
PUBLISHED
August 1996
AUTHORS
M. Crawford
STREAM
IETF
OBSOLETED BY
RFC 2464 — IPv6 over Ethernet
DEFAULT MTU
1500 octets
ETHERNET TYPE CODE
86DD hexadecimal
LINK-LOCAL PREFIX
FE80:0000:0000:0000
MULTICAST PREFIX
3333 hexadecimal
DOI
10.17487/RFC1972

RFC text

Contents
Original text · RFC Editor View on rfc-editor.org ↗
Network Working Group                                        M. Crawford
Request for Comments: 1972                                      Fermilab
Category: Standards Track                                    August 1996



  A Method for the Transmission of IPv6 Packets over Ethernet Networks

Status of this Memo

   This document specifies an Internet standards track protocol for the
   Internet community, and requests discussion and suggestions for
   improvements.  Please refer to the current edition of the "Internet
   Official Protocol Standards" (STD 1) for the standardization state
   and status of this protocol.  Distribution of this memo is unlimited.

Introduction

   This memo specifies the frame format for transmission of IPv6 [IPV6]
   packets and the method of forming IPv6 link-local addresses on
   Ethernet networks.  It also specifies the content of the
   Source/Target Link-layer Address option used the the Router
   Solicitation, Router Advertisement, Neighbor Solicitation, and
   Neighbor Advertisement messages described in [DISC], when those
   messages are transmitted on an Ethernet.

Maximum Transmission Unit

   The default MTU size for IPv6 packets on an Ethernet is 1500 octets.
   This size may be reduced by a Router Advertisement [DISC] containing
   an MTU option which specifies a smaller MTU, or by manual
   configuration of each node.  If a Router Advertisement is received
   with an MTU option specifying an MTU larger than 1500, or larger than
   a manually configured value less than 1500, that MTU option must be
   ignored.

Frame Format

   IPv6 packets are transmitted in standard Ethernet frames.  The
   ethernet header contains the Destination and Source ethernet
   addresses and the ethernet type code, which must contain the value
   86DD hexadecimal.  The data field contains the IPv6 header followed
   immediately by the payload, and possibly padding octets to meet the
   minimum frame size for Ethernet.

       +-------+-------+-------+-------+-------+-------+       ^
       |          Destination Ethernet address         |       |
       +-------+-------+-------+-------+-------+-------+    ethernet
       |            Source Ethernet address            |     header
       +-------+-------+-------+-------+-------+-------+       |
       |  86      DD   |                                       v
       +-------+-------+-------+-------+-------+------+------+
       |            IPv6 header and payload ...              /
       +-------+-------+-------+-------+-------+------+------+

Stateless Autoconfiguration and Link-Local Addresses

   The address token [CONF] for an Ethernet interface is the interface's
   built-in 48-bit IEEE 802 address, in canonical bit order and with the
   octets in the same order in which they would appear in the header of
   an ethernet frame.  (The individual/group bit is in the first octet
   and the OUI is in the first three octets.) A different MAC address
   set manually or by software should not be used as the address token.

   An IPv6 address prefix used for stateless autoconfiguration of an
   ethernet interface must be 80 bits in length.

   The IPv6 Link-local address [AARCH] for an Ethernet interface is
   formed by appending the interface's IEEE 802 address to the 80-bit
   prefix FE80::.

      +-------+-------+-------+-------+-------+-------+------+------+
      |  FE      80      00      00      00      00      00     00  |
      +-------+-------+-------+-------+-------+-------+------+------+
      |  00      00   |               Ethernet Address              |
      +-------+-------+-------+-------+-------+-------+------+------+

Address Mapping -- Unicast

   The procedure for mapping IPv6 addresses into Ethernet link-layer
   addresses is described in [DISC].  The Source/Target Link-layer
   Address option has the following form when the link layer is
   Ethernet.

     +-------+-------+-------+-------+-------+-------+-------+-------+
     | Type  |Length |               Ethernet Address                |
     +-------+-------+-------+-------+-------+-------+-------+-------+

Option fields:


Type        1 for Source Link-layer address.
            2 for Target Link-layer address.


Length      1 (in units of 8 octets).


Ethernet Address
            The 48 bit Ethernet IEEE 802 address, in canonical bit
            order.  This is the address the interface currently responds
            to, and may be different from the built-in address used as
            the address token.

Address Mapping -- Multicast

   An IPv6 packet with a multicast destination address DST is
   transmitted to the Ethernet multicast address whose first two octets
   are the value 3333 hexadecimal and whose last four octets are the
   last four octets of DST, ordered from more to least significant.

             +-------+-------+-------+-------+-------+-------+
             |   33  |   33  | DST13 | DST14 | DST15 | DST16 |
             +-------+-------+-------+-------+-------+-------+

Security Considerations

   Security issues are not discussed in this memo.

References

   [AARCH] Hinden, R., and S. Deering, "IP Version 6 Addressing
           Architecture", RFC 1884, December 1995.

   [CONF] Thomson, S., and T. Narten, "IPv6 Stateless Address
          Autoconfiguration", RFC 1971, August 1996.

   [DISC] Narten, T., Nordmark, E., and W. Simpson, "Neighbor Discovery
          for IP Version 6 (IPv6)", RFC 1970, August 1996.

   [IPV6] Deering, S., and R. Hinden, "Internet Protocol, Version 6
          (IPv6) Specification", RFC 1883, December 1995.

Author's Address

   Matt Crawford
   Fermilab MS 368
   PO Box 500
   Batavia, IL 60510
   USA

   Phone: +1 708 840-3461
   EMail: crawdad@fnal.gov

AI ELI5

On this page
PROBLEMIPv6 is a new version of IP, but networks use Ethernet to physically send packets. The standard for connecting IPv6 to Ethernet was needed.
MECHANISMRFC 1972 specifies that IPv6 packets go into Ethernet frames with type code 86DD hexadecimal, and link-local addresses are formed from the Ethernet MAC address and a standard prefix.
WHY IT FADEDIt was replaced by RFC 2464, which provided equivalent functionality.

§1Introduction

IPv6 is the next version of the Internet Protocol, offering much larger address space than IPv4. RFC 1972 specifies how IPv6 packets are sent across Ethernet networks, including the frame format, the maximum transmission unit size, and how to form IPv6 addresses on Ethernet interfaces.

The document also specifies how IPv6 addresses are mapped to Ethernet addresses for both unicast (one-to-one) and multicast (one-to-many) communication, and defines the format of the Source/Target Link-layer Address options used in IPv6 Neighbor Discovery messages on Ethernet.

This memo is the rulebook for putting IPv6 packets into Ethernet frames and creating temporary addresses that work on the local network.

§2Frame Format and MTU Size

IPv6 packets are transmitted in standard Ethernet frames. The Ethernet header contains the source and destination Ethernet addresses and the type code, which must be set to 86DD hexadecimal to indicate IPv6. The data field contains the IPv6 header followed immediately by its payload, and may include padding octets to meet Ethernet minimum frame size.

The default maximum transmission unit (MTU) size for IPv6 packets on Ethernet is 1500 octets. This size can be reduced by a Router Advertisement containing an MTU option, or manually configured on each node. Larger MTU values in Router Advertisements must be ignored.

IPv6 packets go in Ethernet envelopes with a special number saying what is inside. The packet can be up to 1500 bytes, but smaller sizes are allowed if the router says so.

§3Address Mapping and Link-Local Addresses

Link-local addresses are formed by combining the standard 80-bit prefix FE80:0000:0000:0000 with the 48-bit IEEE 802 Ethernet address of the interface. This allows nodes to automatically create usable addresses for local network communication without central administration.

For unicast communication (sending to a single Ethernet address), the Source and Target Link-layer Address options in Neighbor Discovery messages contain the 48-bit Ethernet address. For multicast, IPv6 multicast addresses are mapped to Ethernet multicast addresses: the first two octets are 3333 hexadecimal, followed by the last four octets of the IPv6 multicast address.

Computers create their own temporary addresses by mixing a special pattern with their Ethernet address. When sending to multiple computers at once, a special multicast address starting with 33 33 tells Ethernet which computers should hear the message.

§4References