Issues with Private IP Addressing in the Internet
RFC 6752, “Issues with Private IP Addressing in the Internet”, is an Informational document published in September 2012 by A. Kirkham. The canonical text is published by the RFC Editor.
Abstract
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.
What “Informational” means
Published for the general information of the community. It does not define an IETF standard and carries no standards-track status.
The canonical text of RFC 6752 is hosted at rfc-editor.org. Available in TXT,HTML.
- RFC 6751 Native IPv6 behind IPv4-to-IPv4 NAT Customer Premises Equipment
- RFC 6753 A Location Dereference Protocol Using HTTP-Enabled Location Delivery
- RFC 6750 The OAuth 2.0 Authorization Framework: Bearer Token Usage
- RFC 6754 Protocol Independent Multicast Equal-Cost Multipath Redirect
- RFC 6749 The OAuth 2.0 Authorization Framework
- RFC 6755 An IETF URN Sub-Namespace for OAuth
- RFC 6748 Optional Advanced Deployment Scenarios for the Identifier-Locator Network Protocol
- RFC 6756 Internet Engineering Task Force and International Telecommunication Union - Telecommunication Standardization Sector Collaboration Guidelines