FYI 37, RFC 2901 on Administrative Internet Infrastructure Guide

RFC Editor <rfc-ed@ISI.EDU> Fri, 01 September 2000 21:18 UTC

Received: from loki.ietf.org (loki [10.27.2.29]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA20399; Fri, 1 Sep 2000 17:18:09 -0400 (EDT)
Received: (from adm@localhost) by loki.ietf.org (8.9.1b+Sun/8.9.1) id RAA05201 for ietf-123-outbound.10@ietf.org; Fri, 1 Sep 2000 17:15:03 -0400 (EDT)
Received: from ietf.org (odin.ietf.org [10.27.2.28]) by loki.ietf.org (8.9.1b+Sun/8.9.1) with ESMTP id RAA05129 for <all-ietf@loki.ietf.org>; Fri, 1 Sep 2000 17:03:26 -0400 (EDT)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA20088 for <all-ietf@ietf.org>; Fri, 1 Sep 2000 17:03:21 -0400 (EDT)
Received: from ISI.EDU (jet.isi.edu [128.9.160.87]) by boreas.isi.edu (8.9.3/8.9.3) with ESMTP id OAA20075; Fri, 1 Sep 2000 14:02:52 -0700 (PDT)
Message-Id: <200009012102.OAA20075@boreas.isi.edu>
To: IETF-Announce:;
Subject: FYI 37, RFC 2901 on Administrative Internet Infrastructure Guide
Cc: rfc-ed@ISI.EDU
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
Date: Fri, 01 Sep 2000 14:02:52 -0700
From: RFC Editor <rfc-ed@ISI.EDU>

A new Request for Comments is now available in online RFC libraries.


        FYI 37
        RFC 2901

        Title:	    Guide to Administrative Procedures of the Internet
                    Infrastructure
        Author(s):  Z. Wenzel, J. Klensin, R. Bush, S. Huter
        Status:     Informational
	Date:       August 2000
        Mailbox:    zita@nsrc.org, klensin@nsrc.org, randy@nsrc.org,
                    sghuter@nsrc.org 
        Pages:      31
        Characters: 63680
        Updates/Obsoletes/SeeAlso:  None

        I-D Tag:    draft-wenzel-nsrc-03.txt

        URL:        ftp://ftp.isi.edu/in-notes/rfc2901.txt


This document describes the administrative procedures for networks
seeking to connect to the global Internet.  This includes the steps
and operations necessary for address space allocation and
registration, routing database registration, and domain name
registration.  The document also contains information about the
required forms and how to obtain them.

This memo provides information for the Internet community.  It does
not specify an Internet standard of any kind.  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@IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG.

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 
help: ways_to_get_rfcs.  For example:

        To: rfc-info@RFC-EDITOR.ORG
        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 RFC-Manager@RFC-EDITOR.ORG.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.echo 
Submissions for Requests for Comments should be sent to
RFC-EDITOR@RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.


Joyce K. Reynolds and Sandy Ginoza
USC/Information Sciences Institute

...

Below is the data which will enable a MIME compliant Mail Reader 
implementation to automatically retrieve the ASCII version
of the RFCs.
ftp://ftp.isi.edu/in-notes/rfc2901.txt"><ftp://ftp.isi.edu/in-notes/rfc2901.txt>