IETF Logo Mail Archive

Re: [AVTCORE] AD Evaluation of draft-ietf-avtcore-rtp-circuit-breakers-13

Colin Perkins <csp@csperkins.org> Mon, 07 March 2016 18:48 UTC

Return-Path: <csp@csperkins.org>
X-Original-To: avt@ietfc.amsl.com
Delivered-To: avt@ietfc.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfc.amsl.com (Postfix) with ESMTP id 7C4361CD8B3; Mon, 7 Mar 2016 10:48:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.02
X-Spam-Level:
X-Spam-Status: No, score=-0.02 tagged_above=-999 required=5 tests=[RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.41]) by localhost (ietfc.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NXrRxGjNvXGF; Mon, 7 Mar 2016 10:48:31 -0800 (PST)
Received: from haggis.mythic-beasts.com (haggis.mythic-beasts.com [93.93.131.52]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfc.amsl.com (Postfix) with ESMTPS id 92BB41CD8B2; Mon, 7 Mar 2016 10:48:31 -0800 (PST)
Received: from [82.132.245.66] (port=64229 helo=[172.20.10.2]) by haggis.mythic-beasts.com with esmtpsa (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.80) (envelope-from <csp@csperkins.org>) id 1ad0Ci-0006DM-HH; Mon, 07 Mar 2016 18:48:29 +0000
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 9.2 \(3112\))
From: Colin Perkins <csp@csperkins.org>
In-Reply-To: <56D0CB64.2040705@jive.com>
Date: Mon, 07 Mar 2016 18:47:53 +0000
Content-Transfer-Encoding: quoted-printable
Message-Id: <B2F3E935-07D7-41EE-B5C4-A6066990E0A7@csperkins.org>
References: <55B4CAAF-50FB-4111-82EE-3B40B0D9C2F4@nostrum.com> <3D21CCE4-86DB-4F3D-940B-CEE2868401B6@nostrum.com> <56D0CB64.2040705@jive.com>
To: Simon Perreault <sperreault@jive.com>
X-Mailer: Apple Mail (2.3112)
X-BlackCat-Spam-Score: -28
X-Mythic-Debug: Threshold = On =
Archived-At: <http://mailarchive.ietf.org/arch/msg/avt/kqgu4Tk0YdHtg8l-NdLSwllMf04>
Cc: avt@ietf.org, draft-ietf-avtcore-rtp-circuit-breakers.all@ietf.org
Subject: Re: [AVTCORE] AD Evaluation of draft-ietf-avtcore-rtp-circuit-breakers-13
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/avt>, <mailto:avt-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/avt/>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 07 Mar 2016 18:48:32 -0000

> On 26 Feb 2016, at 22:02, Simon Perreault <sperreault@jive.com> wrote:
> Le 2016-02-24 17:39, Ben Campbell a écrit :
>> There was a brief thread on the wg list about practical implementation
>> experience. Simon started the conversation starting with [1]. Has that
>> conversation been resolved, at least to the extent it can?
> 
> As far as I am concerned:
> 
> - The authors added good text about how to handle non-conforming
> implementations.

Thanks.

> - Even with that text, non-conforming implementations are so common in
> practice as to make this whole idea inapplicable to the SIP world in
> general. I admit WebRTC might be different and having WebRTC endpoints
> implement this algorithm would probably make sense, because they would
> be less likely to have to interoperate with broken implementations.

I’m hopeful that CLUE and WebRTC will push endpoints in the direction of implementing RTP and RTCP more fully, but I certainly agree there are legacy issues. 

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

v2.23.0 | Report a Bug | By Email