< draft-ietf-ipngwg-trans-tokenring-03.txt		draft-ietf-ipngwg-trans-tokenring-04.txt >
	IPng Working Group Matt Crawford, Fermilab		IPng Working Group Matt Crawford, Fermilab
	Internet Draft Thomas Narten, IBM		Internet Draft Thomas Narten, IBM
	Stephen Thomas, TransNexus		Stephen Thomas, TransNexus
	October 23, 1997		November 6, 1997
	Transmission of IPv6 Packets over Token Ring Networks		Transmission of IPv6 Packets over Token Ring Networks
	<draft-ietf-ipngwg-trans-tokenring-03.txt>		<draft-ietf-ipngwg-trans-tokenring-04.txt>
	Status of this Memo		Status of this Memo
	This document is an Internet Draft. Internet Drafts are		This document is an Internet Draft. Internet Drafts are
	working documents of the Internet Engineering Task Force		working documents of the Internet Engineering Task Force
	(IETF), its Areas, and its Working Groups. Note that other		(IETF), its Areas, and its Working Groups. Note that other
	groups may also distribute working documents as Internet		groups may also distribute working documents as Internet
	Drafts.		Drafts.
	Internet Drafts are draft documents valid for a maximum of		Internet Drafts are draft documents valid for a maximum of
	skipping to change at page 1, line 32 ¶		skipping to change at page 1, line 32 ¶
	appropriate to use Internet Drafts as reference material or		appropriate to use Internet Drafts as reference material or
	to cite them other than as a "working draft" or "work in		to cite them other than as a "working draft" or "work in
	progress."		progress."
	To learn the current status of any Internet-Draft, please		To learn the current status of any Internet-Draft, please
	check the "1id-abstracts.txt" listing contained in the		check the "1id-abstracts.txt" listing contained in the
	Internet Drafts Shadow Directories on ds.internic.net (US		Internet Drafts Shadow Directories on ds.internic.net (US
	East Coast), nic.nordu.net (Europe), ftp.isi.edu (US West		East Coast), nic.nordu.net (Europe), ftp.isi.edu (US West
	Coast), or munnari.oz.au (Pacific Rim).		Coast), or munnari.oz.au (Pacific Rim).
	This Internet Draft expires April 23, 1998.		This Internet Draft expires May 6, 1998.
	1. Introduction		1. Introduction
	This memo specifies the MTU and frame format for transmission		This memo specifies the MTU and frame format for transmission
	of IPv6 packets on Token Ring networks. It also specifies the		of IPv6 packets on Token Ring networks. It also specifies the
	method of forming IPv6 link-local addresses on Token Ring		method of forming IPv6 link-local addresses on Token Ring
	networks and the content of the Source/Target Link-layer		networks and the content of the Source/Target Link-layer
	Address option used the Router Solicitation, Router		Address option used the Router Solicitation, Router
	Advertisement, Redirect, Neighbor Solicitation and Neighbor		Advertisement, Redirect, Neighbor Solicitation and Neighbor
	Advertisement messages when those messages are transmitted on		Advertisement messages when those messages are transmitted on
	a Token Ring network.		a Token Ring network.
			Implementors should be careful to note that Token Ring adaptors
			assume addresses are in non-canonical rather than canonical
			format, requiring that special care be taken to insure that
			addresses are processed correctly. See [CANON] for more details.
	The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL		The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL
	NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and		NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL"
	"OPTIONAL" in this document are to be interpreted as described		in this document are to be interpreted as described in [KWORD].
	in [KWORD].
	2. Maximum Transmission Unit		2. Maximum Transmission Unit
	IEEE 802.5 networks have a maximum frame size based on the		IEEE 802.5 networks have a maximum frame size based on the
	maximum time a node may hold the token. This time depends on		maximum time a node may hold the token. This time depends on
	many factors including the data signaling rate and the number		many factors including the data signaling rate and the number
	of nodes on the ring. Because the maximum frame size varies,		of nodes on the ring. Because the maximum frame size varies,
	implementations must rely on manual configuration or router		implementations must rely on manual configuration or router
	advertisements [DISC] to determine actual MTU sizes. Common		advertisements [DISC] to determine actual MTU sizes. Common
	default values include approximately 2000, 4000, and 8000		default values include approximately 2000, 4000, and 8000 octets.
	octets.
	In the absence of any other information, an implementation		In the absence of any other information, an implementation
	should use a default MTU of 1500 octets. This size offers		should use a default MTU of 1500 octets. This size offers
	compatibility with all common 802.5 defaults, as well as with		compatibility with all common 802.5 defaults, as well as with
	Ethernet LANs in an environment using transparent bridging.		Ethernet LANs in an environment using transparent bridging.
	In an environment using source route bridging, the process of		In an environment using source route bridging, the process of
	discovering the MAC-level path to a neighbor can yield the		discovering the MAC-level path to a neighbor can yield the
	MTU for the path to that neighbor. The information is		MTU for the path to that neighbor. The information is
	contained in the largest frame (LF) subfield of the routing		contained in the largest frame (LF) subfield of the routing
	skipping to change at page 9, line 48 ¶		skipping to change at page 9, line 48 ¶
	[ACONF] S. Thomson, T. Narten, "IPv6 Stateless Address		[ACONF] S. Thomson, T. Narten, "IPv6 Stateless Address
	Autoconfiguration", currently draft-ietf-ipngwg-		Autoconfiguration", currently draft-ietf-ipngwg-
	addrconf-v2-00.txt.		addrconf-v2-00.txt.
	[BRIDGE] 10038: 1993 (ISO/IEC) [ANSI/IEEE Std 802.1D, 1993		[BRIDGE] 10038: 1993 (ISO/IEC) [ANSI/IEEE Std 802.1D, 1993
	Edition] Information technology--Telecommunications		Edition] Information technology--Telecommunications
	and information exchange between systems--Local		and information exchange between systems--Local
	area networks--Media access control (MAC) bridges.		area networks--Media access control (MAC) bridges.
			[CANON] T. Narten, C. Burton, "A Caution on Canonical Bit
			Order Of Link-Layer Addresses", currently
			draft-narten-canonical-ordering-00.txt.
	[CONF] S. Thomson, T. Narten, "IPv6 Stateless Address		[CONF] S. Thomson, T. Narten, "IPv6 Stateless Address
	Autoconfiguration", RFC 1971.		Autoconfiguration", RFC 1971.
	[DISC] T. Narten, E. Nordmark, W. A. Simpson, "Neighbor		[DISC] T. Narten, E. Nordmark, W. A. Simpson, "Neighbor
	Discovery for IP Version 6 (IPv6)", currently		Discovery for IP Version 6 (IPv6)", currently
	draft-ietf-ipngwg-discovery-v2-00.txt.		draft-ietf-ipngwg-discovery-v2-00.txt.
	[EUI64] "64-Bit Global Identifier Format Tutorial", http:		[EUI64] "64-Bit Global Identifier Format Tutorial", http:
	//standards.ieee.org/db/oui/tutorials/EUI64.html.		//standards.ieee.org/db/oui/tutorials/EUI64.html.
	skipping to change at page 10, line 30 ¶		skipping to change at page 10, line 33 ¶
	Edition] Information technology--Telecommunications		Edition] Information technology--Telecommunications
	and information exchange between systems--Local and		and information exchange between systems--Local and
	Metropolitan area networks--Specific requirements--		Metropolitan area networks--Specific requirements--
	Part 2: Logical link control.		Part 2: Logical link control.
	11. Authors' Addresses		11. Authors' Addresses
	Matt Crawford		Matt Crawford
	Fermilab MS 368		Fermilab MS 368
	PO Box 500		PO Box 500
	Batavia, IL 60510		Batavia, IL 60510 USA
	USA
	Phone: +1 630 840 3461		Phone: +1 630 840 3461
	EMail: crawdad@fnal.gov		EMail: crawdad@fnal.gov
	Thomas Narten		Thomas Narten
	IBM Corporation		IBM Corporation
	P.O. Box 12195		P.O. Box 12195
	Research Triangle Park, NC 27709-2195		Research Triangle Park, NC 27709-2195 USA
	USA
	Phone: +1 919 254 7798		Phone: +1 919 254 7798
	Email: narten@vnet.ibm.com		Email: narten@vnet.ibm.com
	Stephen Thomas		Stephen Thomas
	TransNexus		TransNexus
	430 Tenth Street NW Suite N204		430 Tenth Street NW Suite N204
	Atlanta, GA 30318		Atlanta, GA 30318 USA
	USA
	Phone: +1 404 872 4745		Phone: +1 404 872 4745
	Email: stephen.thomas@transnexus.com		Email: stephen.thomas@transnexus.com
End of changes. 10 change blocks.
	14 lines changed or deleted		18 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/