idnits 2.17.1 draft-fujisawa-ip1394-ipv6-02.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: ---------------------------------------------------------------------------- ** Missing expiration date. The document expiration date should appear on the first and last page. == 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 (February 1999) is 9174 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 213, but no explicit reference was found in the text == Unused Reference: 'CSR' is defined on line 219, 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' -- Possible downref: Non-RFC (?) normative reference: ref. 'CSR' == Outdated reference: A later version (-19) exists of draft-ietf-ip1394-ipv4-13 ** 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: 9 errors (**), 0 flaws (~~), 4 warnings (==), 5 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Internet-Draft K. Fujisawa 3 Sony Corporation 4 Expires: August, 1999 February 1999 6 Transmission of IPv6 Packets over IEEE 1394 Networks 8 Status of this memo 10 This document is an Internet-Draft and is in full conformance 11 with all provisions of Section 10 of RFC2026. 13 Internet-Drafts are working documents of the Internet Engineering 14 Task Force (IETF), its areas, and its working groups. Note that 15 other groups may also distribute working documents as 16 Internet-Drafts. 18 Internet-Drafts are draft documents valid for a maximum of six 19 months and may be updated, replaced, or obsoleted by other 20 documents at any time. It is inappropriate to use Internet- 21 Drafts as reference material or to cite them other than as 22 "work in progress." 24 The list of current Internet-Drafts can be accessed at 25 http://www.ietf.org/ietf/1id-abstracts.txt 27 The list of Internet-Draft Shadow Directories can be accessed at 28 http://www.ietf.org/shadow.html. 30 Abstract 32 IEEE Std 1394-1995 is a standard for a High Performance Serial Bus. 33 This document proposes the frame format for transmission of IPv6 34 [IPV6] packets and the method of forming IPv6 link-local addresses 35 and statelessly autoconfigured addresses on IEEE1394 networks. 36 It also proposes the content of the Source/Target Link-layer Address 37 option used in Neighbor Discovery [DISC] when the messages are 38 transmitted on an IEEE1394 network. 40 1. INTRODUCTION 42 IEEE Std 1394-1995 is a standard for a High Performance Serial Bus. 43 IETF IP1394 Working Group is standardizing the method to carry IPv4 44 datagrams and ARP packets over IEEE1394 subnetwork [IP1394]. 46 This document proposes 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 proposes 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 SHALL fulfill the following minimum 62 requirements; 64 - it SHALL implement configuration ROM in the general format 65 specified by ISO/IEC 13213:1994 and SHALL implement the bus 66 information block specified by IEEE P1394a [P1394a] and a unit 67 directory specified by this memo; 69 - the max_rec field in its bus information block SHALL be at least 8; 70 this indicates an ability to accept block write requests and 71 asynchronous stream packets with data payload of 512 octets. The 72 same ability SHALL also apply to read requests; that is, the node 73 SHALL be able to transmit a block response packet with a data 74 payload of 512 octets; 76 - it SHALL be isochronous resource manager capable, as specified by 77 1394; 79 - it SHALL support both reception and transmission of asynchronous 80 streams as specified by IEEE P1394a; 82 - it SHALL implement the BROADCAST_CHANNEL register as specified 83 by IEEE P1394a; and 85 - it SHALL be broadcast channel manager capable. 87 4. LINK ENCAPSULATION AND FRAGMENTATION 88 The encapsulation and fragmentation mechanism SHOULD be the same 89 as "5. LINK ENCAPSULATION AND FRAGMENTATION" of [IP1394]. 91 The ether_type value for IPv6 is 0x86dd. 93 The default MTU size for IPv6 packets on an IEEE1394 network is 1500 94 octets. This size may be reduced by a Router Advertisement [DISC] 95 containing an MTU option which specifies a smaller MTU, or by manual 96 configuration of each node. If a Router Advertisement received on 97 an IEEE1394 interface has an MTU option specifying an MTU larger than 98 1500, or larger than a manually configured value, that MTU option may 99 be logged to system management but MUST be otherwise ignored. The 100 mechanism to extend MTU size between particular two nodes is for 101 further study. 103 5. CONFIGURATION ROM 105 Configuration ROM for IPv6-capable nodes SHALL contain a unit 106 directory in the format specified by [IP1394] except following rules. 108 - The value for Unit_SW_Version is TBD. When this draft is approved 109 it is EXPECTED that Unit_SW_Version will assume the value of the 110 RFC number assigned. 112 - The textual descriptor for the Unit_SW_Version SHOULD be "IPv6". 114 6. STATELESS AUTOCONFIGURATION 116 The Interface Identifier [AARCH] for an IEEE1394 interface is formed 117 from the interface's built-in EUI-64 by complementing the 118 "Universal/Local" (U/L) bit, which is the next-to-lowest order bit of 119 the first octet of the EUI-64. Complementing this bit will generally 120 change a 0 value to a 1, since an interface's built-in address is 121 expected to be from a universally administered address space and 122 hence have a globally unique value. A universally administered EUI- 123 64 is signified by a 0 in the U/L bit position, while a globally 124 unique IPv6 Interface Identifier is signified by a 1 in the 125 corresponding position. For further discussion on this point, see 126 [AARCH]. 128 An IPv6 address prefix used for stateless autoconfiguration [ACONF] 129 of an IEEE1394 interface MUST have a length of 64 bits. 131 7. LINK-LOCAL ADDRESSES 133 The IPv6 link-local address [AARCH] for an IEEE1394 interface is 134 formed by appending the Interface Identifier, as defined above, to 135 the prefix FE80::/64. 137 10 bits 54 bits 64 bits 138 +----------+-----------------------+----------------------------+ 139 |1111111010| (zeros) | Interface Identifier | 140 +----------+-----------------------+----------------------------+ 142 8. ADDRESS MAPPING FOR UNICAST 144 The procedure for mapping IPv6 unicast addresses into IEEE1394 link- 145 layer addresses uses the Neighbor Discovery [DISC]. Since 1394 link 146 address (node_ID) will not be constant across a 1394 bridge, we have 147 chosen not to put it in the Link-layer Address option. The recipient 148 of the Neighbor Discovery SHALL use the source_node_ID in the 1394 149 packet header or GASP header in conjunction with the content of the 150 Source link-layer address. 151 The Source/Target Link-layer Address option has the following form 152 when the link layer is IEEE1394. 154 1 2 3 155 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 156 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 157 | Type | Length = 3 | | 158 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ ---+ 159 | node_unique_ID | 160 +--- +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 161 | | max_rec | spd | 162 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 163 | unicast_FIFO | 164 +--- +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 165 | | reserved | 166 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 167 | reserved | 168 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 170 Type 1 for Source Link-layer address. 171 2 for Target Link-layer address. 173 Length 3 (in units of 8 octets). 175 The meaning of 'node_unique_ID', 'unicast_FIFO', 'max_rec' and 'spd' 176 sub-fields are specified in [IP1394]. 178 Note that node_ID may change when 1394 bus-reset occurs. The mapping 179 cache held in the node SHOULD be cleared on 1394 bus-reset. 181 9. IPv6 MULTICAST 183 By default, all best-effort IPv6 multicast SHALL use asynchronous 184 stream packets whose channel number is equal to the channel field 185 from the BROADCAST_CHANNEL register. 187 Best-effort IPv6 multicast for particular multicast group addresses 188 may utilize a different channel number if such a channel number is 189 allocated and advertised prior to use, by the multicast channel 190 allocation protocol (MCAP), as described in [IP1394]. The 'type' 191 field in MCAP group address descriptor SHALL be TBD to indicate an 192 IPv6 group address descriptor. 194 10. OPEN ISSUES 196 a) The mechanism to extend MTU size between particular two nodes. 198 b) The mechanism to allocate and distribute a 1394 isochronous 199 channel number for isochronous transmission of IPv6 packets, 200 for an unicast or multicast flow. 202 Security Considerations 204 Security issues are not discussed in this document. 206 Acknowledgement 208 The auther would like to acknowledge the author of [ETHER] since some 209 part of this document has been derived from [ETHER]. 211 References 213 [1394] IEEE Std 1394-1995, Standard for a High Performance Serial 214 Bus 216 [P1394a] IEEE Project P1394a, Draft Standard for a High Performance 217 Serial Bus (Supplement) 219 [CSR] ISO/IEC 13213:1994, Control and Status Register (CSR) 220 Architecture for Microcomputer Buses 222 [IP1394] IP1394 Working Group, "IPv4 over IEEE 1394", currently 223 draft-ietf-ip1394-ipv4-13.txt. 225 [IPV6] S. Deering, R. Hinden, "Internet Protocol, Version 6 (IPv6) 226 Specification", RFC2460, Dec 1998. 228 [AARCH] R. Hinden, S. Deering "IP Version 6 Addressing 229 Architecture", RFC2373. 231 [ACONF] S. Thomson, T. Narten, "IPv6 Stateless Address 232 Autoconfiguration", RFC2462, Dec 1998. 234 [DISC] T. Narten, E. Nordmark, W. A. Simpson, "Neighbor Discovery 235 for IP Version 6 (IPv6)", RFC2461, Dec 1998. 237 [ETHER] M. Crawford, "Transmission of IPv6 Pacekts over Ethernet 238 Networks", RFC2464, Dec 1998. 240 Author's address 242 Kenji Fujisawa 243 Sony Corporation 244 IT Laboratories, Computer Systems Laboratory 245 6-7-35, Kitashinagawa, 246 Shinagawa-ku, Tokyo, 141-0001 Japan 247 Phone: +81-3-5448-4602 248 E-mail: fujisawa@sm.sony.co.jp 250 Technical changes from old version 252 * Changes from -00.txt 254 - Two octets padding in a Source/Target Link-layer Address option 255 of the Neighbor Discovery has been removed. 257 * Changes from -01.txt 259 - The 'node_ID' sub field has been removed from a Source/Target 260 Link-layer Address option of the Neighbor Discovery, and the 261 order of some fields has been changed in accordance with [IP1394]. 263 - The MCAP type value for IPv6 group address descriptor is changed 264 to TBD. 266 - A new section for "CONFIGURATION ROM" has been added.