Browse Prior Art Database

RTP and Leap Seconds (RFC7164)

IP.com Disclosure Number: IPCOM000235968D
Original Publication Date: 2014-Mar-01
Included in the Prior Art Database: 2014-Apr-01
Document File: 18 page(s) / 21K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

K. Gross: AUTHOR [+2]

Abstract

In some media networking applications, RTP streams are referenced to a wall-clock time (absolute date and time). This is accomplished through use of the NTP timestamp field in the sender report (SR) to create a mapping between RTP timestamps and the wall clock. When a wall-clock reference is used, the playout time for RTP packets is referenced to the wall clock. Smooth and continuous media playout requires a smooth and continuous time base. The time base used by the wall clock may include leap seconds that are not rendered smoothly.

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 14% of the total text.

Internet Engineering Task Force (IETF)                          K. Gross Request for Comments: 7164                                  AVA Networks Updates: 3550                                         R. van Brandenburg Category: Standards Track                                            TNO ISSN: 2070-1721                                               March 2014

                           RTP and Leap Seconds

Abstract

   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.

Status of This Memo

   This is an Internet Standards Track document.

   This document is a product of the Internet Engineering Task Force    (IETF).  It represents the consensus of the IETF community.  It has    received public review and has been approved for publication by the    Internet Engineering Steering Group (IESG).  Further information on    Internet Standards is available in Section 2 of RFC 5741.

   Information about the current status of this document, any errata,    and how to provide feedback on it may be obtained at    http://www.rfc-editor.org/info/rfc7164.

Copyright Notice

   Copyright (c) 2014 IETF Trust and the persons identified as the    document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal    Provisions Relating to IETF Documents    (http://trustee.ietf.org/license-info) in effect on the date of    publication of this document.  Please review these documents    carefully, as they describe your rights and restrictions with respect    to this document.  Code Components extracted from this document must    include Simplified BSD License text as described in Section 4.e of    the Trust Legal Provisions and are provided without warranty as    described in the Simplified BSD License.

Gross & van Brandenburg      Standards Track                    [Page 1]
 RFC 7164                  RTP and Leap Seconds                March 2014

 Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2

   2.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   2

   3.  Leap Seconds  . . . . . . . . . . . . . . . . . . . . . . . .   2

     3.1.  UTC Behavior during a Positive Leap Second  . . . . . . .   3

     3.2.  NTP Behavior during a Positive Leap Second  . . . . . . .   3

     3.3.  POSIX Behavior during a Positive Leap Second  . . . . . .   3

     3.4.  Example of Leap-Second Behaviors  . . . . . . . . . . . .  ...