FW: I-D Action: draft-retana-rtgwg-eacp-01.txt

"Alvaro Retana (aretana)" <aretana@cisco.com> Wed, 13 February 2013 15:53 UTC

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 9A47021F8788 for <rtgwg@ietfa.amsl.com>; Wed, 13 Feb 2013 07:53:03 -0800 (PST)
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=[AWL=0.000, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LIOfkbGxydm5 for <rtgwg@ietfa.amsl.com>; Wed, 13 Feb 2013 07:52:57 -0800 (PST)
Received: from rcdn-iport-3.cisco.com (rcdn-iport-3.cisco.com [173.37.86.74]) by ietfa.amsl.com (Postfix) with ESMTP id 1E73121F8783 for <rtgwg@ietf.org>; Wed, 13 Feb 2013 07:52:57 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=4537; q=dns/txt; s=iport; t=1360770777; x=1361980377; h=from:to:subject:date:message-id:in-reply-to:content-id: content-transfer-encoding:mime-version; bh=HUZFWPFefD6/Jbka7Cpox6JzrA8ODdj5N4prP/xtUXw=; b=hV0/xDACn7Q3Ya0C5yQQPQhXvShAey5EPewCxHlQ8eGh/kfUVs8UsQJb fn4RL+vns0qR0xyr0cCVaue6wv7YY+DvRjxTSkCrLVQ+IDGRTkGYGkWzJ DPKa+jttXk1LpxezCS0Aj+XhhR3OOE2Ync3W02xdk+v6yKrFWhq/2tF3w 8=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgkFAOWzG1GtJXG//2dsb2JhbABEg3m8cRZzgh8BAQEEAQEBCywrCR0BCCIUNwsbAQYDAgQTCAESh3cHBZ1poQCNSoNYYQOXQYomhRCDBoIn
X-IronPort-AV: E=Sophos;i="4.84,658,1355097600"; d="scan'208";a="176700419"
Received: from rcdn-core2-4.cisco.com ([173.37.113.191]) by rcdn-iport-3.cisco.com with ESMTP; 13 Feb 2013 15:52:53 +0000
Received: from xhc-aln-x13.cisco.com (xhc-aln-x13.cisco.com [173.36.12.87]) by rcdn-core2-4.cisco.com (8.14.5/8.14.5) with ESMTP id r1DFqrUE030978 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL) for <rtgwg@ietf.org>; Wed, 13 Feb 2013 15:52:53 GMT
Received: from xmb-aln-x15.cisco.com ([169.254.9.213]) by xhc-aln-x13.cisco.com ([173.36.12.87]) with mapi id 14.02.0318.004; Wed, 13 Feb 2013 09:52:53 -0600
From: "Alvaro Retana (aretana)" <aretana@cisco.com>
To: "rtgwg@ietf.org" <rtgwg@ietf.org>
Subject: FW: I-D Action: draft-retana-rtgwg-eacp-01.txt
Thread-Topic: I-D Action: draft-retana-rtgwg-eacp-01.txt
Thread-Index: AQHOCf1km8R/urP4qkG8rBFAxgvU4Zh4ASIA
Date: Wed, 13 Feb 2013 15:52:52 +0000
Message-ID: <BBD66FD99311804F80324E8139B3C94ED5B183@xmb-aln-x15.cisco.com>
In-Reply-To: <20130213151819.12024.15592.idtracker@ietfa.amsl.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.82.232.118]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <FBF6679D232BDB4DAFCA9EEAA8D72B74@cisco.com>
Content-Transfer-Encoding: quoted-printable
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 Feb 2013 15:53:06 -0000

[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