
From ietf-ipr@ietf.org  Thu Mar  7 14:34:52 2013
Return-Path: <ietf-ipr@ietf.org>
X-Original-To: rtgwg@ietfa.amsl.com
Delivered-To: rtgwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0537E21F8CF9; Thu,  7 Mar 2013 14:34:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.319
X-Spam-Level: 
X-Spam-Status: No, score=-102.319 tagged_above=-999 required=5 tests=[AWL=0.281, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BkM-kMXRCML6; Thu,  7 Mar 2013 14:34:51 -0800 (PST)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 6A3B321F8A6E; Thu,  7 Mar 2013 14:34:51 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: IETF Secretariat <ietf-ipr@ietf.org>
To: stbryant@cisco.com, cfilsfil@cisco.com, imc.shand@gmail.com, ning.so@tatacommunications.com, sprevidi@cisco.com
Subject: IPR Disclosure: Stewart Bryant's Statement about IPR related to draft-ietf-rtgwg-remote-lfa-01 belonging to Verizon
X-Test-IDTracker: no
X-IETF-IDTracker: 4.42
Message-ID: <20130307223451.2465.85222.idtracker@ietfa.amsl.com>
Date: Thu, 07 Mar 2013 14:34:51 -0800
Cc: adrian@olddog.co.uk, stbryant@cisco.com, ipr-announce@ietf.org, rtgwg@ietf.org
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Routing Area Working Group <rtgwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/rtgwg>
List-Post: <mailto:rtgwg@ietf.org>
List-Help: <mailto:rtgwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 07 Mar 2013 22:34:52 -0000

Dear Stewart Bryant, Clarence Filsfils, Mike Shand, So Ning, Stefano Previd=
i:

 An IPR disclosure that pertains to your Internet-Draft entitled "Remote LFA
FRR" (draft-ietf-rtgwg-remote-lfa) was submitted to the IETF Secretariat on
2013-03-06 and has been posted on the "IETF Page of Intellectual Property R=
ights
Disclosures" (https://datatracker.ietf.org/ipr/2009/). The title of the IPR
disclosure is "Stewart Bryant's Statement about IPR related to draft-ietf-r=
tgwg-
remote-lfa-01 belonging to Verizon."");

The IETF Secretariat


From akatlas@gmail.com  Sun Mar 10 12:59:17 2013
Return-Path: <akatlas@gmail.com>
X-Original-To: rtgwg@ietfa.amsl.com
Delivered-To: rtgwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1AD9321F88D1 for <rtgwg@ietfa.amsl.com>; Sun, 10 Mar 2013 12:59:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.633
X-Spam-Level: 
X-Spam-Status: No, score=-2.633 tagged_above=-999 required=5 tests=[AWL=-0.033, BAYES_00=-2.599, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fYa5uA+BU0A3 for <rtgwg@ietfa.amsl.com>; Sun, 10 Mar 2013 12:59:16 -0700 (PDT)
Received: from mail-ie0-x22e.google.com (mail-ie0-x22e.google.com [IPv6:2607:f8b0:4001:c03::22e]) by ietfa.amsl.com (Postfix) with ESMTP id 4C6F721F88CF for <rtgwg@ietf.org>; Sun, 10 Mar 2013 12:59:16 -0700 (PDT)
Received: by mail-ie0-f174.google.com with SMTP id k10so3880719iea.5 for <rtgwg@ietf.org>; Sun, 10 Mar 2013 12:59:15 -0700 (PDT)
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=ZBIPZQJZWm6vRy65753E4FAJ4hX43kIjDF9Ks/zHELM=; b=INdHaOz5bbllotgddVDmjeLwJdOdLOeIER+Zm4YLI42CAsVU3enuARC0rZAKnbstBU XHC+svUDf2zTvK38lO+DWy6U21hORSj4RpwW0aMNugKAymZHfLZgB/sZBNJX0TEQfENb zhwPv7lcB/lMM6cAVjJe6g0NsG8bOYYKEFbvSfKczAS9++mK4OoN73C9pwDUQw/ZB87F Xp4QOzvJxalwPSvNuJs+cxbknBgc4ZOETJIQqmrdyokxGiLIKGk3aa4UkeUXGzJ4FwYK U8ZgxOSGEYR+kIjj/YYlbyEJYYADa0Uwt6F1A+puQp80wmFthHLyLP4/OvGO8m6TAZpo YyeQ==
MIME-Version: 1.0
X-Received: by 10.43.4.74 with SMTP id ob10mr6799675icb.28.1362945555894; Sun, 10 Mar 2013 12:59:15 -0700 (PDT)
Received: by 10.64.44.169 with HTTP; Sun, 10 Mar 2013 12:59:15 -0700 (PDT)
Date: Sun, 10 Mar 2013 15:59:15 -0400
Message-ID: <CAG4d1rdCiNHE1LkHtto1H4hKMAWRjsNkvJBfYE3triqELr0SAw@mail.gmail.com>
Subject: remote participation and meetecho
From: Alia Atlas <akatlas@gmail.com>
To: rtgwg@ietf.org
Content-Type: text/plain; charset=ISO-8859-1
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Routing Area Working Group <rtgwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/rtgwg>
List-Post: <mailto:rtgwg@ietf.org>
List-Help: <mailto:rtgwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 10 Mar 2013 19:59:17 -0000

We have a meetecho session set-up for our meeting; the tutorial about how to use
meetecho is at: http://ietf86.conf.meetecho.com/index.php/Tutorials
We are still looking for a jabber scribe and minute taker.

Alia

From ietf@meetecho.com  Tue Mar 12 13:24:11 2013
Return-Path: <ietf@meetecho.com>
X-Original-To: rtgwg@ietfa.amsl.com
Delivered-To: rtgwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1691D11E81A4 for <rtgwg@ietfa.amsl.com>; Tue, 12 Mar 2013 13:24:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.655
X-Spam-Level: 
X-Spam-Status: No, score=-0.655 tagged_above=-999 required=5 tests=[AWL=0.064,  BAYES_00=-2.599, HELO_EQ_IT=0.635, HOST_EQ_IT=1.245]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BMv4bh0YVag4 for <rtgwg@ietfa.amsl.com>; Tue, 12 Mar 2013 13:24:10 -0700 (PDT)
Received: from smtpdg11.aruba.it (smtpdg6.aruba.it [62.149.158.236]) by ietfa.amsl.com (Postfix) with ESMTP id EAF4311E81A0 for <rtgwg@ietf.org>; Tue, 12 Mar 2013 13:24:06 -0700 (PDT)
Received: from dell-tcastaldi ([130.129.16.136]) by smtpcmd04.ad.aruba.it with bizsmtp id AkQ31l00g2w8SR601kQ5Cm; Tue, 12 Mar 2013 21:24:06 +0100
Date: Tue, 12 Mar 2013 16:24:01 -0400 (EDT)
From: Meetecho Team <ietf@meetecho.com>
To: rtgwg@ietf.org
Message-ID: <22611277.19.1363119841756.JavaMail.tcastaldi@dell-tcastaldi>
Subject: Meetecho support for RTGWG session
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="----=_Part_18_1133335.1363119841754"
X-Mailman-Approved-At: Tue, 12 Mar 2013 13:51:50 -0700
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Routing Area Working Group <rtgwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/rtgwg>
List-Post: <mailto:rtgwg@ietf.org>
List-Help: <mailto:rtgwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 12 Mar 2013 20:24:11 -0000

------=_Part_18_1133335.1363119841754
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Dear all,

a virtual room has been reserved on the Meetecho system for the 
RTGWG WG meeting session.
Access to the on-line session (including audio and video streams) will
be made available (just a couple of minutes before session start time) at:
http://www.meetecho.com/ietf86/rtgwg

The Meetecho session automatically logs you into the standard IETF
jabber room. So, from there, you can have an integrated experience
involving all media and allowing you to interact with the room.

A tutorial of interactivity features of the tool can be found at:
	http://www.meetecho.com/ietf86

Cheers,
the Meetecho Team


This email has been automatically generated by The Meetecho Conferencing System


------=_Part_18_1133335.1363119841754--

From aretana@cisco.com  Tue Mar 12 17:56:30 2013
Return-Path: <aretana@cisco.com>
X-Original-To: rtgwg@ietfa.amsl.com
Delivered-To: rtgwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 39BD021F8C71 for <rtgwg@ietfa.amsl.com>; Tue, 12 Mar 2013 17:56:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.598
X-Spam-Level: 
X-Spam-Status: No, score=-10.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zMx+bDkntwMU for <rtgwg@ietfa.amsl.com>; Tue, 12 Mar 2013 17:56:29 -0700 (PDT)
Received: from rcdn-iport-4.cisco.com (rcdn-iport-4.cisco.com [173.37.86.75]) by ietfa.amsl.com (Postfix) with ESMTP id CA35421F8B2B for <rtgwg@ietf.org>; Tue, 12 Mar 2013 17:56:28 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=6094; q=dns/txt; s=iport; t=1363136188; x=1364345788; h=from:to:subject:date:message-id:in-reply-to:mime-version; bh=0rf5MEAu0QE9zrt2sHbSDJQCwJ1QEGxJTwhV82krNLs=; b=KANaJQYaIaATq4J/jEPRRFMSbyTuwXTJrTikzdGi+ArqtsDd2JOyx6qi tS2kjcZVp8mNm15Oy644a10M2tPCN6fVwbSKkrbl2u70avqcvMv08kPfA aZrmNOfNCVi1VBdExfqEKvGsXw7TOEgrWBO6m94FcDzbZvYl+BGQ1sicu w=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AswKAG3OP1GtJV2b/2dsb2JhbABDhAmFKrtVgUwWbQeCKwEEgQsBCCILEjkUEQIEEwgBiAsMoE+TLY1EF41dfzgKglVhA5MRlDuCfQ2CKA
X-IronPort-AV: E=Sophos;i="4.84,833,1355097600";  d="scan'208,217";a="186836836"
Received: from rcdn-core-4.cisco.com ([173.37.93.155]) by rcdn-iport-4.cisco.com with ESMTP; 13 Mar 2013 00:56:14 +0000
Received: from xhc-rcd-x11.cisco.com (xhc-rcd-x11.cisco.com [173.37.183.85]) by rcdn-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id r2D0uE9I022001 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL) for <rtgwg@ietf.org>; Wed, 13 Mar 2013 00:56:14 GMT
Received: from xmb-aln-x15.cisco.com ([169.254.9.248]) by xhc-rcd-x11.cisco.com ([173.37.183.85]) with mapi id 14.02.0318.004; Tue, 12 Mar 2013 19:56:14 -0500
From: "Alvaro Retana (aretana)" <aretana@cisco.com>
To: "rtgwg@ietf.org" <rtgwg@ietf.org>
Subject: Re: rtgwg Agenda Posted (IETF 86)
Thread-Topic: rtgwg Agenda Posted (IETF 86)
Thread-Index: AQHOFERydNLhMqCDIkWR4pQqWXWpC5iiwQuA
Date: Wed, 13 Mar 2013 00:56:13 +0000
Message-ID: <BBD66FD99311804F80324E8139B3C94E11C89AE8@xmb-aln-x15.cisco.com>
In-Reply-To: <BBD66FD99311804F80324E8139B3C94ED8970B@xmb-aln-x15.cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.21.82.37]
Content-Type: multipart/alternative; boundary="_000_BBD66FD99311804F80324E8139B3C94E11C89AE8xmbalnx15ciscoc_"
MIME-Version: 1.0
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Routing Area Working Group <rtgwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/rtgwg>
List-Post: <mailto:rtgwg@ietf.org>
List-Help: <mailto:rtgwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 13 Mar 2013 00:56:30 -0000

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

Hi!

I have posted the slides we have so far.

Presenters:  Please send the missing slides..and check to make sure I got t=
he right version posted.

As mentioned below, we may change the order of the presentations based on s=
lide availability..  Given the tight agenda that could mean reduced time as=
 well.

Thanks!

Alvaro.

On 2/26/13 12:12 PM, "Alvaro Retana (aretana)" <aretana@cisco.com<mailto:ar=
etana@cisco.com>> wrote:

http://www.ietf.org/proceedings/86/agenda/agenda-86-rtgwg


As you can see, we have received a significant number of presentation reque=
sts and are out of time.

We will dedicate the second hour of the meeting to power-aware/energy-effic=
ient networking.  According to the WG's charter, rtgwg is the appropriate p=
lace to discuss topics that are not ready for their own WG/BOF and that are=
 related to routing.  Please be clear that this section of the meeting shou=
ld not be considered a BOF or side-meeting or any other such construct targ=
eted at potentially creating a WG.  The goal is to discuss the technology a=
nd potential work items, if any, that the WG may take on.  Ideally we would=
 reach agreement (pending discussion on the list, of course) on what the to=
pic covers, what may belong in the IETF at this time, and whether there is =
interest in doing any work.

We have asked all the presenters to start a discussion on the list about th=
eir drafts, pointing out the parts they would like the most feedback on.  T=
he intention is to both have an idea of the initial interest and for the co=
ntent to not be completely new at the in-person meeting, hopefully resultin=
g in better discussions.  Please take a look and make comments on line.

Note to presenters:  The time on the agenda includes presentation and discu=
ssion, so please plan accordingly.  Given that the WG meeting is scheduled =
for Wednesday, and taking other commitments into account, we MUST receive a=
ll presentations by the end of the day on Monday Mar/11 (pick your favorite=
 timezone).  The chairs MAY change the order of the presentations based on =
slide availability.

Thanks!

Alvaro.

--_000_BBD66FD99311804F80324E8139B3C94E11C89AE8xmbalnx15ciscoc_
Content-Type: text/html; charset="us-ascii"
Content-ID: <672341881B4EC34D82EBD987F67826BC@cisco.com>
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
</head>
<body style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-lin=
e-break: after-white-space; color: rgb(0, 0, 0); font-size: 14px; font-fami=
ly: Calibri, sans-serif; ">
<div>Hi!</div>
<div><br>
</div>
<div>I have posted the slides we have so far.</div>
<div><br>
</div>
<div>Presenters: &nbsp;Please send the missing slides..and check to make su=
re I got the right version posted.</div>
<div><br>
</div>
<div>As mentioned below, we may change the order of the presentations based=
 on slide availability.. &nbsp;Given the tight agenda that could mean reduc=
ed time as well.</div>
<div><br>
</div>
<div>Thanks!</div>
<div><br>
</div>
<div>Alvaro.</div>
<div><br>
</div>
<span id=3D"OLK_SRC_BODY_SECTION">
<div>
<div>On 2/26/13 12:12 PM, &quot;Alvaro Retana (aretana)&quot; &lt;<a href=
=3D"mailto:aretana@cisco.com">aretana@cisco.com</a>&gt; wrote:</div>
</div>
<div><br>
</div>
<blockquote id=3D"MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE" style=3D"BORDER-LEFT:=
 #b5c4df 5 solid; PADDING:0 0 0 5; MARGIN:0 0 0 5;">
<div>
<div style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line=
-break: after-white-space; color: rgb(0, 0, 0); font-size: 14px; font-famil=
y: Calibri, sans-serif; ">
<div><a href=3D"http://www.ietf.org/proceedings/86/agenda/agenda-86-rtgwg">=
http://www.ietf.org/proceedings/86/agenda/agenda-86-rtgwg</a></div>
<div><br>
</div>
<div><br>
</div>
<div>As you can see, we have received a significant number of presentation =
requests and are out of time.&nbsp;</div>
<div><br>
</div>
<div>
<div>We will dedicate the second hour of the meeting to power-aware/energy-=
efficient networking. &nbsp;According to the WG's charter, rtgwg is the app=
ropriate place to discuss topics that are not ready for their own WG/BOF an=
d that are related to routing. &nbsp;Please
 be clear that this section of the meeting should not be considered a BOF o=
r side-meeting or any other such construct targeted at potentially creating=
 a WG. &nbsp;The goal is to discuss the technology and potential work items=
, if any, that the WG may take on. &nbsp;Ideally
 we would reach agreement (pending discussion on the list, of course) on wh=
at the topic covers, what may belong in the IETF at this time, and whether =
there is interest in doing any work.</div>
</div>
<div><br>
</div>
<div>We have asked all the presenters to start a discussion on the list abo=
ut their drafts, pointing out the parts they would like the most feedback o=
n. &nbsp;The intention is to both have an idea of the initial interest and =
for the content to not be completely
 new at the in-person meeting, hopefully resulting in better discussions. &=
nbsp;Please take a look and make comments on line.</div>
<div><br>
</div>
<div>Note to presenters: &nbsp;The time on the agenda includes presentation=
 and discussion, so please plan accordingly. &nbsp;Given that the WG meetin=
g is scheduled for Wednesday, and taking other commitments into account, we=
 MUST receive all presentations by the end
 of the day on Monday Mar/11 (pick your favorite timezone). &nbsp;The chair=
s MAY change the order of the presentations based on slide availability.</d=
iv>
<div><br>
</div>
<div>Thanks!</div>
<div><br>
</div>
<div>Alvaro.</div>
</div>
</div>
</blockquote>
</span>
</body>
</html>

--_000_BBD66FD99311804F80324E8139B3C94E11C89AE8xmbalnx15ciscoc_--

From lucy.yong@huawei.com  Wed Mar 13 12:24:56 2013
Return-Path: <lucy.yong@huawei.com>
X-Original-To: rtgwg@ietfa.amsl.com
Delivered-To: rtgwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5296D21F8995 for <rtgwg@ietfa.amsl.com>; Wed, 13 Mar 2013 12:24:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.613
X-Spam-Level: 
X-Spam-Status: No, score=-6.613 tagged_above=-999 required=5 tests=[AWL=-0.015, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Lup6NoWaufjz for <rtgwg@ietfa.amsl.com>; Wed, 13 Mar 2013 12:24:55 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id D0AF521F8935 for <rtgwg@ietf.org>; Wed, 13 Mar 2013 12:24:54 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml204-edg.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.5-GA FastPath queued) with ESMTP id AQP51092; Wed, 13 Mar 2013 19:24:53 +0000 (GMT)
Received: from LHREML406-HUB.china.huawei.com (10.201.5.243) by lhreml204-edg.china.huawei.com (172.18.7.223) with Microsoft SMTP Server (TLS) id 14.1.323.7; Wed, 13 Mar 2013 19:24:20 +0000
Received: from DFWEML404-HUB.china.huawei.com (10.193.5.203) by lhreml406-hub.china.huawei.com (10.201.5.243) with Microsoft SMTP Server (TLS) id 14.1.323.7; Wed, 13 Mar 2013 19:24:52 +0000
Received: from DFWEML509-MBX.china.huawei.com ([169.254.11.122]) by dfweml404-hub.china.huawei.com ([10.193.5.203]) with mapi id 14.01.0323.007; Wed, 13 Mar 2013 12:24:05 -0700
From: Lucy yong <lucy.yong@huawei.com>
To: Alia Atlas <akatlas@gmail.com>, "rtgwg@ietf.org" <rtgwg@ietf.org>
Subject: RE: WGLC on draft-ietf-rtgwg-cl-requirements-09
Thread-Topic: WGLC on draft-ietf-rtgwg-cl-requirements-09
Thread-Index: AQHOEGt6gogRYpkHRUC+AEEAgOCAJpikHuhQ
Date: Wed, 13 Mar 2013 19:24:44 +0000
Message-ID: <2691CE0099834E4A9C5044EEC662BB9D452399E1@dfweml509-mbx.china.huawei.com>
References: <CAG4d1revx=f6+Oi1jvkCQDrwRy-2qmD2e2E+TJcm6QX2tf2KxQ@mail.gmail.com>
In-Reply-To: <CAG4d1revx=f6+Oi1jvkCQDrwRy-2qmD2e2E+TJcm6QX2tf2KxQ@mail.gmail.com>
Accept-Language: en-US, zh-CN
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.47.136.191]
Content-Type: multipart/alternative; boundary="_000_2691CE0099834E4A9C5044EEC662BB9D452399E1dfweml509mbxchi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Routing Area Working Group <rtgwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/rtgwg>
List-Post: <mailto:rtgwg@ietf.org>
List-Help: <mailto:rtgwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 13 Mar 2013 19:24:56 -0000

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

One comment as one of co-authors.

Suggest to change the title to "requirements for a composite link in MPLS n=
etwork". This will make consistent with the title in the framework doc.

Lucy

From: rtgwg-bounces@ietf.org [mailto:rtgwg-bounces@ietf.org] On Behalf Of A=
lia Atlas
Sent: Thursday, February 21, 2013 1:42 PM
To: rtgwg@ietf.org
Subject: WGLC on draft-ietf-rtgwg-cl-requirements-09

This is to start a working group last call on draft-ietf-rtgwg-cl-requireme=
nts-09.
The WGLC will conclude on March 15; extra time is given to include the IETF=
 meeting.

Please read and send comments.

Thanks,
Alia & Alvaro

--_000_2691CE0099834E4A9C5044EEC662BB9D452399E1dfweml509mbxchi_
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:SimSun;
	panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@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;}
@font-face
	{font-family:"\@SimSun";
	panose-1:2 1 6 0 3 1 1 1 1 1;}
/* 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;}
span.EmailStyle17
	{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.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></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">One comment as one of co-=
authors.<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">Suggest to change the tit=
le to &#8220;requirements for a composite link in MPLS network&#8221;. This=
 will make consistent with the title in the framework doc.<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">Lucy<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>
<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;"> rtgwg-bo=
unces@ietf.org [mailto:rtgwg-bounces@ietf.org]
<b>On Behalf Of </b>Alia Atlas<br>
<b>Sent:</b> Thursday, February 21, 2013 1:42 PM<br>
<b>To:</b> rtgwg@ietf.org<br>
<b>Subject:</b> WGLC on draft-ietf-rtgwg-cl-requirements-09<o:p></o:p></spa=
n></p>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">This is to start a working group last call on draft-=
ietf-rtgwg-cl-requirements-09.<o:p></o:p></p>
<div>
<p class=3D"MsoNormal">The WGLC will conclude on March 15; extra time is gi=
ven to include the IETF meeting.<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">Please read and send comments.<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">Thanks,<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal">Alia &amp; Alvaro<o:p></o:p></p>
</div>
</div>
</div>
</body>
</html>

--_000_2691CE0099834E4A9C5044EEC662BB9D452399E1dfweml509mbxchi_--

From ietf@meetecho.com  Wed Mar 13 17:17:46 2013
Return-Path: <ietf@meetecho.com>
X-Original-To: rtgwg@ietfa.amsl.com
Delivered-To: rtgwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 938E621F8D39 for <rtgwg@ietfa.amsl.com>; Wed, 13 Mar 2013 17:17:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.513
X-Spam-Level: 
X-Spam-Status: No, score=-0.513 tagged_above=-999 required=5 tests=[AWL=-0.100, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_EQ_IT=0.635, RDNS_NONE=0.1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ORaFD4iwvt36 for <rtgwg@ietfa.amsl.com>; Wed, 13 Mar 2013 17:17:45 -0700 (PDT)
Received: from smtpdg8.aruba.it (unknown [62.149.158.226]) by ietfa.amsl.com (Postfix) with ESMTP id 5D46721F8D3A for <rtgwg@ietf.org>; Wed, 13 Mar 2013 17:17:43 -0700 (PDT)
Received: from dell-tcastaldi ([130.129.16.136]) by smtpcmd03.ad.aruba.it with bizsmtp id BCHd1l00J2w8SR601CHfa1; Thu, 14 Mar 2013 01:17:40 +0100
Date: Wed, 13 Mar 2013 20:17:35 -0400 (EDT)
From: Meetecho Team <ietf@meetecho.com>
To: rtgwg@ietf.org
Message-ID: <13238549.1.1363220255070.JavaMail.tcastaldi@dell-tcastaldi>
Subject: RTGWG session recording available
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="----=_Part_0_12423818.1363220255024"
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Routing Area Working Group <rtgwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/rtgwg>
List-Post: <mailto:rtgwg@ietf.org>
List-Help: <mailto:rtgwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 14 Mar 2013 00:17:47 -0000

------=_Part_0_12423818.1363220255024
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Dear all,

the full recording (synchronized video, audio, slides and jabber room) of the 
RTGWG WG session at IETF 86 is available at the following URL:
http://ietf86.conf.meetecho.com/index.php/Recorded_Sessions#RTGWG

In case of problems with the playout, just drop an e-mail to ietf-support@meetecho.com.

For the chair(s): please feel free to put the link to the recording in the minutes,
if you think this might be useful.

Cheers,
the Meetecho Team


This email has been automatically generated by The Meetecho Conferencing System


------=_Part_0_12423818.1363220255024--

From wwwrun@rfc-editor.org  Thu Mar 21 00:01:38 2013
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: rtgwg@ietfa.amsl.com
Delivered-To: rtgwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2CE4A21F8FDD for <rtgwg@ietfa.amsl.com>; Thu, 21 Mar 2013 00:01:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.6
X-Spam-Level: 
X-Spam-Status: No, score=-102.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vKThDxpr0r6a for <rtgwg@ietfa.amsl.com>; Thu, 21 Mar 2013 00:01:37 -0700 (PDT)
Received: from rfc-editor.org (unknown [IPv6:2001:1890:123a::1:2f]) by ietfa.amsl.com (Postfix) with ESMTP id 71BAD21F8F13 for <rtgwg@ietf.org>; Thu, 21 Mar 2013 00:01:37 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 7FB26B1E008; Thu, 21 Mar 2013 00:01:22 -0700 (PDT)
To: cf@cisco.com, pierre.francois@imdea.org, imc.shand@googlemail.com, bruno.decraene@orange.com, uttaro@att.com, N.Leymann@telekom.de, Martin.Horneffer@telekom.de, stbryant@cisco.com, adrian@olddog.co.uk, aretana@cisco.com, akatlas@gmail.com
Subject: [Technical Errata Reported] RFC6571 (3561)
From: RFC Errata System <rfc-editor@rfc-editor.org>
Message-Id: <20130321070126.7FB26B1E008@rfc-editor.org>
Date: Thu, 21 Mar 2013 00:01:22 -0700 (PDT)
Cc: rfc-editor@rfc-editor.org, rozic@hawaii.edu, rtgwg@ietf.org
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Routing Area Working Group <rtgwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/rtgwg>
List-Post: <mailto:rtgwg@ietf.org>
List-Help: <mailto:rtgwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 21 Mar 2013 07:01:38 -0000

The following errata report has been submitted for RFC6571,
"Loop-Free Alternate (LFA) Applicability in Service Provider (SP) Networks".

--------------------------------------
You may review the report below and at:
http://www.rfc-editor.org/errata_search.php?rfc=6571&eid=3561

--------------------------------------
Type: Technical
Reported by: Ciril Rozic <rozic@hawaii.edu>

Section: 3.1.1.1

Original Text
-------------
The LFA to P is via C2, because c < d + u.  It is node-protecting if
   eq2: x + e < x + c, i.e., if e < c.

Corrected Text
--------------
The LFA to P is via C2 if x + e < d + u + x.   It is node-protecting if
   eq2: x + e < c + x, i.e., if e < c.

Notes
-----
The condition for the first sentence e < d + u is not stated in the assumptions in Section 3.

The second sentence is not incorrect, but "c + x" is more consistent with eq1 in Section 2.

Instructions:
-------------
This errata is currently posted as "Reported". If necessary, please
use "Reply All" to discuss whether it should be verified or
rejected. When a decision is reached, the verifying party (IESG)
can log in to change the status and edit the report, if necessary. 

--------------------------------------
RFC6571 (draft-ietf-rtgwg-lfa-applicability-06)
--------------------------------------
Title               : Loop-Free Alternate (LFA) Applicability in Service Provider (SP) Networks
Publication Date    : June 2012
Author(s)           : C. Filsfils, Ed., P. Francois, Ed., M. Shand, B. Decraene, J. Uttaro, N. Leymann, M. Horneffer
Category            : INFORMATIONAL
Source              : Routing Area Working Group
Area                : Routing
Stream              : IETF
Verifying Party     : IESG

From curtis@occnc.com  Thu Mar 21 18:51:47 2013
Return-Path: <curtis@occnc.com>
X-Original-To: rtgwg@ietfa.amsl.com
Delivered-To: rtgwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 45C0C21F8DDC for <rtgwg@ietfa.amsl.com>; Thu, 21 Mar 2013 18:51:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.345
X-Spam-Level: 
X-Spam-Status: No, score=-0.345 tagged_above=-999 required=5 tests=[AWL=0.150,  BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553,  RDNS_NONE=0.1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hfGWvtV3RSTm for <rtgwg@ietfa.amsl.com>; Thu, 21 Mar 2013 18:51:44 -0700 (PDT)
Received: from gateway1.orleans.occnc.com (unknown [173.9.106.132]) by ietfa.amsl.com (Postfix) with ESMTP id 723DD21F8DD9 for <rtgwg@ietf.org>; Thu, 21 Mar 2013 18:51:42 -0700 (PDT)
Received: from harbor1.ipv6.occnc.com (harbor1.ipv6.occnc.com [IPv6:2001:470:1f07:1545::2:819]) (authenticated bits=0) by gateway1.orleans.occnc.com (8.14.5/8.14.5) with ESMTP id r2M1oPxS020663; Thu, 21 Mar 2013 21:50:25 -0400 (EDT) (envelope-from curtis@occnc.com)
Message-Id: <201303220150.r2M1oPxS020663@gateway1.orleans.occnc.com>
To: "Alvaro Retana (aretana)" <aretana@cisco.com>
From: Curtis Villamizar <curtis@occnc.com>
Subject: Re: FW: I-D Action: draft-retana-rtgwg-eacp-01.txt
In-reply-to: Your message of "Wed, 13 Feb 2013 15:52:52 GMT." <BBD66FD99311804F80324E8139B3C94ED5B183@xmb-aln-x15.cisco.com>
Date: Thu, 21 Mar 2013 21:50:24 -0400
Cc: "rtgwg@ietf.org" <rtgwg@ietf.org>
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: curtis@occnc.com
List-Id: Routing Area Working Group <rtgwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/rtgwg>
List-Post: <mailto:rtgwg@ietf.org>
List-Help: <mailto:rtgwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 22 Mar 2013 01:51:47 -0000

Alvaro,

I'm not sure what it means to put a OTN interface in a "low power
state".  OTN and SONET interfaces are a continuous stream of bits at a
constant rate dictated by the ITU-T.  The rate is not adjustable.  It
doesn't save any power by sending GFP null frames over OTN links.

Since most long haul router to router links are Ethenet across the
room, followed by long stretches of OTN, there may be no significant
benefit to putting the short Ethernet into lower power mode.  Plus as
discussed at IETF-86, the Ethernet low power mode applies only to
copper Ethernet (10/100 Mb/s, 1 Gb/s copper) and not to the fiber
forms of Ethernt used by providers.

So before anyone writes any more problem statements, requirements,
frameworks, or complete solutions for energy aware networks, we need
to have some research and some hard facts about where energy goes and
where there are opportunities to save energy.  We also should be
asking whether providers and high end network equipment vendors see a
need for any protocol work in this area.  So far the answer is a
resounding "no".

It is also worth pointing out that research so far has indicated that
the greatest total savings is the furthest down the food chain at or
near the customer network.  So the low power Ethernet applied to the
10/100/1000 copper used in homes and small business makes a lot of
sense.  IETF may not be the right place to attack the next layer up
the food chain, things like CMTS to CM (cable modem termination
systems to cable modem) or DSL efficiencies.

Curtis


In message <BBD66FD99311804F80324E8139B3C94ED5B183@xmb-aln-x15.cisco.com>
"Alvaro Retana (aretana)" writes:

[Chair hat off.]

Hi!

We just published an update (a refresh really) of the draft below.

The draft is NOT a set of requirements to be solved in the realm of power
aware/energy efficient networking.  We are not trying to define
requirements on how to save energy, how much energy should be saved, how,
when or where.  Nor are we recommending any specific solution.

So, what is it? ;-)   The intent of the draft is to "provide the tools and
knowledge necessary for protocol designers to modify network protocols to
best balance efficiency against performance, and to provide the background
   information network operators will need to intelligently deploy and use
protocol modifications to network protocols."

In other words..  We recognize that saving energy may be in many people's
minds, but we also recognize that networks have been designed/deployed
with a set of business (availability, ability to satisfy customer SLAs,
for example) and application (min bw, jitter/delay budgets, for instance)
requirements in mind, which need to still be satisfied even while saving
energy.

The draft goes on to evaluate considerations derived from the
business/application requirements that may be affected by applying common
methods of reducing energy (reducing the topology or reducing the link
speed, for example):  bw reduction, stretch, fast recovery, introducing
jitter and other operational aspects.

As an example, we mention (section 5.1) that eliminating links from the
topology (shutting them down or putting them in a "low power state")
should result in lower energy utilization..but that it will also affect
the total available bw in the network.  The requirement then comes in in
the form of "Modifications to control plane protocols to achieve network
energy efficiency SHOULD provide the ability to set the minimal bandwidth,
   jitter, and delay through the network".  I'll leave you to read some of
the other examples/considerations and requirements.

The end result of the draft is the definition of a framework against which
we can evaluate "the tradeoffs between modifications made to network
protocols to conserve energy and network performance metrics and
requirements".

Thanks!

Alvaro.


On 2/13/13 10:18 AM, "internet-drafts@ietf.org" <internet-drafts@ietf.org>
wrote:

>
>A New Internet-Draft is available from the on-line Internet-Drafts
>directories.
>
>
>	Title           : A Framework and Requirements for Energy Aware Control
>Planes
>	Author(s)       : Alvaro Retana
>                          Russ White
>                          Manuel Paul
>	Filename        : draft-retana-rtgwg-eacp-01.txt
>	Pages           : 16
>	Date            : 2013-02-13
>
>Abstract:
>   There has been, for several years, a rising concern over the energy
>   usage of large scale networks.  This concern is strongly focused on
>   campus, data center, and other highly concentrated deployments of
>   network infrastructure.  Given the steadily increasing demand for
>   higher network speeds, always-on service models, and ubiquitous
>   network coverage, it is also of growing importance for
>   telecommunication networks both local and wide area in scope.  One of
>   the issues in moving forward to reduce energy usage is to ensure that
>   the network can still meet the performance specifications required to
>   support the applications running over it.
>
>   This document provides an overview of the various areas of concern in
>   the interaction between network performance and efforts at energy
>   aware control planes, as a guide for those working on modifying
>   current control planes or designing new control planes to improve the
>   energy efficiency of high density, highly complex, network
>   deployments.
>
>
>The IETF datatracker status page for this draft is:
>https://datatracker.ietf.org/doc/draft-retana-rtgwg-eacp
>
>There's also a htmlized version available at:
>http://tools.ietf.org/html/draft-retana-rtgwg-eacp-01
>
>A diff from the previous version is available at:
>http://www.ietf.org/rfcdiff?url2=draft-retana-rtgwg-eacp-01
>
>
>Internet-Drafts are also available by anonymous FTP at:
>ftp://ftp.ietf.org/internet-drafts/
>
>_______________________________________________
>I-D-Announce mailing list
>I-D-Announce@ietf.org
>https://www.ietf.org/mailman/listinfo/i-d-announce
>Internet-Draft directories: http://www.ietf.org/shadow.html
>or ftp://ftp.ietf.org/ietf/1shadow-sites.txt

_______________________________________________
rtgwg mailing list
rtgwg@ietf.org
https://www.ietf.org/mailman/listinfo/rtgwg

From internet-drafts@ietf.org  Fri Mar 22 20:56:39 2013
Return-Path: <internet-drafts@ietf.org>
X-Original-To: rtgwg@ietfa.amsl.com
Delivered-To: rtgwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4D33421F90B3; Fri, 22 Mar 2013 20:56:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.488
X-Spam-Level: 
X-Spam-Status: No, score=-102.488 tagged_above=-999 required=5 tests=[AWL=0.112, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NXR3ASWArN+A; Fri, 22 Mar 2013 20:56:38 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id D37C421F8FCD; Fri, 22 Mar 2013 20:56:23 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
Subject: I-D Action: draft-ietf-rtgwg-cl-requirement-10.txt
X-Test-IDTracker: no
X-IETF-IDTracker: 4.43
Message-ID: <20130323035623.15730.24123.idtracker@ietfa.amsl.com>
Date: Fri, 22 Mar 2013 20:56:23 -0700
Cc: rtgwg@ietf.org
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Routing Area Working Group <rtgwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/rtgwg>
List-Post: <mailto:rtgwg@ietf.org>
List-Help: <mailto:rtgwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 23 Mar 2013 03:56:39 -0000

A New Internet-Draft is available from the on-line Internet-Drafts director=
ies.
 This draft is a work item of the Routing Area Working Group Working Group =
of the IETF.

	Title           : Requirements for Composite Links in MPLS Networks
	Author(s)       : Curtis Villamizar
                          Dave McDysan
                          So Ning
                          Andrew Malis
                          Lucy Yong
	Filename        : draft-ietf-rtgwg-cl-requirement-10.txt
	Pages           : 16
	Date            : 2013-03-22

Abstract:
   There is often a need to provide large aggregates of bandwidth that
   are best provided using parallel links between routers or MPLS LSR.
   In core networks there is often no alternative since the aggregate
   capacities of core networks today far exceed the capacity of a single
   physical link or single packet processing element.

   The presence of parallel links, with each link potentially comprised
   of multiple layers has resulted in additional requirements.  Certain
   services may benefit from being restricted to a subset of the
   component links or a specific component link, where component link
   characteristics, such as latency, differ.  Certain services require
   that an LSP be treated as atomic and avoid reordering.  Other
   services will continue to require only that reordering not occur
   within a microflow as is current practice.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-rtgwg-cl-requirement

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-ietf-rtgwg-cl-requirement-10

A diff from the previous version is available at:
http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-rtgwg-cl-requirement-10


Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/


From curtis@occnc.com  Fri Mar 22 21:01:43 2013
Return-Path: <curtis@occnc.com>
X-Original-To: rtgwg@ietfa.amsl.com
Delivered-To: rtgwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A9E4121F8FCD for <rtgwg@ietfa.amsl.com>; Fri, 22 Mar 2013 21:01:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.435
X-Spam-Level: 
X-Spam-Status: No, score=-0.435 tagged_above=-999 required=5 tests=[AWL=0.060,  BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553,  RDNS_NONE=0.1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xaByMQFWzCYn for <rtgwg@ietfa.amsl.com>; Fri, 22 Mar 2013 21:01:43 -0700 (PDT)
Received: from gateway1.orleans.occnc.com (unknown [173.9.106.132]) by ietfa.amsl.com (Postfix) with ESMTP id 1793221F8FB0 for <rtgwg@ietf.org>; Fri, 22 Mar 2013 21:01:42 -0700 (PDT)
Received: from harbor1.ipv6.occnc.com (harbor1.ipv6.occnc.com [IPv6:2001:470:1f07:1545::2:819]) (authenticated bits=0) by gateway1.orleans.occnc.com (8.14.5/8.14.5) with ESMTP id r2N3wj7S041055; Fri, 22 Mar 2013 23:58:45 -0400 (EDT) (envelope-from curtis@occnc.com)
Message-Id: <201303230358.r2N3wj7S041055@gateway1.orleans.occnc.com>
To: Lucy yong <lucy.yong@huawei.com>
From: Curtis Villamizar <curtis@occnc.com>
Subject: Re: WGLC on draft-ietf-rtgwg-cl-requirements-09
In-reply-to: Your message of "Wed, 13 Mar 2013 19:24:44 -0000." <2691CE0099834E4A9C5044EEC662BB9D452399E1@dfweml509-mbx.china.huawei.com>
Date: Fri, 22 Mar 2013 23:58:45 -0400
Cc: "rtgwg@ietf.org" <rtgwg@ietf.org>
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: curtis@occnc.com
List-Id: Routing Area Working Group <rtgwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/rtgwg>
List-Post: <mailto:rtgwg@ietf.org>
List-Help: <mailto:rtgwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 23 Mar 2013 04:01:43 -0000

In message <2691CE0099834E4A9C5044EEC662BB9D452399E1@dfweml509-mbx.china.huawei.com>
Lucy yong writes:
 
> One comment as one of co-authors.
>  
> Suggest to change the title to "requirements for a composite link in
> MPLS network". This will make consistent with the title in the
> framework doc.
>  
> Lucy
>  
> From: rtgwg-bounces@ietf.org [mailto:rtgwg-bounces@ietf.org] On Behalf Of Alia Atlas
> Sent: Thursday, February 21, 2013 1:42 PM
> To: rtgwg@ietf.org
> Subject: WGLC on draft-ietf-rtgwg-cl-requirements-09
>  
> This is to start a working group last call on
> draft-ietf-rtgwg-cl-requirements-09.  The WGLC will conclude on March
> 15; extra time is given to include the IETF meeting.
>  
> Please read and send comments.
>  
> Thanks,
> Alia & Alvaro



Lucy,

This is the second and only remaining comment in the last call.  Sorry
I missed replying to this.  The request is to change the title.  If
you don't mind making CLs and networks plural in the title then:

  OLD

    Requirements for MPLS Over a Composite Link

  NEW

    Requirements for Composite Links in MPLS Networks

I just made this change since it seems non-controversial and it seems
to me to be a better title.

The only other change was requested by Alia and that was removing the
sentence "Current practice related to multipath is described briefly
in an appendix." from the abstract (that appendix is now in the use
cases document).

draft-ietf-rtgwg-cl-requirement-10 has been posted.

If there are no objections to the title change, then the WG chairs can
conclude the last call.

Curtis

From russw@riw.us  Sat Mar 23 07:37:19 2013
Return-Path: <russw@riw.us>
X-Original-To: rtgwg@ietfa.amsl.com
Delivered-To: rtgwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5B70021F8A5E for <rtgwg@ietfa.amsl.com>; Sat, 23 Mar 2013 07:37:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zNfiUYIs9+Yl for <rtgwg@ietfa.amsl.com>; Sat, 23 Mar 2013 07:37:18 -0700 (PDT)
Received: from da31.namelessnet.net (da31.namelessnet.net [74.124.205.66]) by ietfa.amsl.com (Postfix) with ESMTP id AEA5621F8972 for <rtgwg@ietf.org>; Sat, 23 Mar 2013 07:37:12 -0700 (PDT)
Received: from cpe-098-122-147-095.nc.res.rr.com ([98.122.147.95] helo=[192.168.100.52]) by da31.namelessnet.net with esmtpa (Exim 4.80) (envelope-from <russw@riw.us>) id 1UJPZI-0005ur-Im for rtgwg@ietf.org; Sat, 23 Mar 2013 07:37:12 -0700
Message-ID: <514DBE23.4040108@riw.us>
Date: Sat, 23 Mar 2013 10:37:23 -0400
From: Russ White <russw@riw.us>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130307 Thunderbird/17.0.4
MIME-Version: 1.0
To: rtgwg@ietf.org
Subject: Re: FW: I-D Action: draft-retana-rtgwg-eacp-01.txt
References: <201303220150.r2M1oPxS020663@gateway1.orleans.occnc.com>
In-Reply-To: <201303220150.r2M1oPxS020663@gateway1.orleans.occnc.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Antivirus-Scanner: Seems clean.  You should still use an Antivirus Scanner
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Routing Area Working Group <rtgwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/rtgwg>
List-Post: <mailto:rtgwg@ietf.org>
List-Help: <mailto:rtgwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 23 Mar 2013 14:37:19 -0000

> So before anyone writes any more problem statements, requirements,
> frameworks, or complete solutions for energy aware networks, we need
> to have some research and some hard facts about where energy goes and
> where there are opportunities to save energy.  We also should be
> asking whether providers and high end network equipment vendors see a
> need for any protocol work in this area.  So far the answer is a
> resounding "no".

I actually disagree...

The point of this draft is to guide the research into what would make
sense and what wouldn't, not to make a definitive statement. I
understand the perspective that, "if it doesn't save x amount of power,
it's not worth doing..."

But technology changes, after all, and in just a few short years the
answer to that question might well change. So, if we come to the point
where the answer changes, how have we defined the question?

This draft is about defining the questions that need to be asked, not
about doing work in answering those questions.

Different topic, IMHO.

:-)

Russ



From curtis@occnc.com  Sat Mar 23 09:24:59 2013
Return-Path: <curtis@occnc.com>
X-Original-To: rtgwg@ietfa.amsl.com
Delivered-To: rtgwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4512D21F8867 for <rtgwg@ietfa.amsl.com>; Sat, 23 Mar 2013 09:24:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.445
X-Spam-Level: 
X-Spam-Status: No, score=-0.445 tagged_above=-999 required=5 tests=[AWL=0.050,  BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553,  RDNS_NONE=0.1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ngTlDbTPJK6j for <rtgwg@ietfa.amsl.com>; Sat, 23 Mar 2013 09:24:58 -0700 (PDT)
Received: from gateway1.orleans.occnc.com (unknown [173.9.106.132]) by ietfa.amsl.com (Postfix) with ESMTP id AA53F21F884A for <rtgwg@ietf.org>; Sat, 23 Mar 2013 09:24:58 -0700 (PDT)
Received: from harbor1.ipv6.occnc.com (harbor1.ipv6.occnc.com [IPv6:2001:470:1f07:1545::2:819]) (authenticated bits=0) by gateway1.orleans.occnc.com (8.14.5/8.14.5) with ESMTP id r2NGNgpt046392; Sat, 23 Mar 2013 12:23:42 -0400 (EDT) (envelope-from curtis@occnc.com)
Message-Id: <201303231623.r2NGNgpt046392@gateway1.orleans.occnc.com>
To: Russ White <russw@riw.us>
From: Curtis Villamizar <curtis@occnc.com>
Subject: Re: FW: I-D Action: draft-retana-rtgwg-eacp-01.txt
In-reply-to: Your message of "Sat, 23 Mar 2013 10:37:23 EDT." <514DBE23.4040108@riw.us>
Date: Sat, 23 Mar 2013 12:23:42 -0400
Cc: rtgwg@ietf.org
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: curtis@occnc.com
List-Id: Routing Area Working Group <rtgwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/rtgwg>
List-Post: <mailto:rtgwg@ietf.org>
List-Help: <mailto:rtgwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 23 Mar 2013 16:24:59 -0000

In message <514DBE23.4040108@riw.us>
Russ White writes:
 
>  
> > So before anyone writes any more problem statements, requirements,
> > frameworks, or complete solutions for energy aware networks, we need
> > to have some research and some hard facts about where energy goes and
> > where there are opportunities to save energy.  We also should be
> > asking whether providers and high end network equipment vendors see a
> > need for any protocol work in this area.  So far the answer is a
> > resounding "no".
>  
> I actually disagree...
>  
> The point of this draft is to guide the research into what would make
> sense and what wouldn't, not to make a definitive statement. I
> understand the perspective that, "if it doesn't save x amount of power,
> it's not worth doing..."
>  
> But technology changes, after all, and in just a few short years the
> answer to that question might well change. So, if we come to the point
> where the answer changes, how have we defined the question?
>  
> This draft is about defining the questions that need to be asked, not
> about doing work in answering those questions.
>  
> Different topic, IMHO.
>  
> :-)
>  
> Russ


Russ,

If our starting point is total cluelessness, then defining a taxonomy
of the solution space would be very counterproductive.

Stretch and microsleeps are solution space and I'd argue that the best
solutions for core may involve neither.  There is no highly credible
evidence that either has an impact on core network energy usage and
IMO stronger arguments that it would have no effect or infeasible
(microsleeping finely tuned temperature compensated colored lasers?)
than the the very weak arguments (mostly speculation) that there is
benefits to these two approaches for core.

So the research happen where it belongs - elsewhere.  Then when there
is credible research presented, it might be time to consider a
taxonomy of the problem and solution space in an SDO.

Curtis

From russw@riw.us  Sat Mar 23 10:44:52 2013
Return-Path: <russw@riw.us>
X-Original-To: rtgwg@ietfa.amsl.com
Delivered-To: rtgwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 61E0E21F888B for <rtgwg@ietfa.amsl.com>; Sat, 23 Mar 2013 10:44:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HWSqBRx3B9Cq for <rtgwg@ietfa.amsl.com>; Sat, 23 Mar 2013 10:44:51 -0700 (PDT)
Received: from da31.namelessnet.net (da31.namelessnet.net [74.124.205.66]) by ietfa.amsl.com (Postfix) with ESMTP id B176A21F8867 for <rtgwg@ietf.org>; Sat, 23 Mar 2013 10:44:51 -0700 (PDT)
Received: from cpe-098-122-147-095.nc.res.rr.com ([98.122.147.95] helo=[192.168.100.75]) by da31.namelessnet.net with esmtpa (Exim 4.80) (envelope-from <russw@riw.us>) id 1UJSUs-0006Mp-S8; Sat, 23 Mar 2013 10:44:50 -0700
Message-ID: <514DEA1E.2090008@riw.us>
Date: Sat, 23 Mar 2013 13:45:02 -0400
From: Russ White <russw@riw.us>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130307 Thunderbird/17.0.4
MIME-Version: 1.0
To: curtis@occnc.com
Subject: Re: FW: I-D Action: draft-retana-rtgwg-eacp-01.txt
References: <201303231623.r2NGNgpt046392@gateway1.orleans.occnc.com>
In-Reply-To: <201303231623.r2NGNgpt046392@gateway1.orleans.occnc.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Antivirus-Scanner: Seems clean.  You should still use an Antivirus Scanner
Cc: rtgwg@ietf.org
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Routing Area Working Group <rtgwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/rtgwg>
List-Post: <mailto:rtgwg@ietf.org>
List-Help: <mailto:rtgwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 23 Mar 2013 17:44:52 -0000

> Stretch and microsleeps are solution space and I'd argue that the best
> solutions for core may involve neither.  There is no highly credible
> evidence that either has an impact on core network energy usage and
> IMO stronger arguments that it would have no effect or infeasible
> (microsleeping finely tuned temperature compensated colored lasers?)
> than the the very weak arguments (mostly speculation) that there is
> benefits to these two approaches for core.

No, stretch and sleep states are not "in the solution space." If you're
going to save energy by using sleep states, then you need to deal with
state. These are bars any given design must overcome, not suggestions
for a design that would work.

> So the research happen where it belongs - elsewhere.  Then when there
> is credible research presented, it might be time to consider a
> taxonomy of the problem and solution space in an SDO.

So your basic argument is --"we should only consider this when it's
proven to be economically viable." My counter to that is simple:

There's more to this game than saving more than x$/year. There's also
the impact on the control plane to consider as a "cost."

This draft is an attempt to at least point those costs out in a
reasonable and understandable way. In other words, it's trying to get
all the requirements on the table, rather than focusing myopically on
the economic costs.

Again, it's answering a completely different question than you're asking.

Russ


From lucy.yong@huawei.com  Sun Mar 24 14:01:41 2013
Return-Path: <lucy.yong@huawei.com>
X-Original-To: rtgwg@ietfa.amsl.com
Delivered-To: rtgwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 918DB21F8DC5 for <rtgwg@ietfa.amsl.com>; Sun, 24 Mar 2013 14:01:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id x+wZZ7pMfDD1 for <rtgwg@ietfa.amsl.com>; Sun, 24 Mar 2013 14:01:39 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id 647B021F8DC0 for <rtgwg@ietf.org>; Sun, 24 Mar 2013 14:01:39 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml203-edg.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.5-GA FastPath queued) with ESMTP id APT06815; Sun, 24 Mar 2013 21:01:23 +0000 (GMT)
Received: from LHREML402-HUB.china.huawei.com (10.201.5.241) by lhreml203-edg.huawei.com (172.18.7.221) with Microsoft SMTP Server (TLS) id 14.1.323.7; Sun, 24 Mar 2013 21:01:08 +0000
Received: from DFWEML407-HUB.china.huawei.com (10.193.5.132) by lhreml402-hub.china.huawei.com (10.201.5.241) with Microsoft SMTP Server (TLS) id 14.1.323.7; Sun, 24 Mar 2013 21:01:18 +0000
Received: from DFWEML509-MBX.china.huawei.com ([169.254.11.122]) by dfweml407-hub.china.huawei.com ([10.193.5.132]) with mapi id 14.01.0323.007; Sun, 24 Mar 2013 14:01:11 -0700
From: Lucy yong <lucy.yong@huawei.com>
To: "curtis@occnc.com" <curtis@occnc.com>
Subject: RE: WGLC on draft-ietf-rtgwg-cl-requirements-09
Thread-Topic: WGLC on draft-ietf-rtgwg-cl-requirements-09
Thread-Index: AQHOJ3r4z04Ma4ODEUerEX2nGrJBcJi1VfgA
Date: Sun, 24 Mar 2013 21:01:11 +0000
Message-ID: <2691CE0099834E4A9C5044EEC662BB9D4523CFBD@dfweml509-mbx.china.huawei.com>
References: Your message of "Wed, 13 Mar 2013 19:24:44 -0000." <2691CE0099834E4A9C5044EEC662BB9D452399E1@dfweml509-mbx.china.huawei.com> <201303230358.r2N3wj7S041055@gateway1.orleans.occnc.com>
In-Reply-To: <201303230358.r2N3wj7S041055@gateway1.orleans.occnc.com>
Accept-Language: en-US, zh-CN
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.47.137.114]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Cc: "rtgwg@ietf.org" <rtgwg@ietf.org>
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Routing Area Working Group <rtgwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/rtgwg>
List-Post: <mailto:rtgwg@ietf.org>
List-Help: <mailto:rtgwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 24 Mar 2013 21:01:41 -0000

Hi Cutis,

The change is fine. Agree that the LC is completed.

Thanks,
Lucy

> -----Original Message-----
> From: Curtis Villamizar [mailto:curtis@occnc.com]
> Sent: Friday, March 22, 2013 10:59 PM
> To: Lucy yong
> Cc: Alia Atlas; rtgwg@ietf.org
> Subject: Re: WGLC on draft-ietf-rtgwg-cl-requirements-09
>=20
>=20
> In message <2691CE0099834E4A9C5044EEC662BB9D452399E1@dfweml509-
> mbx.china.huawei.com>
> Lucy yong writes:
>=20
> > One comment as one of co-authors.
> >
> > Suggest to change the title to "requirements for a composite link in
> > MPLS network". This will make consistent with the title in the
> > framework doc.
> >
> > Lucy
> >
> > From: rtgwg-bounces@ietf.org [mailto:rtgwg-bounces@ietf.org] On
> Behalf Of Alia Atlas
> > Sent: Thursday, February 21, 2013 1:42 PM
> > To: rtgwg@ietf.org
> > Subject: WGLC on draft-ietf-rtgwg-cl-requirements-09
> >
> > This is to start a working group last call on
> > draft-ietf-rtgwg-cl-requirements-09.  The WGLC will conclude on March
> > 15; extra time is given to include the IETF meeting.
> >
> > Please read and send comments.
> >
> > Thanks,
> > Alia & Alvaro
>=20
>=20
>=20
> Lucy,
>=20
> This is the second and only remaining comment in the last call.  Sorry
> I missed replying to this.  The request is to change the title.  If
> you don't mind making CLs and networks plural in the title then:
>=20
>   OLD
>=20
>     Requirements for MPLS Over a Composite Link
>=20
>   NEW
>=20
>     Requirements for Composite Links in MPLS Networks
>=20
> I just made this change since it seems non-controversial and it seems
> to me to be a better title.
>=20
> The only other change was requested by Alia and that was removing the
> sentence "Current practice related to multipath is described briefly
> in an appendix." from the abstract (that appendix is now in the use
> cases document).
>=20
> draft-ietf-rtgwg-cl-requirement-10 has been posted.
>=20
> If there are no objections to the title change, then the WG chairs can
> conclude the last call.
>=20
> Curtis

From zhangmingui@huawei.com  Sun Mar 24 19:59:09 2013
Return-Path: <zhangmingui@huawei.com>
X-Original-To: rtgwg@ietfa.amsl.com
Delivered-To: rtgwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 590C121F8AA8 for <rtgwg@ietfa.amsl.com>; Sun, 24 Mar 2013 19:59:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7lOR4Ug+yu7Y for <rtgwg@ietfa.amsl.com>; Sun, 24 Mar 2013 19:59:08 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id A28A621F8B0B for <rtgwg@ietf.org>; Sun, 24 Mar 2013 19:59:07 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml204-edg.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.5-GA FastPath queued) with ESMTP id APT21518; Mon, 25 Mar 2013 02:58:51 +0000 (GMT)
Received: from LHREML402-HUB.china.huawei.com (10.201.5.241) by lhreml204-edg.china.huawei.com (172.18.7.223) with Microsoft SMTP Server (TLS) id 14.1.323.7; Mon, 25 Mar 2013 02:58:41 +0000
Received: from NKGEML401-HUB.china.huawei.com (10.98.56.32) by lhreml402-hub.china.huawei.com (10.201.5.241) with Microsoft SMTP Server (TLS) id 14.1.323.7; Mon, 25 Mar 2013 02:58:46 +0000
Received: from NKGEML508-MBX.china.huawei.com ([169.254.7.233]) by nkgeml401-hub.china.huawei.com ([10.98.56.32]) with mapi id 14.01.0323.007; Mon, 25 Mar 2013 10:58:40 +0800
From: Mingui Zhang <zhangmingui@huawei.com>
To: "curtis@occnc.com" <curtis@occnc.com>, "Alvaro Retana (aretana)" <aretana@cisco.com>
Subject: RE: FW: I-D Action: draft-retana-rtgwg-eacp-01.txt
Thread-Topic: FW: I-D Action: draft-retana-rtgwg-eacp-01.txt
Thread-Index: AQHOJp/WEXBNGToejkmx0Lh1SZ1pD5iw9cSg
Date: Mon, 25 Mar 2013 02:58:40 +0000
Message-ID: <4552F0907735844E9204A62BBDD325E732B080B3@nkgeml508-mbx.china.huawei.com>
References: Your message of "Wed, 13 Feb 2013 15:52:52 GMT." <BBD66FD99311804F80324E8139B3C94ED5B183@xmb-aln-x15.cisco.com> <201303220150.r2M1oPxS020663@gateway1.orleans.occnc.com>
In-Reply-To: <201303220150.r2M1oPxS020663@gateway1.orleans.occnc.com>
Accept-Language: en-US, zh-CN
Content-Language: zh-CN
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.111.102.175]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Cc: "rtgwg@ietf.org" <rtgwg@ietf.org>
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Routing Area Working Group <rtgwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/rtgwg>
List-Post: <mailto:rtgwg@ietf.org>
List-Help: <mailto:rtgwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 25 Mar 2013 02:59:09 -0000

Hi Curtis,

Please find my comments in-line below.

>-----Original Message-----
>From: rtgwg-bounces@ietf.org [mailto:rtgwg-bounces@ietf.org] On Behalf Of
>Curtis Villamizar
>Sent: Friday, March 22, 2013 9:50 AM
>To: Alvaro Retana (aretana)
>Cc: rtgwg@ietf.org
>Subject: Re: FW: I-D Action: draft-retana-rtgwg-eacp-01.txt
>
>
>Alvaro,
>
>I'm not sure what it means to put a OTN interface in a "low power
>state".  OTN and SONET interfaces are a continuous stream of bits at a
>constant rate dictated by the ITU-T.  The rate is not adjustable.  It
>doesn't save any power by sending GFP null frames over OTN links.
>
>Since most long haul router to router links are Ethenet across the
>room, followed by long stretches of OTN, there may be no significant
>benefit to putting the short Ethernet into lower power mode.  Plus as
>discussed at IETF-86, the Ethernet low power mode applies only to
>copper Ethernet (10/100 Mb/s, 1 Gb/s copper) and not to the fiber
>forms of Ethernt used by providers.

The methodology from my side is to put those optical components in a manage=
able DOWN state (sleeping). If protocol work creates the opportunity for th=
em to stay in the sleeping state for seconds or minutes, energy saving can =
be significant.
Fiber forms for Ethernet does not support micro-sleeping mode, but they may=
 support deep-sleeping mode. PHYs can negotiate a longer time to stay in de=
ep-sleeping mode.

>
>So before anyone writes any more problem statements, requirements,
>frameworks, or complete solutions for energy aware networks, we need
>to have some research and some hard facts about where energy goes and
>where there are opportunities to save energy. =20

I agree that we should let numbers tell the truth. According to our observa=
tion, line-cards are the most power hungry part of high-end routers and swi=
tches. They can consume nearly 70% of the total power. Meanwhile, idle rout=
ers/switches consume more than 80% of their peak power. If we can shut-down=
 components on line-cards or whole line-cards, we can save a considerable a=
mount of energy.

This observation treats a router/switch as a black box. Our next step is to=
 open this black box and see what further meaningful numbers we will get.

>We also should be
>asking whether providers and high end network equipment vendors see a
>need for any protocol work in this area.  So far the answer is a
>resounding "no".

Energy Efficient Ethernet (EEE) involves a great deal of protocol work. Net=
work equipments supporting EEE have already been shipped around by vendors.=
 Providers may not resist solutions that can save their OPEX, only if vendo=
rs can come up with workable ones.

>
>It is also worth pointing out that research so far has indicated that
>the greatest total savings is the furthest down the food chain at or
>near the customer network.  So the low power Ethernet applied to the
>10/100/1000 copper used in homes and small business makes a lot of
>sense.  IETF may not be the right place to attack the next layer up
>the food chain, things like CMTS to CM (cable modem termination
>systems to cable modem) or DSL efficiencies.

Power/Energy Aware NETwork needs the combination of "hardware work" and "pr=
otocol work". Protocol work should make use of the hardware characteristics=
. IOW, protocol work should create the opportunity for these techniques to =
save most energy.=20

Energy saving for composite links may become another low-hanging fruit. As =
you pointed out, the traffic aggregation onto component links may impact th=
e cooling system. We can have a test to see what will happen, whether we sh=
ould have some limit on the aggregation.

Thanks,
Mingui



>
>Curtis
>
>
>In message
><BBD66FD99311804F80324E8139B3C94ED5B183@xmb-aln-x15.cisco.com>
>"Alvaro Retana (aretana)" writes:
>
>[Chair hat off.]
>
>Hi!
>
>We just published an update (a refresh really) of the draft below.
>
>The draft is NOT a set of requirements to be solved in the realm of power
>aware/energy efficient networking.  We are not trying to define
>requirements on how to save energy, how much energy should be saved, how,
>when or where.  Nor are we recommending any specific solution.
>
>So, what is it? ;-)   The intent of the draft is to "provide the tools and
>knowledge necessary for protocol designers to modify network protocols to
>best balance efficiency against performance, and to provide the background
>   information network operators will need to intelligently deploy and use
>protocol modifications to network protocols."
>
>In other words..  We recognize that saving energy may be in many people's
>minds, but we also recognize that networks have been designed/deployed
>with a set of business (availability, ability to satisfy customer SLAs,
>for example) and application (min bw, jitter/delay budgets, for instance)
>requirements in mind, which need to still be satisfied even while saving
>energy.
>
>The draft goes on to evaluate considerations derived from the
>business/application requirements that may be affected by applying common
>methods of reducing energy (reducing the topology or reducing the link
>speed, for example):  bw reduction, stretch, fast recovery, introducing
>jitter and other operational aspects.
>
>As an example, we mention (section 5.1) that eliminating links from the
>topology (shutting them down or putting them in a "low power state")
>should result in lower energy utilization..but that it will also affect
>the total available bw in the network.  The requirement then comes in in
>the form of "Modifications to control plane protocols to achieve network
>energy efficiency SHOULD provide the ability to set the minimal bandwidth,
>   jitter, and delay through the network".  I'll leave you to read some of
>the other examples/considerations and requirements.
>
>The end result of the draft is the definition of a framework against which
>we can evaluate "the tradeoffs between modifications made to network
>protocols to conserve energy and network performance metrics and
>requirements".
>
>Thanks!
>
>Alvaro.
>
>
>On 2/13/13 10:18 AM, "internet-drafts@ietf.org" <internet-drafts@ietf.org>
>wrote:
>
>>
>>A New Internet-Draft is available from the on-line Internet-Drafts
>>directories.
>>
>>
>>	Title           : A Framework and Requirements for Energy Aware
>Control
>>Planes
>>	Author(s)       : Alvaro Retana
>>                          Russ White
>>                          Manuel Paul
>>	Filename        : draft-retana-rtgwg-eacp-01.txt
>>	Pages           : 16
>>	Date            : 2013-02-13
>>
>>Abstract:
>>   There has been, for several years, a rising concern over the energy
>>   usage of large scale networks.  This concern is strongly focused on
>>   campus, data center, and other highly concentrated deployments of
>>   network infrastructure.  Given the steadily increasing demand for
>>   higher network speeds, always-on service models, and ubiquitous
>>   network coverage, it is also of growing importance for
>>   telecommunication networks both local and wide area in scope.  One of
>>   the issues in moving forward to reduce energy usage is to ensure that
>>   the network can still meet the performance specifications required to
>>   support the applications running over it.
>>
>>   This document provides an overview of the various areas of concern in
>>   the interaction between network performance and efforts at energy
>>   aware control planes, as a guide for those working on modifying
>>   current control planes or designing new control planes to improve the
>>   energy efficiency of high density, highly complex, network
>>   deployments.
>>
>>
>>The IETF datatracker status page for this draft is:
>>https://datatracker.ietf.org/doc/draft-retana-rtgwg-eacp
>>
>>There's also a htmlized version available at:
>>http://tools.ietf.org/html/draft-retana-rtgwg-eacp-01
>>
>>A diff from the previous version is available at:
>>http://www.ietf.org/rfcdiff?url2=3Ddraft-retana-rtgwg-eacp-01
>>
>>
>>Internet-Drafts are also available by anonymous FTP at:
>>ftp://ftp.ietf.org/internet-drafts/
>>
>>_______________________________________________
>>I-D-Announce mailing list
>>I-D-Announce@ietf.org
>>https://www.ietf.org/mailman/listinfo/i-d-announce
>>Internet-Draft directories: http://www.ietf.org/shadow.html
>>or ftp://ftp.ietf.org/ietf/1shadow-sites.txt
>
>_______________________________________________
>rtgwg mailing list
>rtgwg@ietf.org
>https://www.ietf.org/mailman/listinfo/rtgwg
>_______________________________________________
>rtgwg mailing list
>rtgwg@ietf.org
>https://www.ietf.org/mailman/listinfo/rtgwg

From curtis@occnc.com  Mon Mar 25 18:44:19 2013
Return-Path: <curtis@occnc.com>
X-Original-To: rtgwg@ietfa.amsl.com
Delivered-To: rtgwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E110121F8825 for <rtgwg@ietfa.amsl.com>; Mon, 25 Mar 2013 18:44:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.919
X-Spam-Level: *
X-Spam-Status: No, score=1.919 tagged_above=-999 required=5 tests=[BAYES_40=-0.185, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553,  RDNS_NONE=0.1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pXo+RyBrRVa1 for <rtgwg@ietfa.amsl.com>; Mon, 25 Mar 2013 18:44:19 -0700 (PDT)
Received: from gateway1.orleans.occnc.com (unknown [173.9.106.132]) by ietfa.amsl.com (Postfix) with ESMTP id 5160021F8804 for <rtgwg@ietf.org>; Mon, 25 Mar 2013 18:44:18 -0700 (PDT)
Received: from harbor1.ipv6.occnc.com (harbor1.ipv6.occnc.com [IPv6:2001:470:1f07:1545::2:819]) (authenticated bits=0) by gateway1.orleans.occnc.com (8.14.5/8.14.5) with ESMTP id r2Q1gxSK018031; Mon, 25 Mar 2013 21:42:59 -0400 (EDT) (envelope-from curtis@occnc.com)
Message-Id: <201303260142.r2Q1gxSK018031@gateway1.orleans.occnc.com>
To: Russ White <russw@riw.us>
From: Curtis Villamizar <curtis@occnc.com>
Subject: Re: FW: I-D Action: draft-retana-rtgwg-eacp-01.txt
In-reply-to: Your message of "Sat, 23 Mar 2013 13:45:02 EDT." <514DEA1E.2090008@riw.us>
Date: Mon, 25 Mar 2013 21:42:59 -0400
Cc: rtgwg@ietf.org
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: curtis@occnc.com
List-Id: Routing Area Working Group <rtgwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/rtgwg>
List-Post: <mailto:rtgwg@ietf.org>
List-Help: <mailto:rtgwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 26 Mar 2013 01:44:20 -0000

In message <514DEA1E.2090008@riw.us>
Russ White writes:
 
> > Stretch and microsleeps are solution space and I'd argue that the best
> > solutions for core may involve neither.  There is no highly credible
> > evidence that either has an impact on core network energy usage and
> > IMO stronger arguments that it would have no effect or infeasible
> > (microsleeping finely tuned temperature compensated colored lasers?)
> > than the the very weak arguments (mostly speculation) that there is
> > benefits to these two approaches for core.
>  
> No, stretch and sleep states are not "in the solution space." If you're
> going to save energy by using sleep states, then you need to deal with
> state. These are bars any given design must overcome, not suggestions
> for a design that would work.
>  
> > So the research happen where it belongs - elsewhere.  Then when there
> > is credible research presented, it might be time to consider a
> > taxonomy of the problem and solution space in an SDO.
>  
> So your basic argument is --"we should only consider this when it's
> proven to be economically viable." My counter to that is simple:
>  
> There's more to this game than saving more than x$/year. There's also
> the impact on the control plane to consider as a "cost."
>  
> This draft is an attempt to at least point those costs out in a
> reasonable and understandable way. In other words, it's trying to get
> all the requirements on the table, rather than focusing myopically on
> the economic costs.
>  
> Again, it's answering a completely different question than you're asking.
>  
> Russ


Russ,

This isn't a question of whether routing based techniques are
economically viable.  It is a question of whether there is any
real validity at all in the assertion that routing techniques aimed at
reducing power will in fact reduce power at all.

First research or other work (such as in industry, aka provider and
vendor space) must establish with reasonable credibility that there is
something to be gained by a particular strategy.  Then if there is a
potential for reasonable gains, the advantages and disadvatages can be
weighed.  With nothing on the advantages side, there is no sense in
spending any effort weighing the disadvantages.

Curtis

From curtis@occnc.com  Mon Mar 25 20:45:17 2013
Return-Path: <curtis@occnc.com>
X-Original-To: rtgwg@ietfa.amsl.com
Delivered-To: rtgwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AB5E521F88EF for <rtgwg@ietfa.amsl.com>; Mon, 25 Mar 2013 20:45:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.853
X-Spam-Level: 
X-Spam-Status: No, score=0.853 tagged_above=-999 required=5 tests=[AWL=-0.141,  BAYES_05=-1.11, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553,  RDNS_NONE=0.1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TtlW1HYu7KEY for <rtgwg@ietfa.amsl.com>; Mon, 25 Mar 2013 20:45:16 -0700 (PDT)
Received: from gateway1.orleans.occnc.com (unknown [173.9.106.132]) by ietfa.amsl.com (Postfix) with ESMTP id 7F58621F88E8 for <rtgwg@ietf.org>; Mon, 25 Mar 2013 20:45:16 -0700 (PDT)
Received: from harbor1.ipv6.occnc.com (harbor1.ipv6.occnc.com [IPv6:2001:470:1f07:1545::2:819]) (authenticated bits=0) by gateway1.orleans.occnc.com (8.14.5/8.14.5) with ESMTP id r2Q3gklt021682; Mon, 25 Mar 2013 23:42:46 -0400 (EDT) (envelope-from curtis@occnc.com)
Message-Id: <201303260342.r2Q3gklt021682@gateway1.orleans.occnc.com>
To: Mingui Zhang <zhangmingui@huawei.com>
From: Curtis Villamizar <curtis@occnc.com>
Subject: Re: FW: I-D Action: draft-retana-rtgwg-eacp-01.txt
In-reply-to: Your message of "Mon, 25 Mar 2013 02:58:40 -0000." <4552F0907735844E9204A62BBDD325E732B080B3@nkgeml508-mbx.china.huawei.com>
Date: Mon, 25 Mar 2013 23:42:46 -0400
Cc: "rtgwg@ietf.org" <rtgwg@ietf.org>
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: curtis@occnc.com
List-Id: Routing Area Working Group <rtgwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/rtgwg>
List-Post: <mailto:rtgwg@ietf.org>
List-Help: <mailto:rtgwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 26 Mar 2013 03:45:17 -0000

In message <4552F0907735844E9204A62BBDD325E732B080B3@nkgeml508-mbx.china.huawei.com>
Mingui Zhang writes:
> 
> Hi Curtis,
>  
> Please find my comments in-line below.

Hi Mingui,

> >-----Original Message-----
> >From: rtgwg-bounces@ietf.org [mailto:rtgwg-bounces@ietf.org] On Behalf Of
> >Curtis Villamizar
> >Sent: Friday, March 22, 2013 9:50 AM
> >To: Alvaro Retana (aretana)
> >Cc: rtgwg@ietf.org
> >Subject: Re: FW: I-D Action: draft-retana-rtgwg-eacp-01.txt
> >
> >
> >Alvaro,
> >
> >I'm not sure what it means to put a OTN interface in a "low power
> >state".  OTN and SONET interfaces are a continuous stream of bits at a
> >constant rate dictated by the ITU-T.  The rate is not adjustable.  It
> >doesn't save any power by sending GFP null frames over OTN links.
> >
> >Since most long haul router to router links are Ethenet across the
> >room, followed by long stretches of OTN, there may be no significant
> >benefit to putting the short Ethernet into lower power mode.  Plus as
> >discussed at IETF-86, the Ethernet low power mode applies only to
> >copper Ethernet (10/100 Mb/s, 1 Gb/s copper) and not to the fiber
> >forms of Ethernt used by providers.
>  
> The methodology from my side is to put those optical components in a
> manageable DOWN state (sleeping). If protocol work creates the
> opportunity for them to stay in the sleeping state for seconds or
> minutes, energy saving can be significant.  Fiber forms for Ethernet
> does not support micro-sleeping mode, but they may support
> deep-sleeping mode. PHYs can negotiate a longer time to stay in
> deep-sleeping mode.

BTW- That sounds to me like solution space.

As stated from Pat (don't have her last name handy) at IETF-86, there
was a reason IEEE wrote the existing standard for copper Ethernet
only.

It is harder to power down a laser and power up.  It is very hard to
power down and power back up a temperature compensated finely tuned
laser used in WDM systems, particularly todays DWDM and ULH circuits.
Those can take over a minute to acheive stability, during which time
they cannot be used.  So if you could power down for an extended
period of time, maybe there would be hope.

> >So before anyone writes any more problem statements, requirements,
> >frameworks, or complete solutions for energy aware networks, we need
> >to have some research and some hard facts about where energy goes and
> >where there are opportunities to save energy.  
>  
> I agree that we should let numbers tell the truth. According to our
> observation, line-cards are the most power hungry part of high-end
> routers and switches. They can consume nearly 70% of the total
> power. Meanwhile, idle routers/switches consume more than 80% of their
> peak power. If we can shut-down components on line-cards or whole
> line-cards, we can save a considerable amount of energy.

Your observation used the topology of a real network but had nothing
to do with the power being consumed by the network who's topology you
used.

> This observation treats a router/switch as a black box. Our next step
> is to open this black box and see what further meaningful numbers we
> will get.

Yes.  And that is still in the research stage.

> >We also should be
> >asking whether providers and high end network equipment vendors see a
> >need for any protocol work in this area.  So far the answer is a
> >resounding "no".
>  
> Energy Efficient Ethernet (EEE) involves a great deal of protocol
> work. Network equipments supporting EEE have already been shipped
> around by vendors. Providers may not resist solutions that can save
> their OPEX, only if vendors can come up with workable ones.

And supports copper only.  Providers don't use copper Ethernet.

> >It is also worth pointing out that research so far has indicated that
> >the greatest total savings is the furthest down the food chain at or
> >near the customer network.  So the low power Ethernet applied to the
> >10/100/1000 copper used in homes and small business makes a lot of
> >sense.  IETF may not be the right place to attack the next layer up
> >the food chain, things like CMTS to CM (cable modem termination
> >systems to cable modem) or DSL efficiencies.
>  
> Power/Energy Aware NETwork needs the combination of "hardware work"
> and "protocol work". Protocol work should make use of the hardware
> characteristics. IOW, protocol work should create the opportunity for
> these techniques to save most energy.

The assertion that protocol work is needed is nothing more than an
empty assertion.  There are currently no facts to back it up.

> Energy saving for composite links may become another low-hanging
> fruit. As you pointed out, the traffic aggregation onto component
> links may impact the cooling system. We can have a test to see what
> will happen, whether we should have some limit on the aggregation.
>  
> Thanks,
> Mingui

I'm not convinced that there is any savings for composite link, or
today's simpler LAG.  The switching uses more power than the laser on
a short haul interface.  I'm not sure to shut down the transport
lasers.  If you move the switching to a smaller subset of cards, you
heat that subset of cards more and the fan has to run hard enough to
cool the hottest card in the chassis.  There may be no net decrease in
switching power, negligible laser power decrease, and an larger
increase in fan power, yielding higher power consumption for the same
amount of traffic.  AFAIK, no one has measured using the types of
equipment actually at a provider.  Using vendor data sheets and
extrapolating doesn't work.

Curtis


> >Curtis
> >
> >
> >In message
> ><BBD66FD99311804F80324E8139B3C94ED5B183@xmb-aln-x15.cisco.com>
> >"Alvaro Retana (aretana)" writes:
> >
> >[Chair hat off.]
> >
> >Hi!
> >
> >We just published an update (a refresh really) of the draft below.
> >
> >The draft is NOT a set of requirements to be solved in the realm of power
> >aware/energy efficient networking.  We are not trying to define
> >requirements on how to save energy, how much energy should be saved, how,
> >when or where.  Nor are we recommending any specific solution.
> >
> >So, what is it? ;-)   The intent of the draft is to "provide the tools and
> >knowledge necessary for protocol designers to modify network protocols to
> >best balance efficiency against performance, and to provide the background
> >   information network operators will need to intelligently deploy and use
> >protocol modifications to network protocols."
> >
> >In other words..  We recognize that saving energy may be in many people's
> >minds, but we also recognize that networks have been designed/deployed
> >with a set of business (availability, ability to satisfy customer SLAs,
> >for example) and application (min bw, jitter/delay budgets, for instance)
> >requirements in mind, which need to still be satisfied even while saving
> >energy.
> >
> >The draft goes on to evaluate considerations derived from the
> >business/application requirements that may be affected by applying common
> >methods of reducing energy (reducing the topology or reducing the link
> >speed, for example):  bw reduction, stretch, fast recovery, introducing
> >jitter and other operational aspects.
> >
> >As an example, we mention (section 5.1) that eliminating links from the
> >topology (shutting them down or putting them in a "low power state")
> >should result in lower energy utilization..but that it will also affect
> >the total available bw in the network.  The requirement then comes in in
> >the form of "Modifications to control plane protocols to achieve network
> >energy efficiency SHOULD provide the ability to set the minimal bandwidth,
> >   jitter, and delay through the network".  I'll leave you to read some of
> >the other examples/considerations and requirements.
> >
> >The end result of the draft is the definition of a framework against which
> >we can evaluate "the tradeoffs between modifications made to network
> >protocols to conserve energy and network performance metrics and
> >requirements".
> >
> >Thanks!
> >
> >Alvaro.
> >
> >
> >On 2/13/13 10:18 AM, "internet-drafts@ietf.org" <internet-drafts@ietf.org>
> >wrote:
> >
> >>
> >>A New Internet-Draft is available from the on-line Internet-Drafts
> >>directories.
> >>
> >>
> >>	Title           : A Framework and Requirements for Energy Aware
> >Control
> >>Planes
> >>	Author(s)       : Alvaro Retana
> >>                          Russ White
> >>                          Manuel Paul
> >>	Filename        : draft-retana-rtgwg-eacp-01.txt
> >>	Pages           : 16
> >>	Date            : 2013-02-13
> >>
> >>Abstract:
> >>   There has been, for several years, a rising concern over the energy
> >>   usage of large scale networks.  This concern is strongly focused on
> >>   campus, data center, and other highly concentrated deployments of
> >>   network infrastructure.  Given the steadily increasing demand for
> >>   higher network speeds, always-on service models, and ubiquitous
> >>   network coverage, it is also of growing importance for
> >>   telecommunication networks both local and wide area in scope.  One of
> >>   the issues in moving forward to reduce energy usage is to ensure that
> >>   the network can still meet the performance specifications required to
> >>   support the applications running over it.
> >>
> >>   This document provides an overview of the various areas of concern in
> >>   the interaction between network performance and efforts at energy
> >>   aware control planes, as a guide for those working on modifying
> >>   current control planes or designing new control planes to improve the
> >>   energy efficiency of high density, highly complex, network
> >>   deployments.
> >>
> >>
> >>The IETF datatracker status page for this draft is:
> >>https://datatracker.ietf.org/doc/draft-retana-rtgwg-eacp
> >>
> >>There's also a htmlized version available at:
> >>http://tools.ietf.org/html/draft-retana-rtgwg-eacp-01
> >>
> >>A diff from the previous version is available at:
> >>http://www.ietf.org/rfcdiff?url2=draft-retana-rtgwg-eacp-01
> >>
> >>
> >>Internet-Drafts are also available by anonymous FTP at:
> >>ftp://ftp.ietf.org/internet-drafts/
> >>
> >>_______________________________________________
> >>I-D-Announce mailing list
> >>I-D-Announce@ietf.org
> >>https://www.ietf.org/mailman/listinfo/i-d-announce
> >>Internet-Draft directories: http://www.ietf.org/shadow.html
> >>or ftp://ftp.ietf.org/ietf/1shadow-sites.txt

From shane@castlepoint.net  Tue Mar 26 09:05:27 2013
Return-Path: <shane@castlepoint.net>
X-Original-To: rtgwg@ietfa.amsl.com
Delivered-To: rtgwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B18DD21E8039 for <rtgwg@ietfa.amsl.com>; Tue, 26 Mar 2013 09:05:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.437
X-Spam-Level: 
X-Spam-Status: No, score=-0.437 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_ORG=0.611,  RDNS_NONE=0.1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id g5rv8wVJvx1x for <rtgwg@ietfa.amsl.com>; Tue, 26 Mar 2013 09:05:27 -0700 (PDT)
Received: from mail.friendswithtools.org (unknown [64.78.239.70]) by ietfa.amsl.com (Postfix) with ESMTP id C4EC621E8034 for <rtgwg@ietf.org>; Tue, 26 Mar 2013 09:05:26 -0700 (PDT)
Received: from dspam (unknown [127.0.0.1]) by mail.friendswithtools.org (Postfix) with SMTP id D4E3930007D for <rtgwg@ietf.org>; Tue, 26 Mar 2013 16:05:25 +0000 (UTC)
Received: from [10.9.0.10] (web.hollyman.com [64.78.239.73]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by mail.friendswithtools.org (Postfix) with ESMTPSA id 2DF43300056; Tue, 26 Mar 2013 10:05:24 -0600 (MDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\))
Subject: Re: I-D Action: draft-retana-rtgwg-eacp-01.txt
From: Shane Amante <shane@castlepoint.net>
In-Reply-To: <201303260342.r2Q3gklt021682@gateway1.orleans.occnc.com>
Date: Tue, 26 Mar 2013 10:05:25 -0600
Content-Transfer-Encoding: quoted-printable
Message-Id: <1A978525-A45A-425E-B418-9B2D317FC6A4@castlepoint.net>
References: <201303260342.r2Q3gklt021682@gateway1.orleans.occnc.com>
To: curtis@occnc.com
X-Mailer: Apple Mail (2.1503)
X-DSPAM-Result: Innocent
X-DSPAM-Processed: Tue Mar 26 10:05:25 2013
X-DSPAM-Confidence: 1.0000
X-DSPAM-Improbability: 1 in 98689409 chance of being spam
X-DSPAM-Probability: 0.0023
X-DSPAM-Signature: 5151c74542079514813969
X-DSPAM-Factors: 27, same+#+#+into, 0.40000, a+Inter, 0.40000, to+CE, 0.40000, to+CE, 0.40000, 2013+at, 0.40000, Mar+#+#+#+9, 0.40000, network+#+#+#+a, 0.40000, links+#+Intra, 0.40000, that+#+practically, 0.40000, answer+#+a, 0.40000, to+#+#+definitions, 0.40000, would+#+on, 0.40000, not+seen, 0.40000, supports+#+only, 0.40000, Mime-Version*Mail+6.3, 0.40000, Mar+#+2013, 0.40000, also+#+#+#+whether, 0.40000, WDM+#+#+and, 0.40000, possible+#+somehow, 0.40000, can+#+#+with, 0.40000, to+#+#+#+to, 0.40000, what+the, 0.40000, a+#+PE, 0.40000, already+#+#+around, 0.40000, multiplexed+#+#+#+U, 0.40000, Zhang+#+#+#+also, 0.40000, complexity+in, 0.40000
Cc: "rtgwg@ietf.org" <rtgwg@ietf.org>
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Routing Area Working Group <rtgwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/rtgwg>
List-Post: <mailto:rtgwg@ietf.org>
List-Help: <mailto:rtgwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 26 Mar 2013 16:05:27 -0000

Curtis,

One correction, below.

On Mar 25, 2013, at 9:42 PM, Curtis Villamizar <curtis@occnc.com> wrote:
> In message =
<4552F0907735844E9204A62BBDD325E732B080B3@nkgeml508-mbx.china.huawei.com>
> Mingui Zhang writes:
[--snip--]
>>> We also should be
>>> asking whether providers and high end network equipment vendors see =
a
>>> need for any protocol work in this area.  So far the answer is a
>>> resounding "no".
>>=20
>> Energy Efficient Ethernet (EEE) involves a great deal of protocol
>> work. Network equipments supporting EEE have already been shipped
>> around by vendors. Providers may not resist solutions that can save
>> their OPEX, only if vendors can come up with workable ones.
>=20
> And supports copper only.  Providers don't use copper Ethernet.

Sure, we do ... at the [very] **edges** of our network. =20

I wholly agree with you that Providers (absolutely) DO NOT use copper =
Ethernet in the "core" of their network, which I would define as:
a) Inter-City links, (P <-> P)
b) Peering links, (ASBR <-> ASBR)
c) P <-> PE links
d) Intra-Metro [WDM] device interconnection links, e.g.: interconnection =
of Ethernet switches via their East-West ring-side interfaces, (N-PE <-> =
U-PE *and* U-PE <-> U-PE).

For the above, providers only ever use fiber and/or WDM over fiber for =
such interconnections.  It's interesting to note that most of those =
links, (a) thru (c), are the only links over which providers run routing =
and signaling protocols, (e.g.: IS-IS, LDP, RSVP, etc.).  While =
technically possible to run routing and signaling protocols for (d), due =
to a variety of factors, that is not the case.  Instead, it is more =
common to see some form of Layer-2 ring protocol protocol, (e.g.: RSTP, =
G.8032, etc.), being run on those interfaces, since there is only a very =
simple East-West forwarding decision that needs to be made.  Regardless, =
I agree with your overall points and question what, if any, value is =
there in modifying routing and/or signaling protocols for this "core" =
part of the network to accommodate idle power states, given the =
substantial complexity in attempting to quickly *and* accurately =
transition from a quiescent state back to a 'nominal' state of full =
capacity.


I would say that we *DO* use copper Ethernet at the [furthest] "edge" of =
the network, which I would define as a U-PE <-> CE hand-offs, where the =
distances are short enough (> 100m) that it is technically feasible to =
do so.  (Refer to RFC4026 for definitions of U-PE to N-PE).  =
Interestingly enough, a substantial portion of the *N*-PE <-> CE =
circuits are running BGP, (think: Internet and/or IPVPN services).  But, =
as I stated above, the N-PE <-> U-PE interconnects use: i) =
fiber/WDM-over-fiber; and, ii) are statistically multiplexed in that =
multiple U-PE's share the same physical "uplinks" into the N-PE.  So, =
even if it were possible to somehow "turn-off" BGP from N-PE to CE, then =
I don't see that that could practically lead to power-savings on the =
N-PE since the N-PE's ring-side interfaces are both optical and need to =
stay operational/running in order to provide service to other U-PE's.

Thus, the only practical application I can see of power savings would be =
on copper interfaces at the deepest "edge" of the network, (U-PE to CE), =
but there's no active routing protocols on those interfaces.  And, =
although there's Layer-2 control protocols, e.g.: LLDP and the MEF's =
"Ethernet LMI", but I've not seen either of those achieve widespread =
deployment mostly because the CE devices do not support it, (yet).  But, =
we're the IETF, not the IEEE nor the MEF ... so, I'm not clear what the =
IETF would be able to work on here.

-shane=


From ttauber@1-4-5.net  Tue Mar 26 18:15:30 2013
Return-Path: <ttauber@1-4-5.net>
X-Original-To: rtgwg@ietfa.amsl.com
Delivered-To: rtgwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 88F9121F86D3 for <rtgwg@ietfa.amsl.com>; Tue, 26 Mar 2013 18:15:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.425
X-Spam-Level: 
X-Spam-Status: No, score=-100.425 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FH_RELAY_NODNS=1.451, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RDNS_NONE=0.1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TElQXQD9mMW6 for <rtgwg@ietfa.amsl.com>; Tue, 26 Mar 2013 18:15:30 -0700 (PDT)
Received: from mail-we0-x235.google.com (mail-we0-x235.google.com [IPv6:2a00:1450:400c:c03::235]) by ietfa.amsl.com (Postfix) with ESMTP id C8B3521F86CE for <rtgwg@ietf.org>; Tue, 26 Mar 2013 18:15:29 -0700 (PDT)
Received: by mail-we0-f181.google.com with SMTP id d7so1629203wer.12 for <rtgwg@ietf.org>; Tue, 26 Mar 2013 18:15:28 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-received:x-originating-ip:in-reply-to:references :date:message-id:subject:from:to:cc:content-type:x-gm-message-state; bh=RtNnoEZhcpCCsY8DiXgmuD09EVu3BLIDvO7Jc4DUemE=; b=o47kRpFWB6mvI1/8nAcYsmcBBz2DENPiuHjvUzU3KBtO9UjljthoNYVQABeDlaH4G1 Ud5+5w9RkXht636DqMYml+pElmKe8XPowC/hb0nKA6MeyLnaIma3ctr1iDeRTVgEitRp OYcrSOPFlTuJO/MpkaSjBz7yZ/ORF10Uw2YxGYRViP3TKKHPnIk6PkY326puBn8jpkWz wakhBS4KKDmdZwkTLLL2DA7OpPLdVZk2UeDhMAom8Oqu7gx8b7HOqJ5ge+45lBFfxn0I eSj53aLzUs9SNyhpr5Ia+yf33m0WW/xW/86HnFMX9FP9/fwr03JNw1kkt/cmCdVcMjhV 3lJg==
MIME-Version: 1.0
X-Received: by 10.180.101.41 with SMTP id fd9mr6478703wib.20.1364346928761; Tue, 26 Mar 2013 18:15:28 -0700 (PDT)
Received: by 10.194.178.3 with HTTP; Tue, 26 Mar 2013 18:15:28 -0700 (PDT)
X-Originating-IP: [24.104.152.66]
In-Reply-To: <1A978525-A45A-425E-B418-9B2D317FC6A4@castlepoint.net>
References: <201303260342.r2Q3gklt021682@gateway1.orleans.occnc.com> <1A978525-A45A-425E-B418-9B2D317FC6A4@castlepoint.net>
Date: Tue, 26 Mar 2013 21:15:28 -0400
Message-ID: <CAGQUKcc1EfPTH7-S81BKLpmJr6OO_zKkCAqmOh35WP-e_W+_OA@mail.gmail.com>
Subject: Re: I-D Action: draft-retana-rtgwg-eacp-01.txt
From: Tony Tauber <ttauber@1-4-5.net>
To: Shane Amante <shane@castlepoint.net>
Content-Type: multipart/alternative; boundary=f46d041826c20a24cd04d8ddc612
X-Gm-Message-State: ALoCoQnnIMO8W2mFK7PSxj1tx3xrccLv+moBvJmI59UbTCGPVD82uhUTq6wpERex+ONyKNZJ6CFp
Cc: "rtgwg@ietf.org" <rtgwg@ietf.org>
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Routing Area Working Group <rtgwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/rtgwg>
List-Post: <mailto:rtgwg@ietf.org>
List-Help: <mailto:rtgwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 27 Mar 2013 01:15:30 -0000

--f46d041826c20a24cd04d8ddc612
Content-Type: text/plain; charset=ISO-8859-1

On Tue, Mar 26, 2013 at 12:05 PM, Shane Amante <shane@castlepoint.net>wrote:

>
> Thus, the only practical application I can see of power savings would be
> on copper interfaces at the deepest "edge" of the network, (U-PE to CE),
> but there's no active routing protocols on those interfaces.  And, although
> there's Layer-2 control protocols, e.g.: LLDP and the MEF's "Ethernet LMI",
> but I've not seen either of those achieve widespread deployment mostly
> because the CE devices do not support it, (yet).  But, we're the IETF, not
> the IEEE nor the MEF ... so, I'm not clear what the IETF would be able to
> work on here.


Now that you mention it, datacenter or campus LANs would appear to be the
biggest wins in terms of power and raw numbers of interfaces.
IEEE seems like a better match in that case.  No idea if there are things
going on in that venue.

Tony

--f46d041826c20a24cd04d8ddc612
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

On Tue, Mar 26, 2013 at 12:05 PM, Shane Amante <span dir=3D"ltr">&lt;<a hre=
f=3D"mailto:shane@castlepoint.net" target=3D"_blank">shane@castlepoint.net<=
/a>&gt;</span> wrote:<br><div class=3D"gmail_quote"><blockquote class=3D"gm=
ail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-le=
ft:1ex">
<br>
Thus, the only practical application I can see of power savings would be on=
 copper interfaces at the deepest &quot;edge&quot; of the network, (U-PE to=
 CE), but there&#39;s no active routing protocols on those interfaces. =A0A=
nd, although there&#39;s Layer-2 control protocols, e.g.: LLDP and the MEF&=
#39;s &quot;Ethernet LMI&quot;, but I&#39;ve not seen either of those achie=
ve widespread deployment mostly because the CE devices do not support it, (=
yet). =A0But, we&#39;re the IETF, not the IEEE nor the MEF ... so, I&#39;m =
not clear what the IETF would be able to work on here.</blockquote>
<div><br>Now that you mention it, datacenter or campus LANs would appear to=
 be=20
the biggest wins in terms of power and raw numbers of interfaces.<br>IEEE s=
eems like a better match in that case.=A0 No idea if there are things going=
 on in that venue.<br><br>Tony<br></div></div>

--f46d041826c20a24cd04d8ddc612--

From zhangmingui@huawei.com  Tue Mar 26 19:23:00 2013
Return-Path: <zhangmingui@huawei.com>
X-Original-To: rtgwg@ietfa.amsl.com
Delivered-To: rtgwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A9F2F21F8499 for <rtgwg@ietfa.amsl.com>; Tue, 26 Mar 2013 19:22:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ejBHJs3NHRBg for <rtgwg@ietfa.amsl.com>; Tue, 26 Mar 2013 19:22:58 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id 455FD11E80A2 for <rtgwg@ietf.org>; Tue, 26 Mar 2013 19:22:54 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml204-edg.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.5-GA FastPath queued) with ESMTP id APU98440; Wed, 27 Mar 2013 02:22:52 +0000 (GMT)
Received: from LHREML401-HUB.china.huawei.com (10.201.5.240) by lhreml204-edg.china.huawei.com (172.18.7.223) with Microsoft SMTP Server (TLS) id 14.1.323.7; Wed, 27 Mar 2013 02:22:40 +0000
Received: from NKGEML410-HUB.china.huawei.com (10.98.56.41) by lhreml401-hub.china.huawei.com (10.201.5.240) with Microsoft SMTP Server (TLS) id 14.1.323.7; Wed, 27 Mar 2013 02:22:51 +0000
Received: from NKGEML508-MBX.china.huawei.com ([169.254.7.233]) by nkgeml410-hub.china.huawei.com ([10.98.56.41]) with mapi id 14.01.0323.007; Wed, 27 Mar 2013 10:22:46 +0800
From: Mingui Zhang <zhangmingui@huawei.com>
To: Tony Tauber <ttauber@1-4-5.net>, Shane Amante <shane@castlepoint.net>
Subject: RE: I-D Action: draft-retana-rtgwg-eacp-01.txt
Thread-Topic: I-D Action: draft-retana-rtgwg-eacp-01.txt
Thread-Index: AQHOKjzdPlSU4jQyrUGb3fpynX3u9Ji4NowAgACOwdA=
Date: Wed, 27 Mar 2013 02:22:46 +0000
Message-ID: <4552F0907735844E9204A62BBDD325E732B08279@nkgeml508-mbx.china.huawei.com>
References: <201303260342.r2Q3gklt021682@gateway1.orleans.occnc.com> <1A978525-A45A-425E-B418-9B2D317FC6A4@castlepoint.net> <CAGQUKcc1EfPTH7-S81BKLpmJr6OO_zKkCAqmOh35WP-e_W+_OA@mail.gmail.com>
In-Reply-To: <CAGQUKcc1EfPTH7-S81BKLpmJr6OO_zKkCAqmOh35WP-e_W+_OA@mail.gmail.com>
Accept-Language: en-US, zh-CN
Content-Language: zh-CN
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.111.102.175]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Cc: "rtgwg@ietf.org" <rtgwg@ietf.org>
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Routing Area Working Group <rtgwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/rtgwg>
List-Post: <mailto:rtgwg@ietf.org>
List-Help: <mailto:rtgwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 27 Mar 2013 02:23:01 -0000

>Now that you mention it, datacenter or campus LANs would appear to be the
>biggest wins in terms of power and raw numbers of interfaces.
>IEEE seems like a better match in that case.  No idea if there are things =
going
>on in that venue.

As for "datacenter or campus LANs", I'd mention that ISIS can be used as th=
e control protocol (e.g., TRILL and SPB). This is an area that matches IETF=
.

Mingui


>-----Original Message-----
>From: rtgwg-bounces@ietf.org [mailto:rtgwg-bounces@ietf.org] On Behalf Of
>Tony Tauber
>Sent: Wednesday, March 27, 2013 9:15 AM
>To: Shane Amante
>Cc: rtgwg@ietf.org
>Subject: Re: I-D Action: draft-retana-rtgwg-eacp-01.txt
>
>On Tue, Mar 26, 2013 at 12:05 PM, Shane Amante <shane@castlepoint.net>
>wrote:
>
>
>
>	Thus, the only practical application I can see of power savings would be =
on
>copper interfaces at the deepest "edge" of the network, (U-PE to CE), but
>there's no active routing protocols on those interfaces.  And, although th=
ere's
>Layer-2 control protocols, e.g.: LLDP and the MEF's "Ethernet LMI", but I'=
ve not
>seen either of those achieve widespread deployment mostly because the CE
>devices do not support it, (yet).  But, we're the IETF, not the IEEE nor t=
he
>MEF ... so, I'm not clear what the IETF would be able to work on here.
>
>
>Now that you mention it, datacenter or campus LANs would appear to be the
>biggest wins in terms of power and raw numbers of interfaces.
>IEEE seems like a better match in that case.  No idea if there are things =
going
>on in that venue.
>
>Tony


From mickseaman@sbcglobal.net  Tue Mar 26 20:30:21 2013
Return-Path: <mickseaman@sbcglobal.net>
X-Original-To: rtgwg@ietfa.amsl.com
Delivered-To: rtgwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5A98E21F873D for <rtgwg@ietfa.amsl.com>; Tue, 26 Mar 2013 20:30:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.599
X-Spam-Level: 
X-Spam-Status: No, score=-4.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, GB_I_INVITATION=-2]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HKGCkqpXlQ4S for <rtgwg@ietfa.amsl.com>; Tue, 26 Mar 2013 20:30:20 -0700 (PDT)
Received: from nm24-vm0.access.bullet.mail.sp2.yahoo.com (nm24-vm0.access.bullet.mail.sp2.yahoo.com [98.139.44.182]) by ietfa.amsl.com (Postfix) with ESMTP id CEF4121F871C for <rtgwg@ietf.org>; Tue, 26 Mar 2013 20:30:20 -0700 (PDT)
Received: from [98.139.44.105] by nm24.access.bullet.mail.sp2.yahoo.com with NNFMP; 27 Mar 2013 03:30:18 -0000
Received: from [98.138.84.175] by tm10.access.bullet.mail.sp2.yahoo.com with NNFMP; 27 Mar 2013 03:30:17 -0000
Received: from [127.0.0.1] by smtp109.sbc.mail.ne1.yahoo.com with NNFMP; 27 Mar 2013 03:30:17 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sbcglobal.net; s=s1024; t=1364355017; bh=v1Q80buJnZfyEKa/BxNBZdVBq5dMuXHdqiTNigXhJ08=; h=X-Yahoo-Newman-Id:X-Yahoo-Newman-Property:X-YMail-OSG:X-Yahoo-SMTP:X-Rocket-Received:Message-ID:Date:From:User-Agent:MIME-Version:To:Subject:References:In-Reply-To:Content-Type:Content-Transfer-Encoding; b=2xVN5aF4UtFcB6yMN0rlLSx3rf5KLQAE3bDJSLdhS/nDIaZBe5uK13QA++ldcBaDa6u0F0/usO+wLYdg15oAKArsfzLy+buZ8vna6/o9FlRsFMHXe8sME0ejg/k06RWCZ9LDzNQkzL8B0oF84rDXdJSuYoOSEMPOwJ1LpERTzgE=
X-Yahoo-Newman-Id: 849682.13115.bm@smtp109.sbc.mail.ne1.yahoo.com
X-Yahoo-Newman-Property: ymail-3
X-YMail-OSG: fOrCD.4VM1nI_6y9MdxuXyx3G8fgWl98f2BImW.3vcSy_4l u_vUhUpYsOox0OhnVBVY0ZvzmtQxHDRNkdq7aItxcnOUPU7v0Gr2KM0n5r6l KsigiE0paBEXzs.GWmVvn3oHdHc6od1sDPhTcobf81ydEntKCRdzDmc.m6uw kCYhR__3bLQlrb0zoTrpbx82.NImI4aJLKpKBiQqQ6wqKwx.BV.ae0JixG0Q I34aSiG1yfQ4hHWvznM4.BaY4CHNQ.E.O8rtIlqIEXyVhezXf_p6AOHAV7Ou HxFdjAXZfARlsgDgioUi3slSo5mV.DzyzxtsWEPo0xPrHtrOlUiTgwIjUrL8 WKYxva6Q_MmSGeYr_SPGUOmQZNITyBwLOviBPUk7gnuux_hVqtdgBA.tK3LP ZdqYZLpx5l0F48TSkkZrWMdXhBGgx1zD3wvRkMPxlmX7K7MYcPV98RDznsRT J4RPEwIfoN3uPOU5skGl0f93LVceWMw--
X-Yahoo-SMTP: AR5_vwuswBBBxttajAdmA6MrHv2fOmL0PL2m9ko1TKipiHmVNQ--
X-Rocket-Received: from [192.168.0.113] (mickseaman@75.18.211.247 with plain) by smtp109.sbc.mail.ne1.yahoo.com with SMTP; 26 Mar 2013 20:30:17 -0700 PDT
Message-ID: <515267DB.7050508@sbcglobal.net>
Date: Tue, 26 Mar 2013 20:30:35 -0700
From: Mick Seaman <mickseaman@sbcglobal.net>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:17.0) Gecko/20130307 Thunderbird/17.0.4
MIME-Version: 1.0
To: rtgwg@ietf.org, zhangmingui@huawei.com
Subject: Re: I-D Action: draft-retana-rtgwg-eacp-01.txt
References: <201303260342.r2Q3gklt021682@gateway1.orleans.occnc.com> <1A978525-A45A-425E-B418-9B2D317FC6A4@castlepoint.net> <CAGQUKcc1EfPTH7-S81BKLpmJr6OO_zKkCAqmOh35WP-e_W+_OA@mail.gmail.com> <4552F0907735844E9204A62BBDD325E732B08279@nkgeml508-mbx.china.huawei.com>
In-Reply-To: <4552F0907735844E9204A62BBDD325E732B08279@nkgeml508-mbx.china.huawei.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Routing Area Working Group <rtgwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/rtgwg>
List-Post: <mailto:rtgwg@ietf.org>
List-Help: <mailto:rtgwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 27 Mar 2013 03:30:21 -0000

I'll let the TRILL folks speak for themselves, but I would politely 
suggest that you keep your hands off SPB.

So far as SPB is concerned ISIS is a protocol for ensuring that all 
participants converge on the same data as the basis of performing the 
necessary topology and related calculations. Those calculations are 
specified by the IEEE. Some of the data shared, and the way in which the 
calculations are performed, has a close relationship with 
interoperability with parts of the bridged/switched network where other 
topology protocols operate. The fact that ISIS is employed as part of 
the solution is not an invitation for others to "enhance"/rework/invent 
anew or otherwise muck with the current standards.

If there is any doubt about this I can no doubt arrange for the point to 
be made more forcefully.

Mick Seaman



On 3/26/2013 7:22 PM, Mingui Zhang wrote:
>> Now that you mention it, datacenter or campus LANs would appear to be the
>> biggest wins in terms of power and raw numbers of interfaces.
>> IEEE seems like a better match in that case.  No idea if there are things going
>> on in that venue.
> As for "datacenter or campus LANs", I'd mention that ISIS can be used as the control protocol (e.g., TRILL and SPB). This is an area that matches IETF.
>
> Mingui
>
>
>> -----Original Message-----
>> From: rtgwg-bounces@ietf.org [mailto:rtgwg-bounces@ietf.org] On Behalf Of
>> Tony Tauber
>> Sent: Wednesday, March 27, 2013 9:15 AM
>> To: Shane Amante
>> Cc: rtgwg@ietf.org
>> Subject: Re: I-D Action: draft-retana-rtgwg-eacp-01.txt
>>
>> On Tue, Mar 26, 2013 at 12:05 PM, Shane Amante <shane@castlepoint.net>
>> wrote:
>>
>>
>>
>> 	Thus, the only practical application I can see of power savings would be on
>> copper interfaces at the deepest "edge" of the network, (U-PE to CE), but
>> there's no active routing protocols on those interfaces.  And, although there's
>> Layer-2 control protocols, e.g.: LLDP and the MEF's "Ethernet LMI", but I've not
>> seen either of those achieve widespread deployment mostly because the CE
>> devices do not support it, (yet).  But, we're the IETF, not the IEEE nor the
>> MEF ... so, I'm not clear what the IETF would be able to work on here.
>>
>>
>> Now that you mention it, datacenter or campus LANs would appear to be the
>> biggest wins in terms of power and raw numbers of interfaces.
>> IEEE seems like a better match in that case.  No idea if there are things going
>> on in that venue.
>>
>> Tony
> _______________________________________________
> rtgwg mailing list
> rtgwg@ietf.org
> https://www.ietf.org/mailman/listinfo/rtgwg
>


From curtis@occnc.com  Thu Mar 28 14:03:54 2013
Return-Path: <curtis@occnc.com>
X-Original-To: rtgwg@ietfa.amsl.com
Delivered-To: rtgwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6D9EC21F8FD4 for <rtgwg@ietfa.amsl.com>; Thu, 28 Mar 2013 14:03:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.173
X-Spam-Level: 
X-Spam-Status: No, score=-0.173 tagged_above=-999 required=5 tests=[AWL=0.322,  BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553,  RDNS_NONE=0.1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zDamuD7CkoXO for <rtgwg@ietfa.amsl.com>; Thu, 28 Mar 2013 14:03:54 -0700 (PDT)
Received: from gateway1.orleans.occnc.com (unknown [173.9.106.132]) by ietfa.amsl.com (Postfix) with ESMTP id D444421F8F1F for <rtgwg@ietf.org>; Thu, 28 Mar 2013 14:03:53 -0700 (PDT)
Received: from harbor1.ipv6.occnc.com (harbor1.ipv6.occnc.com [IPv6:2001:470:1f07:1545::2:819]) (authenticated bits=0) by gateway1.orleans.occnc.com (8.14.5/8.14.5) with ESMTP id r2SL1F0X061798; Thu, 28 Mar 2013 17:01:16 -0400 (EDT) (envelope-from curtis@occnc.com)
Message-Id: <201303282101.r2SL1F0X061798@gateway1.orleans.occnc.com>
To: Mingui Zhang <zhangmingui@huawei.com>
From: Curtis Villamizar <curtis@occnc.com>
Subject: Re: I-D Action: draft-retana-rtgwg-eacp-01.txt
In-reply-to: Your message of "Wed, 27 Mar 2013 02:22:46 -0000." <4552F0907735844E9204A62BBDD325E732B08279@nkgeml508-mbx.china.huawei.com>
Date: Thu, 28 Mar 2013 17:01:15 -0400
Cc: Shane Amante <shane@castlepoint.net>, Tony Tauber <ttauber@1-4-5.net>, "rtgwg@ietf.org" <rtgwg@ietf.org>
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: curtis@occnc.com
List-Id: Routing Area Working Group <rtgwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/rtgwg>
List-Post: <mailto:rtgwg@ietf.org>
List-Help: <mailto:rtgwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 28 Mar 2013 21:03:54 -0000

In message <4552F0907735844E9204A62BBDD325E732B08279@nkgeml508-mbx.china.huawei.com>
Mingui Zhang writes:
>
> >Now that you mention it, datacenter or campus LANs would appear to be the
> >biggest wins in terms of power and raw numbers of interfaces.
> >IEEE seems like a better match in that case.  No idea if there are
> >things going
> >on in that venue.
>  
> As for "datacenter or campus LANs", I'd mention that ISIS can be used
> as the control protocol (e.g., TRILL and SPB). This is an area that
> matches IETF.
>  
> Mingui


Mingui,

Are you familiar with the english (maybe just american) expression
"grabbing at straws"?

I think datacenter interest in Trill and SPB is declining,
particularly in very large datacenters where scaling limits are being
felt.  The current chaos in datacenters revolves around SDN, or more
precisely at this point, arguing about what SDN is and isn't.

Curtis


> >-----Original Message-----
> >From: rtgwg-bounces@ietf.org [mailto:rtgwg-bounces@ietf.org] On Behalf Of
> >Tony Tauber
> >Sent: Wednesday, March 27, 2013 9:15 AM
> >To: Shane Amante
> >Cc: rtgwg@ietf.org
> >Subject: Re: I-D Action: draft-retana-rtgwg-eacp-01.txt
> >
> >On Tue, Mar 26, 2013 at 12:05 PM, Shane Amante <shane@castlepoint.net>
> >wrote:
> >
> >
> >
> >	Thus, the only practical application I can see of power savings would be on
> >copper interfaces at the deepest "edge" of the network, (U-PE to CE), but
> >there's no active routing protocols on those interfaces.  And, although there's
> >Layer-2 control protocols, e.g.: LLDP and the MEF's "Ethernet LMI", but I've not
> >seen either of those achieve widespread deployment mostly because the CE
> >devices do not support it, (yet).  But, we're the IETF, not the IEEE nor the
> >MEF ... so, I'm not clear what the IETF would be able to work on here.
> >
> >
> >Now that you mention it, datacenter or campus LANs would appear to be the
> >biggest wins in terms of power and raw numbers of interfaces.
> >IEEE seems like a better match in that case.  No idea if there are things going
> >on in that venue.
> >
> >Tony

From zhangmingui@huawei.com  Fri Mar 29 01:34:07 2013
Return-Path: <zhangmingui@huawei.com>
X-Original-To: rtgwg@ietfa.amsl.com
Delivered-To: rtgwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3BDE521F92AA for <rtgwg@ietfa.amsl.com>; Fri, 29 Mar 2013 01:34:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hS6aTu5YrAbH for <rtgwg@ietfa.amsl.com>; Fri, 29 Mar 2013 01:34:06 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id EFA9421F92A7 for <rtgwg@ietf.org>; Fri, 29 Mar 2013 01:34:05 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml203-edg.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.5-GA FastPath queued) with ESMTP id APW86250; Fri, 29 Mar 2013 08:33:50 +0000 (GMT)
Received: from LHREML405-HUB.china.huawei.com (10.201.5.242) by lhreml203-edg.huawei.com (172.18.7.221) with Microsoft SMTP Server (TLS) id 14.1.323.7; Fri, 29 Mar 2013 08:33:20 +0000
Received: from NKGEML404-HUB.china.huawei.com (10.98.56.35) by lhreml405-hub.china.huawei.com (10.201.5.242) with Microsoft SMTP Server (TLS) id 14.1.323.7; Fri, 29 Mar 2013 08:33:45 +0000
Received: from NKGEML508-MBX.china.huawei.com ([169.254.7.233]) by nkgeml404-hub.china.huawei.com ([10.98.56.35]) with mapi id 14.01.0323.007; Fri, 29 Mar 2013 16:33:38 +0800
From: Mingui Zhang <zhangmingui@huawei.com>
To: "curtis@occnc.com" <curtis@occnc.com>
Subject: RE: I-D Action: draft-retana-rtgwg-eacp-01.txt
Thread-Topic: I-D Action: draft-retana-rtgwg-eacp-01.txt
Thread-Index: AQHOK/diPlSU4jQyrUGb3fpynX3u9Ji7+J1Q
Date: Fri, 29 Mar 2013 08:33:37 +0000
Message-ID: <4552F0907735844E9204A62BBDD325E732B08413@nkgeml508-mbx.china.huawei.com>
References: Your message of "Wed, 27 Mar 2013 02:22:46 -0000." <4552F0907735844E9204A62BBDD325E732B08279@nkgeml508-mbx.china.huawei.com> <201303282101.r2SL1F0X061798@gateway1.orleans.occnc.com>
In-Reply-To: <201303282101.r2SL1F0X061798@gateway1.orleans.occnc.com>
Accept-Language: en-US, zh-CN
Content-Language: zh-CN
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-cr-hashedpuzzle: B8nR Cxv8 EWkm HPig LVlh MN7r MW3L NCmn OM+r OPxd OuQX P3pF RqpQ VWOh XDcb XaBx; 2; YwB1AHIAdABpAHMAQABvAGMAYwBuAGMALgBjAG8AbQA7AHIAdABnAHcAZwBAAGkAZQB0AGYALgBvAHIAZwA=; Sosha1_v1; 7; {0E2A577B-7E7D-4044-90FF-0ED09C8B86DB}; egBoAGEAbgBnAG0AaQBuAGcAdQBpAEAAaAB1AGEAdwBlAGkALgBjAG8AbQA=; Fri, 29 Mar 2013 08:33:31 GMT; UgBFADoAIABJAC0ARAAgAEEAYwB0AGkAbwBuADoAIABkAHIAYQBmAHQALQByAGUAdABhAG4AYQAtAHIAdABnAHcAZwAtAGUAYQBjAHAALQAwADEALgB0AHgAdAA=
x-cr-puzzleid: {0E2A577B-7E7D-4044-90FF-0ED09C8B86DB}
x-originating-ip: [10.111.102.175]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Cc: "rtgwg@ietf.org" <rtgwg@ietf.org>
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Routing Area Working Group <rtgwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/rtgwg>
List-Post: <mailto:rtgwg@ietf.org>
List-Help: <mailto:rtgwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 29 Mar 2013 08:34:07 -0000

Hi Curtis,

Scalability is not the only issue that DC operators concern. Energy conserv=
ation is also a critical issue. I wonder whether you are suggesting another=
 "straw" by mentioning SDN. However, we do not intend to work on greening D=
CNs right now. In PANET-Problem Statement we scope our work in ISP networks=
.=20

Whatever the specific protocol is, only if it can be used to achieve our me=
thod then we can make use of it. The method is to aggregate traffic through=
 protocol work and create opportunity for network devices to enter low powe=
r mode (e.g., sleeping) in order to achieve the energy conservation of the =
network. The apparent waste on idle power by high-end routers and switches =
makes us believe there is opportunity for this kind of energy saving. Green=
TE is one of those solutions that reveal this feasibility.=20

I feel that we are here trying to obtain conclusions based on guess rather =
than fact. Power saving of networks requires the cooperation of hardware & =
protocol. We need "walk on two legs". I think it's time to get more relevan=
t observations along with hardware experts.

Thanks,
Mingui

>-----Original Message-----
>From: Curtis Villamizar [mailto:curtis@occnc.com]
>Sent: Friday, March 29, 2013 5:01 AM
>To: Mingui Zhang
>Cc: Tony Tauber; Shane Amante; rtgwg@ietf.org
>Subject: Re: I-D Action: draft-retana-rtgwg-eacp-01.txt
>
>
>In message
><4552F0907735844E9204A62BBDD325E732B08279@nkgeml508-mbx.china.hu
>awei.com>
>Mingui Zhang writes:
>>
>> >Now that you mention it, datacenter or campus LANs would appear to be t=
he
>> >biggest wins in terms of power and raw numbers of interfaces.
>> >IEEE seems like a better match in that case.  No idea if there are
>> >things going
>> >on in that venue.
>>
>> As for "datacenter or campus LANs", I'd mention that ISIS can be used
>> as the control protocol (e.g., TRILL and SPB). This is an area that
>> matches IETF.
>>
>> Mingui
>
>
>Mingui,
>
>Are you familiar with the english (maybe just american) expression
>"grabbing at straws"?
>
>I think datacenter interest in Trill and SPB is declining,
>particularly in very large datacenters where scaling limits are being
>felt.  The current chaos in datacenters revolves around SDN, or more
>precisely at this point, arguing about what SDN is and isn't.
>
>Curtis
>
>
>> >-----Original Message-----
>> >From: rtgwg-bounces@ietf.org [mailto:rtgwg-bounces@ietf.org] On Behalf
>Of
>> >Tony Tauber
>> >Sent: Wednesday, March 27, 2013 9:15 AM
>> >To: Shane Amante
>> >Cc: rtgwg@ietf.org
>> >Subject: Re: I-D Action: draft-retana-rtgwg-eacp-01.txt
>> >
>> >On Tue, Mar 26, 2013 at 12:05 PM, Shane Amante <shane@castlepoint.net>
>> >wrote:
>> >
>> >
>> >
>> >	Thus, the only practical application I can see of power savings would =
be on
>> >copper interfaces at the deepest "edge" of the network, (U-PE to CE), b=
ut
>> >there's no active routing protocols on those interfaces.  And, although
>there's
>> >Layer-2 control protocols, e.g.: LLDP and the MEF's "Ethernet LMI", but=
 I've
>not
>> >seen either of those achieve widespread deployment mostly because the C=
E
>> >devices do not support it, (yet).  But, we're the IETF, not the IEEE no=
r the
>> >MEF ... so, I'm not clear what the IETF would be able to work on here.
>> >
>> >
>> >Now that you mention it, datacenter or campus LANs would appear to be t=
he
>> >biggest wins in terms of power and raw numbers of interfaces.
>> >IEEE seems like a better match in that case.  No idea if there are thin=
gs
>going
>> >on in that venue.
>> >
>> >Tony

From eosborne@cisco.com  Fri Mar 29 05:42:08 2013
Return-Path: <eosborne@cisco.com>
X-Original-To: rtgwg@ietfa.amsl.com
Delivered-To: rtgwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4D9F321F93CB for <rtgwg@ietfa.amsl.com>; Fri, 29 Mar 2013 05:42:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level: 
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DoFoHTcqcmkQ for <rtgwg@ietfa.amsl.com>; Fri, 29 Mar 2013 05:42:07 -0700 (PDT)
Received: from rcdn-iport-5.cisco.com (rcdn-iport-5.cisco.com [173.37.86.76]) by ietfa.amsl.com (Postfix) with ESMTP id AF96B21F93FD for <rtgwg@ietf.org>; Fri, 29 Mar 2013 05:42:07 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=354; q=dns/txt; s=iport; t=1364560927; x=1365770527; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=eVcWxzaB3dyoYMrk8hQyPs6Ob7vfuVAt8cKWy1Obj4E=; b=VvNHNdo3CuW5XitjQmWJEXfUl7YWDhTNGkFzEhcOi6N/clh/Dc0UK7HW pB6jO2CmOxwXmYtfVH5aXrHpoL/2fPMsLMyQdtMO1aoan1RFWd3x/niex aIUI8bygJSI6OP1Ji3EoB59G4Wr6y8cg1U90fmbJ0PPZAT7QljmB1HMoB 8=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgAFAH2KVVGtJV2Z/2dsb2JhbABDwlyBCBZ0gh8BAQEDAToxDgULAgEIIhQQMiUCBAENDYgGBr9ijWeBADEHgl9hA6dwgwuCKA
X-IronPort-AV: E=Sophos;i="4.87,373,1363132800"; d="scan'208";a="192890368"
Received: from rcdn-core-2.cisco.com ([173.37.93.153]) by rcdn-iport-5.cisco.com with ESMTP; 29 Mar 2013 12:42:07 +0000
Received: from xhc-rcd-x04.cisco.com (xhc-rcd-x04.cisco.com [173.37.183.78]) by rcdn-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id r2TCg7M5014703 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Fri, 29 Mar 2013 12:42:07 GMT
Received: from xmb-rcd-x09.cisco.com ([169.254.9.206]) by xhc-rcd-x04.cisco.com ([173.37.183.78]) with mapi id 14.02.0318.004; Fri, 29 Mar 2013 07:42:06 -0500
From: "Eric Osborne (eosborne)" <eosborne@cisco.com>
To: Mingui Zhang <zhangmingui@huawei.com>, "curtis@occnc.com" <curtis@occnc.com>
Subject: RE: I-D Action: draft-retana-rtgwg-eacp-01.txt
Thread-Topic: I-D Action: draft-retana-rtgwg-eacp-01.txt
Thread-Index: AQHOK/di0DBzJ5FbF0iowZh3Kc/AZ5i8rBmA///xghA=
Date: Fri, 29 Mar 2013 12:42:06 +0000
Message-ID: <20ECF67871905846A80F77F8F4A275721011C7A2@xmb-rcd-x09.cisco.com>
References: Your message of "Wed, 27 Mar 2013 02:22:46 -0000." <4552F0907735844E9204A62BBDD325E732B08279@nkgeml508-mbx.china.huawei.com> <201303282101.r2SL1F0X061798@gateway1.orleans.occnc.com> <4552F0907735844E9204A62BBDD325E732B08413@nkgeml508-mbx.china.huawei.com>
In-Reply-To: <4552F0907735844E9204A62BBDD325E732B08413@nkgeml508-mbx.china.huawei.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.98.66.75]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "rtgwg@ietf.org" <rtgwg@ietf.org>
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Routing Area Working Group <rtgwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/rtgwg>
List-Post: <mailto:rtgwg@ietf.org>
List-Help: <mailto:rtgwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 29 Mar 2013 12:42:08 -0000

...

> I feel that we are here trying to obtain conclusions based on guess rathe=
r than
> fact. Power saving of networks requires the cooperation of hardware &
> protocol. We need "walk on two legs". I think it's time to get more relev=
ant
> observations along with hardware experts.

Finally, something we can all agree on. :)




eric
