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

"Ingemar Johansson S" <ingemar.s.johansson@ericsson.com> Mon, 16 November 2009 09:16 UTC

Return-Path: <ingemar.s.johansson@ericsson.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 46DBB3A690C for <re-ecn@core3.amsl.com>; Mon, 16 Nov 2009 01:16:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.646
X-Spam-Level:
X-Spam-Status: No, score=-5.646 tagged_above=-999 required=5 tests=[AWL=0.603, BAYES_00=-2.599, HELO_EQ_SE=0.35, RCVD_IN_DNSWL_MED=-4]
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 dFAXTWTQRNEZ for <re-ecn@core3.amsl.com>; Mon, 16 Nov 2009 01:16:52 -0800 (PST)
Received: from mailgw4.ericsson.se (mailgw4.ericsson.se [193.180.251.62]) by core3.amsl.com (Postfix) with ESMTP id ACAFA3A6901 for <re-ecn@ietf.org>; Mon, 16 Nov 2009 01:16:51 -0800 (PST)
X-AuditID: c1b4fb3e-b7b90ae000005e1e-c0-4b01187d4f78
Received: from esealmw126.eemea.ericsson.se (Unknown_Domain [153.88.253.125]) by mailgw4.ericsson.se (Symantec Mail Security) with SMTP id FE.9A.24094.D78110B4; Mon, 16 Nov 2009 10:16:45 +0100 (CET)
Received: from esealmw109.eemea.ericsson.se ([153.88.200.2]) by esealmw126.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.3959); Mon, 16 Nov 2009 10:16:45 +0100
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: Mon, 16 Nov 2009 10:16:44 +0100
Message-ID: <130EBB38279E9847BAAAE0B8F9905F8C023D4625@esealmw109.eemea.ericsson.se>
In-Reply-To: <200911131529.nADFTSi3014951@bagheera.jungle.bt.co.uk>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [re-ECN] Other transports than TCP in charter
Thread-Index: Acpkd8w7hRn/TW+MTZqtC7wslfNTQACJY38A
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> <200911131529.nADFTSi3014951@bagheera.jungle.bt.co.uk>
From: "Ingemar Johansson S" <ingemar.s.johansson@ericsson.com>
To: "Bob Briscoe" <rbriscoe@jungle.bt.co.uk>, "ken carlberg" <carlberg@g11.org.uk>
X-OriginalArrivalTime: 16 Nov 2009 09:16:45.0137 (UTC) FILETIME=[8470E410:01CA669D]
X-Brightmail-Tracker: AAAAAA==
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: Mon, 16 Nov 2009 09:16:53 -0000

Hi

As stated earlier I agree on the proposed approach below.

/Ingemar 

> -----Original Message-----
> From: Bob Briscoe [mailto:rbriscoe@jungle.bt.co.uk] 
> Sent: den 13 november 2009 16:16
> To: ken carlberg
> Cc: Ingemar Johansson S; bo zhou; re-ecn@ietf.org
> Subject: Re: [re-ECN] Other transports than TCP in charter
> 
> 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 
> 
>