A new Request for Comments is now available in online RFC libraries.
RFC 4103
Title: RTP Payload for Text Conversation
Author(s): G. Hellstrom, P. Jones
Status: Standards Track
Date: June 2005
Mailbox: gunnar.hellstrom@omnitor.se, paulej@packetizer.com
Pages: 20
Characters: 44246
Obsoletes: 2793
I-D Tag: draft-ietf-avt-rfc2793bis-09.txt
URL: ftp://ftp.rfc-editor.org/in-notes/rfc4103.txt
This memo obsoletes RFC 2793; it 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.
One payload format is described for transmitting text on a separate
RTP session dedicated for the transmission of text.
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.
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.
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.
- <ftp://ftp.isi.edu/in-notes/rfc4103.txt>
-
_______________________________________________
IETF-Announce@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf-announce
