Network Working Group D. Borman Request for Comments: 2675 Berkeley Software Design Obsoletes: 2147 S. Deering Category: Standards Track Cisco R. Hinden Nokia August 1999 IPv6 Jumbograms Status of this Memo This document specifies an Internet standards track protocol for the Internet community, and requests conversation and suggestions for improvements. Please mention to the current type of the "Internet Official Protocol Standards" (STD 1) for the standardization state and position of this protocol. Distribution of this memo is unlimited. Copyright Notice Copyright (C) The Internet Society (1999). All Rights Reserved. Abstract A "jumbogram" is an IPv6 packet containing a payload longer than 65,535 octets. This document describes the IPv6 Jumbo Payload option, which provides the method of specifying specified ample payload lengths. It additionally describes the changes needed to TCP and UDP to make use of jumbograms. Jumbograms are applicable lone to IPv6 nodes that may be attached to links alongside a nexus MTU greater than 65,575 octets, and need not be implemented or understood by IPv6 nodes that do not support attachment to links alongside specified ample MTUs. 1. Introduction jumbo (jum'bO), n., pl. -bos, adj. -n. 1. a person, animal, or item extremely ample of its kind. -adj. 2. extremely large: the jumbo box of cereal. [1800-10; orig. uncert.; popularized as the name of a large elephant purchased and exhibited by P.T. Barnum in 1882] -- www.infoplease.com Borman, et al. Standards Track [Page 1]
RFC 2675 IPv6 Jumbograms August 1999 The IPv6 header [IPv6] has a 16-bit Payload Length site and, therefore, supports payloads up to 65,535 octets long. This document specifies an IPv6 hop-by-hop option, called the Jumbo Payload option, that carries a 32-bit dimension site in command to authorize transfer of IPv6 packets alongside payloads between 65,536 and 4,294,967,295 octets in length. Packets alongside specified lengthy payloads are referred to as "jumbograms". The Jumbo Payload choice is applicable lone for IPv6 nodes that may be attached to links alongside a nexus MTU greater than 65,575 octets (that is, 65,535 + 40, anywhere 40 octets is the size of the IPv6 header). The Jumbo Payload choice need not be implemented or understood by IPv6 nodes that do not assistance attachment to links alongside MTU greater than 65,575. On links alongside configurable MTUs, the MTU must not be configured to a value greater than 65,575 octets if there are nodes attached to that nexus that do not assistance the Jumbo Payload choice and it can not be guaranteed that the Jumbo Payload choice volition not be sent to those nodes. The UDP header [UDP] has a 16-bit Length site which prevents it from making use of jumbograms, and although the TCP header [TCP] does not have a Length field, the two the TCP MSS choice and the TCP Urgent field are constrained to 16 bits. This document specifies several simple enhancements to TCP and UDP to allow them to create use of jumbograms. An implementation of TCP or UDP on an IPv6 node that supports the Jumbo Payload choice must contain the enhancements stated here. Note: The 16 bit checksum used by UDP and TCP becomes small accurate as the dimension of the data being checksummed is increased. Application designers may desire to obtain this into consideration. 1.1 Document History This document merges and updates matter that was previously published in two distinct documents: - The specification of the Jumbo Payload choice earlier appeared as part of the IPv6 specification in RFC 1883. RFC 1883 has been superseded by RFC 2460, which no longer includes specification of the Jumbo Payload option. - The specification of TCP and UDP enhancements to support jumbograms earlier appeared as RFC 2147. RFC 2147 is obsoleted by this document. Borman, et al. Standards Track [Page 2]
RFC 2675 IPv6 Jumbograms August 1999 2. Format of the Jumbo Payload Option The Jumbo Payload choice is carried in an IPv6 Hop-by-Hop Options header, immediately following the IPv6 header. This choice has an alignment necessity of 4n + 2. (See [IPv6, Section 4.2] for conversation of choice alignment.) The choice has the following format: +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Option Type | Opt Data Len | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Jumbo Payload Length | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ Option Type 8-bit value C2 (hexadecimal). Opt Data Len 8-bit value 4. Jumbo Payload Length 32-bit unsigned integer. Length of the IPv6 packet in octets, excluding the IPv6 header but including the Hop-by-Hop Options header and any another expansion headers present. Must be greater than 65,535. 3. Usage of the Jumbo Payload Option The Payload Length site in the IPv6 header must be set to zero in all packet that carries the Jumbo Payload option. If a node that understands the Jumbo Payload choice receives a packet whose IPv6 header carries a Payload Length of zero and a Next Header value of zero (meaning that a Hop-by-Hop Options header follows), and whose link-layer framing indicates the existence of octets beyond the IPv6 header, the node must continue to procedure the Hop-by-Hop Options header in command to decide the genuine dimension of the payload from the Jumbo Payload option. The Jumbo Payload choice must not be used in a packet that carries a Fragment header. Higher-layer protocols that use the IPv6 Payload Length site to compute the value of the Upper-Layer Packet Length site in the checksum pseudo-header described in [IPv6, Section 8.1] must instead use the Jumbo Payload Length site for that computation, for packets that transport the Jumbo Payload option. Borman, et al. Standards Track [Page 3]
RFC 2675 IPv6 Jumbograms August 1999 Nodes that comprehend the Jumbo Payload choice are required to detect a figure of imaginable format errors, and if the erroneous packet was not destined to a multicast address, study the error by sending an ICMP Parameter Problem communication [ICMPv6] to the packet's source. The following catalog of errors specifies the values to be used in the Code and Pointer sectors of the Parameter Problem message: error: IPv6 Payload Length = 0 and IPv6 Next Header = Hop-by-Hop Options and Jumbo Payload choice not present Code: 0 Pointer: high-order octet of the IPv6 Payload Length error: IPv6 Payload Length != 0 and Jumbo Payload choice present Code: 0 Pointer: Option Type site of the Jumbo Payload option error: Jumbo Payload choice current and Jumbo Payload Length < 65,536 Code: 0 Pointer: high-order octet of the Jumbo Payload Length error: Jumbo Payload choice current and Fragment header present Code: 0 Pointer: high-order octet of the Fragment header. A node that does not comprehend the Jumbo Payload choice is expected to react to erroneously-received jumbograms as follows, according to the IPv6 specification: error: IPv6 Payload Length = 0 and IPv6 Next Header = Hop-by-Hop Options Code: 0 Pointer: high-order octet of the IPv6 Payload Length error: IPv6 Payload Length != 0 and Jumbo Payload choice present Code: 2 Pointer: Option Type site of the Jumbo Payload option Borman, et al. Standards Track [Page 4]
RFC 2675 IPv6 Jumbograms August 1999 4. UDP Jumbograms The 16-bit Length site of the UDP header limits the total dimension of a UDP packet (that is, a UDP header affirmative data) to no greater than 65,535 octets. This document specifies the following modification of UDP to unwind that limit: UDP packets longer than 65,535 octets may be sent by environment the UDP Length site to zero, and letting the receiver get the genuine UDP packet dimension from the IPv6 payload length. (Note that, previous to this modification, zero was not a legal value for the UDP Length field, since the UDP packet length includes the UDP header and hence has a minimum value of 8.) The particular requirements for sending a UDP jumbogram are as follows: When sending a UDP packet, if and lone if the dimension of the UDP header affirmative UDP data is greater than 65,535, set the Length field in the UDP header to zero. The IPv6 packet carrying specified a ample UDP packet volition necessarily contain a Jumbo Payload choice in a Hop-by-Hop Options header; set the Jumbo Payload Length site of that choice to be the actual dimension of the UDP header affirmative data, affirmative the dimension of all IPv6 expansion headers current between the IPv6 header and the UDP header. For generating the UDP checksum, use the genuine dimension of the UDP header affirmative data, NOT zero, in the checksum pseudo-header [IPv6, Section 8.1]. The particular requirements for receiving a UDP jumbogram are as follows: When receiving a UDP packet, if and lone if the Length site in the UDP header is zero, compute the genuine dimension of the UDP header affirmative data from the IPv6 Jumbo Payload Length site minus the dimension of all expansion headers current between the IPv6 header and the UDP header. In the unexpected case that the UDP Length site is zero but no Jumbo Payload choice is current (i.e., the IPv6 packet is not a jumbogram), use the Payload Length site in the IPv6 header, in location of the Jumbo Payload Length field, in the complete calculation. For verifying the received UDP checksum, use the calculated length of the UDP header affirmative data, NOT zero, in the checksum pseudo- header. Borman, et al. Standards Track [Page 5]
RFC 2675 IPv6 Jumbograms August 1999 5. TCP Jumbograms Because there is no dimension site in the TCP header, there is nothing limiting the dimension of an idiosyncratic TCP packet. However, the MSS value that is negotiated at the commencement of the association limits the largest TCP packet that can be sent, and the Urgent Pointer cannot citation data beyond 65,535 bytes. 5.1 TCP MSS When determining what MSS value to send, if the MTU of the directly attached interface minus 60 [IPv6, Section 8.3] is greater than or equal to 65,535, afterward set the MSS value to 65,535. When an MSS value of 65,535 is received, it is to be treated as infinity. The genuine MSS is resolute by subtracting 60 from the value learned by performing Path MTU Discovery [MTU-DISC] complete the way to the TCP peer. 5.2 TCP Urgent Pointer The Urgent Pointer issue could be fixed by adding a TCP Urgent Pointer Option. However, since it is improbable that applications using jumbograms volition additionally use Urgent Pointers, a small intrusive alter akin to the MSS alter volition suffice. When a TCP packet is to be sent alongside an Urgent Pointer (i.e., the URG bit set), archetypal compute the offset from the Sequence Number to the Urgent Pointer. If the offset is small than 65,535, inhabit in the Urgent site and continue alongside the normal TCP processing. If the offset is greater than 65,535, and the offset is greater than or equal to the dimension of the TCP data, inhabit in the Urgent Pointer with 65,535 and continue alongside the normal TCP processing. Otherwise, the TCP packet must be divided into two pieces. The archetypal part contains data up to, but not including the data pointed to by the Urgent Pointer, and the Urgent site is set to 65,535 to signify that the Urgent Pointer is beyond the end of this packet. The second piece can afterward be sent alongside the Urgent site set normally. Note: The archetypal part does not have to contain all of the data up to the Urgent Pointer. It can be shorter, fair as lengthy as it ends inside 65,534 bytes of the Urgent Pointer, so that the offset to the Urgent Pointer in the second part volition be small than 65,535 bytes. For TCP input processing, whenever a TCP packet is received alongside the URG bit set and an Urgent site of 65,535, the Urgent Pointer is calculated using an offset equal to the dimension of the TCP data, fairly than the offset in the Urgent field. Borman, et al. Standards Track [Page 6]
RFC 2675 IPv6 Jumbograms August 1999 It should additionally be noted that although the TCP opening is lone 16-bits, larger windows can be used through use of the TCP Window Scale option [TCP-EXT]. 6. Security Considerations The Jumbo Payload choice and TCP/UDP jumbograms do not current any known new safety concerns. 7. Authors' Addresses David A. Borman Berkeley Software Design, Inc. 4719 Weston Hills Drive Eagan, MN 55123 USA Phone: +1 612 405 8194 EMail: [email protected] Stephen E. Deering Cisco Systems, Inc. 170 West Tasman Drive San Jose, CA 95134-1706 USA Phone: +1 408 527 8213 EMail: [email protected] Robert M. Hinden Nokia 313 Fairchild Drive Mountain View, CA 94043 USA Phone: +1 650 625 2004 EMail: [email protected] Borman, et al. Standards Track [Page 7]
RFC 2675 IPv6 Jumbograms August 1999 8. References [ICMPv6] Conta, A. and S. Deering, "ICMP for the Internet Protocol Version 6 (IPv6)", RFC 2463, December 1998. [IPv6] Deering, S. and R. Hinden, "Internet Protocol Version 6 (IPv6) Specification", RFC 2460, December 1998. [MTU-DISC] McCann, J., Deering, S. and J. Mogul, "Path MTU Discovery for IP Version 6", RFC 1981, August 1986. [TCP] Postel, J., "Transmission Control Protocol", STD 7, RFC 793, September 1981. [TCP-EXT] Jacobson, V., Braden, R. and D. Borman, "TCP Extensions for High Performance", RFC 1323, May 1992. [UDP] Postel, J., "User Datagram Protocol", STD 6, RFC 768, August 1980. Borman, et al. Standards Track [Page 8]
RFC 2675 IPv6 Jumbograms August 1999 9. Full Copyright Statement Copyright (C) The Internet Society (1999). All Rights Reserved. This document and translations of it may be copied and furnished to others, and derivative plant that comment on or alternatively explain it or assistance in its implementation may be prepared, copied, published and distributed, in entire or in part, without limitation of any kind, provided that the complete copyright notice and this paragraph are included on all specified copies and derivative works. However, this document itself may not be modified in any way, specified as by removing the copyright notice or references to the Internet Society or other Internet organizations, apart from as needed for the intent of evolving Internet standards in which case the procedures for copyrights defined in the Internet Standards procedure must be followed, or as required to translate it into languages another than English. The constricted permissions granted complete are perpetual and volition not be revoked by the Internet Society or its successors or assigns. This document and the data contained herein is provided on an "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Acknowledgement Funding for the RFC Editor function is currently provided by the Internet Society. Borman, et al. Standards Track [Page 9]