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

Jonathan Rosenberg <jdrosen@jdrosen.net> Sat, 15 February 2020 00:16 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 EDB6D12006F for <v3@ietfa.amsl.com>; Fri, 14 Feb 2020 16:16:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.696
X-Spam-Level:
X-Spam-Status: No, score=-1.696 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, HTML_MESSAGE=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 jM5hthHz-dNE for <v3@ietfa.amsl.com>; Fri, 14 Feb 2020 16:16:38 -0800 (PST)
Received: from se4-iad1.servconfig.com (se4-iad1.servconfig.com [144.208.77.49]) (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 682E912002E for <v3@ietf.org>; Fri, 14 Feb 2020 16:16:38 -0800 (PST)
Received: from ecbiz261.inmotionhosting.com ([173.231.209.30]) by se4-iad1.servconfig.com with esmtps (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.92) (envelope-from <jdrosen@jdrosen.net>) id 1j2l7f-000RHJ-U4 for v3@ietf.org; Fri, 14 Feb 2020 19:16:36 -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=CHiwx5JFrfj2c6VfVVk6YKk343kMkRv0PHPDylrFFXk=; b=RU3qPmmhvYeBdl+s2QxH0lw4lw SqVfKJd5JGQDoW12oDlw3/1ivzuU1rwoM0VA+6fwYflewwP0of1fiSaDZ0I+xXm7gsp0w6ze9/8Td OBXRkcpjRu51ZFai7ZUi7aMNYmYkxDg7Ri11YaQGbeWLGcbPf6nK99RDPOFwu+GCw1O2HNAYnGP// mlZF3nAkb7kJGdK1Qp6MxEellYn5NrE1tno70rFAcQrndfyJIfTKdmiF+ROy9Fi9uwmhLdVTFoi2f QH/o26JYusmO9MjAa3oxnSG6FxDRCuER16wX5VXfV7g3P802V3wZVerZUON/ZAz/Cye1UAU3OCSvk MT/arPoA==;
Received: from mail-io1-f46.google.com ([209.85.166.46]:42950) by ecbiz261.inmotionhosting.com with esmtpsa (TLSv1.2:ECDHE-RSA-AES128-GCM-SHA256:128) (Exim 4.92) (envelope-from <jdrosen@jdrosen.net>) id 1j2l7R-00DbCG-2k for v3@ietf.org; Fri, 14 Feb 2020 19:15:50 -0500
Received: by mail-io1-f46.google.com with SMTP id z1so11875122iom.9 for <v3@ietf.org>; Fri, 14 Feb 2020 16:15:37 -0800 (PST)
X-Gm-Message-State: APjAAAWvRtuqJYOej+c0z3PCoPuaN1cCF7QsJmyTgWSvoc+H6NcNbeP9 /czzqQJCX0dDeFexWb88nwH2EIcJecQ1mvrsdrY=
X-Google-Smtp-Source: APXvYqxQAn0rQ4fQEePxNibumx6lbqU1kXFnAg4aC6EQnapZ0BlKM0CgpOPdpbjVoCVgwcV7cNlD323eUP2BuKFEMPs=
X-Received: by 2002:a5d:8cda:: with SMTP id k26mr4509953iot.26.1581725736768; Fri, 14 Feb 2020 16:15:36 -0800 (PST)
MIME-Version: 1.0
References: <BYAPR06MB43914433BF91CE216E6123A6FB150@BYAPR06MB4391.namprd06.prod.outlook.com> <CAKKJt-eKB4wxqK8Xiho2tYaqpM3_fjQYsjJh5-cf_RWd6iR8sQ@mail.gmail.com>
In-Reply-To: <CAKKJt-eKB4wxqK8Xiho2tYaqpM3_fjQYsjJh5-cf_RWd6iR8sQ@mail.gmail.com>
From: Jonathan Rosenberg <jdrosen@jdrosen.net>
Date: Fri, 14 Feb 2020 19:15:25 -0500
X-Gmail-Original-Message-ID: <CA+23+fGNO86ii6q0hd3aiSdib2AT-iu3O+DmgGJXTFbFkGxLnQ@mail.gmail.com>
Message-ID: <CA+23+fGNO86ii6q0hd3aiSdib2AT-iu3O+DmgGJXTFbFkGxLnQ@mail.gmail.com>
To: Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>
Cc: Jonathan Rosenberg <jdrosen@five9.com>, "Cullen Jennings (fluffy)" <fluffy@cisco.com>, "v3@ietf.org" <v3@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000ac20bd059e923814"
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/gcnlw0QHHUXH8HYgJuwhvgiygxCWpSDasLI4SayDByyq9LIhVUZbR67CQ7/vm /hHDJU4RXkTNWdUk1Ol2OGx3IfrIJKywOmJyM1qr8uRnWBrbSAGDVIBiLrYj5ZoIoy4PXHicFwFw 5HF8KiNxM6kSO29YenZFl5Xer5kiRqTvrH+vupzAOD1iTNszLoM5iEbcxRy+GrzXpowsUIBWsz7t tC2m2ThBbLcvEVRb/r9HWBYzE6OiUynZipmyZiM0lULr8PxcDYeuUgzgc3py4wwfFTjOngSpMgA1 FfmD5Q1Ri4JUCeduAwCaU+JKXuJDa3LaePMOFRkhzVJFWn887ct0NFXnFWKxnGmiI3p9NEdyvIai 1RA3FPo67MEDuAALBU22yFTfTjFLpPQ2bGaaic07uJ3vXyFtAA0UIYoHm1gwgFcgYa/4CwGqOUcw rXf55E8Tb8bmXq4yH8StrboPphDtmrtUkwms9uj8bOqE9zVJwqYsk3or8Gj2HmxmMxqxWK5EnsxU GLXTnONsqyI++u9UMf5U2lFyXMWcv2ZlvSNZcmGO3E8wIzvpj9IzyBpc10ZJwnPg5Vau74sFbhfo ZlF1GXLOQZdS8jFK9oM9BiWgnyTP5U+2EI3IHdVmWi9wfe+j5ndHnjKR6RgQ6scM/oDJnhhySxnS UjC8FhcgFHOAfCPQP05ugM5yDzctcfgaSyAJ9MhDnhMqABCuK7DVpOJr7QXPUVGQLHKUZefri0p8 f92Xww6vVgUVN12b1Ctfih74/Kdn2mre/hsBBxzR0ZxLcHZ9dOib+PDi4u2haUHn/BQCHjGLkVb5 6XojhwdH1Mn7J4uSyCg7jhh/Fb63kdiJpuIhZTtQmX7chX285rlMjQH/0fIV9R/2gMGq0KWAzmMf +ibVDnPQOMCpsNjBCLwXzWC5g1Gci8JLiiOdckUewCJrmQRcNgZ00xRl+f8iOCsvtWSXG9hVBIXs M154ZZ32GUyS5252yqCXA5IXj4HepxxbQBGvUiB0+JkVifJS4++53jbBRHy4XRzMJndCfnj5VlMP x+smqJveimuPWrFNgyzondpF
X-Report-Abuse-To: spam@se1-lax1.servconfig.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/v3/sAbEYQSSgWnU6497a5QIdIwnxTs>
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: Sat, 15 Feb 2020 00:16:41 -0000

RTP is in scope, in that, RIPT replaces RTP (and SDP and SIP).

Basically, the output of the codec is placed into something called a 'media
chunk' which adds a few parameters which are similar to RTP (i.e.,
timestamp) and then sent in a PUT request or GET response.

No doubt an issue of contention will be whether we should just encapsulate
RTP vs. whats in the draft.

-Jonathan R.

On Fri, Feb 14, 2020 at 6:57 PM Spencer Dawkins at IETF <
spencerdawkins.ietf@gmail.com> wrote:

> Hi, Jonathan,
>
> Thank you for this e-mail, and especially for the one describing the four
> drafts that describe what you're thinking of.
>
> I have one point of confusion, inline below.
>
> On Fri, Feb 14, 2020 at 4:00 PM Jonathan Rosenberg <jdrosen@five9.com>
> wrote:
>
>> 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.
>>
>
> I'm confused about the mention of RTP here. From my understanding so far,
> RTP is MOSTLY out of the proposed scope, but this sentence made me think
> that RTP will be changed or replaced, or encapsulated in QUIC, or something
> else wild in this proposed working group, the way SIP is being replaced. Is
> it correct that "transmission of media packets" refers to signaling
> necessary to tell each endpoint what the media path will look like (I saw
> your P2P media open issue), or are you thinking about something else?
>
> Would removing "and RTP" make a difference for the proposed working
> group's scope?
>
> Best,
>
> Spencer
>
>
>> 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.
>> --
>> V3 mailing list
>> V3@ietf.org
>> https://www.ietf.org/mailman/listinfo/v3
>>
> --
> V3 mailing list
> V3@ietf.org
> https://www.ietf.org/mailman/listinfo/v3
>


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