Search RFCs

RFC Editor

File formats:

Status:

PROPOSED STANDARD

Updates:

RFC 791,RFC 1122,RFC 2003

Author:

J. Touch

Stream:

IETF

Source:

intarea (int)

Cite this RFC:TXT  | XML  |  BibTeX

DOI:  https://doi.org/10.17487/RFC6864

Discuss this RFC: Send questions or comments to the mailing listint-area@ietf.org

Other actions:Submit Errata  | Find IPR Disclosures from the IETF  | View History of RFC 6864

Abstract

The IPv4 Identification (ID) field enables fragmentation andreassembly and, as currently specified, is required to be uniquewithin the maximum lifetime for all datagrams with a givensource address/destination address/protocol tuple. If enforced,this uniqueness requirement would limit all connections to 6.4 Mbpsfor typical datagram sizes. Because individual connectionscommonly exceed this speed, it is clear that existing systemsviolate the current specification. This document updatesthe specification of the IPv4 ID field in RFCs 791, 1122,and 2003 to more closely reflect current practice and to moreclosely match IPv6 so that the field's value is defined only when adatagram is actually fragmented. It also discusses the impact ofthese changes on how datagrams are used. [STANDARDS-TRACK]

For the definition ofStatus,seeRFC 2026.

For the definition ofStream, seeRFC 8729.