Skip to main content

6. Relevant Work

This document builds upon previous work and is related to other Internet standards:

  • RFC 1597: The predecessor obsoleted by this document, which defined similar private address space.
  • RFC 1627: Also obsoleted by this document.
  • RFC 1519: Classless Inter-Domain Routing (CIDR), which provides a framework for address aggregation.
  • RFC 1812: Requirements for IPv4 Routers, covering how routers should handle private addresses.

6.2 Network Address Translation (NAT)​

The development of NAT technology is closely related to the use of private address space. NAT allows internal networks using private addresses to access the public Internet while maintaining the privacy of internal address structures.

6.3 IPv6 Transition​

Although this document focuses on IPv4, the concept of private address space has related considerations in IPv6 transition plans. IPv6 provides a much larger address space but still reserves address ranges for local use (such as Unique Local Addresses - ULA).

6.4 Security Considerations​

The use of private address space is related to network security policies, particularly in firewall configuration and access control. Enterprises should incorporate the use of private address space into their overall security architecture.

Last updated on