Re: [v6ops] Fw: New Version Notification for draft-elkins-6man-ipv6-pdm-dest-option-04.txt

Brian Haberman <brian@innovationslab.net> Mon, 28 October 2013 16:24 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 69EA521F9F08; Mon, 28 Oct 2013 09:24:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.562
X-Spam-Level:
X-Spam-Status: No, score=-102.562 tagged_above=-999 required=5 tests=[AWL=0.038, BAYES_00=-2.599, 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 uJT9wXzC8fBb; Mon, 28 Oct 2013 09:24:13 -0700 (PDT)
Received: from uillean.fuaim.com (uillean.fuaim.com [206.197.161.140]) by ietfa.amsl.com (Postfix) with ESMTP id EC8F421F9FE9; Mon, 28 Oct 2013 09:24:12 -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 6B2A6880A4; Mon, 28 Oct 2013 09:24:12 -0700 (PDT)
Received: from 102527254.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 D1EE3130003; Mon, 28 Oct 2013 09:24:11 -0700 (PDT)
Message-ID: <526E8FA3.70506@innovationslab.net>
Date: Mon, 28 Oct 2013 12:24:03 -0400
From: Brian Haberman <brian@innovationslab.net>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:24.0) Gecko/20100101 Thunderbird/24.0.1
MIME-Version: 1.0
To: "Ackermann, Michael" <MAckermann@bcbsm.com>, Ray Hunter <v6ops@globis.net>
References: <20131017032024.5051.20799.idtracker@ietfa.amsl.com> <1381980305.36254.YahooMailNeo@web2803.biz.mail.ne1.yahoo.com> <5263C783.1080001@globis.net> <1382396300.22968.YahooMailNeo@web2801.biz.mail.ne1.yahoo.com> <526616C4.40304@globis.net> <4FC37E442D05A748896589E468752CAA0CA88734@PWN401EA160.ent.corp.bcbsm.com> <52695E3A.9090406@globis.net> <4FC37E442D05A748896589E468752CAA0CA8A36F@PWN401EA160.ent.corp.bcbsm.com> <526AAC81.3050402@globis.net> <4FC37E442D05A748896589E468752CAA0CA8B1CD@PWN401EA160.ent.corp.bcbsm.com>
In-Reply-To: <4FC37E442D05A748896589E468752CAA0CA8B1CD@PWN401EA160.ent.corp.bcbsm.com>
X-Enigmail-Version: 1.6
Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="LXMC8R1hVTxIoGgRMCMvKvREBwr3bvGvq"
Cc: v6ops WG <v6ops@ietf.org>, 6man WG <ipv6@ietf.org>, "ippm@ietf.org" <ippm@ietf.org>
Subject: Re: [v6ops] Fw: New Version Notification for draft-elkins-6man-ipv6-pdm-dest-option-04.txt
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, 28 Oct 2013 16:24:19 -0000

Hi Michael.

On 10/28/13 12:13 PM, Ackermann, Michael wrote:
> Hey Ray
> 
> It appears your experiences with Time Synch and Stratum levels are
> different than mine.   In the older Telecom and Voice World Stratum
> was a great indicator of clocking accuracy.   Still is as far as I
> know.   This was always true with or without NTP in the picture. And
> whenever we had two Stratum 0's or 1's, be they the same or different
> masters, they WOULD be in synch.   We never had a situation that was
> an exception to that, with or without NTP.

The NTP definition of stratum is different from that used in the
telecommunications domain.  The primary feature of a NTP stratum 0 clock
is the ability to generate accurate pulse per second signals, hence
calling them reference clocks.  It should be noted that in NTP, stratum
0 clocks are *not* NTP servers, they are the source of time information
to stratum 1 servers that serve time via NTP.

Regards,
Brian