Re: [re-ECN] Conex charter - now in External Review

"Woundy, Richard" <Richard_Woundy@cable.comcast.com> Tue, 27 April 2010 17:48 UTC

Return-Path: <richard_woundy@cable.comcast.com>
X-Original-To: re-ecn@core3.amsl.com
Delivered-To: re-ecn@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 062E43A6A89 for <re-ecn@core3.amsl.com>; Tue, 27 Apr 2010 10:48:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.6
X-Spam-Level:
X-Spam-Status: No, score=-0.6 tagged_above=-999 required=5 tests=[AWL=-2.737, BAYES_50=0.001, HELO_EQ_MODEMCABLE=0.768, HOST_EQ_MODEMCABLE=1.368]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QD2nHX5oJWCJ for <re-ecn@core3.amsl.com>; Tue, 27 Apr 2010 10:48:34 -0700 (PDT)
Received: from paoakoavas10.cable.comcast.com (paoakoavas10.cable.comcast.com [208.17.35.59]) by core3.amsl.com (Postfix) with ESMTP id B0A9328C0F1 for <re-ecn@ietf.org>; Tue, 27 Apr 2010 10:48:33 -0700 (PDT)
Received: from ([24.40.15.92]) by paoakoavas10.cable.comcast.com with ESMTP id KP-TDCH7.80620920; Tue, 27 Apr 2010 13:48:05 -0400
Received: from pacdcexcmb05.cable.comcast.com ([24.40.15.116]) by PACDCEXCSMTP03.cable.comcast.com with Microsoft SMTPSVC(6.0.3790.4675); Tue, 27 Apr 2010 13:48:05 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Tue, 27 Apr 2010 13:47:54 -0400
Message-ID: <EE00404438E9444D90AEA84210DC406793D9DB@pacdcexcmb05.cable.comcast.com>
In-Reply-To: <20100427151601.GF16203@verdi>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [re-ECN] Conex charter - now in External Review
Thread-Index: AcrmIM5HLDDAzXZ+QUySsN+PriiiJAADpHNA
References: <20100401165723.GA1375@verdi><4A916DBC72536E419A0BD955EDECEDEC06363F60@E03MVB1-UKBR.domain1.systemhost.net><20100406192914.GG11835@verdi> <4BBBF64C.2020101@thinkingcat.com><6036E869-9710-4F7B-BB30-5A70C7250D36@nokia.com><20100413184853.GA76668@verdi> <4BD6F2DD.3040202@cisco.com> <20100427151601.GF16203@verdi>
From: "Woundy, Richard" <Richard_Woundy@cable.comcast.com>
To: John Leslie <john@jlc.net>, Stewart Bryant <stbryant@cisco.com>
X-OriginalArrivalTime: 27 Apr 2010 17:48:05.0648 (UTC) FILETIME=[CA5ED900:01CAE631]
Cc: re-ecn@ietf.org
Subject: Re: [re-ECN] Conex charter - now in External Review
X-BeenThere: re-ecn@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: re-inserted explicit congestion notification <re-ecn.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/re-ecn>, <mailto:re-ecn-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/re-ecn>
List-Post: <mailto:re-ecn@ietf.org>
List-Help: <mailto:re-ecn-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/re-ecn>, <mailto:re-ecn-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 27 Apr 2010 17:48:36 -0000

I agree with John pretty much. Since I have been looking at CONEX, that
would imply that my employer has at least some minimal interest in CONEX
technology. But to make the leap that my employer is committed to deploy
this technology is a huge leap.

Remember: the current charter text states that the current expected work
outputs are "Informational" and "Experimental" documents, so I'm not
even sure what you mean by "deployment".

Here are some (purposely snarky) responses, to show why it is hard to
answer, and why these are BUSINESS QUESTIONS outside of the scope of our
group:

(Let's NOT discuss these questions on the list!!!)

Is there a list of vendors that have stated that they plan to implement
CONEX technology in their products? Is there a list of vendors that have
stated that they have no plans to implement CONEX technology in their
products?

For the vendors that are planning to implement CONEX, what CONEX
features will be implemented? What is the CONEX implementation roadmap?
What is the additional cost for CONEX features (by product, by feature),
or alternatively will certain CONEX features be 'table stakes' for
certain vendors?

Again, let's NOT discuss these questions on the list!!!

-- Rich

-----Original Message-----
From: re-ecn-bounces@ietf.org [mailto:re-ecn-bounces@ietf.org] On Behalf
Of John Leslie
Sent: Tuesday, April 27, 2010 11:16 AM
To: Stewart Bryant
Cc: re-ecn@ietf.org
Subject: Re: [re-ECN] Conex charter - now in External Review

Stewart Bryant <stbryant@cisco.com> wrote:
> 
> Is there a list of service providers that have stated that they wish
to 
> deploy CONEX technology?

   I am not aware of such a list, although the ISP I own (JLC.net)
should
certainly be included.

   In fairness, ConEx is very much a moving target right now, so I'd
hesitate to push any of the ISPs I talk with to plan adoption of it.

> Similarly is there a list of service providers that have stated that 
> they do not wish to deploy CONEX technology?

   I don't know... this has the same moving-target issue...

   In fairness, I don't think it matters much whether any individual
ISP deploys it. It is about visibility of congestion information, not
about what anyone might do with it. For myself, I always want to stare
at data for a while before attempting to automate anything.

> Do we know which members of the list that wish to deploy the
technology 
> need to deploy it over an IP network and which need to deploy it over
an 
> MPLS enabled network?

   Good question!

   My personal view is that ConEx makes absolutely no difference except
at IP-layer forwarding points; so I can't imagine why I'd want to view
it (least of all change it) at MPLS layer.

   (I'm only partly familiar with how ECN is carried through MPLS layer
in the EXP field; but I can't think of anything useful to do about it
until the return to IP-layer forwarding.)

> Thanks

   My pleasure...

--
John Leslie <john@jlc.net>
_______________________________________________
re-ECN mailing list
re-ECN@ietf.org
https://www.ietf.org/mailman/listinfo/re-ecn