Sign in
Version 5.13.0, 2015-03-25
Report a bug

RTP and Leap Seconds

Document type: Replaced Internet-Draft (individual)
Document stream: No stream defined
Last updated: 2012-10-11 (latest revision 2012-05-23)
Intended RFC status: Unknown
Other versions: (expired, archived): plain text, pdf, html

Stream State:No stream defined
Document shepherd: No shepherd assigned

IESG State: Replaced by draft-ietf-avtcore-leap-second
Responsible AD: (None)
Send notices to: No addresses provided

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


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 <>
Ray van Brandenburg <>

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