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

Mick Seaman <mickseaman@sbcglobal.net> Wed, 27 March 2013 03:30 UTC

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
>