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

bo zhou <zhouboyj@gmail.com> Wed, 18 November 2009 02:19 UTC

Return-Path: <zhouboyj@gmail.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 0B51D3A682C for <re-ecn@core3.amsl.com>; Tue, 17 Nov 2009 18:19:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level:
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001]
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 aV1asytIk2zH for <re-ecn@core3.amsl.com>; Tue, 17 Nov 2009 18:19:50 -0800 (PST)
Received: from mail-iw0-f186.google.com (mail-iw0-f186.google.com [209.85.223.186]) by core3.amsl.com (Postfix) with ESMTP id D83B83A67AE for <re-ecn@ietf.org>; Tue, 17 Nov 2009 18:19:49 -0800 (PST)
Received: by iwn16 with SMTP id 16so556926iwn.29 for <re-ecn@ietf.org>; Tue, 17 Nov 2009 18:19:45 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type; bh=3hXnGZ5qXU/OIQCwbA7MmcxJkcrxCQWXjwrGv9t280k=; b=qkbs/QcNizu6ZaUzrHCMmt6TMX3t6dXvJAfRYNJYzN6+e6gLJXE/plWZf6ssRUnToK XfnOwAgGgpOVwtwdHBsUEIZZJVyx5OMSje9wO+SklAbk2fXS+4pS0WC267d7lKYnl5kO LbZBEqzkEEya1C+ivigoTqvqrtcKTWJqg4g50=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=i2Q5CYdtbHOMzlj+BIozd1Y63SzPeX/P3R/2xa76w/iSdJXMkP5gDQwYutZNA0HuuX 2ueQHzYSnvkB4BpV1X+5VZ7Sz/TOz4v/tN4Dk6FLEGDG/SrQB+5nOT3q3DwoPJQtWDQE 8tgLHayB1vQJa8aVJsAHsUgOxs2++lDcSIseQ=
MIME-Version: 1.0
Received: by 10.231.20.230 with SMTP id g38mr424303ibb.49.1258510785609; Tue, 17 Nov 2009 18:19:45 -0800 (PST)
In-Reply-To: <130EBB38279E9847BAAAE0B8F9905F8C023D4625@esealmw109.eemea.ericsson.se>
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> <130EBB38279E9847BAAAE0B8F9905F8C023D4625@esealmw109.eemea.ericsson.se>
Date: Wed, 18 Nov 2009 10:19:45 +0800
Message-ID: <36a593230911171819i13890694qbaa8cddc551d9ab@mail.gmail.com>
From: bo zhou <zhouboyj@gmail.com>
To: Ingemar Johansson S <ingemar.s.johansson@ericsson.com>
Content-Type: multipart/alternative; boundary=0015176f13b6527ff504789be099
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: Wed, 18 Nov 2009 02:19:51 -0000

+1 support the proposed approach.

Regards,

Bo

On Mon, Nov 16, 2009 at 5:16 PM, Ingemar Johansson S <
ingemar.s.johansson@ericsson.com> wrote:

> 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
> >
> >
>



-- 
Regards,

Bo Zhou
China Mobile