RTP and Leap Seconds
draft-gross-leap-second-01
| Document | Type |
Replaced Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Kevin Gross , Ray van Brandenburg | ||
| Last updated | 2012-11-15 (Latest revision 2012-05-23) | ||
| Replaced by | draft-ietf-avtcore-leap-second | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Replaced by draft-ietf-avtcore-leap-second | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
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.
Authors
Kevin Gross
Ray van Brandenburg
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)