RFC 6619: Scalable Operation of Address Translators with Per-Interface Bindings
In plain English — editorial summary, not part of the RFC
This document explains how to employ address translation in networks that serve a large number of individual customers without requiring a correspondingly large amount of private IPv4 address space. [STANDARDS-TRACK]
Document record
- Document ID
- RFC6619
- Published
- June 2012
- Authors
- J. Arkko; L. Eggert; M. Townsley
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- —
- Pages
- 9
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 6535Dual-Stack Hosts Using "Bump-in-the-Host" (BIH)Current
February 2012
- RFC 7934Host Address Availability RecommendationsCurrent
July 2016
- RFC 7021Assessing the Impact of Carrier-Grade NAT on Network ApplicationsCurrent
September 2013
- RFC 6556Testing Eyeball HappinessCurrent
April 2012
- RFC 6145IP/ICMP Translation AlgorithmObsoleted
April 2011
- RFC 6081Teredo ExtensionsCurrent
January 2011
- RFC 7341DHCPv4-over-DHCPv6 (DHCP 4o6) TransportCurrent
August 2014
- RFC 7484Finding the Authoritative Registration Data (RDAP) ServiceObsoleted
March 2015
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?