Re: [dispatch] Text media handling in RTP based real-time conferences

Arnoud van Wijk <arnoud.vanwijk@realtimetext.org> Tue, 21 June 2011 09:32 UTC

Return-Path: <arnoud.vanwijk@realtimetext.org>
X-Original-To: dispatch@ietfa.amsl.com
Delivered-To: dispatch@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 79ADF21F858D for <dispatch@ietfa.amsl.com>; Tue, 21 Jun 2011 02:32:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.165
X-Spam-Level:
X-Spam-Status: No, score=-2.165 tagged_above=-999 required=5 tests=[AWL=0.433, BAYES_00=-2.599, HTML_MESSAGE=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 WjfwDpk5uWvD for <dispatch@ietfa.amsl.com>; Tue, 21 Jun 2011 02:32:34 -0700 (PDT)
Received: from mx-in01.nouzelle.com (mx-in01.nouzelle.com [87.119.194.132]) by ietfa.amsl.com (Postfix) with ESMTP id 3779A21F858B for <dispatch@ietf.org>; Tue, 21 Jun 2011 02:32:33 -0700 (PDT)
Received: from internal02.nouzelle.com (internal02.nouzelle.local [172.29.32.13]) by mx-in01.nouzelle.com (Postfix) with ESMTP id E8415125BDB for <dispatch@ietf.org>; Tue, 21 Jun 2011 11:30:57 +0200 (CEST)
Received: from mailscan.nouzelle.com (unknown [172.29.32.10]) by internal02.nouzelle.com (Postfix) with ESMTP id D662A10219AD0 for <dispatch@ietf.org>; Tue, 21 Jun 2011 11:32:31 +0200 (CEST)
X-Virus-Scanned: by amavisd-new at nouzelle.com
Received: from internal02.nouzelle.com ([172.29.32.13]) by mailscan.nouzelle.com (mailscan.nouzelle.com [172.29.32.10]) (amavisd-new, port 10026) with ESMTP id Eh9sL+bOR97G for <dispatch@ietf.org>; Tue, 21 Jun 2011 11:32:30 +0200 (CEST)
Received: from arnoud-van-wijks-macbook-pro.local (541BD3CF.cm-5-4d.dynamic.ziggo.nl [84.27.211.207]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by internal02.nouzelle.com (Postfix) with ESMTPSA id D196B10219ACE for <dispatch@ietf.org>; Tue, 21 Jun 2011 11:32:30 +0200 (CEST)
Message-ID: <4E00652E.8000804@realtimetext.org>
Date: Tue, 21 Jun 2011 11:32:30 +0200
From: Arnoud van Wijk <arnoud.vanwijk@realtimetext.org>
Organization: R3TF
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2.17) Gecko/20110414 Thunderbird/3.1.10
MIME-Version: 1.0
To: dispatch@ietf.org
References: <4DDE3268.2030307@realtimetext.org> <4DEF2BE7.9090306@realtimetext.org>
In-Reply-To: <4DEF2BE7.9090306@realtimetext.org>
Content-Type: multipart/alternative; boundary="------------060100080307050305020400"
Subject: Re: [dispatch] Text media handling in RTP based real-time conferences
X-BeenThere: dispatch@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: arnoud.vanwijk@realtimetext.org
List-Id: DISPATCH Working Group Mail List <dispatch.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dispatch>, <mailto:dispatch-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dispatch>
List-Post: <mailto:dispatch@ietf.org>
List-Help: <mailto:dispatch-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dispatch>, <mailto:dispatch-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 21 Jun 2011 09:32:35 -0000

I want to add an additional comment why this draft is important and why 
we need this work as a separate draft despite that media handling in RTP 
conferences should not matter using text, video or audio.

This draft is actually a BCP. It specifies the recommended procedures to 
follow in implementations among the enormous amount of available 
options. We have encountered the confusion many times where implementers 
are scratching behind their ears and ask what is the best way?
By publishing this BCP we increase the likelihood of interoperability of 
different solutions in a significant way, and that is an enormously 
important task for us as IETF.

Sincerely,

Arnoud van Wijk



On 08-06-11 09:59, Arnoud van Wijk wrote:
> Hi everybody,
>
> Since this draft was submitted in March ago, I like to ask DISPATCH if 
> the AVTCORE WG is the best WG for it.
> I think so, since this does handle media handling in conferences.
> We have edited this draft based on the discussions in AVT core in 
> march about SSRC multiplexing.
>
> It is very important that when using RTT streams in a multiparty call 
> that it will work with all SIP based call control environments.
> I feel that we need together with AVT to work out the details to 
> ensure that this remains possible.
>
> Several solutions are currently being implemented in RTT systems by 
> several companies and the longer we wait..the harder it gets to ensure 
> the best implementation to be used.
>
> So, this is quite important for real-world cases.
>
> I am looking forward to your feedback as always.
>
> sincerely
>
> Arnoud van Wijk
>
>
>
>> A New Internet-Draft is available from the on-line Internet-Drafts directories.
>>
>> 	Title           : Text media handling in RTP based real-time conferences
>> 	Author(s)       : G. Hellstrom, A. Wijk
>> 	Filename        : draft-hellstrom-text-conference-04.txt
>> 	Pages           : 9
>> 	Date            : 2011-03-14
>>
>> This memo specifies methods for text media handling in multi-party
>> calls, where the text is carried by the RTP protocol.  Real-time text
>> is carried in a time-sampled mode according to RFC 4103.  Centralized
>> multi-party handling of real-time text is achieved through a media
>> control unit coordinating multiple RTP text streams into one single
>> stream RTP session, identifying each stream with its own CSRC.
>> Identification for the streams are provided through the RTCP
>> messages.  This mechanism enables the receiving application to
>> present the received real-time text medium in different ways
>> according to user preferences.  Some presentation related features
>> are also described explaining suitable variations of transmission and
>> presentation of text.  Call control features are described for the
>> SIP environment, while the transport mechanisms should be suitable
>> for any IP based call control environment using RTP transport.  Two
>> alternative methods using a single RTP stream and source
>> identification inline in the text stream are also described.
>>
>> A URL for this Internet-Draft is:
>> http://www.ietf.org/internet-drafts/draft-hellstrom-text-conference-04.txt
>>
>> Internet-Drafts are also available by anonymous FTP at:
>> ftp://ftp.ietf.org/internet-drafts/
>>
>> Below is the data which will enable a MIME compliant mail reader
>> implementation to automatically retrieve the ASCII version of the
>> Internet-Draft.
>>
>> <ftp://ftp.ietf.org/internet-drafts/draft-hellstrom-text-conference-04.txt>
>>
>
>
> _______________________________________________
> dispatch mailing list
> dispatch@ietf.org
> https://www.ietf.org/mailman/listinfo/dispatch