IP video telephony with text component, IP Text Telephony, IP Total Conversation, IP Mobiles with text etc. can now be accomplished in a standardised way.
The specification on how to transmit text for real time chatting in IP networks is now published as RFC 2793 from IETF. (It was approved in February, but got published with its number now.)
With it comes a new registered MIME type "text/t140" so that it can be specified for example in the multimedia protocol SIP.
The multimedia protocol ITU-T H.323 is already ready for text addition with its Annex G, referencing to RFC 2793.
Thanks to all who have contributed, and good luck to all who now creates interworking Total Conversation solutions with this component!
Regards Gunnar Hellström ______________________________________ Gunnar Hellström Omnitor AB Alsnögatan 7, 4tr S-116 41 Stockholm Sweden
Mob +46 708 204 288 Tel +46 8 556 002 03 Fax +46 8 556 002 06 Video +46 8 556 002 05 Txt (All kinds) +46 8 556 002 05 E-mail gunnar.hellstrom@omnitor.se WWW: http://www.omnitor.se
-----Original Message----- From: RFC Editor [mailto:rfc-ed@ISI.EDU] Sent: Friday, May 05, 2000 1:17 AM To: IETF-Announce: ; Cc: rfc-ed@ISI.EDU; rem-conf@es.net Subject: RFC 2793 on RTP Payload for Text Conversation
A new Request for Comments is now available in online RFC libraries.
RFC 2793
Title: RTP Payload for Text Conversation Author(s): G. Hellstrom Status: Standards Track Date: May 2000 Mailbox: gunnar.hellstrom@omnitor.se Pages: 10 Characters: 20674 Updates/Obsoletes/SeeAlso: None
URL: ftp://ftp.isi.edu/in-notes/rfc2793.txt
This memo describes how to carry text conversation session contents in RTP packets. Text conversation session contents are specified in ITU-T Recommendation T.140 [1].
Text conversation is used alone or in connection to other conversational facilities such as video and voice, to form multimedia conversation services.
This RTP payload description contains an optional possibility to include redundant text from already transmitted packets in order to reduce the risk of text loss caused by packet loss. The redundancy coding follows RFC 2198.
This document is a product of the Audio/Video Transport Working Group of the IETF.
This is now a Proposed Standard Protocol.
This document specifies an Internet standards track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the "Internet Official Protocol Standards" (STD 1) for the standardization state and status of this protocol. Distribution of this memo is unlimited.
This announcement is sent to the IETF list and the RFC-DIST list. Requests to be added to or deleted from the IETF distribution list should be sent to IETF-REQUEST@IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG.
Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example:
To: rfc-info@RFC-EDITOR.ORG Subject: getting rfcs
help: ways_to_get_rfcs
Requests for special distribution should be addressed to either the author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution.echo Submissions for Requests for Comments should be sent to RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information.
Joyce K. Reynolds and Sandy Ginoza USC/Information Sciences Institute
...
Below is the data which will enable a MIME compliant Mail Reader implementation to automatically retrieve the ASCII version of the RFCs.
RETRIEVE: rfc DOC-ID: rfc2793