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

Brian Rosen <> Tue, 12 July 2022 14:34 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 07FBBC14F748 for <>; Tue, 12 Jul 2022 07:34:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.894
X-Spam-Status: No, score=-1.894 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_HELO_NONE=0.001, T_SCC_BODY_TEXT_LINE=-0.01, T_SPF_PERMERROR=0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (2048-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id eop1kG7yhrDQ for <>; Tue, 12 Jul 2022 07:34:18 -0700 (PDT)
Received: from ( [IPv6:2607:f8b0:4864:20::131]) (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 (Postfix) with ESMTPS id 87AB6C14F728 for <>; Tue, 12 Jul 2022 07:34:18 -0700 (PDT)
Received: by with SMTP id z3so4920732ilz.5 for <>; Tue, 12 Jul 2022 07:34:18 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20210112; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=qZlFmYIIvJv252TE2QQ/IcRoKuo8p6CJi0Rm1iwYIA4=; b=HDn+yjWZ/eOlGRgtUjZDtGR2nQmA9P+HyWrqPuRgN0oK0YLHJnPdHHN+wT7b9g3P3d uV+WTIxGvNywExu0Qgqk2uNwfMngM5Jikx5d79sPRQ+7ka7RRw0N9W1SRF+eja6H75tu no5c9Kgy63RPba/1f5njBV71mhDR95m+fVqkh1oD6sW7Zxm46BBGXsZWRDQZbWy1vXDK tIUBp5O/7hcbJsMjB3fthY3qDZ8lLPX4lGar2RbMqpSGExyPN6IKff0na7FnsIAMNrZQ aC9lo+8QiSwWSkXpCCdJDZjTMSNp0SXVAjw7gt5nksYphry1sWZsnUuFBytBNTc8NfEO qrug==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20210112; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=qZlFmYIIvJv252TE2QQ/IcRoKuo8p6CJi0Rm1iwYIA4=; b=FJmZ6s5DZlzTu8FznVKp4El0IgSqCgQUlP5mDsKDddYpPXDnGww33bAAn2oREHwIlp nCI/SU2IWLi8qIBvsc5Lr4l+/Z+Q8nzJ3LFK/9Rsf206rMoakdbZZzy0cYYvUIoNgESv hOl4bQwNWr90sLzaWrSgaU4cYJOnEvPZch+7v4+DC0kWA7Ss9SgOIcy5lXEhyiGV9UO5 g4GTzpy3qmK06vt/Ca9CZ2i0G5Lc1bQruTm2ZBFm2aGGPlpuMjNWN+8EQDvkhRwUkkfC J8qT66yKaqBc+P5cznyf5WdlnX2TDwbV5fylAxNb1JpCiai1VVHiqmBGYFpNYQEsxFUk WOkQ==
X-Gm-Message-State: AJIora/Z9gefFzkHiElKMxGhvUvZ6R6GwYQHtTYKTWYKHIOlfSjsiR6G fXjK8XQixBl8VY/MZ3VZQWLHBxjqOFWMpC3T
X-Google-Smtp-Source: AGRyM1vYAvu099bW7KxpkyehIH1q0jtrYrmLxxppdFu77AMMzJw6BRCgXdY1QCAXpmM5rpwUQXkcfA==
X-Received: by 2002:a92:8747:0:b0:2da:cf0d:b615 with SMTP id d7-20020a928747000000b002dacf0db615mr12611173ilm.168.1657636457639; Tue, 12 Jul 2022 07:34:17 -0700 (PDT)
Received: from ( []) by with ESMTPSA id k16-20020a056e02135000b002dc263170b1sm3794135ilr.40.2022. (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Tue, 12 Jul 2022 07:34:16 -0700 (PDT)
From: Brian Rosen <>
Message-Id: <>
Content-Type: multipart/alternative; boundary="Apple-Mail=_449F77E9-5DF5-4720-BB98-CF75F700A33C"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3696.100.31\))
Date: Tue, 12 Jul 2022 10:34:13 -0400
In-Reply-To: <>
To: Jonathan Rosenberg <>
References: <>
X-Mailer: Apple Mail (2.3696.100.31)
Archived-At: <>
Subject: Re: [dispatch] New I-D - SPIN - on voice/video interop between app providers
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: DISPATCH Working Group Mail List <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Tue, 12 Jul 2022 14:34:23 -0000

Definitely interesting.  Would be wiling to work on it.

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.


> On Jul 12, 2022, at 10:13 AM, Jonathan Rosenberg <> wrote:
> Hi fellow dispatchers - 
> I wanted to call attention to the following draft submitted yesterday:
> <>
> 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.
> <>
> <>_______________________________________________
> dispatch mailing list