Re: FW: I-D Action: draft-retana-rtgwg-eacp-01.txt
Curtis Villamizar <curtis@occnc.com> Fri, 22 March 2013 01:51 UTC
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
- FW: I-D Action: draft-retana-rtgwg-eacp-01.txt Alvaro Retana (aretana)
- Re: FW: I-D Action: draft-retana-rtgwg-eacp-01.txt Curtis Villamizar
- Re: FW: I-D Action: draft-retana-rtgwg-eacp-01.txt Russ White
- Re: FW: I-D Action: draft-retana-rtgwg-eacp-01.txt Curtis Villamizar
- Re: FW: I-D Action: draft-retana-rtgwg-eacp-01.txt Russ White
- RE: FW: I-D Action: draft-retana-rtgwg-eacp-01.txt Mingui Zhang
- Re: FW: I-D Action: draft-retana-rtgwg-eacp-01.txt Curtis Villamizar
- Re: FW: I-D Action: draft-retana-rtgwg-eacp-01.txt Curtis Villamizar
- Re: I-D Action: draft-retana-rtgwg-eacp-01.txt Shane Amante
- Re: I-D Action: draft-retana-rtgwg-eacp-01.txt Tony Tauber
- RE: I-D Action: draft-retana-rtgwg-eacp-01.txt Mingui Zhang
- Re: I-D Action: draft-retana-rtgwg-eacp-01.txt Mick Seaman
- Re: I-D Action: draft-retana-rtgwg-eacp-01.txt Curtis Villamizar
- RE: I-D Action: draft-retana-rtgwg-eacp-01.txt Mingui Zhang
- RE: I-D Action: draft-retana-rtgwg-eacp-01.txt Eric Osborne (eosborne)