API Build-data JSON Resources
Theme

Choose how MSRBot.io looks on this device.

Auto (match system) Light mode Dark mode

Preference is stored in this browser only.

IETF RFC 6864
[ACTIVE]

Updated Specification of the IPv4 ID Field

Metadata

Publisher
IETF
Doc Type
Standard
Pages
19
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]
Publication Date
2013-02-01
Status Note
Proposed Standard
DOI
10.17487/RFC6864
Link
https://doi.org/10.17487/RFC6864
Author(s)
Dr. Joseph D. Touch
Latest version of IETF RFC 6864

Document Versions — IETF RFC 6864

  • ▶ IETF RFC 6864 (2013-02-01)
    THIS DOC [ACTIVE] [LATEST VERSION]

Normative Reference(s)

Bibliographic Reference(s)

  • Despres, R., Ed., Matsushima, S., Murakami, T., and O. Troan, "IPv4 Residual Deployment across IPv6-Service networks (4rd) ISP-NAT's made optional", Work in Progress, March 2011. EXTERNAL
  • Perreault, S., Ed., Yamagata, I., Miyakawa, S., Nakagawa, A., and H. Ashida, "Common requirements for Carrier Grade NATs (CGNs)", Work in Progress, December 2012. EXTERNAL
  • Bellovin, S., "A Technique for Counting NATted Hosts", Internet Measurement Conference, Proceedings of the 2nd ACM SIGCOMM Workshop on Internet Measurement, November 2002. EXTERNAL
  • Boucadair, M., Touch, J., Levis, P., and R. Penno, "Analysis of Solution Candidates to Reveal a Host Identifier in Shared Address Deployments", Work in Progress, September 2011. EXTERNAL
  • IETF RFC 1144 [Active*]
  • IETF RFC 2460 [Superseded*]
  • IETF RFC 2508 [Active*]
  • IETF RFC 2671 [Superseded*]
  • IETF RFC 3022 [Active*]
  • IETF RFC 3545 [Active*]
  • IETF RFC 3828 [Active*]
  • IETF RFC 4301 [Active, Amended*]
  • IETF RFC 4302 [Active*]
  • IETF RFC 4443 [Active*]
  • IETF RFC 4960 [Superseded*]
  • RFC4963 — RFC4963 EXTERNAL
  • RFC5225 — RFC5225 EXTERNAL
  • RFC5320 — RFC5320 EXTERNAL
  • IETF RFC 6145 [Superseded*]
  • RFC6219 — RFC6219 EXTERNAL
  • RFC6621 — RFC6621 EXTERNAL
Source Data (JSON)

Full registry record with provenance metadata. Open directly: /api/doc/RFC6864.json

Reference Tree

Explore all references and references to this document, as a navigable tree.

Open Reference Tree
Reference this Doc

Plain text (ISO 690 compliant)

Preview:
IETF RFC 6864, Updated Specification of the IPv4 ID Field. Available at https://doi.org/10.17487/RFC6864
Snippet:
IETF RFC 6864, Updated Specification of the IPv4 ID Field. Available at https://doi.org/10.17487/RFC6864

HTML (ISO 690 compliant)

Preview:
IETF RFC 6864, Updated Specification of the IPv4 ID Field. Available at https://doi.org/10.17487/RFC6864
Snippet:
<span class="citation"><cite>IETF RFC 6864</cite>, Updated Specification of the IPv4 ID Field. Available at <a href="https://doi.org/10.17487/RFC6864" target="_blank" rel="noopener">https://doi.org/10.17487/RFC6864</a></span>

SMPTE Icon SMPTE's HTML Pub

Preview:
IETF RFC 6864, Updated Specification of the IPv4 ID Field
doi: 10.17487/RFC6864
url: https://doi.org/10.17487/RFC6864
Snippet:
<li>
<cite id="bib-rfc6864">IETF RFC 6864</cite>, Updated Specification of the IPv4 ID Field
<span class="doi">10.17487/RFC6864</span>
</li>

Referenced By