As per Relevance of the word crawford, we have this rfc below:
Network Working Group M.
Request for Comments: 1972
Category: Standards Track August 1996
A Method for the Transmission of IPv6 Packets over Ethernet
Status of this
This document specifies an Internet standards track protocol for
Internet community, and requests discussion and suggestions
improvements. Please refer to the current edition of the "
Official Protocol Standards" (STD 1) for the standardization
and status of this protocol. Distribution of this memo is unlimited
This memo specifies the frame format for transmission of IPv6 [IPV6]
packets and the method of forming IPv6 link-local addresses
Ethernet networks. It also specifies the content of
Source/Target Link-layer Address option used the the
Solicitation, Router Advertisement, Neighbor Solicitation,
Neighbor Advertisement messages described in [DISC], when
messages are transmitted on an Ethernet
Maximum Transmission
The default MTU size for IPv6 packets on an Ethernet is 1500 octets
This size may be reduced by a Router Advertisement [DISC]
an MTU option which specifies a smaller MTU, or by
configuration of each node. If a Router Advertisement is
with an MTU option specifying an MTU larger than 1500, or larger
a manually configured value less than 1500, that MTU option must
ignored
Frame
IPv6 packets are transmitted in standard Ethernet frames.
ethernet header contains the Destination and Source
addresses and the ethernet type code, which must contain the
86DD hexadecimal. The data field contains the IPv6 header
immediately by the payload, and possibly padding octets to meet
minimum frame size for Ethernet
Crawford Standards Track [Page 1]
RFC 1972 Transmission of IPv6 Packets Over Ethernet August 1996
+-------+-------+-------+-------+-------+-------+ ^
| Destination Ethernet address | |
+-------+-------+-------+-------+-------+-------+
| Source Ethernet address |
+-------+-------+-------+-------+-------+-------+ |
| 86 DD |
+-------+-------+-------+-------+-------+------+------+
| IPv6 header and payload ... /
+-------+-------+-------+-------+-------+------+------+
Stateless Autoconfiguration and Link-Local
The address token [CONF] for an Ethernet interface is the interface'
built-in 48-bit IEEE 802 address, in canonical bit order and with
octets in the same order in which they would appear in the header
an ethernet frame. (The individual/group bit is in the first
and the OUI is in the first three octets.) A different MAC
set manually or by software should not be used as the address token
An IPv6 address prefix used for stateless autoconfiguration of
ethernet interface must be 80 bits in length
The IPv6 Link-local address [AARCH] for an Ethernet interface
formed by appending the interface's IEEE 802 address to the 80-
prefix FE80::.
+-------+-------+-------+-------+-------+-------+------+------+
| FE 80 00 00 00 00 00 00 |
+-------+-------+-------+-------+-------+-------+------+------+
| 00 00 | Ethernet Address |
+-------+-------+-------+-------+-------+-------+------+------+
Address Mapping --
The procedure for mapping IPv6 addresses into Ethernet link-
addresses is described in [DISC]. The Source/Target Link-
Address option has the following form when the link layer
Ethernet
+-------+-------+-------+-------+-------+-------+-------+-------+
| Type |Length | Ethernet Address |
+-------+-------+-------+-------+-------+-------+-------+-------+
Crawford Standards Track [Page 2]
RFC 1972 Transmission of IPv6 Packets Over Ethernet August 1996
Option fields
Type 1 for Source Link-layer address
2 for Target Link-layer address
Length 1 (in units of 8 octets).
Ethernet
The 48 bit Ethernet IEEE 802 address, in canonical
order. This is the address the interface currently
to, and may be different from the built-in address used
the address token
Address Mapping --
An IPv6 packet with a multicast destination address DST
transmitted to the Ethernet multicast address whose first two
are the value 3333 hexadecimal and whose last four octets are
last four octets of DST, ordered from more to least significant
+-------+-------+-------+-------+-------+-------+
| 33 | 33 | DST13 | DST14 | DST15 | DST16 |
+-------+-------+-------+-------+-------+-------+
Security
Security issues are not discussed in this memo
[AARCH] Hinden, R., and S. Deering, "IP Version 6
Architecture", RFC 1884, December 1995.
[CONF] Thomson, S., and T. Narten, "IPv6 Stateless
Autoconfiguration", RFC 1971, August 1996.
[DISC] Narten, T., Nordmark, E., and W. Simpson, "Neighbor
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.
Crawford Standards Track [Page 3]
RFC 1972 Transmission of IPv6 Packets Over Ethernet August 1996
Author's
Matt
Fermilab MS 368
PO Box 500
Batavia, IL 60510
Phone: +1 708 840-3461
EMail: crawdad@fnal.
Crawford Standards Track [Page 4]
if you see any problems within the linking, don't worry be happy,
this is version 0.1 of the Relevance System and you gotta expect some crappy subroutines sometimes,
just be content we did not write this in Java, which would have made this "bigger and better" HAHAHHA.
RFC documents can be found at I.E.T.F.
Relevance System Copyright © 2002 Spectrum WorldResearch
other technical nosh by ServerMasters Corporation
collaboration of BobX
