Re: [v6ops] draft-elkins-v6ops-ipv6-pdm-recommended-usage-00
Brian Haberman <brian@innovationslab.net> Mon, 05 August 2013 14:22 UTC
Return-Path: <brian@innovationslab.net>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EDEDF21F9F1C for <v6ops@ietfa.amsl.com>; Mon, 5 Aug 2013 07:22:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.287
X-Spam-Level:
X-Spam-Status: No, score=-102.287 tagged_above=-999 required=5 tests=[AWL=-0.288, BAYES_00=-2.599, J_CHICKENPOX_13=0.6, 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 OBGxyC56Jilq for <v6ops@ietfa.amsl.com>; Mon, 5 Aug 2013 07:21:59 -0700 (PDT)
Received: from uillean.fuaim.com (uillean.fuaim.com [206.197.161.140]) by ietfa.amsl.com (Postfix) with ESMTP id 3A2CE21F9F01 for <v6ops@ietf.org>; Mon, 5 Aug 2013 07:21:40 -0700 (PDT)
Received: from clairseach.fuaim.com (clairseach-high.fuaim.com [206.197.161.158]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by uillean.fuaim.com (Postfix) with ESMTP id E5C1D880FB for <v6ops@ietf.org>; Mon, 5 Aug 2013 07:21:39 -0700 (PDT)
Received: from 10252294.rudm1.ra.johnshopkins.edu (addr16212925014.ippl.jhmi.edu [162.129.250.14]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by clairseach.fuaim.com (Postfix) with ESMTP id AE84813680D7 for <v6ops@ietf.org>; Mon, 5 Aug 2013 07:21:39 -0700 (PDT)
Message-ID: <51FFB4F2.4060503@innovationslab.net>
Date: Mon, 05 Aug 2013 10:21:38 -0400
From: Brian Haberman <brian@innovationslab.net>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130620 Thunderbird/17.0.7
MIME-Version: 1.0
To: v6ops@ietf.org
References: <51FA6667.4010200@bogus.com> <1375366309.93638.YahooMailNeo@web2803.biz.mail.ne1.yahoo.com>
In-Reply-To: <1375366309.93638.YahooMailNeo@web2803.biz.mail.ne1.yahoo.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Subject: Re: [v6ops] draft-elkins-v6ops-ipv6-pdm-recommended-usage-00
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 05 Aug 2013 14:22:09 -0000
ntpwg@lists.ntp.org will get you the NTP WG. Regards, Brian On 8/1/13 10:11 AM, Nalini Elkins wrote: > Thanks for your comments, Joel. > > I want to take some time to research this further and talk to some more people. I will respond back on the list to this point in about 2 weeks. I want to talk this over with some of the folks actively working on NTP at IETF. > > Nalini Elkins > Inside Products, Inc. > (831) 659-8360 > www.insidethestack.com > > > > ________________________________ > From: joel jaeggli <joelja@bogus.com> > To: Nalini Elkins <nalini.elkins@insidethestack.com>; IPv6 Ops WG <v6ops@ietf.org> > Sent: Thursday, August 1, 2013 6:45 AM > Subject: draft-elkins-v6ops-ipv6-pdm-recommended-usage-00 > > > Since I ran into you in the hall and the dicussion turned to ntp... > > I'll try and be succinct, and as a non-expert in the time field this > should be taken with a grain of salt. > > The generic utility of a high-resultion time-stamp is imho dodgey > outside of situations where the clocks are deliberately syncronized and > traceable to a common standard whether the protocol used for this is ntp > or ieee 1588 (or since this is the ietf PTPV2) . While this is tractable > for devices in a single span of control, the agruement that ntp might be > suffcient to make this timstamp useful generically between two > aribitratry devices where this functionality may need to be enabled is > imho a hard one to assert. > > It is a set of operational practice and discipline moreso than the > choice of technology that allows for a high-resolution timestamp to have > sufficient precision to be useful between hosts. > > joel > > > > _______________________________________________ > v6ops mailing list > v6ops@ietf.org > https://www.ietf.org/mailman/listinfo/v6ops >
- [v6ops] draft-elkins-v6ops-ipv6-pdm-recommended-u… joel jaeggli
- Re: [v6ops] draft-elkins-v6ops-ipv6-pdm-recommend… Nalini Elkins
- Re: [v6ops] draft-elkins-v6ops-ipv6-pdm-recommend… Brian Haberman
- Re: [v6ops] draft-elkins-v6ops-ipv6-pdm-recommend… Nalini Elkins
- Re: [v6ops] draft-elkins-v6ops-ipv6-pdm-recommend… Nalini Elkins
- Re: [v6ops] draft-elkins-v6ops-ipv6-pdm-recommend… joel jaeggli
- Re: [v6ops] draft-elkins-v6ops-ipv6-pdm-recommend… Nalini Elkins
- Re: [v6ops] draft-elkins-v6ops-ipv6-pdm-recommend… Ackermann, Michael
- Re: [v6ops] draft-elkins-v6ops-ipv6-pdm-recommend… Nalini Elkins
- Re: [v6ops] draft-elkins-v6ops-ipv6-pdm-recommend… MORTON JR., ALFRED C (AL)
- Re: [v6ops] draft-elkins-v6ops-ipv6-pdm-recommend… joel jaeggli
- Re: [v6ops] draft-elkins-v6ops-ipv6-pdm-recommend… Nalini Elkins
- Re: [v6ops] draft-elkins-v6ops-ipv6-pdm-recommend… Randy Bush
- Re: [v6ops] draft-elkins-v6ops-ipv6-pdm-recommend… joel jaeggli
- Re: [v6ops] draft-elkins-v6ops-ipv6-pdm-recommend… Nalini Elkins
- Re: [v6ops] draft-elkins-v6ops-ipv6-pdm-recommend… Randy Bush
- Re: [v6ops] draft-elkins-v6ops-ipv6-pdm-recommend… Nalini Elkins
- Re: [v6ops] draft-elkins-v6ops-ipv6-pdm-recommend… Bill Jouris
- Re: [v6ops] draft-elkins-v6ops-ipv6-pdm-recommend… Mark ZZZ Smith
- Re: [v6ops] draft-elkins-v6ops-ipv6-pdm-recommend… Nalini Elkins
- Re: [v6ops] draft-elkins-v6ops-ipv6-pdm-recommend… Ackermann, Michael