RFC 5484: Associating Time-Codes with RTP Streams
In plain English — editorial summary, not part of the RFC
This document describes a mechanism for associating \%time-codes, as defined by the Society of Motion Picture and Television Engineers (SMPTE), with media streams in a way that is independent of the RTP payload format of the media stream itself. [STANDARDS-TRACK]
Document record
- Document ID
- RFC5484
- Published
- March 2009
- Authors
- D. Singer
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rai
- Pages
- 13
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 3497RTP Payload Format for Society of Motion Picture and Television Engineers (SMPTE) 292M VideoCurrent
March 2003
- RFC 4585Extended RTP Profile for Real-time Transport Control Protocol (RTCP)-Based Feedback (RTP/AVPF)Updated
July 2006
- RFC 4175RTP Payload Format for Uncompressed VideoUpdated
September 2005
- RFC 5432Quality of Service (QoS) Mechanism Selection in the Session Description Protocol (SDP)Current
March 2009
- RFC 4574The Session Description Protocol (SDP) Label AttributeCurrent
August 2006
- RFC 5483ENUM Implementation Issues and ExperiencesCurrent
March 2009
- RFC 5486Session Peering for Multimedia Interconnect (SPEERMINT) TerminologyCurrent
March 2009
- RFC 5479Requirements and Analysis of Media Security Management ProtocolsCurrent
April 2009
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?