datatracker.ietf.org
Sign In
Version 4.50, 2013-05-15
Report a bug

Updated Specification of the IPv4 ID Field
draft-ietf-intarea-ipv4-id-update-07

RFC
Document Stream: IETF
Last updated: 2012-11-27
Replaces: draft-touch-intarea-ipv4-unique-id
Intended RFC status: Proposed Standard
Other versions: (expired, archived): plain text, pdf, html

IETF State: Submitted to IESG for Publication (intarea)
Document shepherd:Julien Laganier
Shepherd writeup
Consensus:Unknown

IESG State: RFC 6864
IANA Action State: No IC 
On agenda of 2012-07-05 IESG telechat
Responsible AD: Brian Haberman
IESG Note: The Document Shepherd is Julien Laganier (julien.ietf@gmail.com).
Send notices to: intarea-chairs@tools.ietf.org, draft-ietf-intarea-ipv4-id-update.notify@tools.ietf.org

This Internet-Draft is no longer active. Unofficial copies of old Internet-Drafts can be found here:
http://tools.ietf.org/id/draft-ietf-intarea-ipv4-id-update.

Abstract:
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 address/destination address/protocol tuple. If enforced, this uniqueness requirement would limit all connections to 6.4 Mbps for typical datagram sizes. 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 RFCs 791, 1122, and 2003 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. [STANDARDS-TRACK]

Authors:
Joseph Touch <touch@isi.edu>

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid)