RFC 6598: IANA-Reserved IPv4 Prefix for Shared Address Space
In plain English — editorial summary, not part of the RFC
This document requests the allocation of an IPv4 /10 address block to be used as Shared Address Space to accommodate the needs of Carrier- Grade NAT (CGN) devices. It is anticipated that Service Providers will use this Shared Address Space to number the interfaces that connect CGN devices to Customer Premises Equipment (CPE). Shared Address Space is distinct from RFC 1918 private address space because it is intended for use on Service Provider networks. However, it may be used in a manner similar to RFC 1918 private address space on routing equipment that is able to do address translation across router interfaces when the addresses are identical on two different interfaces. Details are provided in the text of this document. This document details the allocation of an additional special-use IPv4 address block and updates RFC 5735. This memo documents an Internet Best Current Practice.
Document record
- Document ID
- RFC6598
- Published
- April 2012
- Authors
- J. Weil; V. Kuarsingh; C. Donley; C. Liljenstolpe; M. Azinger
- Status
- BEST CURRENT PRACTICE
- Stream
- IETF
- Area
- —
- Pages
- 11
- Also known as
- BCP153
- Updates:
- RFC 5735
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 6888Common Requirements for Carrier-Grade NATs (CGNs)Current
April 2013
- RFC 7648Port Control Protocol (PCP) Proxy FunctionCurrent
September 2015
- RFC 7857Updates to Network Address Translation (NAT) Behavioral RequirementsCurrent
April 2016
- RFC 8045RADIUS Extensions for IP Port Configuration and ReportingCurrent
January 2017
- RFC 3519Mobile IP Traversal of Network Address Translation (NAT) DevicesCurrent
May 2003
- RFC 7021Assessing the Impact of Carrier-Grade NAT on Network ApplicationsCurrent
September 2013
- RFC 6619Scalable Operation of Address Translators with Per-Interface BindingsCurrent
June 2012
- RFC 6544TCP Candidates with Interactive Connectivity Establishment (ICE)Current
March 2012
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?