Re: [re-ECN] Other transports than TCP in charter
<toby.moncaster@bt.com> Fri, 13 November 2009 09:21 UTC
Return-Path: <toby.moncaster@bt.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 B68A63A6935 for <re-ecn@core3.amsl.com>;
Fri, 13 Nov 2009 01:21:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.287
X-Spam-Level:
X-Spam-Status: No, score=-3.287 tagged_above=-999 required=5 tests=[AWL=0.311,
BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
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 QyU8Vb27RH52 for
<re-ecn@core3.amsl.com>; Fri, 13 Nov 2009 01:21:23 -0800 (PST)
Received: from smtp2.smtp.bt.com (smtp2.smtp.bt.com [217.32.164.150]) by
core3.amsl.com (Postfix) with ESMTP id 8951C3A68C4 for <re-ecn@ietf.org>;
Fri, 13 Nov 2009 01:21:21 -0800 (PST)
Received: from E03MVZ1-UKDY.domain1.systemhost.net ([193.113.30.61]) by
smtp2.smtp.bt.com with Microsoft SMTPSVC(6.0.3790.3959);
Fri, 13 Nov 2009 09:21:50 +0000
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative;
boundary="----_=_NextPart_001_01CA6442.BACCF1FA"
Date: Fri, 13 Nov 2009 09:21:47 -0000
Message-ID: <AEDCAF87EEC94F49BA92EBDD49854CC70DEB979C@E03MVZ1-UKDY.domain1.systemhost.net>
In-Reply-To: <36a593230911121809m2b1322cctfcc124f5b7ec707@mail.gmail.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [re-ECN] Other transports than TCP in charter
Thread-Index: AcpkBmlM6OvtifNlSqWIgJ9IKcuGiwAOvCWA
References: <130EBB38279E9847BAAAE0B8F9905F8C023967DD@esealmw109.eemea.ericsson.se>
<36a593230911121809m2b1322cctfcc124f5b7ec707@mail.gmail.com>
From: <toby.moncaster@bt.com>
To: <zhouboyj@gmail.com>, <ingemar.s.johansson@ericsson.com>
X-OriginalArrivalTime: 13 Nov 2009 09:21:50.0457 (UTC)
FILETIME=[BB2FC690:01CA6442]
Cc: re-ecn@ietf.org
Subject: Re: [re-ECN] Other transports than TCP in charter
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: Fri, 13 Nov 2009 09:21:29 -0000
Any WG that is formed as a result of this BoF will have a very difficult balancing act to do - clearly eventually we want every transport that is commonly used on the network to integrate ConEx. However each transport will add significantly to the time it takes the WG to produce usable output. My view is that we therefore need to approach transports in a sensible order. One possible compromise might be as follows: · Define a clear set of minimal transport requirements since these will allow people to start working out how to integrate this into their transport of choice. · Fully define the protocol extensions for TCP since this is still the transport of choice for both the majority of bits and the majority of flows. · Then follow Ingemar's suggestion of adding this to RTP (and related real-time protocols) since these are becoming ever more significant as real-time media really starts to take off. · Then move onto transports such as SCTP and DCCP once we have evidence of how the TCP implementation is going. Given the current approach of the IESG is to try and limit the scope of charters in order to get results more quickly we are going to have to choose a point to divide the above list into current and future charters. The deciding factor will be to some extent the number of people prepared to work on a given item. Personally speaking I am torn between putting the split after TCP (which will allow us to make very rapid progress) and after RTP (which may well become very significant in the near future). Toby ____________________________________________________________________ Toby Moncaster, Senior Researcher, Network Infrastructure Practice B54/70 Adastral Park, Ipswich, IP53RE, UK. +44 7918 901170 From: re-ecn-bounces@ietf.org [mailto:re-ecn-bounces@ietf.org] On Behalf Of bo zhou Sent: 13 November 2009 02:10 To: Ingemar Johansson S Cc: re-ecn@ietf.org Subject: Re: [re-ECN] Other transports than TCP in charter I believe Ingemar's suggestion is reasonable. Hope the ConEx WG can consider all transport protocols rather than TCP only. Regards, Bo Zhou China Mobile On Fri, Nov 13, 2009 at 10:00 AM, Ingemar Johansson S <ingemar.s.johansson@ericsson.com> wrote: Hi I have raised this concern earlier on this list but I do this again just to make sure that this does not fall between the chairs. The proposed "strawman" BoF charter discusses TCP. I would like the group to consider IP as the common denominator, the motivation can be found at. http://www.ietf.org/mail-archive/web/re-ecn/current/msg00410.html In short the work done in ConEx should be able to apply on UDP as well as TCP. Other transports of interest may be SCTP and DCCP. /Ingemar ================================= INGEMAR JOHANSSON M.Sc. Senior Research Engineer Ericsson AB Multimedia Technologies Labratoriegränd 11 971 28, Luleå, Sweden Phone +46-1071 43042 SMS/MMS +46-73 078 3289 ingemar.s.johansson@ericsson.com www.ericsson.com <http://www.ericsson.com/> Visit http://labs.ericsson.com <http://labs.ericsson.com/> ! ================================= _______________________________________________ re-ECN mailing list re-ECN@ietf.org https://www.ietf.org/mailman/listinfo/re-ecn -- Regards, Bo Zhou China Mobile
- [re-ECN] Other transports than TCP in charter Ingemar Johansson S
- Re: [re-ECN] Other transports than TCP in charter bo zhou
- Re: [re-ECN] Other transports than TCP in charter toby.moncaster
- Re: [re-ECN] Other transports than TCP in charter John Leslie
- Re: [re-ECN] Other transports than TCP in charter toby.moncaster
- Re: [re-ECN] Other transports than TCP in charter Bob Briscoe
- Re: [re-ECN] Other transports than TCP in charter ken carlberg
- Re: [re-ECN] Other transports than TCP in charter toby.moncaster
- Re: [re-ECN] Other transports than TCP in charter Mirja Kühlewind
- Re: [re-ECN] Other transports than TCP in charter John Leslie
- Re: [re-ECN] Other transports than TCP in charter Bob Briscoe
- Re: [re-ECN] Other transports than TCP in charter John Leslie
- Re: [re-ECN] Other transports than TCP in charter Bob Briscoe
- Re: [re-ECN] Other transports than TCP in charter philip.eardley
- Re: [re-ECN] Other transports than TCP in charter Mirja Kühlewind
- Re: [re-ECN] Other transports than TCP in charter John Leslie
- Re: [re-ECN] Other transports than TCP in charter John Leslie
- Re: [re-ECN] Other transports than TCP in charter Ingemar Johansson S
- Re: [re-ECN] Other transports than TCP in charter Ingemar Johansson S
- Re: [re-ECN] Other transports than TCP in charter bo zhou