Re: [AVTCORE] Leap seconds

David Singer <singer@apple.com> Mon, 19 September 2011 17:15 UTC

Return-Path: <singer@apple.com>
X-Original-To: avt@ietfa.amsl.com
Delivered-To: avt@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7A20121F8CCB for <avt@ietfa.amsl.com>; Mon, 19 Sep 2011 10:15:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.599
X-Spam-Level:
X-Spam-Status: No, score=-106.599 tagged_above=-999 required=5 tests=[AWL=-0.001, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MV2UemUX9QvK for <avt@ietfa.amsl.com>; Mon, 19 Sep 2011 10:15:54 -0700 (PDT)
Received: from mail-out.apple.com (mail-out.apple.com [17.151.62.49]) by ietfa.amsl.com (Postfix) with ESMTP id 3914721F8CCA for <avt@ietf.org>; Mon, 19 Sep 2011 10:15:48 -0700 (PDT)
MIME-version: 1.0
Content-type: multipart/alternative; boundary="Boundary_(ID_20CknH0HZkCxKvYOAPtbUA)"
Received: from relay15.apple.com ([17.128.113.54]) by mail-out.apple.com (Oracle Communications Messaging Exchange Server 7u4-20.01 64bit (built Nov 21 2010)) with ESMTP id <0LRS0083V5C92VP0@mail-out.apple.com> for avt@ietf.org; Mon, 19 Sep 2011 10:17:28 -0700 (PDT)
X-AuditID: 11807136-b7c7fae00000458f-8b-4e777d7d5461
Received: from [17.153.27.199] (Unknown_Domain [17.153.27.199]) by relay15.apple.com (Apple SCV relay) with SMTP id 3F.FE.17807.D7D777E4; Mon, 19 Sep 2011 10:35:57 -0700 (PDT)
From: David Singer <singer@apple.com>
In-reply-to: <CALw1_Q0UD563WAES2bauEFa2+zr+qtwCs_=sX8hRED1VgPQTfw@mail.gmail.com>
Date: Mon, 19 Sep 2011 10:17:28 -0700
Message-id: <6B776E08-0395-4683-B325-9A4A7B4535A0@apple.com>
References: <CALw1_Q0qK1WDc_KjEneOWrqr+jfVsqdwFYpF=ht-tS4SSNp8nQ@mail.gmail.com> <71C9EC0544D1F64D8B7D91EDCC6220200A2D0340@NABSREX027324.NAB.ORG> <alpine.BSF.2.00.1109141110001.25117@hsa.packetdesign.com> <CALw1_Q2L5z1bdVaENm7ky-epWjmxD326FLQ7THrObO_KMfdXfw@mail.gmail.com> <78481CCB-7A70-4BC4-91DC-A707301F22A5@apple.com> <CALw1_Q2VFe3d52ufVp2wSeNCHiwqgnhLh39dQTWYa52jWLaV+g@mail.gmail.com> <8EF3B729-407D-4A6F-9B5C-9E6833F2478B@apple.com> <CALw1_Q05fXDmTFapSaH1NRCsp2eWdemNus40gXsFwsx4HbR34Q@mail.gmail.com> <0F41102E-7F7A-4D69-B22D-6BFC3215D6C0@apple.com> <CALw1_Q0UD563WAES2bauEFa2+zr+qtwCs_=sX8hRED1VgPQTfw@mail.gmail.com>
To: Kevin Gross <kevin.gross@avanw.com>
X-Mailer: Apple Mail (2.1084)
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFtrJLMWRmVeSWpSXmKPExsUiOFP6uG5tbbmfwY7nmhYve1ayW7w41M7m wOTx7+p2Zo8lS34yBTBFcdmkpOZklqUW6dslcGVceD+HrWCiQ8WO7QdZGxg3mncxcnJICJhI fHm2jAXCFpO4cG89G4gtJLCRUeLmj0IQW1hAWeLWpmvMIDavgKHE0k3t7CA2s4CbxJRVJ1lB bDYBVYkHc44xgticAoESrRd/g9WzAMVP/5/AAlEvILGifzJTFyMH0Bwbie0/VboYuYBWfWaR 2P15E9heEQF1iUe7HoLVSAjISjQty5jAyDcLyeZZSDZD2NoSyxa+Zp4F1MEsoCMxeSEjqjCE /fH8EaYFjGyrGAWLUnMSKw1N9RILCnJS9ZLzczcxggK0odBsB+OOv3KHGAU4GJV4eBnbyvyE WBPLiitzDzFKcDArifC+zir3E+JNSaysSi3Kjy8qzUktPsQozcGiJM6bI17iJySQnliSmp2a WpBaBJNl4uCUamCcPtts7qlov7TTVdwCvHbvjzxawNdvwXrpkNQCc9GTByfuD2KcLmmrnDSj +MqmrRcMb4dotuleNPu450XxhucLxdXnisXvlXbaUTFrw60nE6u+ffujtHVWc/jd6801VZXi mUkr1mYFin+t+vCPZfbDd30qrQ2qjGpfpE9YLf/4/pWe5lrB8OXGSizFGYmGWsxFxYkAo3gM TkwCAAA=
Cc: avt@ietf.org
Subject: Re: [AVTCORE] Leap seconds
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/avt>, <mailto:avt-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/avt>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 19 Sep 2011 17:15:55 -0000

I guess there is some ... unclarity.  On the one hand we read that the tickers that count seconds do just that, tick every second, and that leap-second correction is only required if you want to convert these to civil time.  On the other hand we read of this 'stalling' behavior.  

If we stall periodically, then the counters always have {365 or 366 days} * 24 * 60 * 60 seconds per year.  If we don't, some years are +/-1 second if a second was inserted or deleted, and you need to know which years since your zero-point had leap seconds.


On Sep 19, 2011, at 9:01 , Kevin Gross wrote:

> David Singer and I spent some time last week working through this offline. We're using the same sources and coming to different conclusions. We need some help resolving this open question.
> 
> David's position is that the NTP timestamp continues to increment, with the system oscillator, through a leap second. The leap second is not visible in the NTP timestamp but in a higher layer process that converts NTP timestamps to UTC.
> 
> My reading is that the NTP timestamp *is* UTC time and that the clock is paused for 1 second and a new timeline established at the leap second. This behavior will either upset or complicate media systems attempting to reference their playback to the NTP timestamps delivered in RTCP sender reports.
> 
> RFC 3550 (RTP) does not discuss leap seconds.
> 
> RFC 5905 (NTP) describes the mechanism used to convey an upcoming leap second but does not appear to discuss timestamp behavior associated with the leap second.
> 
> The following two references from David Mills (RFC 5905 author) directly discuss leap second behavior:
> http://www.eecis.udel.edu/~mills/leap.html Section 5
> Last section of http://doc.ntp.org/4.1.2/leap.htm
> -- 
> Kevin Gross
> +1-303-447-0517
> Media Network Consultant
> AVA Networks - www.AVAnw.com, www.X192.org
> 
> 
> _______________________________________________
> Audio/Video Transport Core Maintenance
> avt@ietf.org
> https://www.ietf.org/mailman/listinfo/avt

David Singer
Multimedia and Software Standards, Apple Inc.