Re: [re-ECN] Conex charter

I have been out and have read the posts on this thread. Not intending to
shoot the IESG messenger, but wanted to add my input.

I agree that in general the detailed discussion of whether deployment of
a protocol before it is  standardized is premature. Based upon the
charter description and mailing list discussions, within the service
provider I work for there are those who do and don't want to deploy any
type of congestion control.

IMO, the IESG needs to look at this problem in a broader perspective --
because this is where the IETF can add the most value. What is needed is
a solution that is deployed by not only service provider using their IP
(possibly MPLS in some special cases) vendors, but also operating system
and application vendors. Without all three, IMO, this effort will
experience the same limited deployment fate as other congestion
approaches (e.g., Decbit, FR DE, ATM CLP, ATM ABR, ECN). 

So, in a sense this is a chicken and egg problem, and there is a need to
start somewhere. IMO, the real driver is application level protocols
that can interpret congestion (and other) feedback from service
providers (ledbat is a start here) in a meaningful business sense. The
operating system is also critical because it is the glue that connects
these parts.

Thanks,

Dave

> -----Original Message-----
> From: re-ecn-bounces@ietf.org 
> [mailto:re-ecn-bounces@ietf.org] On Behalf Of Stewart Bryant
> Sent: Tuesday, April 27, 2010 10:21 AM
> To: re-ecn@ietf.org
> Subject: Re: [re-ECN] Conex charter - now in External Review
> 
> Is there a list of service providers that have stated that 
> they wish to deploy CONEX technology?
> 
> Similarly is there a list of service providers that have 
> stated that they do not wish to deploy CONEX technology?
> 
> 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?
> 
> Thanks
> 
> Stewart
> 
> 
> 
> 
> _______________________________________________
> re-ECN mailing list
> re-ECN@ietf.org
> https://www.ietf.org/mailman/listinfo/re-ecn
> 