Re: [dispatch] New I-D - SPIN - on voice/video interop between app providers

Jonathan Rosenberg <jdrosen@jdrosen.net> Wed, 13 July 2022 02:37 UTC

Return-Path: <jdrosen2@gmail.com>
X-Original-To: dispatch@ietfa.amsl.com
Delivered-To: dispatch@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CFE79C157B57 for <dispatch@ietfa.amsl.com>; Tue, 12 Jul 2022 19:37:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.159
X-Spam-Level:
X-Spam-Status: No, score=-1.159 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FORGED_FROMDOMAIN=0.248, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.248, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H2=-0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=no autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2x4rkIfD0Ryj for <dispatch@ietfa.amsl.com>; Tue, 12 Jul 2022 19:37:44 -0700 (PDT)
Received: from mail-oi1-f176.google.com (mail-oi1-f176.google.com [209.85.167.176]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2BDF3C157B53 for <dispatch@ietf.org>; Tue, 12 Jul 2022 19:37:44 -0700 (PDT)
Received: by mail-oi1-f176.google.com with SMTP id u9so12851227oiv.12 for <dispatch@ietf.org>; Tue, 12 Jul 2022 19:37:44 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=3cFTIXbNj7qZ6GRmUIBnIgNaZj/u/4P1Gpc9gz+LW/4=; b=W/+hN0pf+O54jqcapHbOR5JgSQzEmVkqBMnEIBxHNC486h62z3REjgDF5THyeBm1ZI QpVkbnEVxzx7xA+13SNNwTuPYUMa7+6YSJmSx5E4lPmqheyPPYHzaY0M8sEsMybefHiN 9pkvueWxp3LW7cbB6lpNl8EfqEQXEBbeH7nCBFUeHT0VXFDMnCxggLbD4+qz7UdrnOso X2HOIQBoFrRYSStVkGkoo/IkOX3C2vX+EWeqTvIdtJ70Lk7VClZG6Y2bFBkZcat+ulwV uF8TkeQgs43MI3eKyr81qsP33v++dBxGCr7ternut8VX61GDfhnz/45/PZCR7Pv+9Izt Oc1Q==
X-Gm-Message-State: AJIora/rzbTtX0UvQ0f1XyeRoWpkb5hYuUgRerLFLA0a31sPm+AYrXLf Gxr88TzlEnxprhgBoo6boW8qBMncIhI=
X-Google-Smtp-Source: AGRyM1t7h1BBw1NT7vAQwIZwMt4ovR6vff0ao5bPpp0Xc2XWbsbtyDGF0eZa00w+0bvFx0ZaUOss0w==
X-Received: by 2002:a05:6808:1a1c:b0:33a:d57:7706 with SMTP id bk28-20020a0568081a1c00b0033a0d577706mr3712973oib.248.1657679862730; Tue, 12 Jul 2022 19:37:42 -0700 (PDT)
Received: from mail-oa1-f53.google.com (mail-oa1-f53.google.com. [209.85.160.53]) by smtp.gmail.com with ESMTPSA id a20-20020a05680802d400b0033a10770ab9sm2118575oid.19.2022.07.12.19.37.42 for <dispatch@ietf.org> (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Tue, 12 Jul 2022 19:37:42 -0700 (PDT)
Received: by mail-oa1-f53.google.com with SMTP id 586e51a60fabf-10c0d96953fso12638508fac.0 for <dispatch@ietf.org>; Tue, 12 Jul 2022 19:37:42 -0700 (PDT)
X-Received: by 2002:a05:6870:15c9:b0:101:cdac:3887 with SMTP id k9-20020a05687015c900b00101cdac3887mr620226oad.35.1657679861905; Tue, 12 Jul 2022 19:37:41 -0700 (PDT)
MIME-Version: 1.0
References: <73C345C6-F9E6-484D-94D3-51FE6A0ACD23@shockey.us> <87bkttvkr9.fsf@hobgoblin.ariadne.com>
In-Reply-To: <87bkttvkr9.fsf@hobgoblin.ariadne.com>
From: Jonathan Rosenberg <jdrosen@jdrosen.net>
Date: Tue, 12 Jul 2022 22:38:16 -0400
X-Gmail-Original-Message-ID: <CA+23+fHiaU1Ki8BtEn+pM4fDA_w=1Eb4wXe8eBLkhvKuuXaz-g@mail.gmail.com>
Message-ID: <CA+23+fHiaU1Ki8BtEn+pM4fDA_w=1Eb4wXe8eBLkhvKuuXaz-g@mail.gmail.com>
To: "Dale R. Worley" <worley@ariadne.com>
Cc: Richard Shockey <richard@shockey.us>, dispatch@ietf.org
Content-Type: multipart/alternative; boundary="00000000000051fe7d05e3a6ab14"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dispatch/oyiSyyRi4oteO6OHIhah2Kc9w4w>
Subject: Re: [dispatch] New I-D - SPIN - on voice/video interop between app providers
X-BeenThere: dispatch@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: DISPATCH Working Group Mail List <dispatch.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dispatch>, <mailto:dispatch-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dispatch/>
List-Post: <mailto:dispatch@ietf.org>
List-Help: <mailto:dispatch-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dispatch>, <mailto:dispatch-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 13 Jul 2022 02:37:47 -0000

Dale you've hit the nail on the head of "what's different". If it weren't
for DMA this would not be worth trying. Of course, even with DMA, it may
not succeed.

But - the argument that I am hoping we can use to convince those that need
to implement this - primarily that major platform providers (Google, Apple)
- is that this is better than the alternatives (the alternatives range from
do nothing, to some proprietary APIs they expose). This approach is better
because it is better for users and tries to deliver what is (i believe)
truly the goal of the DMA - to provide seamless interoperability.

Thx,
Jonathan R.


On Tue, Jul 12, 2022 at 9:58 PM Dale R. Worley <worley@ariadne.com> wrote:

> Richard Shockey <richard@shockey.us> writes:
> > There is a very very long history of trying to get vendors to
> > interoperate on advanced communications protocols. All of them have
> > been a failure.
>
> I'm hardly surprised, unfortunately.  But what is different is
>
> > This work is motivated by the recent passage of regulation in the
> > European Union - the Digital Markets Act (DMA) - which, amongst many
> > other provisions, requires that vendors of applications with a large
> > number of users enable interoperability with applications made by
> > other vendors.
>
> If the EU is really behind this, the IETF is in a position to make sure
> the legal requirements cover what people need done.
>
> Brian Rosen mentions
> > Probably want to mention Real Time Text via RFC4103 (SIP signaled like
> > voice and video).
> Since the EU wants inclusiveness, I'm sure we can get RTT and video
> included.
>
> Dale
>
> _______________________________________________
> dispatch mailing list
> dispatch@ietf.org
> https://www.ietf.org/mailman/listinfo/dispatch
>