Here's something else to waste time on on a Sunday afternoon.

----- Forwarded message from RFC Editor <[EMAIL PROTECTED]> -----

Date: Fri, 30 Mar 2001 10:53:43 -0800
From: RFC Editor <[EMAIL PROTECTED]>
Subject: RFC 3092 on Etymology of "Foo"


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


         RFC 3092

         Title:     Etymology of "Foo"
         Author(s):  D. Eastlake 3rd, C. Manros, E. Raymond
         Status:     Informational
        Date:       1 April 2001
         Mailbox:    [EMAIL PROTECTED],
                     [EMAIL PROTECTED], [EMAIL PROTECTED]
         Pages:      14
         Characters: 29235
         Updates/Obsoletes/SeeAlso:  None

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


Approximately 212 RFCs so far, starting with RFC 269, contain the
terms `foo', `bar', or `foobar' as metasyntactic variables without any
proper explanation or definition.  This document rectifies that
deficiency.

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 [EMAIL PROTECTED]  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to [EMAIL PROTECTED]

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to [EMAIL PROTECTED] with the message body
help: ways_to_get_rfcs.  For example:

         To: [EMAIL PROTECTED]
         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 [EMAIL PROTECTED]  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.echo
Submissions for Requests for Comments should be sent to
[EMAIL PROTECTED]  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.
Content-Type: text/plain
Content-ID: <[EMAIL PROTECTED]>

RETRIEVE: rfc
DOC-ID: rfc3092

<ftp://ftp.isi.edu/in-notes/rfc3092.txt>


----- End forwarded message -----

-- 
Bob Miller                              K<bob>
kbobsoft, LLC, software consulting
http://kbobsoft.com                     [EMAIL PROTECTED]

Reply via email to