Re: [AVTCORE] New mile stone on support for leap seconds in RTP sessions

Kevin Gross <kevin.gross@avanw.com> Mon, 28 May 2012 15:16 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 0088021F8625 for <avt@ietfa.amsl.com>; Mon, 28 May 2012 08:16:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.128
X-Spam-Level:
X-Spam-Status: No, score=0.128 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FH_RELAY_NODNS=1.451, FM_FORGED_GMAIL=0.622, HELO_MISMATCH_COM=0.553, HTML_MESSAGE=0.001, 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 M6DSS-vYGatg for <avt@ietfa.amsl.com>; Mon, 28 May 2012 08:16:40 -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 8635C21F8613 for <avt@ietf.org>; Mon, 28 May 2012 08:16:40 -0700 (PDT)
Received: (qmail 27921 invoked by uid 0); 28 May 2012 15:16:39 -0000
Received: from unknown (HELO host291.hostmonster.com) (74.220.215.91) by oproxy1.bluehost.com with SMTP; 28 May 2012 15:16:39 -0000
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=avanw.com; s=default; h=Content-Type:Cc:To:From:Subject:Message-ID:Date:References:In-Reply-To:MIME-Version; bh=bqCfLpB8qgFN0p7Tm0zBV0sXNLyeJGZUgZwbN29AHng=; b=dvnMpJe+BaYRbSZ77nt08wXPCyLiS3629bv6SiE5aS7ER3y5bGv0OOWCCRrjnftCG+opSumM9/uZEzWSODfMvhIbl55MNFEjFzPtZZsJqABOBWdhExmF+kb7KYTn/PFM;
Received: from mail-wg0-f44.google.com ([74.125.82.44]) by host291.hostmonster.com with esmtpsa (TLSv1:RC4-SHA:128) (Exim 4.76) (envelope-from <kevin.gross@avanw.com>) id 1SZ1gU-0008GD-UT for avt@ietf.org; Mon, 28 May 2012 09:16:39 -0600
Received: by wgbdr13 with SMTP id dr13so2091422wgb.13 for <avt@ietf.org>; Mon, 28 May 2012 08:16:37 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.216.196.91 with SMTP id q69mr4893080wen.185.1338218197435; Mon, 28 May 2012 08:16:37 -0700 (PDT)
Received: by 10.223.144.216 with HTTP; Mon, 28 May 2012 08:16:37 -0700 (PDT)
In-Reply-To: <CAJNg7VKaiVLxQi1oSrJVSjFFzJEJ_q=PMe8dr1qL8d-3VZD1CA@mail.gmail.com>
References: <4fbcf53c.0387cd0a.095f.ffff9ffa@mx.google.com> <CAJNg7V+xHXnyFVnmvJm7here7SWdE9CeOOwvxmSDc+i4R-DE+Q@mail.gmail.com> <CAJNg7VKaiVLxQi1oSrJVSjFFzJEJ_q=PMe8dr1qL8d-3VZD1CA@mail.gmail.com>
Date: Mon, 28 May 2012 09:16:37 -0600
Message-ID: <CALw1_Q30noKOMC7AY+Nfh=6rsZ_4G7YD1fzgqHyu_1xm7-DZpg@mail.gmail.com>
From: Kevin Gross <kevin.gross@avanw.com>
To: Marshall Eubanks <marshall.eubanks@gmail.com>
Content-Type: multipart/alternative; boundary="0016e6de00ac4a45da04c11a344c"
X-Identified-User: {1416:host291.hostmonster.com:avanwcom:avanw.com} {sentby:smtp auth 74.125.82.44 authed with kevin.gross@avanw.com}
Cc: avt@ietf.org
Subject: Re: [AVTCORE] New mile stone on support for leap seconds in RTP sessions
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, 28 May 2012 15:16:42 -0000

Thank you for your comments. We will incorporate your suggestions.

Kevin Gross

On Mon, May 28, 2012 at 8:05 AM, Marshall Eubanks <
marshall.eubanks@gmail.com> wrote:

> On Wed, May 23, 2012 at 10:41 AM, Marshall Eubanks
> <marshall.eubanks@gmail.com> wrote:
> > On Wed, May 23, 2012 at 10:31 AM, Roni Even <ron.even.tlv@gmail.com>
> wrote:
> >> Hi,
> >>
> >> At last IETF meeting as part of the discussion on IDMS is was agreed
> that
> >> support for leap seconds in RTP session is relevant to RFC3550 and not
> only
> >> to IDMS.
> >>
> >> We would like to take a new milestone for AVTcore
> >>
> >>
> >>
> >> Nov 2012 - Submit support for leap seconds for RTP session  as Proposed
> >> Standard
> >>
> >> This will be an update to RFC 3550.
> >>
> >>
> >>
> >> We would also like to adopt
> >> http://www.ietf.org/id/draft-gross-avtcore-leap-second-00.txt as a
> starting
> >> point for this goal.
> >>
> >>
> >>
> >> There are two questions to the WGs
> >>
> >>
> >>
> >> 1.       Do you support the new milestone that will update RFC3550
> >>
> >
> > Support.
> >
> >> 2.       Do you think that we should adopt the above individual draft
> as an
> >> initial document
> >>
> >
> > Need to read it first. It just came out.
>
> Having read it, I support its adoption.
>
> Note :
>
> Section 3 :
>
> When
>   they occur, leap seconds are scheduled at the end of the last day of
>   December and/or June each year.
>
> That is not what the standard says, although it has been the practice.
> In no more than a century, if leap seconds continue, there
> will _have_ to be more frequent updates.
>
> From the USNO.
> http://www.usno.navy.mil/USNO/time/master-clock/leap-seconds
>
> "According to the CCIR Recommendation, first preference is given to
> the opportunities at the end of December and June, and second
> preference to those at the end of March and September. Since the
> system was introduced in 1972, only dates in June and December have
> been used. "
>
> I think that  CCIR Recommendation 460-4 (1986) should be added as a
> reference, and the above text be changed to
>
>   When
>   they occur, leap seconds are preferentially scheduled at the end of
> the last day of
>   December and/or June each year, although they could also occur at
> the end of March or September.
>
> Regards
> Marshall
>
>
>
> >
> > Marshall
> >
> >>
> >>
> >>
> >>
> >> Please respond by June 6th
> >>
> >>
> >>
> >> Thanks
> >>
> >> Roni Even
> >>
> >>
> >>
> >>
> >> _______________________________________________
> >> Audio/Video Transport Core Maintenance
> >> avt@ietf.org
> >> https://www.ietf.org/mailman/listinfo/avt
> >>
> _______________________________________________
> Audio/Video Transport Core Maintenance
> avt@ietf.org
> https://www.ietf.org/mailman/listinfo/avt
>