RTP and Leap Seconds

Document Type Replaced Internet-Draft (individual)
Last updated 2012-10-11 (latest revision 2012-05-23)
Replaced by draft-ietf-avtcore-leap-second
Stream (None)
Intended RFC status (None)
Expired & archived
plain text pdf html
Stream Stream state (No stream defined)
Document shepherd No shepherd assigned
IESG IESG state Replaced by draft-ietf-avtcore-leap-second
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at


This document discusses issues that arise when RTP sessions span (UTC) leap seconds. It updates RFC 3550 to describe how RTP senders and receivers should behave in the presence of leap seconds.


Kevin Gross (kevin.gross@avanw.com)
Ray van Brandenburg (ray.vanbrandenburg@tno.nl)

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)