Hierarchical IPv4 Framework
RFC 6306
Revision differences
Document history
Date | By | Action |
---|---|---|
2018-12-20
|
(System) | Received changes through RFC Editor sync (changed abstract to 'This document describes a framework for how the current IPv4 address space can be divided into … Received changes through RFC Editor sync (changed abstract to 'This document describes a framework for how the current IPv4 address space can be divided into two new address categories: a core address space (Area Locators, ALOCs) that is globally unique, and an edge address space (Endpoint Locators, ELOCs) that is regionally unique. In the future, the ELOC space will only be significant in a private network or in a service provider domain. Therefore, a 32x32 bit addressing scheme and a hierarchical routing architecture are achieved. The hierarchical IPv4 framework is backwards compatible with the current IPv4 Internet. This document also discusses a method for decoupling the location and identifier functions -- future applications can make use of the separation. The framework requires extensions to the existing Domain Name System (DNS), the existing IPv4 stack of the endpoints, middleboxes, and routers in the Internet. The framework can be implemented incrementally for endpoints, DNS, middleboxes, and routers. This document defines an Experimental Protocol for the Internet community.') |
2015-10-14
|
(System) | Notify list changed from pfrejborg@gmail.com, draft-frejborg-hipv4@ietf.org, tony.li@tony.li to tony.li@tony.li |
2011-11-28
|
Cindy Morgan | Setting stream while adding document to the tracker |
2011-11-28
|
Cindy Morgan | Stream changed to IRTF from ISE |
2011-07-11
|
Amy Vezza | State changed to RFC Published from RFC Ed Queue. RFC 6306 |
2011-07-08
|
(System) | RFC published |