
From balajivenkat299@gmail.com  Tue Feb  5 22:57:46 2013
Return-Path: <balajivenkat299@gmail.com>
X-Original-To: irtf-discuss@ietfa.amsl.com
Delivered-To: irtf-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 90BF421F853E for <irtf-discuss@ietfa.amsl.com>; Tue,  5 Feb 2013 22:57:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.597
X-Spam-Level: 
X-Spam-Status: No, score=-4.597 tagged_above=-999 required=5 tests=[AWL=-1.000, BAYES_00=-2.599, HTML_MESSAGE=0.001, HTML_OBFUSCATE_05_10=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2TRPats0AkpE for <irtf-discuss@ietfa.amsl.com>; Tue,  5 Feb 2013 22:57:45 -0800 (PST)
Received: from mail-ob0-f171.google.com (mail-ob0-f171.google.com [209.85.214.171]) by ietfa.amsl.com (Postfix) with ESMTP id E184A21F847C for <irtf-discuss@irtf.org>; Tue,  5 Feb 2013 22:57:44 -0800 (PST)
Received: by mail-ob0-f171.google.com with SMTP id x4so989700obh.16 for <irtf-discuss@irtf.org>; Tue, 05 Feb 2013 22:57:44 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:date:message-id:subject:from:to :content-type; bh=dqZVU59KPEMl85tFdHBgwxG5SL5G01M0A4iUpRe8TTs=; b=D2LkaW2563GwS6RqxbAMX0xx4lryNPWQPNTFlt3dwkoQIrkeyuqmPklDWbkORVqsCu wKbTfSZM/XTsrqE2zdwRpCQOR+klHyn5m+ffjQ+Jmi5xquISYRH6JuwPjQbn/4O4vJZ1 aiP9Hg6lmoyDdSYGovLtFVH8sO6Mb8icIv8xM3immr5Q2v7VcmZCGm9WXOvp3zLSrkIh 7RMWl2+oFCxPfFZVQA5xTRHewJBeS179iZyGL3nf3aguldBB3oTUrNRNESppOyXu+RCt NmEIWGrtoH3CW96YL0UnnqRfbRaZWeaVBGZ95D9b5SlffQ9GfX9qzF3mGtE+N26NJ0Rn 65KQ==
MIME-Version: 1.0
X-Received: by 10.60.0.199 with SMTP id 7mr21883450oeg.139.1360133864252; Tue, 05 Feb 2013 22:57:44 -0800 (PST)
Received: by 10.60.55.71 with HTTP; Tue, 5 Feb 2013 22:57:44 -0800 (PST)
Date: Wed, 6 Feb 2013 12:27:44 +0530
Message-ID: <CAHF4apMOpXohhWpYXB8X74yG4fBhcjVW0c=vNW4qXudJ7H92rA@mail.gmail.com>
From: Balaji venkat Venkataswami <balajivenkat299@gmail.com>
To: irtf-discuss@irtf.org, Lars Eggert <lars.eggert@nokia.com>,  Susan Hares <susan.hares@huawei.com>
Content-Type: multipart/alternative; boundary=e89a8fb1f3bed3669304d508d7d7
Subject: [irtf-discuss] Request for a side-bar meeting in the IETF Orlando on Power-Aware Networking drafts
X-BeenThere: irtf-discuss@irtf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IRTF general and new-work discussion list <irtf-discuss.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/options/irtf-discuss>, <mailto:irtf-discuss-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/irtf-discuss>
List-Post: <mailto:irtf-discuss@irtf.org>
List-Help: <mailto:irtf-discuss-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/irtf-discuss>, <mailto:irtf-discuss-request@irtf.org?subject=subscribe>
X-List-Received-Date: Wed, 06 Feb 2013 06:57:46 -0000

--e89a8fb1f3bed3669304d508d7d7
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

Dear Lars, all,

We would like a side-bar meeting (in an adjacent room) to discuss the
following Power-Aware-Networking proposals.
A detailed outline of the drafts submitted have been detailed below. We
would like a 20 minute slot with 10 minutes for Q&A if possible.
We would however concur with whatever time you give us on this matter.

We are a group of research and industry individuals tied together with a
common goal towards reducing the energy consumption in the core and edge
networks.

We present a metric-based hierarchical approach to reduce power consumption
in core and edge networks. The proposal considers both unicast and the
multicast cases. For unicast, the metric considered is *consumed-power to
available-bandwidth* and for multicast the metric is *consumed-power to
available-replication-capacity.*

 With unicast, the metric is used to determine a low-power path between
sources and destinations. With multicast, the metric serves the twin
purpose of finding low-power multicast paths as well as multicast
replication points.  We evolve multiple techniques at various hierarchical
levels. One at the Inter-AS level, Inter-Area level within the AS and
intra-Area within an AS. Additionally, the proposed method can also be used
to determine disjoint or redundant paths for load balancing or fault
tolerance. Additionally since TCAMs are one of the biggest power guzzlers
in all the components on a router/switch, we have presented a solution for
intra-AS purposes to use the TCAM according to the traffic matrix passing
through the system and shut down those TCAM banks that are unused. With
this in mind, we have also advocated taking into account a TCAM-POWER-Ratio
in order to compute the paths from source to destination based on this
metric. Once low-power paths, in either the unicast or the multicast cases,
are identified then currently available traffic engineering techniques
could be used to route the data packets. In the case of inter-AS BGP path
selection is also modified to arrive at paths which are low-power paths.

 Our main objective is as follows...

We now outline four important aspects that any approach for power reduction
should be capable of addressing.

 *Should cater for both unicast and multicast scenarios*

Multicast provides an important scenario for the Internet. Today, most
proposals consider mainly low-power path routing with unicast traffic.
Multicast traffic has received a lot of attention in wireless networks, but
not in the wired domain. Any new proposal should be able to address both
the unicast and the multicast traffic scenarios. Having different methods
for these two scenarios might lead to unnecessary processing burden in the
routers, which might hinder its scalability.

 *Should not rely on just switching off unused links*

Most approaches to optimize energy pursue the following approach: measure,
monitor and respond to the system energy usage by switching off unused or
under-utilized links. Such an approach could be effective for reducing
power locally. The effect on the network is not clearly understood.
Further, the power usage involved in turning on and rebooting/reconfiguring
the device is often not explicitly considered. We note that Service Level
Agreement (SLA) requirements may not even permit the links to be switched
off. Also services provided by ISPs like Virtual Private Networks (VPNs)
can be affected by such re-routing decisions.

 *Should follow an hierarchical and distributed approach*

For scalability, it is important that the algorithms proposed for inter-AS
should also be applicable to intra-AS situations. Networks do not work in
isolation, so any proposal should be both distributed and hierarchical. The
algorithms should be applicable at every level of the hierarchy.

 *Should  provide incentives for ISP for adoption*

The engineering proposals should be aligned with commercial incentives for
rapid and widespread adoption. Today, the device manufacturers and the ISPs
operate independently of each other, and there is no incentive for
manufacturers to work towards low-power and high bandwidth devices. An
ISP=92s revenue model is based on the consumed bandwidth, which in turn lea=
d
naturally to more power consumption. If the proposed method chooses routers
that consume low-power and increase the data flow through them, then this
indirectly provides encouragement for ISPs to purchase low-power and high
bandwidth devices.



We now present our metric-based proposals in the below mentioned drafts
which addresses the aforementioned design aspects.

We would like the routing community to provide feedback on these drafts. We
also intend to present this work in an abridged format in the upcoming IETF=
.

 The drafts are as follows....




   - mjsraman-panet-bgp-power-path<http://tools.ietf.org/html/draft-mjsrama=
n-panet-bgp-power-path>
    (timeline)<http://www.arkko.com/tools/lifecycle/draft-mjsraman-panet-bg=
p-power-path-timing.html>
    Inter-AS-Proposal
   - mjsraman-panet-ecmp-redirect-power-repl-cap<http://tools.ietf.org/html=
/draft-mjsraman-panet-ecmp-redirect-power-repl-cap>
    (timeline)<http://www.arkko.com/tools/lifecycle/draft-mjsraman-panet-ec=
mp-redirect-power-repl-cap-timing.html>
    Multicast
   - mjsraman-panet-inter-as-power-source<http://tools.ietf.org/html/draft-=
mjsraman-panet-inter-as-power-source>
    (timeline)<http://www.arkko.com/tools/lifecycle/draft-mjsraman-panet-in=
ter-as-power-source-timing.html>
Inter-AS
   Proposal
   - mjsraman-panet-inter-as-psp<http://tools.ietf.org/html/draft-mjsraman-=
panet-inter-as-psp>
    (timeline)<http://www.arkko.com/tools/lifecycle/draft-mjsraman-panet-in=
ter-as-psp-timing.html>
Inter-AS
   Proposal
   - mjsraman-panet-inter-as-psp-protect<http://tools.ietf.org/html/draft-m=
jsraman-panet-inter-as-psp-protect>
    (timeline)<http://www.arkko.com/tools/lifecycle/draft-mjsraman-panet-in=
ter-as-psp-protect-timing.html>
Inter-AS
   Proposal
   - mjsraman-panet-pce-power-mcast-replic<http://tools.ietf.org/html/draft=
-mjsraman-panet-pce-power-mcast-replic>
    (timeline)<http://www.arkko.com/tools/lifecycle/draft-mjsraman-panet-pc=
e-power-mcast-replic-timing.html>
    Multicast
   - mjsraman-panet-pim-power<http://tools.ietf.org/html/draft-mjsraman-pan=
et-pim-power>
    (timeline)<http://www.arkko.com/tools/lifecycle/draft-mjsraman-panet-pi=
m-power-timing.html>
    Multicast
   - mjsraman-panet-tcam-power-efficiency<http://tools.ietf.org/html/draft-=
mjsraman-panet-tcam-power-efficiency>
    (timeline)<http://www.arkko.com/tools/lifecycle/draft-mjsraman-panet-tc=
am-power-efficiency-timing.html>
TCAM
   related
   - mjsraman-panet-tcam-power-ratio<http://tools.ietf.org/html/draft-mjsra=
man-panet-tcam-power-ratio>
    (timeline<http://www.arkko.com/tools/lifecycle/draft-mjsraman-panet-tca=
m-power-ratio-timing.html>)
   TCAM related
   - mjsraman-pce-power-replic<http://tools.ietf.org/html/draft-mjsraman-pc=
e-power-replic>
    (timeline)<http://www.arkko.com/tools/lifecycle/draft-mjsraman-pce-powe=
r-replic-timing.html>
    Multicast
   - mjsraman-panet-intra-as-psp-te-leak<http://tools.ietf.org/html/draft-m=
jsraman-panet-intra-as-psp-te-leak>
    (timeline)<http://www.arkko.com/tools/lifecycle/draft-mjsraman-panet-in=
tra-as-psp-te-leak-timing.html>
Inter-Area
   within an AS
   - mjsraman-panet-ospf-power-topo<http://tools.ietf.org/html/draft-mjsram=
an-panet-ospf-power-topo>
    (timeline)<http://www.arkko.com/tools/lifecycle/draft-mjsraman-panet-os=
pf-power-topo-timing.html>
Intra-Area
   within an AS

We understand it is a lot of matter to go through. We would much appreciate
if some of you could review the inter-AS proposals while others take up
multicast and Intra-AS unicast and multicast.

Thanks again for your time on this matter.

thanks and regards,
balaji venkat

--e89a8fb1f3bed3669304d508d7d7
Content-Type: text/html; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

Dear Lars, all,<div><br></div><div>We would like a side-bar meeting (in an =
adjacent room) to discuss the following Power-Aware-Networking proposals.</=
div><div>A detailed outline of the drafts submitted have been detailed belo=
w. We would like a 20 minute slot with 10 minutes for Q&amp;A if possible.<=
/div>
<div>We would however concur with whatever time you give us on this matter.=
</div><div><p style=3D"color:rgb(34,34,34);font-family:arial,sans-serif;fon=
t-size:13px;background-color:rgb(255,255,255)">We are a group of research a=
nd industry individuals tied together with a common goal towards reducing t=
he energy consumption in the core and edge networks.</p>
<p style=3D"color:rgb(34,34,34);font-family:arial,sans-serif;font-size:13px=
;background-color:rgb(255,255,255)">We present a metric-based hierarchical =
approach to reduce power consumption in core and edge networks. The proposa=
l considers both unicast and the multicast cases. For unicast, the metric c=
onsidered is=A0<i>consumed-power to available-bandwidth</i>=A0and for multi=
cast the metric is=A0<i>consumed-power to available-replication-capacity.</=
i></p>
<p style=3D"color:rgb(34,34,34);font-family:arial,sans-serif;font-size:13px=
;background-color:rgb(255,255,255)"><span lang=3D"EN-US">=A0</span><span la=
ng=3D"EN-US">With unicast, the metric is=A0</span><span lang=3D"EN-US">used=
 to determine a low-power path between sources and destinations.=A0</span><=
span lang=3D"EN-US" style=3D"background-color:transparent">With multicast, =
the=A0</span><span lang=3D"EN-US" style=3D"background-color:transparent">me=
tric serves the twin purpose of finding low-power multicast paths as well a=
s multicast replication points.</span><span lang=3D"EN-US" style=3D"backgro=
und-color:transparent">=A0=A0</span>We evolve multiple techniques at variou=
s hierarchical levels. One at the Inter-AS level, Inter-Area level within t=
he AS and intra-Area within an AS. Additionally, the proposed method can al=
so be used to determine disjoint or redundant paths for load balancing or f=
ault tolerance. Additionally since TCAMs are one of the biggest power guzzl=
ers in all the components on a router/switch, we have presented a solution =
for intra-AS purposes to use the TCAM according to the traffic matrix passi=
ng through the system and shut down those TCAM banks that are unused. With =
this in mind, we have also advocated taking into account a TCAM-POWER-Ratio=
 in order to compute the paths from source to destination based on this met=
ric. Once low-power paths, in either the unicast or the multicast cases, ar=
e identified then currently available traffic engineering techniques could =
be used to route the data packets. In the case of inter-AS BGP path selecti=
on is also modified to arrive at paths which are low-power paths.</p>
<p style=3D"color:rgb(34,34,34);font-family:arial,sans-serif;font-size:13px=
;background-color:rgb(255,255,255)"><span lang=3D"EN-US">=A0Our main object=
ive is as follows...</span></p><p style=3D"color:rgb(34,34,34);font-family:=
arial,sans-serif;font-size:13px;background-color:rgb(255,255,255)">
<span lang=3D"EN-US"></span></p><p align=3D"left" style=3D"color:rgb(34,34,=
34);font-family:arial,sans-serif;font-size:13px;background-color:rgb(255,25=
5,255)">We now outline four important aspects that any approach for power r=
eduction should be capable of addressing.</p>
<p align=3D"left" style=3D"color:rgb(34,34,34);font-family:arial,sans-serif=
;font-size:13px;background-color:rgb(255,255,255)">=A0<i>Should cater for b=
oth unicast and multicast scenarios</i></p><p align=3D"left" style=3D"color=
:rgb(34,34,34);font-family:arial,sans-serif;font-size:13px;background-color=
:rgb(255,255,255)">
</p><p align=3D"left" style=3D"color:rgb(34,34,34);font-family:arial,sans-s=
erif;font-size:13px;background-color:rgb(255,255,255)">Multicast provides a=
n important scenario for the Internet. Today, most proposals consider mainl=
y low-power path routing with unicast traffic. Multicast traffic has receiv=
ed a lot of attention in wireless networks, but not in the wired domain. An=
y new proposal should be able to address both the unicast and the multicast=
 traffic scenarios. Having different methods for these two scenarios might =
lead to unnecessary processing burden in the routers, which might hinder it=
s scalability.=A0=A0=A0=A0=A0=A0=A0=A0</p>
<p align=3D"left" style=3D"color:rgb(34,34,34);font-family:arial,sans-serif=
;font-size:13px;background-color:rgb(255,255,255)">=A0<i>Should not rely on=
 just switching off unused links</i></p><p align=3D"left" style=3D"color:rg=
b(34,34,34);font-family:arial,sans-serif;font-size:13px;background-color:rg=
b(255,255,255)">
</p><p align=3D"left" style=3D"color:rgb(34,34,34);font-family:arial,sans-s=
erif;font-size:13px;background-color:rgb(255,255,255)">Most approaches to o=
ptimize energy pursue the following approach: measure, monitor and respond =
to the system energy usage by switching off unused or under-utilized links.=
 Such an approach could be effective for reducing power locally. The effect=
 on the network is not clearly understood. Further, the power usage involve=
d in turning on and rebooting/reconfiguring the device is often not explici=
tly considered. We note that Service Level Agreement (SLA) requirements may=
 not even permit the links to be switched off. Also services provided by IS=
Ps like Virtual Private Networks (VPNs) can be affected by such re-routing =
decisions.</p>
<p align=3D"left" style=3D"color:rgb(34,34,34);font-family:arial,sans-serif=
;font-size:13px;background-color:rgb(255,255,255)">=A0<i>Should follow an h=
ierarchical and distributed approach</i></p><p align=3D"left" style=3D"colo=
r:rgb(34,34,34);font-family:arial,sans-serif;font-size:13px;background-colo=
r:rgb(255,255,255)">
</p><p align=3D"left" style=3D"color:rgb(34,34,34);font-family:arial,sans-s=
erif;font-size:13px;background-color:rgb(255,255,255)">For scalability, it =
is important that the algorithms proposed for inter-AS should also be appli=
cable to intra-AS situations. Networks do not work in isolation, so any pro=
posal should be both distributed and hierarchical. The algorithms should be=
 applicable at every level of the hierarchy.=A0=A0</p>
<p align=3D"left" style=3D"color:rgb(34,34,34);font-family:arial,sans-serif=
;font-size:13px;background-color:rgb(255,255,255)">=A0<i>Should=A0=A0provid=
e incentives for ISP for adoption</i></p><p align=3D"left" style=3D"color:r=
gb(34,34,34);font-family:arial,sans-serif;font-size:13px;background-color:r=
gb(255,255,255)">
</p><p align=3D"left" style=3D"color:rgb(34,34,34);font-family:arial,sans-s=
erif;font-size:13px;background-color:rgb(255,255,255)">The engineering prop=
osals should be aligned with commercial incentives for rapid and widespread=
 adoption. Today, the device manufacturers and the ISPs operate independent=
ly of each other, and there is no incentive for manufacturers to work towar=
ds low-power and high bandwidth devices. An ISP=92s revenue model is based =
on the consumed bandwidth, which in turn lead naturally to more power consu=
mption. If the proposed method chooses routers that consume low-power and i=
ncrease the data flow through them, then this indirectly provides encourage=
ment for ISPs to purchase low-power and high bandwidth devices.=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0</p>
<p align=3D"left" style=3D"color:rgb(34,34,34);font-family:arial,sans-serif=
;font-size:13px;background-color:rgb(255,255,255)">=A0</p><p align=3D"left"=
 style=3D"color:rgb(34,34,34);font-family:arial,sans-serif;font-size:13px;b=
ackground-color:rgb(255,255,255)">
We now present our metric-based proposals in the below mentioned drafts whi=
ch addresses the aforementioned design aspects.</p><p align=3D"left" style=
=3D"color:rgb(34,34,34);font-family:arial,sans-serif;font-size:13px;backgro=
und-color:rgb(255,255,255)">
We would like the routing community to provide feedback on these drafts. We=
 also intend to present this work in an abridged format in the upcoming IET=
F.</p><p class=3D"MsoNormal" style=3D"color:rgb(34,34,34);font-family:arial=
,sans-serif;font-size:13px;background-color:rgb(255,255,255)">
<span style=3D"font-size:11pt">=A0The drafts are as follows....</span></p><=
p class=3D"MsoNormal" style=3D"color:rgb(34,34,34);font-family:arial,sans-s=
erif;font-size:13px;background-color:rgb(255,255,255)"><span style=3D"font-=
size:11pt"><br>
</span></p><p class=3D"MsoNormal" style=3D"color:rgb(34,34,34);font-family:=
arial,sans-serif;font-size:13px;background-color:rgb(255,255,255)"><span st=
yle=3D"font-size:11pt"><br></span></p><p class=3D"MsoNormal" style=3D"color=
:rgb(34,34,34);font-family:arial,sans-serif;font-size:13px;background-color=
:rgb(255,255,255)">
</p><ul style=3D"color:rgb(34,34,34);font-size:13px;background-color:rgb(25=
5,255,255);font-family:sans-serif;padding-left:1em;margin:1em"><li style=3D=
"margin-left:15px;margin-bottom:3pt"><a href=3D"http://tools.ietf.org/html/=
draft-mjsraman-panet-bgp-power-path" target=3D"_blank" style=3D"color:rgb(6=
8,0,136);border-bottom-width:0px">mjsraman-panet-bgp-power-path</a>=A0<a hr=
ef=3D"http://www.arkko.com/tools/lifecycle/draft-mjsraman-panet-bgp-power-p=
ath-timing.html" target=3D"_blank" style=3D"color:rgb(68,0,136);border-bott=
om-width:0px">(timeline)</a>=A0Inter-AS-Proposal</li>
<li style=3D"margin-left:15px;margin-bottom:3pt"><a href=3D"http://tools.ie=
tf.org/html/draft-mjsraman-panet-ecmp-redirect-power-repl-cap" target=3D"_b=
lank" style=3D"color:rgb(68,0,136);border-bottom-width:0px">mjsraman-panet-=
ecmp-redirect-power-repl-cap</a>=A0<a href=3D"http://www.arkko.com/tools/li=
fecycle/draft-mjsraman-panet-ecmp-redirect-power-repl-cap-timing.html" targ=
et=3D"_blank" style=3D"color:rgb(68,0,136);border-bottom-width:0px">(timeli=
ne)</a>=A0Multicast</li>
<li style=3D"margin-left:15px;margin-bottom:3pt"><a href=3D"http://tools.ie=
tf.org/html/draft-mjsraman-panet-inter-as-power-source" target=3D"_blank" s=
tyle=3D"color:rgb(68,0,136);border-bottom-width:0px">mjsraman-panet-inter-a=
s-power-source</a>=A0<a href=3D"http://www.arkko.com/tools/lifecycle/draft-=
mjsraman-panet-inter-as-power-source-timing.html" target=3D"_blank" style=
=3D"color:rgb(68,0,136);border-bottom-width:0px">(timeline)</a>=A0Inter-AS =
Proposal</li>
<li style=3D"margin-left:15px;margin-bottom:3pt"><a href=3D"http://tools.ie=
tf.org/html/draft-mjsraman-panet-inter-as-psp" target=3D"_blank" style=3D"c=
olor:rgb(68,0,136);border-bottom-width:0px">mjsraman-panet-inter-as-psp</a>=
=A0<a href=3D"http://www.arkko.com/tools/lifecycle/draft-mjsraman-panet-int=
er-as-psp-timing.html" target=3D"_blank" style=3D"color:rgb(68,0,136);borde=
r-bottom-width:0px">(timeline)</a>=A0Inter-AS Proposal</li>
<li style=3D"margin-left:15px;margin-bottom:3pt"><a href=3D"http://tools.ie=
tf.org/html/draft-mjsraman-panet-inter-as-psp-protect" target=3D"_blank" st=
yle=3D"color:rgb(68,0,136);border-bottom-width:0px">mjsraman-panet-inter-as=
-psp-protect</a>=A0<a href=3D"http://www.arkko.com/tools/lifecycle/draft-mj=
sraman-panet-inter-as-psp-protect-timing.html" target=3D"_blank" style=3D"c=
olor:rgb(68,0,136);border-bottom-width:0px">(timeline)</a>=A0Inter-AS Propo=
sal</li>
<li style=3D"margin-left:15px;margin-bottom:3pt"><a href=3D"http://tools.ie=
tf.org/html/draft-mjsraman-panet-pce-power-mcast-replic" target=3D"_blank" =
style=3D"color:rgb(68,0,136);border-bottom-width:0px">mjsraman-panet-pce-po=
wer-mcast-replic</a>=A0<a href=3D"http://www.arkko.com/tools/lifecycle/draf=
t-mjsraman-panet-pce-power-mcast-replic-timing.html" target=3D"_blank" styl=
e=3D"color:rgb(68,0,136);border-bottom-width:0px">(timeline)</a>=A0Multicas=
t</li>
<li style=3D"margin-left:15px;margin-bottom:3pt"><a href=3D"http://tools.ie=
tf.org/html/draft-mjsraman-panet-pim-power" target=3D"_blank" style=3D"colo=
r:rgb(68,0,136);border-bottom-width:0px">mjsraman-panet-pim-power</a>=A0<a =
href=3D"http://www.arkko.com/tools/lifecycle/draft-mjsraman-panet-pim-power=
-timing.html" target=3D"_blank" style=3D"color:rgb(68,0,136);border-bottom-=
width:0px">(timeline)</a>=A0Multicast</li>
<li style=3D"margin-left:15px;margin-bottom:3pt"><a href=3D"http://tools.ie=
tf.org/html/draft-mjsraman-panet-tcam-power-efficiency" target=3D"_blank" s=
tyle=3D"color:rgb(68,0,136);border-bottom-width:0px">mjsraman-panet-tcam-po=
wer-efficiency</a>=A0<a href=3D"http://www.arkko.com/tools/lifecycle/draft-=
mjsraman-panet-tcam-power-efficiency-timing.html" target=3D"_blank" style=
=3D"color:rgb(68,0,136);border-bottom-width:0px">(timeline)</a>=A0TCAM rela=
ted</li>
<li style=3D"margin-left:15px;margin-bottom:3pt"><a href=3D"http://tools.ie=
tf.org/html/draft-mjsraman-panet-tcam-power-ratio" target=3D"_blank" style=
=3D"color:rgb(68,0,136);border-bottom-width:0px">mjsraman-panet-tcam-power-=
ratio</a>=A0<a href=3D"http://www.arkko.com/tools/lifecycle/draft-mjsraman-=
panet-tcam-power-ratio-timing.html" target=3D"_blank" style=3D"color:rgb(68=
,0,136);border-bottom-width:0px">(timeline</a>) TCAM related</li>
<li style=3D"margin-left:15px;margin-bottom:3pt"><a href=3D"http://tools.ie=
tf.org/html/draft-mjsraman-pce-power-replic" target=3D"_blank" style=3D"col=
or:rgb(68,0,136);border-bottom-width:0px">mjsraman-pce-power-replic</a>=A0<=
a href=3D"http://www.arkko.com/tools/lifecycle/draft-mjsraman-pce-power-rep=
lic-timing.html" target=3D"_blank" style=3D"color:rgb(68,0,136);border-bott=
om-width:0px">(timeline)</a>=A0Multicast</li>
<li style=3D"margin-left:15px;margin-bottom:3pt"><a href=3D"http://tools.ie=
tf.org/html/draft-mjsraman-panet-intra-as-psp-te-leak" target=3D"_blank" st=
yle=3D"color:rgb(68,0,136);border-bottom-width:0px">mjsraman-panet-intra-as=
-psp-te-leak</a>=A0<a href=3D"http://www.arkko.com/tools/lifecycle/draft-mj=
sraman-panet-intra-as-psp-te-leak-timing.html" target=3D"_blank" style=3D"c=
olor:rgb(68,0,136);border-bottom-width:0px">(timeline)</a>=A0Inter-Area wit=
hin an AS</li>
<li style=3D"margin-left:15px;margin-bottom:3pt"><a href=3D"http://tools.ie=
tf.org/html/draft-mjsraman-panet-ospf-power-topo" target=3D"_blank" style=
=3D"color:rgb(68,0,136);border-bottom-width:0px">mjsraman-panet-ospf-power-=
topo</a>=A0<a href=3D"http://www.arkko.com/tools/lifecycle/draft-mjsraman-p=
anet-ospf-power-topo-timing.html" target=3D"_blank" style=3D"color:rgb(68,0=
,136);border-bottom-width:0px">(timeline)</a>=A0Intra-Area within an AS</li=
>
</ul><div style=3D"color:rgb(34,34,34);font-family:arial,sans-serif;font-si=
ze:13px;background-color:rgb(255,255,255)"><font face=3D"sans-serif">We und=
erstand it is a lot of matter to go through. We would much appreciate if so=
me of you could review the inter-AS proposals while others take up multicas=
t and Intra-AS unicast and multicast.</font></div>
<div style=3D"color:rgb(34,34,34);font-family:arial,sans-serif;font-size:13=
px;background-color:rgb(255,255,255)"><font face=3D"sans-serif"><br></font>=
</div><div style=3D"color:rgb(34,34,34);font-family:arial,sans-serif;font-s=
ize:13px;background-color:rgb(255,255,255)">
<font face=3D"sans-serif">Thanks again for your time on this matter.</font>=
</div><div style=3D"color:rgb(34,34,34);font-family:arial,sans-serif;font-s=
ize:13px;background-color:rgb(255,255,255)"><font face=3D"sans-serif"><br><=
/font></div>
<div style=3D"color:rgb(34,34,34);font-family:arial,sans-serif;font-size:13=
px;background-color:rgb(255,255,255)"><font face=3D"sans-serif">thanks and =
regards,</font></div><div style=3D"color:rgb(34,34,34);font-family:arial,sa=
ns-serif;font-size:13px;background-color:rgb(255,255,255)">
<font face=3D"sans-serif">balaji venkat</font></div></div>

--e89a8fb1f3bed3669304d508d7d7--

From dromasca@avaya.com  Wed Feb  6 02:45:33 2013
Return-Path: <dromasca@avaya.com>
X-Original-To: irtf-discuss@ietfa.amsl.com
Delivered-To: irtf-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B425721F86F2 for <irtf-discuss@ietfa.amsl.com>; Wed,  6 Feb 2013 02:45:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.527
X-Spam-Level: 
X-Spam-Status: No, score=-102.527 tagged_above=-999 required=5 tests=[AWL=-0.728, BAYES_00=-2.599, HTML_MESSAGE=0.001, SARE_SUB_RAND_LETTRS4=0.799, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MKTK9IlqNv+E for <irtf-discuss@ietfa.amsl.com>; Wed,  6 Feb 2013 02:45:29 -0800 (PST)
Received: from p-us1-iereast-outbound.us1.avaya.com (p-us1-iereast-outbound.us1.avaya.com [135.11.29.13]) by ietfa.amsl.com (Postfix) with ESMTP id 8091821F868D for <irtf-discuss@irtf.org>; Wed,  6 Feb 2013 02:45:29 -0800 (PST)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AqcFAP0QA1HGmAcF/2dsb2JhbABFgkgjskwBiRoWc4IeAQEBAQMSG0wQAgEIDQQEAQELCwsBAgQHMhQJCAIEAQ0FCAwHB4dtAQuhWJx0jRV1glRhA5IgOoRPhHGKO4J3giQ
X-IronPort-AV: E=Sophos;i="4.84,541,1355115600"; d="scan'208,217";a="47592005"
Received: from unknown (HELO co300216-co-erhwest.avaya.com) ([198.152.7.5]) by p-us1-iereast-outbound.us1.avaya.com with ESMTP; 06 Feb 2013 05:44:18 -0500
Received: from unknown (HELO AZ-FFEXHC04.global.avaya.com) ([135.64.58.14]) by co300216-co-erhwest-out.avaya.com with ESMTP; 06 Feb 2013 05:44:04 -0500
Received: from AZ-FFEXMB04.global.avaya.com ([fe80::6db7:b0af:8480:c126]) by AZ-FFEXHC04.global.avaya.com ([135.64.58.14]) with mapi id 14.02.0328.009; Wed, 6 Feb 2013 05:45:31 -0500
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: Balaji venkat Venkataswami <balajivenkat299@gmail.com>, "irtf-discuss@irtf.org" <irtf-discuss@irtf.org>, Lars Eggert <lars.eggert@nokia.com>, Susan Hares <susan.hares@huawei.com>
Thread-Topic: [irtf-discuss] Request for a side-bar meeting in the IETF Orlando on Power-Aware Networking drafts
Thread-Index: AQHOBDdWB+gPQyOI+kugTUCpXgQUH5hspTOQ
Date: Wed, 6 Feb 2013 10:45:30 +0000
Message-ID: <9904FB1B0159DA42B0B887B7FA8119CA082E38@AZ-FFEXMB04.global.avaya.com>
References: <CAHF4apMOpXohhWpYXB8X74yG4fBhcjVW0c=vNW4qXudJ7H92rA@mail.gmail.com>
In-Reply-To: <CAHF4apMOpXohhWpYXB8X74yG4fBhcjVW0c=vNW4qXudJ7H92rA@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [135.64.58.45]
Content-Type: multipart/alternative; boundary="_000_9904FB1B0159DA42B0B887B7FA8119CA082E38AZFFEXMB04globala_"
MIME-Version: 1.0
Cc: "eerg@listserv.netlab.nec.de" <eerg@listserv.netlab.nec.de>
Subject: Re: [irtf-discuss] Request for a side-bar meeting in the IETF Orlando on Power-Aware Networking drafts
X-BeenThere: irtf-discuss@irtf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IRTF general and new-work discussion list <irtf-discuss.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/options/irtf-discuss>, <mailto:irtf-discuss-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/irtf-discuss>
List-Post: <mailto:irtf-discuss@irtf.org>
List-Help: <mailto:irtf-discuss-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/irtf-discuss>, <mailto:irtf-discuss-request@irtf.org?subject=subscribe>
X-List-Received-Date: Wed, 06 Feb 2013 10:45:33 -0000

--_000_9904FB1B0159DA42B0B887B7FA8119CA082E38AZFFEXMB04globala_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hi Balaji,

Is the scope of the work that you propose different of EERG,  could it be p=
art of EERG, or an extension?

Thanks and Regards,

Dan



From: irtf-discuss-bounces@irtf.org [mailto:irtf-discuss-bounces@irtf.org] =
On Behalf Of Balaji venkat Venkataswami
Sent: Wednesday, February 06, 2013 8:58 AM
To: irtf-discuss@irtf.org; Lars Eggert; Susan Hares
Subject: [irtf-discuss] Request for a side-bar meeting in the IETF Orlando =
on Power-Aware Networking drafts

Dear Lars, all,

We would like a side-bar meeting (in an adjacent room) to discuss the follo=
wing Power-Aware-Networking proposals.
A detailed outline of the drafts submitted have been detailed below. We wou=
ld like a 20 minute slot with 10 minutes for Q&A if possible.
We would however concur with whatever time you give us on this matter.

We are a group of research and industry individuals tied together with a co=
mmon goal towards reducing the energy consumption in the core and edge netw=
orks.

We present a metric-based hierarchical approach to reduce power consumption=
 in core and edge networks. The proposal considers both unicast and the mul=
ticast cases. For unicast, the metric considered is consumed-power to avail=
able-bandwidth and for multicast the metric is consumed-power to available-=
replication-capacity.

 With unicast, the metric is used to determine a low-power path between sou=
rces and destinations. With multicast, the metric serves the twin purpose o=
f finding low-power multicast paths as well as multicast replication points=
.  We evolve multiple techniques at various hierarchical levels. One at the=
 Inter-AS level, Inter-Area level within the AS and intra-Area within an AS=
. Additionally, the proposed method can also be used to determine disjoint =
or redundant paths for load balancing or fault tolerance. Additionally sinc=
e TCAMs are one of the biggest power guzzlers in all the components on a ro=
uter/switch, we have presented a solution for intra-AS purposes to use the =
TCAM according to the traffic matrix passing through the system and shut do=
wn those TCAM banks that are unused. With this in mind, we have also advoca=
ted taking into account a TCAM-POWER-Ratio in order to compute the paths fr=
om source to destination based on this metric. Once low-power paths, in eit=
her the unicast or the multicast cases, are identified then currently avail=
able traffic engineering techniques could be used to route the data packets=
. In the case of inter-AS BGP path selection is also modified to arrive at =
paths which are low-power paths.

 Our main objective is as follows...

We now outline four important aspects that any approach for power reduction=
 should be capable of addressing.

 Should cater for both unicast and multicast scenarios

Multicast provides an important scenario for the Internet. Today, most prop=
osals consider mainly low-power path routing with unicast traffic. Multicas=
t traffic has received a lot of attention in wireless networks, but not in =
the wired domain. Any new proposal should be able to address both the unica=
st and the multicast traffic scenarios. Having different methods for these =
two scenarios might lead to unnecessary processing burden in the routers, w=
hich might hinder its scalability.

 Should not rely on just switching off unused links

Most approaches to optimize energy pursue the following approach: measure, =
monitor and respond to the system energy usage by switching off unused or u=
nder-utilized links. Such an approach could be effective for reducing power=
 locally. The effect on the network is not clearly understood. Further, the=
 power usage involved in turning on and rebooting/reconfiguring the device =
is often not explicitly considered. We note that Service Level Agreement (S=
LA) requirements may not even permit the links to be switched off. Also ser=
vices provided by ISPs like Virtual Private Networks (VPNs) can be affected=
 by such re-routing decisions.

 Should follow an hierarchical and distributed approach

For scalability, it is important that the algorithms proposed for inter-AS =
should also be applicable to intra-AS situations. Networks do not work in i=
solation, so any proposal should be both distributed and hierarchical. The =
algorithms should be applicable at every level of the hierarchy.

 Should  provide incentives for ISP for adoption

The engineering proposals should be aligned with commercial incentives for =
rapid and widespread adoption. Today, the device manufacturers and the ISPs=
 operate independently of each other, and there is no incentive for manufac=
turers to work towards low-power and high bandwidth devices. An ISP's reven=
ue model is based on the consumed bandwidth, which in turn lead naturally t=
o more power consumption. If the proposed method chooses routers that consu=
me low-power and increase the data flow through them, then this indirectly =
provides encouragement for ISPs to purchase low-power and high bandwidth de=
vices.



We now present our metric-based proposals in the below mentioned drafts whi=
ch addresses the aforementioned design aspects.

We would like the routing community to provide feedback on these drafts. We=
 also intend to present this work in an abridged format in the upcoming IET=
F.
 The drafts are as follows....


*         mjsraman-panet-bgp-power-path<http://tools.ietf.org/html/draft-mj=
sraman-panet-bgp-power-path> (timeline)<http://www.arkko.com/tools/lifecycl=
e/draft-mjsraman-panet-bgp-power-path-timing.html> Inter-AS-Proposal
*         mjsraman-panet-ecmp-redirect-power-repl-cap<http://tools.ietf.org=
/html/draft-mjsraman-panet-ecmp-redirect-power-repl-cap> (timeline)<http://=
www.arkko.com/tools/lifecycle/draft-mjsraman-panet-ecmp-redirect-power-repl=
-cap-timing.html> Multicast
*         mjsraman-panet-inter-as-power-source<http://tools.ietf.org/html/d=
raft-mjsraman-panet-inter-as-power-source> (timeline)<http://www.arkko.com/=
tools/lifecycle/draft-mjsraman-panet-inter-as-power-source-timing.html> Int=
er-AS Proposal
*         mjsraman-panet-inter-as-psp<http://tools.ietf.org/html/draft-mjsr=
aman-panet-inter-as-psp> (timeline)<http://www.arkko.com/tools/lifecycle/dr=
aft-mjsraman-panet-inter-as-psp-timing.html> Inter-AS Proposal
*         mjsraman-panet-inter-as-psp-protect<http://tools.ietf.org/html/dr=
aft-mjsraman-panet-inter-as-psp-protect> (timeline)<http://www.arkko.com/to=
ols/lifecycle/draft-mjsraman-panet-inter-as-psp-protect-timing.html> Inter-=
AS Proposal
*         mjsraman-panet-pce-power-mcast-replic<http://tools.ietf.org/html/=
draft-mjsraman-panet-pce-power-mcast-replic> (timeline)<http://www.arkko.co=
m/tools/lifecycle/draft-mjsraman-panet-pce-power-mcast-replic-timing.html> =
Multicast
*         mjsraman-panet-pim-power<http://tools.ietf.org/html/draft-mjsrama=
n-panet-pim-power> (timeline)<http://www.arkko.com/tools/lifecycle/draft-mj=
sraman-panet-pim-power-timing.html> Multicast
*         mjsraman-panet-tcam-power-efficiency<http://tools.ietf.org/html/d=
raft-mjsraman-panet-tcam-power-efficiency> (timeline)<http://www.arkko.com/=
tools/lifecycle/draft-mjsraman-panet-tcam-power-efficiency-timing.html> TCA=
M related
*         mjsraman-panet-tcam-power-ratio<http://tools.ietf.org/html/draft-=
mjsraman-panet-tcam-power-ratio> (timeline<http://www.arkko.com/tools/lifec=
ycle/draft-mjsraman-panet-tcam-power-ratio-timing.html>) TCAM related
*         mjsraman-pce-power-replic<http://tools.ietf.org/html/draft-mjsram=
an-pce-power-replic> (timeline)<http://www.arkko.com/tools/lifecycle/draft-=
mjsraman-pce-power-replic-timing.html> Multicast
*         mjsraman-panet-intra-as-psp-te-leak<http://tools.ietf.org/html/dr=
aft-mjsraman-panet-intra-as-psp-te-leak> (timeline)<http://www.arkko.com/to=
ols/lifecycle/draft-mjsraman-panet-intra-as-psp-te-leak-timing.html> Inter-=
Area within an AS
*         mjsraman-panet-ospf-power-topo<http://tools.ietf.org/html/draft-m=
jsraman-panet-ospf-power-topo> (timeline)<http://www.arkko.com/tools/lifecy=
cle/draft-mjsraman-panet-ospf-power-topo-timing.html> Intra-Area within an =
AS
We understand it is a lot of matter to go through. We would much appreciate=
 if some of you could review the inter-AS proposals while others take up mu=
lticast and Intra-AS unicast and multicast.

Thanks again for your time on this matter.

thanks and regards,
balaji venkat

--_000_9904FB1B0159DA42B0B887B7FA8119CA082E38AZFFEXMB04globala_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 12 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:Wingdings;
	panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
	{font-family:Wingdings;
	panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p
	{mso-style-priority:99;
	mso-margin-top-alt:auto;
	margin-right:0in;
	mso-margin-bottom-alt:auto;
	margin-left:0in;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
span.EmailStyle18
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;}
div.WordSection1
	{page:WordSection1;}
/* List Definitions */
@list l0
	{mso-list-id:2010475288;
	mso-list-template-ids:-1465632976;}
@list l0:level1
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:.5in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
ol
	{margin-bottom:0in;}
ul
	{margin-bottom:0in;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">Hi Balaji,<o:p></o:p></sp=
an></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">Is the scope of the work =
that you propose different of EERG, &nbsp;could it be part of EERG, or an e=
xtension?
<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">Thanks and Regards,<o:p><=
/o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">Dan<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<div style=3D"border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in =
4.0pt">
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span style=3D"font-s=
ize:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> irtf-dis=
cuss-bounces@irtf.org [mailto:irtf-discuss-bounces@irtf.org]
<b>On Behalf Of </b>Balaji venkat Venkataswami<br>
<b>Sent:</b> Wednesday, February 06, 2013 8:58 AM<br>
<b>To:</b> irtf-discuss@irtf.org; Lars Eggert; Susan Hares<br>
<b>Subject:</b> [irtf-discuss] Request for a side-bar meeting in the IETF O=
rlando on Power-Aware Networking drafts<o:p></o:p></span></p>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Dear Lars, all,<o:p></o:p></p>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">We would like a side-bar meeting (in an adjacent roo=
m) to discuss the following Power-Aware-Networking proposals.<o:p></o:p></p=
>
</div>
<div>
<p class=3D"MsoNormal">A detailed outline of the drafts submitted have been=
 detailed below. We would like a 20 minute slot with 10 minutes for Q&amp;A=
 if possible.<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal">We would however concur with whatever time you give =
us on this matter.<o:p></o:p></p>
</div>
<div>
<p style=3D"background:white"><span style=3D"font-size:10.0pt;font-family:&=
quot;Arial&quot;,&quot;sans-serif&quot;;color:#222222">We are a group of re=
search and industry individuals tied together with a common goal towards re=
ducing the energy consumption in the core and edge networks.<o:p></o:p></sp=
an></p>
<p style=3D"background:white"><span style=3D"font-size:10.0pt;font-family:&=
quot;Arial&quot;,&quot;sans-serif&quot;;color:#222222">We present a metric-=
based hierarchical approach to reduce power consumption in core and edge ne=
tworks. The proposal considers both unicast and the multicast
 cases. For unicast, the metric considered is&nbsp;<i>consumed-power to ava=
ilable-bandwidth</i>&nbsp;and for multicast the metric is&nbsp;<i>consumed-=
power to available-replication-capacity.</i><o:p></o:p></span></p>
<p style=3D"background:white"><span style=3D"font-size:10.0pt;font-family:&=
quot;Arial&quot;,&quot;sans-serif&quot;;color:#222222">&nbsp;With unicast, =
the metric is&nbsp;used to determine a low-power path between sources and d=
estinations.&nbsp;With multicast, the&nbsp;metric serves the twin purpose o=
f
 finding low-power multicast paths as well as multicast replication points.=
&nbsp;&nbsp;We evolve multiple techniques at various hierarchical levels. O=
ne at the Inter-AS level, Inter-Area level within the AS and intra-Area wit=
hin an AS. Additionally, the proposed method
 can also be used to determine disjoint or redundant paths for load balanci=
ng or fault tolerance. Additionally since TCAMs are one of the biggest powe=
r guzzlers in all the components on a router/switch, we have presented a so=
lution for intra-AS purposes to
 use the TCAM according to the traffic matrix passing through the system an=
d shut down those TCAM banks that are unused. With this in mind, we have al=
so advocated taking into account a TCAM-POWER-Ratio in order to compute the=
 paths from source to destination
 based on this metric. Once low-power paths, in either the unicast or the m=
ulticast cases, are identified then currently available traffic engineering=
 techniques could be used to route the data packets. In the case of inter-A=
S BGP path selection is also modified
 to arrive at paths which are low-power paths.<o:p></o:p></span></p>
<p style=3D"background:white"><span style=3D"font-size:10.0pt;font-family:&=
quot;Arial&quot;,&quot;sans-serif&quot;;color:#222222">&nbsp;Our main objec=
tive is as follows...<o:p></o:p></span></p>
<p style=3D"background:white"><span style=3D"font-size:10.0pt;font-family:&=
quot;Arial&quot;,&quot;sans-serif&quot;;color:#222222">We now outline four =
important aspects that any approach for power reduction should be capable o=
f addressing.<o:p></o:p></span></p>
<p style=3D"background:white"><span style=3D"font-size:10.0pt;font-family:&=
quot;Arial&quot;,&quot;sans-serif&quot;;color:#222222">&nbsp;<i>Should cate=
r for both unicast and multicast scenarios</i><o:p></o:p></span></p>
<p style=3D"background:white"><span style=3D"font-size:10.0pt;font-family:&=
quot;Arial&quot;,&quot;sans-serif&quot;;color:#222222">Multicast provides a=
n important scenario for the Internet. Today, most proposals consider mainl=
y low-power path routing with unicast traffic. Multicast
 traffic has received a lot of attention in wireless networks, but not in t=
he wired domain. Any new proposal should be able to address both the unicas=
t and the multicast traffic scenarios. Having different methods for these t=
wo scenarios might lead to unnecessary
 processing burden in the routers, which might hinder its scalability.&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<o:p></o:p></span></p>
<p style=3D"background:white"><span style=3D"font-size:10.0pt;font-family:&=
quot;Arial&quot;,&quot;sans-serif&quot;;color:#222222">&nbsp;<i>Should not =
rely on just switching off unused links</i><o:p></o:p></span></p>
<p style=3D"background:white"><span style=3D"font-size:10.0pt;font-family:&=
quot;Arial&quot;,&quot;sans-serif&quot;;color:#222222">Most approaches to o=
ptimize energy pursue the following approach: measure, monitor and respond =
to the system energy usage by switching off unused or under-utilized
 links. Such an approach could be effective for reducing power locally. The=
 effect on the network is not clearly understood. Further, the power usage =
involved in turning on and rebooting/reconfiguring the device is often not =
explicitly considered. We note that
 Service Level Agreement (SLA) requirements may not even permit the links t=
o be switched off. Also services provided by ISPs like Virtual Private Netw=
orks (VPNs) can be affected by such re-routing decisions.<o:p></o:p></span>=
</p>
<p style=3D"background:white"><span style=3D"font-size:10.0pt;font-family:&=
quot;Arial&quot;,&quot;sans-serif&quot;;color:#222222">&nbsp;<i>Should foll=
ow an hierarchical and distributed approach</i><o:p></o:p></span></p>
<p style=3D"background:white"><span style=3D"font-size:10.0pt;font-family:&=
quot;Arial&quot;,&quot;sans-serif&quot;;color:#222222">For scalability, it =
is important that the algorithms proposed for inter-AS should also be appli=
cable to intra-AS situations. Networks do not work in isolation,
 so any proposal should be both distributed and hierarchical. The algorithm=
s should be applicable at every level of the hierarchy.&nbsp;&nbsp;<o:p></o=
:p></span></p>
<p style=3D"background:white"><span style=3D"font-size:10.0pt;font-family:&=
quot;Arial&quot;,&quot;sans-serif&quot;;color:#222222">&nbsp;<i>Should&nbsp=
;&nbsp;provide incentives for ISP for adoption</i><o:p></o:p></span></p>
<p style=3D"background:white"><span style=3D"font-size:10.0pt;font-family:&=
quot;Arial&quot;,&quot;sans-serif&quot;;color:#222222">The engineering prop=
osals should be aligned with commercial incentives for rapid and widespread=
 adoption. Today, the device manufacturers and the ISPs
 operate independently of each other, and there is no incentive for manufac=
turers to work towards low-power and high bandwidth devices. An ISP&#8217;s=
 revenue model is based on the consumed bandwidth, which in turn lead natur=
ally to more power consumption. If the
 proposed method chooses routers that consume low-power and increase the da=
ta flow through them, then this indirectly provides encouragement for ISPs =
to purchase low-power and high bandwidth devices.&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<o:p>=
</o:p></span></p>
<p style=3D"background:white"><span style=3D"font-size:10.0pt;font-family:&=
quot;Arial&quot;,&quot;sans-serif&quot;;color:#222222">&nbsp;<o:p></o:p></s=
pan></p>
<p style=3D"background:white"><span style=3D"font-size:10.0pt;font-family:&=
quot;Arial&quot;,&quot;sans-serif&quot;;color:#222222">We now present our m=
etric-based proposals in the below mentioned drafts which addresses the afo=
rementioned design aspects.<o:p></o:p></span></p>
<p style=3D"background:white"><span style=3D"font-size:10.0pt;font-family:&=
quot;Arial&quot;,&quot;sans-serif&quot;;color:#222222">We would like the ro=
uting community to provide feedback on these drafts. We also intend to pres=
ent this work in an abridged format in the upcoming IETF.<o:p></o:p></span>=
</p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto;background:white">
<span style=3D"font-size:11.0pt;font-family:&quot;Arial&quot;,&quot;sans-se=
rif&quot;;color:#222222">&nbsp;The drafts are as follows....</span><span st=
yle=3D"font-size:10.0pt;font-family:&quot;Arial&quot;,&quot;sans-serif&quot=
;;color:#222222"><o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto;background:white">
<span style=3D"font-size:10.0pt;font-family:&quot;Arial&quot;,&quot;sans-se=
rif&quot;;color:#222222"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto;background:white">
<span style=3D"font-size:10.0pt;font-family:&quot;Arial&quot;,&quot;sans-se=
rif&quot;;color:#222222"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;margin-right:12.0pt=
;margin-bottom:3.0pt;margin-left:23.25pt;text-indent:-.25in;mso-list:l0 lev=
el1 lfo1;background:white">
<![if !supportLists]><span style=3D"font-size:10.0pt;font-family:Symbol;col=
or:#222222"><span style=3D"mso-list:Ignore">&middot;<span style=3D"font:7.0=
pt &quot;Times New Roman&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;
</span></span></span><![endif]><span dir=3D"LTR"></span><span style=3D"font=
-size:10.0pt;font-family:&quot;Arial&quot;,&quot;sans-serif&quot;;color:#22=
2222"><a href=3D"http://tools.ietf.org/html/draft-mjsraman-panet-bgp-power-=
path" target=3D"_blank"><span style=3D"color:#440088">mjsraman-panet-bgp-po=
wer-path</span></a>&nbsp;<a href=3D"http://www.arkko.com/tools/lifecycle/dr=
aft-mjsraman-panet-bgp-power-path-timing.html" target=3D"_blank"><span styl=
e=3D"color:#440088">(timeline)</span></a>&nbsp;Inter-AS-Proposal<o:p></o:p>=
</span></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;margin-right:12.0pt=
;margin-bottom:3.0pt;margin-left:23.25pt;text-indent:-.25in;mso-list:l0 lev=
el1 lfo1;background:white">
<![if !supportLists]><span style=3D"font-size:10.0pt;font-family:Symbol;col=
or:#222222"><span style=3D"mso-list:Ignore">&middot;<span style=3D"font:7.0=
pt &quot;Times New Roman&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;
</span></span></span><![endif]><span dir=3D"LTR"></span><span style=3D"font=
-size:10.0pt;font-family:&quot;Arial&quot;,&quot;sans-serif&quot;;color:#22=
2222"><a href=3D"http://tools.ietf.org/html/draft-mjsraman-panet-ecmp-redir=
ect-power-repl-cap" target=3D"_blank"><span style=3D"color:#440088">mjsrama=
n-panet-ecmp-redirect-power-repl-cap</span></a>&nbsp;<a href=3D"http://www.=
arkko.com/tools/lifecycle/draft-mjsraman-panet-ecmp-redirect-power-repl-cap=
-timing.html" target=3D"_blank"><span style=3D"color:#440088">(timeline)</s=
pan></a>&nbsp;Multicast<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;margin-right:12.0pt=
;margin-bottom:3.0pt;margin-left:23.25pt;text-indent:-.25in;mso-list:l0 lev=
el1 lfo1;background:white">
<![if !supportLists]><span style=3D"font-size:10.0pt;font-family:Symbol;col=
or:#222222"><span style=3D"mso-list:Ignore">&middot;<span style=3D"font:7.0=
pt &quot;Times New Roman&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;
</span></span></span><![endif]><span dir=3D"LTR"></span><span style=3D"font=
-size:10.0pt;font-family:&quot;Arial&quot;,&quot;sans-serif&quot;;color:#22=
2222"><a href=3D"http://tools.ietf.org/html/draft-mjsraman-panet-inter-as-p=
ower-source" target=3D"_blank"><span style=3D"color:#440088">mjsraman-panet=
-inter-as-power-source</span></a>&nbsp;<a href=3D"http://www.arkko.com/tool=
s/lifecycle/draft-mjsraman-panet-inter-as-power-source-timing.html" target=
=3D"_blank"><span style=3D"color:#440088">(timeline)</span></a>&nbsp;Inter-=
AS
 Proposal<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;margin-right:12.0pt=
;margin-bottom:3.0pt;margin-left:23.25pt;text-indent:-.25in;mso-list:l0 lev=
el1 lfo1;background:white">
<![if !supportLists]><span style=3D"font-size:10.0pt;font-family:Symbol;col=
or:#222222"><span style=3D"mso-list:Ignore">&middot;<span style=3D"font:7.0=
pt &quot;Times New Roman&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;
</span></span></span><![endif]><span dir=3D"LTR"></span><span style=3D"font=
-size:10.0pt;font-family:&quot;Arial&quot;,&quot;sans-serif&quot;;color:#22=
2222"><a href=3D"http://tools.ietf.org/html/draft-mjsraman-panet-inter-as-p=
sp" target=3D"_blank"><span style=3D"color:#440088">mjsraman-panet-inter-as=
-psp</span></a>&nbsp;<a href=3D"http://www.arkko.com/tools/lifecycle/draft-=
mjsraman-panet-inter-as-psp-timing.html" target=3D"_blank"><span style=3D"c=
olor:#440088">(timeline)</span></a>&nbsp;Inter-AS
 Proposal<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;margin-right:12.0pt=
;margin-bottom:3.0pt;margin-left:23.25pt;text-indent:-.25in;mso-list:l0 lev=
el1 lfo1;background:white">
<![if !supportLists]><span style=3D"font-size:10.0pt;font-family:Symbol;col=
or:#222222"><span style=3D"mso-list:Ignore">&middot;<span style=3D"font:7.0=
pt &quot;Times New Roman&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;
</span></span></span><![endif]><span dir=3D"LTR"></span><span style=3D"font=
-size:10.0pt;font-family:&quot;Arial&quot;,&quot;sans-serif&quot;;color:#22=
2222"><a href=3D"http://tools.ietf.org/html/draft-mjsraman-panet-inter-as-p=
sp-protect" target=3D"_blank"><span style=3D"color:#440088">mjsraman-panet-=
inter-as-psp-protect</span></a>&nbsp;<a href=3D"http://www.arkko.com/tools/=
lifecycle/draft-mjsraman-panet-inter-as-psp-protect-timing.html" target=3D"=
_blank"><span style=3D"color:#440088">(timeline)</span></a>&nbsp;Inter-AS
 Proposal<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;margin-right:12.0pt=
;margin-bottom:3.0pt;margin-left:23.25pt;text-indent:-.25in;mso-list:l0 lev=
el1 lfo1;background:white">
<![if !supportLists]><span style=3D"font-size:10.0pt;font-family:Symbol;col=
or:#222222"><span style=3D"mso-list:Ignore">&middot;<span style=3D"font:7.0=
pt &quot;Times New Roman&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;
</span></span></span><![endif]><span dir=3D"LTR"></span><span style=3D"font=
-size:10.0pt;font-family:&quot;Arial&quot;,&quot;sans-serif&quot;;color:#22=
2222"><a href=3D"http://tools.ietf.org/html/draft-mjsraman-panet-pce-power-=
mcast-replic" target=3D"_blank"><span style=3D"color:#440088">mjsraman-pane=
t-pce-power-mcast-replic</span></a>&nbsp;<a href=3D"http://www.arkko.com/to=
ols/lifecycle/draft-mjsraman-panet-pce-power-mcast-replic-timing.html" targ=
et=3D"_blank"><span style=3D"color:#440088">(timeline)</span></a>&nbsp;Mult=
icast<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;margin-right:12.0pt=
;margin-bottom:3.0pt;margin-left:23.25pt;text-indent:-.25in;mso-list:l0 lev=
el1 lfo1;background:white">
<![if !supportLists]><span style=3D"font-size:10.0pt;font-family:Symbol;col=
or:#222222"><span style=3D"mso-list:Ignore">&middot;<span style=3D"font:7.0=
pt &quot;Times New Roman&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;
</span></span></span><![endif]><span dir=3D"LTR"></span><span style=3D"font=
-size:10.0pt;font-family:&quot;Arial&quot;,&quot;sans-serif&quot;;color:#22=
2222"><a href=3D"http://tools.ietf.org/html/draft-mjsraman-panet-pim-power"=
 target=3D"_blank"><span style=3D"color:#440088">mjsraman-panet-pim-power</=
span></a>&nbsp;<a href=3D"http://www.arkko.com/tools/lifecycle/draft-mjsram=
an-panet-pim-power-timing.html" target=3D"_blank"><span style=3D"color:#440=
088">(timeline)</span></a>&nbsp;Multicast<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;margin-right:12.0pt=
;margin-bottom:3.0pt;margin-left:23.25pt;text-indent:-.25in;mso-list:l0 lev=
el1 lfo1;background:white">
<![if !supportLists]><span style=3D"font-size:10.0pt;font-family:Symbol;col=
or:#222222"><span style=3D"mso-list:Ignore">&middot;<span style=3D"font:7.0=
pt &quot;Times New Roman&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;
</span></span></span><![endif]><span dir=3D"LTR"></span><span style=3D"font=
-size:10.0pt;font-family:&quot;Arial&quot;,&quot;sans-serif&quot;;color:#22=
2222"><a href=3D"http://tools.ietf.org/html/draft-mjsraman-panet-tcam-power=
-efficiency" target=3D"_blank"><span style=3D"color:#440088">mjsraman-panet=
-tcam-power-efficiency</span></a>&nbsp;<a href=3D"http://www.arkko.com/tool=
s/lifecycle/draft-mjsraman-panet-tcam-power-efficiency-timing.html" target=
=3D"_blank"><span style=3D"color:#440088">(timeline)</span></a>&nbsp;TCAM
 related<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;margin-right:12.0pt=
;margin-bottom:3.0pt;margin-left:23.25pt;text-indent:-.25in;mso-list:l0 lev=
el1 lfo1;background:white">
<![if !supportLists]><span style=3D"font-size:10.0pt;font-family:Symbol;col=
or:#222222"><span style=3D"mso-list:Ignore">&middot;<span style=3D"font:7.0=
pt &quot;Times New Roman&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;
</span></span></span><![endif]><span dir=3D"LTR"></span><span style=3D"font=
-size:10.0pt;font-family:&quot;Arial&quot;,&quot;sans-serif&quot;;color:#22=
2222"><a href=3D"http://tools.ietf.org/html/draft-mjsraman-panet-tcam-power=
-ratio" target=3D"_blank"><span style=3D"color:#440088">mjsraman-panet-tcam=
-power-ratio</span></a>&nbsp;<a href=3D"http://www.arkko.com/tools/lifecycl=
e/draft-mjsraman-panet-tcam-power-ratio-timing.html" target=3D"_blank"><spa=
n style=3D"color:#440088">(timeline</span></a>)
 TCAM related<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;margin-right:12.0pt=
;margin-bottom:3.0pt;margin-left:23.25pt;text-indent:-.25in;mso-list:l0 lev=
el1 lfo1;background:white">
<![if !supportLists]><span style=3D"font-size:10.0pt;font-family:Symbol;col=
or:#222222"><span style=3D"mso-list:Ignore">&middot;<span style=3D"font:7.0=
pt &quot;Times New Roman&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;
</span></span></span><![endif]><span dir=3D"LTR"></span><span style=3D"font=
-size:10.0pt;font-family:&quot;Arial&quot;,&quot;sans-serif&quot;;color:#22=
2222"><a href=3D"http://tools.ietf.org/html/draft-mjsraman-pce-power-replic=
" target=3D"_blank"><span style=3D"color:#440088">mjsraman-pce-power-replic=
</span></a>&nbsp;<a href=3D"http://www.arkko.com/tools/lifecycle/draft-mjsr=
aman-pce-power-replic-timing.html" target=3D"_blank"><span style=3D"color:#=
440088">(timeline)</span></a>&nbsp;Multicast<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;margin-right:12.0pt=
;margin-bottom:3.0pt;margin-left:23.25pt;text-indent:-.25in;mso-list:l0 lev=
el1 lfo1;background:white">
<![if !supportLists]><span style=3D"font-size:10.0pt;font-family:Symbol;col=
or:#222222"><span style=3D"mso-list:Ignore">&middot;<span style=3D"font:7.0=
pt &quot;Times New Roman&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;
</span></span></span><![endif]><span dir=3D"LTR"></span><span style=3D"font=
-size:10.0pt;font-family:&quot;Arial&quot;,&quot;sans-serif&quot;;color:#22=
2222"><a href=3D"http://tools.ietf.org/html/draft-mjsraman-panet-intra-as-p=
sp-te-leak" target=3D"_blank"><span style=3D"color:#440088">mjsraman-panet-=
intra-as-psp-te-leak</span></a>&nbsp;<a href=3D"http://www.arkko.com/tools/=
lifecycle/draft-mjsraman-panet-intra-as-psp-te-leak-timing.html" target=3D"=
_blank"><span style=3D"color:#440088">(timeline)</span></a>&nbsp;Inter-Area
 within an AS<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;margin-right:12.0pt=
;margin-bottom:3.0pt;margin-left:23.25pt;text-indent:-.25in;mso-list:l0 lev=
el1 lfo1;background:white">
<![if !supportLists]><span style=3D"font-size:10.0pt;font-family:Symbol;col=
or:#222222"><span style=3D"mso-list:Ignore">&middot;<span style=3D"font:7.0=
pt &quot;Times New Roman&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;
</span></span></span><![endif]><span dir=3D"LTR"></span><span style=3D"font=
-size:10.0pt;font-family:&quot;Arial&quot;,&quot;sans-serif&quot;;color:#22=
2222"><a href=3D"http://tools.ietf.org/html/draft-mjsraman-panet-ospf-power=
-topo" target=3D"_blank"><span style=3D"color:#440088">mjsraman-panet-ospf-=
power-topo</span></a>&nbsp;<a href=3D"http://www.arkko.com/tools/lifecycle/=
draft-mjsraman-panet-ospf-power-topo-timing.html" target=3D"_blank"><span s=
tyle=3D"color:#440088">(timeline)</span></a>&nbsp;Intra-Area
 within an AS<o:p></o:p></span></p>
<div>
<p class=3D"MsoNormal" style=3D"background:white"><span style=3D"font-size:=
10.0pt;font-family:&quot;Arial&quot;,&quot;sans-serif&quot;;color:#222222">=
We understand it is a lot of matter to go through. We would much appreciate=
 if some of you could review the inter-AS proposals while
 others take up multicast and Intra-AS unicast and multicast.<o:p></o:p></s=
pan></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"background:white"><span style=3D"font-size:=
10.0pt;font-family:&quot;Arial&quot;,&quot;sans-serif&quot;;color:#222222">=
<o:p>&nbsp;</o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"background:white"><span style=3D"font-size:=
10.0pt;font-family:&quot;Arial&quot;,&quot;sans-serif&quot;;color:#222222">=
Thanks again for your time on this matter.<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"background:white"><span style=3D"font-size:=
10.0pt;font-family:&quot;Arial&quot;,&quot;sans-serif&quot;;color:#222222">=
<o:p>&nbsp;</o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"background:white"><span style=3D"font-size:=
10.0pt;font-family:&quot;Arial&quot;,&quot;sans-serif&quot;;color:#222222">=
thanks and regards,<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"background:white"><span style=3D"font-size:=
10.0pt;font-family:&quot;Arial&quot;,&quot;sans-serif&quot;;color:#222222">=
balaji venkat<o:p></o:p></span></p>
</div>
</div>
</div>
</div>
</body>
</html>

--_000_9904FB1B0159DA42B0B887B7FA8119CA082E38AZFFEXMB04globala_--

From dromasca@avaya.com  Wed Feb  6 02:47:35 2013
Return-Path: <dromasca@avaya.com>
X-Original-To: irtf-discuss@ietfa.amsl.com
Delivered-To: irtf-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1B25521F8984 for <irtf-discuss@ietfa.amsl.com>; Wed,  6 Feb 2013 02:47:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.507
X-Spam-Level: 
X-Spam-Status: No, score=-102.507 tagged_above=-999 required=5 tests=[AWL=-0.708, BAYES_00=-2.599, HTML_MESSAGE=0.001, SARE_SUB_RAND_LETTRS4=0.799, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6a1tA0wQe0of for <irtf-discuss@ietfa.amsl.com>; Wed,  6 Feb 2013 02:47:31 -0800 (PST)
Received: from p-us1-iereast-outbound.us1.avaya.com (p-us1-iereast-outbound.us1.avaya.com [135.11.29.13]) by ietfa.amsl.com (Postfix) with ESMTP id DEA2421F8481 for <irtf-discuss@irtf.org>; Wed,  6 Feb 2013 02:47:30 -0800 (PST)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AqcFAP0QA1GHCzI1/2dsb2JhbABFgkgjskwBiRoWc4IeAQEBAQMSG0wQAgEIDQQEAQELCwsBAgQHMhQJCAIEAQ0FCAwHB4dtAQuhWJx0jRV1glRhA5IgOoRPhHGKO4J3giQ
X-IronPort-AV: E=Sophos;i="4.84,541,1355115600"; d="scan'208,217";a="47592167"
Received: from unknown (HELO p-us1-erheast.us1.avaya.com) ([135.11.50.53]) by p-us1-iereast-outbound.us1.avaya.com with ESMTP; 06 Feb 2013 05:46:20 -0500
Received: from unknown (HELO AZ-FFEXHC03.global.avaya.com) ([135.64.58.13]) by p-us1-erheast-out.us1.avaya.com with ESMTP; 06 Feb 2013 05:47:01 -0500
Received: from AZ-FFEXMB04.global.avaya.com ([fe80::6db7:b0af:8480:c126]) by AZ-FFEXHC03.global.avaya.com ([135.64.58.13]) with mapi id 14.02.0328.009; Wed, 6 Feb 2013 05:47:48 -0500
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: Balaji venkat Venkataswami <balajivenkat299@gmail.com>, "irtf-discuss@irtf.org" <irtf-discuss@irtf.org>, Susan Hares <susan.hares@huawei.com>, Lars Eggert <lars@netapp.com>
Thread-Topic: [irtf-discuss] Request for a side-bar meeting in the IETF Orlando on Power-Aware Networking drafts
Thread-Index: AQHOBDdWB+gPQyOI+kugTUCpXgQUH5hspTOQ
Date: Wed, 6 Feb 2013 10:47:47 +0000
Message-ID: <9904FB1B0159DA42B0B887B7FA8119CA082E55@AZ-FFEXMB04.global.avaya.com>
References: <CAHF4apMOpXohhWpYXB8X74yG4fBhcjVW0c=vNW4qXudJ7H92rA@mail.gmail.com>
In-Reply-To: <CAHF4apMOpXohhWpYXB8X74yG4fBhcjVW0c=vNW4qXudJ7H92rA@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [135.64.58.45]
Content-Type: multipart/alternative; boundary="_000_9904FB1B0159DA42B0B887B7FA8119CA082E55AZFFEXMB04globala_"
MIME-Version: 1.0
Cc: "eerg@listserv.netlab.nec.de" <eerg@listserv.netlab.nec.de>
Subject: Re: [irtf-discuss] Request for a side-bar meeting in the IETF Orlando on Power-Aware Networking drafts
X-BeenThere: irtf-discuss@irtf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IRTF general and new-work discussion list <irtf-discuss.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/options/irtf-discuss>, <mailto:irtf-discuss-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/irtf-discuss>
List-Post: <mailto:irtf-discuss@irtf.org>
List-Help: <mailto:irtf-discuss-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/irtf-discuss>, <mailto:irtf-discuss-request@irtf.org?subject=subscribe>
X-List-Received-Date: Wed, 06 Feb 2013 10:47:35 -0000

--_000_9904FB1B0159DA42B0B887B7FA8119CA082E55AZFFEXMB04globala_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

(resending to a better address of Lars, although I am pretty sure that he r=
eads irtf-discuss)

Hi Balaji,

Is the scope of the work that you propose different of EERG,  could it be p=
art of EERG, or an extension?

Thanks and Regards,

Dan



From: irtf-discuss-bounces@irtf.org [mailto:irtf-discuss-bounces@irtf.org] =
On Behalf Of Balaji venkat Venkataswami
Sent: Wednesday, February 06, 2013 8:58 AM
To: irtf-discuss@irtf.org; Lars Eggert; Susan Hares
Subject: [irtf-discuss] Request for a side-bar meeting in the IETF Orlando =
on Power-Aware Networking drafts

Dear Lars, all,

We would like a side-bar meeting (in an adjacent room) to discuss the follo=
wing Power-Aware-Networking proposals.
A detailed outline of the drafts submitted have been detailed below. We wou=
ld like a 20 minute slot with 10 minutes for Q&A if possible.
We would however concur with whatever time you give us on this matter.

We are a group of research and industry individuals tied together with a co=
mmon goal towards reducing the energy consumption in the core and edge netw=
orks.

We present a metric-based hierarchical approach to reduce power consumption=
 in core and edge networks. The proposal considers both unicast and the mul=
ticast cases. For unicast, the metric considered is consumed-power to avail=
able-bandwidth and for multicast the metric is consumed-power to available-=
replication-capacity.

 With unicast, the metric is used to determine a low-power path between sou=
rces and destinations. With multicast, the metric serves the twin purpose o=
f finding low-power multicast paths as well as multicast replication points=
.  We evolve multiple techniques at various hierarchical levels. One at the=
 Inter-AS level, Inter-Area level within the AS and intra-Area within an AS=
. Additionally, the proposed method can also be used to determine disjoint =
or redundant paths for load balancing or fault tolerance. Additionally sinc=
e TCAMs are one of the biggest power guzzlers in all the components on a ro=
uter/switch, we have presented a solution for intra-AS purposes to use the =
TCAM according to the traffic matrix passing through the system and shut do=
wn those TCAM banks that are unused. With this in mind, we have also advoca=
ted taking into account a TCAM-POWER-Ratio in order to compute the paths fr=
om source to destination based on this metric. Once low-power paths, in eit=
her the unicast or the multicast cases, are identified then currently avail=
able traffic engineering techniques could be used to route the data packets=
. In the case of inter-AS BGP path selection is also modified to arrive at =
paths which are low-power paths.

 Our main objective is as follows...

We now outline four important aspects that any approach for power reduction=
 should be capable of addressing.

 Should cater for both unicast and multicast scenarios

Multicast provides an important scenario for the Internet. Today, most prop=
osals consider mainly low-power path routing with unicast traffic. Multicas=
t traffic has received a lot of attention in wireless networks, but not in =
the wired domain. Any new proposal should be able to address both the unica=
st and the multicast traffic scenarios. Having different methods for these =
two scenarios might lead to unnecessary processing burden in the routers, w=
hich might hinder its scalability.

 Should not rely on just switching off unused links

Most approaches to optimize energy pursue the following approach: measure, =
monitor and respond to the system energy usage by switching off unused or u=
nder-utilized links. Such an approach could be effective for reducing power=
 locally. The effect on the network is not clearly understood. Further, the=
 power usage involved in turning on and rebooting/reconfiguring the device =
is often not explicitly considered. We note that Service Level Agreement (S=
LA) requirements may not even permit the links to be switched off. Also ser=
vices provided by ISPs like Virtual Private Networks (VPNs) can be affected=
 by such re-routing decisions.

 Should follow an hierarchical and distributed approach

For scalability, it is important that the algorithms proposed for inter-AS =
should also be applicable to intra-AS situations. Networks do not work in i=
solation, so any proposal should be both distributed and hierarchical. The =
algorithms should be applicable at every level of the hierarchy.

 Should  provide incentives for ISP for adoption

The engineering proposals should be aligned with commercial incentives for =
rapid and widespread adoption. Today, the device manufacturers and the ISPs=
 operate independently of each other, and there is no incentive for manufac=
turers to work towards low-power and high bandwidth devices. An ISP's reven=
ue model is based on the consumed bandwidth, which in turn lead naturally t=
o more power consumption. If the proposed method chooses routers that consu=
me low-power and increase the data flow through them, then this indirectly =
provides encouragement for ISPs to purchase low-power and high bandwidth de=
vices.



We now present our metric-based proposals in the below mentioned drafts whi=
ch addresses the aforementioned design aspects.

We would like the routing community to provide feedback on these drafts. We=
 also intend to present this work in an abridged format in the upcoming IET=
F.
 The drafts are as follows....


*         mjsraman-panet-bgp-power-path<http://tools.ietf.org/html/draft-mj=
sraman-panet-bgp-power-path> (timeline)<http://www.arkko.com/tools/lifecycl=
e/draft-mjsraman-panet-bgp-power-path-timing.html> Inter-AS-Proposal
*         mjsraman-panet-ecmp-redirect-power-repl-cap<http://tools.ietf.org=
/html/draft-mjsraman-panet-ecmp-redirect-power-repl-cap> (timeline)<http://=
www.arkko.com/tools/lifecycle/draft-mjsraman-panet-ecmp-redirect-power-repl=
-cap-timing.html> Multicast
*         mjsraman-panet-inter-as-power-source<http://tools.ietf.org/html/d=
raft-mjsraman-panet-inter-as-power-source> (timeline)<http://www.arkko.com/=
tools/lifecycle/draft-mjsraman-panet-inter-as-power-source-timing.html> Int=
er-AS Proposal
*         mjsraman-panet-inter-as-psp<http://tools.ietf.org/html/draft-mjsr=
aman-panet-inter-as-psp> (timeline)<http://www.arkko.com/tools/lifecycle/dr=
aft-mjsraman-panet-inter-as-psp-timing.html> Inter-AS Proposal
*         mjsraman-panet-inter-as-psp-protect<http://tools.ietf.org/html/dr=
aft-mjsraman-panet-inter-as-psp-protect> (timeline)<http://www.arkko.com/to=
ols/lifecycle/draft-mjsraman-panet-inter-as-psp-protect-timing.html> Inter-=
AS Proposal
*         mjsraman-panet-pce-power-mcast-replic<http://tools.ietf.org/html/=
draft-mjsraman-panet-pce-power-mcast-replic> (timeline)<http://www.arkko.co=
m/tools/lifecycle/draft-mjsraman-panet-pce-power-mcast-replic-timing.html> =
Multicast
*         mjsraman-panet-pim-power<http://tools.ietf.org/html/draft-mjsrama=
n-panet-pim-power> (timeline)<http://www.arkko.com/tools/lifecycle/draft-mj=
sraman-panet-pim-power-timing.html> Multicast
*         mjsraman-panet-tcam-power-efficiency<http://tools.ietf.org/html/d=
raft-mjsraman-panet-tcam-power-efficiency> (timeline)<http://www.arkko.com/=
tools/lifecycle/draft-mjsraman-panet-tcam-power-efficiency-timing.html> TCA=
M related
*         mjsraman-panet-tcam-power-ratio<http://tools.ietf.org/html/draft-=
mjsraman-panet-tcam-power-ratio> (timeline<http://www.arkko.com/tools/lifec=
ycle/draft-mjsraman-panet-tcam-power-ratio-timing.html>) TCAM related
*         mjsraman-pce-power-replic<http://tools.ietf.org/html/draft-mjsram=
an-pce-power-replic> (timeline)<http://www.arkko.com/tools/lifecycle/draft-=
mjsraman-pce-power-replic-timing.html> Multicast
*         mjsraman-panet-intra-as-psp-te-leak<http://tools.ietf.org/html/dr=
aft-mjsraman-panet-intra-as-psp-te-leak> (timeline)<http://www.arkko.com/to=
ols/lifecycle/draft-mjsraman-panet-intra-as-psp-te-leak-timing.html> Inter-=
Area within an AS
*         mjsraman-panet-ospf-power-topo<http://tools.ietf.org/html/draft-m=
jsraman-panet-ospf-power-topo> (timeline)<http://www.arkko.com/tools/lifecy=
cle/draft-mjsraman-panet-ospf-power-topo-timing.html> Intra-Area within an =
AS
We understand it is a lot of matter to go through. We would much appreciate=
 if some of you could review the inter-AS proposals while others take up mu=
lticast and Intra-AS unicast and multicast.

Thanks again for your time on this matter.

thanks and regards,
balaji venkat

--_000_9904FB1B0159DA42B0B887B7FA8119CA082E55AZFFEXMB04globala_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 12 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p
	{mso-style-priority:99;
	mso-margin-top-alt:auto;
	margin-right:0in;
	mso-margin-bottom-alt:auto;
	margin-left:0in;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
span.EmailStyle18
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;}
div.WordSection1
	{page:WordSection1;}
/* List Definitions */
@list l0
	{mso-list-id:2010475288;
	mso-list-template-ids:-1465632976;}
@list l0:level1
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:.5in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l0:level2
	{mso-level-tab-stop:1.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level3
	{mso-level-tab-stop:1.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level4
	{mso-level-tab-stop:2.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level5
	{mso-level-tab-stop:2.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level6
	{mso-level-tab-stop:3.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level7
	{mso-level-tab-stop:3.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level8
	{mso-level-tab-stop:4.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level9
	{mso-level-tab-stop:4.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
ol
	{margin-bottom:0in;}
ul
	{margin-bottom:0in;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">(resending to a better ad=
dress of Lars, although I am pretty sure that he reads irtf-discuss)<o:p></=
o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">Hi Balaji,<o:p></o:p></sp=
an></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">Is the scope of the work =
that you propose different of EERG, &nbsp;could it be part of EERG, or an e=
xtension?
<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">Thanks and Regards,<o:p><=
/o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">Dan<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<div style=3D"border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in =
4.0pt">
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span style=3D"font-s=
ize:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> irtf-dis=
cuss-bounces@irtf.org [mailto:irtf-discuss-bounces@irtf.org]
<b>On Behalf Of </b>Balaji venkat Venkataswami<br>
<b>Sent:</b> Wednesday, February 06, 2013 8:58 AM<br>
<b>To:</b> irtf-discuss@irtf.org; Lars Eggert; Susan Hares<br>
<b>Subject:</b> [irtf-discuss] Request for a side-bar meeting in the IETF O=
rlando on Power-Aware Networking drafts<o:p></o:p></span></p>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Dear Lars, all,<o:p></o:p></p>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">We would like a side-bar meeting (in an adjacent roo=
m) to discuss the following Power-Aware-Networking proposals.<o:p></o:p></p=
>
</div>
<div>
<p class=3D"MsoNormal">A detailed outline of the drafts submitted have been=
 detailed below. We would like a 20 minute slot with 10 minutes for Q&amp;A=
 if possible.<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal">We would however concur with whatever time you give =
us on this matter.<o:p></o:p></p>
</div>
<div>
<p style=3D"background:white"><span style=3D"font-size:10.0pt;font-family:&=
quot;Arial&quot;,&quot;sans-serif&quot;;color:#222222">We are a group of re=
search and industry individuals tied together with a common goal towards re=
ducing the energy consumption in the core and edge networks.<o:p></o:p></sp=
an></p>
<p style=3D"background:white"><span style=3D"font-size:10.0pt;font-family:&=
quot;Arial&quot;,&quot;sans-serif&quot;;color:#222222">We present a metric-=
based hierarchical approach to reduce power consumption in core and edge ne=
tworks. The proposal considers both unicast and the multicast
 cases. For unicast, the metric considered is&nbsp;<i>consumed-power to ava=
ilable-bandwidth</i>&nbsp;and for multicast the metric is&nbsp;<i>consumed-=
power to available-replication-capacity.</i><o:p></o:p></span></p>
<p style=3D"background:white"><span style=3D"font-size:10.0pt;font-family:&=
quot;Arial&quot;,&quot;sans-serif&quot;;color:#222222">&nbsp;With unicast, =
the metric is&nbsp;used to determine a low-power path between sources and d=
estinations.&nbsp;With multicast, the&nbsp;metric serves the twin purpose o=
f
 finding low-power multicast paths as well as multicast replication points.=
&nbsp;&nbsp;We evolve multiple techniques at various hierarchical levels. O=
ne at the Inter-AS level, Inter-Area level within the AS and intra-Area wit=
hin an AS. Additionally, the proposed method
 can also be used to determine disjoint or redundant paths for load balanci=
ng or fault tolerance. Additionally since TCAMs are one of the biggest powe=
r guzzlers in all the components on a router/switch, we have presented a so=
lution for intra-AS purposes to
 use the TCAM according to the traffic matrix passing through the system an=
d shut down those TCAM banks that are unused. With this in mind, we have al=
so advocated taking into account a TCAM-POWER-Ratio in order to compute the=
 paths from source to destination
 based on this metric. Once low-power paths, in either the unicast or the m=
ulticast cases, are identified then currently available traffic engineering=
 techniques could be used to route the data packets. In the case of inter-A=
S BGP path selection is also modified
 to arrive at paths which are low-power paths.<o:p></o:p></span></p>
<p style=3D"background:white"><span style=3D"font-size:10.0pt;font-family:&=
quot;Arial&quot;,&quot;sans-serif&quot;;color:#222222">&nbsp;Our main objec=
tive is as follows...<o:p></o:p></span></p>
<p style=3D"background:white"><span style=3D"font-size:10.0pt;font-family:&=
quot;Arial&quot;,&quot;sans-serif&quot;;color:#222222">We now outline four =
important aspects that any approach for power reduction should be capable o=
f addressing.<o:p></o:p></span></p>
<p style=3D"background:white"><span style=3D"font-size:10.0pt;font-family:&=
quot;Arial&quot;,&quot;sans-serif&quot;;color:#222222">&nbsp;<i>Should cate=
r for both unicast and multicast scenarios</i><o:p></o:p></span></p>
<p style=3D"background:white"><span style=3D"font-size:10.0pt;font-family:&=
quot;Arial&quot;,&quot;sans-serif&quot;;color:#222222">Multicast provides a=
n important scenario for the Internet. Today, most proposals consider mainl=
y low-power path routing with unicast traffic. Multicast
 traffic has received a lot of attention in wireless networks, but not in t=
he wired domain. Any new proposal should be able to address both the unicas=
t and the multicast traffic scenarios. Having different methods for these t=
wo scenarios might lead to unnecessary
 processing burden in the routers, which might hinder its scalability.&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<o:p></o:p></span></p>
<p style=3D"background:white"><span style=3D"font-size:10.0pt;font-family:&=
quot;Arial&quot;,&quot;sans-serif&quot;;color:#222222">&nbsp;<i>Should not =
rely on just switching off unused links</i><o:p></o:p></span></p>
<p style=3D"background:white"><span style=3D"font-size:10.0pt;font-family:&=
quot;Arial&quot;,&quot;sans-serif&quot;;color:#222222">Most approaches to o=
ptimize energy pursue the following approach: measure, monitor and respond =
to the system energy usage by switching off unused or under-utilized
 links. Such an approach could be effective for reducing power locally. The=
 effect on the network is not clearly understood. Further, the power usage =
involved in turning on and rebooting/reconfiguring the device is often not =
explicitly considered. We note that
 Service Level Agreement (SLA) requirements may not even permit the links t=
o be switched off. Also services provided by ISPs like Virtual Private Netw=
orks (VPNs) can be affected by such re-routing decisions.<o:p></o:p></span>=
</p>
<p style=3D"background:white"><span style=3D"font-size:10.0pt;font-family:&=
quot;Arial&quot;,&quot;sans-serif&quot;;color:#222222">&nbsp;<i>Should foll=
ow an hierarchical and distributed approach</i><o:p></o:p></span></p>
<p style=3D"background:white"><span style=3D"font-size:10.0pt;font-family:&=
quot;Arial&quot;,&quot;sans-serif&quot;;color:#222222">For scalability, it =
is important that the algorithms proposed for inter-AS should also be appli=
cable to intra-AS situations. Networks do not work in isolation,
 so any proposal should be both distributed and hierarchical. The algorithm=
s should be applicable at every level of the hierarchy.&nbsp;&nbsp;<o:p></o=
:p></span></p>
<p style=3D"background:white"><span style=3D"font-size:10.0pt;font-family:&=
quot;Arial&quot;,&quot;sans-serif&quot;;color:#222222">&nbsp;<i>Should&nbsp=
;&nbsp;provide incentives for ISP for adoption</i><o:p></o:p></span></p>
<p style=3D"background:white"><span style=3D"font-size:10.0pt;font-family:&=
quot;Arial&quot;,&quot;sans-serif&quot;;color:#222222">The engineering prop=
osals should be aligned with commercial incentives for rapid and widespread=
 adoption. Today, the device manufacturers and the ISPs
 operate independently of each other, and there is no incentive for manufac=
turers to work towards low-power and high bandwidth devices. An ISP&#8217;s=
 revenue model is based on the consumed bandwidth, which in turn lead natur=
ally to more power consumption. If the
 proposed method chooses routers that consume low-power and increase the da=
ta flow through them, then this indirectly provides encouragement for ISPs =
to purchase low-power and high bandwidth devices.&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<o:p>=
</o:p></span></p>
<p style=3D"background:white"><span style=3D"font-size:10.0pt;font-family:&=
quot;Arial&quot;,&quot;sans-serif&quot;;color:#222222">&nbsp;<o:p></o:p></s=
pan></p>
<p style=3D"background:white"><span style=3D"font-size:10.0pt;font-family:&=
quot;Arial&quot;,&quot;sans-serif&quot;;color:#222222">We now present our m=
etric-based proposals in the below mentioned drafts which addresses the afo=
rementioned design aspects.<o:p></o:p></span></p>
<p style=3D"background:white"><span style=3D"font-size:10.0pt;font-family:&=
quot;Arial&quot;,&quot;sans-serif&quot;;color:#222222">We would like the ro=
uting community to provide feedback on these drafts. We also intend to pres=
ent this work in an abridged format in the upcoming IETF.<o:p></o:p></span>=
</p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto;background:white">
<span style=3D"font-size:11.0pt;font-family:&quot;Arial&quot;,&quot;sans-se=
rif&quot;;color:#222222">&nbsp;The drafts are as follows....</span><span st=
yle=3D"font-size:10.0pt;font-family:&quot;Arial&quot;,&quot;sans-serif&quot=
;;color:#222222"><o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto;background:white">
<span style=3D"font-size:10.0pt;font-family:&quot;Arial&quot;,&quot;sans-se=
rif&quot;;color:#222222"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto;background:white">
<span style=3D"font-size:10.0pt;font-family:&quot;Arial&quot;,&quot;sans-se=
rif&quot;;color:#222222"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;margin-right:12.0pt=
;margin-bottom:3.0pt;margin-left:23.25pt;text-indent:-.25in;mso-list:l0 lev=
el1 lfo2;background:white">
<![if !supportLists]><span style=3D"font-size:10.0pt;font-family:Symbol;col=
or:#222222"><span style=3D"mso-list:Ignore">&middot;<span style=3D"font:7.0=
pt &quot;Times New Roman&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;
</span></span></span><![endif]><span dir=3D"LTR"></span><span style=3D"font=
-size:10.0pt;font-family:&quot;Arial&quot;,&quot;sans-serif&quot;;color:#22=
2222"><a href=3D"http://tools.ietf.org/html/draft-mjsraman-panet-bgp-power-=
path" target=3D"_blank"><span style=3D"color:#440088">mjsraman-panet-bgp-po=
wer-path</span></a>&nbsp;<a href=3D"http://www.arkko.com/tools/lifecycle/dr=
aft-mjsraman-panet-bgp-power-path-timing.html" target=3D"_blank"><span styl=
e=3D"color:#440088">(timeline)</span></a>&nbsp;Inter-AS-Proposal<o:p></o:p>=
</span></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;margin-right:12.0pt=
;margin-bottom:3.0pt;margin-left:23.25pt;text-indent:-.25in;mso-list:l0 lev=
el1 lfo2;background:white">
<![if !supportLists]><span style=3D"font-size:10.0pt;font-family:Symbol;col=
or:#222222"><span style=3D"mso-list:Ignore">&middot;<span style=3D"font:7.0=
pt &quot;Times New Roman&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;
</span></span></span><![endif]><span dir=3D"LTR"></span><span style=3D"font=
-size:10.0pt;font-family:&quot;Arial&quot;,&quot;sans-serif&quot;;color:#22=
2222"><a href=3D"http://tools.ietf.org/html/draft-mjsraman-panet-ecmp-redir=
ect-power-repl-cap" target=3D"_blank"><span style=3D"color:#440088">mjsrama=
n-panet-ecmp-redirect-power-repl-cap</span></a>&nbsp;<a href=3D"http://www.=
arkko.com/tools/lifecycle/draft-mjsraman-panet-ecmp-redirect-power-repl-cap=
-timing.html" target=3D"_blank"><span style=3D"color:#440088">(timeline)</s=
pan></a>&nbsp;Multicast<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;margin-right:12.0pt=
;margin-bottom:3.0pt;margin-left:23.25pt;text-indent:-.25in;mso-list:l0 lev=
el1 lfo2;background:white">
<![if !supportLists]><span style=3D"font-size:10.0pt;font-family:Symbol;col=
or:#222222"><span style=3D"mso-list:Ignore">&middot;<span style=3D"font:7.0=
pt &quot;Times New Roman&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;
</span></span></span><![endif]><span dir=3D"LTR"></span><span style=3D"font=
-size:10.0pt;font-family:&quot;Arial&quot;,&quot;sans-serif&quot;;color:#22=
2222"><a href=3D"http://tools.ietf.org/html/draft-mjsraman-panet-inter-as-p=
ower-source" target=3D"_blank"><span style=3D"color:#440088">mjsraman-panet=
-inter-as-power-source</span></a>&nbsp;<a href=3D"http://www.arkko.com/tool=
s/lifecycle/draft-mjsraman-panet-inter-as-power-source-timing.html" target=
=3D"_blank"><span style=3D"color:#440088">(timeline)</span></a>&nbsp;Inter-=
AS
 Proposal<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;margin-right:12.0pt=
;margin-bottom:3.0pt;margin-left:23.25pt;text-indent:-.25in;mso-list:l0 lev=
el1 lfo2;background:white">
<![if !supportLists]><span style=3D"font-size:10.0pt;font-family:Symbol;col=
or:#222222"><span style=3D"mso-list:Ignore">&middot;<span style=3D"font:7.0=
pt &quot;Times New Roman&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;
</span></span></span><![endif]><span dir=3D"LTR"></span><span style=3D"font=
-size:10.0pt;font-family:&quot;Arial&quot;,&quot;sans-serif&quot;;color:#22=
2222"><a href=3D"http://tools.ietf.org/html/draft-mjsraman-panet-inter-as-p=
sp" target=3D"_blank"><span style=3D"color:#440088">mjsraman-panet-inter-as=
-psp</span></a>&nbsp;<a href=3D"http://www.arkko.com/tools/lifecycle/draft-=
mjsraman-panet-inter-as-psp-timing.html" target=3D"_blank"><span style=3D"c=
olor:#440088">(timeline)</span></a>&nbsp;Inter-AS
 Proposal<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;margin-right:12.0pt=
;margin-bottom:3.0pt;margin-left:23.25pt;text-indent:-.25in;mso-list:l0 lev=
el1 lfo2;background:white">
<![if !supportLists]><span style=3D"font-size:10.0pt;font-family:Symbol;col=
or:#222222"><span style=3D"mso-list:Ignore">&middot;<span style=3D"font:7.0=
pt &quot;Times New Roman&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;
</span></span></span><![endif]><span dir=3D"LTR"></span><span style=3D"font=
-size:10.0pt;font-family:&quot;Arial&quot;,&quot;sans-serif&quot;;color:#22=
2222"><a href=3D"http://tools.ietf.org/html/draft-mjsraman-panet-inter-as-p=
sp-protect" target=3D"_blank"><span style=3D"color:#440088">mjsraman-panet-=
inter-as-psp-protect</span></a>&nbsp;<a href=3D"http://www.arkko.com/tools/=
lifecycle/draft-mjsraman-panet-inter-as-psp-protect-timing.html" target=3D"=
_blank"><span style=3D"color:#440088">(timeline)</span></a>&nbsp;Inter-AS
 Proposal<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;margin-right:12.0pt=
;margin-bottom:3.0pt;margin-left:23.25pt;text-indent:-.25in;mso-list:l0 lev=
el1 lfo2;background:white">
<![if !supportLists]><span style=3D"font-size:10.0pt;font-family:Symbol;col=
or:#222222"><span style=3D"mso-list:Ignore">&middot;<span style=3D"font:7.0=
pt &quot;Times New Roman&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;
</span></span></span><![endif]><span dir=3D"LTR"></span><span style=3D"font=
-size:10.0pt;font-family:&quot;Arial&quot;,&quot;sans-serif&quot;;color:#22=
2222"><a href=3D"http://tools.ietf.org/html/draft-mjsraman-panet-pce-power-=
mcast-replic" target=3D"_blank"><span style=3D"color:#440088">mjsraman-pane=
t-pce-power-mcast-replic</span></a>&nbsp;<a href=3D"http://www.arkko.com/to=
ols/lifecycle/draft-mjsraman-panet-pce-power-mcast-replic-timing.html" targ=
et=3D"_blank"><span style=3D"color:#440088">(timeline)</span></a>&nbsp;Mult=
icast<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;margin-right:12.0pt=
;margin-bottom:3.0pt;margin-left:23.25pt;text-indent:-.25in;mso-list:l0 lev=
el1 lfo2;background:white">
<![if !supportLists]><span style=3D"font-size:10.0pt;font-family:Symbol;col=
or:#222222"><span style=3D"mso-list:Ignore">&middot;<span style=3D"font:7.0=
pt &quot;Times New Roman&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;
</span></span></span><![endif]><span dir=3D"LTR"></span><span style=3D"font=
-size:10.0pt;font-family:&quot;Arial&quot;,&quot;sans-serif&quot;;color:#22=
2222"><a href=3D"http://tools.ietf.org/html/draft-mjsraman-panet-pim-power"=
 target=3D"_blank"><span style=3D"color:#440088">mjsraman-panet-pim-power</=
span></a>&nbsp;<a href=3D"http://www.arkko.com/tools/lifecycle/draft-mjsram=
an-panet-pim-power-timing.html" target=3D"_blank"><span style=3D"color:#440=
088">(timeline)</span></a>&nbsp;Multicast<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;margin-right:12.0pt=
;margin-bottom:3.0pt;margin-left:23.25pt;text-indent:-.25in;mso-list:l0 lev=
el1 lfo2;background:white">
<![if !supportLists]><span style=3D"font-size:10.0pt;font-family:Symbol;col=
or:#222222"><span style=3D"mso-list:Ignore">&middot;<span style=3D"font:7.0=
pt &quot;Times New Roman&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;
</span></span></span><![endif]><span dir=3D"LTR"></span><span style=3D"font=
-size:10.0pt;font-family:&quot;Arial&quot;,&quot;sans-serif&quot;;color:#22=
2222"><a href=3D"http://tools.ietf.org/html/draft-mjsraman-panet-tcam-power=
-efficiency" target=3D"_blank"><span style=3D"color:#440088">mjsraman-panet=
-tcam-power-efficiency</span></a>&nbsp;<a href=3D"http://www.arkko.com/tool=
s/lifecycle/draft-mjsraman-panet-tcam-power-efficiency-timing.html" target=
=3D"_blank"><span style=3D"color:#440088">(timeline)</span></a>&nbsp;TCAM
 related<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;margin-right:12.0pt=
;margin-bottom:3.0pt;margin-left:23.25pt;text-indent:-.25in;mso-list:l0 lev=
el1 lfo2;background:white">
<![if !supportLists]><span style=3D"font-size:10.0pt;font-family:Symbol;col=
or:#222222"><span style=3D"mso-list:Ignore">&middot;<span style=3D"font:7.0=
pt &quot;Times New Roman&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;
</span></span></span><![endif]><span dir=3D"LTR"></span><span style=3D"font=
-size:10.0pt;font-family:&quot;Arial&quot;,&quot;sans-serif&quot;;color:#22=
2222"><a href=3D"http://tools.ietf.org/html/draft-mjsraman-panet-tcam-power=
-ratio" target=3D"_blank"><span style=3D"color:#440088">mjsraman-panet-tcam=
-power-ratio</span></a>&nbsp;<a href=3D"http://www.arkko.com/tools/lifecycl=
e/draft-mjsraman-panet-tcam-power-ratio-timing.html" target=3D"_blank"><spa=
n style=3D"color:#440088">(timeline</span></a>)
 TCAM related<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;margin-right:12.0pt=
;margin-bottom:3.0pt;margin-left:23.25pt;text-indent:-.25in;mso-list:l0 lev=
el1 lfo2;background:white">
<![if !supportLists]><span style=3D"font-size:10.0pt;font-family:Symbol;col=
or:#222222"><span style=3D"mso-list:Ignore">&middot;<span style=3D"font:7.0=
pt &quot;Times New Roman&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;
</span></span></span><![endif]><span dir=3D"LTR"></span><span style=3D"font=
-size:10.0pt;font-family:&quot;Arial&quot;,&quot;sans-serif&quot;;color:#22=
2222"><a href=3D"http://tools.ietf.org/html/draft-mjsraman-pce-power-replic=
" target=3D"_blank"><span style=3D"color:#440088">mjsraman-pce-power-replic=
</span></a>&nbsp;<a href=3D"http://www.arkko.com/tools/lifecycle/draft-mjsr=
aman-pce-power-replic-timing.html" target=3D"_blank"><span style=3D"color:#=
440088">(timeline)</span></a>&nbsp;Multicast<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;margin-right:12.0pt=
;margin-bottom:3.0pt;margin-left:23.25pt;text-indent:-.25in;mso-list:l0 lev=
el1 lfo2;background:white">
<![if !supportLists]><span style=3D"font-size:10.0pt;font-family:Symbol;col=
or:#222222"><span style=3D"mso-list:Ignore">&middot;<span style=3D"font:7.0=
pt &quot;Times New Roman&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;
</span></span></span><![endif]><span dir=3D"LTR"></span><span style=3D"font=
-size:10.0pt;font-family:&quot;Arial&quot;,&quot;sans-serif&quot;;color:#22=
2222"><a href=3D"http://tools.ietf.org/html/draft-mjsraman-panet-intra-as-p=
sp-te-leak" target=3D"_blank"><span style=3D"color:#440088">mjsraman-panet-=
intra-as-psp-te-leak</span></a>&nbsp;<a href=3D"http://www.arkko.com/tools/=
lifecycle/draft-mjsraman-panet-intra-as-psp-te-leak-timing.html" target=3D"=
_blank"><span style=3D"color:#440088">(timeline)</span></a>&nbsp;Inter-Area
 within an AS<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;margin-right:12.0pt=
;margin-bottom:3.0pt;margin-left:23.25pt;text-indent:-.25in;mso-list:l0 lev=
el1 lfo2;background:white">
<![if !supportLists]><span style=3D"font-size:10.0pt;font-family:Symbol;col=
or:#222222"><span style=3D"mso-list:Ignore">&middot;<span style=3D"font:7.0=
pt &quot;Times New Roman&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;
</span></span></span><![endif]><span dir=3D"LTR"></span><span style=3D"font=
-size:10.0pt;font-family:&quot;Arial&quot;,&quot;sans-serif&quot;;color:#22=
2222"><a href=3D"http://tools.ietf.org/html/draft-mjsraman-panet-ospf-power=
-topo" target=3D"_blank"><span style=3D"color:#440088">mjsraman-panet-ospf-=
power-topo</span></a>&nbsp;<a href=3D"http://www.arkko.com/tools/lifecycle/=
draft-mjsraman-panet-ospf-power-topo-timing.html" target=3D"_blank"><span s=
tyle=3D"color:#440088">(timeline)</span></a>&nbsp;Intra-Area
 within an AS<o:p></o:p></span></p>
<div>
<p class=3D"MsoNormal" style=3D"background:white"><span style=3D"font-size:=
10.0pt;font-family:&quot;Arial&quot;,&quot;sans-serif&quot;;color:#222222">=
We understand it is a lot of matter to go through. We would much appreciate=
 if some of you could review the inter-AS proposals while
 others take up multicast and Intra-AS unicast and multicast.<o:p></o:p></s=
pan></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"background:white"><span style=3D"font-size:=
10.0pt;font-family:&quot;Arial&quot;,&quot;sans-serif&quot;;color:#222222">=
<o:p>&nbsp;</o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"background:white"><span style=3D"font-size:=
10.0pt;font-family:&quot;Arial&quot;,&quot;sans-serif&quot;;color:#222222">=
Thanks again for your time on this matter.<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"background:white"><span style=3D"font-size:=
10.0pt;font-family:&quot;Arial&quot;,&quot;sans-serif&quot;;color:#222222">=
<o:p>&nbsp;</o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"background:white"><span style=3D"font-size:=
10.0pt;font-family:&quot;Arial&quot;,&quot;sans-serif&quot;;color:#222222">=
thanks and regards,<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"background:white"><span style=3D"font-size:=
10.0pt;font-family:&quot;Arial&quot;,&quot;sans-serif&quot;;color:#222222">=
balaji venkat<o:p></o:p></span></p>
</div>
</div>
</div>
</div>
</body>
</html>

--_000_9904FB1B0159DA42B0B887B7FA8119CA082E55AZFFEXMB04globala_--

From balajivenkat299@gmail.com  Wed Feb  6 03:13:13 2013
Return-Path: <balajivenkat299@gmail.com>
X-Original-To: irtf-discuss@ietfa.amsl.com
Delivered-To: irtf-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 57DD021F8809 for <irtf-discuss@ietfa.amsl.com>; Wed,  6 Feb 2013 03:13:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.865
X-Spam-Level: 
X-Spam-Status: No, score=-3.865 tagged_above=-999 required=5 tests=[AWL=-1.066, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1, SARE_SUB_RAND_LETTRS4=0.799]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zidd2tjydF4Z for <irtf-discuss@ietfa.amsl.com>; Wed,  6 Feb 2013 03:13:08 -0800 (PST)
Received: from mail-qa0-f50.google.com (mail-qa0-f50.google.com [209.85.216.50]) by ietfa.amsl.com (Postfix) with ESMTP id 4FA8B21F8808 for <irtf-discuss@irtf.org>; Wed,  6 Feb 2013 03:13:08 -0800 (PST)
Received: by mail-qa0-f50.google.com with SMTP id dx4so594005qab.9 for <irtf-discuss@irtf.org>; Wed, 06 Feb 2013 03:13:07 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=A202XbfR+I4MvliLf4IqoNyA0pFz/npHBMw9qb7hF1w=; b=MVyGOyKemk42ozCZzwQp2naHXk+crcAnLobPzBBn15ZFpXYrXSBgM2OzugTY/ADB+Q 4uf/pjzdX0YJ0cvqqKdM5Qvja1xIVDqNA5Xzmeu7FyLGDqJl+tU5PVW8Qarbh8/X9as2 m6RI3V8FNMLWMkrqREqaSGuxlGFkxtpDQw7B/IBTxHENLmS6gVVABzX0ijLxJKbPFk14 jn7cZlabf7spPePxvX6bunB3KkO+6J0fLWv2F2JmxzhCiKs7Rpr66PmGbPj+fPH+DIR8 7axnW3Wmg2DKGauRCBU2MalNdjpBZel+WC56BIUpb9NVZeNk7A7wAa2fg3eFdB3gFcBM dJLA==
MIME-Version: 1.0
X-Received: by 10.224.210.135 with SMTP id gk7mr20978342qab.57.1360149187546;  Wed, 06 Feb 2013 03:13:07 -0800 (PST)
Received: by 10.49.118.232 with HTTP; Wed, 6 Feb 2013 03:13:07 -0800 (PST)
In-Reply-To: <9904FB1B0159DA42B0B887B7FA8119CA082E38@AZ-FFEXMB04.global.avaya.com>
References: <CAHF4apMOpXohhWpYXB8X74yG4fBhcjVW0c=vNW4qXudJ7H92rA@mail.gmail.com> <9904FB1B0159DA42B0B887B7FA8119CA082E38@AZ-FFEXMB04.global.avaya.com>
Date: Wed, 6 Feb 2013 16:43:07 +0530
Message-ID: <CAHF4apN_94fp0VVrspjXFDTbfkusHY7e7usaNNgQ92Spaz_fgw@mail.gmail.com>
From: Balaji venkat Venkataswami <balajivenkat299@gmail.com>
To: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
Content-Type: multipart/alternative; boundary=20cf300facd32a4f4204d50c69ac
Cc: "irtf-discuss@irtf.org" <irtf-discuss@irtf.org>, "eerg@listserv.netlab.nec.de" <eerg@listserv.netlab.nec.de>, Susan Hares <susan.hares@huawei.com>, Lars Eggert <lars.eggert@nokia.com>
Subject: Re: [irtf-discuss] Request for a side-bar meeting in the IETF Orlando on Power-Aware Networking drafts
X-BeenThere: irtf-discuss@irtf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IRTF general and new-work discussion list <irtf-discuss.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/options/irtf-discuss>, <mailto:irtf-discuss-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/irtf-discuss>
List-Post: <mailto:irtf-discuss@irtf.org>
List-Help: <mailto:irtf-discuss-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/irtf-discuss>, <mailto:irtf-discuss-request@irtf.org?subject=subscribe>
X-List-Received-Date: Wed, 06 Feb 2013 11:13:13 -0000

--20cf300facd32a4f4204d50c69ac
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

Hi Dan,

It could be definitely part of EERG. That is our opinion.

thanks and regards,
balaji venkat

On Wed, Feb 6, 2013 at 4:15 PM, Romascanu, Dan (Dan) <dromasca@avaya.com>wr=
ote:

>  Hi Balaji,****
>
> ** **
>
> Is the scope of the work that you propose different of EERG,  could it be
> part of EERG, or an extension? ****
>
> ** **
>
> Thanks and Regards,****
>
> ** **
>
> Dan****
>
> ** **
>
> ** **
>
> ** **
>
> *From:* irtf-discuss-bounces@irtf.org [mailto:
> irtf-discuss-bounces@irtf.org] *On Behalf Of *Balaji venkat Venkataswami
> *Sent:* Wednesday, February 06, 2013 8:58 AM
> *To:* irtf-discuss@irtf.org; Lars Eggert; Susan Hares
> *Subject:* [irtf-discuss] Request for a side-bar meeting in the IETF
> Orlando on Power-Aware Networking drafts****
>
> ** **
>
> Dear Lars, all,****
>
> ** **
>
> We would like a side-bar meeting (in an adjacent room) to discuss the
> following Power-Aware-Networking proposals.****
>
> A detailed outline of the drafts submitted have been detailed below. We
> would like a 20 minute slot with 10 minutes for Q&A if possible.****
>
> We would however concur with whatever time you give us on this matter.***=
*
>
> We are a group of research and industry individuals tied together with a
> common goal towards reducing the energy consumption in the core and edge
> networks.****
>
> We present a metric-based hierarchical approach to reduce power
> consumption in core and edge networks. The proposal considers both unicas=
t
> and the multicast cases. For unicast, the metric considered is *consumed-=
power
> to available-bandwidth* and for multicast the metric is *consumed-power
> to available-replication-capacity.*****
>
>  With unicast, the metric is used to determine a low-power path between
> sources and destinations. With multicast, the metric serves the twin
> purpose of finding low-power multicast paths as well as multicast
> replication points.  We evolve multiple techniques at various hierarchica=
l
> levels. One at the Inter-AS level, Inter-Area level within the AS and
> intra-Area within an AS. Additionally, the proposed method can also be us=
ed
> to determine disjoint or redundant paths for load balancing or fault
> tolerance. Additionally since TCAMs are one of the biggest power guzzlers
> in all the components on a router/switch, we have presented a solution fo=
r
> intra-AS purposes to use the TCAM according to the traffic matrix passing
> through the system and shut down those TCAM banks that are unused. With
> this in mind, we have also advocated taking into account a TCAM-POWER-Rat=
io
> in order to compute the paths from source to destination based on this
> metric. Once low-power paths, in either the unicast or the multicast case=
s,
> are identified then currently available traffic engineering techniques
> could be used to route the data packets. In the case of inter-AS BGP path
> selection is also modified to arrive at paths which are low-power paths.*=
*
> **
>
>  Our main objective is as follows...****
>
> We now outline four important aspects that any approach for power
> reduction should be capable of addressing.****
>
>  *Should cater for both unicast and multicast scenarios*****
>
> Multicast provides an important scenario for the Internet. Today, most
> proposals consider mainly low-power path routing with unicast traffic.
> Multicast traffic has received a lot of attention in wireless networks, b=
ut
> not in the wired domain. Any new proposal should be able to address both
> the unicast and the multicast traffic scenarios. Having different methods
> for these two scenarios might lead to unnecessary processing burden in th=
e
> routers, which might hinder its scalability.        ****
>
>  *Should not rely on just switching off unused links*****
>
> Most approaches to optimize energy pursue the following approach: measure=
,
> monitor and respond to the system energy usage by switching off unused or
> under-utilized links. Such an approach could be effective for reducing
> power locally. The effect on the network is not clearly understood.
> Further, the power usage involved in turning on and rebooting/reconfiguri=
ng
> the device is often not explicitly considered. We note that Service Level
> Agreement (SLA) requirements may not even permit the links to be switched
> off. Also services provided by ISPs like Virtual Private Networks (VPNs)
> can be affected by such re-routing decisions.****
>
>  *Should follow an hierarchical and distributed approach*****
>
> For scalability, it is important that the algorithms proposed for inter-A=
S
> should also be applicable to intra-AS situations. Networks do not work in
> isolation, so any proposal should be both distributed and hierarchical. T=
he
> algorithms should be applicable at every level of the hierarchy.  ****
>
>  *Should  provide incentives for ISP for adoption*****
>
> The engineering proposals should be aligned with commercial incentives fo=
r
> rapid and widespread adoption. Today, the device manufacturers and the IS=
Ps
> operate independently of each other, and there is no incentive for
> manufacturers to work towards low-power and high bandwidth devices. An
> ISP=92s revenue model is based on the consumed bandwidth, which in turn l=
ead
> naturally to more power consumption. If the proposed method chooses route=
rs
> that consume low-power and increase the data flow through them, then this
> indirectly provides encouragement for ISPs to purchase low-power and high
> bandwidth devices.                ****
>
>  ****
>
> We now present our metric-based proposals in the below mentioned drafts
> which addresses the aforementioned design aspects.****
>
> We would like the routing community to provide feedback on these drafts.
> We also intend to present this work in an abridged format in the upcoming
> IETF.****
>
>  The drafts are as follows....****
>
> ** **
>
> ** **
>
> **=B7         **mjsraman-panet-bgp-power-path<http://tools.ietf.org/html/=
draft-mjsraman-panet-bgp-power-path>
>  (timeline)<http://www.arkko.com/tools/lifecycle/draft-mjsraman-panet-bgp=
-power-path-timing.html>
>  Inter-AS-Proposal****
>
> **=B7         **mjsraman-panet-ecmp-redirect-power-repl-cap<http://tools.=
ietf.org/html/draft-mjsraman-panet-ecmp-redirect-power-repl-cap>
>  (timeline)<http://www.arkko.com/tools/lifecycle/draft-mjsraman-panet-ecm=
p-redirect-power-repl-cap-timing.html>
>  Multicast****
>
> **=B7         **mjsraman-panet-inter-as-power-source<http://tools.ietf.or=
g/html/draft-mjsraman-panet-inter-as-power-source>
>  (timeline)<http://www.arkko.com/tools/lifecycle/draft-mjsraman-panet-int=
er-as-power-source-timing.html> Inter-AS
> Proposal****
>
> **=B7         **mjsraman-panet-inter-as-psp<http://tools.ietf.org/html/dr=
aft-mjsraman-panet-inter-as-psp>
>  (timeline)<http://www.arkko.com/tools/lifecycle/draft-mjsraman-panet-int=
er-as-psp-timing.html> Inter-AS
> Proposal****
>
> **=B7         **mjsraman-panet-inter-as-psp-protect<http://tools.ietf.org=
/html/draft-mjsraman-panet-inter-as-psp-protect>
>  (timeline)<http://www.arkko.com/tools/lifecycle/draft-mjsraman-panet-int=
er-as-psp-protect-timing.html> Inter-AS
> Proposal****
>
> **=B7         **mjsraman-panet-pce-power-mcast-replic<http://tools.ietf.o=
rg/html/draft-mjsraman-panet-pce-power-mcast-replic>
>  (timeline)<http://www.arkko.com/tools/lifecycle/draft-mjsraman-panet-pce=
-power-mcast-replic-timing.html>
>  Multicast****
>
> **=B7         **mjsraman-panet-pim-power<http://tools.ietf.org/html/draft=
-mjsraman-panet-pim-power>
>  (timeline)<http://www.arkko.com/tools/lifecycle/draft-mjsraman-panet-pim=
-power-timing.html>
>  Multicast****
>
> **=B7         **mjsraman-panet-tcam-power-efficiency<http://tools.ietf.or=
g/html/draft-mjsraman-panet-tcam-power-efficiency>
>  (timeline)<http://www.arkko.com/tools/lifecycle/draft-mjsraman-panet-tca=
m-power-efficiency-timing.html> TCAM
> related****
>
> **=B7         **mjsraman-panet-tcam-power-ratio<http://tools.ietf.org/htm=
l/draft-mjsraman-panet-tcam-power-ratio>
>  (timeline<http://www.arkko.com/tools/lifecycle/draft-mjsraman-panet-tcam=
-power-ratio-timing.html>)
> TCAM related****
>
> **=B7         **mjsraman-pce-power-replic<http://tools.ietf.org/html/draf=
t-mjsraman-pce-power-replic>
>  (timeline)<http://www.arkko.com/tools/lifecycle/draft-mjsraman-pce-power=
-replic-timing.html>
>  Multicast****
>
> **=B7         **mjsraman-panet-intra-as-psp-te-leak<http://tools.ietf.org=
/html/draft-mjsraman-panet-intra-as-psp-te-leak>
>  (timeline)<http://www.arkko.com/tools/lifecycle/draft-mjsraman-panet-int=
ra-as-psp-te-leak-timing.html> Inter-Area
> within an AS****
>
> **=B7         **mjsraman-panet-ospf-power-topo<http://tools.ietf.org/html=
/draft-mjsraman-panet-ospf-power-topo>
>  (timeline)<http://www.arkko.com/tools/lifecycle/draft-mjsraman-panet-osp=
f-power-topo-timing.html> Intra-Area
> within an AS****
>
> We understand it is a lot of matter to go through. We would much
> appreciate if some of you could review the inter-AS proposals while other=
s
> take up multicast and Intra-AS unicast and multicast.****
>
> ** **
>
> Thanks again for your time on this matter.****
>
> ** **
>
> thanks and regards,****
>
> balaji venkat****
>

--20cf300facd32a4f4204d50c69ac
Content-Type: text/html; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

Hi Dan,<div><br></div><div>It could be definitely part of EERG. That is our=
 opinion.</div><div><br></div><div>thanks and regards,</div><div>balaji ven=
kat<br><br><div class=3D"gmail_quote">On Wed, Feb 6, 2013 at 4:15 PM, Romas=
canu, Dan (Dan) <span dir=3D"ltr">&lt;<a href=3D"mailto:dromasca@avaya.com"=
 target=3D"_blank">dromasca@avaya.com</a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">





<div lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">Hi Balaji,<u></u><u></u><=
/span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d"><u></u>=A0<u></u></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">Is the scope of the work =
that you propose different of EERG, =A0could it be part of EERG, or an exte=
nsion?
<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d"><u></u>=A0<u></u></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">Thanks and Regards,<u></u=
><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d"><u></u>=A0<u></u></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">Dan<u></u><u></u></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d"><u></u>=A0<u></u></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d"><u></u>=A0<u></u></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d"><u></u>=A0<u></u></span><=
/p>
<div style=3D"border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in =
4.0pt">
<div>
<div style=3D"border:none;border-top:solid #b5c4df 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span style=3D"font-s=
ize:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> <a href=
=3D"mailto:irtf-discuss-bounces@irtf.org" target=3D"_blank">irtf-discuss-bo=
unces@irtf.org</a> [mailto:<a href=3D"mailto:irtf-discuss-bounces@irtf.org"=
 target=3D"_blank">irtf-discuss-bounces@irtf.org</a>]
<b>On Behalf Of </b>Balaji venkat Venkataswami<br>
<b>Sent:</b> Wednesday, February 06, 2013 8:58 AM<br>
<b>To:</b> <a href=3D"mailto:irtf-discuss@irtf.org" target=3D"_blank">irtf-=
discuss@irtf.org</a>; Lars Eggert; Susan Hares<br>
<b>Subject:</b> [irtf-discuss] Request for a side-bar meeting in the IETF O=
rlando on Power-Aware Networking drafts<u></u><u></u></span></p>
</div>
</div><div><div class=3D"h5">
<p class=3D"MsoNormal"><u></u>=A0<u></u></p>
<p class=3D"MsoNormal">Dear Lars, all,<u></u><u></u></p>
<div>
<p class=3D"MsoNormal"><u></u>=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">We would like a side-bar meeting (in an adjacent roo=
m) to discuss the following Power-Aware-Networking proposals.<u></u><u></u>=
</p>
</div>
<div>
<p class=3D"MsoNormal">A detailed outline of the drafts submitted have been=
 detailed below. We would like a 20 minute slot with 10 minutes for Q&amp;A=
 if possible.<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">We would however concur with whatever time you give =
us on this matter.<u></u><u></u></p>
</div>
<div>
<p style=3D"background:white"><span style=3D"font-size:10.0pt;font-family:&=
quot;Arial&quot;,&quot;sans-serif&quot;;color:#222222">We are a group of re=
search and industry individuals tied together with a common goal towards re=
ducing the energy consumption in the core and edge networks.<u></u><u></u><=
/span></p>

<p style=3D"background:white"><span style=3D"font-size:10.0pt;font-family:&=
quot;Arial&quot;,&quot;sans-serif&quot;;color:#222222">We present a metric-=
based hierarchical approach to reduce power consumption in core and edge ne=
tworks. The proposal considers both unicast and the multicast
 cases. For unicast, the metric considered is=A0<i>consumed-power to availa=
ble-bandwidth</i>=A0and for multicast the metric is=A0<i>consumed-power to =
available-replication-capacity.</i><u></u><u></u></span></p>
<p style=3D"background:white"><span style=3D"font-size:10.0pt;font-family:&=
quot;Arial&quot;,&quot;sans-serif&quot;;color:#222222">=A0With unicast, the=
 metric is=A0used to determine a low-power path between sources and destina=
tions.=A0With multicast, the=A0metric serves the twin purpose of
 finding low-power multicast paths as well as multicast replication points.=
=A0=A0We evolve multiple techniques at various hierarchical levels. One at =
the Inter-AS level, Inter-Area level within the AS and intra-Area within an=
 AS. Additionally, the proposed method
 can also be used to determine disjoint or redundant paths for load balanci=
ng or fault tolerance. Additionally since TCAMs are one of the biggest powe=
r guzzlers in all the components on a router/switch, we have presented a so=
lution for intra-AS purposes to
 use the TCAM according to the traffic matrix passing through the system an=
d shut down those TCAM banks that are unused. With this in mind, we have al=
so advocated taking into account a TCAM-POWER-Ratio in order to compute the=
 paths from source to destination
 based on this metric. Once low-power paths, in either the unicast or the m=
ulticast cases, are identified then currently available traffic engineering=
 techniques could be used to route the data packets. In the case of inter-A=
S BGP path selection is also modified
 to arrive at paths which are low-power paths.<u></u><u></u></span></p>
<p style=3D"background:white"><span style=3D"font-size:10.0pt;font-family:&=
quot;Arial&quot;,&quot;sans-serif&quot;;color:#222222">=A0Our main objectiv=
e is as follows...<u></u><u></u></span></p>
<p style=3D"background:white"><span style=3D"font-size:10.0pt;font-family:&=
quot;Arial&quot;,&quot;sans-serif&quot;;color:#222222">We now outline four =
important aspects that any approach for power reduction should be capable o=
f addressing.<u></u><u></u></span></p>

<p style=3D"background:white"><span style=3D"font-size:10.0pt;font-family:&=
quot;Arial&quot;,&quot;sans-serif&quot;;color:#222222">=A0<i>Should cater f=
or both unicast and multicast scenarios</i><u></u><u></u></span></p>
<p style=3D"background:white"><span style=3D"font-size:10.0pt;font-family:&=
quot;Arial&quot;,&quot;sans-serif&quot;;color:#222222">Multicast provides a=
n important scenario for the Internet. Today, most proposals consider mainl=
y low-power path routing with unicast traffic. Multicast
 traffic has received a lot of attention in wireless networks, but not in t=
he wired domain. Any new proposal should be able to address both the unicas=
t and the multicast traffic scenarios. Having different methods for these t=
wo scenarios might lead to unnecessary
 processing burden in the routers, which might hinder its scalability.=A0=
=A0=A0=A0=A0=A0=A0=A0<u></u><u></u></span></p>
<p style=3D"background:white"><span style=3D"font-size:10.0pt;font-family:&=
quot;Arial&quot;,&quot;sans-serif&quot;;color:#222222">=A0<i>Should not rel=
y on just switching off unused links</i><u></u><u></u></span></p>
<p style=3D"background:white"><span style=3D"font-size:10.0pt;font-family:&=
quot;Arial&quot;,&quot;sans-serif&quot;;color:#222222">Most approaches to o=
ptimize energy pursue the following approach: measure, monitor and respond =
to the system energy usage by switching off unused or under-utilized
 links. Such an approach could be effective for reducing power locally. The=
 effect on the network is not clearly understood. Further, the power usage =
involved in turning on and rebooting/reconfiguring the device is often not =
explicitly considered. We note that
 Service Level Agreement (SLA) requirements may not even permit the links t=
o be switched off. Also services provided by ISPs like Virtual Private Netw=
orks (VPNs) can be affected by such re-routing decisions.<u></u><u></u></sp=
an></p>

<p style=3D"background:white"><span style=3D"font-size:10.0pt;font-family:&=
quot;Arial&quot;,&quot;sans-serif&quot;;color:#222222">=A0<i>Should follow =
an hierarchical and distributed approach</i><u></u><u></u></span></p>
<p style=3D"background:white"><span style=3D"font-size:10.0pt;font-family:&=
quot;Arial&quot;,&quot;sans-serif&quot;;color:#222222">For scalability, it =
is important that the algorithms proposed for inter-AS should also be appli=
cable to intra-AS situations. Networks do not work in isolation,
 so any proposal should be both distributed and hierarchical. The algorithm=
s should be applicable at every level of the hierarchy.=A0=A0<u></u><u></u>=
</span></p>
<p style=3D"background:white"><span style=3D"font-size:10.0pt;font-family:&=
quot;Arial&quot;,&quot;sans-serif&quot;;color:#222222">=A0<i>Should=A0=A0pr=
ovide incentives for ISP for adoption</i><u></u><u></u></span></p>
<p style=3D"background:white"><span style=3D"font-size:10.0pt;font-family:&=
quot;Arial&quot;,&quot;sans-serif&quot;;color:#222222">The engineering prop=
osals should be aligned with commercial incentives for rapid and widespread=
 adoption. Today, the device manufacturers and the ISPs
 operate independently of each other, and there is no incentive for manufac=
turers to work towards low-power and high bandwidth devices. An ISP=92s rev=
enue model is based on the consumed bandwidth, which in turn lead naturally=
 to more power consumption. If the
 proposed method chooses routers that consume low-power and increase the da=
ta flow through them, then this indirectly provides encouragement for ISPs =
to purchase low-power and high bandwidth devices.=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0<u></u><u></u></span></p>

<p style=3D"background:white"><span style=3D"font-size:10.0pt;font-family:&=
quot;Arial&quot;,&quot;sans-serif&quot;;color:#222222">=A0<u></u><u></u></s=
pan></p>
<p style=3D"background:white"><span style=3D"font-size:10.0pt;font-family:&=
quot;Arial&quot;,&quot;sans-serif&quot;;color:#222222">We now present our m=
etric-based proposals in the below mentioned drafts which addresses the afo=
rementioned design aspects.<u></u><u></u></span></p>

<p style=3D"background:white"><span style=3D"font-size:10.0pt;font-family:&=
quot;Arial&quot;,&quot;sans-serif&quot;;color:#222222">We would like the ro=
uting community to provide feedback on these drafts. We also intend to pres=
ent this work in an abridged format in the upcoming IETF.<u></u><u></u></sp=
an></p>

<p class=3D"MsoNormal" style=3D"background:white">
<span style=3D"font-size:11.0pt;font-family:&quot;Arial&quot;,&quot;sans-se=
rif&quot;;color:#222222">=A0The drafts are as follows....</span><span style=
=3D"font-size:10.0pt;font-family:&quot;Arial&quot;,&quot;sans-serif&quot;;c=
olor:#222222"><u></u><u></u></span></p>

<p class=3D"MsoNormal" style=3D"background:white">
<span style=3D"font-size:10.0pt;font-family:&quot;Arial&quot;,&quot;sans-se=
rif&quot;;color:#222222"><u></u>=A0<u></u></span></p>
<p class=3D"MsoNormal" style=3D"background:white">
<span style=3D"font-size:10.0pt;font-family:&quot;Arial&quot;,&quot;sans-se=
rif&quot;;color:#222222"><u></u>=A0<u></u></span></p>
<p class=3D"MsoNormal" style=3D"margin-right:12.0pt;margin-bottom:3.0pt;mar=
gin-left:23.25pt;background:white">
<u></u><span style=3D"font-size:10.0pt;font-family:Symbol;color:#222222"><s=
pan>=B7<span style=3D"font:7.0pt &quot;Times New Roman&quot;">=A0=A0=A0=A0=
=A0=A0=A0=A0
</span></span></span><u></u><span dir=3D"LTR"></span><span style=3D"font-si=
ze:10.0pt;font-family:&quot;Arial&quot;,&quot;sans-serif&quot;;color:#22222=
2"><a href=3D"http://tools.ietf.org/html/draft-mjsraman-panet-bgp-power-pat=
h" target=3D"_blank"><span style=3D"color:#440088">mjsraman-panet-bgp-power=
-path</span></a>=A0<a href=3D"http://www.arkko.com/tools/lifecycle/draft-mj=
sraman-panet-bgp-power-path-timing.html" target=3D"_blank"><span style=3D"c=
olor:#440088">(timeline)</span></a>=A0Inter-AS-Proposal<u></u><u></u></span=
></p>

<p class=3D"MsoNormal" style=3D"margin-right:12.0pt;margin-bottom:3.0pt;mar=
gin-left:23.25pt;background:white">
<u></u><span style=3D"font-size:10.0pt;font-family:Symbol;color:#222222"><s=
pan>=B7<span style=3D"font:7.0pt &quot;Times New Roman&quot;">=A0=A0=A0=A0=
=A0=A0=A0=A0
</span></span></span><u></u><span dir=3D"LTR"></span><span style=3D"font-si=
ze:10.0pt;font-family:&quot;Arial&quot;,&quot;sans-serif&quot;;color:#22222=
2"><a href=3D"http://tools.ietf.org/html/draft-mjsraman-panet-ecmp-redirect=
-power-repl-cap" target=3D"_blank"><span style=3D"color:#440088">mjsraman-p=
anet-ecmp-redirect-power-repl-cap</span></a>=A0<a href=3D"http://www.arkko.=
com/tools/lifecycle/draft-mjsraman-panet-ecmp-redirect-power-repl-cap-timin=
g.html" target=3D"_blank"><span style=3D"color:#440088">(timeline)</span></=
a>=A0Multicast<u></u><u></u></span></p>

<p class=3D"MsoNormal" style=3D"margin-right:12.0pt;margin-bottom:3.0pt;mar=
gin-left:23.25pt;background:white">
<u></u><span style=3D"font-size:10.0pt;font-family:Symbol;color:#222222"><s=
pan>=B7<span style=3D"font:7.0pt &quot;Times New Roman&quot;">=A0=A0=A0=A0=
=A0=A0=A0=A0
</span></span></span><u></u><span dir=3D"LTR"></span><span style=3D"font-si=
ze:10.0pt;font-family:&quot;Arial&quot;,&quot;sans-serif&quot;;color:#22222=
2"><a href=3D"http://tools.ietf.org/html/draft-mjsraman-panet-inter-as-powe=
r-source" target=3D"_blank"><span style=3D"color:#440088">mjsraman-panet-in=
ter-as-power-source</span></a>=A0<a href=3D"http://www.arkko.com/tools/life=
cycle/draft-mjsraman-panet-inter-as-power-source-timing.html" target=3D"_bl=
ank"><span style=3D"color:#440088">(timeline)</span></a>=A0Inter-AS
 Proposal<u></u><u></u></span></p>
<p class=3D"MsoNormal" style=3D"margin-right:12.0pt;margin-bottom:3.0pt;mar=
gin-left:23.25pt;background:white">
<u></u><span style=3D"font-size:10.0pt;font-family:Symbol;color:#222222"><s=
pan>=B7<span style=3D"font:7.0pt &quot;Times New Roman&quot;">=A0=A0=A0=A0=
=A0=A0=A0=A0
</span></span></span><u></u><span dir=3D"LTR"></span><span style=3D"font-si=
ze:10.0pt;font-family:&quot;Arial&quot;,&quot;sans-serif&quot;;color:#22222=
2"><a href=3D"http://tools.ietf.org/html/draft-mjsraman-panet-inter-as-psp"=
 target=3D"_blank"><span style=3D"color:#440088">mjsraman-panet-inter-as-ps=
p</span></a>=A0<a href=3D"http://www.arkko.com/tools/lifecycle/draft-mjsram=
an-panet-inter-as-psp-timing.html" target=3D"_blank"><span style=3D"color:#=
440088">(timeline)</span></a>=A0Inter-AS
 Proposal<u></u><u></u></span></p>
<p class=3D"MsoNormal" style=3D"margin-right:12.0pt;margin-bottom:3.0pt;mar=
gin-left:23.25pt;background:white">
<u></u><span style=3D"font-size:10.0pt;font-family:Symbol;color:#222222"><s=
pan>=B7<span style=3D"font:7.0pt &quot;Times New Roman&quot;">=A0=A0=A0=A0=
=A0=A0=A0=A0
</span></span></span><u></u><span dir=3D"LTR"></span><span style=3D"font-si=
ze:10.0pt;font-family:&quot;Arial&quot;,&quot;sans-serif&quot;;color:#22222=
2"><a href=3D"http://tools.ietf.org/html/draft-mjsraman-panet-inter-as-psp-=
protect" target=3D"_blank"><span style=3D"color:#440088">mjsraman-panet-int=
er-as-psp-protect</span></a>=A0<a href=3D"http://www.arkko.com/tools/lifecy=
cle/draft-mjsraman-panet-inter-as-psp-protect-timing.html" target=3D"_blank=
"><span style=3D"color:#440088">(timeline)</span></a>=A0Inter-AS
 Proposal<u></u><u></u></span></p>
<p class=3D"MsoNormal" style=3D"margin-right:12.0pt;margin-bottom:3.0pt;mar=
gin-left:23.25pt;background:white">
<u></u><span style=3D"font-size:10.0pt;font-family:Symbol;color:#222222"><s=
pan>=B7<span style=3D"font:7.0pt &quot;Times New Roman&quot;">=A0=A0=A0=A0=
=A0=A0=A0=A0
</span></span></span><u></u><span dir=3D"LTR"></span><span style=3D"font-si=
ze:10.0pt;font-family:&quot;Arial&quot;,&quot;sans-serif&quot;;color:#22222=
2"><a href=3D"http://tools.ietf.org/html/draft-mjsraman-panet-pce-power-mca=
st-replic" target=3D"_blank"><span style=3D"color:#440088">mjsraman-panet-p=
ce-power-mcast-replic</span></a>=A0<a href=3D"http://www.arkko.com/tools/li=
fecycle/draft-mjsraman-panet-pce-power-mcast-replic-timing.html" target=3D"=
_blank"><span style=3D"color:#440088">(timeline)</span></a>=A0Multicast<u><=
/u><u></u></span></p>

<p class=3D"MsoNormal" style=3D"margin-right:12.0pt;margin-bottom:3.0pt;mar=
gin-left:23.25pt;background:white">
<u></u><span style=3D"font-size:10.0pt;font-family:Symbol;color:#222222"><s=
pan>=B7<span style=3D"font:7.0pt &quot;Times New Roman&quot;">=A0=A0=A0=A0=
=A0=A0=A0=A0
</span></span></span><u></u><span dir=3D"LTR"></span><span style=3D"font-si=
ze:10.0pt;font-family:&quot;Arial&quot;,&quot;sans-serif&quot;;color:#22222=
2"><a href=3D"http://tools.ietf.org/html/draft-mjsraman-panet-pim-power" ta=
rget=3D"_blank"><span style=3D"color:#440088">mjsraman-panet-pim-power</spa=
n></a>=A0<a href=3D"http://www.arkko.com/tools/lifecycle/draft-mjsraman-pan=
et-pim-power-timing.html" target=3D"_blank"><span style=3D"color:#440088">(=
timeline)</span></a>=A0Multicast<u></u><u></u></span></p>

<p class=3D"MsoNormal" style=3D"margin-right:12.0pt;margin-bottom:3.0pt;mar=
gin-left:23.25pt;background:white">
<u></u><span style=3D"font-size:10.0pt;font-family:Symbol;color:#222222"><s=
pan>=B7<span style=3D"font:7.0pt &quot;Times New Roman&quot;">=A0=A0=A0=A0=
=A0=A0=A0=A0
</span></span></span><u></u><span dir=3D"LTR"></span><span style=3D"font-si=
ze:10.0pt;font-family:&quot;Arial&quot;,&quot;sans-serif&quot;;color:#22222=
2"><a href=3D"http://tools.ietf.org/html/draft-mjsraman-panet-tcam-power-ef=
ficiency" target=3D"_blank"><span style=3D"color:#440088">mjsraman-panet-tc=
am-power-efficiency</span></a>=A0<a href=3D"http://www.arkko.com/tools/life=
cycle/draft-mjsraman-panet-tcam-power-efficiency-timing.html" target=3D"_bl=
ank"><span style=3D"color:#440088">(timeline)</span></a>=A0TCAM
 related<u></u><u></u></span></p>
<p class=3D"MsoNormal" style=3D"margin-right:12.0pt;margin-bottom:3.0pt;mar=
gin-left:23.25pt;background:white">
<u></u><span style=3D"font-size:10.0pt;font-family:Symbol;color:#222222"><s=
pan>=B7<span style=3D"font:7.0pt &quot;Times New Roman&quot;">=A0=A0=A0=A0=
=A0=A0=A0=A0
</span></span></span><u></u><span dir=3D"LTR"></span><span style=3D"font-si=
ze:10.0pt;font-family:&quot;Arial&quot;,&quot;sans-serif&quot;;color:#22222=
2"><a href=3D"http://tools.ietf.org/html/draft-mjsraman-panet-tcam-power-ra=
tio" target=3D"_blank"><span style=3D"color:#440088">mjsraman-panet-tcam-po=
wer-ratio</span></a>=A0<a href=3D"http://www.arkko.com/tools/lifecycle/draf=
t-mjsraman-panet-tcam-power-ratio-timing.html" target=3D"_blank"><span styl=
e=3D"color:#440088">(timeline</span></a>)
 TCAM related<u></u><u></u></span></p>
<p class=3D"MsoNormal" style=3D"margin-right:12.0pt;margin-bottom:3.0pt;mar=
gin-left:23.25pt;background:white">
<u></u><span style=3D"font-size:10.0pt;font-family:Symbol;color:#222222"><s=
pan>=B7<span style=3D"font:7.0pt &quot;Times New Roman&quot;">=A0=A0=A0=A0=
=A0=A0=A0=A0
</span></span></span><u></u><span dir=3D"LTR"></span><span style=3D"font-si=
ze:10.0pt;font-family:&quot;Arial&quot;,&quot;sans-serif&quot;;color:#22222=
2"><a href=3D"http://tools.ietf.org/html/draft-mjsraman-pce-power-replic" t=
arget=3D"_blank"><span style=3D"color:#440088">mjsraman-pce-power-replic</s=
pan></a>=A0<a href=3D"http://www.arkko.com/tools/lifecycle/draft-mjsraman-p=
ce-power-replic-timing.html" target=3D"_blank"><span style=3D"color:#440088=
">(timeline)</span></a>=A0Multicast<u></u><u></u></span></p>

<p class=3D"MsoNormal" style=3D"margin-right:12.0pt;margin-bottom:3.0pt;mar=
gin-left:23.25pt;background:white">
<u></u><span style=3D"font-size:10.0pt;font-family:Symbol;color:#222222"><s=
pan>=B7<span style=3D"font:7.0pt &quot;Times New Roman&quot;">=A0=A0=A0=A0=
=A0=A0=A0=A0
</span></span></span><u></u><span dir=3D"LTR"></span><span style=3D"font-si=
ze:10.0pt;font-family:&quot;Arial&quot;,&quot;sans-serif&quot;;color:#22222=
2"><a href=3D"http://tools.ietf.org/html/draft-mjsraman-panet-intra-as-psp-=
te-leak" target=3D"_blank"><span style=3D"color:#440088">mjsraman-panet-int=
ra-as-psp-te-leak</span></a>=A0<a href=3D"http://www.arkko.com/tools/lifecy=
cle/draft-mjsraman-panet-intra-as-psp-te-leak-timing.html" target=3D"_blank=
"><span style=3D"color:#440088">(timeline)</span></a>=A0Inter-Area
 within an AS<u></u><u></u></span></p>
<p class=3D"MsoNormal" style=3D"margin-right:12.0pt;margin-bottom:3.0pt;mar=
gin-left:23.25pt;background:white">
<u></u><span style=3D"font-size:10.0pt;font-family:Symbol;color:#222222"><s=
pan>=B7<span style=3D"font:7.0pt &quot;Times New Roman&quot;">=A0=A0=A0=A0=
=A0=A0=A0=A0
</span></span></span><u></u><span dir=3D"LTR"></span><span style=3D"font-si=
ze:10.0pt;font-family:&quot;Arial&quot;,&quot;sans-serif&quot;;color:#22222=
2"><a href=3D"http://tools.ietf.org/html/draft-mjsraman-panet-ospf-power-to=
po" target=3D"_blank"><span style=3D"color:#440088">mjsraman-panet-ospf-pow=
er-topo</span></a>=A0<a href=3D"http://www.arkko.com/tools/lifecycle/draft-=
mjsraman-panet-ospf-power-topo-timing.html" target=3D"_blank"><span style=
=3D"color:#440088">(timeline)</span></a>=A0Intra-Area
 within an AS<u></u><u></u></span></p>
<div>
<p class=3D"MsoNormal" style=3D"background:white"><span style=3D"font-size:=
10.0pt;font-family:&quot;Arial&quot;,&quot;sans-serif&quot;;color:#222222">=
We understand it is a lot of matter to go through. We would much appreciate=
 if some of you could review the inter-AS proposals while
 others take up multicast and Intra-AS unicast and multicast.<u></u><u></u>=
</span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"background:white"><span style=3D"font-size:=
10.0pt;font-family:&quot;Arial&quot;,&quot;sans-serif&quot;;color:#222222">=
<u></u>=A0<u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"background:white"><span style=3D"font-size:=
10.0pt;font-family:&quot;Arial&quot;,&quot;sans-serif&quot;;color:#222222">=
Thanks again for your time on this matter.<u></u><u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"background:white"><span style=3D"font-size:=
10.0pt;font-family:&quot;Arial&quot;,&quot;sans-serif&quot;;color:#222222">=
<u></u>=A0<u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"background:white"><span style=3D"font-size:=
10.0pt;font-family:&quot;Arial&quot;,&quot;sans-serif&quot;;color:#222222">=
thanks and regards,<u></u><u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"background:white"><span style=3D"font-size:=
10.0pt;font-family:&quot;Arial&quot;,&quot;sans-serif&quot;;color:#222222">=
balaji venkat<u></u><u></u></span></p>
</div>
</div>
</div></div></div>
</div>
</div>

</blockquote></div><br></div>

--20cf300facd32a4f4204d50c69ac--

From balajivenkat299@gmail.com  Wed Feb  6 03:14:45 2013
Return-Path: <balajivenkat299@gmail.com>
X-Original-To: irtf-discuss@ietfa.amsl.com
Delivered-To: irtf-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1E3CC21F8808 for <irtf-discuss@ietfa.amsl.com>; Wed,  6 Feb 2013 03:14:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.598
X-Spam-Level: 
X-Spam-Status: No, score=-3.598 tagged_above=-999 required=5 tests=[AWL=-0.799, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1, SARE_SUB_RAND_LETTRS4=0.799]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Fw4U0+Zw5y3v for <irtf-discuss@ietfa.amsl.com>; Wed,  6 Feb 2013 03:14:42 -0800 (PST)
Received: from mail-qc0-f172.google.com (mail-qc0-f172.google.com [209.85.216.172]) by ietfa.amsl.com (Postfix) with ESMTP id 1C07621F86D8 for <irtf-discuss@irtf.org>; Wed,  6 Feb 2013 03:14:37 -0800 (PST)
Received: by mail-qc0-f172.google.com with SMTP id b25so468102qca.31 for <irtf-discuss@irtf.org>; Wed, 06 Feb 2013 03:14:36 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=nf/Kbv+chzmZXYjpSXokqtDNDgGayuvf/Ts4kq2WIzA=; b=TYrImOdHLkq6I6HuPxV9IfNhbQRBnZc3HnSFAuF8qM6Qstp/a4oZMM5AyuFF6l0aCh HD+givsdU53LA4NjyRcpd4cIz7NQGKhDUqt/2PqmZj6fHeQMxknqg8EiTvznBWU95sdn O5niuJxCobuUuvnYminDZPIJg7DNVYXdqlaC9MgwQfM2QEf7s6DXnRyCeoQG3qlv7IXE Nj/I9bfemhwm3knpjV0S6Q+7KesoFx3dpZlXaAZXOMc2dliKegVCAZjE47F/ysMYzwFf crH2TnVC0NFVCB+En9imuQT4wnl2ku54j+RITe/Y5G3Yudvc53l3xtY1zmcz/oF0siWF gmyQ==
MIME-Version: 1.0
X-Received: by 10.49.127.238 with SMTP id nj14mr24986294qeb.9.1360149276082; Wed, 06 Feb 2013 03:14:36 -0800 (PST)
Received: by 10.49.118.232 with HTTP; Wed, 6 Feb 2013 03:14:36 -0800 (PST)
In-Reply-To: <CAHF4apN_94fp0VVrspjXFDTbfkusHY7e7usaNNgQ92Spaz_fgw@mail.gmail.com>
References: <CAHF4apMOpXohhWpYXB8X74yG4fBhcjVW0c=vNW4qXudJ7H92rA@mail.gmail.com> <9904FB1B0159DA42B0B887B7FA8119CA082E38@AZ-FFEXMB04.global.avaya.com> <CAHF4apN_94fp0VVrspjXFDTbfkusHY7e7usaNNgQ92Spaz_fgw@mail.gmail.com>
Date: Wed, 6 Feb 2013 16:44:36 +0530
Message-ID: <CAHF4apOQ-_b9x6kEt_7oTU0+t8NGtJZ7zzaSqHG6+_sgJ+0Y9A@mail.gmail.com>
From: Balaji venkat Venkataswami <balajivenkat299@gmail.com>
To: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
Content-Type: multipart/alternative; boundary=047d7b5da2a571438804d50c6e8c
Cc: "irtf-discuss@irtf.org" <irtf-discuss@irtf.org>, "eerg@listserv.netlab.nec.de" <eerg@listserv.netlab.nec.de>, Susan Hares <susan.hares@huawei.com>
Subject: Re: [irtf-discuss] Request for a side-bar meeting in the IETF Orlando on Power-Aware Networking drafts
X-BeenThere: irtf-discuss@irtf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IRTF general and new-work discussion list <irtf-discuss.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/options/irtf-discuss>, <mailto:irtf-discuss-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/irtf-discuss>
List-Post: <mailto:irtf-discuss@irtf.org>
List-Help: <mailto:irtf-discuss-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/irtf-discuss>, <mailto:irtf-discuss-request@irtf.org?subject=subscribe>
X-List-Received-Date: Wed, 06 Feb 2013 11:14:45 -0000

--047d7b5da2a571438804d50c6e8c
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

CCing the correct Lars Eggert email.

thanks and regards,
balaji venkat

On Wed, Feb 6, 2013 at 4:43 PM, Balaji venkat Venkataswami <
balajivenkat299@gmail.com> wrote:

> Hi Dan,
>
> It could be definitely part of EERG. That is our opinion.
>
> thanks and regards,
> balaji venkat
>
>
> On Wed, Feb 6, 2013 at 4:15 PM, Romascanu, Dan (Dan) <dromasca@avaya.com>=
wrote:
>
>>  Hi Balaji,****
>>
>> ** **
>>
>> Is the scope of the work that you propose different of EERG,  could it b=
e
>> part of EERG, or an extension? ****
>>
>> ** **
>>
>> Thanks and Regards,****
>>
>> ** **
>>
>> Dan****
>>
>> ** **
>>
>> ** **
>>
>> ** **
>>
>> *From:* irtf-discuss-bounces@irtf.org [mailto:
>> irtf-discuss-bounces@irtf.org] *On Behalf Of *Balaji venkat Venkataswami
>> *Sent:* Wednesday, February 06, 2013 8:58 AM
>> *To:* irtf-discuss@irtf.org; Lars Eggert; Susan Hares
>> *Subject:* [irtf-discuss] Request for a side-bar meeting in the IETF
>> Orlando on Power-Aware Networking drafts****
>>
>> ** **
>>
>> Dear Lars, all,****
>>
>> ** **
>>
>> We would like a side-bar meeting (in an adjacent room) to discuss the
>> following Power-Aware-Networking proposals.****
>>
>> A detailed outline of the drafts submitted have been detailed below. We
>> would like a 20 minute slot with 10 minutes for Q&A if possible.****
>>
>> We would however concur with whatever time you give us on this matter.**=
*
>> *
>>
>> We are a group of research and industry individuals tied together with a
>> common goal towards reducing the energy consumption in the core and edge
>> networks.****
>>
>> We present a metric-based hierarchical approach to reduce power
>> consumption in core and edge networks. The proposal considers both unica=
st
>> and the multicast cases. For unicast, the metric considered is *consumed=
-power
>> to available-bandwidth* and for multicast the metric is *consumed-power
>> to available-replication-capacity.*****
>>
>>  With unicast, the metric is used to determine a low-power path between
>> sources and destinations. With multicast, the metric serves the twin
>> purpose of finding low-power multicast paths as well as multicast
>> replication points.  We evolve multiple techniques at various hierarchic=
al
>> levels. One at the Inter-AS level, Inter-Area level within the AS and
>> intra-Area within an AS. Additionally, the proposed method can also be u=
sed
>> to determine disjoint or redundant paths for load balancing or fault
>> tolerance. Additionally since TCAMs are one of the biggest power guzzler=
s
>> in all the components on a router/switch, we have presented a solution f=
or
>> intra-AS purposes to use the TCAM according to the traffic matrix passin=
g
>> through the system and shut down those TCAM banks that are unused. With
>> this in mind, we have also advocated taking into account a TCAM-POWER-Ra=
tio
>> in order to compute the paths from source to destination based on this
>> metric. Once low-power paths, in either the unicast or the multicast cas=
es,
>> are identified then currently available traffic engineering techniques
>> could be used to route the data packets. In the case of inter-AS BGP pat=
h
>> selection is also modified to arrive at paths which are low-power paths.=
*
>> ***
>>
>>  Our main objective is as follows...****
>>
>> We now outline four important aspects that any approach for power
>> reduction should be capable of addressing.****
>>
>>  *Should cater for both unicast and multicast scenarios*****
>>
>> Multicast provides an important scenario for the Internet. Today, most
>> proposals consider mainly low-power path routing with unicast traffic.
>> Multicast traffic has received a lot of attention in wireless networks, =
but
>> not in the wired domain. Any new proposal should be able to address both
>> the unicast and the multicast traffic scenarios. Having different method=
s
>> for these two scenarios might lead to unnecessary processing burden in t=
he
>> routers, which might hinder its scalability.        ****
>>
>>  *Should not rely on just switching off unused links*****
>>
>> Most approaches to optimize energy pursue the following approach:
>> measure, monitor and respond to the system energy usage by switching off
>> unused or under-utilized links. Such an approach could be effective for
>> reducing power locally. The effect on the network is not clearly
>> understood. Further, the power usage involved in turning on and
>> rebooting/reconfiguring the device is often not explicitly considered. W=
e
>> note that Service Level Agreement (SLA) requirements may not even permit
>> the links to be switched off. Also services provided by ISPs like Virtua=
l
>> Private Networks (VPNs) can be affected by such re-routing decisions.***=
*
>>
>>  *Should follow an hierarchical and distributed approach*****
>>
>> For scalability, it is important that the algorithms proposed for
>> inter-AS should also be applicable to intra-AS situations. Networks do n=
ot
>> work in isolation, so any proposal should be both distributed and
>> hierarchical. The algorithms should be applicable at every level of the
>> hierarchy.  ****
>>
>>  *Should  provide incentives for ISP for adoption*****
>>
>> The engineering proposals should be aligned with commercial incentives
>> for rapid and widespread adoption. Today, the device manufacturers and t=
he
>> ISPs operate independently of each other, and there is no incentive for
>> manufacturers to work towards low-power and high bandwidth devices. An
>> ISP=92s revenue model is based on the consumed bandwidth, which in turn =
lead
>> naturally to more power consumption. If the proposed method chooses rout=
ers
>> that consume low-power and increase the data flow through them, then thi=
s
>> indirectly provides encouragement for ISPs to purchase low-power and hig=
h
>> bandwidth devices.                ****
>>
>>  ****
>>
>> We now present our metric-based proposals in the below mentioned drafts
>> which addresses the aforementioned design aspects.****
>>
>> We would like the routing community to provide feedback on these drafts.
>> We also intend to present this work in an abridged format in the upcomin=
g
>> IETF.****
>>
>>  The drafts are as follows....****
>>
>> ** **
>>
>> ** **
>>
>> **=B7         **mjsraman-panet-bgp-power-path<http://tools.ietf.org/html=
/draft-mjsraman-panet-bgp-power-path>
>>  (timeline)<http://www.arkko.com/tools/lifecycle/draft-mjsraman-panet-bg=
p-power-path-timing.html>
>>  Inter-AS-Proposal****
>>
>> **=B7         **mjsraman-panet-ecmp-redirect-power-repl-cap<http://tools=
.ietf.org/html/draft-mjsraman-panet-ecmp-redirect-power-repl-cap>
>>  (timeline)<http://www.arkko.com/tools/lifecycle/draft-mjsraman-panet-ec=
mp-redirect-power-repl-cap-timing.html>
>>  Multicast****
>>
>> **=B7         **mjsraman-panet-inter-as-power-source<http://tools.ietf.o=
rg/html/draft-mjsraman-panet-inter-as-power-source>
>>  (timeline)<http://www.arkko.com/tools/lifecycle/draft-mjsraman-panet-in=
ter-as-power-source-timing.html> Inter-AS
>> Proposal****
>>
>> **=B7         **mjsraman-panet-inter-as-psp<http://tools.ietf.org/html/d=
raft-mjsraman-panet-inter-as-psp>
>>  (timeline)<http://www.arkko.com/tools/lifecycle/draft-mjsraman-panet-in=
ter-as-psp-timing.html> Inter-AS
>> Proposal****
>>
>> **=B7         **mjsraman-panet-inter-as-psp-protect<http://tools.ietf.or=
g/html/draft-mjsraman-panet-inter-as-psp-protect>
>>  (timeline)<http://www.arkko.com/tools/lifecycle/draft-mjsraman-panet-in=
ter-as-psp-protect-timing.html> Inter-AS
>> Proposal****
>>
>> **=B7         **mjsraman-panet-pce-power-mcast-replic<http://tools.ietf.=
org/html/draft-mjsraman-panet-pce-power-mcast-replic>
>>  (timeline)<http://www.arkko.com/tools/lifecycle/draft-mjsraman-panet-pc=
e-power-mcast-replic-timing.html>
>>  Multicast****
>>
>> **=B7         **mjsraman-panet-pim-power<http://tools.ietf.org/html/draf=
t-mjsraman-panet-pim-power>
>>  (timeline)<http://www.arkko.com/tools/lifecycle/draft-mjsraman-panet-pi=
m-power-timing.html>
>>  Multicast****
>>
>> **=B7         **mjsraman-panet-tcam-power-efficiency<http://tools.ietf.o=
rg/html/draft-mjsraman-panet-tcam-power-efficiency>
>>  (timeline)<http://www.arkko.com/tools/lifecycle/draft-mjsraman-panet-tc=
am-power-efficiency-timing.html> TCAM
>> related****
>>
>> **=B7         **mjsraman-panet-tcam-power-ratio<http://tools.ietf.org/ht=
ml/draft-mjsraman-panet-tcam-power-ratio>
>>  (timeline<http://www.arkko.com/tools/lifecycle/draft-mjsraman-panet-tca=
m-power-ratio-timing.html>)
>> TCAM related****
>>
>> **=B7         **mjsraman-pce-power-replic<http://tools.ietf.org/html/dra=
ft-mjsraman-pce-power-replic>
>>  (timeline)<http://www.arkko.com/tools/lifecycle/draft-mjsraman-pce-powe=
r-replic-timing.html>
>>  Multicast****
>>
>> **=B7         **mjsraman-panet-intra-as-psp-te-leak<http://tools.ietf.or=
g/html/draft-mjsraman-panet-intra-as-psp-te-leak>
>>  (timeline)<http://www.arkko.com/tools/lifecycle/draft-mjsraman-panet-in=
tra-as-psp-te-leak-timing.html> Inter-Area
>> within an AS****
>>
>> **=B7         **mjsraman-panet-ospf-power-topo<http://tools.ietf.org/htm=
l/draft-mjsraman-panet-ospf-power-topo>
>>  (timeline)<http://www.arkko.com/tools/lifecycle/draft-mjsraman-panet-os=
pf-power-topo-timing.html> Intra-Area
>> within an AS****
>>
>> We understand it is a lot of matter to go through. We would much
>> appreciate if some of you could review the inter-AS proposals while othe=
rs
>> take up multicast and Intra-AS unicast and multicast.****
>>
>> ** **
>>
>> Thanks again for your time on this matter.****
>>
>> ** **
>>
>> thanks and regards,****
>>
>> balaji venkat****
>>
>
>

--047d7b5da2a571438804d50c6e8c
Content-Type: text/html; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

CCing the correct Lars Eggert email.<div><br></div><div>thanks and regards,=
</div><div>balaji venkat<br><br><div class=3D"gmail_quote">On Wed, Feb 6, 2=
013 at 4:43 PM, Balaji venkat Venkataswami <span dir=3D"ltr">&lt;<a href=3D=
"mailto:balajivenkat299@gmail.com" target=3D"_blank">balajivenkat299@gmail.=
com</a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">Hi Dan,<div><br></div><div>It could be defin=
itely part of EERG. That is our opinion.</div><div><br></div><div>thanks an=
d regards,</div>
<div>balaji venkat<div><div class=3D"h5"><br><br><div class=3D"gmail_quote"=
>On Wed, Feb 6, 2013 at 4:15 PM, Romascanu, Dan (Dan) <span dir=3D"ltr">&lt=
;<a href=3D"mailto:dromasca@avaya.com" target=3D"_blank">dromasca@avaya.com=
</a>&gt;</span> wrote:<br>

<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">





<div lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">Hi Balaji,<u></u><u></u><=
/span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d"><u></u>=A0<u></u></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">Is the scope of the work =
that you propose different of EERG, =A0could it be part of EERG, or an exte=
nsion?
<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d"><u></u>=A0<u></u></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">Thanks and Regards,<u></u=
><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d"><u></u>=A0<u></u></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">Dan<u></u><u></u></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d"><u></u>=A0<u></u></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d"><u></u>=A0<u></u></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d"><u></u>=A0<u></u></span><=
/p>
<div style=3D"border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in =
4.0pt">
<div>
<div style=3D"border:none;border-top:solid #b5c4df 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span style=3D"font-s=
ize:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> <a href=
=3D"mailto:irtf-discuss-bounces@irtf.org" target=3D"_blank">irtf-discuss-bo=
unces@irtf.org</a> [mailto:<a href=3D"mailto:irtf-discuss-bounces@irtf.org"=
 target=3D"_blank">irtf-discuss-bounces@irtf.org</a>]
<b>On Behalf Of </b>Balaji venkat Venkataswami<br>
<b>Sent:</b> Wednesday, February 06, 2013 8:58 AM<br>
<b>To:</b> <a href=3D"mailto:irtf-discuss@irtf.org" target=3D"_blank">irtf-=
discuss@irtf.org</a>; Lars Eggert; Susan Hares<br>
<b>Subject:</b> [irtf-discuss] Request for a side-bar meeting in the IETF O=
rlando on Power-Aware Networking drafts<u></u><u></u></span></p>
</div>
</div><div><div>
<p class=3D"MsoNormal"><u></u>=A0<u></u></p>
<p class=3D"MsoNormal">Dear Lars, all,<u></u><u></u></p>
<div>
<p class=3D"MsoNormal"><u></u>=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">We would like a side-bar meeting (in an adjacent roo=
m) to discuss the following Power-Aware-Networking proposals.<u></u><u></u>=
</p>
</div>
<div>
<p class=3D"MsoNormal">A detailed outline of the drafts submitted have been=
 detailed below. We would like a 20 minute slot with 10 minutes for Q&amp;A=
 if possible.<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">We would however concur with whatever time you give =
us on this matter.<u></u><u></u></p>
</div>
<div>
<p style=3D"background:white"><span style=3D"font-size:10.0pt;font-family:&=
quot;Arial&quot;,&quot;sans-serif&quot;;color:#222222">We are a group of re=
search and industry individuals tied together with a common goal towards re=
ducing the energy consumption in the core and edge networks.<u></u><u></u><=
/span></p>


<p style=3D"background:white"><span style=3D"font-size:10.0pt;font-family:&=
quot;Arial&quot;,&quot;sans-serif&quot;;color:#222222">We present a metric-=
based hierarchical approach to reduce power consumption in core and edge ne=
tworks. The proposal considers both unicast and the multicast
 cases. For unicast, the metric considered is=A0<i>consumed-power to availa=
ble-bandwidth</i>=A0and for multicast the metric is=A0<i>consumed-power to =
available-replication-capacity.</i><u></u><u></u></span></p>
<p style=3D"background:white"><span style=3D"font-size:10.0pt;font-family:&=
quot;Arial&quot;,&quot;sans-serif&quot;;color:#222222">=A0With unicast, the=
 metric is=A0used to determine a low-power path between sources and destina=
tions.=A0With multicast, the=A0metric serves the twin purpose of
 finding low-power multicast paths as well as multicast replication points.=
=A0=A0We evolve multiple techniques at various hierarchical levels. One at =
the Inter-AS level, Inter-Area level within the AS and intra-Area within an=
 AS. Additionally, the proposed method
 can also be used to determine disjoint or redundant paths for load balanci=
ng or fault tolerance. Additionally since TCAMs are one of the biggest powe=
r guzzlers in all the components on a router/switch, we have presented a so=
lution for intra-AS purposes to
 use the TCAM according to the traffic matrix passing through the system an=
d shut down those TCAM banks that are unused. With this in mind, we have al=
so advocated taking into account a TCAM-POWER-Ratio in order to compute the=
 paths from source to destination
 based on this metric. Once low-power paths, in either the unicast or the m=
ulticast cases, are identified then currently available traffic engineering=
 techniques could be used to route the data packets. In the case of inter-A=
S BGP path selection is also modified
 to arrive at paths which are low-power paths.<u></u><u></u></span></p>
<p style=3D"background:white"><span style=3D"font-size:10.0pt;font-family:&=
quot;Arial&quot;,&quot;sans-serif&quot;;color:#222222">=A0Our main objectiv=
e is as follows...<u></u><u></u></span></p>
<p style=3D"background:white"><span style=3D"font-size:10.0pt;font-family:&=
quot;Arial&quot;,&quot;sans-serif&quot;;color:#222222">We now outline four =
important aspects that any approach for power reduction should be capable o=
f addressing.<u></u><u></u></span></p>


<p style=3D"background:white"><span style=3D"font-size:10.0pt;font-family:&=
quot;Arial&quot;,&quot;sans-serif&quot;;color:#222222">=A0<i>Should cater f=
or both unicast and multicast scenarios</i><u></u><u></u></span></p>
<p style=3D"background:white"><span style=3D"font-size:10.0pt;font-family:&=
quot;Arial&quot;,&quot;sans-serif&quot;;color:#222222">Multicast provides a=
n important scenario for the Internet. Today, most proposals consider mainl=
y low-power path routing with unicast traffic. Multicast
 traffic has received a lot of attention in wireless networks, but not in t=
he wired domain. Any new proposal should be able to address both the unicas=
t and the multicast traffic scenarios. Having different methods for these t=
wo scenarios might lead to unnecessary
 processing burden in the routers, which might hinder its scalability.=A0=
=A0=A0=A0=A0=A0=A0=A0<u></u><u></u></span></p>
<p style=3D"background:white"><span style=3D"font-size:10.0pt;font-family:&=
quot;Arial&quot;,&quot;sans-serif&quot;;color:#222222">=A0<i>Should not rel=
y on just switching off unused links</i><u></u><u></u></span></p>
<p style=3D"background:white"><span style=3D"font-size:10.0pt;font-family:&=
quot;Arial&quot;,&quot;sans-serif&quot;;color:#222222">Most approaches to o=
ptimize energy pursue the following approach: measure, monitor and respond =
to the system energy usage by switching off unused or under-utilized
 links. Such an approach could be effective for reducing power locally. The=
 effect on the network is not clearly understood. Further, the power usage =
involved in turning on and rebooting/reconfiguring the device is often not =
explicitly considered. We note that
 Service Level Agreement (SLA) requirements may not even permit the links t=
o be switched off. Also services provided by ISPs like Virtual Private Netw=
orks (VPNs) can be affected by such re-routing decisions.<u></u><u></u></sp=
an></p>


<p style=3D"background:white"><span style=3D"font-size:10.0pt;font-family:&=
quot;Arial&quot;,&quot;sans-serif&quot;;color:#222222">=A0<i>Should follow =
an hierarchical and distributed approach</i><u></u><u></u></span></p>
<p style=3D"background:white"><span style=3D"font-size:10.0pt;font-family:&=
quot;Arial&quot;,&quot;sans-serif&quot;;color:#222222">For scalability, it =
is important that the algorithms proposed for inter-AS should also be appli=
cable to intra-AS situations. Networks do not work in isolation,
 so any proposal should be both distributed and hierarchical. The algorithm=
s should be applicable at every level of the hierarchy.=A0=A0<u></u><u></u>=
</span></p>
<p style=3D"background:white"><span style=3D"font-size:10.0pt;font-family:&=
quot;Arial&quot;,&quot;sans-serif&quot;;color:#222222">=A0<i>Should=A0=A0pr=
ovide incentives for ISP for adoption</i><u></u><u></u></span></p>
<p style=3D"background:white"><span style=3D"font-size:10.0pt;font-family:&=
quot;Arial&quot;,&quot;sans-serif&quot;;color:#222222">The engineering prop=
osals should be aligned with commercial incentives for rapid and widespread=
 adoption. Today, the device manufacturers and the ISPs
 operate independently of each other, and there is no incentive for manufac=
turers to work towards low-power and high bandwidth devices. An ISP=92s rev=
enue model is based on the consumed bandwidth, which in turn lead naturally=
 to more power consumption. If the
 proposed method chooses routers that consume low-power and increase the da=
ta flow through them, then this indirectly provides encouragement for ISPs =
to purchase low-power and high bandwidth devices.=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0<u></u><u></u></span></p>


<p style=3D"background:white"><span style=3D"font-size:10.0pt;font-family:&=
quot;Arial&quot;,&quot;sans-serif&quot;;color:#222222">=A0<u></u><u></u></s=
pan></p>
<p style=3D"background:white"><span style=3D"font-size:10.0pt;font-family:&=
quot;Arial&quot;,&quot;sans-serif&quot;;color:#222222">We now present our m=
etric-based proposals in the below mentioned drafts which addresses the afo=
rementioned design aspects.<u></u><u></u></span></p>


<p style=3D"background:white"><span style=3D"font-size:10.0pt;font-family:&=
quot;Arial&quot;,&quot;sans-serif&quot;;color:#222222">We would like the ro=
uting community to provide feedback on these drafts. We also intend to pres=
ent this work in an abridged format in the upcoming IETF.<u></u><u></u></sp=
an></p>


<p class=3D"MsoNormal" style=3D"background:white">
<span style=3D"font-size:11.0pt;font-family:&quot;Arial&quot;,&quot;sans-se=
rif&quot;;color:#222222">=A0The drafts are as follows....</span><span style=
=3D"font-size:10.0pt;font-family:&quot;Arial&quot;,&quot;sans-serif&quot;;c=
olor:#222222"><u></u><u></u></span></p>


<p class=3D"MsoNormal" style=3D"background:white">
<span style=3D"font-size:10.0pt;font-family:&quot;Arial&quot;,&quot;sans-se=
rif&quot;;color:#222222"><u></u>=A0<u></u></span></p>
<p class=3D"MsoNormal" style=3D"background:white">
<span style=3D"font-size:10.0pt;font-family:&quot;Arial&quot;,&quot;sans-se=
rif&quot;;color:#222222"><u></u>=A0<u></u></span></p>
<p class=3D"MsoNormal" style=3D"margin-right:12.0pt;margin-bottom:3.0pt;mar=
gin-left:23.25pt;background:white">
<u></u><span style=3D"font-size:10.0pt;font-family:Symbol;color:#222222"><s=
pan>=B7<span style=3D"font:7.0pt &quot;Times New Roman&quot;">=A0=A0=A0=A0=
=A0=A0=A0=A0
</span></span></span><u></u><span dir=3D"LTR"></span><span style=3D"font-si=
ze:10.0pt;font-family:&quot;Arial&quot;,&quot;sans-serif&quot;;color:#22222=
2"><a href=3D"http://tools.ietf.org/html/draft-mjsraman-panet-bgp-power-pat=
h" target=3D"_blank"><span style=3D"color:#440088">mjsraman-panet-bgp-power=
-path</span></a>=A0<a href=3D"http://www.arkko.com/tools/lifecycle/draft-mj=
sraman-panet-bgp-power-path-timing.html" target=3D"_blank"><span style=3D"c=
olor:#440088">(timeline)</span></a>=A0Inter-AS-Proposal<u></u><u></u></span=
></p>


<p class=3D"MsoNormal" style=3D"margin-right:12.0pt;margin-bottom:3.0pt;mar=
gin-left:23.25pt;background:white">
<u></u><span style=3D"font-size:10.0pt;font-family:Symbol;color:#222222"><s=
pan>=B7<span style=3D"font:7.0pt &quot;Times New Roman&quot;">=A0=A0=A0=A0=
=A0=A0=A0=A0
</span></span></span><u></u><span dir=3D"LTR"></span><span style=3D"font-si=
ze:10.0pt;font-family:&quot;Arial&quot;,&quot;sans-serif&quot;;color:#22222=
2"><a href=3D"http://tools.ietf.org/html/draft-mjsraman-panet-ecmp-redirect=
-power-repl-cap" target=3D"_blank"><span style=3D"color:#440088">mjsraman-p=
anet-ecmp-redirect-power-repl-cap</span></a>=A0<a href=3D"http://www.arkko.=
com/tools/lifecycle/draft-mjsraman-panet-ecmp-redirect-power-repl-cap-timin=
g.html" target=3D"_blank"><span style=3D"color:#440088">(timeline)</span></=
a>=A0Multicast<u></u><u></u></span></p>


<p class=3D"MsoNormal" style=3D"margin-right:12.0pt;margin-bottom:3.0pt;mar=
gin-left:23.25pt;background:white">
<u></u><span style=3D"font-size:10.0pt;font-family:Symbol;color:#222222"><s=
pan>=B7<span style=3D"font:7.0pt &quot;Times New Roman&quot;">=A0=A0=A0=A0=
=A0=A0=A0=A0
</span></span></span><u></u><span dir=3D"LTR"></span><span style=3D"font-si=
ze:10.0pt;font-family:&quot;Arial&quot;,&quot;sans-serif&quot;;color:#22222=
2"><a href=3D"http://tools.ietf.org/html/draft-mjsraman-panet-inter-as-powe=
r-source" target=3D"_blank"><span style=3D"color:#440088">mjsraman-panet-in=
ter-as-power-source</span></a>=A0<a href=3D"http://www.arkko.com/tools/life=
cycle/draft-mjsraman-panet-inter-as-power-source-timing.html" target=3D"_bl=
ank"><span style=3D"color:#440088">(timeline)</span></a>=A0Inter-AS
 Proposal<u></u><u></u></span></p>
<p class=3D"MsoNormal" style=3D"margin-right:12.0pt;margin-bottom:3.0pt;mar=
gin-left:23.25pt;background:white">
<u></u><span style=3D"font-size:10.0pt;font-family:Symbol;color:#222222"><s=
pan>=B7<span style=3D"font:7.0pt &quot;Times New Roman&quot;">=A0=A0=A0=A0=
=A0=A0=A0=A0
</span></span></span><u></u><span dir=3D"LTR"></span><span style=3D"font-si=
ze:10.0pt;font-family:&quot;Arial&quot;,&quot;sans-serif&quot;;color:#22222=
2"><a href=3D"http://tools.ietf.org/html/draft-mjsraman-panet-inter-as-psp"=
 target=3D"_blank"><span style=3D"color:#440088">mjsraman-panet-inter-as-ps=
p</span></a>=A0<a href=3D"http://www.arkko.com/tools/lifecycle/draft-mjsram=
an-panet-inter-as-psp-timing.html" target=3D"_blank"><span style=3D"color:#=
440088">(timeline)</span></a>=A0Inter-AS
 Proposal<u></u><u></u></span></p>
<p class=3D"MsoNormal" style=3D"margin-right:12.0pt;margin-bottom:3.0pt;mar=
gin-left:23.25pt;background:white">
<u></u><span style=3D"font-size:10.0pt;font-family:Symbol;color:#222222"><s=
pan>=B7<span style=3D"font:7.0pt &quot;Times New Roman&quot;">=A0=A0=A0=A0=
=A0=A0=A0=A0
</span></span></span><u></u><span dir=3D"LTR"></span><span style=3D"font-si=
ze:10.0pt;font-family:&quot;Arial&quot;,&quot;sans-serif&quot;;color:#22222=
2"><a href=3D"http://tools.ietf.org/html/draft-mjsraman-panet-inter-as-psp-=
protect" target=3D"_blank"><span style=3D"color:#440088">mjsraman-panet-int=
er-as-psp-protect</span></a>=A0<a href=3D"http://www.arkko.com/tools/lifecy=
cle/draft-mjsraman-panet-inter-as-psp-protect-timing.html" target=3D"_blank=
"><span style=3D"color:#440088">(timeline)</span></a>=A0Inter-AS
 Proposal<u></u><u></u></span></p>
<p class=3D"MsoNormal" style=3D"margin-right:12.0pt;margin-bottom:3.0pt;mar=
gin-left:23.25pt;background:white">
<u></u><span style=3D"font-size:10.0pt;font-family:Symbol;color:#222222"><s=
pan>=B7<span style=3D"font:7.0pt &quot;Times New Roman&quot;">=A0=A0=A0=A0=
=A0=A0=A0=A0
</span></span></span><u></u><span dir=3D"LTR"></span><span style=3D"font-si=
ze:10.0pt;font-family:&quot;Arial&quot;,&quot;sans-serif&quot;;color:#22222=
2"><a href=3D"http://tools.ietf.org/html/draft-mjsraman-panet-pce-power-mca=
st-replic" target=3D"_blank"><span style=3D"color:#440088">mjsraman-panet-p=
ce-power-mcast-replic</span></a>=A0<a href=3D"http://www.arkko.com/tools/li=
fecycle/draft-mjsraman-panet-pce-power-mcast-replic-timing.html" target=3D"=
_blank"><span style=3D"color:#440088">(timeline)</span></a>=A0Multicast<u><=
/u><u></u></span></p>


<p class=3D"MsoNormal" style=3D"margin-right:12.0pt;margin-bottom:3.0pt;mar=
gin-left:23.25pt;background:white">
<u></u><span style=3D"font-size:10.0pt;font-family:Symbol;color:#222222"><s=
pan>=B7<span style=3D"font:7.0pt &quot;Times New Roman&quot;">=A0=A0=A0=A0=
=A0=A0=A0=A0
</span></span></span><u></u><span dir=3D"LTR"></span><span style=3D"font-si=
ze:10.0pt;font-family:&quot;Arial&quot;,&quot;sans-serif&quot;;color:#22222=
2"><a href=3D"http://tools.ietf.org/html/draft-mjsraman-panet-pim-power" ta=
rget=3D"_blank"><span style=3D"color:#440088">mjsraman-panet-pim-power</spa=
n></a>=A0<a href=3D"http://www.arkko.com/tools/lifecycle/draft-mjsraman-pan=
et-pim-power-timing.html" target=3D"_blank"><span style=3D"color:#440088">(=
timeline)</span></a>=A0Multicast<u></u><u></u></span></p>


<p class=3D"MsoNormal" style=3D"margin-right:12.0pt;margin-bottom:3.0pt;mar=
gin-left:23.25pt;background:white">
<u></u><span style=3D"font-size:10.0pt;font-family:Symbol;color:#222222"><s=
pan>=B7<span style=3D"font:7.0pt &quot;Times New Roman&quot;">=A0=A0=A0=A0=
=A0=A0=A0=A0
</span></span></span><u></u><span dir=3D"LTR"></span><span style=3D"font-si=
ze:10.0pt;font-family:&quot;Arial&quot;,&quot;sans-serif&quot;;color:#22222=
2"><a href=3D"http://tools.ietf.org/html/draft-mjsraman-panet-tcam-power-ef=
ficiency" target=3D"_blank"><span style=3D"color:#440088">mjsraman-panet-tc=
am-power-efficiency</span></a>=A0<a href=3D"http://www.arkko.com/tools/life=
cycle/draft-mjsraman-panet-tcam-power-efficiency-timing.html" target=3D"_bl=
ank"><span style=3D"color:#440088">(timeline)</span></a>=A0TCAM
 related<u></u><u></u></span></p>
<p class=3D"MsoNormal" style=3D"margin-right:12.0pt;margin-bottom:3.0pt;mar=
gin-left:23.25pt;background:white">
<u></u><span style=3D"font-size:10.0pt;font-family:Symbol;color:#222222"><s=
pan>=B7<span style=3D"font:7.0pt &quot;Times New Roman&quot;">=A0=A0=A0=A0=
=A0=A0=A0=A0
</span></span></span><u></u><span dir=3D"LTR"></span><span style=3D"font-si=
ze:10.0pt;font-family:&quot;Arial&quot;,&quot;sans-serif&quot;;color:#22222=
2"><a href=3D"http://tools.ietf.org/html/draft-mjsraman-panet-tcam-power-ra=
tio" target=3D"_blank"><span style=3D"color:#440088">mjsraman-panet-tcam-po=
wer-ratio</span></a>=A0<a href=3D"http://www.arkko.com/tools/lifecycle/draf=
t-mjsraman-panet-tcam-power-ratio-timing.html" target=3D"_blank"><span styl=
e=3D"color:#440088">(timeline</span></a>)
 TCAM related<u></u><u></u></span></p>
<p class=3D"MsoNormal" style=3D"margin-right:12.0pt;margin-bottom:3.0pt;mar=
gin-left:23.25pt;background:white">
<u></u><span style=3D"font-size:10.0pt;font-family:Symbol;color:#222222"><s=
pan>=B7<span style=3D"font:7.0pt &quot;Times New Roman&quot;">=A0=A0=A0=A0=
=A0=A0=A0=A0
</span></span></span><u></u><span dir=3D"LTR"></span><span style=3D"font-si=
ze:10.0pt;font-family:&quot;Arial&quot;,&quot;sans-serif&quot;;color:#22222=
2"><a href=3D"http://tools.ietf.org/html/draft-mjsraman-pce-power-replic" t=
arget=3D"_blank"><span style=3D"color:#440088">mjsraman-pce-power-replic</s=
pan></a>=A0<a href=3D"http://www.arkko.com/tools/lifecycle/draft-mjsraman-p=
ce-power-replic-timing.html" target=3D"_blank"><span style=3D"color:#440088=
">(timeline)</span></a>=A0Multicast<u></u><u></u></span></p>


<p class=3D"MsoNormal" style=3D"margin-right:12.0pt;margin-bottom:3.0pt;mar=
gin-left:23.25pt;background:white">
<u></u><span style=3D"font-size:10.0pt;font-family:Symbol;color:#222222"><s=
pan>=B7<span style=3D"font:7.0pt &quot;Times New Roman&quot;">=A0=A0=A0=A0=
=A0=A0=A0=A0
</span></span></span><u></u><span dir=3D"LTR"></span><span style=3D"font-si=
ze:10.0pt;font-family:&quot;Arial&quot;,&quot;sans-serif&quot;;color:#22222=
2"><a href=3D"http://tools.ietf.org/html/draft-mjsraman-panet-intra-as-psp-=
te-leak" target=3D"_blank"><span style=3D"color:#440088">mjsraman-panet-int=
ra-as-psp-te-leak</span></a>=A0<a href=3D"http://www.arkko.com/tools/lifecy=
cle/draft-mjsraman-panet-intra-as-psp-te-leak-timing.html" target=3D"_blank=
"><span style=3D"color:#440088">(timeline)</span></a>=A0Inter-Area
 within an AS<u></u><u></u></span></p>
<p class=3D"MsoNormal" style=3D"margin-right:12.0pt;margin-bottom:3.0pt;mar=
gin-left:23.25pt;background:white">
<u></u><span style=3D"font-size:10.0pt;font-family:Symbol;color:#222222"><s=
pan>=B7<span style=3D"font:7.0pt &quot;Times New Roman&quot;">=A0=A0=A0=A0=
=A0=A0=A0=A0
</span></span></span><u></u><span dir=3D"LTR"></span><span style=3D"font-si=
ze:10.0pt;font-family:&quot;Arial&quot;,&quot;sans-serif&quot;;color:#22222=
2"><a href=3D"http://tools.ietf.org/html/draft-mjsraman-panet-ospf-power-to=
po" target=3D"_blank"><span style=3D"color:#440088">mjsraman-panet-ospf-pow=
er-topo</span></a>=A0<a href=3D"http://www.arkko.com/tools/lifecycle/draft-=
mjsraman-panet-ospf-power-topo-timing.html" target=3D"_blank"><span style=
=3D"color:#440088">(timeline)</span></a>=A0Intra-Area
 within an AS<u></u><u></u></span></p>
<div>
<p class=3D"MsoNormal" style=3D"background:white"><span style=3D"font-size:=
10.0pt;font-family:&quot;Arial&quot;,&quot;sans-serif&quot;;color:#222222">=
We understand it is a lot of matter to go through. We would much appreciate=
 if some of you could review the inter-AS proposals while
 others take up multicast and Intra-AS unicast and multicast.<u></u><u></u>=
</span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"background:white"><span style=3D"font-size:=
10.0pt;font-family:&quot;Arial&quot;,&quot;sans-serif&quot;;color:#222222">=
<u></u>=A0<u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"background:white"><span style=3D"font-size:=
10.0pt;font-family:&quot;Arial&quot;,&quot;sans-serif&quot;;color:#222222">=
Thanks again for your time on this matter.<u></u><u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"background:white"><span style=3D"font-size:=
10.0pt;font-family:&quot;Arial&quot;,&quot;sans-serif&quot;;color:#222222">=
<u></u>=A0<u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"background:white"><span style=3D"font-size:=
10.0pt;font-family:&quot;Arial&quot;,&quot;sans-serif&quot;;color:#222222">=
thanks and regards,<u></u><u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"background:white"><span style=3D"font-size:=
10.0pt;font-family:&quot;Arial&quot;,&quot;sans-serif&quot;;color:#222222">=
balaji venkat<u></u><u></u></span></p>
</div>
</div>
</div></div></div>
</div>
</div>

</blockquote></div><br></div></div></div>
</blockquote></div><br></div>

--047d7b5da2a571438804d50c6e8c--

From lars@netapp.com  Wed Feb  6 03:36:07 2013
Return-Path: <lars@netapp.com>
X-Original-To: irtf-discuss@ietfa.amsl.com
Delivered-To: irtf-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9428121F8984 for <irtf-discuss@ietfa.amsl.com>; Wed,  6 Feb 2013 03:36:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.889
X-Spam-Level: 
X-Spam-Status: No, score=-9.889 tagged_above=-999 required=5 tests=[AWL=-0.089, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, SARE_SUB_RAND_LETTRS4=0.799]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jQnERi6LYN3d for <irtf-discuss@ietfa.amsl.com>; Wed,  6 Feb 2013 03:36:05 -0800 (PST)
Received: from mx12.netapp.com (mx12.netapp.com [216.240.18.77]) by ietfa.amsl.com (Postfix) with ESMTP id 29BAE21F8971 for <irtf-discuss@irtf.org>; Wed,  6 Feb 2013 03:36:04 -0800 (PST)
X-IronPort-AV: E=Sophos;i="4.84,614,1355126400"; d="scan'208";a="17050078"
Received: from smtp1.corp.netapp.com ([10.57.156.124]) by mx12-out.netapp.com with ESMTP; 06 Feb 2013 03:36:03 -0800
Received: from vmwexceht01-prd.hq.netapp.com (vmwexceht01-prd.hq.netapp.com [10.106.76.239]) by smtp1.corp.netapp.com (8.13.1/8.13.1/NTAP-1.6) with ESMTP id r16Ba2cZ009855; Wed, 6 Feb 2013 03:36:02 -0800 (PST)
Received: from SACEXCMBX01-PRD.hq.netapp.com ([169.254.2.54]) by vmwexceht01-prd.hq.netapp.com ([10.106.76.239]) with mapi id 14.02.0328.009; Wed, 6 Feb 2013 03:36:01 -0800
From: "Eggert, Lars" <lars@netapp.com>
To: "<eerg@listserv.netlab.nec.de>" <eerg@listserv.netlab.nec.de>
Thread-Topic: [EERG] [irtf-discuss] Request for a side-bar meeting in the IETF Orlando on Power-Aware Networking drafts
Thread-Index: AQHOBDdH1oE+cJfMhUWzP5+w+gl6SZhtK9cAgAAHt4CAAAZkgA==
Date: Wed, 6 Feb 2013 11:36:00 +0000
Message-ID: <D4D47BCFFE5A004F95D707546AC0D7E91F6E5515@SACEXCMBX01-PRD.hq.netapp.com>
References: <CAHF4apMOpXohhWpYXB8X74yG4fBhcjVW0c=vNW4qXudJ7H92rA@mail.gmail.com> <9904FB1B0159DA42B0B887B7FA8119CA082E38@AZ-FFEXMB04.global.avaya.com> <CAHF4apN_94fp0VVrspjXFDTbfkusHY7e7usaNNgQ92Spaz_fgw@mail.gmail.com>
In-Reply-To: <CAHF4apN_94fp0VVrspjXFDTbfkusHY7e7usaNNgQ92Spaz_fgw@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.106.53.51]
Content-Type: text/plain; charset="Windows-1252"
Content-ID: <741FA8CC932FBB4E8538BAF3DFA01F92@tahoe.netapp.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "irtf-discuss@irtf.org" <irtf-discuss@irtf.org>, Susan Hares <susan.hares@huawei.com>
Subject: Re: [irtf-discuss] [EERG] Request for a side-bar meeting in the IETF Orlando on Power-Aware Networking drafts
X-BeenThere: irtf-discuss@irtf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IRTF general and new-work discussion list <irtf-discuss.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/options/irtf-discuss>, <mailto:irtf-discuss-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/irtf-discuss>
List-Post: <mailto:irtf-discuss@irtf.org>
List-Help: <mailto:irtf-discuss-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/irtf-discuss>, <mailto:irtf-discuss-request@irtf.org?subject=subscribe>
X-List-Received-Date: Wed, 06 Feb 2013 11:36:07 -0000

Hi,

On Feb 6, 2013, at 12:13, Balaji venkat Venkataswami <balajivenkat299@gmail=
.com> wrote:
> It could be definitely part of EERG. That is our opinion.

You should probably also bring this up in RRG, since there is a distinct fo=
cus on routing here?

Lars=

From balajivenkat299@gmail.com  Wed Feb  6 04:08:46 2013
Return-Path: <balajivenkat299@gmail.com>
X-Original-To: irtf-discuss@ietfa.amsl.com
Delivered-To: irtf-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D489C21F8971 for <irtf-discuss@ietfa.amsl.com>; Wed,  6 Feb 2013 04:08:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.504
X-Spam-Level: 
X-Spam-Status: No, score=0.504 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, MIME_QP_LONG_LINE=1.396, RCVD_ILLEGAL_IP=1.908, RCVD_IN_DNSWL_LOW=-1, SARE_SUB_RAND_LETTRS4=0.799]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 219eSUyDVaXT for <irtf-discuss@ietfa.amsl.com>; Wed,  6 Feb 2013 04:08:44 -0800 (PST)
Received: from mail-pa0-f46.google.com (mail-pa0-f46.google.com [209.85.220.46]) by ietfa.amsl.com (Postfix) with ESMTP id 8672221F8550 for <irtf-discuss@irtf.org>; Wed,  6 Feb 2013 04:08:39 -0800 (PST)
Received: by mail-pa0-f46.google.com with SMTP id kp14so774483pab.5 for <irtf-discuss@irtf.org>; Wed, 06 Feb 2013 04:08:35 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:references:mime-version:in-reply-to:content-type :content-transfer-encoding:message-id:cc:x-mailer:from:subject:date :to; bh=QDIUWPUJnc5D+sOavQzhaKGl8DFZXBNt6rlywKxST1M=; b=Vq8FUG8q/j+/cJ4zSeFqbHmL2e1DCWbXaVh+DzQESWQXbdGw2JVaHnl0fmoYRJCCL+ eZyRC0S+WU4ybp1PFdMpxia/YbxZWx9rVG+7mfRtz8ihGYeYEfTLdu3gndab02uW7waB fC5Uwykrba5yQ5exd+GBLjyLvCVqBpVilJUxHIPqmSf8mbfo6cY1SA79aGstva6n+fBU UheOGD0ZaP3gVLRgjef7cTNJJPkCTdr5fXyPBOu4pu3pRHUGFiK1rlET4yyQQbyaRF2J 5GeAARNNpxmgwZBIwq3u1vTSVfRiFwXmCIkUjiIOq6YxSNWnlz8rHBJUh74bz66SQJ2k 6a7w==
X-Received: by 10.66.82.170 with SMTP id j10mr75626078pay.9.1360152515489; Wed, 06 Feb 2013 04:08:35 -0800 (PST)
Received: from [223.181.219.11] ([223.181.219.11]) by mx.google.com with ESMTPS id m3sm37275707pav.4.2013.02.06.04.08.30 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 06 Feb 2013 04:08:34 -0800 (PST)
References: <CAHF4apMOpXohhWpYXB8X74yG4fBhcjVW0c=vNW4qXudJ7H92rA@mail.gmail.com> <9904FB1B0159DA42B0B887B7FA8119CA082E38@AZ-FFEXMB04.global.avaya.com> <CAHF4apN_94fp0VVrspjXFDTbfkusHY7e7usaNNgQ92Spaz_fgw@mail.gmail.com> <D4D47BCFFE5A004F95D707546AC0D7E91F6E5515@SACEXCMBX01-PRD.hq.netapp.com>
Mime-Version: 1.0 (1.0)
In-Reply-To: <D4D47BCFFE5A004F95D707546AC0D7E91F6E5515@SACEXCMBX01-PRD.hq.netapp.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Message-Id: <F03B546C-463B-4F01-A822-71B4E31668E6@gmail.com>
X-Mailer: iPhone Mail (10A551)
From: Balaji Venkat <balajivenkat299@gmail.com>
Date: Wed, 6 Feb 2013 17:38:30 +0530
To: "Eggert, Lars" <lars@netapp.com>
Cc: "irtf-discuss@irtf.org" <irtf-discuss@irtf.org>, "<eerg@listserv.netlab.nec.de>" <eerg@listserv.netlab.nec.de>, Susan Hares <susan.hares@huawei.com>
Subject: Re: [irtf-discuss] [EERG] Request for a side-bar meeting in the IETF Orlando on Power-Aware Networking drafts
X-BeenThere: irtf-discuss@irtf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IRTF general and new-work discussion list <irtf-discuss.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/options/irtf-discuss>, <mailto:irtf-discuss-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/irtf-discuss>
List-Post: <mailto:irtf-discuss@irtf.org>
List-Help: <mailto:irtf-discuss-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/irtf-discuss>, <mailto:irtf-discuss-request@irtf.org?subject=subscribe>
X-List-Received-Date: Wed, 06 Feb 2013 12:08:47 -0000

Dear Lars

Tony li replied saying the RRG is in hibernation and that RRG will not meet i=
n Orlando

Would be much obliged if you can us help in this regard

Thanks and regards=20
Balaji

Sent from my iPhone

On 06-Feb-2013, at 5:06 PM, "Eggert, Lars" <lars@netapp.com> wrote:

> Hi,
>=20
> On Feb 6, 2013, at 12:13, Balaji venkat Venkataswami <balajivenkat299@gmai=
l.com> wrote:
>> It could be definitely part of EERG. That is our opinion.
>=20
> You should probably also bring this up in RRG, since there is a distinct f=
ocus on routing here?
>=20
> Lars

From lars@netapp.com  Wed Feb  6 04:22:34 2013
Return-Path: <lars@netapp.com>
X-Original-To: irtf-discuss@ietfa.amsl.com
Delivered-To: irtf-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BEF8D21F857E for <irtf-discuss@ietfa.amsl.com>; Wed,  6 Feb 2013 04:22:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.884
X-Spam-Level: 
X-Spam-Status: No, score=-9.884 tagged_above=-999 required=5 tests=[AWL=-0.084, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, SARE_SUB_RAND_LETTRS4=0.799]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RT1nY8eeOtfF for <irtf-discuss@ietfa.amsl.com>; Wed,  6 Feb 2013 04:22:32 -0800 (PST)
Received: from mx12.netapp.com (mx12.netapp.com [216.240.18.77]) by ietfa.amsl.com (Postfix) with ESMTP id 40FC821F855F for <irtf-discuss@irtf.org>; Wed,  6 Feb 2013 04:22:31 -0800 (PST)
X-IronPort-AV: E=Sophos;i="4.84,615,1355126400"; d="scan'208";a="17065112"
Received: from smtp2.corp.netapp.com ([10.57.159.114]) by mx12-out.netapp.com with ESMTP; 06 Feb 2013 04:22:30 -0800
Received: from vmwexceht04-prd.hq.netapp.com (vmwexceht04-prd.hq.netapp.com [10.106.77.34]) by smtp2.corp.netapp.com (8.13.1/8.13.1/NTAP-1.6) with ESMTP id r16CMSC8022263; Wed, 6 Feb 2013 04:22:30 -0800 (PST)
Received: from VMWEXCEHT06-PRD.hq.netapp.com (10.106.77.104) by vmwexceht04-prd.hq.netapp.com (10.106.77.34) with Microsoft SMTP Server (TLS) id 14.2.328.9; Wed, 6 Feb 2013 04:22:28 -0800
Received: from SACEXCMBX01-PRD.hq.netapp.com ([169.254.2.54]) by vmwexceht06-prd.hq.netapp.com ([10.106.77.104]) with mapi id 14.02.0328.009; Wed, 6 Feb 2013 04:22:28 -0800
From: "Eggert, Lars" <lars@netapp.com>
To: Balaji Venkat <balajivenkat299@gmail.com>
Thread-Topic: [irtf-discuss] [EERG] Request for a side-bar meeting in the IETF Orlando on Power-Aware Networking drafts
Thread-Index: AQHOBGKxjkiQ0CEV50yDRXZupnohgphtRpeA
Date: Wed, 6 Feb 2013 12:22:27 +0000
Message-ID: <D4D47BCFFE5A004F95D707546AC0D7E91F6E5ED0@SACEXCMBX01-PRD.hq.netapp.com>
References: <CAHF4apMOpXohhWpYXB8X74yG4fBhcjVW0c=vNW4qXudJ7H92rA@mail.gmail.com> <9904FB1B0159DA42B0B887B7FA8119CA082E38@AZ-FFEXMB04.global.avaya.com> <CAHF4apN_94fp0VVrspjXFDTbfkusHY7e7usaNNgQ92Spaz_fgw@mail.gmail.com> <D4D47BCFFE5A004F95D707546AC0D7E91F6E5515@SACEXCMBX01-PRD.hq.netapp.com> <F03B546C-463B-4F01-A822-71B4E31668E6@gmail.com>
In-Reply-To: <F03B546C-463B-4F01-A822-71B4E31668E6@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.106.53.51]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <92E0933822030C42A4097DFC9A4BF065@tahoe.netapp.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "irtf-discuss@irtf.org" <irtf-discuss@irtf.org>, "eerg@listserv.netlab.nec.de" <eerg@listserv.netlab.nec.de>, Susan Hares <susan.hares@huawei.com>
Subject: Re: [irtf-discuss] [EERG] Request for a side-bar meeting in the IETF Orlando on Power-Aware Networking drafts
X-BeenThere: irtf-discuss@irtf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IRTF general and new-work discussion list <irtf-discuss.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/options/irtf-discuss>, <mailto:irtf-discuss-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/irtf-discuss>
List-Post: <mailto:irtf-discuss@irtf.org>
List-Help: <mailto:irtf-discuss-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/irtf-discuss>, <mailto:irtf-discuss-request@irtf.org?subject=subscribe>
X-List-Received-Date: Wed, 06 Feb 2013 12:22:35 -0000

Hi,

On Feb 6, 2013, at 13:08, Balaji Venkat <balajivenkat299@gmail.com> wrote:
> Tony li replied saying the RRG is in hibernation and that RRG will not me=
et in Orlando

it's in hibernation, but still looking for new topics, as far as I understa=
nd. So a pitch for looking into research related to energy savings in the r=
outing system could lead to something that would bring the RRG out of hiber=
nation.=20

It probably won't do so for Orlando, but you are very late with a room requ=
est for the Orlando meeting anyway.

Lars


From tony.li@tony.li  Wed Feb  6 08:56:30 2013
Return-Path: <tony.li@tony.li>
X-Original-To: irtf-discuss@ietfa.amsl.com
Delivered-To: irtf-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id ED7D021F844C for <irtf-discuss@ietfa.amsl.com>; Wed,  6 Feb 2013 08:56:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -99.638
X-Spam-Level: 
X-Spam-Status: No, score=-99.638 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_NET=0.611,  RDNS_NONE=0.1, SARE_SUB_RAND_LETTRS4=0.799, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id u3JaB+55zU-6 for <irtf-discuss@ietfa.amsl.com>; Wed,  6 Feb 2013 08:56:29 -0800 (PST)
Received: from qmta04.emeryville.ca.mail.comcast.net (qmta04.emeryville.ca.mail.comcast.net [IPv6:2001:558:fe2d:43:76:96:30:40]) by ietfa.amsl.com (Postfix) with ESMTP id 8B24521F8514 for <irtf-discuss@irtf.org>; Wed,  6 Feb 2013 08:56:21 -0800 (PST)
Received: from omta24.emeryville.ca.mail.comcast.net ([76.96.30.92]) by qmta04.emeryville.ca.mail.comcast.net with comcast id x4Hu1k0011zF43QA44wH96; Wed, 06 Feb 2013 16:56:17 +0000
Received: from [192.168.2.111] ([98.248.36.188]) by omta24.emeryville.ca.mail.comcast.net with comcast id x4wF1k00L43ZcXW8k4wG5M; Wed, 06 Feb 2013 16:56:17 +0000
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
From: Tony Li <tony.li@tony.li>
In-Reply-To: <D4D47BCFFE5A004F95D707546AC0D7E91F6E5ED0@SACEXCMBX01-PRD.hq.netapp.com>
Date: Wed, 6 Feb 2013 08:56:15 -0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <E4C5319E-DCBC-4DCE-AE3A-2AB0C61F2556@tony.li>
References: <CAHF4apMOpXohhWpYXB8X74yG4fBhcjVW0c=vNW4qXudJ7H92rA@mail.gmail.com> <9904FB1B0159DA42B0B887B7FA8119CA082E38@AZ-FFEXMB04.global.avaya.com> <CAHF4apN_94fp0VVrspjXFDTbfkusHY7e7usaNNgQ92Spaz_fgw@mail.gmail.com> <D4D47BCFFE5A004F95D707546AC0D7E91F6E5515@SACEXCMBX01-PRD.hq.netapp.com> <F03B546C-463B-4F01-A822-71B4E31668E6@gmail.com> <D4D47BCFFE5A004F95D707546AC0D7E91F6E5ED0@SACEXCMBX01-PRD.hq.netapp.com>
To: "Eggert, Lars" <lars@netapp.com>
X-Mailer: Apple Mail (2.1499)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20121106; t=1360169777; bh=yVpYSfq4IqXd3SXZKE6l9EttyoMdIpGpZeO4UzPfCWI=; h=Received:Received:Content-Type:Mime-Version:Subject:From:Date: Message-Id:To; b=mxgoIScf8i08IYv/3vj7gc/5BrJoiE4ulKsSSVXoPM1uNxNgK9ICwVNLbchLyQ/98 6MEdvD5MZyTXo9oGt3f4OZ2yIyqK4idteD2pr7YEyBkcl6sSHjOk8kFViVBSfg1Azl CNZe0Vd5OQ6SZKd+q7s2kLUQZ0MxEt2qsEkAqu5KTme21cny3USr1CHwP6YDuknl3i PJh7KCuj4R3pQNNuietUub/lKtnqaYBgklK+RZGPR9LCE+DXq/jkDktl/ViVvy80OA mLqD903XC3kOone0fNge8mikaQp+yEBzPWXl5L78qHVcixZizkkOM3OjVj7S+WLSn8 yT5sCWuj7s0Sg==
Cc: "irtf-discuss@irtf.org" <irtf-discuss@irtf.org>, "eerg@listserv.netlab.nec.de" <eerg@listserv.netlab.nec.de>, Susan Hares <susan.hares@huawei.com>
Subject: Re: [irtf-discuss] [EERG] Request for a side-bar meeting in the IETF Orlando on Power-Aware Networking drafts
X-BeenThere: irtf-discuss@irtf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IRTF general and new-work discussion list <irtf-discuss.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/options/irtf-discuss>, <mailto:irtf-discuss-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/irtf-discuss>
List-Post: <mailto:irtf-discuss@irtf.org>
List-Help: <mailto:irtf-discuss-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/irtf-discuss>, <mailto:irtf-discuss-request@irtf.org?subject=subscribe>
X-List-Received-Date: Wed, 06 Feb 2013 16:56:30 -0000

On Feb 6, 2013, at 4:22 AM, "Eggert, Lars" <lars@netapp.com> wrote:

> it's in hibernation, but still looking for new topics, as far as I =
understand. So a pitch for looking into research related to energy =
savings in the routing system could lead to something that would bring =
the RRG out of hibernation.=20


Yes, it's true that the RRG could be revived, but before we bring the =
RRG out of hibernation, there needs to be a sufficient community to pick =
up and carry on the work.  So far, I'm unaware of that community.

Regards,
Tony


From lars@netapp.com  Tue Feb 26 00:26:08 2013
Return-Path: <lars@netapp.com>
X-Original-To: irtf-discuss@ietfa.amsl.com
Delivered-To: irtf-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CB6EF21F88A0 for <irtf-discuss@ietfa.amsl.com>; Tue, 26 Feb 2013 00:26:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.801
X-Spam-Level: 
X-Spam-Status: No, score=-9.801 tagged_above=-999 required=5 tests=[AWL=-0.316, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, SARE_MILLIONSOF=0.315, SARE_SUB_RAND_LETTRS4=0.799]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cDrCTZBdgZlz for <irtf-discuss@ietfa.amsl.com>; Tue, 26 Feb 2013 00:26:08 -0800 (PST)
Received: from mx12.netapp.com (mx12.netapp.com [216.240.18.77]) by ietfa.amsl.com (Postfix) with ESMTP id 1FE8521F8895 for <irtf-discuss@irtf.org>; Tue, 26 Feb 2013 00:26:08 -0800 (PST)
X-IronPort-AV: E=Sophos;i="4.84,739,1355126400"; d="scan'208";a="26029296"
Received: from smtp1.corp.netapp.com ([10.57.156.124]) by mx12-out.netapp.com with ESMTP; 26 Feb 2013 00:26:08 -0800
Received: from vmwexceht04-prd.hq.netapp.com (vmwexceht04-prd.hq.netapp.com [10.106.77.34]) by smtp1.corp.netapp.com (8.13.1/8.13.1/NTAP-1.6) with ESMTP id r1Q8Q7tR017129 for <irtf-discuss@irtf.org>; Tue, 26 Feb 2013 00:26:08 -0800 (PST)
Received: from SACEXCMBX01-PRD.hq.netapp.com ([169.254.2.54]) by vmwexceht04-prd.hq.netapp.com ([10.106.77.34]) with mapi id 14.02.0328.009; Tue, 26 Feb 2013 00:26:07 -0800
From: "Eggert, Lars" <lars@netapp.com>
To: "irtf-discuss@irtf.org" <irtf-discuss@irtf.org>
Thread-Topic: [irtf-discuss] preliminary agenda for the IRTF Open Meeting in Vancouver
Thread-Index: AQHOE/rsAW3GIfohBk2rMKUFho/TOA==
Date: Tue, 26 Feb 2013 08:26:07 +0000
Message-ID: <D4D47BCFFE5A004F95D707546AC0D7E91F760129@SACEXCMBX01-PRD.hq.netapp.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.106.53.51]
Content-Type: text/plain; charset="Windows-1252"
Content-ID: <4E575690BC65C849A3553ED9AF680657@tahoe.netapp.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: [irtf-discuss] preliminary agenda for the IRTF Open Meeting in	Vancouver
X-BeenThere: irtf-discuss@irtf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IRTF general and new-work discussion list <irtf-discuss.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/options/irtf-discuss>, <mailto:irtf-discuss-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/irtf-discuss>
List-Post: <mailto:irtf-discuss@irtf.org>
List-Help: <mailto:irtf-discuss-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/irtf-discuss>, <mailto:irtf-discuss-request@irtf.org?subject=subscribe>
X-List-Received-Date: Tue, 26 Feb 2013 08:26:08 -0000

A preliminary agenda for the IRTF Open Meeting in Vancouver is now online: =
https://www.ietf.org/proceedings/86/agenda/agenda-86-irtfopen

Lars

--

Preliminary Agenda
IRTF Open Meeting @ IETF-86

1030-1130 Tuesday Morning Session II
Room Caribbean 5

Slot lengths below indicate presentation+discussion time.


State of the IRTF
    Lars Eggert
    10+5 min


Applied Networking Prize (ANRP) Award Talk
    30+15 min

    *** Gonca G=FCrsun *** for defining a metric that allows
    an analysis of BGP routing policies:

    Gonca G=FCrsun, Natali Ruchansky, Evimaria Terzi and Mark
    Crovella.  Routing State Distance: A Path-based Metric
    For Network Analysis.  Proc. ACM IMC, Boston, MA, USA,
    Nov. 2012.
    http://cs-people.bu.edu/goncag/papers/imc12-rsd.pdf

    The size and complexity of the millions of BGP paths in
    use at any time can hide important phenomena and hinder
    attempts to understand the path selection behavior of
    ASes. In this paper we introduce a new approach to
    analysis of the interdomain routing system designed to
    shed light on collective routing policies. Our approach
    starts by defining a new metric for =91distance=92 between
    prefixes, which we call routing state distance (RSD). We
    show that RSD has a number of properties that make it
    attractive for use in visualizing and analyzing the
    state of the BGP system.

