< draft-ietf-ipngwg-1394-00.txt		draft-ietf-ipngwg-1394-01.txt >
	Internet-Draft K. Fujisawa, A. Onoe		Internet-Draft K. Fujisawa, A. Onoe
	<draft-ietf-ipngwg-1394-00.txt> Sony Corporation		<draft-ietf-ipngwg-1394-01.txt> Sony Corporation
	Expires: May, 2001 November 2000		Expires: August, 2001 February 2001
	Transmission of IPv6 Packets over IEEE 1394 Networks		Transmission of IPv6 Packets over IEEE 1394 Networks
	Status of this memo		Status of this memo
	This document is an Internet-Draft and is in full conformance		This document is an Internet-Draft and is in full conformance
	with all provisions of Section 10 of RFC2026.		with all provisions of Section 10 of RFC2026.
	Internet-Drafts are working documents of the Internet Engineering		Internet-Drafts are working documents of the Internet Engineering
	Task Force (IETF), its areas, and its working groups. Note that		Task Force (IETF), its areas, and its working groups. Note that
	skipping to change at page 5, line 28 ¶		skipping to change at page 5, line 28 ¶
	speed at which the PHY may send, receive or repeat		speed at which the PHY may send, receive or repeat
	packets. The encoding used for spd is specified in		packets. The encoding used for spd is specified in
	the Table 2 of [IP1394].		the Table 2 of [IP1394].
	unicast_FIFO This field MUST specify the 48-bit offset of the		unicast_FIFO This field MUST specify the 48-bit offset of the
	node's FIFO available for the receipt of IPv6		node's FIFO available for the receipt of IPv6
	datagrams. The offset of a node's unicast FIFO		datagrams. The offset of a node's unicast FIFO
	MUST NOT change, except as the result of a power		MUST NOT change, except as the result of a power
	reset.		reset.
			reserved This field MUST be set to all zeros by the sender
			and ignored by the receiver.
	Note that node_ID may change when 1394 bus-reset occurs. The mapping		Note that node_ID may change when 1394 bus-reset occurs. The mapping
	cache held in the node SHOULD be cleared on 1394 bus-reset.		cache held in the node SHOULD be cleared on 1394 bus-reset.
	According to [1394], the maximum data payload and the transmission		According to [1394], the maximum data payload and the transmission
	speed SHOULD be determined based on the sender's capability, the		speed SHOULD be determined based on the sender's capability, the
	recipient's capability, and the PHYs of all intervening nodes.		recipient's capability, and the PHYs of all intervening nodes.
	9. IPv6 MULTICAST		9. IPv6 MULTICAST
	By default, all best-effort IPv6 multicast MUST use asynchronous		By default, all best-effort IPv6 multicast MUST use asynchronous
	stream packets whose channel number is equal to the channel field		stream packets whose channel number is equal to the channel field
	from the BROADCAST_CHANNEL register.		from the BROADCAST_CHANNEL register. In particular, datagrams
			addressed to all-nodes multicast addresses, all-routers multicast
			addresses, and solicited-node multicast addresses [AARCH] MUST use
			the default channel specified by the BROADCAST_CHANNEL register.
	Best-effort IPv6 multicast for particular multicast group addresses		Best-effort IPv6 multicast for other multicast group addresses may
	may utilize a different channel number if such a channel number is		utilize a different channel number if such a channel number is
	allocated and advertised prior to use, by a multicast channel		allocated and advertised prior to use, by the multicast channel
	allocation protocol (MCAP), as described in [IP1394]. The		allocation protocol (MCAP), as described in [IP1394].
	implementors are encouraged to support this protocol when
	transmitting high-rate multicast streams. The MCAP 'type' value for		When a node wishes to receive multicast data addressed to other than
	IPv6 group address descriptor is {to be assigned by IANA}.		all-nodes multicast addresses, all-routers multicast addresses, and
			solicited-node multicast addresses, it MUST confirm if the channel
			mapping between a multicast group address and a channel number exists
			using MCAP, as described in "9.3 Multicast Receive" in [IP1394].
			The implementation of MCAP is optional for send-only nodes. A node
			MAY transmit multicast data addressed to any multicast addresses into
			the default broadcast channel regardless of the existing allocation
			of the channel. If a node wishes to transmit multicast data on other
			than the default channel, it MUST first confirm by MCAP whether or
			not a channel number for the group address has been already
			allocated. The implementors are encouraged to use this protocol when
			transmitting high-rate multicast streams.
			The MCAP 'type' value for IPv6 group address descriptor is {to be
			assigned by IANA}.
	10. IANA CONSIDERATIONS		10. IANA CONSIDERATIONS
	The value for Unit_SW_Version, described in section 5, MUST be		The value for Unit_SW_Version, described in section 5, MUST be
	assigned from the name space "CSR Protocol Identifiers" managed by		assigned from the name space "CSR Protocol Identifiers" managed by
	IANA. The detail of the "CSR Protocol Identifiers" is described in		IANA. The detail of the "CSR Protocol Identifiers" is described in
	"10. IANA CONSIDERATIONS" of [IP1394].		"10. IANA CONSIDERATIONS" of [IP1394].
	The value for MCAP type value, described in section 9, MUST be		The value for MCAP type value, described in section 9, MUST be
	managed and assigned by IANA. MCAP (Multicast Channel Allocation		managed and assigned by IANA. MCAP (Multicast Channel Allocation
	skipping to change at page 7, line 23 ¶		skipping to change at page 8, line 7 ¶
	Atsushi Onoe		Atsushi Onoe
	Internet Systems Laboratory, IN Laboratories, Sony Corporation		Internet Systems Laboratory, IN Laboratories, Sony Corporation
	6-7-35 Kitashinagawa, Shinagawa-ku, Tokyo 141-0001, JAPAN		6-7-35 Kitashinagawa, Shinagawa-ku, Tokyo 141-0001, JAPAN
	Tel: +81-3-5448-4620		Tel: +81-3-5448-4620
	Fax: +81-3-5448-4622		Fax: +81-3-5448-4622
	Email: onoe@sm.sony.co.jp		Email: onoe@sm.sony.co.jp
	Full Copyright Statement		Full Copyright Statement
	Copyright (C) The Internet Society (2000). All Rights Reserved.		Copyright (C) The Internet Society (2001). All Rights Reserved.
	This document and translations of it may be copied and furnished to		This document and translations of it may be copied and furnished to
	others, and derivative works that comment on or otherwise explain it		others, and derivative works that comment on or otherwise explain it
	or assist in its implementation may be prepared, copied, published		or assist in its implementation may be prepared, copied, published
	and distributed, in whole or in part, without restriction of any		and distributed, in whole or in part, without restriction of any
	kind, provided that the above copyright notice and this paragraph are		kind, provided that the above copyright notice and this paragraph are
	included on all such copies and derivative works. However, this		included on all such copies and derivative works. However, this
	document itself may not be modified in any way, such as by removing		document itself may not be modified in any way, such as by removing
	the copyright notice or references to the Internet Society or other		the copyright notice or references to the Internet Society or other
	Internet organizations, except as needed for the purpose of		Internet organizations, except as needed for the purpose of
End of changes. 5 change blocks.
	11 lines changed or deleted		32 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/