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

Jonathan Rosenberg <jdrosen@jdrosen.net> Tue, 18 February 2020 16:18 UTC

Return-Path: <jdrosen@jdrosen.net>
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 AD00012082B for <v3@ietfa.amsl.com>; Tue, 18 Feb 2020 08:18:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.697
X-Spam-Level:
X-Spam-Status: No, score=-1.697 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=neutral reason="invalid (public key: not available)" header.d=jdrosen.net
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 6gcxhTpg6GHy for <v3@ietfa.amsl.com>; Tue, 18 Feb 2020 08:18:11 -0800 (PST)
Received: from se1g-lax1.servconfig.com (se1g-lax1.servconfig.com [173.231.224.7]) (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 DD724120823 for <v3@ietf.org>; Tue, 18 Feb 2020 08:18:11 -0800 (PST)
Received: from ecbiz261.inmotionhosting.com ([173.231.209.30]) by se1-lax1.servconfig.com with esmtps (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.92) (envelope-from <jdrosen@jdrosen.net>) id 1j45ZR-000mWp-5h for v3@ietf.org; Tue, 18 Feb 2020 11:18:11 -0500
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=jdrosen.net ; s=default; h=Content-Type:Cc:To:Subject:Message-ID:Date:From:In-Reply-To: References:MIME-Version:Sender:Reply-To:Content-Transfer-Encoding:Content-ID: Content-Description:Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc :Resent-Message-ID:List-Id:List-Help:List-Unsubscribe:List-Subscribe: List-Post:List-Owner:List-Archive; bh=imizgzRHuc9F+E/LzrZtRwD03H1TJk0ayoJv6EGskAM=; b=g1M8+SDI64Xsq+jf7RtsnNw6EU F5azIymhGZYWXmwBWFXVGdaO5Dn7qy7s7GixEXO3JdR6HuNXw7TeMaZz6pkMkQtP34Anx90B14j9r fVv1BP1z29SjSmkcJUCRQWBOC5g0bET/l637LBeElsK+kEwDJnfUKybYCLGqvUVHkJDyP0POfsk9g nXeEdC/X8Cqv5mdqs+j2x1rBf+OYT6XWl3/gxgrQz56nwc7SxK547foIyw4FFfXZEScmSXlYgbPYy J+lizi66Y27xx/RP6xT6ZLDdRcJzTkpck8apzMv5+uhZyWQIIJc0pZrL6rC5h1n2E7zcyeT4McE4r 0KN0g+ZQ==;
Received: from mail-io1-f44.google.com ([209.85.166.44]:43706) by ecbiz261.inmotionhosting.com with esmtpsa (TLSv1.2:ECDHE-RSA-AES128-GCM-SHA256:128) (Exim 4.92) (envelope-from <jdrosen@jdrosen.net>) id 1j45ZF-00AKeN-PP for v3@ietf.org; Tue, 18 Feb 2020 11:18:00 -0500
Received: by mail-io1-f44.google.com with SMTP id n21so10772371ioo.10 for <v3@ietf.org>; Tue, 18 Feb 2020 08:17:49 -0800 (PST)
X-Gm-Message-State: APjAAAVfPcfpdO4p0haf8EOJbvsUqZoRB99Rqn/SGih7hSBpkn6wbWLs CSIsIq1Fj9D9Qz16riWOgnnwWzD+pPlpiUrhnEc=
X-Google-Smtp-Source: APXvYqzvJwRlJQ+JSPoLRn77lgbPa9TFrE4K7trLiESaL/1z6M7C0Hhr36bzQeFWopDRmXTiCkOObxhONiP+yZx1E4c=
X-Received: by 2002:a02:c856:: with SMTP id r22mr17043160jao.67.1582042669428; Tue, 18 Feb 2020 08:17:49 -0800 (PST)
MIME-Version: 1.0
References: <BYAPR06MB43914433BF91CE216E6123A6FB150@BYAPR06MB4391.namprd06.prod.outlook.com> <BN7PR03MB382733B66857CB3077294EE6A5140@BN7PR03MB3827.namprd03.prod.outlook.com>
In-Reply-To: <BN7PR03MB382733B66857CB3077294EE6A5140@BN7PR03MB3827.namprd03.prod.outlook.com>
From: Jonathan Rosenberg <jdrosen@jdrosen.net>
Date: Tue, 18 Feb 2020 11:17:40 -0500
X-Gmail-Original-Message-ID: <CA+23+fEvHQ_Cerz0SHEp7X3EK4BwTaLPRZT_KtCgpmpty54oCw@mail.gmail.com>
Message-ID: <CA+23+fEvHQ_Cerz0SHEp7X3EK4BwTaLPRZT_KtCgpmpty54oCw@mail.gmail.com>
To: "Asveren, Tolga" <tasveren@rbbn.com>
Cc: "v3@ietf.org" <v3@ietf.org>
Content-Type: multipart/alternative; boundary="00000000000054bb66059edc03ac"
X-OutGoing-Spam-Status: No, score=-1.0
X-Get-Message-Sender-Via: ecbiz261.inmotionhosting.com: authenticated_id: jdrosen+jdrosen.net/only user confirmed/virtual account not confirmed
X-Authenticated-Sender: ecbiz261.inmotionhosting.com: jdrosen@jdrosen.net
X-Originating-IP: 173.231.209.30
X-SpamExperts-Domain: ecbiz261.inmotionhosting.com
X-SpamExperts-Username: 173.231.209.30
Authentication-Results: servconfig.com; auth=pass smtp.auth=173.231.209.30@ecbiz261.inmotionhosting.com
X-SpamExperts-Outgoing-Class: ham
X-SpamExperts-Outgoing-Evidence: Combined (0.15)
X-Recommended-Action: accept
X-Filter-ID: Mvzo4OR0dZXEDF/gcnlw0UaqOYGQPGxXNcBH7FeyDZOpSDasLI4SayDByyq9LIhVUZbR67CQ7/vm /hHDJU4RXkTNWdUk1Ol2OGx3IfrIJKywOmJyM1qr8uRnWBrbSAGDVIBiLrYj5ZoIoy4PXHicFwFw 5HF8KiNxM6kSO29YenaY9bdq0EON4RNGMUh5J7R3OD1iTNszLoM5iEbcxRy+GrzXpowsUIBWsz7t tC2m2ThBbLcvEVRb/r9HWBYzE6OiUynZipmyZiM0lULr8PxcDQ859t5Zm0OOefk8LbDww7mpMgA1 FfmD5Q1Ri4JUCeduAwCaU+JKXuJDa3LaePMOFRkhzVJFWn887ct0NFXnFWKxnGmiI3p9NEdyvIai 1RA3FPo67MEDuAALBU22yFTfTjFLpPQ2bGaaic07uJ3vXyFtAA0UIYoHm1gwgFcgYa/4CwGqOUcw rXf55E8Tb8bmXq4yH8StrboPphDtmrtUkwms9uj8bOqE9zVJwqYsk3or8Gj2HmxmMxqxWK5EnsxU GLXTnONsqyI++u9UMf5U2lFyXMWcv2ZlvSNZcmGO3E8wIzvpj9IzyBpc10ZJwnPg5fBV252scOaf ybLncV5ytvzHxZEr9wH8jvEYq4G7LfdVjChLeYthZU1lM6/gbciaFgeYUOp7A73HI6oJg7w/Vof6 YmOb0cm/jlUi0C0X1wkZmvtgLQBE6JCZUWue67WpMNceukMN09FBQI4tHOZJwryo3XV1cJLZMtEz A2v+alrb+9VmH4yLdjIP1NJr6OX7MYY/QERfiWFBSy9n7PhFo6md15a2Tsdf3yBjq0Dq6ul5IJwU /YV5eNfgV4UOdT/wJO5ju7W/Y+RQq5XLdDQ0RP/Kir5QPkBrQyl4yskJmeQu647lNwN4qOsSZg+f YhVZGxpN1T+iX953am4sFN+f3QgEiBscwRdrth+1+oWTDTjsr38cN0L29hpYqOQomv/Sn+VqlxCw ALt0hbFWOgdGYXTpvNtRsd99Q/INNbtNR5q5d5O7X0it+0/kURoXh2ZFLG+oUxu75HT7xuCs3Hk6 gtbuIpMEOulDVml39K4YUCHJMS+4ayUpOtEhdxekWDmK9g==
X-Report-Abuse-To: spam@se1-lax1.servconfig.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/v3/S79BbMR31wRu_osBUZXEbV9s5SQ>
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: Tue, 18 Feb 2020 16:18:15 -0000

Tolga -

Totally agree that pragmatic "this actually works" is crucial. This is why
the following is called out in the charter:

The group will do its work in conjunction with active software
development efforts, so that implementation experience feeds directly
into protocol development.


I think your suggestion is a good one - that it is not just implementation
of the protocol, but working on practical implementation into things like -
I dont know, maybe Ribbon SBCs (hint hint) - and cloud services like amazon
and google, to gain an understanding of what works.

Thx,
Jonathan R.

On Sat, Feb 15, 2020 at 3:28 PM Asveren, Tolga <tasveren@rbbn.com> wrote:

> Definitely interesting/useful concept in general if the end result indeed
> can deliver benefits on the following aspects: HA, load-balancing,
> auto-scaling, cloud-friendliness. Having said that, just “going HTTP”
> hardly would provide satisfactory results IMHO. The issues with Cloud/real
> tiem session (mis)match are usually due to the fact that the infrastructure
> is tailored for certain type of applications, i.e. for the lack of a better
> term “web applications”. Failover, service discovery, load balancing,
> message retransmission/back-off/circuit breaking, what is understood as HA
> etc… are all areas where a real time session application is currently a
> misfit. Yes, there are workarounds/various strategies but mostly
> painful/indirect/not complete.
>
>
>
> I am optimistic that things can be made better but it really would help if
> we make sure that each strategic decision first goes through a detailed
> analysis in terms of its implementation/deployment implications/benefits
> -or lack of it-. This aspect is usually not considered as an integral part
> of protocol standardization but IMHO for this WG it should, as “making life
> easier” is one of the core goals. Furthermore, I would argue that following
> a modular approach -as much as possible- could be useful so that certain
> pieces can be plugged into the SIP/SDP world as well, e.g. HTTP
> encapsulated RTP if that happens to be the choice.
>
>
>
> Thanks,
>
> Tolga
>
>
>
> *From:* V3 <v3-bounces@ietf.org> *On Behalf Of *Jonathan Rosenberg
> *Sent:* Friday, February 14, 2020 5:00 PM
> *To:* v3@ietf.org
> *Cc:* Cullen Jennings (fluffy) <fluffy@cisco.com>
> *Subject:* [V3] RIPT BoF approved for IETF 107 - Draft charter below
>
>
> ------------------------------
>
> NOTICE: This email was received from an EXTERNAL sender
> ------------------------------
>
>
>
> Good news folks – RIPT bof was approved for IETF107 and we’ll be meeting.
> Goal is to try and get a WG formed. As such, charter discussion is in
> order. Cullen, myself and Justin worked a draft charter. Comments please:
>
>
>
>
>
> This working group will standardize a protocol, capable of operating
>
> atop HTTP/3, which supports real-time voice and video communications,
>
> including signaling, media negotiation, and transmission of media
>
> packets.
>
>
>
> The primary rationale for this new protocol is to enable deployment of
>
> real-time communications services on modern "cloud" systems. These
>
> systems are built around HTTP, and for HTTP-based applications, they
>
> enable load balancing, HA, auto-scaling, and so on. However, real-time
>
> communications protocols are based on SIP and RTP, and they cannot take
>
> advantage of these HTTP-based capabilities.
>
>
>
> It is a non-goal of this working group to replicate all of SIP and its
>
> many extensions into HTTP. The group will limit itself to supporting the
>
> functionality in widespread actual usage today.
>
>
>
> The protocol uses HTTP techniques for authentication and authorization
>
> (notably OAuth), and requires hop by hop encryption (i.e., https). The
>
> protocol will also allow for e2e media encryption, although keying is
>
> out of scope, and is expected to be handled by other protocols such as
>
> MLS. This extension will also utilize STIR for callerID.
>
>
>
> This protocol should be implementable in browsers, thick desktop
>
> clients, mobile apps and servers.
>
>
>
> The group will standardize an extension to the baseline protocol that
>
> automates the configuration necessary to achieve calling between on
>
> organization which is a customer of the other (for example, enterprise
>
> to service provider).
>
>
>
> [OPEN ISSUE: Is P2P media in or out? If in, ICE or something else ?]
>
>
>
> The group will do its work in conjunction with active software
>
> development efforts, so that implementation experience feeds directly
>
> into protocol development.
>
>
>
> The group will coordinate with the Webtranport, QUIC, HTTPbis and STIR
>
> working groups.
>
>
>
> Milestones:
>
>
>
> Dec 2020: Submit baseline protocol to IESG
>
> Mar 2021: Submit autoconfiguration protocol to IESG
>
>
>
> Thx,
>
> Jonathan R.
>
>
>
> --
>
> Jonathan Rosenberg
>
> CTO and Head of AI, Five9
>
>
>
>
> ------------------------------
>
>
> CONFIDENTIALITY NOTICE: This e-mail and any files attached may contain
> confidential information of Five9 and/or its affiliated entities. Access by
> the intended recipient only is authorized. Any liability arising from any
> party acting, or refraining from acting, on any information contained in
> this e-mail is hereby excluded. If you are not the intended recipient,
> please notify the sender immediately, destroy the original transmission and
> its attachments and do not disclose the contents to any other person, use
> it for any purpose, or store or copy the information in any medium.
> Copyright in this e-mail and any attachments belongs to Five9 and/or its
> affiliated entities.
>
>
> ------------------------------
> Notice: This e-mail together with any attachments may contain information
> of Ribbon Communications Inc. that is confidential and/or proprietary for
> the sole use of the intended recipient. Any review, disclosure, reliance or
> distribution by others or forwarding without express permission is strictly
> prohibited. If you are not the intended recipient, please notify the sender
> immediately and then delete all copies, including any attachments.
> ------------------------------
> --
> V3 mailing list
> V3@ietf.org
> https://www.ietf.org/mailman/listinfo/v3
>


-- 
Jonathan Rosenberg, Ph.D.
jdrosen@jdrosen.net
http://www.jdrosen.net