RFC 7164: RTP and Leap Seconds
In plain English — editorial summary, not part of the RFC
This document discusses issues that arise when RTP sessions span Coordinated Universal Time (UTC) leap seconds. It updates RFC 3550 by describing how RTP senders and receivers should behave in the presence of leap seconds.
Document record
- Document ID
- RFC7164
- Published
- March 2014
- Authors
- K. Gross; R. Brandenburg
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- wit
- Pages
- 9
- Also known as
- —
- Updates:
- RFC 3550
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 9581Concise Binary Object Representation (CBOR) Tags for Time, Duration, and PeriodCurrent
August 2024
- RFC 6904Encryption of Header Extensions in the Secure Real-time Transport Protocol (SRTP)Current
April 2013
- RFC 7384Security Requirements of Time Protocols in Packet Switched NetworksCurrent
October 2014
- RFC 7604Comparison of Different NAT Traversal Techniques for Media Controlled by the Real-Time Streaming Protocol (RTSP)Current
September 2015
- RFC 5576Source-Specific Media Attributes in the Session Description Protocol (SDP)Current
June 2009
- RFC 5459G.729.1 RTP Payload Format Update: Discontinuous Transmission (DTX) SupportCurrent
January 2009
- RFC 5371RTP Payload Format for JPEG 2000 Video StreamsCurrent
October 2008
- RFC 4102Registration of the text/red MIME Sub-TypeUpdated
June 2005
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?