RFC 6752: Issues with Private IP Addressing in the Internet
In plain English — editorial summary, not part of the RFC
The purpose of this document is to provide a discussion of the potential problems of using private, RFC 1918, or non-globally routable addressing within the core of a Service Provider (SP) network. The discussion focuses on link addresses and, to a small extent, loopback addresses. While many of the issues are well recognised within the ISP community, there appears to be no document that collectively describes the issues. This document is not an Internet Standards Track specification; it is published for informational purposes.
Document record
- Document ID
- RFC6752
- Published
- September 2012
- Authors
- A. Kirkham
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- ops
- Pages
- 14
- Also known as
- —
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 6765xDSL Multi-Pair Bonding (G.Bond) MIBCurrent
February 2013
- RFC 6738Diameter IKEv2 SK: Using Shared Keys to Support Interaction between IKEv2 Servers and Diameter ServersCurrent
October 2012
- RFC 6766xDSL Multi-Pair Bonding Using Time-Division Inverse Multiplexing (G.Bond/TDIM) MIBCurrent
February 2013
- RFC 6767Ethernet-Based xDSL Multi-Pair Bonding (G.Bond/Ethernet) MIBCurrent
February 2013
- RFC 6737The Diameter Capabilities Update ApplicationCurrent
October 2012
- RFC 6736Diameter Network Address and Port Translation Control ApplicationCurrent
October 2012
- RFC 6768ATM-Based xDSL Bonded Interfaces MIBCurrent
February 2013
- RFC 6735Diameter Priority Attribute-Value PairsCurrent
October 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?