Re: [tsvwg] Review of draft-carlberg-tsvwg-ecn-reactions-03

ken carlberg <carlberg@g11.org.uk> Thu, 25 October 2012 11:06 UTC

Return-Path: <carlberg@g11.org.uk>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8E18521F895B for <tsvwg@ietfa.amsl.com>; Thu, 25 Oct 2012 04:06:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.755
X-Spam-Level:
X-Spam-Status: No, score=-0.755 tagged_above=-999 required=5 tests=[AWL=-0.756, BAYES_50=0.001]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OHTVHgDXIK6P for <tsvwg@ietfa.amsl.com>; Thu, 25 Oct 2012 04:06:17 -0700 (PDT)
Received: from portland.eukhosting.net (portland.ukserverhosting.net [92.48.103.133]) by ietfa.amsl.com (Postfix) with ESMTP id A137721F8920 for <tsvwg@ietf.org>; Thu, 25 Oct 2012 04:06:15 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=g11.org.uk; s=default; h=To:References:Message-Id:Content-Transfer-Encoding:Cc:Date:In-Reply-To:From:Content-Type:Mime-Version:Subject; bh=95+maffRGsEepT23VjUKhTtBExnxTqKMaA9Rk/MuNOk=; b=yZiYfu+8YCqU8ijBOGyf7yeJiETJZ2b6WnIMpg3+1x7sMvP7e8Fr4GjAoiCwG3WaAN7Ow3YOpkGyskH2iqorZ9QGJnFjekJ8HflpbC1xt/rwLtXJ0Z+KhqRJsN8jAX85;
Received: from c-76-111-69-4.hsd1.va.comcast.net ([76.111.69.4]:49394 helo=[192.168.0.20]) by portland.eukhosting.net with esmtpa (Exim 4.80) (envelope-from <carlberg@g11.org.uk>) id 1TRLGN-0003Pt-Bc; Thu, 25 Oct 2012 11:06:11 +0000
Mime-Version: 1.0 (Apple Message framework v1283)
Content-Type: text/plain; charset="us-ascii"
From: ken carlberg <carlberg@g11.org.uk>
In-Reply-To: <201210241759.q9OHxPwP025144@bagheera.jungle.bt.co.uk>
Date: Thu, 25 Oct 2012 07:06:12 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <549A1F93-77FE-4EBB-BC2A-D845E4C9BCD4@g11.org.uk>
References: <201210191729.q9JHTarm031903@bagheera.jungle.bt.co.uk> <7C75DFAD-B8B8-485B-B019-21BBCCE92D42@gmail.com> <201210231822.q9NIM8hP021179@bagheera.jungle.bt.co.uk> <8DD13F65-E4BB-4D07-8E7A-016F72F65A84@g11.org.uk> <201210241759.q9OHxPwP025144@bagheera.jungle.bt.co.uk>
To: Bob Briscoe <bob.briscoe@bt.com>
X-Mailer: Apple Mail (2.1283)
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - portland.eukhosting.net
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - g11.org.uk
X-Source:
X-Source-Args:
X-Source-Dir:
Cc: Piers O'HANLON <p.ohanlon@cs.ucl.ac.uk>, tsvwg IETF list <tsvwg@ietf.org>
Subject: Re: [tsvwg] Review of draft-carlberg-tsvwg-ecn-reactions-03
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 25 Oct 2012 11:06:17 -0000

On Oct 24, 2012, at 1:59 PM, Bob Briscoe wrote:

> 
> The chances of much loss following ECN CE are, I assume, fairly low, so it seems very tenuous to be thinking of adding the complexity of FEC when a small amount of loss can probably be handled just fine.

depends on the event causing the congestion.  my assumption is that the vast majority of these events are brief transitive events, and as you say, can be handled fine.  however, the events I get exposed to (eg, disasters, sudden weather events, sustained flash crowds) last from tens of minutes, hours, and even days, which is much too long for certain folks.  

> I still think a nearly unresponsive algo would give you nearly exactly the same behaviour as exemption if 1% or 10% authorized users did happen, but it would still avoid boiling the network if you did get 90%. Whereas completely unresponsive would not.

yes, a fair point, which we need to make clear in the document.

-ken