Re: [AVTCORE] RFC6679 ECN in RTP: intent of ect = 0, 1, or random?

Colin Perkins <> Thu, 05 November 2015 07:35 UTC

Return-Path: <>
Received: from localhost ( []) by (Postfix) with ESMTP id 150881B3B79 for <>; Wed, 4 Nov 2015 23:35:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.3
X-Spam-Status: No, score=-1.3 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, J_CHICKENPOX_36=0.6] autolearn=no
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id NmpCn63w6N1c for <>; Wed, 4 Nov 2015 23:35:01 -0800 (PST)
Received: from ( [IPv6:2a00:1098:0:86:1000:0:2:1]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 058EA1B3B77 for <>; Wed, 4 Nov 2015 23:35:01 -0800 (PST)
Received: from [2001:c40:0:3048:8887:19c2:7578:721a] (port=63397 by with esmtpsa (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.80) (envelope-from <>) id 1ZuF4O-0006rH-7b; Thu, 05 Nov 2015 07:34:53 +0000
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2104\))
From: Colin Perkins <>
In-Reply-To: <>
Date: Thu, 5 Nov 2015 16:34:32 +0900
Content-Transfer-Encoding: quoted-printable
Message-Id: <>
References: <> <> <>
To: Bob Briscoe <>
X-Mailer: Apple Mail (2.2104)
X-BlackCat-Spam-Score: -28
X-Mythic-Debug: Threshold = On =
Archived-At: <>
Cc: Ingemar Johansson S <>, Magnus Westerlund <>, Ken Carlberg <>,
Subject: Re: [AVTCORE] RFC6679 ECN in RTP: intent of ect = 0, 1, or random?
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Thu, 05 Nov 2015 07:35:03 -0000


> On 4 Nov 2015, at 17:50, Bob Briscoe <> wrote:
> Piers,
> I realised I didn't send the mail thanking you for your response. Thank you - v useful, and confirmation of my vague memory of events.
> 1. Would the authors (and wider community) be happy to allow ECT(1) not to be set-aside for future anti-cheating use, as long as there was another way, in principle, for the sender to check for cheating?

I have no objection. You might check with the RMCAT chairs, since some of their proposals make use of ECN with RTP, but I doubt this will be a problem.

> For TCP, we worked out a way for the sender to check for cheating without burning a codepoint - by the sender introducing one or two CE codepoints of its own, and checking the receiver reports them. Would this be harder for RTP? Are the receiver reports deterministic enough for the sender to determine whether codepoints it injected are correctly counted in the next report?

The sender could easily set a CE mark on a small number of packets it’s sending. For unicast cases, where there’s an explicit control loop, it should be able to correlate this with the returned RTCP feedback. Where it might be difficult is with open loop layered multicast congestion control, where some receivers might see the CE mark and drop a layer since they don’t know it’s a synthetic mark.


> 2. A couple of days after I posted the original question, we posted the -00 individual draft aiming to start the process of repurposing ECT(1). You will see the sentence in the scope section <>
> See security considerations for discussion on feedback integrity checking.
> Bob
> On 19/10/15 10:15, Piers O'Hanlon wrote:
>> Hi Bob,
>> I think the reasoning was that ECT(1)/random could potentially be used to detect cheating/failures as mentioned in section 7.4, but I can't see that it's going to make a lot of difference if ECT(1) is not used.
>> Piers
>> On 17 Oct 2015, at 22:59, Bob Briscoe wrote:
>>> Guys,
>>> [Ignore last identical email - I left the list off the distr in error]
>>> I'm writing a draft to propose a new use for ECT(1).
>>> In reading RFC6679, It says that the there is no intent to use an ECN nonce.
>>> Also it says the receiver might want to advise the sender not to use ect=random, if its behind a header compression link. And that ect=0 is recommended and the default.
>>> But it doesn't seem to actually say why a sender might send ECT(1) instead of ECT(0). Or why a sender might use the two randomly. Or why a receiver might ask for ect=1, or ect=random.
>>> I'm trying to work out whether there would be any detriment to RFC6679 if it couldn't use ECT(1). It looks like not.
>>> Bob
>>> -- 
>>> ________________________________________________________________
>>> Bob Briscoe
> -- 
> ________________________________________________________________
> Bob Briscoe

Colin Perkins