Re: [V3] RIPT BoF approved for IETF 107 - Draft charter below

Ross Finlayson <finlayson@live555.com> Wed, 19 February 2020 15:17 UTC

Return-Path: <finlayson@live555.com>
X-Original-To: v3@ietfa.amsl.com
Delivered-To: v3@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 273DA1200B5 for <v3@ietfa.amsl.com>; Wed, 19 Feb 2020 07:17:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level:
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_NONE=0.001] 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 UCZUJP0QpSJQ for <v3@ietfa.amsl.com>; Wed, 19 Feb 2020 07:17:53 -0800 (PST)
Received: from us.live555.com (us.live555.com [52.8.240.222]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4A514120026 for <v3@ietf.org>; Wed, 19 Feb 2020 07:17:53 -0800 (PST)
Received: from [127.0.0.1] (localhost.live555.com [IPv6:0:0:0:0:0:0:0:1]) by us.live555.com (8.15.2/8.15.2) with ESMTP id 01JFHZlr006612; Wed, 19 Feb 2020 07:17:36 -0800 (PST) (envelope-from finlayson@live555.com)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 13.0 \(3608.60.0.2.5\))
From: Ross Finlayson <finlayson@live555.com>
In-Reply-To: <B0796F47-9F6C-4242-8A96-33A9FCEF73B5@live555.com>
Date: Thu, 20 Feb 2020 04:17:35 +1300
Cc: Jonathan Rosenberg <jdrosen@five9.com>, "Cullen Jennings (fluffy)" <fluffy@cisco.com>, Jonathan Rosenberg <jdrosen@jdrosen.net>, "v3@ietf.org" <v3@ietf.org>, Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>, Justin Uberti <juberti@google.com>
Content-Transfer-Encoding: quoted-printable
Message-Id: <4D3CA306-87F0-4B23-A6DC-C76751982A8D@live555.com>
References: <BYAPR06MB43914433BF91CE216E6123A6FB150@BYAPR06MB4391.namprd06.prod.outlook.com> <CAKKJt-eKB4wxqK8Xiho2tYaqpM3_fjQYsjJh5-cf_RWd6iR8sQ@mail.gmail.com> <CA+23+fGNO86ii6q0hd3aiSdib2AT-iu3O+DmgGJXTFbFkGxLnQ@mail.gmail.com> <F72DFB60-1BA3-4CD3-9DB2-DF986F3729DE@live555.com> <BYAPR06MB4391E5B3FB4258BEF59F7BFBFB110@BYAPR06MB4391.namprd06.prod.outlook.com> <3254DED7-C105-4674-82E4-0D6968CB8744@live555.com> <CAKKJt-e5byVGLTgQAKWn=c9q1eU4mf8e=b8mucPOppPsmFnShw@mail.gmail.com> <CAOJ7v-0YiTZUQ5C7T8zOoe7f4jLWG8hYE08mC_cNuqzVLMZy6w@mail.gmail.com> <CAKKJt-ewJuBY_wu9Uhg2ijOcCRXpFy-tXzFwoKjarA3EV6-EkA@mail.gmail.com> <BYAPR06MB43911753D17BCADE1B0DF40DFB100@BYAPR06MB4391.namprd06.prod.outlook.com> <B0796F47-9F6C-4242-8A96-33A9FCEF73B5@live555.com>
To: Ross Finlayson <finlayson@live555.com>
X-Mailer: Apple Mail (2.3608.60.0.2.5)
Archived-At: <https://mailarchive.ietf.org/arch/msg/v3/r2PFjsupzrrH_3OX0AaOTY-7PVg>
Subject: Re: [V3] RIPT BoF approved for IETF 107 - Draft charter below
X-BeenThere: v3@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: <v3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/v3>, <mailto:v3-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/v3/>
List-Post: <mailto:v3@ietf.org>
List-Help: <mailto:v3-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v3>, <mailto:v3-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 19 Feb 2020 15:17:55 -0000


> On Feb 20, 2020, at 3:52 AM, Ross Finlayson <finlayson@live555.com> wrote:
> 
> OK, thanks - this explanation makes it very clear that what you’re planning is a protocol for audio/video calls *over HTTP* - and over HTTP only.  A lot of the confusion (largely on my part, I admit) about what you’re proposing would have been avoided if this had been clearer in the name of the protocol (and BOF) - i.e., if there had been an “H” in there (I would have preferred something like MoH: “Media over HTTP” :-)

On reflection, something like “RMoH” (“Real-time Media over HTTP”) would be even better, to distinguish this from other HTTP-based media delivery systems like HLS (“HTTP Live Streaming”), that don’t have the same low-latency requirements.


Ross Finlayson
Live Networks, Inc.
http://www.live555.com/