RFC 3251 on Electricity over IP

RFC Editor <rfc-ed@ISI.EDU> Mon, 01 April 2002 22:49 UTC

Received: from loki.ietf.org (loki [10.27.2.29]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA17991; Mon, 1 Apr 2002 17:49:09 -0500 (EST)
Received: (from adm@localhost) by loki.ietf.org (8.9.1b+Sun/8.9.1) id RAA03163 for ietf-123-outbound.10@ietf.org; Mon, 1 Apr 2002 17:45: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 RAA03141 for <all-ietf@loki.ietf.org>; Mon, 1 Apr 2002 17:44:52 -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 RAA17904 for <all-ietf@ietf.org>; Mon, 1 Apr 2002 17:44:48 -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 g31Miom14961; Mon, 1 Apr 2002 14:44:50 -0800 (PST)
Message-Id: <200204012244.g31Miom14961@gamma.isi.edu>
To: IETF-Announce:;
Subject: RFC 3251 on Electricity over IP
Cc: rfc-ed@ISI.EDU
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
Date: Mon, 01 Apr 2002 14:44:49 -0800
From: RFC Editor <rfc-ed@ISI.EDU>

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


        RFC 3251

        Title:	    Electricity over IP
        Author(s):  B. Rajagopalan
        Status:     Informational
	Date:       1 April 2002
        Mailbox:    braja@tellium.com
        Pages:      9
        Characters: 18994
        Updates/Obsoletes/SeeAlso:  None

        I-D Tag:    draft-bala-mplamps-04.txt

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


Mostly Pointless Lamp Switching (MPLampS) is an architecture for
carrying electricity over IP (with an MPLS control plane).  According
to our marketing department, MPLampS has the potential to
dramatically lower the price, ease the distribution and usage, and
improve the manageability of delivering electricity.  This document is
motivated by such work as SONET/SDH over IP/MPLS (with apologies
to the authors).  Readers of the previous work have been observed
scratching their heads and muttering, "What next?".  This document
answers that question.

This document has also been written as a public service.  The "Sub-IP"
area has been formed to give equal opportunity to those working on
technologies outside of traditional IP networking to write
complicated IETF documents.  There are possibly many who are wondering
how to exploit this opportunity and attain high visibility.  Towards
this goal, we see the topics of "foo-over-MPLS" (or MPLS control for
random technologies) as highly amenable for producing a countless
number of unimplementable documents.  This document illustrates the
key ingredients that go into producing any "foo-over-MPLS" document
and may be used as a template for all such work.

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