RE: [MMUSIC] I-D ACTION:draft-ietf-mmusic-sdp-media-content-04.txt

"Arnoud van Wijk" <arnoud@annies.nl> Thu, 24 August 2006 09:36 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GGBdU-0007u4-1T; Thu, 24 Aug 2006 05:36:28 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GGBdS-0007tz-Fc for mmusic@ietf.org; Thu, 24 Aug 2006 05:36:26 -0400
Received: from mx1.cambrium.nl ([217.19.16.130] helo=gollum.cambrium.nl) by ietf-mx.ietf.org with smtp (Exim 4.43) id 1GGBdR-0006SA-10 for mmusic@ietf.org; Thu, 24 Aug 2006 05:36:26 -0400
Received: (qmail 20266 invoked from network); 24 Aug 2006 09:36:23 -0000
Received: from 82-197-192-189.dsl.cambrium.nl (HELO solstice) (82.197.192.189) by gollum.cambrium.nl with SMTP; 24 Aug 2006 09:36:23 -0000
From: Arnoud van Wijk <arnoud@annies.nl>
To: 'Colin Perkins' <csp@csperkins.org>, 'Gunnar Hellström' <gunnar.hellstrom@omnitor.se>
Subject: RE: [MMUSIC] I-D ACTION:draft-ietf-mmusic-sdp-media-content-04.txt
Date: Thu, 24 Aug 2006 11:36:26 +0200
Message-ID: <000c01c6c760$c546d7e0$2400a8c0@solstice>
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Office Outlook 11
In-reply-to: <EE1B6897-3299-424D-859A-41292B0B3399@csperkins.org>
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.2962
Thread-index: AcbGjGikzEFs2dZpTbqF+o7RkQ/CpAA04/hg
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 0fa76816851382eb71b0a882ccdc29ac
Cc: 'Cullen Jennings' <fluffy@cisco.com>, 'MMusic' <mmusic@ietf.org>, "'Gonzalo. Camarillo@ericsson. com'" <Gonzalo.Camarillo@ericsson.com>
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
Errors-To: mmusic-bounces@ietf.org

Hi Colin,
I agree with Gunnar and disagree with you.
The txp content label is no different the the other content labels IMHO.
And again, it is NOT about a PSTN textphone, but about turntaking be used in
the call since it media stream contains real-time text to be used in turn
taking method.
It is not about a special phone, or limited device that is elsewise unable
to be connected.
But I am still waiting on Gonzalo's view on this.

Greetz

Arnoud

Arnoud A. T. van Wijk
AnnieS New Technology
www.AnnieS.nl
Mobile textphone (SIP): arnoud@annies.nl

> -----Original Message-----
> From: Colin Perkins [mailto:csp@csperkins.org]
> Sent: woensdag 23 augustus 2006 10:15
> To: Gunnar Hellström
> Cc: Cullen Jennings; MMusic; Gonzalo. Camarillo@ericsson. com
> Subject: Re: [MMUSIC] I-D ACTION:draft-ietf-mmusic-sdp-media-content-
> 04.txt
> 
> Gunnar,
> 
> On 23 Aug 2006, at 08:28, Gunnar Hellström wrote:
> > It is allowed to have more than one content attribute.
> 
> True, but irrelevant.
> 
> > There is no difference in characteristics of the txp attribute
> > compared to the other accepted attributes.
> > slides come from a slide showing application that has a specific
> > expected behaviour of showing one slide at a time.
> > Speaker has its source in a camera, a keyboard and a microphone
> > that likely requires some polite method to be allowed to control.
> > All have sources in devices and have a mixed meaning of device
> > indications and preparation for human behaviour when using the
> > contents.
> > There is no reason to separate out txp in this collection of
> > attributes.
> 
> I disagree, for the reasons I have previously explained.
> 
> > With the new slimmed description it is of the same size and level
> > as the others.
> 
> The "size and level" of the description was never the problem.
> Instead, there is concern that its semantics don't fit with the
> content label.
> 
> > As I remember it, the last call just asked for an improved
> > description, not questioning the idea to include the attribute.
> 
> I am explicitly questioning the inclusion of the txp label in the
> media content draft. I believe it should be removed to a separate
> draft, defining a new SDP attribute. We should also consider if the
> user-floor label should be removed too.
> 
> A simple rewording of the description of the txp label, of the type
> you are proposing, without considering the semantics, will not
> resolve this issue.
> 
> Colin
> _______________________________________________
> mmusic mailing list
> mmusic@ietf.org
> https://www1.ietf.org/mailman/listinfo/mmusic



_______________________________________________
mmusic mailing list
mmusic@ietf.org
https://www1.ietf.org/mailman/listinfo/mmusic