RTP Payload for Text Conversation
draft-hellstrom-avt-rfc2793bis-02
| Document | Type | Expired Internet-Draft (individual) | |
|---|---|---|---|
| Authors | Gunnar Hellstrom , Paul Jones | ||
| Last updated | 2003-10-28 | ||
| Stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats |
Expired & archived
pdf
htmlized (tools)
htmlized
bibtex
|
||
| Stream | Stream state | (No stream defined) | |
| Consensus Boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | |||
| Responsible AD | (None) | ||
| Send notices to | (None) | ||
https://www.ietf.org/archive/id/draft-hellstrom-avt-rfc2793bis-02.txt
Abstract
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.
Authors
Gunnar Hellstrom
(gunnar.hellstrom@omnitor.se)
Paul Jones
(paulej@packetizer.com)
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)