idnits 2.17.1 draft-ietf-ip1394-ipv6-00.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 == It seems as if not all pages are separated by form feeds - found 0 form feeds but 6 pages 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 (May 1999) is 9112 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 222, but no explicit reference was found in the text == Unused Reference: 'CSR' is defined on line 228, 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' -- Possible downref: Non-RFC (?) normative reference: ref. 'IP1394' ** 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 (==), 6 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: November, 1999 May 1999 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 is standardizing 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. 51 This document is a product of the IP1394 working group within the 52 Internet Engineering Task Force. Comments are solicited and should 53 be addressed to the working group's mailing list at 54 ip1394@mailbag.intel.com. 56 2. SPECIFICATION TERMINOLOGY 58 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 59 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 60 document are to be interpreted as described in RFC 2119. 62 3. IPv6-CAPABLE NODES 64 An IPv6-capable node SHALL fulfill the following minimum 65 requirements; 67 - it SHALL implement configuration ROM in the general format 68 specified by ISO/IEC 13213:1994 and SHALL implement the bus 69 information block specified by IEEE P1394a [P1394a] and a unit 70 directory specified by this document; 72 - the max_rec field in its bus information block SHALL be at least 8; 73 this indicates an ability to accept block write requests and 74 asynchronous stream packets with data payload of 512 octets. The 75 same ability SHALL also apply to read requests; that is, the node 76 SHALL be able to transmit a block response packet with a data 77 payload of 512 octets; 79 - it SHALL be isochronous resource manager capable, as specified by 80 1394; 82 - it SHALL support both reception and transmission of asynchronous 83 streams as specified by IEEE P1394a; 85 - it SHALL implement the BROADCAST_CHANNEL register as specified 86 by IEEE P1394a; and 88 - it SHALL be broadcast channel manager capable. 90 4. LINK ENCAPSULATION AND FRAGMENTATION 92 The encapsulation and fragmentation mechanism SHOULD be the same 93 as "5. LINK ENCAPSULATION AND FRAGMENTATION" of [IP1394]. 95 The ether_type value for IPv6 is 0x86dd. 97 The default MTU size for IPv6 packets on an IEEE1394 network is 1500 98 octets. This size may be reduced by a Router Advertisement [DISC] 99 containing an MTU option which specifies a smaller MTU, or by manual 100 configuration of each node. If a Router Advertisement received on 101 an IEEE1394 interface has an MTU option specifying an MTU larger than 102 1500, or larger than a manually configured value, that MTU option may 103 be logged to system management but MUST be otherwise ignored. The 104 mechanism to extend MTU size between particular two nodes is for 105 further study. 107 5. CONFIGURATION ROM 109 Configuration ROM for IPv6-capable nodes SHALL contain a unit 110 directory in the format specified by [IP1394] except following rules. 112 - The value for Unit_SW_Version is TBD. When this draft is approved 113 it is EXPECTED that Unit_SW_Version will assume the value of the 114 RFC number assigned. 116 - The textual descriptor for the Unit_SW_Version SHOULD be "IPv6". 118 6. STATELESS AUTOCONFIGURATION 120 The Interface Identifier [AARCH] for an IEEE1394 interface is formed 121 from the interface's built-in EUI-64 by complementing the 122 "Universal/Local" (U/L) bit, which is the next-to-lowest order bit of 123 the first octet of the EUI-64. Complementing this bit will generally 124 change a 0 value to a 1, since an interface's built-in address is 125 expected to be from a universally administered address space and 126 hence have a globally unique value. A universally administered EUI- 127 64 is signified by a 0 in the U/L bit position, while a globally 128 unique IPv6 Interface Identifier is signified by a 1 in the 129 corresponding position. For further discussion on this point, see 130 [AARCH]. 132 An IPv6 address prefix used for stateless autoconfiguration [ACONF] 133 of an IEEE1394 interface MUST have a length of 64 bits. 135 7. LINK-LOCAL ADDRESSES 136 The IPv6 link-local address [AARCH] for an IEEE1394 interface is 137 formed by appending the Interface Identifier, as defined above, to 138 the prefix FE80::/64. 140 10 bits 54 bits 64 bits 141 +----------+-----------------------+----------------------------+ 142 |1111111010| (zeros) | Interface Identifier | 143 +----------+-----------------------+----------------------------+ 145 8. ADDRESS MAPPING FOR UNICAST 147 The procedure for mapping IPv6 unicast addresses into IEEE1394 link- 148 layer addresses uses the Neighbor Discovery [DISC]. Since 1394 link 149 address (node_ID) will not be constant across a 1394 bridge, we have 150 chosen not to put it in the Link-layer Address option. The recipient 151 of the Neighbor Discovery SHOULD use the source_ID (obtained from 152 either the asynchronous packet header or the GASP header) in 153 conjunction with the content of the Source link-layer address. 154 The recipient of an Neighbor Discovery packet SHOULD ignore it unless 155 the most significant ten bits of the source_ID are equal to either 156 0x3FF or the most significant ten bits of the recipient's NODE_IDS 157 register. 159 The Source/Target Link-layer Address option has the following form 160 when the link layer is IEEE1394. 162 1 2 3 163 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 164 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 165 | Type | Length = 3 | | 166 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ ---+ 167 | node_unique_ID | 168 +--- +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 169 | | max_rec | spd | 170 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 171 | unicast_FIFO | 172 +--- +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 173 | | reserved | 174 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 175 | reserved | 176 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 178 Type 1 for Source Link-layer address. 179 2 for Target Link-layer address. 181 Length 3 (in units of 8 octets). 183 The meaning of 'node_unique_ID', 'unicast_FIFO', 'max_rec' and 'spd' 184 sub-fields are specified in [IP1394]. 186 Note that node_ID may change when 1394 bus-reset occurs. The mapping 187 cache held in the node SHOULD be cleared on 1394 bus-reset. 189 9. IPv6 MULTICAST 191 By default, all best-effort IPv6 multicast SHALL use asynchronous 192 stream packets whose channel number is equal to the channel field 193 from the BROADCAST_CHANNEL register. 195 Best-effort IPv6 multicast for particular multicast group addresses 196 may utilize a different channel number if such a channel number is 197 allocated and advertised prior to use, by a multicast channel 198 allocation protocol (MCAP), as described in [IP1394]. The 199 implementors are encouraged to support this protocol when 200 transmitting high-rate multicast streams. The MCAP 'type' value for 201 IPv6 group address descriptor is TBD. 203 10. OPEN ISSUES 205 a) The mechanism to extend MTU size between particular two nodes. 207 b) The mechanism to allocate and distribute a 1394 isochronous 208 channel number for isochronous transmission of IPv6 packets, 209 for an unicast or multicast flow. 211 Security Considerations 213 Security issues are not discussed in this document. 215 Acknowledgment 217 The editor would like to acknowledge the author of [ETHER] since some 218 part of this document has been derived from [ETHER]. 220 References 222 [1394] IEEE Std 1394-1995, Standard for a High Performance Serial 223 Bus 225 [P1394a] IEEE Project P1394a, Draft Standard for a High Performance 226 Serial Bus (Supplement) 228 [CSR] ISO/IEC 13213:1994, Control and Status Register (CSR) 229 Architecture for Microcomputer Buses 231 [IP1394] IP1394 Working Group, "IPv4 over IEEE 1394", currently 233 [IPV6] S. Deering, R. Hinden, "Internet Protocol, Version 6 (IPv6) 234 Specification", RFC2460, Dec 1998. 236 [AARCH] R. Hinden, S. Deering "IP Version 6 Addressing 237 Architecture", RFC2373. 239 [ACONF] S. Thomson, T. Narten, "IPv6 Stateless Address 240 Autoconfiguration", RFC2462, Dec 1998. 242 [DISC] T. Narten, E. Nordmark, W. A. Simpson, "Neighbor Discovery 243 for IP Version 6 (IPv6)", RFC2461, Dec 1998. 245 [ETHER] M. Crawford, "Transmission of IPv6 Packets over Ethernet 246 Networks", RFC2464, Dec 1998. 248 Author's address 250 Kenji Fujisawa 251 Sony Corporation 252 IT Development Dept., Personal IT Network Company 253 6-7-35, Kitashinagawa, 254 Shinagawa-ku, Tokyo, 141-0001 Japan 255 Phone: +81-3-5448-8507 256 E-mail: fujisawa@sm.sony.co.jp