home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Internet Info 1997 December
/
Internet_Info_CD-ROM_Walnut_Creek_December_1997.iso
/
drafts
/
draft_ietf_a_c
/
draft-ietf-cidrd-addr-ownership-07.txt
< prev
next >
Wrap
Text File
|
1996-10-17
|
3KB
|
71 lines
A new Request for Comments is now available in online RFC libraries.
BCP 7:
RFC 2008:
Title: Implications of Various Address Allocation
Policies for Internet Routing
Author: Y. Rekhter, T. Li
Date: October 1996
Mailbox: yakov@cisco.com, tli@cisco.com
Pages: 13
Characters: 34,717
Updates/Obsoletes: None
URL: ftp://ds.internic.net/rfc/rfc2008.txt
The purpose of this document is to articulate certain relevant
fundamental technical issues that must be considered in formulating
unicast address allocation and management policies for the Public
Internet, and to provide recommendations with respect to these
policies. This RFC is a product of the CIDR Deployment Working Group
of the IETF.
IESG Note: The addressing constraints described in this document are
largely the result of the interaction of existing router technology,
address assignment, and architectural history. After extensive review
and discussion, the authors of this document, the IETF working group
that reviewed it, and the IESG have concluded that there are no other
currently deployable technologies available to overcome these
limitations. In the event that routing or router technology develops
to the point that adequate routing aggregation can be achieved by
other means or that routers can deal with larger routing and more
dynamic tables, it may be appropriate to review these constraints.
This document specifies an Internet Best Current Practices for the
Internet Community, and requests discussion and suggestions for
improvements. Distribution of this memo is unlimited.
This announcement is sent to the IETF list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST@CNRI.RESTON.VA.US. Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST@ISI.EDU.
Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info@ISI.EDU with the message body
help: ways_to_get_rfcs. For example:
To: rfc-info@ISI.EDU
Subject: getting rfcs
help: ways_to_get_rfcs
Requests for special distribution should be addressed to either the
author of the RFC in question, or to admin@DS.INTERNIC.NET. Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.
Submissions for Requests for Comments should be sent to
RFC-EDITOR@ISI.EDU. Please consult RFC 1543, Instructions to RFC
Authors, for further information.
Joyce K. Reynolds and Mary Kennedy
USC/Information Sciences Institute