I see Larry finally got around to writing up his Coffee Pot Control Protocol.
Date seems a bit more precise than usual, though.  See also RFC 2325 for a
coffee pot MIB.

---------------- Forwarded  Message ----------------------

Subject: RFC 2324 on HTCPCP/1.0
To: (IETF-Announce)
Cc: rfc-ed@ISI
From: rfc-ed@ISI:EDU:Xerox
Date: Mon, 30 Mar 1998 15:11:57 PST

--NextPart


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


        RFC 2324:

        Title:      Hyper Text Coffee Pot Control Protocol
		    (HTCPCP/1.0)
	Author(s):  L. Masinter
	Status:     Informational
	Date:       1 April 1998
        Mailbox:    masinter@parc.xerox.com
	Pages:      10
        Characters: 19610
        Updates/Obsoletes: None

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


This document describes HTCPCP, a protocol for controlling,
monitoring, and diagnosing coffee pots.

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@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 RFC-Manager@ISI.EDU.  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 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.

--NextPart
Content-Type: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type:  Message/External-body;
        access-type="mail-server";
        server="RFC-INFO@ISI.EDU"

Content-Type: text/plain
Content-ID: <980330151057.RFC@ISI.EDU>

RETRIEVE: rfc
DOC-ID: rfc2324

--OtherAccess
Content-Type:   Message/External-body;
        name="rfc2324.txt";
        site="ftp.isi.edu";
        access-type="anon-ftp";
        directory="in-notes"

Content-Type: text/plain
Content-ID: <980330151057.RFC@ISI.EDU>

--OtherAccess--
--NextPart--



---------------- End of Forwarded Message ---------------