The IPv4 Identification (ID) field enables fragmentation and
reassembly, and as currently specified is required to be unique
within the maximum lifetime for all datagrams with a given
source/destination/protocol tuple. If enforced, this uniqueness
requirement would limit all connections to 6.4 Mbps. Because
individual connections commonly exceed this speed, it is clear that
existing systems violate the current specification. This document
updates the specification of the IPv4 ID field in RFC791, RFC1122,
and RFC2003 to more closely reflect current practice and to more
closely match IPv6 so that the field's value is defined only when a
datagram is actually fragmented. It also discusses the impact of
these changes on how datagrams are used.
Working Group Summary
The normal WG process was followed and the document as it stands now
reflects WG consensus with nothing special worth mentioning.
The document was given adequate reviews. The Document Shepherd has
no concerns about the depth or breadth of these reviews.
The Document Shepherd for this document Julien Laganier. The responsible
Area Director is Brian Haberman.
RFC Editor Note
Reordering is typically associated with routing transients or where multiple
alternate paths exist.
Reordering is typically associated with routing transients or where flows are
split across multiple paths.