IETF Logo Mail Archive

Re: congestion control? - (was Re: Appointment of a Transport Area Director)

Toerless Eckert <eckert@cisco.com> Thu, 07 March 2013 04:23 UTC

Return-Path: <eckert@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0B74021F85B1 for <ietf@ietfa.amsl.com>; Wed, 6 Mar 2013 20:23:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.785
X-Spam-Level:
X-Spam-Status: No, score=-9.785 tagged_above=-999 required=5 tests=[AWL=0.814, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id teTYiBYFS80m for <ietf@ietfa.amsl.com>; Wed, 6 Mar 2013 20:23:23 -0800 (PST)
Received: from mtv-iport-3.cisco.com (mtv-iport-3.cisco.com [173.36.130.14]) by ietfa.amsl.com (Postfix) with ESMTP id 6E94F21F8477 for <ietf@ietf.org>; Wed, 6 Mar 2013 20:23:23 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1161; q=dns/txt; s=iport; t=1362630203; x=1363839803; h=date:from:to:cc:subject:message-id:references: mime-version:in-reply-to; bh=vYMgeaS9fSirNv276z0rJ64YUZpoz0z04X6CnU589AM=; b=Z8OK+S1tzZxQsgF6vUd1bBsWFs2bnFRHh8caoexE6k1FVT8hqZ9AwYSr B66YicPXuVoYVfKZPc++YsSNO6oc6dBl8YWeODdMi+NvnnV1WprHwgrOj YkaqxvyFaugLTQ2fAiwOCbvxpZk4oHstG9w/ksqMq4zt5eEbg8JCsvdVl g=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av8EAAgWOFGrRDoI/2dsb2JhbABDxEaBZBZzgisBAQEEOjEOEAsYCSUPBUkTFId+u1aPDAeCX2EDiGyNXgGQcIMq
X-IronPort-AV: E=Sophos;i="4.84,799,1355097600"; d="scan'208";a="71941995"
Received: from mtv-core-3.cisco.com ([171.68.58.8]) by mtv-iport-3.cisco.com with ESMTP; 07 Mar 2013 04:23:18 +0000
Received: from mcast-linux1.cisco.com (mcast-linux1.cisco.com [172.27.244.121]) by mtv-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id r274MvkZ016348 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 7 Mar 2013 04:22:57 GMT
Received: from mcast-linux1.cisco.com (localhost.cisco.com [127.0.0.1]) by mcast-linux1.cisco.com (8.13.8/8.13.8) with ESMTP id r274KC4T024475; Wed, 6 Mar 2013 20:20:27 -0800
Received: (from eckert@localhost) by mcast-linux1.cisco.com (8.13.8/8.13.8/Submit) id r274KBe0024474; Wed, 6 Mar 2013 20:20:11 -0800
Date: Wed, 06 Mar 2013 20:20:11 -0800
From: Toerless Eckert <eckert@cisco.com>
To: "Eggert, Lars" <lars@netapp.com>
Subject: Re: congestion control? - (was Re: Appointment of a Transport Area Director)
Message-ID: <20130307042011.GB20642@cisco.com>
References: <CAKFn1SEuNSHQMXKH2nc6E3Za=La7-jNfB+DW_exOsfjFrFYwfQ@mail.gmail.com> <3061.1362422679@sandelman.ca> <D4D47BCFFE5A004F95D707546AC0D7E91F784CDA@SACEXCMBX01-PRD.hq.netapp.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <D4D47BCFFE5A004F95D707546AC0D7E91F784CDA@SACEXCMBX01-PRD.hq.netapp.com>
User-Agent: Mutt/1.4.2.2i
Cc: "<end2end-interest@postel.org>" <end2end-interest@postel.org>, IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 07 Mar 2013 04:23:25 -0000

On Tue, Mar 05, 2013 at 07:52:56AM +0000, Eggert, Lars wrote:
> On Mar 4, 2013, at 19:44, Michael Richardson <mcr+ietf@sandelman.ca> wrote:
> > The Transport Area has all of the groups that deal with transport
> > protocols that need to do congestion control.   Further, the (current)
> > split of work means that all of the groups that need congestion
> > oversight would be cared for by the position that is currently becoming
> > empty as Wes leaves.
> 
> Also, other areas frequently build protocols that need review from a congestion control perspective (do they back of under loss, can they even detect loss, etc.)
> 
> Inside the area, there is typically enough CC clue applied by the TSV community as a whole. It's outside the area where the TSV AD as a person gets involved a lot.
> 
> Lars

Sure, but that could equally well be seen as a problem of the way how the
IESG chooses to perform its business. There are enough experts that
could consult whether its in role of directorates or else. They may just
not want to take on an AD role.

And there are a lot more TSV friction points with whats going on in the IETF
than just CC.

v2.23.0 | Report a Bug | By Email