Re: [rtcweb] RTP usage: supporting RTP ECN?

Magnus Westerlund <magnus.westerlund@ericsson.com> Mon, 10 March 2014 15:28 UTC

Return-Path: <magnus.westerlund@ericsson.com>
X-Original-To: rtcweb@ietfa.amsl.com
Delivered-To: rtcweb@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 888061A0457 for <rtcweb@ietfa.amsl.com>; Mon, 10 Mar 2014 08:28:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.851
X-Spam-Level:
X-Spam-Status: No, score=-3.851 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_SE=0.35, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham
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 WZsI-XkkCbvy for <rtcweb@ietfa.amsl.com>; Mon, 10 Mar 2014 08:28:13 -0700 (PDT)
Received: from mailgw1.ericsson.se (mailgw1.ericsson.se [193.180.251.45]) by ietfa.amsl.com (Postfix) with ESMTP id 7068D1A0438 for <rtcweb@ietf.org>; Mon, 10 Mar 2014 08:28:12 -0700 (PDT)
X-AuditID: c1b4fb2d-b7f5d8e000002a7b-e2-531dda06a72d
Received: from ESESSHC023.ericsson.se (Unknown_Domain [153.88.253.124]) by mailgw1.ericsson.se (Symantec Mail Security) with SMTP id 4A.17.10875.60ADD135; Mon, 10 Mar 2014 16:28:06 +0100 (CET)
Received: from [127.0.0.1] (153.88.183.153) by smtp.internal.ericsson.com (153.88.183.89) with Microsoft SMTP Server id 14.2.347.0; Mon, 10 Mar 2014 16:28:05 +0100
Message-ID: <531DDA05.5050707@ericsson.com>
Date: Mon, 10 Mar 2014 16:28:05 +0100
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:24.0) Gecko/20100101 Thunderbird/24.3.0
MIME-Version: 1.0
To: "Huangyihong (Rachel)" <rachel.huang@huawei.com>, "rtcweb@ietf.org" <rtcweb@ietf.org>
References: <51E6A56BD6A85142B9D172C87FC3ABBB861952E2@nkgeml501-mbs.china.huawei.com>
In-Reply-To: <51E6A56BD6A85142B9D172C87FC3ABBB861952E2@nkgeml501-mbs.china.huawei.com>
X-Enigmail-Version: 1.6
Content-Type: text/plain; charset="windows-1252"
Content-Transfer-Encoding: 8bit
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFmpkluLIzCtJLcpLzFFi42KZGfG3RpftlmywwckZKhZLO0+xW6z9187u wOTRcuQtq8eSJT+ZApiiuGxSUnMyy1KL9O0SuDIe7/zOWPCEp2J5b1ED4wquLkYODgkBE4kv /WZdjJxAppjEhXvr2boYuTiEBA4xSjxZ2MgC4SxnlHizeicjSBWvgLbE/zPr2EFsFgFVifmH 5jCB2GwCFhI3fzSygdiiAsESOw/8hqoXlDg58wkLiC0iEC3R076DGWSxsICpxK893CBhIYFQ iX/nFrCC2JwCYRLbHvUzQtwmLtHTGAQSZhYwkDiyaA4rhC0v0bx1NjNEq7ZEQ1MH6wRGwVlI ls1C0jILScsCRuZVjOy5iZk56eWGmxiBwXhwy2/dHYynzokcYpTmYFES5/3w1jlISCA9sSQ1 OzW1ILUovqg0J7X4ECMTB6dUA6OAt2blIc7TqbVfDVS3OgQJ7tme9sjCesaSOempnEqJpkd2 vE2f8DJJZbaL4hMJ58p5lYJMNakJDYZs/Jf55uuZCze1+CuIL1HtCtmwLCQk+/i1hYe1vkxM uMRsFOe5vi+7fM7BZuFz56Yd0wloVXluM0tYNXNy59XzW14mPft+NnmbY1OsjhJLcUaioRZz UXEiACcmUPAUAgAA
Archived-At: http://mailarchive.ietf.org/arch/msg/rtcweb/TgZ_GU1ktiBFHSFFcpZ2AJyZ-vM
Subject: Re: [rtcweb] RTP usage: supporting RTP ECN?
X-BeenThere: rtcweb@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Real-Time Communication in WEB-browsers working group list <rtcweb.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtcweb>, <mailto:rtcweb-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/rtcweb/>
List-Post: <mailto:rtcweb@ietf.org>
List-Help: <mailto:rtcweb-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtcweb>, <mailto:rtcweb-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 10 Mar 2014 15:28:17 -0000

On 2014-03-06 10:56, Huangyihong (Rachel) wrote:
> Hi,
> 
>  
> 
> draft-ietf-rtcweb-rtp-usage-12 doesn’t have any description regarding to
> RTP ECN RFC6679. I’m wondering why. But from my point of view, it’s
> worth some discussion. The usage of ECN is a trend though it is not
> universal in current network. Supporting it in browsers for RTP media
> transport may be good for future.
> 

Hi Rachel,
(as individual/author)

We did consider ECN for RTP and it was discussed a bit at the Stockholm
interim meeting in June 2012. My recollection of this is that the
complexity trade-off versus the potential gains and the risk for it
causing negative impact resulted in that we did not included it at this
stage.

I do think adding ECN would be a good thing, but we do need to know that
it is working reasonably well and provide a benefit sufficiently often.
I think the importance of AQM will enable more deployment of ECN also.
Thus enabling improved performance for real-time applications like
WebRTC based ones.

I would suggest that we revisit this question after the core set of
specifications have been done.

Cheers

Magnus Westerlund

----------------------------------------------------------------------
Services, Media and Network features, Ericsson Research EAB/TXM
----------------------------------------------------------------------
Ericsson AB                 | Phone  +46 10 7148287
Färögatan 6                 | Mobile +46 73 0949079
SE-164 80 Stockholm, Sweden | mailto: magnus.westerlund@ericsson.com
----------------------------------------------------------------------