[AVTCORE] draft-ietf-avtcore-idms-01 leap seconds
Kevin Gross <kevin.gross@avanw.com> Thu, 20 October 2011 02:35 UTC
Return-Path: <kevin.gross@avanw.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 D018F11E80CD for <avt@ietfa.amsl.com>; Wed, 19 Oct 2011 19:35:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.127
X-Spam-Level:
X-Spam-Status: No, score=0.127 tagged_above=-999 required=5 tests=[AWL=0.001, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, FM_FORGED_GMAIL=0.622, HELO_MISMATCH_COM=0.553, RDNS_NONE=0.1]
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 2qVQ5xSY2Zls for <avt@ietfa.amsl.com>; Wed, 19 Oct 2011 19:35:33 -0700 (PDT)
Received: from oproxy1-pub.bluehost.com (oproxy1.bluehost.com [IPv6:2605:dc00:100:2::a1]) by ietfa.amsl.com (Postfix) with SMTP id 1A49711E80BF for <avt@ietf.org>; Wed, 19 Oct 2011 19:35:33 -0700 (PDT)
Received: (qmail 31438 invoked by uid 0); 20 Oct 2011 02:35:32 -0000
Received: from unknown (HELO host291.hostmonster.com) (74.220.215.91) by oproxy1.bluehost.com with SMTP; 20 Oct 2011 02:35:32 -0000
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=avanw.com; s=default; h=Content-Transfer-Encoding:Content-Type:To:From:Subject:Message-ID:Date:MIME-Version; bh=9jnL+7cbUsIIUApvvrqxXW2l7SewDWdghZ2JQiWaQpY=; b=nRyHWMo4eCRMs6zGvqjrA6NWt/cIhl0FDppsal4eyBherHq9FMLwSMqnT2gOUG0WZ/cqp8vDe0IEdBr8WuS7V4ggc29FmZE3p0XduyqsRxubvMcEnubQi+ALZ6DmKCkt;
Received: from mail-ey0-f172.google.com ([209.85.215.172]) by host291.hostmonster.com with esmtpsa (TLSv1:RC4-SHA:128) (Exim 4.76) (envelope-from <kevin.gross@avanw.com>) id 1RGiTj-0003sW-PG for avt@ietf.org; Wed, 19 Oct 2011 20:35:32 -0600
Received: by eyg24 with SMTP id 24so2486692eyg.31 for <avt@ietf.org>; Wed, 19 Oct 2011 19:35:30 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.223.61.211 with SMTP id u19mr15011145fah.29.1319078130405; Wed, 19 Oct 2011 19:35:30 -0700 (PDT)
Received: by 10.223.93.202 with HTTP; Wed, 19 Oct 2011 19:35:30 -0700 (PDT)
Date: Wed, 19 Oct 2011 20:35:30 -0600
Message-ID: <CALw1_Q3e65LbGf3DZ17HCMkmSw5ZWTJnuGQ_qKt8YmHPHSnAUw@mail.gmail.com>
From: Kevin Gross <kevin.gross@avanw.com>
To: avt@ietf.org
Content-Type: text/plain; charset="windows-1252"
Content-Transfer-Encoding: quoted-printable
X-Identified-User: {1416:host291.hostmonster.com:avanwcom:avanw.com} {sentby:smtp auth 209.85.215.172 authed with kevin.gross@avanw.com}
Subject: [AVTCORE] draft-ietf-avtcore-idms-01 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: Thu, 20 Oct 2011 02:35:33 -0000
I've prepared the following paragraphs which discuss the issue and describe measures required to avoid leap second problems. I propose this be inserted into section 8 of draft-ietf-avtcore-idms-01. A subset of these recommendations are applicable to RFC 3550 applications that make use of the NTP timestamp in sender reports. I’d be happy to propose corresponding revisions to RFC 3550 once we’ve ironed out IDMS. "IDMS implementation is simplified by using a clock reference with timescale which does not include leap seconds. IEEE 1588, GPS and other TAI (Inernational Atomic Time) references do not include leap seconds. NTP time, operating system clocks and other UTC (Coordinated Universal Time) references include leap seconds (though the ITU is studying a proposal which could eventually eliminate leap seconds from UTC). If a timescale with leap seconds is used for IDMS, receivers must take care not to generate any IDMS XR reports in the immediate vicinity of the leap second. Synchronization servers must ignore any such reports that may inadvertently generated. Senders using a leap-second-bearing reference must not generate sender reports containing an origination NTP timestamp in the vicinity or a leap second. Receivers should ignore timestamps in any such reports inadvertently generated. Receivers working to a leap-second-bearing reference must also be careful to take leap seconds into account if a leap second occurs between the time a RTP packet is originated and when it is to be presented. "Leap seconds are potentially scheduled at the end of the last day of December and June each year. NTP inserts a leap second at the beginning of the last second of the day. This results in the clock freezing for one second immediately prior to the last second of the affected day. Most system clocks insert the leap second at the end of the last second. This results in repetition of the last second of the day. Generating or using timestamps during the entire last second of a day on which a leap second has been scheduled should therefore be avoided. Note that the period to be avoided has a real-time duration of two seconds. It is also important that all participants correctly implement leap seconds and have a working communications channel to receive notification of leap second scheduling. Without prior knowledge of leap second schedule, NTP servers and clients may be offset by exactly one second with respect to their UTC reference. This potential discrepancy begins when a leap second occurs and ends when all participants receive a time update from a server or peer. Such a long-lived discrepancy can be particularly disruptive to RTP and IDMS operation." On Fri, Sep 23, 2011 at 9:48 AM, Kevin Gross <kevin.gross@avanw.com> wrote: > > Qin, > Thank you for this reminder. I have revisited the IDMS draft and am reminded that it does define a means to specify wallclock source. I think it could use a little work but it is an excellent start. > The IDMS draft doesn't mention leap seconds but since it is a draft, that can easily be changed! > I will contact Ray Brandenburg and see if I can offer to help with this. > I think it would still be useful to add some leap second discussion to 3550 but I would propose to work it out under IDMS first since IDMS receivers is where these NTP timestamps will be most relied upon. > Kevin Gross > > On Thu, Sep 22, 2011 at 3:52 AM, Qin Wu <bill.wu@huawei.com> wrote: >> >> Hi, Kevin: >> Regarding how to know where the leap seconds are, I think, you may follow two potential ways: >> 1. you may take take David's suggestion, compare the NTP/RTP pairs in the two consecutive SRs to know if exception happen. >> 2. you may look at IDMS draft, the parameter clock source is defined in SDP to signal the source for clock >> synchronization. Using this parameter, the receiver may know where the leap seconds are. >> Does this make sense? >> >> Regards! >> -Qin
- [AVTCORE] draft-ietf-avtcore-idms-01 leap seconds Kevin Gross
- [AVTCORE] draft-ietf-avtcore-idms-01 leap seconds Kevin Gross
- Re: [AVTCORE] draft-ietf-avtcore-idms-01 leap sec… Brandenburg, R. (Ray) van