RFC 7160: Support for Multiple Clock Rates in an RTP Session
In plain English — editorial summary, not part of the RFC
This document clarifies the RTP specification regarding the use of different clock rates in an RTP session. It also provides guidance on how legacy RTP implementations that use multiple clock rates can interoperate with RTP implementations that use the algorithm described in this document. It updates RFC 3550.
Document record
- Document ID
- RFC7160
- Published
- April 2014
- Authors
- M. Petit-Huguenin; G. Zorn
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- art
- Pages
- 13
- Also known as
- —
- Updates:
- RFC 3550
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 7163URN for Country-Specific Emergency ServicesCurrent
March 2014
- RFC 7134The Management Policy of the Resource Priority Header (RPH) Registry Changed to "IETF Review"Current
March 2014
- RFC 7131Session Initiation Protocol (SIP) History-Info Header Call Flow ExamplesCurrent
March 2014
- RFC 7195Session Description Protocol (SDP) Extension for Setting Audio and Video Media Streams over Circuit-Switched Bearers in the Public Switched Telephone Network (PSTN)Current
May 2014
- RFC 7197Duplication Delay Attribute in the Session Description ProtocolCurrent
April 2014
- RFC 7198Duplicating RTP StreamsCurrent
April 2014
- RFC 7118The WebSocket Protocol as a Transport for the Session Initiation Protocol (SIP)Current
January 2014
- RFC 7205Use Cases for Telepresence MultistreamsCurrent
April 2014
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?