On the Assignment of Provider Rooted Addresses
draft-ietf-pip-provider-addr-00
| Document | Type |
Expired Internet-Draft
(pip WG)
Expired & archived
|
|
|---|---|---|---|
| Author | Paul Francis | ||
| Last updated | 1993-03-22 | ||
| RFC stream | Internet Engineering Task Force (IETF) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Additional resources | thumper.bellcore.com%3A~/pub/tsuchiya/pip-archive | ||
| Stream | WG state | WG Document | |
| Document shepherd | (None) | ||
| IESG | IESG state | Expired | |
| Consensus boilerplate | Unknown | ||
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
There is an ongoing debate in the IETF about the pros and cons of provider versus geographically assigned addresses. This paper describes the characteristics of provider-rooted address assignment, and compares it with geographical address assignment.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)