idnits 2.17.1 draft-fujisawa-ip1394-ipv6-04.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** Looks like you're using RFC 2026 boilerplate. This must be updated to follow RFC 3978/3979, as updated by RFC 4748. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- == No 'Intended status' indicated for this document; assuming Proposed Standard Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack an IANA Considerations section. (See Section 2.2 of https://www.ietf.org/id-info/checklist for how to handle the case when there are no actions for IANA.) ** The document seems to lack separate sections for Informative/Normative References. All references will be assumed normative when checking for downward references. ** The abstract seems to contain references ([IPV6], [DISC]), which it shouldn't. Please replace those with straight textual mentions of the documents in question. Miscellaneous warnings: ---------------------------------------------------------------------------- -- The document seems to lack a disclaimer for pre-RFC5378 work, but may have content which was first submitted before 10 November 2008. If you have contacted all the original authors and they are all willing to grant the BCP78 rights to the IETF Trust, then this is fine, and you can ignore this comment. If not, you may need to add the pre-RFC5378 disclaimer. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- The document date (June 2000) is 8708 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) == Unused Reference: '1394' is defined on line 211, but no explicit reference was found in the text -- Possible downref: Non-RFC (?) normative reference: ref. '1394' -- Possible downref: Non-RFC (?) normative reference: ref. 'P1394a' ** Obsolete normative reference: RFC 2460 (ref. 'IPV6') (Obsoleted by RFC 8200) ** Obsolete normative reference: RFC 2373 (ref. 'AARCH') (Obsoleted by RFC 3513) ** Obsolete normative reference: RFC 2462 (ref. 'ACONF') (Obsoleted by RFC 4862) ** Obsolete normative reference: RFC 2461 (ref. 'DISC') (Obsoleted by RFC 4861) Summary: 8 errors (**), 0 flaws (~~), 2 warnings (==), 4 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 Internet-Draft K. Fujisawa 2 Sony Corporation 3 Expires: December, 2000 June 2000 5 Transmission of IPv6 Packets over IEEE 1394 Networks 7 Status of this memo 9 This document is an Internet-Draft and is in full conformance 10 with all provisions of Section 10 of RFC2026. 12 Internet-Drafts are working documents of the Internet Engineering 13 Task Force (IETF), its areas, and its working groups. Note that 14 other groups may also distribute working documents as 15 Internet-Drafts. 17 Internet-Drafts are draft documents valid for a maximum of six 18 months and may be updated, replaced, or obsoleted by other 19 documents at any time. It is inappropriate to use Internet- 20 Drafts as reference material or to cite them other than as 21 "work in progress." 23 The list of current Internet-Drafts can be accessed at 24 http://www.ietf.org/ietf/1id-abstracts.txt 26 The list of Internet-Draft Shadow Directories can be accessed at 27 http://www.ietf.org/shadow.html. 29 Abstract 31 IEEE Std 1394-1995 is a standard for a High Performance Serial Bus. 32 This document describes the frame format for transmission of IPv6 33 [IPV6] packets and the method of forming IPv6 link-local addresses 34 and statelessly autoconfigured addresses on IEEE1394 networks. 35 It also describes the content of the Source/Target Link-layer Address 36 option used in Neighbor Discovery [DISC] when the messages are 37 transmitted on an IEEE1394 network. 39 1. INTRODUCTION 41 IEEE Std 1394-1995 is a standard for a High Performance Serial Bus. 42 IETF IP1394 Working Group has standardized the method to carry IPv4 43 datagrams and ARP packets over IEEE1394 subnetwork [IP1394]. 45 This document describes the frame format for transmission of IPv6 46 [IPV6] packets and the method of forming IPv6 link-local addresses 47 and statelessly autoconfigured addresses on IEEE1394 networks. 48 It also describes the content of the Source/Target Link-layer Address 49 option used in Neighbor Discovery [DISC] when the messages are 50 transmitted on an IEEE1394 network. 52 2. SPECIFICATION TERMINOLOGY 54 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 55 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 56 document are to be interpreted as described in RFC 2119. 58 3. IPv6-CAPABLE NODES 60 An IPv6-capable node SHALL fulfill the following minimum 61 requirements: 63 - it SHALL implement configuration ROM in the general format 64 specified by ISO/IEC 13213:1994 and SHALL implement the bus 65 information block specified by IEEE P1394a [P1394a] and a unit 66 directory specified by this document; 68 - the max_rec field in its bus information block SHALL be at least 8; 69 this indicates an ability to accept block write requests and 70 asynchronous stream packets with data payload of 512 octets. The 71 same ability SHALL also apply to read requests; that is, the node 72 SHALL be able to transmit a block response packet with a data 73 payload of 512 octets; 75 - it SHALL be isochronous resource manager capable, as specified by 76 IEEE P1394a; 78 - it SHALL support both reception and transmission of asynchronous 79 streams as specified by IEEE P1394a. 81 4. LINK ENCAPSULATION AND FRAGMENTATION 83 The encapsulation and fragmentation mechanism SHOULD be the same 84 as "5. LINK ENCAPSULATION AND FRAGMENTATION" of [IP1394]. 86 The ether_type value for IPv6 is 0x86dd. 88 The default MTU size for IPv6 packets on an IEEE1394 network is 1500 89 octets. This size may be reduced by a Router Advertisement [DISC] 90 containing an MTU option which specifies a smaller MTU, or by manual 91 configuration of each node. If a Router Advertisement received on 92 an IEEE1394 interface has an MTU option specifying an MTU larger than 93 1500, or larger than a manually configured value, that MTU option may 94 be logged to system management but MUST be otherwise ignored. The 95 mechanism to extend MTU size between particular two nodes is for 96 further study. 98 5. CONFIGURATION ROM 100 Configuration ROM for IPv6-capable nodes SHALL contain a unit 101 directory in the format specified by [IP1394] except following rules. 103 - The value for Unit_SW_Version is TBD. 105 - The textual descriptor for the Unit_SW_Version SHOULD be "IPv6". 107 6. STATELESS AUTOCONFIGURATION 109 The Interface Identifier [AARCH] for an IEEE1394 interface is formed 110 from the interface's built-in EUI-64 by complementing the 111 "Universal/Local" (U/L) bit, which is the next-to-lowest order bit of 112 the first octet of the EUI-64. Complementing this bit will generally 113 change a 0 value to a 1, since an interface's built-in address is 114 expected to be from a universally administered address space and 115 hence have a globally unique value. A universally administered EUI- 116 64 is signified by a 0 in the U/L bit position, while a globally 117 unique IPv6 Interface Identifier is signified by a 1 in the 118 corresponding position. For further discussion on this point, see 119 [AARCH]. 121 An IPv6 address prefix used for stateless autoconfiguration [ACONF] 122 of an IEEE1394 interface MUST have a length of 64 bits. 124 7. LINK-LOCAL ADDRESSES 126 The IPv6 link-local address [AARCH] for an IEEE1394 interface is 127 formed by appending the Interface Identifier, as defined above, to 128 the prefix FE80::/64. 130 10 bits 54 bits 64 bits 131 +----------+-----------------------+----------------------------+ 132 |1111111010| (zeros) | Interface Identifier | 133 +----------+-----------------------+----------------------------+ 135 8. ADDRESS MAPPING FOR UNICAST 136 The procedure for mapping IPv6 unicast addresses into IEEE1394 link- 137 layer addresses uses the Neighbor Discovery [DISC]. Since 1394 link 138 address (node_ID) will not be constant across a 1394 bridge, we have 139 chosen not to put it in the Link-layer Address option. The recipient 140 of the Neighbor Discovery SHOULD use the source_ID (obtained from 141 either the asynchronous packet header or the GASP header) in 142 conjunction with the content of the Source link-layer address. 143 The recipient of an Neighbor Discovery packet SHOULD ignore it unless 144 the most significant ten bits of the source_ID are equal to either 145 0x3FF or the most significant ten bits of the recipient's NODE_IDS 146 register. 148 The Source/Target Link-layer Address option has the following form 149 when the link layer is IEEE1394. 151 1 2 3 152 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 153 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 154 | Type | Length = 3 | | 155 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ ---+ 156 | node_unique_ID | 157 +--- +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 158 | | max_rec | spd | 159 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 160 | unicast_FIFO | 161 +--- +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 162 | | reserved | 163 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 164 | reserved | 165 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 167 Type 1 for Source Link-layer address. 168 2 for Target Link-layer address. 170 Length 3 (in units of 8 octets). 172 The meaning of 'node_unique_ID', 'unicast_FIFO', 'max_rec' and 'spd' 173 sub-fields are specified in [IP1394]. 175 Note that node_ID may change when 1394 bus-reset occurs. The mapping 176 cache held in the node SHOULD be cleared on 1394 bus-reset. 178 9. IPv6 MULTICAST 180 By default, all best-effort IPv6 multicast SHALL use asynchronous 181 stream packets whose channel number is equal to the channel field 182 from the BROADCAST_CHANNEL register. 184 Best-effort IPv6 multicast for particular multicast group addresses 185 may utilize a different channel number if such a channel number is 186 allocated and advertised prior to use, by a multicast channel 187 allocation protocol (MCAP), as described in [IP1394]. The 188 implementors are encouraged to support this protocol when 189 transmitting high-rate multicast streams. The MCAP 'type' value for 190 IPv6 group address descriptor is TBD. 192 10. OPEN ISSUES 194 a) The mechanism to extend MTU size between particular two nodes. 196 b) The mechanism to allocate and distribute a 1394 isochronous 197 channel number for isochronous transmission of IPv6 packets, 198 for an unicast or multicast flow. 200 Security Considerations 202 Security issues are not discussed in this document. 204 Acknowledgment 206 The editor would like to acknowledge the author of [ETHER] since some 207 part of this document has been derived from [ETHER]. 209 References 211 [1394] IEEE Std 1394-1995, Standard for a High Performance Serial 212 Bus 214 [P1394a] IEEEE P1394a Draft Standard for a High Performance Serial 215 Bus (Amendment) 217 [IP1394] Johansson, P., "IPv4 over IEEE 1394", RFC 2734, December 218 1999. 220 [IPV6] S. Deering, R. Hinden, "Internet Protocol, Version 6 (IPv6) 221 Specification", RFC2460, Dec 1998. 223 [AARCH] R. Hinden, S. Deering "IP Version 6 Addressing 224 Architecture", RFC2373. 226 [ACONF] S. Thomson, T. Narten, "IPv6 Stateless Address 227 Autoconfiguration", RFC2462, Dec 1998. 229 [DISC] T. Narten, E. Nordmark, W. A. Simpson, "Neighbor Discovery 230 for IP Version 6 (IPv6)", RFC2461, Dec 1998. 232 [ETHER] M. Crawford, "Transmission of IPv6 Packets over Ethernet 233 Networks", RFC2464, Dec 1998. 235 Author's address 237 Kenji Fujisawa 238 Sony Corporation 239 6-7-35, Kitashinagawa, 240 Shinagawa-ku, Tokyo, 141-0001 Japan 241 Phone: +81-3-5795-8507 242 E-mail: fujisawa@sm.sony.co.jp