An Architecture for SIPP-16 Address Allocation
draft-rekhter-arch-sipp16-addr-00

Document Type Expired Internet-Draft (individual)
Last updated 1994-07-19
Stream (None)
Intended RFC status (None)
Formats
Expired & archived
plain text pdf html bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Expired
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at
https://www.ietf.org/archive/id/draft-rekhter-arch-sipp16-addr-00.txt

Abstract

This paper provides an architecture for allocating IPng addresses in the Internet. This paper does not go into the details of an addressing plan. This paper focuses on addressing for a particular proposal known as SIPP-16, but the general principles apply to any hierarchically allocated address space. The IPng address space is a finite shared resource that must be managed for the good of the community. The managers of this resource are acting as its custodians. They have a responsibility to the community to manage it for the common good.

Authors

Tony Li (tli@cisco.com)
Yakov Rekhter (yakov@juniper.net)

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)