Transmission of IPv6 Packets over IEEE 1394 Networks (RFC3146)
Original Publication Date: 2001-Oct-01
Included in the Prior Art Database: 2019-Feb-13
Internet Society Requests For Comment (RFCs)
K. Fujisawa: AUTHOR [+1]
This document describes the frame format for transmission of IPv6 packets and the method of forming IPv6 link-local addresses and statelessly autoconfigured addresses on IEEE1394 networks. [STANDARDS-TRACK]
Network Working Group K. Fujisawa Request for Comments: 3146 A. Onoe Category: Standards Track Sony Corporation October 2001
Transmission of IPv6 Packets over IEEE 1394 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.
Copyright (C) The Internet Society (2001). All Rights Reserved.
This document describes the frame format for transmission of IPv6 packets and the method of forming IPv6 link-local addresses and statelessly autoconfigured addresses on IEEE1394 networks.
IEEE Std 1394-1995 (and its amendment) is a standard for a High Performance Serial Bus. IETF IP1394 Working Group has standardized the method to carry IPv4 datagrams and ARP packets over IEEE1394 subnetwork [IP1394].
This document describes the frame format for transmission of IPv6 [IPV6] packets and the method of forming IPv6 link-local addresses and statelessly autoconfigured addresses on IEEE1394 networks. It also describes the content of the Source/Target Link-layer Address option used in Neighbor Discovery [DISC] when the messages are transmitted on an IEEE1394 network.
2. SPECIFICATION TERMINOLOGY
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119.
Fujisawa & Onoe Standards Track [Page 1]
RFC 3146 IPv6 Packets over IEEE 1394 Networks October 2001
3. IPv6-CAPABLE NODES
An IPv6-capable node MUST fulfill the following minimum requirements:
- it MUST implement configuration ROM in the general format specified by ISO/IEC 13213:1994 and MUST implement the bus information block specified by IEEE Std 1394a-2000 [1394a] and a unit directory specified by this document;
- the max_rec field in its bus information block MUST be at least 8; this indicates an ability to accept block write requests and asynchronous stream packets with data payload of 512 octets. The same ability MUST also apply to read requests; that is, the node MUST be able to transmit a block response packet with a data payload of 512 octets;
- it MUST be isochronous resource manager capable, as specified by IEEE Std 1394a-2000;
- it MUST support both reception and transmission of asynchronous streams as specified by IEEE Std 1394a-2000.
4. LINK ENCAPSULATION AND FRAGMENTATION
The encapsulation and fragmentation mechanism MUST be the same as "4. LINK ENCAPSULATION AND FRAGMENTATION" of [IP1394].
Note: Since there is an ether_type field to discriminate protocols and MCAP (multicast channel allocation protocol) is used for both IPv4 and IPv6, the version field in GASP (global asynchronous stream packet) header of IPv6 datagrams is t...