[AVT] RE: I-D ACTION:draft-ietf-avt-rfc2793bis-07.txt

["Arnoud van Wijk" <a.vwijk at viataal.nl>]

Hello everybody,

I have been involved with this draft with many discussions on the AVT list.
Showing how important certain aspects are of interactive texting.
Also pointing out the exact use of audio/t140c. (gateways ONLY!!! Never ever
in end-terminals!!!!)

I read the latest version of this draft:

I am speaking as one person who is using T140/RTP, text/t140 with redundancy
on a daily basis now. And as experienced user I believe that this draft is
the best compromise we can get. And states clear enough the intentions and
needs for text/t140 and audio/t140c and the need that 2 generations
redundancy is necessary where the characters are actually sent 3 times with
almost NO bandwidth increase to guarantee no characters disappear in the
real-time text conversation in case of packetloss.

My Personal preference is to make those wordings STRONGER then it is in this
draft. But I agree with the compromise wordings in this draft.

I just want to see this as an RFC and that we all use text/t140 and * cough*
*cough* audio/t140c.

Gunnar and Paul,
Well done!

AVT chair: draft is fine for RFC tract IMHO.

Greetz

Arnoud

-----Original Message-----
From: i-d-announce-bounces at ietf.org
[mailto:i-d-announce-bounces at ietf.org]On Behalf Of
Internet-Drafts at ietf.org
Sent: Monday, June 28, 2004 9:30 PM
To: i-d-announce at ietf.org
Subject: I-D ACTION:draft-ietf-avt-rfc2793bis-07.txt


A New Internet-Draft is available from the on-line Internet-Drafts
directories.


	Title		: RTP Payload for Text Conversation
	Author(s)	: G. Hellstrom, P. Jones
	Filename	: draft-ietf-avt-rfc2793bis-07.txt
	Pages		: 25
	Date		: 2004-6-25

This memo describes how to carry real time text conversation
   session contents in RTP packets. Text conversation session contents
   are specified in ITU-T Recommendation T.140.

   Two payload formats are described. One for transmitting text on a
   separate RTP session dedicated for the transmission of text, and
   one for transmitting audio and text data within one single RTP
   session.

   This RTP payload description recommends a method to include
   redundant text from already transmitted packets in order to reduce
   the risk of text loss caused by packet loss.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-avt-rfc2793bis-07.txt

To remove yourself from the I-D Announcement list, send a message to
i-d-announce-request at ietf.org with the word unsubscribe in the body of the
message.
You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce
to change your subscription settings.


Internet-Drafts are also available by anonymous FTP. Login with the username
"anonymous" and a password of your e-mail address. After logging in,
type "cd internet-drafts" and then
	"get draft-ietf-avt-rfc2793bis-07.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt


Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv at ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-avt-rfc2793bis-07.txt".

NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.


Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.



_______________________________________________
Audio/Video Transport Working Group
avt at ietf.org
https://www1.ietf.org/mailman/listinfo/avt