RFC 2468 on I REMEMBER IANA

RFC Editor <rfc-ed@ISI.EDU> Tue, 20 October 1998 19:25 UTC

Received: (from adm@localhost) by ietf.org (8.8.5/8.8.7a) id PAA00757 for ietf-123-outbound.10@ietf.org; Tue, 20 Oct 1998 15:25:01 -0400 (EDT)
Received: from tnt.isi.edu (tnt.isi.edu [128.9.128.128]) by ietf.org (8.8.5/8.8.7a) with ESMTP id PAA00606 for <all-ietf@ietf.org>; Tue, 20 Oct 1998 15:19:20 -0400 (EDT)
Received: from ISI.EDU (jet.isi.edu [128.9.160.87]) by tnt.isi.edu (8.8.7/8.8.6) with ESMTP id MAA10402; Tue, 20 Oct 1998 12:19:21 -0700 (PDT)
Message-Id: <199810201919.MAA10402@tnt.isi.edu>
To: IETF-Announce:;
Subject: RFC 2468 on I REMEMBER IANA
Cc: rfc-ed@ISI.EDU
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
Date: Tue, 20 Oct 1998 12:19:21 -0700
From: RFC Editor <rfc-ed@ISI.EDU>

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


	RFC 2468:

        Title:	    I REMEMBER IANA    
	Author(s):  V. Cerf
	Status:     Informational
	Date:       October 1998
        Mailbox:    vcerf@mci.net
	Pages:      4
        Characters: 8543	
        Updates/Obsoletes/See Also: None
        I-D Tag:    None

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


Jon, our beloved IANA, is gone.  Even as I write these words I cannot
quite grasp this stark fact.  We had almost lost him once before in
1991.  Surely we knew he was at risk as are we all.  But he had been
our rock, the foundation on which our every web search and email was
built, always there to mediate the random dispute, to remind us when
our documentation did not do justice to its subject, to make difficult
decisions with apparent ease, and to consult when careful
consideration was needed.  We will survive our loss and we will
remember.  He has left a monumental legacy for all Internauts to
contemplate.  Steadfast service for decades, moving when others seemed
paralyzed, always finding the right course in a complex minefield of
technical and sometimes political obstacles.

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