RFC 4396: RTP Payload Format for 3rd Generation Partnership Project (3GPP) Timed Text
In plain English — editorial summary, not part of the RFC
This document specifies an RTP payload format for the transmission of 3GPP (3rd Generation Partnership Project) timed text. 3GPP timed text is a time-lined, decorated text media format with defined storage in a 3GP file. Timed Text can be synchronized with audio/video contents and used in applications such as captioning, titling, and multimedia presentations. In the following sections, the problems of streaming timed text are addressed, and a payload format for streaming 3GPP timed text over RTP is specified. [STANDARDS-TRACK]
Document record
- Document ID
- RFC4396
- Published
- February 2006
- Authors
- J. Rey; Y. Matsui
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rai
- Pages
- 66
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 4042UTF-9 and UTF-18 Efficient Transformation Formats of UnicodeCurrent
April 2005
- RFC 3327Session Initiation Protocol (SIP) Extension Header Field for Registering Non-Adjacent ContactsUpdated
December 2002
- RFC 4457The Session Initiation Protocol (SIP) P-User-Database Private-Header (P-Header)Current
April 2006
- RFC 4281The Codecs Parameter for "Bucket" Media TypesObsoleted
December 2005
- RFC 4187Extensible Authentication Protocol Method for 3rd Generation Authentication and Key Agreement (EAP-AKA)Updated
January 2006
- RFC 4186Extensible Authentication Protocol Method for Global System for Mobile Communications (GSM) Subscriber Identity Modules (EAP-SIM)Current
January 2006
- RFC 5002The Session Initiation Protocol (SIP) P-Profile-Key Private Header (P-Header)Updated
August 2007
- RFC 5137ASCII Escaping of Unicode CharactersCurrent
February 2008
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?