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

Jonathan Rosenberg <jdrosen@jdrosen.net> Wed, 13 July 2022 02:42 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 3D992C157B57 for <dispatch@ietfa.amsl.com>; Tue, 12 Jul 2022 19:42:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.178
X-Spam-Level:
X-Spam-Status: No, score=-1.178 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_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, 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 3bsY0iQViw4F for <dispatch@ietfa.amsl.com>; Tue, 12 Jul 2022 19:42:18 -0700 (PDT)
Received: from mail-ot1-f42.google.com (mail-ot1-f42.google.com [209.85.210.42]) (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 4893FC157B53 for <dispatch@ietf.org>; Tue, 12 Jul 2022 19:42:18 -0700 (PDT)
Received: by mail-ot1-f42.google.com with SMTP id j15-20020a056830014f00b0061c4d8736b5so5137512otp.1 for <dispatch@ietf.org>; Tue, 12 Jul 2022 19:42:18 -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=oj5ZUstbgqEKP+WIYNljbHwCPoXhEpRPqLZGix6y1C4=; b=Uh8x4V1oUdxdkv6CMjm42bjRiNI6Ug1yvJaYqWgDfTUAOs4M5++DPNbMvUBw3R9Tci FBoL2pXxKyEce2+DmCekgz5dJlDq25F4HpIriVFBprFpE/gZYzQiXDpDkokysRnP5N8N sGizs3DoHmgMz08h7q37BQ8WAAWPTdTphhCtFpr0HteVII/fIMS+2P281uXodJdInMWN hWR6wbtNQ1Yatsir5Nh31YbIf4Eph9SjaPQPQOA1vBuSebHDJBBKttTLrDyIzhsP/iD6 6JbcDbax0S6iUIpXsVDqlwVkKiIArB8IYzZFIbjjVwF66Hin0kNwLVMPtLZNnpHXx58o vFxg==
X-Gm-Message-State: AJIora+HndNfHQuAgIWbjQsdhS6/vPj9CCH8YB9y/D1CRtxTw5UD77uy DXZrcHx5plI2LZbT7uBiv8WuCRKdYig=
X-Google-Smtp-Source: AGRyM1uawqqj5sLxAatPZCrr1HJeNbkIM3mQ4FKENg9kFEQCVAR8Eh8fOPOHYDBn+I7eTlvvTiGz4A==
X-Received: by 2002:a9d:75d7:0:b0:61c:63ae:474e with SMTP id c23-20020a9d75d7000000b0061c63ae474emr476525otl.246.1657680137051; Tue, 12 Jul 2022 19:42:17 -0700 (PDT)
Received: from mail-oi1-f180.google.com (mail-oi1-f180.google.com. [209.85.167.180]) by smtp.gmail.com with ESMTPSA id t17-20020a056830225100b00616929b93d6sm4395077otd.14.2022.07.12.19.42.16 for <dispatch@ietf.org> (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Tue, 12 Jul 2022 19:42:16 -0700 (PDT)
Received: by mail-oi1-f180.google.com with SMTP id t189so12863749oie.8 for <dispatch@ietf.org>; Tue, 12 Jul 2022 19:42:16 -0700 (PDT)
X-Received: by 2002:a05:6808:1a19:b0:33a:1514:507b with SMTP id bk25-20020a0568081a1900b0033a1514507bmr726708oib.58.1657680135933; Tue, 12 Jul 2022 19:42:15 -0700 (PDT)
MIME-Version: 1.0
References: <CA+23+fFReP7fi2XmhGoxmeUph8F7HcABsFwriXPzBvuBPBXLMg@mail.gmail.com> <A7174D39-A674-44AE-B539-E94D9FDF7111@brianrosen.net> <28182e9d-757c-4fb1-3407-d900c12d435c@alum.mit.edu> <d4803464-6260-aec3-d120-a6f2cba3deb2@cs.tcd.ie>
In-Reply-To: <d4803464-6260-aec3-d120-a6f2cba3deb2@cs.tcd.ie>
From: Jonathan Rosenberg <jdrosen@jdrosen.net>
Date: Tue, 12 Jul 2022 22:42:50 -0400
X-Gmail-Original-Message-ID: <CA+23+fHoT5==65837JKo8cb-ooYJ_iebX5RhrUAOCmRvUk8bdg@mail.gmail.com>
Message-ID: <CA+23+fHoT5==65837JKo8cb-ooYJ_iebX5RhrUAOCmRvUk8bdg@mail.gmail.com>
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Cc: Paul Kyzivat <pkyzivat@alum.mit.edu>, dispatch@ietf.org
Content-Type: multipart/alternative; boundary="000000000000a754e805e3a6bb0a"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dispatch/pA8Ndol4PTNw17UIgqAnfVg4P5g>
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:42:22 -0000

Stephen and Paul -

The suggestion here to focus on phone numbers is quite intentional.

You are technically correct that, this could be made to work with email
addresses too. The difference however, is that it dramatically expands the
scope of companies that would need to implement this. If we limit ourselves
to mobile numbers - we only need two companies (two that are likely to be
compelled by DMA) to support this. The core problem we need to solve here
is adoption, and we need to optimize for that.

Thx,
Jonathan R.


On Tue, Jul 12, 2022 at 5:03 PM Stephen Farrell <stephen.farrell@cs.tcd.ie>
wrote:

>
> Hiya,
>
> On 12/07/2022 16:31, Paul Kyzivat wrote:
> > On 7/12/22 10:34 AM, Brian Rosen wrote:
> >> Definitely interesting.  Would be wiling to work on it.
> >
> > +1
>
> Same here. If we could produce a good answer here, that'd be
> great. I'm not yet sure if this proposal is a good answer,
> but trying to solve the problem and in the IETF seems like a
> good idea to me.
>
> >
> > IIUC this doesn't cover the case of a user with a computer connected to
> > the internet but without its own phone number or SMS connectivity. Any
> > thoughts on how to deal with that?
>
> That was also my main comment (following a v. quick scan of
> the draft). I'd really like an email address based option as
> well as phone numbers.
>
> Cheers,
> S.
>
>
> >
> >      Thanks,
> >      Paul
> >
> >> Is there a reason MSRP isn’t acceptable for the messaging default
> >> protocol?
> >>
> >> Probably want to mention Real Time Text via RFC4103 (SIP signaled like
> >> voice and video).
> >>
> >> Are the cloud sip extensions actually necessary to get a minimum
> >> viable protocol for this purpose?
> >>
> >> Might want to look at RFC9248 which is a SIP profile that uses the
> >> WebRTC media specs, DTLS-SRTP, and a bunch of other things to get a
> >> common client for audio, video and real time text.  Probably not
> >> entirely suitable for this purpose, but it’s a start of things that
> >> should be considered.
> >>
> >> Brian
> >>
> >>
> >>> On Jul 12, 2022, at 10:13 AM, Jonathan Rosenberg <jdrosen@jdrosen.net
> >>> <mailto:jdrosen@jdrosen.net>> wrote:
> >>>
> >>> Hi fellow dispatchers -
> >>>
> >>> I wanted to call attention to the following draft submitted yesterday:
> >>> https://www.ietf.org/archive/id/draft-rosenberg-dispatch-spin-00.txt
> >>> <https://www.ietf.org/archive/id/draft-rosenberg-dispatch-spin-00.txt>
> >>>
> >>> Abstract:
> >>> This document introduces a framework and a protocol for facilitating
> >>>     voice, video and messaging interoperability between application
> >>>     providers.  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.  While such
> >>> interoperability
> >>>     is broadly present within the public switched telephone network, it
> >>>     is not yet commonplace between over-the-top applications, such as
> >>>     Facetime, WhatsApp, and Facebook Messenger.  This document
> >>>     specifically defines the Simple Protocol for Inviting Numbers
> (SPIN)
> >>>     which is used to deliver invitations to mobile phone numbers that
> >>> can
> >>>     bootstrap subsequent communications over the Internet.
> >>>
> >>> Right now, we're looking to see if there is interest in working on
> >>> this. Comments welcome.
> >>>
> >>> Thx,
> >>> Jonathan R.
> >>>
> >>> --
> >>> Jonathan Rosenberg, Ph.D.
> >>> jdrosen@jdrosen.net <mailto:jdrosen@jdrosen.net>
> >>> http://www.jdrosen.net <http://www.jdrosen.net/>
> >>> _______________________________________________
> >>> dispatch mailing list
> >>> dispatch@ietf.org <mailto:dispatch@ietf.org>
> >>> https://www.ietf.org/mailman/listinfo/dispatch
> >>
> >>
> >> _______________________________________________
> >> dispatch mailing list
> >> dispatch@ietf.org
> >> https://www.ietf.org/mailman/listinfo/dispatch
> >
> > _______________________________________________
> > dispatch mailing list
> > dispatch@ietf.org
> > https://www.ietf.org/mailman/listinfo/dispatch
> _______________________________________________
> dispatch mailing list
> dispatch@ietf.org
> https://www.ietf.org/mailman/listinfo/dispatch
>