Re: [Rum] Real-time text in WebRTC is discussed in mmusic - a topic closely telated to rum
Brian Rosen <br@brianrosen.net> Tue, 27 August 2019 19:49 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 D5962120113 for <rum@ietfa.amsl.com>; Tue, 27 Aug 2019 12:49:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.888
X-Spam-Level:
X-Spam-Status: No, score=-1.888 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, T_SPF_PERMERROR=0.01, URIBL_BLOCKED=0.001] 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 y-QW-kwJa66t for <rum@ietfa.amsl.com>; Tue, 27 Aug 2019 12:49:01 -0700 (PDT)
Received: from mail-qt1-x835.google.com (mail-qt1-x835.google.com [IPv6:2607:f8b0:4864:20::835]) (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 997C91200FF for <rum@ietf.org>; Tue, 27 Aug 2019 12:49:01 -0700 (PDT)
Received: by mail-qt1-x835.google.com with SMTP id u34so297404qte.2 for <rum@ietf.org>; Tue, 27 Aug 2019 12:49:01 -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=og3ySeOdJykWlZeNjK8sbuqm2ux8R3WsFJPSrajzZo8=; b=Q6C7QFB6BpSsK4S3aFks2su0r6J6l+qfJTd69ozS+V3VDbXiIlkHuww4TvGFQBVtrw ev3YYreVZxCnABBBcP/s9ZMi/KlExqFLjCN6HPhz2ZzQHIeotlNE1UOVBqvBwzzSCtwx n/vq4soV4+AzYINEZ4y3iWPCbypD4wNbfKPWRpkK4kUA8+ZyyqLLQcobp+x4wqdLkVtg wOR90DPq+syubq/F2dswGK3nwJ9DqeKPFjW2YG9v9blG9aOhDe2642r/jK0mcRn1ATUW 1Zl7VRsJsmqZ92905B+lhjftE2oCpLrGVVOWIaNdkd/ivaOdVBusK5pjSAjtGhv7fx0d ECxg==
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=og3ySeOdJykWlZeNjK8sbuqm2ux8R3WsFJPSrajzZo8=; b=UH4f/TGO+akI5D1hcUZgSjeBz/6al49L1zPlgh5ZYa1PLMg+n2XJbrgpfyQd4mofYD 1SuS+wNR+WKKk69QUQiblGwpjHWdaw8oo3RRyMqebRPSERgiF6Cyp+pTE0oNwIvxrvxE ySfRhojtLn6B686UNKk/PQ/QkvKV42cwRdOn+LCuwYg1r4gDm7xwj9BPII8bEsUCllzw IngPvc67p4uBDUqY8QTaSAl9fXJuNxdSZ5s3JxSqrmX9lDmNYwvnaND2YltoYiKC8SDc gWedD7CRe+i+S7NssdQ6/H9L3+o1rUgZMBFHEB0Xw6roJ6dVuFQbchTRpaHmI8Ge482G 4Gjw==
X-Gm-Message-State: APjAAAU8A8sIx7/DY5s2HKv9FNg6zoBJnVPKEq0znWKnjibvP1gXZZxa 38m06nXHWzVEcXKaiWxE9nhcuZN9F/4=
X-Google-Smtp-Source: APXvYqwqdTbXHnhuJXeZ6D2yNttnjlvJ1XBAoAEVXVbMaXc7aE7xAKEyHcfHb3m7D4QtUKjute0vgQ==
X-Received: by 2002:ac8:3315:: with SMTP id t21mr571091qta.392.1566935340213; Tue, 27 Aug 2019 12:49:00 -0700 (PDT)
Received: from brians-mbp-2369.lan ([24.154.122.195]) by smtp.gmail.com with ESMTPSA id o127sm185506qkd.104.2019.08.27.12.48.59 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 27 Aug 2019 12:48:59 -0700 (PDT)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\))
From: Brian Rosen <br@brianrosen.net>
In-Reply-To: <9a14addd-9a1c-6130-3880-a814be717323@omnitor.se>
Date: Tue, 27 Aug 2019 15:48:59 -0400
Cc: rum@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <D375F138-E997-4436-9A90-A5583CD0820B@brianrosen.net>
References: <9a14addd-9a1c-6130-3880-a814be717323@omnitor.se>
To: Gunnar Hellström <gunnar.hellstrom@omnitor.se>
X-Mailer: Apple Mail (2.3445.104.11)
Archived-At: <https://mailarchive.ietf.org/arch/msg/rum/Lk90w0qStmiAmHoIw_mWFTOE3pY>
Subject: Re: [Rum] Real-time text in WebRTC is discussed in mmusic - a topic closely telated to rum
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: Tue, 27 Aug 2019 19:49:04 -0000
The problem of conference 4103 RTT is high on my list of work I need to get done. So, I’m motivated to help out. The basic problem is that we’re going to get very inconsistent UI doing it that way, because of how systems will handle backspace of one party that extends beyond responses from other parties: Alice: I waited for you Bob: I didn’t see you Alice: sorry And then Alice types 12 backspaces. What should happen? Brian > On Aug 27, 2019, at 9:52 AM, Gunnar Hellström <gunnar.hellstrom@omnitor.se> wrote: > > Hi, > > A topic is currently discussed in mmusic that is closely related to rum. it is WebRTC transport of real-time text. > > The draft is draft-holmberg-mmusic-t140-usage-data-channel . > > A good point to start reading could be: > > https://mailarchive.ietf.org/arch/browse/mmusic/?gbt=1&q=draft-holmberg-mmusic-t140-usage-data-channel > > Please check if the current state of the discussion suits rum! > > The only issue that seems to be remaining is how to transport RTT data to and from a conference server that combines all traffic per media in a meeting in one data stream. That is not very elegantly specified for RFC 4103 transport of RTT in RTP either, so we might want to do a rapid action together to solve the multi-party RTT MCU case in a general and consistent way. > > Regards > > Gunnar > > -- > ----------------------------------------- > Gunnar Hellström > Omnitor > gunnar.hellstrom@omnitor.se > +46 708 204 288 > >
- [Rum] Real-time text in WebRTC is discussed in mm… Gunnar Hellström
- Re: [Rum] Real-time text in WebRTC is discussed i… Brian Rosen
- Re: [Rum] Real-time text in WebRTC is discussed i… Gunnar Hellström
- Re: [Rum] Real-time text in WebRTC is discussed i… Brian Rosen
- Re: [Rum] Real-time text in WebRTC is discussed i… Gunnar Hellström
- Re: [Rum] Real-time text in WebRTC is discussed i… Paul Kyzivat
- Re: [Rum] [EXT] Re: Real-time text in WebRTC is d… Malloy, Jim
- Re: [Rum] [EXT] Re: Real-time text in WebRTC is d… Paul Kyzivat
- Re: [Rum] Real-time text in WebRTC is discussed i… Brian Rosen
- Re: [Rum] [EXT] Re: Real-time text in WebRTC is d… Brian Rosen
- Re: [Rum] [EXT] Re: Real-time text in WebRTC is d… Paul Kyzivat
- Re: [Rum] [EXT] Re: Real-time text in WebRTC is d… Brian Rosen
- Re: [Rum] [EXT] Re: Real-time text in WebRTC is d… Paul Kyzivat
- Re: [Rum] [EXT] Re: Real-time text in WebRTC is d… Brian Rosen
- Re: [Rum] [EXT] Re: Real-time text in WebRTC is d… Malloy, Jim
- Re: [Rum] [EXT] Re: Real-time text in WebRTC is d… Gunnar Hellström
- Re: [Rum] [EXT] Re: Real-time text in WebRTC is d… John Martin
- Re: [Rum] [EXT] Re: Real-time text in WebRTC is d… Paul Kyzivat
- Re: [Rum] [EXT] Re: Real-time text in WebRTC is d… Gunnar Hellström
- Re: [Rum] [EXT] Re: Real-time text in WebRTC is d… Gunnar Hellström
- Re: [Rum] [EXT] Re: Real-time text in WebRTC is d… Brian Rosen
- Re: [Rum] [EXT] Re: Real-time text in WebRTC is d… Gunnar Hellström