Updated Specification of the IPv4 ID Field
draft-ietf-intarea-ipv4-id-update-06
The information below is for an old version of the document | |||
---|---|---|---|
Document | Type | Active Internet-Draft (intarea WG) | |
Last updated | 2012-11-26 (latest revision 2012-10-09) | ||
Replaces | draft-touch-intarea-ipv4-unique-id | ||
Stream | IETF | ||
Intended RFC status | Proposed Standard | ||
Formats | plain text pdf html bibtex | ||
Stream | WG state | Submitted to IESG for Publication | |
Document shepherd | Julien Laganier | ||
Shepherd write-up | Show (last changed 2012-05-03) | ||
IESG | IESG state | IESG Evaluation::Revised I-D Needed | |
Consensus Boilerplate | Unknown | ||
Telechat date |
Needs a YES. Needs 10 more YES or NO OBJECTION positions to pass. |
||
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 |
Internet Area WG J. Touch Internet Draft USC/ISI Updates: 791,1122,2003 October 9, 2012 Intended status: Proposed Standard Expires: April 2013 Updated Specification of the IPv4 ID Field draft-ietf-intarea-ipv4-id-update-06.txt Status of this Memo This Internet-Draft is submitted to IETF in full conformance with the provisions of BCP 78 and BCP 79. This document may contain material from IETF Documents or IETF Contributions published or made publicly available before November 10, 2008. The person(s) controlling the copyright in some of this material may not have granted the IETF Trust the right to allow modifications of such material outside the IETF Standards Process. Without obtaining an adequate license from the person(s) controlling the copyright in such materials, this document may not be modified outside the IETF Standards Process, and derivative works of it may not be created outside the IETF Standards Process, except to format it for publication as an RFC or to translate it into languages other than English. Internet-Drafts are working documents of the Internet Engineering Task Force (IETF), its areas, and its working groups. Note that other groups may also distribute working documents as Internet- Drafts. Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress." The list of current Internet-Drafts can be accessed at http://www.ietf.org/ietf/1id-abstracts.txt The list of Internet-Draft Shadow Directories can be accessed at http://www.ietf.org/shadow.html This Internet-Draft will expire on April 9, 2013. Touch Expires April 9, 2013 [Page 1] Internet-Draft Updated Spec. of the IPv4 ID Field October 2012 Copyright Notice Copyright (c) 2012 IETF Trust and the persons identified as the document authors. All rights reserved. This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License. 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/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. Table of Contents 1. Introduction...................................................3 2. Conventions used in this document..............................3 3. The IPv4 ID Field..............................................4 3.1. Uses of the IPv4 ID Field.................................4 3.2. Background on IPv4 ID Reassembly Issues...................5 4. Updates to the IPv4 ID Specification...........................6 4.1. IPv4 ID Used Only for Fragmentation.......................7 4.2. Encourage Safe IPv4 ID Use................................8 4.3. IPv4 ID Requirements That Persist.........................8 5. Impact of Proposed Changes.....................................9 5.1. Impact on Legacy Internet Devices.........................9 5.2. Impact on Datagram Generation............................10 5.3. Impact on Middleboxes....................................11 5.3.1. Rewriting Middleboxes...............................11 Touch Expires April 9, 2013 [Page 2] Internet-Draft Updated Spec. of the IPv4 ID Field October 2012 5.3.2. Filtering Middleboxes...............................12 5.4. Impact on Header Compression.............................13 6. Updates to Existing Standards.................................13Show full document text