idnits 2.17.1 draft-ietf-ipngwg-1394-01.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 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 copyright year in the RFC 3978 Section 5.4 Copyright Line does not match the current year -- 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 (February 2001) is 8471 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) -- Possible downref: Non-RFC (?) normative reference: ref. '1394' -- Possible downref: Non-RFC (?) normative reference: ref. '1394a' ** 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: 7 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, A. Onoe 2 Sony Corporation 3 Expires: August, 2001 February 2001 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 (and its amendment) is a standard for a High 42 Performance Serial Bus. IETF IP1394 Working Group has standardized 43 the method to carry IPv4 datagrams and ARP packets over IEEE1394 44 subnetwork [IP1394]. 46 This document describes the frame format for transmission of IPv6 47 [IPV6] packets and the method of forming IPv6 link-local addresses 48 and statelessly autoconfigured addresses on IEEE1394 networks. 49 It also describes the content of the Source/Target Link-layer Address 50 option used in Neighbor Discovery [DISC] when the messages are 51 transmitted on an IEEE1394 network. 53 2. SPECIFICATION TERMINOLOGY 55 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 56 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 57 document are to be interpreted as described in RFC 2119. 59 3. IPv6-CAPABLE NODES 61 An IPv6-capable node MUST fulfill the following minimum requirements: 63 - it MUST implement configuration ROM in the general format 64 specified by ISO/IEC 13213:1994 and MUST implement the bus 65 information block specified by IEEE Std 1394a-2000 [1394a] 66 and a unit directory specified by this document; 68 - the max_rec field in its bus information block MUST 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 MUST also apply to read requests; that is, the node 72 MUST be able to transmit a block response packet with a data 73 payload of 512 octets; 75 - it MUST be isochronous resource manager capable, as specified by 76 IEEE Std 1394a-2000; 78 - it MUST support both reception and transmission of asynchronous 79 streams as specified by IEEE Std 1394a-2000. 81 4. LINK ENCAPSULATION AND FRAGMENTATION 83 The encapsulation and fragmentation mechanism MUST be the same 84 as "4. LINK ENCAPSULATION AND FRAGMENTATION" of [IP1394]. 86 Note: Since there is an ether_type field to discriminate 87 protocols and MCAP (multicast channel allocation protocol) is 88 used for both IPv4 and IPv6, the version field in GASP (global 89 asynchronous stream packet) header of IPv6 datagrams is the same 90 value (one) as [IP1394]. 92 The ether_type value for IPv6 is 0x86dd. 94 The default MTU size for IPv6 packets on an IEEE1394 network is 1500 95 octets. This size may be reduced by a Router Advertisement [DISC] 96 containing an MTU option which specifies a smaller MTU, or by manual 97 configuration of each node. If a Router Advertisement received on 98 an IEEE1394 interface has an MTU option specifying an MTU larger than 99 1500, or larger than a manually configured value, that MTU option may 100 be logged to system management but MUST be otherwise ignored. The 101 mechanism to extend MTU size between particular two nodes is for 102 further study. 104 5. CONFIGURATION ROM 106 Configuration ROM for IPv6-capable nodes MUST contain a unit 107 directory in the format specified by [IP1394] except following rules. 109 - The value for Unit_SW_Version is {to be assigned by IANA}. 111 - The textual descriptor for the Unit_SW_Version MUST be "IPv6". 113 Note: A dual-stack (IPv4 and IPv6) node will have two unit 114 directories for IPv4 and IPv6 respectively. 116 6. STATELESS AUTOCONFIGURATION 118 The Interface Identifier [AARCH] for an IEEE1394 interface is formed 119 from the interface's built-in EUI-64 by complementing the 120 "Universal/Local" (U/L) bit, which is the next-to-lowest order bit of 121 the first octet of the EUI-64. Complementing this bit will generally 122 change a 0 value to a 1, since an interface's built-in EUI-64 is 123 expected to be from a universally administered address space and 124 hence have a globally unique value. A universally administered EUI- 125 64 is signified by a 0 in the U/L bit position, while a globally 126 unique IPv6 Interface Identifier is signified by a 1 in the 127 corresponding position. For further discussion on this point, see 128 [AARCH]. 130 An IPv6 address prefix used for stateless autoconfiguration [ACONF] 131 of an IEEE1394 interface MUST have a length of 64 bits. 133 7. LINK-LOCAL ADDRESSES 134 The IPv6 link-local address [AARCH] for an IEEE1394 interface is 135 formed by appending the Interface Identifier, as defined above, to 136 the prefix FE80::/64. 138 10 bits 54 bits 64 bits 139 +----------+-----------------------+----------------------------+ 140 |1111111010| (zeros) | Interface Identifier | 141 +----------+-----------------------+----------------------------+ 143 8. ADDRESS MAPPING FOR UNICAST 145 The procedure for mapping IPv6 unicast addresses into IEEE1394 link- 146 layer addresses uses the Neighbor Discovery [DISC]. Since 1394 link 147 address (node_ID) will not be constant across a 1394 bridge, we have 148 chosen not to put it in the Link-layer Address option. The recipient 149 of the Neighbor Discovery SHOULD use the source_ID (obtained from 150 either the asynchronous packet header or the GASP header) in 151 conjunction with the content of the Source link-layer address. An 152 implementation MAY use some other methods to obtain a node_ID of the 153 sender utilizing a mapping table between node_unique_ID (EUI-64) and 154 node_ID. The mechanism to make such mapping table is out of scope of 155 this document. 156 The recipient of an Neighbor Discovery packet MUST ignore it unless 157 the most significant ten bits of the source_ID are equal to either 158 0x3FF or the most significant ten bits of the recipient's NODE_IDS 159 register. 161 The Source/Target Link-layer Address option has the following form 162 when the link layer is IEEE1394. 164 1 2 3 165 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 166 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 167 | Type | Length = 3 | | 168 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ ---+ 169 | node_unique_ID (EUI-64) | 170 +--- +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 171 | | max_rec | spd | 172 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 173 | unicast_FIFO | 174 +--- +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 175 | | reserved | 176 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 177 | reserved | 178 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 180 Type 1 for Source Link-layer address. 181 2 for Target Link-layer address. 183 Length 3 (in units of 8 octets). 185 node_unique_ID This field contains the node unique ID of the 186 node and MUST be equal to that specified in the 187 node's configuration ROM. 189 max_rec This field MUST be equal to the value of max_rec 190 in the node's configuration ROM. 192 spd This field MUST be set to the lesser of the node's 193 link speed and PHY speed. The link speed is the 194 maximum speed at which the link may send or 195 receive packets; the PHY speed is the maximum 196 speed at which the PHY may send, receive or repeat 197 packets. The encoding used for spd is specified in 198 the Table 2 of [IP1394]. 200 unicast_FIFO This field MUST specify the 48-bit offset of the 201 node's FIFO available for the receipt of IPv6 202 datagrams. The offset of a node's unicast FIFO 203 MUST NOT change, except as the result of a power 204 reset. 206 reserved This field MUST be set to all zeros by the sender 207 and ignored by the receiver. 209 Note that node_ID may change when 1394 bus-reset occurs. The mapping 210 cache held in the node SHOULD be cleared on 1394 bus-reset. 212 According to [1394], the maximum data payload and the transmission 213 speed SHOULD be determined based on the sender's capability, the 214 recipient's capability, and the PHYs of all intervening nodes. 216 9. IPv6 MULTICAST 218 By default, all best-effort IPv6 multicast MUST use asynchronous 219 stream packets whose channel number is equal to the channel field 220 from the BROADCAST_CHANNEL register. In particular, datagrams 221 addressed to all-nodes multicast addresses, all-routers multicast 222 addresses, and solicited-node multicast addresses [AARCH] MUST use 223 the default channel specified by the BROADCAST_CHANNEL register. 225 Best-effort IPv6 multicast for other multicast group addresses may 226 utilize a different channel number if such a channel number is 227 allocated and advertised prior to use, by the multicast channel 228 allocation protocol (MCAP), as described in [IP1394]. 230 When a node wishes to receive multicast data addressed to other than 231 all-nodes multicast addresses, all-routers multicast addresses, and 232 solicited-node multicast addresses, it MUST confirm if the channel 233 mapping between a multicast group address and a channel number exists 234 using MCAP, as described in "9.3 Multicast Receive" in [IP1394]. 236 The implementation of MCAP is optional for send-only nodes. A node 237 MAY transmit multicast data addressed to any multicast addresses into 238 the default broadcast channel regardless of the existing allocation 239 of the channel. If a node wishes to transmit multicast data on other 240 than the default channel, it MUST first confirm by MCAP whether or 241 not a channel number for the group address has been already 242 allocated. The implementors are encouraged to use this protocol when 243 transmitting high-rate multicast streams. 245 The MCAP 'type' value for IPv6 group address descriptor is {to be 246 assigned by IANA}. 248 10. IANA CONSIDERATIONS 250 The value for Unit_SW_Version, described in section 5, MUST be 251 assigned from the name space "CSR Protocol Identifiers" managed by 252 IANA. The detail of the "CSR Protocol Identifiers" is described in 253 "10. IANA CONSIDERATIONS" of [IP1394]. 255 The value for MCAP type value, described in section 9, MUST be 256 managed and assigned by IANA. MCAP (Multicast Channel Allocation 257 Protocol) is defined in RFC2734, which is used to manage channels in 258 IEEE1394 busses by IP-based protocols. RFC2734 section 9.1 defines 259 MCAP group address descriptor format. It has 8-bit type field which 260 indicates a type of a MCAP descriptor. The values 'zero' and '255' 261 should be reserved and MUST NOT be allocated. The value 'one' is 262 assigned for IPv4 Multicast Group address in RFC2734. 264 Security Considerations 266 The method of derivation of Interface Identifiers from EUI-64 is 267 intended to preserve global uniqueness when possible. However, there 268 is no protection from duplication through accident or forgery. 270 Acknowledgment 272 The authors would like to acknowledge the authors of [IP1394] and 273 [ETHER] since some part of this document has been derived from them. 275 References 277 [1394] IEEE Std 1394-1995, Standard for a High Performance Serial 278 Bus 280 [1394a] IEEE Std 1394a-2000, Standard for a High Performance Serial 281 Bus - Amendment 1 283 [IP1394] P. Johansson, "IPv4 over IEEE 1394", RFC 2734, December 284 1999. 286 [IPV6] S. Deering, R. Hinden, "Internet Protocol, Version 6 (IPv6) 287 Specification", RFC2460, Dec 1998. 289 [AARCH] R. Hinden, S. Deering "IP Version 6 Addressing 290 Architecture", RFC2373. 292 [ACONF] S. Thomson, T. Narten, "IPv6 Stateless Address 293 Autoconfiguration", RFC2462, Dec 1998. 295 [DISC] T. Narten, E. Nordmark, W. A. Simpson, "Neighbor Discovery 296 for IP Version 6 (IPv6)", RFC2461, Dec 1998. 298 [ETHER] M. Crawford, "Transmission of IPv6 Packets over Ethernet 299 Networks", RFC2464, Dec 1998. 301 Authors' address 303 Kenji Fujisawa 304 PNC Development Center, Sony Corporation 305 6-7-35 Kitashinagawa, Shinagawa-ku, Tokyo 141-0001, JAPAN 306 Tel: +81-3-5795-8507 307 Fax: +81-3-5795-8977 308 Email: fujisawa@sm.sony.co.jp 310 Atsushi Onoe 311 Internet Systems Laboratory, IN Laboratories, Sony Corporation 312 6-7-35 Kitashinagawa, Shinagawa-ku, Tokyo 141-0001, JAPAN 313 Tel: +81-3-5448-4620 314 Fax: +81-3-5448-4622 315 Email: onoe@sm.sony.co.jp 317 Full Copyright Statement 319 Copyright (C) The Internet Society (2001). All Rights Reserved. 321 This document and translations of it may be copied and furnished to 322 others, and derivative works that comment on or otherwise explain it 323 or assist in its implementation may be prepared, copied, published 324 and distributed, in whole or in part, without restriction of any 325 kind, provided that the above copyright notice and this paragraph are 326 included on all such copies and derivative works. However, this 327 document itself may not be modified in any way, such as by removing 328 the copyright notice or references to the Internet Society or other 329 Internet organizations, except as needed for the purpose of 330 developing Internet standards in which case the procedures for 331 copyrights defined in the Internet Standards process must be 332 followed, or as required to translate it into languages other than 333 English. 335 The limited permissions granted above are perpetual and will not be 336 revoked by the Internet Society or its successors or assigns. 338 This document and the information contained herein is provided on an 339 "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING 340 TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING 341 BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION 342 HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF 343 MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.