Re: [rtcweb] No Plan

Iñaki Baz Castillo <ibc@aliax.net> Mon, 03 June 2013 21:25 UTC

Return-Path: <ibc@aliax.net>
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 7CC4021F8FA5 for <rtcweb@ietfa.amsl.com>; Mon, 3 Jun 2013 14:25:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.618
X-Spam-Level:
X-Spam-Status: No, score=-1.618 tagged_above=-999 required=5 tests=[AWL=0.060, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, MIME_8BIT_HEADER=0.3, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4kkGoQ8pNImf for <rtcweb@ietfa.amsl.com>; Mon, 3 Jun 2013 14:25:27 -0700 (PDT)
Received: from mail-qa0-x234.google.com (mail-qa0-x234.google.com [IPv6:2607:f8b0:400d:c00::234]) by ietfa.amsl.com (Postfix) with ESMTP id AEC9711E80F2 for <rtcweb@ietf.org>; Mon, 3 Jun 2013 14:20:33 -0700 (PDT)
Received: by mail-qa0-f52.google.com with SMTP id cr7so2133397qab.11 for <rtcweb@ietf.org>; Mon, 03 Jun 2013 14:20:33 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type:content-transfer-encoding:x-gm-message-state; bh=088tR0Kp81ILFJHR+FHmMrI4GxJvtcL0p0qWXv3zoXE=; b=TNNMDSZmIM4evXBF+J54c66iTGe4zZNrMM23DSVsNZ1feQg7Buf5TtgjzQMbPMKQzh 6Lq/E06Da9dVxE5RFV3SkhG9H8orscbFHsAgvSo7QJ06v0uRkirMJp/aboEDNyxOj1lo AM+QP22MHx9vr4tc3EkCS7/b0TZBZaPtUEyDERa71vo5gyNGYNn7IS9DAfB1RThP5cYq YAF8djsOmYYK7fILo/XrpR/TD5rGgoJRtg0BKimqqQIDxqm5SrcrWE62pgjo34/rbrdh 0EP8JxuHxL8ReJN5ekOR5UiCtrytxUiQkapuJ0ZY/HaVCTbsE8K8c55tgqDHssdPmx0S Ky/w==
X-Received: by 10.224.4.74 with SMTP id 10mr21078684qaq.38.1370294432955; Mon, 03 Jun 2013 14:20:32 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.49.26.103 with HTTP; Mon, 3 Jun 2013 14:20:12 -0700 (PDT)
In-Reply-To: <51AD0472.9020506@alum.mit.edu>
References: <51A65017.4090502@jitsi.org> <51A7BEBE.2040302@omnitor.se> <CALiegfk6XchF4U1Orpd6oJsydz-VGtBQ=CwaWrPa_KjsaQynYQ@mail.gmail.com> <51A7CD81.2060805@gmail.com> <51A835D7.9060603@omnitor.se> <CALiegfm4R=3mGqTOxBfvCfnsRg=fe=XapA6s-QQNjrsAkg5HEA@mail.gmail.com> <51A8F3EF.9080702@alum.mit.edu> <CALiegfkfz=qVM_wB21BBOypMTwTjkyG97zAmzHVpA6WHK2DA6w@mail.gmail.com> <51AD0472.9020506@alum.mit.edu>
From: =?UTF-8?Q?I=C3=B1aki_Baz_Castillo?= <ibc@aliax.net>
Date: Mon, 3 Jun 2013 23:20:12 +0200
Message-ID: <CALiegfn099xpZ4Gj950PtGWU0CPx0HZOs7aF--nMj8L6mza0Gg@mail.gmail.com>
To: Paul Kyzivat <pkyzivat@alum.mit.edu>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Gm-Message-State: ALoCoQl64orAKSWhtBQvztk8JxCh6XaZdDa3TsibZG2UUym/1E7WYB7cUmEMIzXrwhj5pCx0nSwA
Cc: "rtcweb@ietf.org" <rtcweb@ietf.org>
Subject: Re: [rtcweb] No Plan
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: Mon, 03 Jun 2013 21:25:42 -0000

2013/6/3 Paul Kyzivat <pkyzivat@alum.mit.edu>du>:

> One answer may be that the difference is that the real-time requirements for
> text aren't as demanding as they are for voice or video. But there are other
> good reasons for identifying interactive text as media. One reason is what
> we are arguing right how: the desire to negotiate properties of the
> transmission. (Should it be byte-by-byte or line-by-line.) Another is that,
> like voice and video there is likely to be a demand to record it for later
> analysis and playback, or to broadcast it to a collection of people.
>
> When text is treated as media, then treating it in parallel with other media
> makes more sense. (For instance ensuring the that the text is synchronized
> with the other media, both initially and when recorded and played back
> later.)

Well, I must recognize that now I see a real usecase: realtime
subtitles synchronized with audio/video streams. That would be much
better than the typicall subtitles embed in the video stream (because
it could be rendered as real text, so the user could choose the text
size, and so on).

Problems of standarizing text over RTP:

- Encoding

- ¿just plain text? ¿could it be HTML code instead? ¿how to send
hyperlinks? ¿how to use custom markup?

- Integrity: RTP can loose packets, do we accept that a chat can loose
"chars" or "lines"?




--
Iñaki Baz Castillo
<ibc@aliax.net>