Re: [rtcweb] WG Last Call: draft-ietf-rtcweb-use-cases-and-requirements-10 - real-time text
Barry Dingle <btdingle@gmail.com> Thu, 31 January 2013 22:23 UTC
Return-Path: <btdingle@gmail.com>
X-Original-To: rtcweb@ietfa.amsl.com
Delivered-To: rtcweb@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 102E921F8446 for <rtcweb@ietfa.amsl.com>; Thu, 31 Jan 2013 14:23:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id oOUqjveBW2Mc for <rtcweb@ietfa.amsl.com>; Thu, 31 Jan 2013 14:23:57 -0800 (PST)
Received: from mail-we0-x22e.google.com (we-in-x022e.1e100.net [IPv6:2a00:1450:400c:c03::22e]) by ietfa.amsl.com (Postfix) with ESMTP id AA59921F842C for <rtcweb@ietf.org>; Thu, 31 Jan 2013 14:23:55 -0800 (PST)
Received: by mail-we0-f174.google.com with SMTP id r6so2505430wey.5 for <rtcweb@ietf.org>; Thu, 31 Jan 2013 14:23:54 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:mime-version:in-reply-to:references:from:date:message-id :subject:to:cc:content-type; bh=B/BbLa76YNu8fS5dAOg5pwAtvXCz/96VXyt9ts4kJPA=; b=oWCEtdLQvyd2Bk2wWwmy60uQRvigUTKz6Z6v7Bi6CsKz2p3656n+kgselJWzEz0QTS DbfKdXucNuZh+NkztQIdcL0Z5rpEvxrlGROo1ScfuCyiMFfkemVay4g6FOJpH6sz5+Ma xHdpr0pZgbxB9rrjUUstE5id4R8Q29fqXrKkqH3W9h4l2brhZ/XJ0aph0Hq3lqU/1d3R 4eEME29dPPGCV8zXnLUB7f/1A4H4wGvtjH/bagb3A28B++waDvW/Rw1g7nCwXHS+M56z wFtlYKwLJksMP4wbL/aoCCAxIgtO2v9/d/e3SdvXNpWX7EujdE3WrnrL6qySZpR2qZdJ sjug==
X-Received: by 10.180.102.7 with SMTP id fk7mr11003990wib.27.1359671034656; Thu, 31 Jan 2013 14:23:54 -0800 (PST)
MIME-Version: 1.0
Received: by 10.194.82.133 with HTTP; Thu, 31 Jan 2013 14:23:34 -0800 (PST)
In-Reply-To: <51098D5A.4040009@omnitor.se>
References: <50F97303.4070906@ericsson.com> <5102FE7E.5000109@omnitor.se> <51039976.1000600@alvestrand.no> <51098D5A.4040009@omnitor.se>
From: Barry Dingle <btdingle@gmail.com>
Date: Fri, 01 Feb 2013 09:23:34 +1100
Message-ID: <CAN=GVAvrLfjouTRku99dOe45268=5iJA--O6HQ6NYiudu+n5=A@mail.gmail.com>
To: Gunnar Hellstrom <gunnar.hellstrom@omnitor.se>
Content-Type: multipart/alternative; boundary="f46d0444e7d70838d204d49d15a1"
Cc: rtcweb@ietf.org
Subject: Re: [rtcweb] WG Last Call: draft-ietf-rtcweb-use-cases-and-requirements-10 - real-time text
X-BeenThere: rtcweb@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Real-Time Communication in WEB-browsers working group list <rtcweb.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtcweb>, <mailto:rtcweb-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/rtcweb>
List-Post: <mailto:rtcweb@ietf.org>
List-Help: <mailto:rtcweb-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtcweb>, <mailto:rtcweb-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 31 Jan 2013 22:24:04 -0000
The email discussion regarding Real-time Text (RTT) in December last year showed a real interest in the need to support it in WebRTC/rtcweb. In addition, there are draft regulations in the USA and in Europe REQUIRING RTT be supported wherever there is voice communication. We need to find a way to include RTT in the Use cases and Gunnar's proposal is a very good start. It does not change any of the existing Use cases as it is an Additional feature. I strongly support the inclusion of RTT in the Use cases and Requirements. Cheers, /Barry Dingle On Thu, Jan 31, 2013 at 8:15 AM, Gunnar Hellstrom < gunnar.hellstrom@omnitor.se> wrote: > On 2013-01-26 09:53, Harald Alvestrand wrote: > > On 01/25/2013 10:51 PM, Gunnar Hellstrom wrote: > > On 2013-01-18 17:06, Magnus Westerlund wrote: > > WG, > > I would here by like to announce a two week WG last call that ends on > the 1st of February. > > Document is available here: > > > https://datatracker.ietf.org/doc/draft-ietf-rtcweb-use-cases-and-requirements/ > > > We had a good discussion in December on inclusion of the real-time text > medium. > > It was decided to document three alternative implementations with pros and > cons and after that decide which one to standardize together with the two > already mentioned media in rtcweb. > > The three alternatives were: > 1.) An RTP medium similar to audio and video, using RFC 4103 transport. > > 2.) A semi-reliable data channel with a standardized label. > > 3.) A web service based protocol, such as BOSH and XEP-0301 for real-time > text in XMPP with a well specified integration with rtcweb in a common > application. > > For all three cases, there is a need to have a specification for how calls > with audio, video and real-time text are exchanged with SIP based > environments, e.g. for interaction with RFC 6443 based emergency services. > > Text is a natural part of today's video and audio applications, so all use > cases look quite meager without it. > > I suggest that we make a rapid mini-investigation on the real-time text > alternatives and decide which variant to include in a use case. > > > I disagree with this summary on two points: > > - I think it's broken to choose between implementation strategies in an > use case. The use case needs to specify the function that we want to > achieve. > > Yes, I totally agree, I did not mean to have the discussion on solution in > the use case document. > > > > - I don't recall a declaration by the chairs that text would be included > in the use cases for RTCWEB. > > I repeat my proposal to do so. This time with a shortened, generally > expressed use case that is intended to allows any one of the three > implementation alternatives to be selected. > > > > My memory is flaky, so if you can find the declaration by the chairs, I'm > happy to let the last point pass. > > Yes, I am on my way to do the last point as well. But timing requires the > addition to the use cases to be handled now. > > > Thus: Proposal for adding real-time text to the use cases, adjusted to be > general and minimal: > > --------------------------Add real-time text in a general way in use case > draft------------------------------------------- > > 4.2.15. Simple Total Conversation service**** > > 4.2.15.1. Description**** > > ** ** > > This use-case has the audio and video communication of the Simple**** > > Video Communication Service use-case (Section 4.2.1 <http://tools.ietf.org/html/draft-ietf-rtcweb-use-cases-and-requirements-09#section-4.2.1>).**** > > ** ** > > In addition to this, the users can send and receive real-time text > in the same call.**** While one user types in the real-time text area, it**** > > is nearly immediately presented to the other user. > > By providing these three media together, the Total Conversation > service is provided. > > Interworking with SIP calls with the same media set, and with SIP > based emergency services is also in scope of this use case. **** > > ** ** > > 4.2.15.2 <#13c8d510f5a08297_section-4.3.1.2>. Derived Requirements**** > > ** ** > > F1, F2, F3, F4, F5, F6, F8, F9, F10, F20, F21,**** > > ** ** > > F39,F40, F41**** > > ** ** > > A1, A2, A3, A4, A7, A8, A9, A10, A11, A12, A27**** > > ** ** > > .............. > > F39 The browser MUST be able to handle text entry**** > > via applications to generate real-time text streams to be included in Total Conversation > calls. Real-time text and Total Conversation > Services are defined in ITU-T F.700 and F.703. **** > > ----------------------------------------------------------------**** > > F40 The browser MUST be able to send real-time text **** > > streams to a peer.**** > > ** ** > > ----------------------------------------------------------------**** > > F41 The browser MUST be able to receive, process and**** > > convey real-time text streams from peers to > applications.**** > > ----------------------------------------------------------------**** > > **** > > ** > > ..... > ** A27 The Web API MUST provide a mechanisms for **** > handling real-time text among the streams.**** > ----------------------------------------------------------------**** > > > > /Gunnar > > _______________________________________________ > rtcweb mailing list > rtcweb@ietf.org > https://www.ietf.org/mailman/listinfo/rtcweb > >
- Re: [rtcweb] WG Last Call: draft-ietf-rtcweb-use-… Gunnar Hellstrom
- Re: [rtcweb] WG Last Call: draft-ietf-rtcweb-use-… Gunnar Hellstrom
- [rtcweb] WG Last Call: draft-ietf-rtcweb-use-case… Magnus Westerlund
- Re: [rtcweb] WG Last Call: draft-ietf-rtcweb-use-… Eggert, Lars
- Re: [rtcweb] WG Last Call: draft-ietf-rtcweb-use-… Eggert, Lars
- Re: [rtcweb] WG Last Call: draft-ietf-rtcweb-use-… Stefan Håkansson LK
- Re: [rtcweb] WG Last Call: draft-ietf-rtcweb-use-… Harald Alvestrand
- Re: [rtcweb] Review of draft-ietf-rtcweb-use-case… Stefan Håkansson LK
- Re: [rtcweb] WG Last Call: draft-ietf-rtcweb-use-… Cullen Jennings (fluffy)
- Re: [rtcweb] WG Last Call: draft-ietf-rtcweb-use-… Martin Thomson
- [rtcweb] Review of draft-ietf-rtcweb-use-cases-an… Bernard Aboba
- [rtcweb] Review of draft-ietf-rtcweb-use-cases-an… Bernard Aboba
- [rtcweb] 2119 language in requirements (Re: Revie… Harald Alvestrand
- Re: [rtcweb] WG Last Call: draft-ietf-rtcweb-use-… Harald Alvestrand
- Re: [rtcweb] WG Last Call: draft-ietf-rtcweb-use-… Stefan Håkansson LK
- Re: [rtcweb] Review of draft-ietf-rtcweb-use-case… Stefan Håkansson LK
- Re: [rtcweb] WG Last Call: draft-ietf-rtcweb-use-… Matthew Kaufman (SKYPE)
- Re: [rtcweb] WG Last Call: draft-ietf-rtcweb-use-… Mary Barnes
- Re: [rtcweb] WG Last Call: draft-ietf-rtcweb-use-… Harald Alvestrand
- Re: [rtcweb] Review of draft-ietf-rtcweb-use-case… Bernard Aboba
- Re: [rtcweb] Review of draft-ietf-rtcweb-use-case… Bernard Aboba
- Re: [rtcweb] WG Last Call: draft-ietf-rtcweb-use-… Martin Thomson
- Re: [rtcweb] WG Last Call: draft-ietf-rtcweb-use-… Martin Thomson
- Re: [rtcweb] WG Last Call: draft-ietf-rtcweb-use-… Gunnar Hellstrom
- Re: [rtcweb] WG Last Call: draft-ietf-rtcweb-use-… Harald Alvestrand
- [rtcweb] Wiretapping (Re: Review of draft-ietf-rt… Harald Alvestrand
- Re: [rtcweb] WG Last Call: draft-ietf-rtcweb-use-… Barry Dingle
- Re: [rtcweb] WG Last Call: draft-ietf-rtcweb-use-… Harald Alvestrand
- Re: [rtcweb] WG Last Call: draft-ietf-rtcweb-use-… Martin Thomson
- Re: [rtcweb] WG Last Call: draft-ietf-rtcweb-use-… Harald Alvestrand
- Re: [rtcweb] WG Last Call: draft-ietf-rtcweb-use-… Stefan Håkansson LK
- Re: [rtcweb] Review of draft-ietf-rtcweb-use-case… Stefan Håkansson LK
- Re: [rtcweb] Review of draft-ietf-rtcweb-use-case… Stefan Håkansson LK
- [rtcweb] Revealing IP addresses (Re: Review of dr… Harald Alvestrand
- Re: [rtcweb] Revealing IP addresses (Re: Review o… Stefan Håkansson LK
- Re: [rtcweb] Revealing IP addresses (Re: Review o… Emil Ivov
- Re: [rtcweb] Revealing IP addresses (Re: Review o… Bernard Aboba
- Re: [rtcweb] WG Last Call: draft-ietf-rtcweb-use-… Barry Dingle
- Re: [rtcweb] WG Last Call: draft-ietf-rtcweb-use-… Dale R. Worley
- Re: [rtcweb] Playing regulator Bernard Aboba
- Re: [rtcweb] WG Last Call: draft-ietf-rtcweb-use-… Gunnar Hellstrom
- Re: [rtcweb] Playing regulator Gunnar Hellstrom
- Re: [rtcweb] Playing regulator Bernard Aboba
- Re: [rtcweb] Playing regulator Richard Shockey
- Re: [rtcweb] Revealing IP addresses (Re: Review o… Harald Alvestrand
- Re: [rtcweb] Revealing IP addresses (Re: Review o… Stefan Håkansson LK
- Re: [rtcweb] Revealing IP addresses (Re: Review o… Harald Alvestrand
- Re: [rtcweb] Revealing IP addresses (Re: Review o… Eric Rescorla
- Re: [rtcweb] Revealing IP addresses (Re: Review o… Burger Eric
- Re: [rtcweb] Playing regulator Eric Burger
- Re: [rtcweb] Revealing IP addresses (Re: Review o… Eric Rescorla
- Re: [rtcweb] Revealing IP addresses (Re: Review o… Eric Burger
- Re: [rtcweb] Revealing IP addresses (Re: Review o… Eric Rescorla
- Re: [rtcweb] Revealing IP addresses (Re: Review o… Eric Burger
- Re: [rtcweb] Revealing IP addresses (Re: Review o… John Leslie
- Re: [rtcweb] Revealing IP addresses (Re: Review o… Matthew Kaufman (SKYPE)
- Re: [rtcweb] Revealing IP addresses (Re: Review o… Dan Wing
- Re: [rtcweb] Revealing IP addresses (Re: Review o… Eric Rescorla
- Re: [rtcweb] Revealing IP addresses (Re: Review o… Matthew Kaufman (SKYPE)
- Re: [rtcweb] Revealing IP addresses (Re: Review o… Richard Barnes
- Re: [rtcweb] Revealing IP addresses (Re: Review o… Matthew Kaufman (SKYPE)
- Re: [rtcweb] WG Last Call: draft-ietf-rtcweb-use-… Magnus Westerlund