< draft-ietf-ipngwg-trans-ethernet-02.txt		draft-ietf-ipngwg-trans-ethernet-03.txt >
	IPng Working Group Matt Crawford		IPng Working Group Matt Crawford
	Internet Draft Fermilab		Internet Draft Fermilab
	July 18, 1997		September 26, 1997
	Transmission of IPv6 Packets over Ethernet Networks		Transmission of IPv6 Packets over Ethernet Networks
	<draft-ietf-ipngwg-trans-ethernet-02.txt>		<draft-ietf-ipngwg-trans-ethernet-03.txt>
	Status of this Memo		Status of this Memo
	This document is an Internet Draft. Internet Drafts are working		This document is an Internet Draft. Internet Drafts are working
	documents of the Internet Engineering Task Force (IETF), its Areas,		documents of the Internet Engineering Task Force (IETF), its Areas,
	and its Working Groups. Note that other groups may also distribute		and its Working Groups. Note that other groups may also distribute
	working documents as Internet Drafts.		working documents as Internet Drafts.
	Internet Drafts are draft documents valid for a maximum of six		Internet Drafts are draft documents valid for a maximum of six
	months. Internet Drafts may be updated, replaced, or obsoleted by		months. Internet Drafts may be updated, replaced, or obsoleted by
	skipping to change at page 2, line 25 ¶		skipping to change at page 2, line 25 ¶
	For purposes of this document, information received from DHCP is		For purposes of this document, information received from DHCP is
	considered "manually configured" and the term Ethernet includes		considered "manually configured" and the term Ethernet includes
	CSMA/CD and full-duplex subnetworks based on ISO/IEC 8802-3, with		CSMA/CD and full-duplex subnetworks based on ISO/IEC 8802-3, with
	various data rates.		various data rates.
	3. Frame Format		3. Frame Format
	IPv6 packets are transmitted in standard Ethernet frames. The		IPv6 packets are transmitted in standard Ethernet frames. The
	Ethernet header contains the Destination and Source Ethernet		Ethernet header contains the Destination and Source Ethernet
	addresses and the ethernet type code, which must contain the value		addresses and the Ethernet type code, which must contain the value
	86DD hexadecimal. The data field contains the IPv6 header followed		86DD hexadecimal. The data field contains the IPv6 header followed
	immediately by the payload, and possibly padding octets to meet the		immediately by the payload, and possibly padding octets to meet the
	minimum frame size for the Ethernet link.		minimum frame size for the Ethernet link.
	0 1		0 1
	0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5		0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	| Destination |		| Destination |
	+- -+		+- -+
	| Ethernet |		| Ethernet |
	skipping to change at page 4, line 8 ¶		skipping to change at page 4, line 8 ¶
	The Interface Identifier is then formed from the EUI-64 by		The Interface Identifier is then formed from the EUI-64 by
	complementing the "Universal/Local" (U/L) bit, which is the next-		complementing the "Universal/Local" (U/L) bit, which is the next-
	to-lowest order bit of the first octet of the EUI-64. Complementing		to-lowest order bit of the first octet of the EUI-64. Complementing
	this bit will generally change a 0 value to a 1, since an		this bit will generally change a 0 value to a 1, since an
	interface's built-in address is expected to be from a universally		interface's built-in address is expected to be from a universally
	administered address space and hence have a globally unique value.		administered address space and hence have a globally unique value.
	A universally administered IEEE 802 address or an EUI-64 is		A universally administered IEEE 802 address or an EUI-64 is
	signified by a 0 in the U/L bit position, while a globally unique		signified by a 0 in the U/L bit position, while a globally unique
	IPv6 Interface Identifier is signified by a 1 in the corresponding		IPv6 Interface Identifier is signified by a 1 in the corresponding
	position. For futher discussion on this point, see [AARCH].		position. For further discussion on this point, see [AARCH].
	For example, the Interface Identifier for an Ethernet interface		For example, the Interface Identifier for an Ethernet interface
	whose built-in address is, in hexadecimal,		whose built-in address is, in hexadecimal,
	34-56-78-9A-BC-DE		34-56-78-9A-BC-DE
	would be		would be
	36-56-78-FF-FE-9A-BC-DE.		36-56-78-FF-FE-9A-BC-DE.
	skipping to change at page 6, line 18 ¶		skipping to change at page 6, line 18 ¶
	is intended to preserve global uniqueness when possible. However,		is intended to preserve global uniqueness when possible. However,
	there is no protection from duplication through accident or forgery.		there is no protection from duplication through accident or forgery.
	9. References		9. References
	[AARCH] R. Hinden, S. Deering "IP Version 6 Addressing		[AARCH] R. Hinden, S. Deering "IP Version 6 Addressing
	Architecture", Currently draft-ietf-ipngwg-addr-arch-v2-		Architecture", Currently draft-ietf-ipngwg-addr-arch-v2-
	02.txt.		02.txt.
	[ACONF] S. Thomson, T. Narten, "IPv6 Stateless Address		[ACONF] S. Thomson, T. Narten, "IPv6 Stateless Address
	Autoconfiguration", RFC 1971.		Autoconfiguration", currently draft-ietf-ipngwg-addrconf-
			v2-00.txt.
	[DISC] T. Narten, E. Nordmark, W. A. Simpson, "Neighbor Discovery		[DISC] T. Narten, E. Nordmark, W. A. Simpson, "Neighbor Discovery
	for IP Version 6 (IPv6)", RFC 1970.		for IP Version 6 (IPv6)", currently draft-ietf-ipngwg-
			discovery-v2-00.txt.
	[EUI64] "64-Bit Global Identifier Format Tutorial",		[EUI64] "64-Bit Global Identifier Format Tutorial",
	http://standards.ieee.org/db/oui/tutorials/EUI64.html.		http://standards.ieee.org/db/oui/tutorials/EUI64.html.
	[IPV6] S. Deering, R. Hinden, "Internet Protocol, Version 6 (IPv6)		[IPV6] S. Deering, R. Hinden, "Internet Protocol, Version 6 (IPv6)
	Specification", RFC 1883.		Specification", currently draft-ietf-ipngwg-ipv6-spec-v2-
			00.txt.
	[KWORD] S. Bradner, "Key words for use in RFCs to Indicate		[KWORD] S. Bradner, "Key words for use in RFCs to Indicate
	Requirement Levels," RFC 2119.		Requirement Levels," RFC 2119.
	10. Author's Address		10. Author's Address
	Matt Crawford		Matt Crawford
	Fermilab MS 368		Fermilab MS 368
	PO Box 500		PO Box 500
	Batavia, IL 60510		Batavia, IL 60510
End of changes. 7 change blocks.
	7 lines changed or deleted		10 lines changed or added
This html diff was produced by rfcdiff 1.48. The latest version is available from http://tools.ietf.org/tools/rfcdiff/