Re: [re-ECN] Other transports than TCP in charter

Bob Briscoe <rbriscoe@jungle.bt.co.uk> Fri, 13 November 2009 15:39 UTC

Return-Path: <rbriscoe@jungle.bt.co.uk>
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 BD3613A695A for <re-ecn@core3.amsl.com>; Fri, 13 Nov 2009 07:39:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.687
X-Spam-Level:
X-Spam-Status: No, score=-1.687 tagged_above=-999 required=5 tests=[AWL=0.430, BAYES_00=-2.599, DNS_FROM_RFC_BOGUSMX=1.482, 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 RH+9IiB2XdYK for <re-ecn@core3.amsl.com>; Fri, 13 Nov 2009 07:39:10 -0800 (PST)
Received: from smtp4.smtp.bt.com (smtp4.smtp.bt.com [217.32.164.151]) by core3.amsl.com (Postfix) with ESMTP id D26A43A6933 for <re-ecn@ietf.org>; Fri, 13 Nov 2009 07:39:09 -0800 (PST)
Received: from i2kc06-ukbr.domain1.systemhost.net ([193.113.197.70]) by smtp4.smtp.bt.com with Microsoft SMTPSVC(6.0.3790.3959); Fri, 13 Nov 2009 15:39:38 +0000
Received: from cbibipnt05.iuser.iroot.adidom.com ([147.149.196.177]) by i2kc06-ukbr.domain1.systemhost.net with Microsoft SMTPSVC(6.0.3790.3959); Fri, 13 Nov 2009 15:36:46 +0000
Received: From bagheera.jungle.bt.co.uk ([132.146.168.158]) by cbibipnt05.iuser.iroot.adidom.com (WebShield SMTP v4.5 MR1a P0803.399); id 1258126172844; Fri, 13 Nov 2009 15:29:32 +0000
Received: from MUT.jungle.bt.co.uk ([10.73.81.253]) by bagheera.jungle.bt.co.uk (8.13.5/8.12.8) with ESMTP id nADFTSi3014951; Fri, 13 Nov 2009 15:29:30 GMT
Message-Id: <200911131529.nADFTSi3014951@bagheera.jungle.bt.co.uk>
X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9
Date: Fri, 13 Nov 2009 15:16:13 +0000
To: ken carlberg <carlberg@g11.org.uk>
From: Bob Briscoe <rbriscoe@jungle.bt.co.uk>
In-Reply-To: <EC9F0C58-47E0-433B-BE0D-B9220DC4289E@g11.org.uk>
References: <130EBB38279E9847BAAAE0B8F9905F8C023967DD@esealmw109.eemea.ericsson.se> <36a593230911121809m2b1322cctfcc124f5b7ec707@mail.gmail.com> <200911131311.nADDBl2M011699@bagheera.jungle.bt.co.uk> <EC9F0C58-47E0-433B-BE0D-B9220DC4289E@g11.org.uk>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Scanned-By: MIMEDefang 2.56 on 132.146.168.158
X-OriginalArrivalTime: 13 Nov 2009 15:36:46.0828 (UTC) FILETIME=[1C1192C0:01CA6477]
Cc: Ingemar Johansson S <ingemar.s.johansson@ericsson.com>, 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 15:39:16 -0000

Ken,

That's what I hoped I had said - you've said it more clearly.


Bob

At 14:24 13/11/2009, ken carlberg wrote:
>Bob,
>
> > I want to manage expectations here.
>
>I'm positive the ADs are thrilled to read this :-)
>
>The thing I (and probably Ingemar) would ideally like to see is a 
>charter that doesn't preclude the introduction of proposed work 
>involving transports other than TCP.  This is perhaps a question to 
>the chairs/ADs, but would it be possible to have a charter that 
>makes a more general statement about transport protocols, and then 
>for now have a specific milestone that only identifies a work item 
>for TCP and no other transport protocol?
>
>the advantage in doing something like this is that if one of us were 
>to come up with an idea that addresses UDP via RTP/RTCP, then we 
>could introduce it to the group for their consideration without 
>having to ask for a change in the charter.  And by the same token, 
>by not listing other transports as a current milestone, we don't 
>commit the proposed group to something that could be considered too 
>much / too soon.
>
>-ken

________________________________________________________________
Bob Briscoe,                                BT Innovate & Design