Re: [AVTCORE] draft-ietf-avtcore-multi-party-rtt-mix-00 Issue 1: transport

worley@ariadne.com Tue, 12 May 2020 02:14 UTC

Return-Path: <worley@alum.mit.edu>
X-Original-To: avt@ietfa.amsl.com
Delivered-To: avt@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 584123A003E for <avt@ietfa.amsl.com>; Mon, 11 May 2020 19:14:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.638
X-Spam-Level:
X-Spam-Status: No, score=-1.638 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.25, SPF_HELO_NONE=0.001, T_SPF_PERMERROR=0.01, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=comcastmailservice.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 emLSbpzCYjcS for <avt@ietfa.amsl.com>; Mon, 11 May 2020 19:14:50 -0700 (PDT)
Received: from resqmta-ch2-02v.sys.comcast.net (resqmta-ch2-02v.sys.comcast.net [IPv6:2001:558:fe21:29:69:252:207:34]) (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 CA2CB3A003D for <avt@ietf.org>; Mon, 11 May 2020 19:14:50 -0700 (PDT)
Received: from resomta-ch2-06v.sys.comcast.net ([69.252.207.102]) by resqmta-ch2-02v.sys.comcast.net with ESMTP id YKLdjcI8djoMlYKRVjrPnB; Tue, 12 May 2020 02:14:49 +0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcastmailservice.net; s=20180828_2048; t=1589249689; bh=EUHsQdxldPE8J8gjaGpN5pfEyrsNk5xEhUlcJe60tRg=; h=Received:Received:Received:Received:From:To:Subject:Date: Message-ID; b=BblbC5ixkwpHwhafeKIOYE+eLL2Tv2SfmMYUYyE8+p/6bD5pro+8H3kD8oMnbVZDj zrwnyJE0tJ9v7u0aJgEL7uyMLu12dFJaYBmMgSKTpCGWFDXVtQw9Vrd22dsXLIsoOZ KareW2qrT4d5GThoBVGOCCTFzeDG1uD5Hw83+El7N2IhLOxQuQe+n3n+X1TXolrq+s wX289ulZdJsAjKfME1dACHM2KcUN5BCyplyvO1+2u5/CAd/qEBtFF5wD+IP6kltsFc gVtEFbb1/fxAFyS4QMANdjFEW7kdL947VIvToTtpexQCK8GnwAtyEtt4XStij7ldfd sPAHbgtWzXfKg==
Received: from hobgoblin.ariadne.com ([IPv6:2601:192:4a00:430:222:fbff:fe91:d396]) by resomta-ch2-06v.sys.comcast.net with ESMTPA id YKRSjeYCuZLgwYKRTjUX9v; Tue, 12 May 2020 02:14:48 +0000
X-Xfinity-VMeta: sc=-100.00;st=legit
Received: from hobgoblin.ariadne.com (hobgoblin.ariadne.com [127.0.0.1]) by hobgoblin.ariadne.com (8.14.7/8.14.7) with ESMTP id 04C2EkCI012885; Mon, 11 May 2020 22:14:46 -0400
Received: (from worley@localhost) by hobgoblin.ariadne.com (8.14.7/8.14.7/Submit) id 04C2Ej2f012878; Mon, 11 May 2020 22:14:45 -0400
X-Authentication-Warning: hobgoblin.ariadne.com: worley set sender to worley@alum.mit.edu using -f
From: worley@ariadne.com (Dale R. Worley)
To: Gunnar =?utf-8?Q?Hellstr=C3=B6m?= <gunnar.hellstrom@ghaccess.se>
Cc: avt@ietf.org
In-Reply-To: <e6d35436-0ba4-6347-6990-46bbf5b4e5b3@ghaccess.se> (gunnar.hellstrom@ghaccess.se)
Sender: worley@ariadne.com (Dale R. Worley)
Date: Mon, 11 May 2020 22:14:45 -0400
Message-ID: <87o8qt3nmy.fsf@hobgoblin.ariadne.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/avt/NFRVlKQOrqNFsqgM4ygXDuBWuOA>
Subject: Re: [AVTCORE] draft-ietf-avtcore-multi-party-rtt-mix-00 Issue 1: transport
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/avt>, <mailto:avt-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/avt/>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 12 May 2020 02:14:52 -0000

Speaking to one aspect of one point:

Gunnar Hellstrom <gunnar.hellstrom@ghaccess.se> writes:
> That 
> means real-time transmission while text is created and accepting some 
> rare dropouts just as we do with voice and video. However, users are 
> nowadays used to text messaging where it is customary to accept a delay 
> and get the text complete in most cases, rather than to have loss. That 
> user experience might be expected from real-time text as well.

I was attending IETF meetings around the time that "real-time text"
became an important project, and my understanding is that the
deaf/hard-of-hearing community is very insistent on the real-time nature
of it, as in seeing the pacing of how the sender is typing characters.
In particular, the SIP MESSAGE method, which resembles mobile phone text
messages, was considered quite inadequate.

The possibility of lost packets was compensated for by the RTP
redundancy mechanism.

Poking around, I find https://en.wikipedia.org/wiki/Real-time_text,
which points to the Real Time Text Task Force
http://www.realtimetext.org/, which has an FAQ
http://www.realtimetext.org/FAQ containing

    Why is Real-Time Text important to people who are deaf or hard of
    hearing?

    In addition to its many applications for fully hearing people, Real-Time
    Text is important as an equivalent alternative to voice communications
    for people who are deaf and hard of hearing. It allows a more natural,
    bi-directional flow of text based conversation to take place compared
    with the "type-enter-wait-read-response-reply" technology of IM(chat)
    and SMS.

    In fact: when Real-Time Text is fully mainstream, it will be solving one
    of the biggest accessibility problems of Internet communications for
    people who are deaf or hard of hearing!

While searching for that, I found that Verizon has a big page on how to
activate RTT on various phone models
https://www.verizon.com/about/accessibility/real-time-text

Dale