A new Request for Comments is now available in online RFC libraries. BCP 12: RFC 2050: Title: INTERNET REGISTRY IP ALLOCATION GUIDELINES Author: K. Hubbard, M. Kosters, D. Conrad, D. Karrenberg, J. Postel Date: November 1996 Mailbox: kimh@internic.net, markk@internic.net, davidc@APNIC.NET, dfk@RIPE.NET, Postel@ISI.EDU Pages: 13 Characters: 28,975 Updates/Obsoletes: 1466 URL: ftp://ds.internic.net/rfc/rfc2050.txt This document describes the registry system for the distribution of globally unique Internet address space and registry operations. Particularly this document describes the rules and guidelines governing the distribution of this address space. This RFC is a product of the CIDR Deployment Working Group of the IETF. IESG Note: By approving this document as a Best Current Practice,the IESG asserts its belief that this policy described herein is an accurate representation of the current practice of the IP address registries with respect to address assignment. This does not constitute endorsement or recommendation of this policy by the IESG. The IESG will reevaluate its approval of this document in December 1997 taking into consideration the results of the discussions that will be take place in the IRE Working Group between now and then. 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