RFC 5450: Transmission Time Offsets in RTP Streams
In plain English — editorial summary, not part of the RFC
This document describes a method to inform Real-time Transport Protocol (RTP) clients when RTP packets are transmitted at a time other than their 'nominal' transmission time. It also provides a mechanism to provide improved inter-arrival jitter reports from the clients, that take into account the reported transmission times. [STANDARDS-TRACK]
Document record
- Document ID
- RFC5450
- Published
- March 2009
- Authors
- D. Singer; H. Desineni
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rai
- Pages
- 8
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 5459G.729.1 RTP Payload Format Update: Discontinuous Transmission (DTX) SupportCurrent
January 2009
- RFC 5438Instant Message Disposition Notification (IMDN)Current
February 2009
- RFC 5478IANA Registration of New Session Initiation Protocol (SIP) Resource-Priority NamespacesCurrent
March 2009
- RFC 5479Requirements and Analysis of Media Security Management ProtocolsCurrent
April 2009
- RFC 5483ENUM Implementation Issues and ExperiencesCurrent
March 2009
- RFC 5484Associating Time-Codes with RTP StreamsCurrent
March 2009
- RFC 5486Session Peering for Multimedia Interconnect (SPEERMINT) TerminologyCurrent
March 2009
- RFC 5411A Hitchhiker's Guide to the Session Initiation Protocol (SIP)Current
February 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?