Re: [Rum] VRS Provider issues - MWI

Brian Rosen <br@brianrosen.net> Thu, 26 August 2021 19:01 UTC

Return-Path: <br@brianrosen.net>
X-Original-To: rum@ietfa.amsl.com
Delivered-To: rum@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0B6A63A0BC4 for <rum@ietfa.amsl.com>; Thu, 26 Aug 2021 12:01:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.889
X-Spam-Level:
X-Spam-Status: No, score=-1.889 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, SPF_HELO_NONE=0.001, T_SPF_PERMERROR=0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=brianrosen-net.20150623.gappssmtp.com
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 SyKjDYWNu4dG for <rum@ietfa.amsl.com>; Thu, 26 Aug 2021 12:01:30 -0700 (PDT)
Received: from mail-qt1-x82a.google.com (mail-qt1-x82a.google.com [IPv6:2607:f8b0:4864:20::82a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7F21C3A0B05 for <rum@ietf.org>; Thu, 26 Aug 2021 12:01:20 -0700 (PDT)
Received: by mail-qt1-x82a.google.com with SMTP id x5so3340733qtq.13 for <rum@ietf.org>; Thu, 26 Aug 2021 12:01:20 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=brianrosen-net.20150623.gappssmtp.com; s=20150623; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=o1bhyDkDkdbg9JvWE3CLNdguOEz33cQABR6oIke5GfA=; b=bqSlI4RV8alMJFaY9/E6NT2a43v6RpDMxnOU7LM5VZ11IjYrPV1XApeWGQpNn8Z9Dj VGn1zc6IC9BV0KHEsbgwXU8qCYsNs+eQCA7nSau16h2anDpAvKtJBleAD9/w6TDn6n84 C4jOgCGt6TvBWwsbcgVDl1t+UiX+A7Pod3dnn/wm2AHzvuP7f9GTa79we/8xugHgfqbC WcfGNLYnPZ6HslSWYdCzEKf9skvN7d7j6OxP1rsHNOEX7lEpsryLP/Titrv3XD3huJGS r8lUC5nltMjbjENvUF4hMMfTUmuurXahCQ2tRMWEfSYe45wEQ20IkxzHX++lhAkpgks/ x7HA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=o1bhyDkDkdbg9JvWE3CLNdguOEz33cQABR6oIke5GfA=; b=aMtdaNhzeJBzn8A6ihKngr1V+gLyhdMigMTGcE52srRxxVykjMJbNyIeemfTYpb8Jc p7U9b+tij1ZXDca9PCeNrAezL/XfZs12oFtnmXf9wRr+pIOxzOiNE0Q39BZlq2wa+tr7 QErwCBMH7J3Fkhb/Hlb3hqGDGhcee7irQz3F2uo2rPw9Ica9hWpwrdsBtOXWWOP1agMe cl4Y1PIVWycLX6giQFTTmW1N9mGzuZ6EZ2fY8Uo7aUyymtwfRWgY967qGgYmohuRxYdv kvAz399yZeZ3SkRPMDRTE0KcCEhqUWkfNqf1lNQu2T7sBtLihrULukHoaqWuwrQbRg2o ihBw==
X-Gm-Message-State: AOAM531azoY+qIvjyi7zN1zGk+BOlz5TP1APlQAShFynXJ3xxEU5vzF9 H+uzMTkqCadZHTiaxJRyhI/ADQ==
X-Google-Smtp-Source: ABdhPJzK5vunPx921g4JfErRwx29RMdpQNp6UkzcQ2i89ns38ZanOOkiF6DoMyHlCLLrwjMH/zYq4g==
X-Received: by 2002:ac8:5a51:: with SMTP id o17mr4697396qta.386.1630004478190; Thu, 26 Aug 2021 12:01:18 -0700 (PDT)
Received: from smtpclient.apple (dynamic-acs-24-154-121-237.zoominternet.net. [24.154.121.237]) by smtp.gmail.com with ESMTPSA id x23sm3039437qkn.29.2021.08.26.12.01.17 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Thu, 26 Aug 2021 12:01:17 -0700 (PDT)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.100.0.2.22\))
From: Brian Rosen <br@brianrosen.net>
In-Reply-To: <a0b6cf32-7aad-b0dd-e394-fde0be41e36d@alum.mit.edu>
Date: Thu, 26 Aug 2021 15:01:16 -0400
Cc: Ed Sayers <ed.sayers@purple.us>, Eugene Christensen <echristensen@sorenson.com>, "rum@ietf.org" <rum@ietf.org>, Isaac Roach <IRoach@sorenson.com>, Alexander Ospina <aospina@aslservices.com>
Content-Transfer-Encoding: quoted-printable
Message-Id: <0D136565-27AA-4FD9-B372-EEFF5532C540@brianrosen.net>
References: <53784b11-70ec-8161-a2b2-01fce0cf2e2a@alum.mit.edu> <DM8P223MB012506C6C5789D0AADCFA314A3C69@DM8P223MB0125.NAMP223.PROD.OUTLOOK.COM> <40343a8a-d8f1-6924-9d47-a87276580bb9@alum.mit.edu> <DM6PR19MB39305FD568E2931D136CBB2DFCC79@DM6PR19MB3930.namprd19.prod.outlook.com> <9C0E0E00-0FFF-49B7-9A9A-E6F4CC2C477A@brianrosen.net> <a0b6cf32-7aad-b0dd-e394-fde0be41e36d@alum.mit.edu>
To: Paul Kyzivat <pkyzivat@alum.mit.edu>
X-Mailer: Apple Mail (2.3654.100.0.2.22)
Archived-At: <https://mailarchive.ietf.org/arch/msg/rum/TQfX2RpHYcM883O47FSqsetBsZM>
Subject: Re: [Rum] VRS Provider issues - MWI
X-BeenThere: rum@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Relay User Machine <rum.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rum>, <mailto:rum-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rum/>
List-Post: <mailto:rum@ietf.org>
List-Help: <mailto:rum-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rum>, <mailto:rum-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 26 Aug 2021 19:01:44 -0000

I’m certainly willing to add a URL for retrieval to the config data.

Brian

> On Aug 26, 2021, at 2:59 PM, Paul Kyzivat <pkyzivat@alum.mit.edu> wrote:
> 
> On 8/26/21 1:33 PM, Brian Rosen wrote:
> 
>> The doc only requires MWI, which is the notification of messages waiting.  It does not assume any specific mechanism to retrieve messages.  Only the notification to the user that there are messages waiting to be retrieved.  So discussion of how messages are streamed is out of scope.
> 
> I don't think that makes sense. An interoperable RUE is a failure if the user still needs a proprietary mechanism to retrieve the video mail.
> 
> The traditional SIP mechanism for voicemail is that the user establishes a sip dialog through which the user receives saved up voice mail. As Ed notes, it is archaic in that it typically doesn't provide a way to pick and choose what you want to hear. (Potentially it can, via some interaction over a media stream established by the call as long as the device doesn't have to do anything special.)
> 
> I was thinking that there was an extension to RFC3842 that included an enumeration of individual messages with a URL to access each. But I haven't been able to find such so I may have been imagining it.
> 
> I think we could allow configuration of either a SIP or an HTTPS URL for use in retrieving video mail. The HTTPS would provide a way to offer a provider-specific GUI for managing the video mail that can be accessed by a RUE that has no proprietary parts.
> 
> 	Thanks,
> 	Paul
>