Re: [tsvwg] I-D Action: draft-khademi-tsvwg-ecn-response-01.txt

Colin Perkins <csp@csperkins.org> Wed, 20 July 2016 14:58 UTC

Return-Path: <csp@csperkins.org>
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 E139212D8F6 for <tsvwg@ietfa.amsl.com>; Wed, 20 Jul 2016 07:58:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TxjBJPUyWCKx for <tsvwg@ietfa.amsl.com>; Wed, 20 Jul 2016 07:58:28 -0700 (PDT)
Received: from balrog.mythic-beasts.com (balrog.mythic-beasts.com [IPv6:2a00:1098:0:82:1000:0:2:1]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C22B612D86F for <tsvwg@ietf.org>; Wed, 20 Jul 2016 07:58:27 -0700 (PDT)
Received: from [2001:67c:370:152:545a:493f:e682:9915] (port=55342) by balrog.mythic-beasts.com with esmtpsa (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.80) (envelope-from <csp@csperkins.org>) id 1bPsx7-0003C0-RN; Wed, 20 Jul 2016 15:58:26 +0100
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
From: Colin Perkins <csp@csperkins.org>
In-Reply-To: <20160720135351.1444.2720.idtracker@ietfa.amsl.com>
Date: Wed, 20 Jul 2016 16:58:21 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <C5E1D4DC-F52A-4F39-99D2-3A96AD7BC66C@csperkins.org>
References: <20160720135351.1444.2720.idtracker@ietfa.amsl.com>
To: Michael Welzl <michawe@ifi.uio.no>
X-Mailer: Apple Mail (2.3124)
X-BlackCat-Spam-Score: -28
X-Mythic-Debug: Threshold = On =
Archived-At: <https://mailarchive.ietf.org/arch/msg/tsvwg/BhfUb4WT8smba93aEKF7kP5oV6k>
Cc: tsvwg <tsvwg@ietf.org>
Subject: Re: [tsvwg] I-D Action: draft-khademi-tsvwg-ecn-response-01.txt
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.17
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: <https://mailarchive.ietf.org/arch/browse/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: Wed, 20 Jul 2016 14:58:36 -0000

Hi,

As I said in the meeting, this should also update Section 7.3.3 of RFC 6679, which makes the same recommendations for congestion response as RFC 3168 for RTP-related use of ECN.

Colin




> On 20 Jul 2016, at 15:53, Internet-Drafts@ietf.org wrote:
> 
> 
> A New Internet-Draft is available from the on-line Internet-Drafts directories.
> 
> 
>        Title           : Updating the Explicit Congestion Notification (ECN) Specification to Allow IETF Experimentation
>        Authors         : Naeem Khademi
>                          Michael Welzl
>                          Grenville Armitage
>                          Godred Fairhurst
> 	Filename        : draft-khademi-tsvwg-ecn-response-01.txt
> 	Pages           : 12
> 	Date            : 2016-07-20
> 
> Abstract:
>   This document relaxes recommendations and prescriptions from RFC3168
>   and RFC4774 that get in the way of experimentation with different ECN
>   strategies.  First, RFC3168 and RFC4774 state that, upon the receipt
>   by an ECN-Capable transport of a single CE packet, the congestion
>   control algorithms followed at the end-systems MUST be essentially
>   the same as the congestion control response to a single dropped
>   packet.  This document relaxes this rule in order to encourage
>   experimentation with different backoff strategies.  Second, this
>   document allows future IETF specifications to use the ECT(1)
>   codepoint in ways that are currently prohibited by RFC3168.  Third,
>   this document allows future IETF experiments to use the ECT(0) or
>   ECT(1) codepoint on any TCP segment.
> 
> 
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-khademi-tsvwg-ecn-response/
> 
> There's also a htmlized version available at:
> https://tools.ietf.org/html/draft-khademi-tsvwg-ecn-response-01
> 
> A diff from the previous version is available at:
> https://www.ietf.org/rfcdiff?url2=draft-khademi-tsvwg-ecn-response-01
> 
> 
> Please note that it may take a couple of minutes from the time of submission
> until the htmlized version and diff are available at tools.ietf.org.
> 
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
> 
> _______________________________________________
> I-D-Announce mailing list
> I-D-Announce@ietf.org
> https://www.ietf.org/mailman/listinfo/i-d-announce
> Internet-Draft directories: http://www.ietf.org/shadow.html
> or ftp://ftp.ietf.org/ietf/1shadow-sites.txt



-- 
Colin Perkins
https://csperkins.org/