RFC 3232 on RFC 1700 Replaced by On-line Database

RFC Editor <rfc-ed@ISI.EDU> Fri, 25 January 2002 00:57 UTC

Received: from loki.ietf.org (loki [10.27.2.29]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA10938; Thu, 24 Jan 2002 19:57:55 -0500 (EST)
Received: (from adm@localhost) by loki.ietf.org (8.9.1b+Sun/8.9.1) id TAA08717 for ietf-123-outbound.10@ietf.org; Thu, 24 Jan 2002 19:55:01 -0500 (EST)
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 TAA08695 for <all-ietf@loki.ietf.org>; Thu, 24 Jan 2002 19:54:07 -0500 (EST)
Received: from gamma.isi.edu (gamma.isi.edu [128.9.144.145]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA10888 for <all-ietf@ietf.org>; Thu, 24 Jan 2002 19:54:04 -0500 (EST)
Received: from ISI.EDU (jet.isi.edu [128.9.160.87]) by gamma.isi.edu (8.11.6/8.11.2) with ESMTP id g0P0s7R09933; Thu, 24 Jan 2002 16:54:07 -0800 (PST)
Message-Id: <200201250054.g0P0s7R09933@gamma.isi.edu>
To: IETF-Announce:;
Subject: RFC 3232 on RFC 1700 Replaced by On-line Database
Cc: rfc-ed@ISI.EDU
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
Date: Thu, 24 Jan 2002 16:54:05 -0800
From: RFC Editor <rfc-ed@ISI.EDU>

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


        RFC 3232

        Title:	    Assigned Numbers: RFC 1700 is Replaced by an
                    On-line Database
        Author(s):  J. Reynolds, Editor
        Status:     Informational
	Date:       January 2002
        Mailbox:    rfc-editor@rfc-editor.org
        Pages:      3
        Characters: 3849
        Obsoletes:  1700

        I-D Tag:    draft-rfc-editor-rfc1700bis-00.txt

        URL:        ftp://ftp.rfc-editor.org/in-notes/rfc3232.txt


This memo obsoletes RFC 1700 (STD 2) "Assigned Numbers", which
contained an October 1994 snapshot of assigned Internet protocol
parameters.

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/rfc3232.txt"><ftp://ftp.isi.edu/in-notes/rfc3232.txt>