network working group b. rajagopalan
request for comments: 3251 tellium, inc.
category: informational 1 april 2002

electricity over ip

status of this memo

this memo provides information for the internet community. it does
not specify an internet standard of any kind. distribution of this
memo is unlimited.

copyright notice

copyright (c) the internet society (2002). all rights reserved.

abstract

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.

1. conventions used in this document

the key words "must", "must not", "do", "don't", "required", "shall",
"shall not", "should", "should not", "recommended", "may", "may be"
and "optional" in this document do not mean anything.

rajagopalan informational [page 1]

rfc 3251 electricity over ip 1 april 2002

2. pre-requisite for reading this document

while reading this document, at various points the readers may have
the urge to ask questions like, "does this make sense?", "is this
feasible?," and "is the author sane?". the readers must have the
ability to suppress such questions and read on. other than this, no
specific technical background is required to read this document. in
certain cases (present document included), it may be required that
readers have no specific technical background.

3. introduction

it was recently brought to our attention that the distribution
network for electricity is not an ip network! after absorbing the
shock that was delivered by this news, the following thoughts
occurred to us:

1. electricity distribution must be based on some outdated technology
(called "legacy distribution system" or lds in the rest of the
document).
2. an lds not based on the internet technology means that two
different networks (electricity and ip) must be administered and
managed. this leads to inefficiencies, higher cost and
bureaucratic foul-ups (which possibly lead to blackouts in
california. we are in the process of verifying this using
simulations as part of a student's ms thesis).
3. the above means that a single network technology (i.e., ip) must
be used to carry both electricity and internet traffic.
4. an internet draft must be written to start work in this area,
before someone else does.
5. such a draft can be used to generate further drafts, ensuring that
we (and ccamp, mpls or another responsible working group) will be
busy for another year.
6. the draft can also be posted in the "white papers" section of our
company web page, proclaiming us as revolutionary pioneers.

hence the present document.

4. terminology

mplamps: mostly pointless lamp switching - the architecture
introduced in this document.

lamp: an end-system in the mplamps architecture (clashes with the
ietf notion of end-system but of course, we don't care).

ler: low-voltage electricity receptor - fancy name for "lamp".

rajagopalan informational [page 2]

rfc 3251 electricity over ip 1 april 2002

es: electricity source - a generator.

lsr: load-switching router - an mplamps device used in the core
electricity distribution network.

lds: legacy distribution system - an inferior electricity
distribution technology that mplamps intends to replace.

rsvp: rather screwed-up, but router vendors push it - an ip signaling
protocol.

rsvp-te: rsvp with tariff extensions - rsvp adaptation for mplamps,
to be used in the new deregulated utilities environment.

crldp: for crying out loud, don't do rsvp - another ip signaling
protocol.

ospf: often seizes-up in multiple area configurations - a
hierarchical ip routing protocol.

isis: it's not ospf, yet it somehow survives - another routing
protocol.

ospf-te, isis-te: ospf and isis with tariff extensions.

cops: policemen. folks who scour all places for possibilities to
slip in the common open policy service protocol.

vpn: voltage protected network - allows a customer with multiple
sites to receive electricity with negligible voltage fluctuation due
to interference from other customers.

sub-ip: substitute ip everywhere - an effort in the ietf to get
involved in technical areas outside of traditional ip networking
(such as mplamps).

itu: international tariffed utilities association - a utilities trade
group whose work is often ignored by the ietf.

5. background

we dug into the electricity distribution technology area to get some
background. what we found stunned us, say, with the potency of a
bare 230v a/c lead dropped into our bathtub while we were still in
it. to put it simply, electricity is generated and distributed along
a vast lds which does not have a single router in it (lsr or
otherwise)! furthermore, the control of devices in this network is
mostly manual, done by folks driving around in trucks. after

rajagopalan informational [page 3]

rfc 3251 electricity over ip 1 april 2002

wondering momentarily about how such a network can exist in the 21st
century, we took a pencil and paper and sketched out a scenario for
integrating the lds network with the proven internet technology. the
fundamental points we came up with are:

1. ip packets carry electricity in discrete, digitized form.
2. each packet would deliver electricity to its destination (e.g., a
device with an ip address) on-demand.
3. mpls control will be used to switch packets within the core lds,
and in the edge premises. the architecture for this is referred
to as mostly-pointless lamp switching (mplamps).
4. the mplamps architectural model will accommodate both the overlay
model, where the electricity consuming devices (referred to as
"lamps") are operated over a distinct control plane, and the peer
model, in which the lamps and the distribution network use a
single control plane.
5. rsvp-te (rsvp with tariff extensions) will be used for
establishing paths for electricity flow in a de-regulated
environment.
6. cops will be used to support accounting and policy.

after jotting these points down, we felt better. we then noted the
following immediate advantages of the proposed scheme:

1. switches and transformers in the lds can be replaced by lsrs,
thereby opening up a new market for routers.
2. electricity can be routed over the internet to reach remote places
which presently do not have electricity connections but have only
internet kiosks (e.g., rural india).
3. electrical technicians can be replaced by highly paid ip network
administrators, and
4. the ietf can get involved in another unrelated technology area.

in the following, we describe the technical issues in a vague manner.

6. electricity encoding

the discrete voltage encoding (dve) scheme has been specified in itu
standard g.110/230v [2] to digitize electrical voltages. in essence,
an electricity source (es) such as a generator is connected to a dv
encoder that encodes the voltage and current, and produces a bit
stream. this bit stream can be carried in ip packets to various
destinations (referred to as lers - low-voltage electricity
receptors) on-demand. at the destination, a dv decoder produces the
right voltage and current based on the received bit stream. it is to
be determined whether the real-time transport protocol (rtp) can be

rajagopalan informational [page 4]

rfc 3251 electricity over ip 1 april 2002

used for achieving synchronization and end-to-end control. we leave
draft writing opportunities in the rtp area to our friends and
colleagues.

7. mplamps architecture

7.1 overview

in an lds, the long-haul transmission of electricity is at high
voltages. the voltage is stepped down progressively as electricity
flows into local distribution networks and is finally delivered to
lers at a standard voltage (e.g., 110v). thus, the lds is a
hierarchical network. this immediately opens up the possibility of
ospf and isis extensions for routing electricity in a transmission
network, but we'll contain the urge to delve into these productive
internet draft areas until later. for the present, we limit our
discussion merely to controlling the flow of electricity in an ip-
based distribution network using mplamps.

under mplamps, a voltage is equated to a label. in the distribution
network, each switching element and transformer is viewed as a load-
switching router (lsr). each ip packet carrying an electricity flow
is assigned a label corresponding to the voltage. electricity
distribution can then be trivially reduced to the task of label
(voltage) switching as electricity flows through the distribution
network. the configuration of switching elements in the distribution
network is done through rsvp-te to provide electricity on demand.

we admit that the above description is vague and sounds crazy. the
example below tries to add more (useless) details, without removing
any doubts the reader might have about the feasibility of this
proposal:

example: turning on a lamp

it is assumed that the lamp is controlled by an intelligent device
(e.g, a (light) switch with an mplamps control plane). turning the
lamp on causes the switch to issue an rsvp-te request (a path message
with new objects) for the electricity flow. this path message
traverses across the network to the es. the resv message issued in
return sets up the label mappings in lsrs. finally, electricity
starts flowing along the path established. it is expected that the
entire process will be completed within a few seconds, thereby giving
the mplamps architecture a distinct advantage over lighting a candle
with a damp match stick.

rajagopalan informational [page 5]

rfc 3251 electricity over ip 1 april 2002

7.2 overlay vs peer models

as noted before, there are two control plane models to be considered.
under the overlay model, the lamps and the distribution network
utilize distinct control planes. under the peer model, a single
control plane is used. a number of arguments can be made for one
model versus the other, and these will be covered in the upcoming
framework document. we merely observe here that it is the lamp
vendors who prefer the peer model against the better judgement of the
lsr vendors. we, however, want to please both camps regardless of
the usefulness of either model. we therefore note here that mplamps
supports both models and also migration scenarios from overlay to
peer.

7.3 routing in the core network

the above description of the hierarchical distribution system
immediately opens up the possibility of applying ospf and isis with
suitable extensions. the readers may rest assured that we are
already working on such concepts as voltage bundling, multi-area
tariff extensions, insulated lsas, etc. future documents will
describe the details.

7.4 voltage protected networks (vpns)

vpns allow a customer with multiple sites to get guaranteed
electricity supply with negligible voltage fluctuations due to
interference from other customers. indeed, some may argue that the
entire mplamps architecture may be trashed if not for the possibility
of doing vpns. whatever be the case, vpns are a hot topic today and
the readers are forewarned that we have every intention of writing
several documents on this. specifically, bgp-support for vpns is an
area we're presently eyeing with interest.

8. multicast

it has been observed that there is a strong spatial and temporal
locality in electricity demand. itu study group 55 has studied this
phenomenon for over a decade and has issued a preliminary report.
this report states that when a lamp is turned on in one house, it is
usually the case that lamps are turned on in neighboring houses at
around the same time (usually at dusk) [3]. this observation has a
serious implication on the scalability of the signaling mechanism.
specifically, the distribution network must be able to handle tens of
thousands of requests all at once. the signaling load can be reduced
if multicast delivery is used. briefly, a request for electricity is
not sent from the lamp all the way to an es, but is handled by the
first lsr that is already in the path to another lamp.

rajagopalan informational [page 6]

rfc 3251 electricity over ip 1 april 2002

support for this requires the application of multicast routing
protocols together with rsvp-te shared reservation styles and the
development of mplamps multicast forwarding mode. we are currently
studying the following multicast routing protocol:

o dvmrp: discrete voltage multicast routing protocol - this protocol
works over existing voltage routing protocols but the danger here is
that electricity is delivered to all lamps when any one lamp is
turned on. indeed, the switching semantics gets annoying - all lamps
get turned on periodically and those not needed must be switched off
each time manually.

other protocols we will eventually consider are current-based tree
(cbt) and practically irrelevant multicast (pim). an issue we are
greatly interested in is multicast scope: we would like support for
distributing electricity with varying scope, from lamps within a
single christmas tree to those in entire cities. needless to say, we
will write many detailed documents on these topics as time
progresses.

9. security considerations

this document must be secured in a locked cabinet to prevent it from
being disposed off with the trash.

10. summary

this document described the motivation and high level concepts behind
mostly pointless lamp switching (mplamps), an architecture for
electricity distribution over ip. mplamps utilizes dve (discrete
voltage encoding), and an mpls control plane in the distribution
network. since the aim of this document is to be a high-visibility
place-holder, we did not get into many details of mplamps. numerous
future documents, unfortunately, will attempt to provide these
details.

11. references

1. a. malis, et al., "sonet/sdh circuit emulation service over mpls
(cem) encapsulation", internet draft, work in progress.

2. international tarriffed utilities association draft standard, itu
g.110/230v, "discrete voltage encoding", march, 1999.

3. international tarriffed utilities association technical report,
itu (sg-55) tr-432-2000, "empirical models for energy
utilization", september, 2000.

rajagopalan informational [page 7]

rfc 3251 electricity over ip 1 april 2002

12. disclaimer

the opinions expressed in this document are solely the author's.
company's opinions, as always, are proprietary and confidential and
may be obtained under appropriate ndas.

13. author's address

bala rajagopalan
tellium, inc.
2 crescent place
ocean port, nj 07757
phone: 732-923-4237
email: braja@tellium.com

rajagopalan informational [page 8]

rfc 3251 electricity over ip 1 april 2002

14. full copyright statement

copyright (c) the internet society (2002). all rights reserved.

this document and translations of it may be copied and furnished to
others, and derivative works that comment on or otherwise explain it
or assist in its implementation may be prepared, copied, published
and distributed, in whole or in part, without restriction of any
kind, provided that the above copyright notice and this paragraph are
included on all such copies and derivative works. however, this
document itself may not be modified in any way, such as by removing
the copyright notice or references to the internet society or other
internet organizations, except as needed for the purpose of
developing internet standards in which case the procedures for
copyrights defined in the internet standards process must be
followed, or as required to translate it into languages other than
english.

the limited permissions granted above are perpetual and will not be
revoked by the internet society or its successors or assigns.

this document and the information contained herein is provided on an
"as is" basis and the internet society and the internet engineering
task force disclaims all warranties, express or implied, including
but not limited to any warranty that the use of the information
herein will not infringe any rights or any implied warranties of
merchantability or fitness for a particular purpose.

acknowledgement

funding for the rfc editor function is currently provided by the
internet society.

rajagopalan informational [page 9]

(huzursuz - 2 Nisan 2003 12:38)