Re: [AVT] I-D ACTION:draft-ietf-avt-rfc2833bisdata-07.txt

["Tom-PT Taylor" <[e-mail]>]

I'm afraid this document is NOT about RFC 4103. It is primarily dealing 
with the case where the operator chooses to transport the text in native 
PSTN format rather than interworking it, even though that is not the 
recommended approach.

Roy, Radhika R. wrote:
> Hi, Tom and Henning:
> 
> I have some quick editorial comments on the draft as follows:
> 
> 1. In the context of the draft, the use of the terms like
> "Text-Telephony" and "conversational-text" are OK. Because they
> represent the "real-time" nature of the same application that is
> compatible with the "real-time" audio application.
> 
> 2. If the same spirit of item 1 needs to be kept throughout the whole
> draft, the terms like "text" and "text-terminal" need to be as follows
> "real-time-text" and "real-time-text-terminal," respectively.
> 
> Best regards,
> Radhika R. Roy
> 
> -----Original Message-----
> From: [e-mail] [mailto:[e-mail]] On Behalf Of
> [e-mail]
> Sent: Tuesday, June 06, 2006 3:50 PM
> To: [e-mail]
> Cc: [e-mail]
> Subject: [AVT] I-D ACTION:draft-ietf-avt-rfc2833bisdata-07.txt 
> 
> A New Internet-Draft is available from the on-line Internet-Drafts
> directories.
> This draft is a work item of the Audio/Video Transport Working Group of
> the IETF.
> 
> 	Title		: Definition of Events For Modem, FAX, and Text
> Telephony Signals
> 	Author(s)	: T. Taylor, H. Schulzrinne
> 	Filename	: draft-ietf-avt-rfc2833bisdata-07.txt
> 	Pages		: 51
> 	Date		: 2006-6-6
> 	
> This memo updates RFC xxxx to add event codes for modem, FAX, and
>    text telephony signals when carried in the telephony event RTP
>    payload.  It supersedes the assignment of event codes for this
>    purpose in RFC 2833, and therefore obsoletes that part of RFC 2833.
> 
>    [Note to RFC Editor: please replace "RFC xxxx" in the header above
>    and throughout this document with the RFC number assigned to
>    draft-ietf-avt-rfc2833bis-14.  Please also make the appropriate
>    change to the first normative reference.]
> 
> A URL for this Internet-Draft is:
> http://www.ietf.org/internet-drafts/draft-ietf-avt-rfc2833bisdata-07.txt
> 
> To remove yourself from the I-D Announcement list, send a message to 
> [e-mail] 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-rfc2833bisdata-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:
> 	[e-mail].
> In the body type:
> 	"FILE /internet-drafts/draft-ietf-avt-rfc2833bisdata-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
> [e-mail]
> https://www1.ietf.org/mailman/listinfo/avt
> 


_______________________________________________
Audio/Video Transport Working Group
[e-mail]
https://www1.ietf.org/mailman/listinfo/avt