RFC 6250: Evolution of the IP Model
In plain English — editorial summary, not part of the RFC
This RFC attempts to document various aspects of the IP service model and how it has evolved over time. In particular, it attempts to document the properties of the IP layer as they are seen by upper- layer protocols and applications, especially properties that were (and, at times, still are) incorrectly perceived to exist as well as properties that would cause problems if changed. The discussion of these properties is organized around evaluating a set of claims, or misconceptions. Finally, this document provides some guidance to protocol designers and implementers. This document is not an Internet Standards Track specification; it is published for informational purposes.
Document record
- Document ID
- RFC6250
- Published
- May 2011
- Authors
- D. Thaler
- Status
- INFORMATIONAL
- Stream
- IAB
- Area
- —
- Pages
- 25
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 3056Connection of IPv6 Domains via IPv4 CloudsCurrent
February 2001
- RFC 2765Stateless IP/ICMP Translation Algorithm (SIIT)Obsoleted
February 2000
- RFC 6275Mobility Support in IPv6Current
July 2011
- RFC 6145IP/ICMP Translation AlgorithmObsoleted
April 2011
- RFC 6535Dual-Stack Hosts Using "Bump-in-the-Host" (BIH)Current
February 2012
- RFC 6556Testing Eyeball HappinessCurrent
April 2012
- RFC 6619Scalable Operation of Address Translators with Per-Interface BindingsCurrent
June 2012
- RFC 5579Transmission of IPv4 Packets over Intra-Site Automatic Tunnel Addressing Protocol (ISATAP) InterfacesCurrent
February 2010
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?