
From nobody Fri Apr  1 05:11:48 2016
Return-Path: <kristof.teichel@ptb.de>
X-Original-To: tictoc@ietfa.amsl.com
Delivered-To: tictoc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 76C2712D109 for <tictoc@ietfa.amsl.com>; Fri,  1 Apr 2016 05:11:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.909
X-Spam-Level: 
X-Spam-Status: No, score=-1.909 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 89aW30vaTz7s for <tictoc@ietfa.amsl.com>; Fri,  1 Apr 2016 05:11:44 -0700 (PDT)
Received: from mx1.bs.ptb.de (mx1.bs.ptb.de [192.53.103.120]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6D67F12D1BF for <tictoc@ietf.org>; Fri,  1 Apr 2016 05:11:44 -0700 (PDT)
Received: from smtp-hub.bs.ptb.de (smtpint01.bs.ptb.de [141.25.87.32]) by mx1.bs.ptb.de  with ESMTP id u31CBfbA023434-u31CBfbC023434 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA bits=256 verify=FAIL); Fri, 1 Apr 2016 14:11:41 +0200
Received: from rose.bs.ptb.de (rose.bs.ptb.de [141.25.85.201]) by smtp-hub.bs.ptb.de (Postfix) with ESMTP id E28AEC4A92; Fri,  1 Apr 2016 14:11:41 +0200 (CEST)
In-Reply-To: <20160331182727.C8A29406078@ip-64-139-1-69.sjc.megapath.net>
References: Message from Sharon Goldberg <goldbe@cs.bu.edu> of "Thu, 31 Mar 2016 12:37:40 EDT." <CAJHGrrQ_HQiqkvF3O6RRtLk=m4=cFF7RT9K7CVEMFXZw8woARA@mail.gmail.com> <20160331182727.C8A29406078@ip-64-139-1-69.sjc.megapath.net>
To: Hal Murray <hmurray@megapathdsl.net>, "NTP Working Group" <ntpwg@lists.ntp.org>, tictoc@ietf.org
MIME-Version: 1.0
Message-ID: <OF12EDCE54.F5A02BBA-ONC1257F88.0042DCF5-C1257F88.0042FC7F@ptb.de>
From: kristof.teichel@ptb.de
Date: Fri, 1 Apr 2016 14:11:39 +0200
Content-Type: multipart/alternative; boundary="=_alternative 0042FC7DC1257F88_="
Archived-At: <http://mailarchive.ietf.org/arch/msg/tictoc/ICjiftN7piqTQUTUVuuKkzmHXf8>
Subject: Re: [TICTOC] [ntpwg]  WGLC on NTS: Round trips for key exchange
X-BeenThere: tictoc@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Timing over IP Connection and Transfer of Clock BOF <tictoc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tictoc>, <mailto:tictoc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tictoc/>
List-Post: <mailto:tictoc@ietf.org>
List-Help: <mailto:tictoc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tictoc>, <mailto:tictoc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 01 Apr 2016 12:11:47 -0000

Dies ist eine mehrteilige Nachricht im MIME-Format.
--=_alternative 0042FC7DC1257F88_=
Content-Type: text/plain; charset="US-ASCII"

> Von: Hal Murray <hmurray@megapathdsl.net>
> An: NTP Working Group <ntpwg@lists.ntp.org>, tictoc@ietf.org
> Kopie: Hal Murray <hmurray@megapathdsl.net>
> Datum: 31.03.2016 20:27
> Betreff: Re: [TICTOC] [ntpwg]  WGLC on NTS: Round trips for key exchange
> Gesendet von: "TICTOC" <tictoc-bounces@ietf.org>
> 
> 
> goldbe@cs.bu.edu said:
> > I suggest that NTS should encourage users to write the current time to 
a
> > persistent file that is available upon reboot.  This should be 
overwritten
> > on every clock update.    Then, when the client reboots, it can check 
that
> > the expiry time of the certificates is no earlier than the last time 
time
> > written to the presisent file.  This limits the impact of attackers 
that use
> > old compromised certificates to break the security of NTS. 
> 
> I think the issue of getting started is much more complicated than that.
> 
> It probably deserves a separate document to collect all the ideas.

I agree.

> Individual documents like NTS should be explicit about what they are 
> assuming.  Do they need valid (how close?) time or valid certificates or 
???

I can see that a paragraph like this might be necessary. We will think 
about where it's appropriate (NTS main document or NTS-4-NTP).
 
> The above paragraph assumes the system has a writable file system.  The 
> "every clock update" may be too expensive for some systems.
> 
> What happens the first time?  Even if you assume that file was sanely 
> initialized at the factory, the unit may have sat on a shelf for a long 
time.
> 
> What do you do if your clock gets set far into the future?
> 
> 
> -- 
> These are my opinions.  I hate spam.
> 
> 
> 
> _______________________________________________
> TICTOC mailing list
> TICTOC@ietf.org
> https://www.ietf.org/mailman/listinfo/tictoc

--=_alternative 0042FC7DC1257F88_=
Content-Type: text/html; charset="US-ASCII"

<tt><font size=2>&gt; Von: Hal Murray &lt;hmurray@megapathdsl.net&gt;</font></tt>
<br><tt><font size=2>&gt; An: NTP Working Group &lt;ntpwg@lists.ntp.org&gt;,
tictoc@ietf.org</font></tt>
<br><tt><font size=2>&gt; Kopie: Hal Murray &lt;hmurray@megapathdsl.net&gt;</font></tt>
<br><tt><font size=2>&gt; Datum: 31.03.2016 20:27</font></tt>
<br><tt><font size=2>&gt; Betreff: Re: [TICTOC] [ntpwg] &nbsp;WGLC on NTS:
Round trips for key exchange</font></tt>
<br><tt><font size=2>&gt; Gesendet von: &quot;TICTOC&quot; &lt;tictoc-bounces@ietf.org&gt;</font></tt>
<br><tt><font size=2>&gt; <br>
&gt; <br>
&gt; goldbe@cs.bu.edu said:<br>
&gt; &gt; I suggest that NTS should encourage users to write the current
time to a<br>
&gt; &gt; persistent file that is available upon reboot. &nbsp;This should
be overwritten<br>
&gt; &gt; on every clock update. &nbsp; &nbsp;Then, when the client reboots,
it can check that<br>
&gt; &gt; the expiry time of the certificates is no earlier than the last
time time<br>
&gt; &gt; written to the presisent file. &nbsp;This limits the impact of
attackers that use<br>
&gt; &gt; old compromised certificates to break the security of NTS. <br>
&gt; <br>
&gt; I think the issue of getting started is much more complicated than
that.<br>
&gt; <br>
&gt; It probably deserves a separate document to collect all the ideas.</font></tt>
<br>
<br><tt><font size=2>I agree.</font></tt>
<br><tt><font size=2><br>
&gt; Individual documents like NTS should be explicit about what they are
<br>
&gt; assuming. &nbsp;Do they need valid (how close?) time or valid certificates
or ???</font></tt>
<br>
<br><tt><font size=2>I can see that a paragraph like this might be necessary.
We will think about where it's appropriate (NTS main document or NTS-4-NTP).<br>
 <br>
&gt; The above paragraph assumes the system has a writable file system.
&nbsp;The <br>
&gt; &quot;every clock update&quot; may be too expensive for some systems.<br>
&gt; <br>
&gt; What happens the first time? &nbsp;Even if you assume that file was
sanely <br>
&gt; initialized at the factory, the unit may have sat on a shelf for a
long time.<br>
&gt; <br>
&gt; What do you do if your clock gets set far into the future?<br>
&gt; <br>
&gt; <br>
&gt; -- <br>
&gt; These are my opinions. &nbsp;I hate spam.<br>
&gt; <br>
&gt; <br>
&gt; <br>
&gt; _______________________________________________<br>
&gt; TICTOC mailing list<br>
&gt; TICTOC@ietf.org<br>
&gt; </font></tt><a href=https://www.ietf.org/mailman/listinfo/tictoc><tt><font size=2>https://www.ietf.org/mailman/listinfo/tictoc</font></tt></a><tt><font size=2><br>
</font></tt>
--=_alternative 0042FC7DC1257F88_=--


From nobody Fri Apr  1 05:18:56 2016
Return-Path: <kristof.teichel@ptb.de>
X-Original-To: tictoc@ietfa.amsl.com
Delivered-To: tictoc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EE02312D12B for <tictoc@ietfa.amsl.com>; Fri,  1 Apr 2016 05:18:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.909
X-Spam-Level: 
X-Spam-Status: No, score=-1.909 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 15mW_5VMVMUT for <tictoc@ietfa.amsl.com>; Fri,  1 Apr 2016 05:18:51 -0700 (PDT)
Received: from mx1.bs.ptb.de (mx1.bs.ptb.de [192.53.103.120]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8256612D123 for <tictoc@ietf.org>; Fri,  1 Apr 2016 05:18:51 -0700 (PDT)
Received: from smtp-hub.bs.ptb.de (smtpint01.bs.ptb.de [141.25.87.32]) by mx1.bs.ptb.de  with ESMTP id u31CIlsS023968-u31CIlsU023968 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA bits=256 verify=FAIL); Fri, 1 Apr 2016 14:18:47 +0200
Received: from rose.bs.ptb.de (rose.bs.ptb.de [141.25.85.201]) by smtp-hub.bs.ptb.de (Postfix) with ESMTP id 533B2C4AA6; Fri,  1 Apr 2016 14:18:47 +0200 (CEST)
In-Reply-To: <CAJHGrrRB8t3gf6On8z-Q-z+TShPAES86fZVvHn+582mu0d1vgQ@mail.gmail.com>
References: <CAJHGrrSxvxRfe8VRRxh8Eh5tkCw-D0t7uuA_YqcLZif=ho45nA@mail.gmail.com> <20160329152654.GH20902@localhost> <OF07030A8A.8267E74D-ONC1257F87.002F2081-C1257F87.0041C9FA@ptb.de> <20160331125908.GG834@localhost> <CAJHGrrRB8t3gf6On8z-Q-z+TShPAES86fZVvHn+582mu0d1vgQ@mail.gmail.com>
To: Sharon Goldberg <goldbe@cs.bu.edu>, "NTP Working Group" <ntpwg@lists.ntp.org>, tictoc@ietf.org
MIME-Version: 1.0
Message-ID: <OF35BF7FFD.C1AF1EA6-ONC1257F88.00430682-C1257F88.0043A34A@ptb.de>
From: kristof.teichel@ptb.de
Date: Fri, 1 Apr 2016 14:18:46 +0200
Content-Type: multipart/alternative; boundary="=_alternative 0043A348C1257F88_="
Archived-At: <http://mailarchive.ietf.org/arch/msg/tictoc/5D7P-9iovUtRCV-ZLJf0WFSNP6k>
Subject: Re: [TICTOC] [ntpwg]  WGLC on NTS: Round trips for key exchange
X-BeenThere: tictoc@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Timing over IP Connection and Transfer of Clock BOF <tictoc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tictoc>, <mailto:tictoc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tictoc/>
List-Post: <mailto:tictoc@ietf.org>
List-Help: <mailto:tictoc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tictoc>, <mailto:tictoc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 01 Apr 2016 12:18:54 -0000

Dies ist eine mehrteilige Nachricht im MIME-Format.
--=_alternative 0043A348C1257F88_=
Content-Type: text/plain; charset="US-ASCII"

> > On Thu, Mar 31, 2016 at 8:59 AM, Miroslav Lichvar 
<mlichvar@redhat.com> wrote:
> > On Thu, Mar 31, 2016 at 01:58:35PM +0200, kristof.teichel@ptb.de 
wrote:
> > > To be honest, we had never assumed for IP fragmentation (on one 
request
> > > and one response) to be a huge problem.
> > 
> > One request and response could still be a problem. If the client is
> > not able to receive fragmented packets, it won't be able to initialize
> > the NTS association.
>
> Right, to second that, there are middleboxes that block fragmented 
packets.
>  
> > > If people see grave problems with it, we would welcome an 
> > > elaboration as  to why this is.
> > 
> > I'm not sure and I was hoping others would comment on that. It seems
> > to me problems with IPv4 fragmentation are quite common due to
> > firewalls dropping ICMP packets or IP fragments, and IPv6 doesn't seem
> > to recommend sending packets larger than 1500.
> 
> To add to that, fragmentation is commonly used as an attack vector. 
> I would strongly discourage the use of IP fragmentation in what is 
> supposed to be a security protocol.  Please see these references for
> a small sampling of examples.

Is the issue specific to IP fragmentation of UDP packets? Or to IP 
fragmentation in general? 
(I'm assuming it does not apply to all possible kinds of packet 
fragmentation.)
I'm sorry, I have yet to go over the linked documents.
 
> 
https://www.nanog.org/sites/default/files/mon.general.fragmentation.bonica.pdf

> 
> http://www.hpl.hp.com/techreports/Compaq-DEC/WRL-87-3.pdf
> 
> http://arxiv.org/abs/1205.4011
> 
> https://media.blackhat.com/bh-eu-12/Atlasis/bh-eu-12-Atlasis-
> Attacking_IPv6-WP.pdf
> 
> http://www.iss.net/security_center/reference/vuln/TearDrop.htm
> 
> 
https://www.offensive-security.com/wifu/Fragmentation-Attack-in-Practice.pdf

>
> Even if you don't see a SPECIFIC attack on NTS in these papers, my 
> point  is that we can usually find a way to exploit IP fragmentation
> in unexpected ways to break security. This has happened over and 
> over in the last two decades on many different protocols. In fact 
> this is exactly what we did in our recent NTP paper, Section VI:
> 
> .https://eprint.iacr.org/2015/1020.pdf
>
> I would strongly object to having NTS rely on IP fragmentation.   
> This would be a horrible design decision.

Noted.
--=_alternative 0043A348C1257F88_=
Content-Type: text/html; charset="US-ASCII"

<tt><font size=2>&gt; &gt; On Thu, Mar 31, 2016 at 8:59 AM, Miroslav Lichvar
&lt;mlichvar@redhat.com&gt; wrote:</font></tt>
<br><tt><font size=2>&gt; &gt; On Thu, Mar 31, 2016 at 01:58:35PM +0200,
kristof.teichel@ptb.de wrote:<br>
&gt; &gt; &gt; To be honest, we had never assumed for IP fragmentation
(on one request<br>
&gt; &gt; &gt; and one response) to be a huge problem.<br>
&gt; &gt; <br>
&gt; &gt; One request and response could still be a problem. If the client
is<br>
&gt; &gt; not able to receive fragmented packets, it won't be able to initialize<br>
&gt; &gt; the NTS association.<br>
&gt;<br>
&gt; Right, to second that, there are middleboxes that block fragmented
packets.<br>
&gt; &nbsp;</font></tt>
<br><tt><font size=2>&gt; &gt; &gt; If people see grave problems with it,
we would welcome an <br>
&gt; &gt; &gt; elaboration as&nbsp; to why this is.<br>
&gt; &gt; <br>
&gt; &gt; I'm not sure and I was hoping others would comment on that. It
seems<br>
&gt; &gt; to me problems with IPv4 fragmentation are quite common due to<br>
&gt; &gt; firewalls dropping ICMP packets or IP fragments, and IPv6 doesn't
seem<br>
&gt; &gt; to recommend sending packets larger than 1500.</font></tt>
<br><tt><font size=2>&gt; <br>
&gt; To add to that, fragmentation is commonly used as an attack vector.&nbsp;<br>
&gt; I would strongly discourage the use of IP fragmentation in what is
<br>
&gt; supposed to be a security protocol.&nbsp; Please see these references
for<br>
&gt; a small sampling of examples.</font></tt>
<br>
<br><tt><font size=2>Is the issue specific to IP fragmentation of UDP packets?
Or to IP fragmentation in general? </font></tt>
<br><tt><font size=2>(I'm assuming it does not apply to all possible kinds
of packet fragmentation.)</font></tt>
<br><tt><font size=2>I'm sorry, I have yet to go over the linked documents.</font></tt>
<br><tt><font size=2>&nbsp;<br>
&gt; </font></tt><a href=https://www.nanog.org/sites/default/files/mon.general.fragmentation.bonica.pdf><tt><font size=2>https://www.nanog.org/sites/default/files/mon.general.fragmentation.bonica.pdf</font></tt></a><tt><font size=2><br>
&gt; <br>
&gt; </font></tt><a href="http://www.hpl.hp.com/techreports/Compaq-DEC/WRL-87-3.pdf"><tt><font size=2>http://www.hpl.hp.com/techreports/Compaq-DEC/WRL-87-3.pdf</font></tt></a><tt><font size=2><br>
&gt; <br>
&gt; </font></tt><a href=http://arxiv.org/abs/1205.4011><tt><font size=2>http://arxiv.org/abs/1205.4011</font></tt></a><tt><font size=2><br>
&gt; <br>
&gt; </font></tt><a href="https://media.blackhat.com/bh-eu-12/Atlasis/bh-eu-12-Atlasis-"><tt><font size=2>https://media.blackhat.com/bh-eu-12/Atlasis/bh-eu-12-Atlasis-</font></tt></a><tt><font size=2><br>
&gt; Attacking_IPv6-WP.pdf<br>
&gt; <br>
&gt; </font></tt><a href=http://www.iss.net/security_center/reference/vuln/TearDrop.htm><tt><font size=2>http://www.iss.net/security_center/reference/vuln/TearDrop.htm</font></tt></a><tt><font size=2><br>
&gt; <br>
&gt; </font></tt><a href="https://www.offensive-security.com/wifu/Fragmentation-Attack-in-Practice.pdf"><tt><font size=2>https://www.offensive-security.com/wifu/Fragmentation-Attack-in-Practice.pdf</font></tt></a><tt><font size=2><br>
&gt;</font></tt>
<br><tt><font size=2>&gt; Even if you don't see a SPECIFIC attack on NTS
in these papers, my <br>
&gt; point&nbsp; is that we can usually find a way to exploit IP fragmentation<br>
&gt; in unexpected ways to break security. This has happened over and <br>
&gt; over in the last two decades on many different protocols. In fact
<br>
&gt; this is exactly what we did in our recent NTP paper, Section VI:<br>
&gt; <br>
&gt; .https://eprint.iacr.org/2015/1020.pdf<br>
&gt;</font></tt>
<br><tt><font size=2>&gt; I would strongly object to having NTS rely on
IP fragmentation.&nbsp;&nbsp; <br>
&gt; This would be a horrible design decision.<br>
</font></tt>
<br><tt><font size=2>Noted.</font></tt>
--=_alternative 0043A348C1257F88_=--


From nobody Fri Apr  1 08:25:34 2016
Return-Path: <Greg.Dowd@microsemi.com>
X-Original-To: tictoc@ietfa.amsl.com
Delivered-To: tictoc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5CA6412D68E for <tictoc@ietfa.amsl.com>; Fri,  1 Apr 2016 08:25:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=mscc365.onmicrosoft.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RODtepKyMsEQ for <tictoc@ietfa.amsl.com>; Fri,  1 Apr 2016 08:25:29 -0700 (PDT)
Received: from na01-bn1-obe.outbound.protection.outlook.com (mail-bn1on0645.outbound.protection.outlook.com [IPv6:2a01:111:f400:fc10::645]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6049312D6B6 for <tictoc@ietf.org>; Fri,  1 Apr 2016 08:25:07 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mscc365.onmicrosoft.com; s=selector1-microsemi-com; h=From:To:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=+/CpvH7Y+TNaEHTlZ19xeUuZqoarpIEUB00jXKPb+u8=; b=U0ncpUefshcBV2B81d57QXtzVwi/akX76OycqObK5gKGjTOcJGsPpVqdUjTHtDNBm/I18l3ss7JJz9nqGejfMGx4/X7yfULsQPzFGk3s8IKu3/oiXx1kG3Qd5NbYRqmrjFClMqk63G72xqFdPqBehkxpmVx3SqUeO6vr5qGp2hY=
Received: from BLUPR02CA043.namprd02.prod.outlook.com (10.160.23.161) by DM2PR0201MB1008.namprd02.prod.outlook.com (10.160.219.142) with Microsoft SMTP Server (TLS) id 15.1.443.12; Fri, 1 Apr 2016 15:24:50 +0000
Received: from BY2FFO11FD032.protection.gbl (2a01:111:f400:7c0c::168) by BLUPR02CA043.outlook.office365.com (2a01:111:e400:8ad::33) with Microsoft SMTP Server (TLS) id 15.1.447.15 via Frontend Transport; Fri, 1 Apr 2016 15:24:50 +0000
Authentication-Results: spf=none (sender IP is 208.19.100.20) smtp.mailfrom=microsemi.com; lists.ntp.org; dkim=none (message not signed) header.d=none;lists.ntp.org; dmarc=none action=none header.from=microsemi.com;
Received-SPF: None (protection.outlook.com: microsemi.com does not designate permitted sender hosts)
Received: from avsrvexchhts2.microsemi.net (208.19.100.20) by BY2FFO11FD032.mail.protection.outlook.com (10.1.14.210) with Microsoft SMTP Server (TLS) id 15.1.453.6 via Frontend Transport; Fri, 1 Apr 2016 15:24:48 +0000
Received: from SJSRVEXCHHTS1.microsemi.net (10.241.34.105) by avsrvexchhts2.microsemi.net (10.100.34.106) with Microsoft SMTP Server (TLS) id 14.3.266.1; Fri, 1 Apr 2016 08:24:43 -0700
Received: from SJSRVEXCHMBX2.microsemi.net ([fe80::6da0:6f9d:d5d1:3d5d]) by sjsrvexchhts1.microsemi.net ([::1]) with mapi id 14.03.0266.001; Fri, 1 Apr 2016 08:24:42 -0700
From: Greg Dowd <Greg.Dowd@microsemi.com>
To: Sharon Goldberg <sharon.goldbe@gmail.com>, "kristof.teichel@ptb.de" <kristof.teichel@ptb.de>
Thread-Topic: [ntpwg] [TICTOC] WGLC on NTS: Round trips for key exchange
Thread-Index: AQHRjCOg8DZ6a195Q0ieQP0IjDuxIp91OaLg
Date: Fri, 1 Apr 2016 15:24:41 +0000
Message-ID: <8D2BF679AAC7C346848A489074F9F8BF7AAFC3EA@sjsrvexchmbx2.microsemi.net>
References: <CAJHGrrSxvxRfe8VRRxh8Eh5tkCw-D0t7uuA_YqcLZif=ho45nA@mail.gmail.com> <20160329152654.GH20902@localhost> <OF07030A8A.8267E74D-ONC1257F87.002F2081-C1257F87.0041C9FA@ptb.de> <20160331125908.GG834@localhost> <CAJHGrrRB8t3gf6On8z-Q-z+TShPAES86fZVvHn+582mu0d1vgQ@mail.gmail.com> <OF35BF7FFD.C1AF1EA6-ONC1257F88.00430682-C1257F88.0043A34A@ptb.de> <BDF6E64B-B7BB-442A-9AA0-FCEBD5374462@gmail.com>
In-Reply-To: <BDF6E64B-B7BB-442A-9AA0-FCEBD5374462@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.241.128.82]
Content-Type: multipart/alternative; boundary="_000_8D2BF679AAC7C346848A489074F9F8BF7AAFC3EAsjsrvexchmbx2mi_"
MIME-Version: 1.0
X-EOPAttributedMessage: 0
X-Forefront-Antispam-Report: CIP:208.19.100.20; IPV:NLI; CTRY:US; EFV:NLI; SFV:NSPM; SFS:(10009020)(2980300002)(428002)(377454003)(24454002)(189002)(243025005)(199003)(16236675004)(50986999)(54356999)(15975445007)(76176999)(19617315012)(19300405004)(106466001)(106116001)(101416001)(86362001)(102836003)(1220700001)(3846002)(1096002)(105586002)(19580395003)(19580405001)(6116002)(4326007)(15395725005)(55846006)(551934003)(2906002)(790700001)(16796002)(19625215002)(84326002)(31430400001)(33656002)(586003)(5008740100001)(2501003)(512874002)(5250100002)(11100500001)(5004730100002)(92566002)(87936001)(2950100001)(2920100001)(6806005)(5003600100002)(189998001)(81166005)(53416004)(2900100001)(5001770100001)(562404015)(19627235001); DIR:OUT; SFP:1101; SCL:1; SRVR:DM2PR0201MB1008; H:avsrvexchhts2.microsemi.net;  FPR:; SPF:None; MLV:sfv; MX:1; A:1; LANG:en; 
X-Microsoft-Exchange-Diagnostics: 1; BY2FFO11FD032; 1:EQZoaBISiO9L8Oh6UGePjmobmh5yBHq5gdMasKoSH/iY+9lhl43FLjFyHJglBgaF1PVx035rUvqUPjd2tiWEMFBy5K3gmr5bkAoLEyniDc6MZWnITxrbz2IxiYidsut8YUmvzi1EF54qD+cfsLBk7Icyng/uMPun6ThB1yAwyvvC3NDmqqGGanAzV8FtxL3f1d8SgceGvpKtv+bNKYXyWxZggNi9y0lGHn4G9JnhkpR1lEiyID7oCxTXDBBxsY6GXJETTcrJW2zkAaH07uKMUFvt34ajhbZID/bwc2+FrJCW3mlYJP34PZAmB0qEjAqFZMJjdoRYJMUl/IgsvfabLLshNB6NGmsAlgSWuNj5BsmrKkjLTwHUzEctdJkPeaD1VXPexOWpuj/Z2zDl/6enp7b4lE2wBngR7oEZgbpPzjH7soKdHRNUzCErU3u2/BZmoMBsjjLo1YOU/Ofyj7JA/WP4P6U8rQ75klQaG72QC20bmwRhPHl1v7iXi9vGWGot
X-MS-Office365-Filtering-Correlation-Id: 02db6e9f-dd6d-417c-a7c8-08d35a41c418
X-Microsoft-Exchange-Diagnostics: 1; DM2PR0201MB1008; 2:1O0VL+4a9xpvbvvaniBkGZ49Oak7vQo+WPlx2yHBHjShq/HwacDjT5/iIHdndRUjr4yIt8NqXSjisvoMX2gt6hSokny45q4FXmT0ARSoQDr1ztEDcHv387KkVnMte82lOk/8FlcPeYR/cqfx3Kp1XKss7zZX8hXajMapj/y5zB1RMCYiTHGbfe2sBWeEB0K0; 3:m19gNXetRfHg4meUT/Iddas6i1wpSj2OhqW3i4aFkv5ump6h4WLn58urVeqieAYqMN6sTWZJA08OswdGJDxW0SxDdxumkhJkXhRLv42dpUom+xl8/BgKRJZR+mB0feSn5NW5ATF7ltbsso+aesK4zBGXplVaE70Thl8xraTCumZe/09FzTXGX0IW1804Z849c1W0I9KbPhmrG0g00SoZi0kI659/eiahgcfQ5sE4zeI=; 25:6c3q0Oq0mBr75Z3YYGXP7d3SZfIxPWWFHkVqjoPhPflgr/kMuT//QUF0jUCMqKjdPALgdqebmUFW5GUzgMaGv/DoIZ9HKFUxVwBuahuZwmHzvLl2g9w58fgBGLr0527A1BXBFdv+zSetIbzeNM770z23lWLm3+UH6yABk63qDeeqAcFQ5uOk4udavsxanxSczfkeux2wFA3or5X+NmVJqpUazk9T6OKM8DeVGShoXMb3m8IjORKpXmDs1toQIUEUhHo0YstxtxiObOoOKMGOYIUTEvxLM0LHnAuFJX21wtKMZoXH67hnK+4FSSkWgsKWx8tEGHwYJV/IY8x3Q7M+95Bsw2fD+UBw5nndSot0Qgk=
X-Microsoft-Antispam: UriScan:;BCL:0;PCL:0;RULEID:;SRVR:DM2PR0201MB1008;
X-Microsoft-Exchange-Diagnostics: 1; DM2PR0201MB1008; 20:07djoHlgNg0AWeQMyEwMRxSZVf8aV1CHskhMGauZ31lsrpqUcvQ2pzdubEQjWFxgk2zF/9DJ2Y6sHfhwfg6EQSciKCFdZI3HqWfXkKIkrg76FIuPUQUl6++WDiCh5Wp6Oscc7erHs5LTqxoK3fgVS6b3wGHo3uPDLkrdrO5To5zGfMlF3ns68IXnsfPpFg1XS296EcvLxRUQx9D4TW/C0Kn21Sl/F6HVlMD1+TAJkhXK2iAMaV25lTIH1swFJplmOrxrv6B8D00kYIHR1sVACx/GRbivvQUpj/8axCsUOO+ovbMr7FayEDPiDPRgV5Ee3q1pZzqwbX7MG0f4ehzrsoIu3pLIrRWwfpr4MYzCO7+mUZ4g3ZrxdgWPVEtxTDtj93Na+cCmAzEb6dhI+4+OnXNVx6rP/gEVCloUGcUm6lrmLEWpoB9iKSBov03a7al611RsYVO4caZruncJB1JWR4PAWQLJz2jOnrzNqjBXnbX8dJbbADs6uCEDzRxZoecz; 4:dxzWQD07tPDIcZlhuf8rJu8t/w709ffS4ZzuDA6bdLWvOn1kFKjqcGCj7IjDTbdZX4rWsHjVzsuPGZ6iuwrAAHmilSi5QKlnYFAWjQFm/JnHVoQfXA3Ku2/VwP7PR+kmtbNC36fxQWosqPlhgmsYW9zGUsOF/Vs6q2MMHsibJvUInYPWfXX9GgkLansM5rIEGg8b16aBiSn3zQRyS7UYe90+K54hGPapro0OBGYYCkr4PQhJ69chYiB6GDASKtEwhZn84Oe3tsw0cNmrfl1qSRXVdyOJOx+n9xb6I3vwfwmeuNnMz11wjKjv7IXsDTPCngxZHHB2Ld/SDNVl+hWr81RDU8QPj/PtMmqNy0aK4FGwcSlwrArejZveAH9tKHHc0A3viMHt/5Zq+KBOjqDxnLPb8BASPtPSMEjWV/iwGoZNiCx2U3lfCsN9Pc5N6AsY
X-Microsoft-Antispam-PRVS: <DM2PR0201MB1008E1AAA458BBA779CA57FBFC9A0@DM2PR0201MB1008.namprd02.prod.outlook.com>
X-Exchange-Antispam-Report-Test: UriScan:;
X-Exchange-Antispam-Report-CFA-Test: BCL:0; PCL:0; RULEID:(601004)(2401047)(13018025)(13023025)(13016025)(8121501046)(5005006)(13024025)(3002001)(10201501046); SRVR:DM2PR0201MB1008; BCL:0; PCL:0; RULEID:; SRVR:DM2PR0201MB1008; 
X-Forefront-PRVS: 0899B47777
X-Microsoft-Exchange-Diagnostics: =?us-ascii?Q?1; DM2PR0201MB1008; 23:855fGl0PWt/1zk9id7e2iO8i2J99g7crGi5P2qy?= =?us-ascii?Q?0t4ra++fDfWxcZEqhuJpSkLPqLYmykINQR/aObf32vUqeoowrPppOYtsZw8B?= =?us-ascii?Q?U7F0F0kMA4C2PN0i3Is9W1BXUHO1cDCEJlvpXC9CPRJTAsIcJKrxLXMcOfKz?= =?us-ascii?Q?IKT3ljXrPFcGajM+25c8mjPN2K2tAoxr6XKvfkpVZXXvvUlc96jT1NagBgE8?= =?us-ascii?Q?/Hip+phUHwu8H+joWhG2t3npbFB+gmaj0soAGpB0O+W7/wz+BjVu/2hwBX4N?= =?us-ascii?Q?OyhgbJzqWbznjZi3MPGo+64lVdUhxviZGeMs6O+tLw+fiYvP7wWcY2XY9IB1?= =?us-ascii?Q?rvus2UlIfL6YA0iZBWH85oaTHWm2nd28MTGjEPO0eBM690qIDla6PzKwvvFu?= =?us-ascii?Q?+Fnmix7MfhpOKhpFrLkFY89FSsLrdoOvDRJSJpfZVmvrYRPJ7wwwDYkB2zIp?= =?us-ascii?Q?Fv6vRL/ftrTjJTUmPmyFHOiBekc40lnFzYYjA7C3CHNraK4ZcbPuH/iglnz2?= =?us-ascii?Q?mf7+Wu3R/oQWVrskchrIcjfUDAmZxFDiHiUDuZaogur+nwUZ2svalzotCC6V?= =?us-ascii?Q?UoEqe6gjinuwPFdXmIPVYp7ggA5ccQWXDyEOub4xML4PUdtR8W4oRP2WJZrZ?= =?us-ascii?Q?XbiKGaX5zyfoyiw8TgacFgJtFGXezGtJCcArL6ci8c+Q1CRO2XfTYp+VtU33?= =?us-ascii?Q?XLEryk4MHfLbrpjbKSeOi07eQHmpAJjSq3goxIIz0zUBh8nfmtWq0e6XcLgd?= =?us-ascii?Q?+zXL9x5MHKc7fsWrwrseIiXfUYKXZ2ec/QZpzqwz7jVLMiGmJymnSVd3FGjz?= =?us-ascii?Q?0smTN7f8dh+x0jvfIYU9keANo2q4JdoMC35msJ75pE8DKSxTU29tcqnqASDm?= =?us-ascii?Q?T72179Tt/qWgiI6oQdnrYQIdtdausozF6f3DIyeKo/DiFGtxiX1nyJ/i4i6B?= =?us-ascii?Q?2HkYcyW+5owF3YhmLAn/gJHyqZnCI+/wW1w+Q9wS5KltH7Bbofqox+LoXNFB?= =?us-ascii?Q?fyrtjWgk7nRU2buZzLlNE0WxgOF2iLC+qf2aOScu+kK8ccdzdob+q9XdzPAg?= =?us-ascii?Q?l2OW4YDzofOwvqEappzDW00bXpMuWA/A5YTgcUdV+TpjFQbwIk1hZ0ciOtjj?= =?us-ascii?Q?15GRMBZ81WSAVPq44SiUrFuZLrr9PPTScbq91VqRPvjqQLjAt/d/SNua+PEb?= =?us-ascii?Q?xuf+dC8Ap6FEjQC1HwrNjOOyA5+JhTG4nGPa0KX7ejQwVox7KE0id9eRVH5w?= =?us-ascii?Q?S27rkjWayVoZI67KrYVCZCdrNbisG+iyOJsIs4LbBR5tunBjjIKH9k7T1k80?= =?us-ascii?Q?QOxGzpNHchVabLWSA46qeZp12c/dIyuuctTITdEXDBjfNkpf+WGimTDtIqNu?= =?us-ascii?Q?4G594Hr8GqplEZTq9P1IgsHORkj6MjP53mRhJE9HzRE6H5OvQFGKFfNVvSp1?= =?us-ascii?Q?ROhYohAF9glDacHaoAsd9M/dUTWGj4IgutFPOuhhcXnFFvKEVHCuKZ3qorud?= =?us-ascii?Q?01UtAyMGhH6tjxQ=3D=3D?=
X-Microsoft-Exchange-Diagnostics: 1; DM2PR0201MB1008; 5:lazXKFqdUADQAzW0KSH/zknS66HXh7w/D3H3JknnsKmjrn9y4WxwssWKyA90jTyfNzChopS5pQw1jgPxdSWUzYASfO0+WtKG1NEw/qDjo6H6RdaTis1p3PjmcazDjPP4XVfsLhRWY8SIaBFDyWLliw==; 24:DIt2ZUkjoph6j9CdnT42GYnJHCp2prXK8xFND/nj1Nn07z40v6TIDdjRHI7M8Do5ZECFPCNibCWUl9fM3xf9bG2hI5Qj3h2DYpusAdB74AY=
SpamDiagnosticOutput: 1:23
SpamDiagnosticMetadata: NSPM
X-OriginatorOrg: microsemi.com
X-MS-Exchange-CrossTenant-OriginalArrivalTime: 01 Apr 2016 15:24:48.2940 (UTC)
X-MS-Exchange-CrossTenant-Id: f267a5c8-86d8-4cc9-af71-1fd2c67c8fad
X-MS-Exchange-CrossTenant-OriginalAttributedTenantConnectingIp: TenantId=f267a5c8-86d8-4cc9-af71-1fd2c67c8fad; Ip=[208.19.100.20];  Helo=[avsrvexchhts2.microsemi.net]
X-MS-Exchange-CrossTenant-FromEntityHeader: HybridOnPrem
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DM2PR0201MB1008
Archived-At: <http://mailarchive.ietf.org/arch/msg/tictoc/sAwKbk1lV2wQrEsVdI13uVzNhNk>
Cc: NTP Working Group <ntpwg@lists.ntp.org>, "tictoc@ietf.org" <tictoc@ietf.org>
Subject: Re: [TICTOC] [ntpwg]  WGLC on NTS: Round trips for key exchange
X-BeenThere: tictoc@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Timing over IP Connection and Transfer of Clock BOF <tictoc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tictoc>, <mailto:tictoc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tictoc/>
List-Post: <mailto:tictoc@ietf.org>
List-Help: <mailto:tictoc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tictoc>, <mailto:tictoc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 01 Apr 2016 15:25:32 -0000

--_000_8D2BF679AAC7C346848A489074F9F8BF7AAFC3EAsjsrvexchmbx2mi_
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64

UmVtb3ZpbmcgZnJhZ21lbnRhdGlvbiBieSBkZWZpbml0aW9uIGluIGFuIGFwcGxpY2F0aW9uIHBy
b3RvY29sIGlzbuKAmXQgZXZlbiBwb3NzaWJsZSBpbiBJcHY0IGFzIHJvdXRlcnMgY2FuIGZyYWcu
ICBJdCBzZWVtcyBhIGxhcmdlIGNoYWxsZW5nZSB0byBtYW5pcHVsYXRlIGFueSB4NTA5IHN0YWNr
IGFuZCBub3QgZXhwZWN0IGZyYWdtZW50YXRpb24/ICBJIGtub3cgd2UgYWxsIHRlbmQgdG8gdGhp
bmsgb2YgMTUxNCAoSVAgb3ZlciA4MDIuMyBFdGhlcm5ldCkgYnV0IE1UVSBpcyBub3QgZGVmaW5l
ZCBieSB0aGUgZW5kcG9pbnRzIGJ1dCB0aGUgcGF0aC4gIEkgdGhpbmsgYSBudW1iZXIgb2YgdGlt
ZXMgdGhlcmUgaGFzIGJlZW4gYSBkaXNjdXNzaW9uIG9mIHJ1bm5pbmcgc29tZSBzZXNzaW9uIGNv
bXBvbmVudHMgb3ZlciB0Y3Agd2hpY2ggbWlnaHQgaGVscCB3aXRoIHNvbWUgb2YgdGhlIHNlcXVl
bmNpbmcgaXNzdWVzIG9mIHNwbGl0dGluZyB0aGUgdHJhbnNhY3Rpb24/ICBBIGJhY2t3YXJkcyBj
b21wYXRpYmlsaXR5IGNoYWxsZW5nZSBpcyB0aGF0LCB3aGlsZSBudHAgb3ducyB1ZHAgYW5kIHRj
cCAxMjMsIEkgdGhpbmsgbWFueSBleGlzdGluZyBmaXJld2FsbCBjb25maWd1cmF0aW9ucyB3b3Vs
ZCBkcm9wIHRjcCBjb25uZWN0aW9ucyBmb3IgMTIzLiAgSSBkb27igJl0IGtub3cgaG93IG1hbnkg
YXV0b2tleSBkZXBsb3ltZW50cyBhcmUgYWN0dWFsbHkgcnVubmluZyBzbyBwZXJoYXBzIGl0IGlz
IG5vdCB0aGF0IGJpZyBhbiBpc3N1ZS4NCg0KRnJvbTogbnRwd2cgW21haWx0bzpudHB3Zy1ib3Vu
Y2VzK2dyZWcuZG93ZD1taWNyb3NlbWkuY29tQGxpc3RzLm50cC5vcmddIE9uIEJlaGFsZiBPZiBT
aGFyb24gR29sZGJlcmcNClNlbnQ6IEZyaWRheSwgQXByaWwgMDEsIDIwMTYgNjowMCBBTQ0KVG86
IGtyaXN0b2YudGVpY2hlbEBwdGIuZGUNCkNjOiBOVFAgV29ya2luZyBHcm91cDsgdGljdG9jQGll
dGYub3JnDQpTdWJqZWN0OiBSZTogW250cHdnXSBbVElDVE9DXSBXR0xDIG9uIE5UUzogUm91bmQg
dHJpcHMgZm9yIGtleSBleGNoYW5nZQ0KDQpFWFRFUk5BTCBFTUFJTA0KDQoNClNoYXJvbiwgb24g
cGhvbmUNCk9uIEFwciAxLCAyMDE2LCBhdCA4OjE4IEFNLCBrcmlzdG9mLnRlaWNoZWxAcHRiLmRl
PG1haWx0bzprcmlzdG9mLnRlaWNoZWxAcHRiLmRlPiB3cm90ZToNCj4gPiBPbiBUaHUsIE1hciAz
MSwgMjAxNiBhdCA4OjU5IEFNLCBNaXJvc2xhdiBMaWNodmFyIDxtbGljaHZhckByZWRoYXQuY29t
PG1haWx0bzptbGljaHZhckByZWRoYXQuY29tPj4gd3JvdGU6DQo+ID4gT24gVGh1LCBNYXIgMzEs
IDIwMTYgYXQgMDE6NTg6MzVQTSArMDIwMCwga3Jpc3RvZi50ZWljaGVsQHB0Yi5kZTxtYWlsdG86
a3Jpc3RvZi50ZWljaGVsQHB0Yi5kZT4gd3JvdGU6DQo+ID4gPiBUbyBiZSBob25lc3QsIHdlIGhh
ZCBuZXZlciBhc3N1bWVkIGZvciBJUCBmcmFnbWVudGF0aW9uIChvbiBvbmUgcmVxdWVzdA0KPiA+
ID4gYW5kIG9uZSByZXNwb25zZSkgdG8gYmUgYSBodWdlIHByb2JsZW0uDQo+ID4NCj4gPiBPbmUg
cmVxdWVzdCBhbmQgcmVzcG9uc2UgY291bGQgc3RpbGwgYmUgYSBwcm9ibGVtLiBJZiB0aGUgY2xp
ZW50IGlzDQo+ID4gbm90IGFibGUgdG8gcmVjZWl2ZSBmcmFnbWVudGVkIHBhY2tldHMsIGl0IHdv
bid0IGJlIGFibGUgdG8gaW5pdGlhbGl6ZQ0KPiA+IHRoZSBOVFMgYXNzb2NpYXRpb24uDQo+DQo+
IFJpZ2h0LCB0byBzZWNvbmQgdGhhdCwgdGhlcmUgYXJlIG1pZGRsZWJveGVzIHRoYXQgYmxvY2sg
ZnJhZ21lbnRlZCBwYWNrZXRzLg0KPg0KPiA+ID4gSWYgcGVvcGxlIHNlZSBncmF2ZSBwcm9ibGVt
cyB3aXRoIGl0LCB3ZSB3b3VsZCB3ZWxjb21lIGFuDQo+ID4gPiBlbGFib3JhdGlvbiBhcyAgdG8g
d2h5IHRoaXMgaXMuDQo+ID4NCj4gPiBJJ20gbm90IHN1cmUgYW5kIEkgd2FzIGhvcGluZyBvdGhl
cnMgd291bGQgY29tbWVudCBvbiB0aGF0LiBJdCBzZWVtcw0KPiA+IHRvIG1lIHByb2JsZW1zIHdp
dGggSVB2NCBmcmFnbWVudGF0aW9uIGFyZSBxdWl0ZSBjb21tb24gZHVlIHRvDQo+ID4gZmlyZXdh
bGxzIGRyb3BwaW5nIElDTVAgcGFja2V0cyBvciBJUCBmcmFnbWVudHMsIGFuZCBJUHY2IGRvZXNu
J3Qgc2VlbQ0KPiA+IHRvIHJlY29tbWVuZCBzZW5kaW5nIHBhY2tldHMgbGFyZ2VyIHRoYW4gMTUw
MC4NCj4NCj4gVG8gYWRkIHRvIHRoYXQsIGZyYWdtZW50YXRpb24gaXMgY29tbW9ubHkgdXNlZCBh
cyBhbiBhdHRhY2sgdmVjdG9yLg0KPiBJIHdvdWxkIHN0cm9uZ2x5IGRpc2NvdXJhZ2UgdGhlIHVz
ZSBvZiBJUCBmcmFnbWVudGF0aW9uIGluIHdoYXQgaXMNCj4gc3VwcG9zZWQgdG8gYmUgYSBzZWN1
cml0eSBwcm90b2NvbC4gIFBsZWFzZSBzZWUgdGhlc2UgcmVmZXJlbmNlcyBmb3INCj4gYSBzbWFs
bCBzYW1wbGluZyBvZiBleGFtcGxlcy4NCg0KSXMgdGhlIGlzc3VlIHNwZWNpZmljIHRvIElQIGZy
YWdtZW50YXRpb24gb2YgVURQIHBhY2tldHM/IE9yIHRvIElQIGZyYWdtZW50YXRpb24gaW4gZ2Vu
ZXJhbD8NCihJJ20gYXNzdW1pbmcgaXQgZG9lcyBub3QgYXBwbHkgdG8gYWxsIHBvc3NpYmxlIGtp
bmRzIG9mIHBhY2tldCBmcmFnbWVudGF0aW9uLikNCkknbSBzb3JyeSwgSSBoYXZlIHlldCB0byBn
byBvdmVyIHRoZSBsaW5rZWQgZG9jdW1lbnRzLg0KDQpBbGwgZnJhZ21lbnRhdGlvbi4gVGhlIGZv
bGxvd2luZyBwYXBlciBhZmZlY3RzIGJvdGggdGNwIGFuZCB1ZHAuDQoNCmh0dHBzOi8vd3d3LnVz
ZW5peC5vcmcvbGVnYWN5L2V2ZW50L3dvb3QxMS90ZWNoL2ZpbmFsX2ZpbGVzL0dpbGFkLnBkZg0K
DQpBZ2Fpbi4gTXkgcG9pbnQgaXMgdGhhdCB3ZSBzaG91bGQgbm90IGJlIHJlbHlpbmcgb24gZnJh
Z21lbnRhdGlvbiBpbiBOVFMuIEl0IHJlZ3VsYXJseSBsZWFkcyB0byB1bmV4cGVjdGVkIGF0dGFj
a3MuDQoNCkFsc28gcXVvdGluZyBSb24gQm9uaWNhIGZyb20gdGhlIGZpcnN0IGxpbmtlZCBjb252
ZXJzYXRpb24gYmVsb3c6DQoNCiJwbGVhc2UgZG9uJ3Qgd3JpdGUgbmV3IGFwcGxpY2F0aW9ucyB0
aGF0IGZyYWdtZW50IHBhY2tldHMuIg0KDQpTaGFyb24NCg0KDQo+IGh0dHBzOi8vd3d3Lm5hbm9n
Lm9yZy9zaXRlcy9kZWZhdWx0L2ZpbGVzL21vbi5nZW5lcmFsLmZyYWdtZW50YXRpb24uYm9uaWNh
LnBkZg0KPg0KPiBodHRwOi8vd3d3LmhwbC5ocC5jb20vdGVjaHJlcG9ydHMvQ29tcGFxLURFQy9X
UkwtODctMy5wZGYNCj4NCj4gaHR0cDovL2FyeGl2Lm9yZy9hYnMvMTIwNS40MDExDQo+DQo+IGh0
dHBzOi8vbWVkaWEuYmxhY2toYXQuY29tL2JoLWV1LTEyL0F0bGFzaXMvYmgtZXUtMTItQXRsYXNp
cy0NCj4gQXR0YWNraW5nX0lQdjYtV1AucGRmDQo+DQo+IGh0dHA6Ly93d3cuaXNzLm5ldC9zZWN1
cml0eV9jZW50ZXIvcmVmZXJlbmNlL3Z1bG4vVGVhckRyb3AuaHRtDQo+DQo+IGh0dHBzOi8vd3d3
Lm9mZmVuc2l2ZS1zZWN1cml0eS5jb20vd2lmdS9GcmFnbWVudGF0aW9uLUF0dGFjay1pbi1QcmFj
dGljZS5wZGYNCj4NCj4gRXZlbiBpZiB5b3UgZG9uJ3Qgc2VlIGEgU1BFQ0lGSUMgYXR0YWNrIG9u
IE5UUyBpbiB0aGVzZSBwYXBlcnMsIG15DQo+IHBvaW50ICBpcyB0aGF0IHdlIGNhbiB1c3VhbGx5
IGZpbmQgYSB3YXkgdG8gZXhwbG9pdCBJUCBmcmFnbWVudGF0aW9uDQo+IGluIHVuZXhwZWN0ZWQg
d2F5cyB0byBicmVhayBzZWN1cml0eS4gVGhpcyBoYXMgaGFwcGVuZWQgb3ZlciBhbmQNCj4gb3Zl
ciBpbiB0aGUgbGFzdCB0d28gZGVjYWRlcyBvbiBtYW55IGRpZmZlcmVudCBwcm90b2NvbHMuIElu
IGZhY3QNCj4gdGhpcyBpcyBleGFjdGx5IHdoYXQgd2UgZGlkIGluIG91ciByZWNlbnQgTlRQIHBh
cGVyLCBTZWN0aW9uIFZJOg0KPg0KPiAuaHR0cHM6Ly9lcHJpbnQuaWFjci5vcmcvMjAxNS8xMDIw
LnBkZg0KPg0KPiBJIHdvdWxkIHN0cm9uZ2x5IG9iamVjdCB0byBoYXZpbmcgTlRTIHJlbHkgb24g
SVAgZnJhZ21lbnRhdGlvbi4NCj4gVGhpcyB3b3VsZCBiZSBhIGhvcnJpYmxlIGRlc2lnbiBkZWNp
c2lvbi4NCg0KTm90ZWQuDQo=

--_000_8D2BF679AAC7C346848A489074F9F8BF7AAFC3EAsjsrvexchmbx2mi_
Content-Type: text/html; charset="utf-8"
Content-Transfer-Encoding: base64

PGh0bWwgeG1sbnM6dj0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTp2bWwiIHhtbG5zOm89InVy
bjpzY2hlbWFzLW1pY3Jvc29mdC1jb206b2ZmaWNlOm9mZmljZSIgeG1sbnM6dz0idXJuOnNjaGVt
YXMtbWljcm9zb2Z0LWNvbTpvZmZpY2U6d29yZCIgeG1sbnM6bT0iaHR0cDovL3NjaGVtYXMubWlj
cm9zb2Z0LmNvbS9vZmZpY2UvMjAwNC8xMi9vbW1sIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcv
VFIvUkVDLWh0bWw0MCI+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIg
Y29udGVudD0idGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjxtZXRhIG5hbWU9IkdlbmVyYXRv
ciIgY29udGVudD0iTWljcm9zb2Z0IFdvcmQgMTQgKGZpbHRlcmVkIG1lZGl1bSkiPg0KPHN0eWxl
PjwhLS0NCi8qIEZvbnQgRGVmaW5pdGlvbnMgKi8NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6
Q2FtYnJpYTsNCglwYW5vc2UtMToyIDQgNSAzIDUgNCA2IDMgMiA0O30NCkBmb250LWZhY2UNCgl7
Zm9udC1mYW1pbHk6Q2FsaWJyaTsNCglwYW5vc2UtMToyIDE1IDUgMiAyIDIgNCAzIDIgNDt9DQpA
Zm9udC1mYWNlDQoJe2ZvbnQtZmFtaWx5OlRhaG9tYTsNCglwYW5vc2UtMToyIDExIDYgNCAzIDUg
NCA0IDIgNDt9DQovKiBTdHlsZSBEZWZpbml0aW9ucyAqLw0KcC5Nc29Ob3JtYWwsIGxpLk1zb05v
cm1hbCwgZGl2Lk1zb05vcm1hbA0KCXttYXJnaW46MGluOw0KCW1hcmdpbi1ib3R0b206LjAwMDFw
dDsNCglmb250LXNpemU6MTIuMHB0Ow0KCWZvbnQtZmFtaWx5OiJUaW1lcyBOZXcgUm9tYW4iLCJz
ZXJpZiI7fQ0KYTpsaW5rLCBzcGFuLk1zb0h5cGVybGluaw0KCXttc28tc3R5bGUtcHJpb3JpdHk6
OTk7DQoJY29sb3I6Ymx1ZTsNCgl0ZXh0LWRlY29yYXRpb246dW5kZXJsaW5lO30NCmE6dmlzaXRl
ZCwgc3Bhbi5Nc29IeXBlcmxpbmtGb2xsb3dlZA0KCXttc28tc3R5bGUtcHJpb3JpdHk6OTk7DQoJ
Y29sb3I6cHVycGxlOw0KCXRleHQtZGVjb3JhdGlvbjp1bmRlcmxpbmU7fQ0KdHQNCgl7bXNvLXN0
eWxlLXByaW9yaXR5Ojk5Ow0KCWZvbnQtZmFtaWx5OiJDb3VyaWVyIE5ldyIsInNlcmlmIjt9DQpz
cGFuLkVtYWlsU3R5bGUxOA0KCXttc28tc3R5bGUtdHlwZTpwZXJzb25hbC1yZXBseTsNCglmb250
LWZhbWlseToiQ2FsaWJyaSIsInNhbnMtc2VyaWYiOw0KCWNvbG9yOiMxRjQ5N0Q7fQ0KLk1zb0No
cERlZmF1bHQNCgl7bXNvLXN0eWxlLXR5cGU6ZXhwb3J0LW9ubHk7DQoJZm9udC1zaXplOjEwLjBw
dDt9DQpAcGFnZSBXb3JkU2VjdGlvbjENCgl7c2l6ZTo4LjVpbiAxMS4waW47DQoJbWFyZ2luOjEu
MGluIDEuMGluIDEuMGluIDEuMGluO30NCmRpdi5Xb3JkU2VjdGlvbjENCgl7cGFnZTpXb3JkU2Vj
dGlvbjE7fQ0KLS0+PC9zdHlsZT48IS0tW2lmIGd0ZSBtc28gOV0+PHhtbD4NCjxvOnNoYXBlZGVm
YXVsdHMgdjpleHQ9ImVkaXQiIHNwaWRtYXg9IjEwMjYiIC8+DQo8L3htbD48IVtlbmRpZl0tLT48
IS0tW2lmIGd0ZSBtc28gOV0+PHhtbD4NCjxvOnNoYXBlbGF5b3V0IHY6ZXh0PSJlZGl0Ij4NCjxv
OmlkbWFwIHY6ZXh0PSJlZGl0IiBkYXRhPSIxIiAvPg0KPC9vOnNoYXBlbGF5b3V0PjwveG1sPjwh
W2VuZGlmXS0tPg0KPC9oZWFkPg0KPGJvZHkgbGFuZz0iRU4tVVMiIGxpbms9ImJsdWUiIHZsaW5r
PSJwdXJwbGUiPg0KPGRpdiBjbGFzcz0iV29yZFNlY3Rpb24xIj4NCjxwIGNsYXNzPSJNc29Ob3Jt
YWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGli
cmkmcXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90Oztjb2xvcjojMUY0OTdEIj5SZW1vdmluZyBm
cmFnbWVudGF0aW9uIGJ5IGRlZmluaXRpb24gaW4gYW4gYXBwbGljYXRpb24gcHJvdG9jb2wgaXNu
4oCZdCBldmVuIHBvc3NpYmxlIGluIElwdjQgYXMgcm91dGVycyBjYW4gZnJhZy4mbmJzcDsgSXQg
c2VlbXMgYSBsYXJnZSBjaGFsbGVuZ2UgdG8gbWFuaXB1bGF0ZSBhbnkNCiB4NTA5IHN0YWNrIGFu
ZCBub3QgZXhwZWN0IGZyYWdtZW50YXRpb24/Jm5ic3A7IEkga25vdyB3ZSBhbGwgdGVuZCB0byB0
aGluayBvZiAxNTE0IChJUCBvdmVyIDgwMi4zIEV0aGVybmV0KSBidXQgTVRVIGlzIG5vdCBkZWZp
bmVkIGJ5IHRoZSBlbmRwb2ludHMgYnV0IHRoZSBwYXRoLiZuYnNwOyBJIHRoaW5rIGEgbnVtYmVy
IG9mIHRpbWVzIHRoZXJlIGhhcyBiZWVuIGEgZGlzY3Vzc2lvbiBvZiBydW5uaW5nIHNvbWUgc2Vz
c2lvbiBjb21wb25lbnRzIG92ZXIgdGNwDQogd2hpY2ggbWlnaHQgaGVscCB3aXRoIHNvbWUgb2Yg
dGhlIHNlcXVlbmNpbmcgaXNzdWVzIG9mIHNwbGl0dGluZyB0aGUgdHJhbnNhY3Rpb24/Jm5ic3A7
IEEgYmFja3dhcmRzIGNvbXBhdGliaWxpdHkgY2hhbGxlbmdlIGlzIHRoYXQsIHdoaWxlIG50cCBv
d25zIHVkcCBhbmQgdGNwIDEyMywgSSB0aGluayBtYW55IGV4aXN0aW5nIGZpcmV3YWxsIGNvbmZp
Z3VyYXRpb25zIHdvdWxkIGRyb3AgdGNwIGNvbm5lY3Rpb25zIGZvciAxMjMuJm5ic3A7IEkgZG9u
4oCZdCBrbm93DQogaG93IG1hbnkgYXV0b2tleSBkZXBsb3ltZW50cyBhcmUgYWN0dWFsbHkgcnVu
bmluZyBzbyBwZXJoYXBzIGl0IGlzIG5vdCB0aGF0IGJpZyBhbiBpc3N1ZS48bzpwPjwvbzpwPjwv
c3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEx
LjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVv
dDs7Y29sb3I6IzFGNDk3RCI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KPGRpdj4NCjxk
aXYgc3R5bGU9ImJvcmRlcjpub25lO2JvcmRlci10b3A6c29saWQgI0I1QzRERiAxLjBwdDtwYWRk
aW5nOjMuMHB0IDBpbiAwaW4gMGluIj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxiPjxzcGFuIHN0
eWxlPSJmb250LXNpemU6MTAuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O1RhaG9tYSZxdW90OywmcXVv
dDtzYW5zLXNlcmlmJnF1b3Q7Ij5Gcm9tOjwvc3Bhbj48L2I+PHNwYW4gc3R5bGU9ImZvbnQtc2l6
ZToxMC4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7VGFob21hJnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYm
cXVvdDsiPiBudHB3ZyBbbWFpbHRvOm50cHdnLWJvdW5jZXMmIzQzO2dyZWcuZG93ZD1taWNyb3Nl
bWkuY29tQGxpc3RzLm50cC5vcmddDQo8Yj5PbiBCZWhhbGYgT2YgPC9iPlNoYXJvbiBHb2xkYmVy
Zzxicj4NCjxiPlNlbnQ6PC9iPiBGcmlkYXksIEFwcmlsIDAxLCAyMDE2IDY6MDAgQU08YnI+DQo8
Yj5Ubzo8L2I+IGtyaXN0b2YudGVpY2hlbEBwdGIuZGU8YnI+DQo8Yj5DYzo8L2I+IE5UUCBXb3Jr
aW5nIEdyb3VwOyB0aWN0b2NAaWV0Zi5vcmc8YnI+DQo8Yj5TdWJqZWN0OjwvYj4gUmU6IFtudHB3
Z10gW1RJQ1RPQ10gV0dMQyBvbiBOVFM6IFJvdW5kIHRyaXBzIGZvciBrZXkgZXhjaGFuZ2U8bzpw
PjwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjwvZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+
PG86cD4mbmJzcDs8L286cD48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibWFyZ2lu
LWJvdHRvbToxMi4wcHQiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTQuMHB0O2ZvbnQtZmFtaWx5
OiZxdW90O0NhbWJyaWEmcXVvdDssJnF1b3Q7c2VyaWYmcXVvdDs7Y29sb3I6cmVkIj5FWFRFUk5B
TCBFTUFJTDwvc3Bhbj48bzpwPjwvbzpwPjwvcD4NCjxkaXY+DQo8ZGl2Pg0KPGRpdj4NCjxwIGNs
YXNzPSJNc29Ob3JtYWwiPjxicj4NCjxicj4NClNoYXJvbiwgb24gcGhvbmUmbmJzcDs8bzpwPjwv
bzpwPjwvcD4NCjwvZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1hcmdpbi1ib3R0
b206MTIuMHB0Ij5PbiBBcHIgMSwgMjAxNiwgYXQgODoxOCBBTSwgPGEgaHJlZj0ibWFpbHRvOmty
aXN0b2YudGVpY2hlbEBwdGIuZGUiPg0Ka3Jpc3RvZi50ZWljaGVsQHB0Yi5kZTwvYT4gd3JvdGU6
PG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxibG9ja3F1b3RlIHN0eWxlPSJtYXJnaW4tdG9wOjUu
MHB0O21hcmdpbi1ib3R0b206NS4wcHQiPg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjx0
dD48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEwLjBwdCI+Jmd0OyAmZ3Q7IE9uIFRodSwgTWFyIDMx
LCAyMDE2IGF0IDg6NTkgQU0sIE1pcm9zbGF2IExpY2h2YXIgJmx0OzxhIGhyZWY9Im1haWx0bzpt
bGljaHZhckByZWRoYXQuY29tIj5tbGljaHZhckByZWRoYXQuY29tPC9hPiZndDsgd3JvdGU6PC9z
cGFuPjwvdHQ+DQo8YnI+DQo8dHQ+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMC4wcHQiPiZndDsg
Jmd0OyBPbiBUaHUsIE1hciAzMSwgMjAxNiBhdCAwMTo1ODozNVBNICYjNDM7MDIwMCwgPGEgaHJl
Zj0ibWFpbHRvOmtyaXN0b2YudGVpY2hlbEBwdGIuZGUiPg0Ka3Jpc3RvZi50ZWljaGVsQHB0Yi5k
ZTwvYT4gd3JvdGU6PC9zcGFuPjwvdHQ+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMC4wcHQ7Zm9u
dC1mYW1pbHk6JnF1b3Q7Q291cmllciBOZXcmcXVvdDssJnF1b3Q7c2VyaWYmcXVvdDsiPjxicj4N
Cjx0dD4mZ3Q7ICZndDsgJmd0OyBUbyBiZSBob25lc3QsIHdlIGhhZCBuZXZlciBhc3N1bWVkIGZv
ciBJUCBmcmFnbWVudGF0aW9uIChvbiBvbmUgcmVxdWVzdDwvdHQ+PGJyPg0KPHR0PiZndDsgJmd0
OyAmZ3Q7IGFuZCBvbmUgcmVzcG9uc2UpIHRvIGJlIGEgaHVnZSBwcm9ibGVtLjwvdHQ+PGJyPg0K
PHR0PiZndDsgJmd0OyA8L3R0Pjxicj4NCjx0dD4mZ3Q7ICZndDsgT25lIHJlcXVlc3QgYW5kIHJl
c3BvbnNlIGNvdWxkIHN0aWxsIGJlIGEgcHJvYmxlbS4gSWYgdGhlIGNsaWVudCBpczwvdHQ+PGJy
Pg0KPHR0PiZndDsgJmd0OyBub3QgYWJsZSB0byByZWNlaXZlIGZyYWdtZW50ZWQgcGFja2V0cywg
aXQgd29uJ3QgYmUgYWJsZSB0byBpbml0aWFsaXplPC90dD48YnI+DQo8dHQ+Jmd0OyAmZ3Q7IHRo
ZSBOVFMgYXNzb2NpYXRpb24uPC90dD48YnI+DQo8dHQ+Jmd0OzwvdHQ+PGJyPg0KPHR0PiZndDsg
UmlnaHQsIHRvIHNlY29uZCB0aGF0LCB0aGVyZSBhcmUgbWlkZGxlYm94ZXMgdGhhdCBibG9jayBm
cmFnbWVudGVkIHBhY2tldHMuPC90dD48YnI+DQo8dHQ+Jmd0OyAmbmJzcDs8L3R0Pjwvc3Bhbj4g
PGJyPg0KPHR0PjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTAuMHB0Ij4mZ3Q7ICZndDsgJmd0OyBJ
ZiBwZW9wbGUgc2VlIGdyYXZlIHByb2JsZW1zIHdpdGggaXQsIHdlIHdvdWxkIHdlbGNvbWUgYW4N
Cjwvc3Bhbj48L3R0PjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTAuMHB0O2ZvbnQtZmFtaWx5OiZx
dW90O0NvdXJpZXIgTmV3JnF1b3Q7LCZxdW90O3NlcmlmJnF1b3Q7Ij48YnI+DQo8dHQ+Jmd0OyAm
Z3Q7ICZndDsgZWxhYm9yYXRpb24gYXMmbmJzcDsgdG8gd2h5IHRoaXMgaXMuPC90dD48YnI+DQo8
dHQ+Jmd0OyAmZ3Q7IDwvdHQ+PGJyPg0KPHR0PiZndDsgJmd0OyBJJ20gbm90IHN1cmUgYW5kIEkg
d2FzIGhvcGluZyBvdGhlcnMgd291bGQgY29tbWVudCBvbiB0aGF0LiBJdCBzZWVtczwvdHQ+PGJy
Pg0KPHR0PiZndDsgJmd0OyB0byBtZSBwcm9ibGVtcyB3aXRoIElQdjQgZnJhZ21lbnRhdGlvbiBh
cmUgcXVpdGUgY29tbW9uIGR1ZSB0bzwvdHQ+PGJyPg0KPHR0PiZndDsgJmd0OyBmaXJld2FsbHMg
ZHJvcHBpbmcgSUNNUCBwYWNrZXRzIG9yIElQIGZyYWdtZW50cywgYW5kIElQdjYgZG9lc24ndCBz
ZWVtPC90dD48YnI+DQo8dHQ+Jmd0OyAmZ3Q7IHRvIHJlY29tbWVuZCBzZW5kaW5nIHBhY2tldHMg
bGFyZ2VyIHRoYW4gMTUwMC48L3R0Pjwvc3Bhbj4gPGJyPg0KPHR0PjxzcGFuIHN0eWxlPSJmb250
LXNpemU6MTAuMHB0Ij4mZ3Q7IDwvc3Bhbj48L3R0PjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTAu
MHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NvdXJpZXIgTmV3JnF1b3Q7LCZxdW90O3NlcmlmJnF1b3Q7
Ij48YnI+DQo8dHQ+Jmd0OyBUbyBhZGQgdG8gdGhhdCwgZnJhZ21lbnRhdGlvbiBpcyBjb21tb25s
eSB1c2VkIGFzIGFuIGF0dGFjayB2ZWN0b3IuJm5ic3A7PC90dD48YnI+DQo8dHQ+Jmd0OyBJIHdv
dWxkIHN0cm9uZ2x5IGRpc2NvdXJhZ2UgdGhlIHVzZSBvZiBJUCBmcmFnbWVudGF0aW9uIGluIHdo
YXQgaXMgPC90dD48YnI+DQo8dHQ+Jmd0OyBzdXBwb3NlZCB0byBiZSBhIHNlY3VyaXR5IHByb3Rv
Y29sLiZuYnNwOyBQbGVhc2Ugc2VlIHRoZXNlIHJlZmVyZW5jZXMgZm9yPC90dD48YnI+DQo8dHQ+
Jmd0OyBhIHNtYWxsIHNhbXBsaW5nIG9mIGV4YW1wbGVzLjwvdHQ+PC9zcGFuPiA8YnI+DQo8YnI+
DQo8dHQ+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMC4wcHQiPklzIHRoZSBpc3N1ZSBzcGVjaWZp
YyB0byBJUCBmcmFnbWVudGF0aW9uIG9mIFVEUCBwYWNrZXRzPyBPciB0byBJUCBmcmFnbWVudGF0
aW9uIGluIGdlbmVyYWw/DQo8L3NwYW4+PC90dD48YnI+DQo8dHQ+PHNwYW4gc3R5bGU9ImZvbnQt
c2l6ZToxMC4wcHQiPihJJ20gYXNzdW1pbmcgaXQgZG9lcyBub3QgYXBwbHkgdG8gYWxsIHBvc3Np
YmxlIGtpbmRzIG9mIHBhY2tldCBmcmFnbWVudGF0aW9uLik8L3NwYW4+PC90dD4NCjxicj4NCjx0
dD48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEwLjBwdCI+SSdtIHNvcnJ5LCBJIGhhdmUgeWV0IHRv
IGdvIG92ZXIgdGhlIGxpbmtlZCBkb2N1bWVudHMuPC9zcGFuPjwvdHQ+DQo8bzpwPjwvbzpwPjwv
cD4NCjwvZGl2Pg0KPC9ibG9ja3F1b3RlPg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxv
OnA+Jm5ic3A7PC9vOnA+PC9wPg0KPC9kaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj5BbGwgZnJh
Z21lbnRhdGlvbi4gVGhlIGZvbGxvd2luZyBwYXBlciBhZmZlY3RzIGJvdGggdGNwIGFuZCB1ZHAu
ICZuYnNwOw0KPG86cD48L286cD48L3A+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86
cD4mbmJzcDs8L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48
YSBocmVmPSJodHRwczovL3d3dy51c2VuaXgub3JnL2xlZ2FjeS9ldmVudC93b290MTEvdGVjaC9m
aW5hbF9maWxlcy9HaWxhZC5wZGYiPmh0dHBzOi8vd3d3LnVzZW5peC5vcmcvbGVnYWN5L2V2ZW50
L3dvb3QxMS90ZWNoL2ZpbmFsX2ZpbGVzL0dpbGFkLnBkZjwvYT48bzpwPjwvbzpwPjwvcD4NCjwv
ZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0K
PC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+QWdhaW4uIE15IHBvaW50IGlzIHRo
YXQgd2Ugc2hvdWxkIG5vdCBiZSByZWx5aW5nIG9uIGZyYWdtZW50YXRpb24gaW4gTlRTLiBJdCBy
ZWd1bGFybHkgbGVhZHMgdG8gdW5leHBlY3RlZCBhdHRhY2tzLiAmbmJzcDs8bzpwPjwvbzpwPjwv
cD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+
PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+QWxzbyBxdW90aW5nIFJv
biBCb25pY2EgZnJvbSB0aGUgZmlyc3QgbGlua2VkIGNvbnZlcnNhdGlvbiBiZWxvdzo8bzpwPjwv
bzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7
PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+JnF1b3Q7cGxl
YXNlIGRvbid0IHdyaXRlIG5ldyBhcHBsaWNhdGlvbnMgdGhhdCBmcmFnbWVudCBwYWNrZXRzLiZx
dW90OzxvOnA+PC9vOnA+PC9wPg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+Jm5i
c3A7PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+U2hhcm9u
Jm5ic3A7PGJyPg0KPGJyPg0KPG86cD48L286cD48L3A+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05v
cm1hbCI+PHR0PjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTAuMHB0Ij4mbmJzcDs8L3NwYW4+PC90
dD48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEwLjBwdDtmb250LWZhbWlseTomcXVvdDtDb3VyaWVy
IE5ldyZxdW90OywmcXVvdDtzZXJpZiZxdW90OyI+PGJyPg0KPHR0PiZndDsgPC90dD48L3NwYW4+
PGEgaHJlZj0iaHR0cHM6Ly93d3cubmFub2cub3JnL3NpdGVzL2RlZmF1bHQvZmlsZXMvbW9uLmdl
bmVyYWwuZnJhZ21lbnRhdGlvbi5ib25pY2EucGRmIj48dHQ+PHNwYW4gc3R5bGU9ImZvbnQtc2l6
ZToxMC4wcHQiPmh0dHBzOi8vd3d3Lm5hbm9nLm9yZy9zaXRlcy9kZWZhdWx0L2ZpbGVzL21vbi5n
ZW5lcmFsLmZyYWdtZW50YXRpb24uYm9uaWNhLnBkZjwvc3Bhbj48L3R0PjwvYT48c3BhbiBzdHls
ZT0iZm9udC1zaXplOjEwLjBwdDtmb250LWZhbWlseTomcXVvdDtDb3VyaWVyIE5ldyZxdW90Oywm
cXVvdDtzZXJpZiZxdW90OyI+PGJyPg0KPHR0PiZndDsgPC90dD48YnI+DQo8dHQ+Jmd0OyA8L3R0
Pjwvc3Bhbj48YSBocmVmPSJodHRwOi8vd3d3LmhwbC5ocC5jb20vdGVjaHJlcG9ydHMvQ29tcGFx
LURFQy9XUkwtODctMy5wZGYiPjx0dD48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEwLjBwdCI+aHR0
cDovL3d3dy5ocGwuaHAuY29tL3RlY2hyZXBvcnRzL0NvbXBhcS1ERUMvV1JMLTg3LTMucGRmPC9z
cGFuPjwvdHQ+PC9hPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTAuMHB0O2ZvbnQtZmFtaWx5OiZx
dW90O0NvdXJpZXIgTmV3JnF1b3Q7LCZxdW90O3NlcmlmJnF1b3Q7Ij48YnI+DQo8dHQ+Jmd0OyA8
L3R0Pjxicj4NCjx0dD4mZ3Q7IDwvdHQ+PC9zcGFuPjxhIGhyZWY9Imh0dHA6Ly9hcnhpdi5vcmcv
YWJzLzEyMDUuNDAxMSI+PHR0PjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTAuMHB0Ij5odHRwOi8v
YXJ4aXYub3JnL2Ficy8xMjA1LjQwMTE8L3NwYW4+PC90dD48L2E+PHNwYW4gc3R5bGU9ImZvbnQt
c2l6ZToxMC4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q291cmllciBOZXcmcXVvdDssJnF1b3Q7c2Vy
aWYmcXVvdDsiPjxicj4NCjx0dD4mZ3Q7IDwvdHQ+PGJyPg0KPHR0PiZndDsgPC90dD48L3NwYW4+
PGEgaHJlZj0iaHR0cHM6Ly9tZWRpYS5ibGFja2hhdC5jb20vYmgtZXUtMTIvQXRsYXNpcy9iaC1l
dS0xMi1BdGxhc2lzLSI+PHR0PjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTAuMHB0Ij5odHRwczov
L21lZGlhLmJsYWNraGF0LmNvbS9iaC1ldS0xMi9BdGxhc2lzL2JoLWV1LTEyLUF0bGFzaXMtPC9z
cGFuPjwvdHQ+PC9hPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTAuMHB0O2ZvbnQtZmFtaWx5OiZx
dW90O0NvdXJpZXIgTmV3JnF1b3Q7LCZxdW90O3NlcmlmJnF1b3Q7Ij48YnI+DQo8dHQ+Jmd0OyBB
dHRhY2tpbmdfSVB2Ni1XUC5wZGY8L3R0Pjxicj4NCjx0dD4mZ3Q7IDwvdHQ+PGJyPg0KPHR0PiZn
dDsgPC90dD48L3NwYW4+PGEgaHJlZj0iaHR0cDovL3d3dy5pc3MubmV0L3NlY3VyaXR5X2NlbnRl
ci9yZWZlcmVuY2UvdnVsbi9UZWFyRHJvcC5odG0iPjx0dD48c3BhbiBzdHlsZT0iZm9udC1zaXpl
OjEwLjBwdCI+aHR0cDovL3d3dy5pc3MubmV0L3NlY3VyaXR5X2NlbnRlci9yZWZlcmVuY2UvdnVs
bi9UZWFyRHJvcC5odG08L3NwYW4+PC90dD48L2E+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMC4w
cHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q291cmllciBOZXcmcXVvdDssJnF1b3Q7c2VyaWYmcXVvdDsi
Pjxicj4NCjx0dD4mZ3Q7IDwvdHQ+PGJyPg0KPHR0PiZndDsgPC90dD48L3NwYW4+PGEgaHJlZj0i
aHR0cHM6Ly93d3cub2ZmZW5zaXZlLXNlY3VyaXR5LmNvbS93aWZ1L0ZyYWdtZW50YXRpb24tQXR0
YWNrLWluLVByYWN0aWNlLnBkZiI+PHR0PjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTAuMHB0Ij5o
dHRwczovL3d3dy5vZmZlbnNpdmUtc2VjdXJpdHkuY29tL3dpZnUvRnJhZ21lbnRhdGlvbi1BdHRh
Y2staW4tUHJhY3RpY2UucGRmPC9zcGFuPjwvdHQ+PC9hPjxzcGFuIHN0eWxlPSJmb250LXNpemU6
MTAuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NvdXJpZXIgTmV3JnF1b3Q7LCZxdW90O3NlcmlmJnF1
b3Q7Ij48YnI+DQo8dHQ+Jmd0OzwvdHQ+PC9zcGFuPiA8YnI+DQo8dHQ+PHNwYW4gc3R5bGU9ImZv
bnQtc2l6ZToxMC4wcHQiPiZndDsgRXZlbiBpZiB5b3UgZG9uJ3Qgc2VlIGEgU1BFQ0lGSUMgYXR0
YWNrIG9uIE5UUyBpbiB0aGVzZSBwYXBlcnMsIG15DQo8L3NwYW4+PC90dD48c3BhbiBzdHlsZT0i
Zm9udC1zaXplOjEwLjBwdDtmb250LWZhbWlseTomcXVvdDtDb3VyaWVyIE5ldyZxdW90OywmcXVv
dDtzZXJpZiZxdW90OyI+PGJyPg0KPHR0PiZndDsgcG9pbnQmbmJzcDsgaXMgdGhhdCB3ZSBjYW4g
dXN1YWxseSBmaW5kIGEgd2F5IHRvIGV4cGxvaXQgSVAgZnJhZ21lbnRhdGlvbjwvdHQ+PGJyPg0K
PHR0PiZndDsgaW4gdW5leHBlY3RlZCB3YXlzIHRvIGJyZWFrIHNlY3VyaXR5LiBUaGlzIGhhcyBo
YXBwZW5lZCBvdmVyIGFuZCA8L3R0Pjxicj4NCjx0dD4mZ3Q7IG92ZXIgaW4gdGhlIGxhc3QgdHdv
IGRlY2FkZXMgb24gbWFueSBkaWZmZXJlbnQgcHJvdG9jb2xzLiBJbiBmYWN0IDwvdHQ+PGJyPg0K
PHR0PiZndDsgdGhpcyBpcyBleGFjdGx5IHdoYXQgd2UgZGlkIGluIG91ciByZWNlbnQgTlRQIHBh
cGVyLCBTZWN0aW9uIFZJOjwvdHQ+PGJyPg0KPHR0PiZndDsgPC90dD48YnI+DQo8dHQ+Jmd0OyAu
PGEgaHJlZj0iaHR0cHM6Ly9lcHJpbnQuaWFjci5vcmcvMjAxNS8xMDIwLnBkZiI+aHR0cHM6Ly9l
cHJpbnQuaWFjci5vcmcvMjAxNS8xMDIwLnBkZjwvYT48L3R0Pjxicj4NCjx0dD4mZ3Q7PC90dD48
L3NwYW4+IDxicj4NCjx0dD48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEwLjBwdCI+Jmd0OyBJIHdv
dWxkIHN0cm9uZ2x5IG9iamVjdCB0byBoYXZpbmcgTlRTIHJlbHkgb24gSVAgZnJhZ21lbnRhdGlv
bi4mbmJzcDsmbmJzcDsNCjwvc3Bhbj48L3R0PjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTAuMHB0
O2ZvbnQtZmFtaWx5OiZxdW90O0NvdXJpZXIgTmV3JnF1b3Q7LCZxdW90O3NlcmlmJnF1b3Q7Ij48
YnI+DQo8dHQ+Jmd0OyBUaGlzIHdvdWxkIGJlIGEgaG9ycmlibGUgZGVzaWduIGRlY2lzaW9uLjwv
dHQ+PGJyPg0KPC9zcGFuPjxicj4NCjx0dD48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEwLjBwdCI+
Tm90ZWQuPC9zcGFuPjwvdHQ+PG86cD48L286cD48L3A+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9kaXY+
DQo8L2Rpdj4NCjwvZGl2Pg0KPC9ib2R5Pg0KPC9odG1sPg0K

--_000_8D2BF679AAC7C346848A489074F9F8BF7AAFC3EAsjsrvexchmbx2mi_--


From nobody Fri Apr  1 09:04:18 2016
Return-Path: <jared@puck.nether.net>
X-Original-To: tictoc@ietfa.amsl.com
Delivered-To: tictoc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CA48312D68D for <tictoc@ietfa.amsl.com>; Fri,  1 Apr 2016 09:04:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.212
X-Spam-Level: 
X-Spam-Status: No, score=-4.212 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WzIofQxe-q1N for <tictoc@ietfa.amsl.com>; Fri,  1 Apr 2016 09:04:14 -0700 (PDT)
Received: from puck.nether.net (puck.nether.net [IPv6:2001:418:3f4::5]) by ietfa.amsl.com (Postfix) with ESMTP id 1B78A12D70A for <tictoc@ietf.org>; Fri,  1 Apr 2016 09:03:49 -0700 (PDT)
Received: from host226.workshop.dns-oarc.net (unknown [200.61.11.226]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by puck.nether.net (Postfix) with ESMTPSA id 5F8855403E1; Fri,  1 Apr 2016 12:03:46 -0400 (EDT)
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
Content-Type: text/plain; charset=utf-8
From: Jared Mauch <jared@puck.nether.net>
In-Reply-To: <8D2BF679AAC7C346848A489074F9F8BF7AAFC3EA@sjsrvexchmbx2.microsemi.net>
Date: Fri, 1 Apr 2016 12:03:43 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <4CC4CA53-B8AF-40A9-9118-128DB06DD7FD@puck.nether.net>
References: <CAJHGrrSxvxRfe8VRRxh8Eh5tkCw-D0t7uuA_YqcLZif=ho45nA@mail.gmail.com> <20160329152654.GH20902@localhost> <OF07030A8A.8267E74D-ONC1257F87.002F2081-C1257F87.0041C9FA@ptb.de> <20160331125908.GG834@localhost> <CAJHGrrRB8t3gf6On8z-Q-z+TShPAES86fZVvHn+582mu0d1vgQ@mail.gmail.com> <OF35BF7FFD.C1AF1EA6-ONC1257F88.00430682-C1257F88.0043A34A@ptb.de> <BDF6E64B-B7BB-442A-9AA0-FCEBD5374462@gmail.com> <8D2BF679AAC7C346848A489074F9F8BF7AAFC3EA@sjsrvexchmbx2.microsemi.net>
To: Greg Dowd <Greg.Dowd@microsemi.com>
X-Mailer: Apple Mail (2.3124)
Archived-At: <http://mailarchive.ietf.org/arch/msg/tictoc/jAbf7zKQFtJC1716Hkgle6qsr4k>
Cc: NTP Working Group <ntpwg@lists.ntp.org>, "tictoc@ietf.org" <tictoc@ietf.org>, Sharon Goldberg <sharon.goldbe@gmail.com>
Subject: Re: [TICTOC] [ntpwg]  WGLC on NTS: Round trips for key exchange
X-BeenThere: tictoc@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Timing over IP Connection and Transfer of Clock BOF <tictoc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tictoc>, <mailto:tictoc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tictoc/>
List-Post: <mailto:tictoc@ietf.org>
List-Help: <mailto:tictoc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tictoc>, <mailto:tictoc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 01 Apr 2016 16:04:17 -0000

> On Apr 1, 2016, at 11:24 AM, Greg Dowd <Greg.Dowd@microsemi.com> =
wrote:
>=20
> Removing fragmentation by definition in an application protocol =
isn=E2=80=99t even possible in Ipv4 as routers can frag.  It seems a =
large challenge to manipulate any x509 stack and not expect =
fragmentation?  I know we all tend to think of 1514 (IP over 802.3 =
Ethernet) but MTU is not defined by the endpoints but the path.  I think =
a number of times there has been a discussion of running some session =
components over tcp which might help with some of the sequencing issues =
of splitting the transaction?  A backwards compatibility challenge is =
that, while ntp owns udp and tcp 123, I think many existing firewall =
configurations would drop tcp connections for 123.  I don=E2=80=99t know =
how many autokey deployments are actually running so perhaps it is not =
that big an issue.

There is a lot of data around packet sizes that are able to be passed on =
the wire without issue.  Anything over 1400 starts to be a risk of being =
dropped.  Consumers on PPPoE often see 1492.

My advice is to look at what has transpired in the DNS protocol around =
this.  If you haven=E2=80=99t had time to read up on the history there, =
it=E2=80=99s ripe with details of what works and does not.  There is a =
lot of probing that happens in the protocol to determine the packet =
sizes permissible with EDNS.

While fragmentation may occur and bits may pass, it is unlikely to be =
reliable.  As the protocol is designed, these operational considerations =
should understood.

- Jared=


From nobody Fri Apr  1 12:56:59 2016
Return-Path: <odonoghue@isoc.org>
X-Original-To: tictoc@ietfa.amsl.com
Delivered-To: tictoc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5DA6412D124 for <tictoc@ietfa.amsl.com>; Fri,  1 Apr 2016 12:56:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=isoc.onmicrosoft.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BAV2LxbdCJn1 for <tictoc@ietfa.amsl.com>; Fri,  1 Apr 2016 12:56:55 -0700 (PDT)
Received: from na01-bn1-obe.outbound.protection.outlook.com (mail-bn1on0621.outbound.protection.outlook.com [IPv6:2a01:111:f400:fc10::621]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 26AAB12D0BB for <tictoc@ietf.org>; Fri,  1 Apr 2016 12:56:55 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=isoc.onmicrosoft.com;  s=selector1-isoc-org; h=From:To:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=jH5ZyO0LbIBw/m0QCHrouRfomeAG8adqsMMBNkyqAII=; b=QSjteOsiSRlbMC1QdQYccZT7rVpD51KNcjsbuTAQPafJhPxCaSBQjI+Mq5h4dKbzK7iPyHLft6bmXey+vJt/shrC5ePNVmauBIDU4/5eN/F9EbAhNgI6ihp7tge4EiaVte7ap0Ip5cpujWe/df92SfLgtNPeDMymH2Q2n2dTkCk=
Received: from BY1PR0601MB1111.namprd06.prod.outlook.com (10.160.196.14) by BY1PR0601MB1111.namprd06.prod.outlook.com (10.160.196.14) with Microsoft SMTP Server (TLS) id 15.1.443.12; Fri, 1 Apr 2016 19:56:34 +0000
Received: from BY1PR0601MB1111.namprd06.prod.outlook.com ([10.160.196.14]) by BY1PR0601MB1111.namprd06.prod.outlook.com ([10.160.196.14]) with mapi id 15.01.0443.017; Fri, 1 Apr 2016 19:56:34 +0000
From: Karen O'Donoghue <odonoghue@isoc.org>
To: "ntpwg@lists.ntp.org" <ntpwg@lists.ntp.org>, "tictoc@ietf.org" <tictoc@ietf.org>
Thread-Topic: Remote Participation for IETF 95: Meetecho Details
Thread-Index: AQHRisHwUm+aYbHzmEGVugXIwIi9Fg==
Date: Fri, 1 Apr 2016 19:56:34 +0000
Message-ID: <042BAC14-28B3-4E7C-8EB3-9DBB26322CD0@isoc.org>
References: <20160330202243.4795.63685.idtracker@ietfa.amsl.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
authentication-results: lists.ntp.org; dkim=none (message not signed) header.d=none;lists.ntp.org; dmarc=none action=none header.from=isoc.org;
x-ms-exchange-messagesentrepresentingtype: 1
x-originating-ip: [31.133.140.249]
x-ms-office365-filtering-correlation-id: c8384ad9-0851-411d-0ed1-08d35a67baa2
x-microsoft-exchange-diagnostics: 1; BY1PR0601MB1111; 5:qn9wz6W7w2zvhs8ZZez/zDY2mB19mbZ6Aj7e7hX2Zhi1tq43kc3DlXAbJTbQC7TNI4CjwCNcU+sPToHJeMcR/gPkbLlT6aCubokerH4X1DfaIpO2iNUSLQoikYqweB2hFNr3t1aSIYsgbuRqT/9SYg==; 24:dMROD+HIg4/4oTiZFKN0aXBOEMztTe6jV9YvnTkk/S4TWAc/kAE1ykjVZkfI/WWNxz53A99aSh3BvJus50ifYjBY+O589M3GwUGfGk4ZQ/E=
x-microsoft-antispam: UriScan:;BCL:0;PCL:0;RULEID:;SRVR:BY1PR0601MB1111;
x-microsoft-antispam-prvs: <BY1PR0601MB11112183B1A3DF88565ECC57C29A0@BY1PR0601MB1111.namprd06.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:;
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(601004)(2401047)(5005006)(8121501046)(10201501046)(3002001); SRVR:BY1PR0601MB1111; BCL:0; PCL:0; RULEID:; SRVR:BY1PR0601MB1111; 
x-forefront-prvs: 0899B47777
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(2473001)(377454003)(3846002)(5002640100001)(10400500002)(86362001)(54356999)(50986999)(76176999)(2501003)(36756003)(2906002)(82746002)(107886002)(19580405001)(189998001)(5004730100002)(92566002)(122556002)(83716003)(77096005)(19300405004)(81166005)(5001770100001)(586003)(16799955002)(87936001)(15395725005)(1096002)(6116002)(3280700002)(19617315012)(106116001)(99286002)(1220700001)(5008740100001)(2900100001)(19273905006)(19580395003)(3660700001)(102836003)(66066001)(11100500001)(15975445007)(16236675004)(104396002); DIR:OUT; SFP:1101; SCL:1; SRVR:BY1PR0601MB1111; H:BY1PR0601MB1111.namprd06.prod.outlook.com; FPR:; SPF:None; MLV:sfv; LANG:en; 
spamdiagnosticoutput: 1:23
spamdiagnosticmetadata: NSPM
Content-Type: multipart/alternative; boundary="_000_042BAC1428B34E7C8EB39DBB26322CD0isocorg_"
MIME-Version: 1.0
X-OriginatorOrg: isoc.org
X-MS-Exchange-CrossTenant-originalarrivaltime: 01 Apr 2016 19:56:34.5873 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 89f84dfb-7285-4810-bc4d-8b9b5794554f
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BY1PR0601MB1111
Archived-At: <http://mailarchive.ietf.org/arch/msg/tictoc/WLlW-_NEuOTG2S9LrD_ljCZm2q0>
Subject: [TICTOC] Fwd: Remote Participation for IETF 95: Meetecho Details
X-BeenThere: tictoc@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Timing over IP Connection and Transfer of Clock BOF <tictoc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tictoc>, <mailto:tictoc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tictoc/>
List-Post: <mailto:tictoc@ietf.org>
List-Help: <mailto:tictoc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tictoc>, <mailto:tictoc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 01 Apr 2016 19:56:58 -0000

--_000_042BAC1428B34E7C8EB39DBB26322CD0isocorg_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Folks,

As a reminder, the Joint NTP/TICTOC meeting here at IETF 95 is
Tuesday, 5 April, 1400-1600 ART (1700-1900 UTC).

As part of the effort to improve remote participation support, there has be=
en a change to the remote participation process for IETF 95. You are asked =
to register for the meeting. There is no cost for this registration.

We will be using meetecho to support this meeting. There are also links to =
a self test that you should perform in advance of the session itself.

Thanks!
Karen

Begin forwarded message:

From: IETF Secretariat <ietf-secretariat@ietf.org<mailto:ietf-secretariat@i=
etf.org>>
Subject: Remote Participation for IETF 95: Meetecho Details
Date: March 30, 2016 at 5:22:43 PM GMT-3
To: "IETF Announcement List" <ietf-announce@ietf.org<mailto:ietf-announce@i=
etf.org>>
Cc: wgchairs@ietf.org<mailto:wgchairs@ietf.org>, recentattendees@ietf.org<m=
ailto:recentattendees@ietf.org>, 95all@ietf.org<mailto:95all@ietf.org>
Reply-To: ietf@ietf.org<mailto:ietf@ietf.org>

You may use Meetecho to participate in or just observe any session being he=
ld in Buenos Aires. Here are the requirements and details.

1. Individuals are required to register for the meeting to observe or parti=
cipate via Meetecho.
- Individuals are required to enter registration I.D and name when logging =
into a session via Meetecho
- The name must match that used to register for the meeting
- Please register even if you are participating as part of remote hub
- There is no cost to register as a remote attendee. Register here:http://i=
etf.org/meeting/register.html<http://ietf.org/meeting/register.html>.

2. Participation includes the ability to transmit audio and video via the M=
eetecho virtual queue.
- The virtual queue permits remote attendees to share audio and video if th=
ey choose, see here for more information: https://ietf95.conf.meetecho.com/=
index.php/UMPIRE_Project
- Anyone who thinks they may want to participate by transmitting audio / vi=
deo should perform the Meetecho self-test prior to the start of the session=
: http://ietf95.conf.meetecho.com/index.php/Self_Test

3. WG Chairs will control the virtual queue, unmuting and muting of remote =
participants

4. The agenda for the WG sessions, as well as more detail on how to use Mee=
techo to participate, can be found here: https://ietf95.conf.meetecho.com/i=
ndex.php/.



--_000_042BAC1428B34E7C8EB39DBB26322CD0isocorg_
Content-Type: text/html; charset="us-ascii"
Content-ID: <03240BFEA9F8B040A9E657826592A574@namprd06.prod.outlook.com>
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
</head>
<body style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-lin=
e-break: after-white-space;" class=3D"">
Folks,
<div class=3D""><br class=3D"">
</div>
<div class=3D"">As a reminder, the Joint NTP/TICTOC meeting here at IETF 95=
 is&nbsp;</div>
<div class=3D"">Tuesday, 5 April, 1400-1600 ART (1700-1900 UTC).&nbsp;</div=
>
<div class=3D""><br class=3D"">
</div>
<div class=3D"">As part of the effort to improve remote participation suppo=
rt, there has been a change to the remote participation process for IETF 95=
. You are asked to register for the meeting. There is no cost for this regi=
stration.&nbsp;</div>
<div class=3D""><br class=3D"">
</div>
<div class=3D"">We will be using meetecho to support this meeting. There ar=
e also links to a self test that you should perform in advance of the sessi=
on itself.&nbsp;</div>
<div class=3D""><br class=3D"">
</div>
<div class=3D"">Thanks!</div>
<div class=3D"">Karen</div>
<div class=3D"">
<div><br class=3D"">
<blockquote type=3D"cite" class=3D"">
<div class=3D"">Begin forwarded message:</div>
<br class=3D"Apple-interchange-newline">
<div style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margi=
n-left: 0px;" class=3D"">
<span style=3D"font-family: -webkit-system-font, Helvetica Neue, Helvetica,=
 sans-serif; color:rgba(0, 0, 0, 1.0);" class=3D""><b class=3D"">From:
</b></span><span style=3D"font-family: -webkit-system-font, Helvetica Neue,=
 Helvetica, sans-serif;" class=3D"">IETF Secretariat &lt;<a href=3D"mailto:=
ietf-secretariat@ietf.org" class=3D"">ietf-secretariat@ietf.org</a>&gt;<br =
class=3D"">
</span></div>
<div style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margi=
n-left: 0px;" class=3D"">
<span style=3D"font-family: -webkit-system-font, Helvetica Neue, Helvetica,=
 sans-serif; color:rgba(0, 0, 0, 1.0);" class=3D""><b class=3D"">Subject:
</b></span><span style=3D"font-family: -webkit-system-font, Helvetica Neue,=
 Helvetica, sans-serif;" class=3D""><b class=3D"">Remote Participation for =
IETF 95: Meetecho Details</b><br class=3D"">
</span></div>
<div style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margi=
n-left: 0px;" class=3D"">
<span style=3D"font-family: -webkit-system-font, Helvetica Neue, Helvetica,=
 sans-serif; color:rgba(0, 0, 0, 1.0);" class=3D""><b class=3D"">Date:
</b></span><span style=3D"font-family: -webkit-system-font, Helvetica Neue,=
 Helvetica, sans-serif;" class=3D"">March 30, 2016 at 5:22:43 PM GMT-3<br c=
lass=3D"">
</span></div>
<div style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margi=
n-left: 0px;" class=3D"">
<span style=3D"font-family: -webkit-system-font, Helvetica Neue, Helvetica,=
 sans-serif; color:rgba(0, 0, 0, 1.0);" class=3D""><b class=3D"">To:
</b></span><span style=3D"font-family: -webkit-system-font, Helvetica Neue,=
 Helvetica, sans-serif;" class=3D"">&quot;IETF Announcement List&quot; &lt;=
<a href=3D"mailto:ietf-announce@ietf.org" class=3D"">ietf-announce@ietf.org=
</a>&gt;<br class=3D"">
</span></div>
<div style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margi=
n-left: 0px;" class=3D"">
<span style=3D"font-family: -webkit-system-font, Helvetica Neue, Helvetica,=
 sans-serif; color:rgba(0, 0, 0, 1.0);" class=3D""><b class=3D"">Cc:
</b></span><span style=3D"font-family: -webkit-system-font, Helvetica Neue,=
 Helvetica, sans-serif;" class=3D""><a href=3D"mailto:wgchairs@ietf.org" cl=
ass=3D"">wgchairs@ietf.org</a>,
<a href=3D"mailto:recentattendees@ietf.org" class=3D"">recentattendees@ietf=
.org</a>, <a href=3D"mailto:95all@ietf.org" class=3D"">
95all@ietf.org</a><br class=3D"">
</span></div>
<div style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margi=
n-left: 0px;" class=3D"">
<span style=3D"font-family: -webkit-system-font, Helvetica Neue, Helvetica,=
 sans-serif; color:rgba(0, 0, 0, 1.0);" class=3D""><b class=3D"">Reply-To:
</b></span><span style=3D"font-family: -webkit-system-font, Helvetica Neue,=
 Helvetica, sans-serif;" class=3D""><a href=3D"mailto:ietf@ietf.org" class=
=3D"">ietf@ietf.org</a><br class=3D"">
</span></div>
<br class=3D"">
<div class=3D"">
<div class=3D"">You may use Meetecho to participate in or just observe any =
session being held in Buenos Aires. Here are the requirements and details.
<br class=3D"">
<br class=3D"">
1. Individuals are required to register for the meeting to observe or parti=
cipate via Meetecho.<br class=3D"">
- Individuals are required to enter registration I.D and name when logging =
into a session via Meetecho<br class=3D"">
- The name must match that used to register for the meeting<br class=3D"">
- Please register even if you are participating as part of remote hub<br cl=
ass=3D"">
- There is no cost to register as a remote attendee. Register here:http://<=
a href=3D"http://ietf.org/meeting/register.html" class=3D"">ietf.org/meetin=
g/register.html</a>.
<br class=3D"">
<br class=3D"">
2. Participation includes the ability to transmit audio and video via the M=
eetecho virtual queue.<br class=3D"">
- The virtual queue permits remote attendees to share audio and video if th=
ey choose, see here for more information:
<a href=3D"https://ietf95.conf.meetecho.com/index.php/UMPIRE_Project" class=
=3D"">https://ietf95.conf.meetecho.com/index.php/UMPIRE_Project</a><br clas=
s=3D"">
- Anyone who thinks they may want to participate by transmitting audio / vi=
deo should perform the Meetecho self-test prior to the start of the session=
:
<a href=3D"http://ietf95.conf.meetecho.com/index.php/Self_Test" class=3D"">=
http://ietf95.conf.meetecho.com/index.php/Self_Test</a><br class=3D"">
<br class=3D"">
3. WG Chairs will control the virtual queue, unmuting and muting of remote =
participants<br class=3D"">
<br class=3D"">
4. The agenda for the WG sessions, as well as more detail on how to use Mee=
techo to participate, can be found here:
<a href=3D"https://ietf95.conf.meetecho.com/index.php/" class=3D"">https://=
ietf95.conf.meetecho.com/index.php/</a>.<br class=3D"">
<br class=3D"">
</div>
</div>
</blockquote>
</div>
<br class=3D"">
</div>
</body>
</html>

--_000_042BAC1428B34E7C8EB39DBB26322CD0isocorg_--


From nobody Sat Apr  2 05:35:02 2016
Return-Path: <odonoghue@isoc.org>
X-Original-To: tictoc@ietfa.amsl.com
Delivered-To: tictoc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8625912D0DD for <tictoc@ietfa.amsl.com>; Sat,  2 Apr 2016 05:35:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=isoc.onmicrosoft.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DU8UGeSqbLa0 for <tictoc@ietfa.amsl.com>; Sat,  2 Apr 2016 05:34:58 -0700 (PDT)
Received: from na01-bn1-obe.outbound.protection.outlook.com (mail-bn1on0680.outbound.protection.outlook.com [IPv6:2a01:111:f400:fc10::680]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CC7B712D52A for <tictoc@ietf.org>; Sat,  2 Apr 2016 05:34:57 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=isoc.onmicrosoft.com;  s=selector1-isoc-org; h=From:To:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=rglv/yX4hVFpKCOzTultoWIIVhYH8NfmnjkONtTqGQk=; b=T8f5fRwjUCyiQlouplXWSXYYYyqrJ/qFRKwkv6cstX96B9w7tyQdYafQ13q4Ife7AacNRldT5TK37WBAZEJ5ob/VmyTmz8S1/Nga34qeMQVyaGBQRzTguMw0eL8v+i4ttLHQetkx9Syn5GGGzK8kKXi5nhNcnRA2vLojPVVEW34=
Received: from BY1PR0601MB1111.namprd06.prod.outlook.com (10.160.196.14) by BY1PR0601MB1112.namprd06.prod.outlook.com (10.160.196.140) with Microsoft SMTP Server (TLS) id 15.1.443.12; Sat, 2 Apr 2016 12:34:39 +0000
Received: from BY1PR0601MB1111.namprd06.prod.outlook.com ([10.160.196.14]) by BY1PR0601MB1111.namprd06.prod.outlook.com ([10.160.196.14]) with mapi id 15.01.0443.017; Sat, 2 Apr 2016 12:34:40 +0000
From: Karen O'Donoghue <odonoghue@isoc.org>
To: "ntpwg@lists.ntp.org" <ntpwg@lists.ntp.org>, "tictoc@ietf.org" <tictoc@ietf.org>
Thread-Topic: Remote Participation for IETF 95: Meetecho Details
Thread-Index: AQHRisHwUm+aYbHzmEGVugXIwIi9Fp92ooWA
Date: Sat, 2 Apr 2016 12:34:39 +0000
Message-ID: <6DD14B3B-4632-4913-900A-E5167254DA05@isoc.org>
References: <20160330202243.4795.63685.idtracker@ietfa.amsl.com> <042BAC14-28B3-4E7C-8EB3-9DBB26322CD0@isoc.org>
In-Reply-To: <042BAC14-28B3-4E7C-8EB3-9DBB26322CD0@isoc.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
authentication-results: lists.ntp.org; dkim=none (message not signed) header.d=none;lists.ntp.org; dmarc=none action=none header.from=isoc.org;
x-ms-exchange-messagesentrepresentingtype: 1
x-originating-ip: [31.130.224.165]
x-ms-office365-filtering-correlation-id: 1a1e634c-a26f-49b4-2ecb-08d35af3290a
x-microsoft-exchange-diagnostics: 1; BY1PR0601MB1112; 5:PigI2bqo1wMAaDfvmlMtdr3TgHnNQvW5Mx8jgXhRhqNWq4oFm0/6P2M4W1x1SWx4YLLNRm2UD+j+4u1pDjsN40ygE6cAuf7nUbw8sbcLMR/m5RWv7DPDYz3FpUqn9jRbXrE/5NWxN9Hp19yy1ct09A==; 24:mJ3Qf/uqkou62Y/4hDteXL04uq17QrqziJWafGf24/N4xmIco5qpewGBtqANI5hfd9BrKeAVnf8TnmPt9uR4da8xEv/fOuMXbvgOGHX55wg=
x-microsoft-antispam: UriScan:;BCL:0;PCL:0;RULEID:;SRVR:BY1PR0601MB1112;
x-microsoft-antispam-prvs: <BY1PR0601MB1112062E0B8F14BFD73A10CBC29B0@BY1PR0601MB1112.namprd06.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:;
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(601004)(2401047)(8121501046)(5005006)(10201501046)(3002001); SRVR:BY1PR0601MB1112; BCL:0; PCL:0; RULEID:; SRVR:BY1PR0601MB1112; 
x-forefront-prvs: 09007040D4
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(164054003)(24454002)(377454003)(54356999)(122556002)(82746002)(76176999)(83716003)(1220700001)(19580405001)(81166005)(1096002)(19580395003)(50986999)(19617315012)(2501003)(586003)(3846002)(86362001)(92566002)(2906002)(10400500002)(87936001)(66066001)(5002640100001)(6116002)(102836003)(107886002)(5004730100002)(3280700002)(189998001)(5001770100001)(15395725005)(3660700001)(16236675004)(33656002)(2950100001)(36756003)(2900100001)(16799955002)(106116001)(99286002)(5008740100001)(19273905006)(15975445007)(19300405004)(77096005)(104396002); DIR:OUT; SFP:1101; SCL:1; SRVR:BY1PR0601MB1112; H:BY1PR0601MB1111.namprd06.prod.outlook.com; FPR:; SPF:None; MLV:sfv; LANG:en; 
spamdiagnosticoutput: 1:23
spamdiagnosticmetadata: NSPM
Content-Type: multipart/alternative; boundary="_000_6DD14B3B46324913900AE5167254DA05isocorg_"
MIME-Version: 1.0
X-OriginatorOrg: isoc.org
X-MS-Exchange-CrossTenant-originalarrivaltime: 02 Apr 2016 12:34:39.8645 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 89f84dfb-7285-4810-bc4d-8b9b5794554f
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BY1PR0601MB1112
Archived-At: <http://mailarchive.ietf.org/arch/msg/tictoc/DtCvxY1ZhuL9t_USV6xF86F4FGI>
Subject: Re: [TICTOC] Remote Participation for IETF 95: Meetecho Details
X-BeenThere: tictoc@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Timing over IP Connection and Transfer of Clock BOF <tictoc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tictoc>, <mailto:tictoc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tictoc/>
List-Post: <mailto:tictoc@ietf.org>
List-Help: <mailto:tictoc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tictoc>, <mailto:tictoc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 02 Apr 2016 12:35:01 -0000

--_000_6DD14B3B46324913900AE5167254DA05isocorg_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Folks,

As sometimes happens when processes change, there has been a glitch with re=
mote registration. Please follow the link provided by the secretariat below=
 to register for remote participation.

Karen,
We realized last night that when registration closed it also automatically
closed remote participation registration as well. We had our IT folk reopen
remote participation registration. They can access remote participation fro=
m
the link on this page.

http://ietf.org/meeting/95/remote-participation.html

Thanks,
Karen

On Apr 1, 2016, at 4:56 PM, Karen O'Donoghue <odonoghue@isoc.org<mailto:odo=
noghue@isoc.org>> wrote:

Folks,

As a reminder, the Joint NTP/TICTOC meeting here at IETF 95 is
Tuesday, 5 April, 1400-1600 ART (1700-1900 UTC).

As part of the effort to improve remote participation support, there has be=
en a change to the remote participation process for IETF 95. You are asked =
to register for the meeting. There is no cost for this registration.

We will be using meetecho to support this meeting. There are also links to =
a self test that you should perform in advance of the session itself.

Thanks!
Karen

Begin forwarded message:

From: IETF Secretariat <ietf-secretariat@ietf.org<mailto:ietf-secretariat@i=
etf.org>>
Subject: Remote Participation for IETF 95: Meetecho Details
Date: March 30, 2016 at 5:22:43 PM GMT-3
To: "IETF Announcement List" <ietf-announce@ietf.org<mailto:ietf-announce@i=
etf.org>>
Cc: wgchairs@ietf.org<mailto:wgchairs@ietf.org>, recentattendees@ietf.org<m=
ailto:recentattendees@ietf.org>, 95all@ietf.org<mailto:95all@ietf.org>
Reply-To: ietf@ietf.org<mailto:ietf@ietf.org>

You may use Meetecho to participate in or just observe any session being he=
ld in Buenos Aires. Here are the requirements and details.

1. Individuals are required to register for the meeting to observe or parti=
cipate via Meetecho.
- Individuals are required to enter registration I.D and name when logging =
into a session via Meetecho
- The name must match that used to register for the meeting
- Please register even if you are participating as part of remote hub
- There is no cost to register as a remote attendee. Register here:http://i=
etf.org/meeting/register.html<http://ietf.org/meeting/register.html>.

2. Participation includes the ability to transmit audio and video via the M=
eetecho virtual queue.
- The virtual queue permits remote attendees to share audio and video if th=
ey choose, see here for more information: https://ietf95.conf.meetecho.com/=
index.php/UMPIRE_Project
- Anyone who thinks they may want to participate by transmitting audio / vi=
deo should perform the Meetecho self-test prior to the start of the session=
: http://ietf95.conf.meetecho.com/index.php/Self_Test

3. WG Chairs will control the virtual queue, unmuting and muting of remote =
participants

4. The agenda for the WG sessions, as well as more detail on how to use Mee=
techo to participate, can be found here: https://ietf95.conf.meetecho.com/i=
ndex.php/.




--_000_6DD14B3B46324913900AE5167254DA05isocorg_
Content-Type: text/html; charset="us-ascii"
Content-ID: <E3575611A84E4F43A7CE11FB3BFB7AC9@namprd06.prod.outlook.com>
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
</head>
<body style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-lin=
e-break: after-white-space;" class=3D"">
Folks,
<div class=3D""><br class=3D"">
</div>
<div class=3D"">As sometimes happens when processes change, there has been =
a glitch with remote registration. Please follow the link provided by the s=
ecretariat below to register for remote participation.&nbsp;</div>
<div class=3D""><br class=3D"">
</div>
<div class=3D"">
<blockquote type=3D"cite" class=3D"">Karen,</blockquote>
<blockquote type=3D"cite" class=3D"">We realized last night that when regis=
tration closed it also automatically<br class=3D"">
closed remote participation registration as well. We had our IT folk reopen=
<br class=3D"">
remote participation registration. They can access remote participation fro=
m<br class=3D"">
the link on this page.<br class=3D"">
<br class=3D"">
<a href=3D"http://ietf.org/meeting/95/remote-participation.html" class=3D""=
>http://ietf.org/meeting/95/remote-participation.html</a><br class=3D"">
</blockquote>
<div class=3D""><br class=3D"">
</div>
Thanks,</div>
<div class=3D"">Karen</div>
<div class=3D""><br class=3D"">
<div>
<blockquote type=3D"cite" class=3D"">
<div class=3D"">On Apr 1, 2016, at 4:56 PM, Karen O'Donoghue &lt;<a href=3D=
"mailto:odonoghue@isoc.org" class=3D"">odonoghue@isoc.org</a>&gt; wrote:</d=
iv>
<br class=3D"Apple-interchange-newline">
<div class=3D"">
<div style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line=
-break: after-white-space;" class=3D"">
Folks,
<div class=3D""><br class=3D"">
</div>
<div class=3D"">As a reminder, the Joint NTP/TICTOC meeting here at IETF 95=
 is&nbsp;</div>
<div class=3D"">Tuesday, 5 April, 1400-1600 ART (1700-1900 UTC).&nbsp;</div=
>
<div class=3D""><br class=3D"">
</div>
<div class=3D"">As part of the effort to improve remote participation suppo=
rt, there has been a change to the remote participation process for IETF 95=
. You are asked to register for the meeting. There is no cost for this regi=
stration.&nbsp;</div>
<div class=3D""><br class=3D"">
</div>
<div class=3D"">We will be using meetecho to support this meeting. There ar=
e also links to a self test that you should perform in advance of the sessi=
on itself.&nbsp;</div>
<div class=3D""><br class=3D"">
</div>
<div class=3D"">Thanks!</div>
<div class=3D"">Karen</div>
<div class=3D"">
<div class=3D""><br class=3D"">
<blockquote type=3D"cite" class=3D"">
<div class=3D"">Begin forwarded message:</div>
<br class=3D"Apple-interchange-newline">
<div style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margi=
n-left: 0px;" class=3D"">
<span style=3D"font-family: -webkit-system-font, 'Helvetica Neue', Helvetic=
a, sans-serif;" class=3D""><b class=3D"">From:
</b></span><span style=3D"font-family: -webkit-system-font, Helvetica Neue,=
 Helvetica, sans-serif;" class=3D"">IETF Secretariat &lt;<a href=3D"mailto:=
ietf-secretariat@ietf.org" class=3D"">ietf-secretariat@ietf.org</a>&gt;<br =
class=3D"">
</span></div>
<div style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margi=
n-left: 0px;" class=3D"">
<span style=3D"font-family: -webkit-system-font, 'Helvetica Neue', Helvetic=
a, sans-serif;" class=3D""><b class=3D"">Subject:
</b></span><span style=3D"font-family: -webkit-system-font, Helvetica Neue,=
 Helvetica, sans-serif;" class=3D""><b class=3D"">Remote Participation for =
IETF 95: Meetecho Details</b><br class=3D"">
</span></div>
<div style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margi=
n-left: 0px;" class=3D"">
<span style=3D"font-family: -webkit-system-font, 'Helvetica Neue', Helvetic=
a, sans-serif;" class=3D""><b class=3D"">Date:
</b></span><span style=3D"font-family: -webkit-system-font, Helvetica Neue,=
 Helvetica, sans-serif;" class=3D"">March 30, 2016 at 5:22:43 PM GMT-3<br c=
lass=3D"">
</span></div>
<div style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margi=
n-left: 0px;" class=3D"">
<span style=3D"font-family: -webkit-system-font, 'Helvetica Neue', Helvetic=
a, sans-serif;" class=3D""><b class=3D"">To:
</b></span><span style=3D"font-family: -webkit-system-font, Helvetica Neue,=
 Helvetica, sans-serif;" class=3D"">&quot;IETF Announcement List&quot; &lt;=
<a href=3D"mailto:ietf-announce@ietf.org" class=3D"">ietf-announce@ietf.org=
</a>&gt;<br class=3D"">
</span></div>
<div style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margi=
n-left: 0px;" class=3D"">
<span style=3D"font-family: -webkit-system-font, 'Helvetica Neue', Helvetic=
a, sans-serif;" class=3D""><b class=3D"">Cc:
</b></span><span style=3D"font-family: -webkit-system-font, Helvetica Neue,=
 Helvetica, sans-serif;" class=3D""><a href=3D"mailto:wgchairs@ietf.org" cl=
ass=3D"">wgchairs@ietf.org</a>,
<a href=3D"mailto:recentattendees@ietf.org" class=3D"">recentattendees@ietf=
.org</a>, <a href=3D"mailto:95all@ietf.org" class=3D"">
95all@ietf.org</a><br class=3D"">
</span></div>
<div style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margi=
n-left: 0px;" class=3D"">
<span style=3D"font-family: -webkit-system-font, 'Helvetica Neue', Helvetic=
a, sans-serif;" class=3D""><b class=3D"">Reply-To:
</b></span><span style=3D"font-family: -webkit-system-font, Helvetica Neue,=
 Helvetica, sans-serif;" class=3D""><a href=3D"mailto:ietf@ietf.org" class=
=3D"">ietf@ietf.org</a><br class=3D"">
</span></div>
<br class=3D"">
<div class=3D"">
<div class=3D"">You may use Meetecho to participate in or just observe any =
session being held in Buenos Aires. Here are the requirements and details.
<br class=3D"">
<br class=3D"">
1. Individuals are required to register for the meeting to observe or parti=
cipate via Meetecho.<br class=3D"">
- Individuals are required to enter registration I.D and name when logging =
into a session via Meetecho<br class=3D"">
- The name must match that used to register for the meeting<br class=3D"">
- Please register even if you are participating as part of remote hub<br cl=
ass=3D"">
- There is no cost to register as a remote attendee. Register here:http://<=
a href=3D"http://ietf.org/meeting/register.html" class=3D"">ietf.org/meetin=
g/register.html</a>.
<br class=3D"">
<br class=3D"">
2. Participation includes the ability to transmit audio and video via the M=
eetecho virtual queue.<br class=3D"">
- The virtual queue permits remote attendees to share audio and video if th=
ey choose, see here for more information:
<a href=3D"https://ietf95.conf.meetecho.com/index.php/UMPIRE_Project" class=
=3D"">https://ietf95.conf.meetecho.com/index.php/UMPIRE_Project</a><br clas=
s=3D"">
- Anyone who thinks they may want to participate by transmitting audio / vi=
deo should perform the Meetecho self-test prior to the start of the session=
:
<a href=3D"http://ietf95.conf.meetecho.com/index.php/Self_Test" class=3D"">=
http://ietf95.conf.meetecho.com/index.php/Self_Test</a><br class=3D"">
<br class=3D"">
3. WG Chairs will control the virtual queue, unmuting and muting of remote =
participants<br class=3D"">
<br class=3D"">
4. The agenda for the WG sessions, as well as more detail on how to use Mee=
techo to participate, can be found here:
<a href=3D"https://ietf95.conf.meetecho.com/index.php/" class=3D"">https://=
ietf95.conf.meetecho.com/index.php/</a>.<br class=3D"">
<br class=3D"">
</div>
</div>
</blockquote>
</div>
<br class=3D"">
</div>
</div>
</div>
</blockquote>
</div>
<br class=3D"">
</div>
</body>
</html>

--_000_6DD14B3B46324913900AE5167254DA05isocorg_--


From nobody Sat Apr  2 11:39:13 2016
Return-Path: <sharon.goldbe@gmail.com>
X-Original-To: tictoc@ietfa.amsl.com
Delivered-To: tictoc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BF93712D5BF for <tictoc@ietfa.amsl.com>; Fri,  1 Apr 2016 06:00:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level: 
X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YObeCvKfqApr for <tictoc@ietfa.amsl.com>; Fri,  1 Apr 2016 06:00:35 -0700 (PDT)
Received: from mail-yw0-x22a.google.com (mail-yw0-x22a.google.com [IPv6:2607:f8b0:4002:c05::22a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8EAB712D5D0 for <tictoc@ietf.org>; Fri,  1 Apr 2016 06:00:34 -0700 (PDT)
Received: by mail-yw0-x22a.google.com with SMTP id d68so19606299ywe.1 for <tictoc@ietf.org>; Fri, 01 Apr 2016 06:00:34 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=PXgEsz3juLMQv8fYbcFRvhobx5hwvKsm0qdQDCHelko=; b=wY1iu0ZQTpQbabLKXMibEKA+C0AzZV9D7BPl0l+w6dctkYcguOgd8AcXYKbx5kmvys QqI4FkmIOzcFwuVuLoS/KxMMj6Sl/c7aLAnJsDdgI4Lzqzi2RASrBQolvaKSXEZkA6HR EqbDRCeRmpsVrsQ2UWZdVfBo1tjjHODIxd3X4Saz+WTA5nqopGB92qspC4pPk9LRzocb P6ufxeMfXd7uoG/1gH22zhjnz9W22yMGOwN1WmNmGqhEQseflQoxYWgAly369bYj+nXj 7WEfvw8wJlxRpd/RgT/Opf555qTNAOtInuiwSCJyXUHzTosHzsqaKAQuac++5fQIKMhI a7Yw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=PXgEsz3juLMQv8fYbcFRvhobx5hwvKsm0qdQDCHelko=; b=Jc3FdN5i1T7wh5iuzOOvVlV7fZZhNAFvzDxIoImRgQ7XUkuBNfjUfCsjrCeyPBQEjM Jjx8NSiMiI1OGy+Mxl+FfWHYN1duMLqHWRb64UDZMx3abmgMf+qW6V+8tYWzBOEEbToj eDeG27LlqYj02nMm53Cn767C7IF6tM7sV13cq9pI7QU0TuNsqi/NfraH0T/3ef5diKdw APvVJ13JNGWz1lqc9jDR3bVgoSmBZIa+wfTJIgxRQoHrzfCgqH9tIuSfgRQkd4jIjQaR vO1Y9Y/mY9KVErPmWUhtqPY7wJI3SNIq/NqJPf2357QM+8ol8AKlT1PMncPoqrpbZ97H li5w==
X-Gm-Message-State: AD7BkJL5UFttld5CT8Tn8K/tNkDmbE2Dbmhqy+VeqJhGgGGDNpEtOiFPBFZYhmpVljRPbg==
X-Received: by 10.129.153.193 with SMTP id q184mr2613177ywg.345.1459515632483;  Fri, 01 Apr 2016 06:00:32 -0700 (PDT)
Received: from [100.98.118.194] (126.sub-70-192-8.myvzw.com. [70.192.8.126]) by smtp.gmail.com with ESMTPSA id w79sm3532741ywd.55.2016.04.01.06.00.29 (version=TLSv1/SSLv3 cipher=OTHER); Fri, 01 Apr 2016 06:00:29 -0700 (PDT)
Content-Type: multipart/alternative; boundary=Apple-Mail-C4351318-B1B8-4D96-AC37-1D1F1CC49A0D
Mime-Version: 1.0 (1.0)
From: Sharon Goldberg <sharon.goldbe@gmail.com>
X-Mailer: iPhone Mail (13E234)
In-Reply-To: <OF35BF7FFD.C1AF1EA6-ONC1257F88.00430682-C1257F88.0043A34A@ptb.de>
Date: Fri, 1 Apr 2016 09:00:28 -0400
Content-Transfer-Encoding: 7bit
Message-Id: <BDF6E64B-B7BB-442A-9AA0-FCEBD5374462@gmail.com>
References: <CAJHGrrSxvxRfe8VRRxh8Eh5tkCw-D0t7uuA_YqcLZif=ho45nA@mail.gmail.com> <20160329152654.GH20902@localhost> <OF07030A8A.8267E74D-ONC1257F87.002F2081-C1257F87.0041C9FA@ptb.de> <20160331125908.GG834@localhost> <CAJHGrrRB8t3gf6On8z-Q-z+TShPAES86fZVvHn+582mu0d1vgQ@mail.gmail.com> <OF35BF7FFD.C1AF1EA6-ONC1257F88.00430682-C1257F88.0043A34A@ptb.de>
To: kristof.teichel@ptb.de
Archived-At: <http://mailarchive.ietf.org/arch/msg/tictoc/_5IXnxRm6sR2FzlC6iPx8Pev7sg>
X-Mailman-Approved-At: Sat, 02 Apr 2016 11:39:12 -0700
Cc: Sharon Goldberg <goldbe@cs.bu.edu>, NTP Working Group <ntpwg@lists.ntp.org>, tictoc@ietf.org
Subject: Re: [TICTOC] [ntpwg]  WGLC on NTS: Round trips for key exchange
X-BeenThere: tictoc@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Timing over IP Connection and Transfer of Clock BOF <tictoc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tictoc>, <mailto:tictoc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tictoc/>
List-Post: <mailto:tictoc@ietf.org>
List-Help: <mailto:tictoc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tictoc>, <mailto:tictoc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 01 Apr 2016 13:00:40 -0000

--Apple-Mail-C4351318-B1B8-4D96-AC37-1D1F1CC49A0D
Content-Type: text/plain;
	charset=us-ascii
Content-Transfer-Encoding: quoted-printable



Sharon, on phone=20
> On Apr 1, 2016, at 8:18 AM, kristof.teichel@ptb.de wrote:
>=20
> > > On Thu, Mar 31, 2016 at 8:59 AM, Miroslav Lichvar <mlichvar@redhat.com=
> wrote:=20
> > > On Thu, Mar 31, 2016 at 01:58:35PM +0200, kristof.teichel@ptb.de wrote=
:
> > > > To be honest, we had never assumed for IP fragmentation (on one requ=
est
> > > > and one response) to be a huge problem.
> > >=20
> > > One request and response could still be a problem. If the client is
> > > not able to receive fragmented packets, it won't be able to initialize=

> > > the NTS association.
> >
> > Right, to second that, there are middleboxes that block fragmented packe=
ts.
> >  =20
> > > > If people see grave problems with it, we would welcome an=20
> > > > elaboration as  to why this is.
> > >=20
> > > I'm not sure and I was hoping others would comment on that. It seems
> > > to me problems with IPv4 fragmentation are quite common due to
> > > firewalls dropping ICMP packets or IP fragments, and IPv6 doesn't seem=

> > > to recommend sending packets larger than 1500.=20
> >=20
> > To add to that, fragmentation is commonly used as an attack vector.=20
> > I would strongly discourage the use of IP fragmentation in what is=20
> > supposed to be a security protocol.  Please see these references for
> > a small sampling of examples.=20
>=20
> Is the issue specific to IP fragmentation of UDP packets? Or to IP fragmen=
tation in general?=20
> (I'm assuming it does not apply to all possible kinds of packet fragmentat=
ion.)=20
> I'm sorry, I have yet to go over the linked documents.=20

All fragmentation. The following paper affects both tcp and udp. =20

https://www.usenix.org/legacy/event/woot11/tech/final_files/Gilad.pdf

Again. My point is that we should not be relying on fragmentation in NTS. It=
 regularly leads to unexpected attacks. =20

Also quoting Ron Bonica from the first linked conversation below:

"please don't write new applications that fragment packets."

Sharon=20
> =20
> > https://www.nanog.org/sites/default/files/mon.general.fragmentation.boni=
ca.pdf
> >=20
> > http://www.hpl.hp.com/techreports/Compaq-DEC/WRL-87-3.pdf
> >=20
> > http://arxiv.org/abs/1205.4011
> >=20
> > https://media.blackhat.com/bh-eu-12/Atlasis/bh-eu-12-Atlasis-
> > Attacking_IPv6-WP.pdf
> >=20
> > http://www.iss.net/security_center/reference/vuln/TearDrop.htm
> >=20
> > https://www.offensive-security.com/wifu/Fragmentation-Attack-in-Practice=
.pdf
> >=20
> > Even if you don't see a SPECIFIC attack on NTS in these papers, my=20
> > point  is that we can usually find a way to exploit IP fragmentation
> > in unexpected ways to break security. This has happened over and=20
> > over in the last two decades on many different protocols. In fact=20
> > this is exactly what we did in our recent NTP paper, Section VI:
> >=20
> > .https://eprint.iacr.org/2015/1020.pdf
> >=20
> > I would strongly object to having NTS rely on IP fragmentation.  =20
> > This would be a horrible design decision.
>=20
> Noted.

--Apple-Mail-C4351318-B1B8-4D96-AC37-1D1F1CC49A0D
Content-Type: text/html;
	charset=utf-8
Content-Transfer-Encoding: 7bit

<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><div><div><br><br>Sharon, on phone&nbsp;</div>On Apr 1, 2016, at 8:18 AM, <a href="mailto:kristof.teichel@ptb.de">kristof.teichel@ptb.de</a> wrote:<br><br></div><blockquote type="cite"><div><tt><font size="2">&gt; &gt; On Thu, Mar 31, 2016 at 8:59 AM, Miroslav Lichvar
&lt;<a href="mailto:mlichvar@redhat.com">mlichvar@redhat.com</a>&gt; wrote:</font></tt>
<br><tt><font size="2">&gt; &gt; On Thu, Mar 31, 2016 at 01:58:35PM +0200,
<a href="mailto:kristof.teichel@ptb.de">kristof.teichel@ptb.de</a> wrote:<br>
&gt; &gt; &gt; To be honest, we had never assumed for IP fragmentation
(on one request<br>
&gt; &gt; &gt; and one response) to be a huge problem.<br>
&gt; &gt; <br>
&gt; &gt; One request and response could still be a problem. If the client
is<br>
&gt; &gt; not able to receive fragmented packets, it won't be able to initialize<br>
&gt; &gt; the NTS association.<br>
&gt;<br>
&gt; Right, to second that, there are middleboxes that block fragmented
packets.<br>
&gt; &nbsp;</font></tt>
<br><tt><font size="2">&gt; &gt; &gt; If people see grave problems with it,
we would welcome an <br>
&gt; &gt; &gt; elaboration as&nbsp; to why this is.<br>
&gt; &gt; <br>
&gt; &gt; I'm not sure and I was hoping others would comment on that. It
seems<br>
&gt; &gt; to me problems with IPv4 fragmentation are quite common due to<br>
&gt; &gt; firewalls dropping ICMP packets or IP fragments, and IPv6 doesn't
seem<br>
&gt; &gt; to recommend sending packets larger than 1500.</font></tt>
<br><tt><font size="2">&gt; <br>
&gt; To add to that, fragmentation is commonly used as an attack vector.&nbsp;<br>
&gt; I would strongly discourage the use of IP fragmentation in what is
<br>
&gt; supposed to be a security protocol.&nbsp; Please see these references
for<br>
&gt; a small sampling of examples.</font></tt>
<br>
<br><tt><font size="2">Is the issue specific to IP fragmentation of UDP packets?
Or to IP fragmentation in general? </font></tt>
<br><tt><font size="2">(I'm assuming it does not apply to all possible kinds
of packet fragmentation.)</font></tt>
<br><tt><font size="2">I'm sorry, I have yet to go over the linked documents.</font></tt>
<br></div></blockquote><div><br></div>All fragmentation. The following paper affects both tcp and udp. &nbsp;<div><br></div><div><a href="https://www.usenix.org/legacy/event/woot11/tech/final_files/Gilad.pdf">https://www.usenix.org/legacy/event/woot11/tech/final_files/Gilad.pdf</a></div><div><br></div><div>Again. My point is that we should not be relying on fragmentation in NTS. It regularly leads to unexpected attacks. &nbsp;</div><div><br></div><div>Also quoting Ron Bonica from the first linked conversation below:</div><div><br></div><div>"please don't write new applications that fragment packets."<br><div><br></div><div>Sharon&nbsp;<br><blockquote type="cite"><div><tt><font size="2">&nbsp;<br>
&gt; </font></tt><a href="https://www.nanog.org/sites/default/files/mon.general.fragmentation.bonica.pdf"><tt><font size="2">https://www.nanog.org/sites/default/files/mon.general.fragmentation.bonica.pdf</font></tt></a><tt><font size="2"><br>
&gt; <br>
&gt; </font></tt><a href="http://www.hpl.hp.com/techreports/Compaq-DEC/WRL-87-3.pdf"><tt><font size="2">http://www.hpl.hp.com/techreports/Compaq-DEC/WRL-87-3.pdf</font></tt></a><tt><font size="2"><br>
&gt; <br>
&gt; </font></tt><a href="http://arxiv.org/abs/1205.4011"><tt><font size="2">http://arxiv.org/abs/1205.4011</font></tt></a><tt><font size="2"><br>
&gt; <br>
&gt; </font></tt><a href="https://media.blackhat.com/bh-eu-12/Atlasis/bh-eu-12-Atlasis-"><tt><font size="2">https://media.blackhat.com/bh-eu-12/Atlasis/bh-eu-12-Atlasis-</font></tt></a><tt><font size="2"><br>
&gt; Attacking_IPv6-WP.pdf<br>
&gt; <br>
&gt; </font></tt><a href="http://www.iss.net/security_center/reference/vuln/TearDrop.htm"><tt><font size="2">http://www.iss.net/security_center/reference/vuln/TearDrop.htm</font></tt></a><tt><font size="2"><br>
&gt; <br>
&gt; </font></tt><a href="https://www.offensive-security.com/wifu/Fragmentation-Attack-in-Practice.pdf"><tt><font size="2">https://www.offensive-security.com/wifu/Fragmentation-Attack-in-Practice.pdf</font></tt></a><tt><font size="2"><br>
&gt;</font></tt>
<br><tt><font size="2">&gt; Even if you don't see a SPECIFIC attack on NTS
in these papers, my <br>
&gt; point&nbsp; is that we can usually find a way to exploit IP fragmentation<br>
&gt; in unexpected ways to break security. This has happened over and <br>
&gt; over in the last two decades on many different protocols. In fact
<br>
&gt; this is exactly what we did in our recent NTP paper, Section VI:<br>
&gt; <br>
&gt; .<a href="https://eprint.iacr.org/2015/1020.pdf">https://eprint.iacr.org/2015/1020.pdf</a><br>
&gt;</font></tt>
<br><tt><font size="2">&gt; I would strongly object to having NTS rely on
IP fragmentation.&nbsp;&nbsp; <br>
&gt; This would be a horrible design decision.<br>
</font></tt>
<br><tt><font size="2">Noted.</font></tt></div></blockquote></div></div></body></html>
--Apple-Mail-C4351318-B1B8-4D96-AC37-1D1F1CC49A0D--


From nobody Mon Apr  4 04:58:38 2016
Return-Path: <kristof.teichel@ptb.de>
X-Original-To: tictoc@ietfa.amsl.com
Delivered-To: tictoc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9278612D563 for <tictoc@ietfa.amsl.com>; Mon,  4 Apr 2016 04:58:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.01
X-Spam-Level: 
X-Spam-Status: No, score=-0.01 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, HTML_MESSAGE=0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Lt8JdFAtyqXq for <tictoc@ietfa.amsl.com>; Mon,  4 Apr 2016 04:58:34 -0700 (PDT)
Received: from mx1.bs.ptb.de (mx1.bs.ptb.de [192.53.103.120]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6658512D676 for <tictoc@ietf.org>; Mon,  4 Apr 2016 04:58:33 -0700 (PDT)
Received: from smtp-hub.bs.ptb.de (smtpint01.bs.ptb.de [141.25.87.32]) by mx1.bs.ptb.de  with ESMTP id u34BwUZ5026710-u34BwUZ7026710 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA bits=256 verify=FAIL); Mon, 4 Apr 2016 13:58:30 +0200
Received: from rose.bs.ptb.de (rose.bs.ptb.de [141.25.85.201]) by smtp-hub.bs.ptb.de (Postfix) with ESMTP id D1FA3C55A8; Mon,  4 Apr 2016 13:58:30 +0200 (CEST)
To: "NTP Working Group" <ntpwg@lists.ntp.org>, tictoc@ietf.org
MIME-Version: 1.0
Message-ID: <OFF80DC420.C7FFCAC3-ONC1257F8B.0040F781-C1257F8B.0041C7B6@ptb.de>
From: kristof.teichel@ptb.de
Date: Mon, 4 Apr 2016 13:58:29 +0200
Content-Type: multipart/alternative; boundary="=_alternative 0041C7B6C1257F8B_="
Archived-At: <http://mailarchive.ietf.org/arch/msg/tictoc/JMEpMjKo0qj4j5vsiLP6ctnFyfM>
Subject: [TICTOC] Meet up for NTS discussions in Buenos Aires?
X-BeenThere: tictoc@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Timing over IP Connection and Transfer of Clock BOF <tictoc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tictoc>, <mailto:tictoc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tictoc/>
List-Post: <mailto:tictoc@ietf.org>
List-Help: <mailto:tictoc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tictoc>, <mailto:tictoc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 04 Apr 2016 11:58:36 -0000

Dies ist eine mehrteilige Nachricht im MIME-Format.
--=_alternative 0041C7B6C1257F8B_=
Content-Type: text/plain; charset="US-ASCII"

Hello all,

I just wanted to throw out the question who else on these mailing lists is 
in Buenos Aires for this IETF meeting and would want to meet up with me to 
discuss any NTS-related issues over some food and/or drink?
I would prefer to do this after tomorrow's WG session.

Best regards,
Kristof
--=_alternative 0041C7B6C1257F8B_=
Content-Type: text/html; charset="US-ASCII"

<font size=2 face="sans-serif">Hello all,</font>
<br>
<br><font size=2 face="sans-serif">I just wanted to throw out the question
who else on these mailing lists is in Buenos Aires for this IETF meeting
and would want to meet up with me to discuss any NTS-related issues over
some food and/or drink?</font>
<br><font size=2 face="sans-serif">I would prefer to do this after tomorrow's
WG session.</font>
<br>
<br><font size=2 face="sans-serif">Best regards,</font>
<br><font size=2 face="sans-serif">Kristof</font>
--=_alternative 0041C7B6C1257F8B_=--


From nobody Mon Apr  4 22:21:51 2016
Return-Path: <odonoghue@isoc.org>
X-Original-To: tictoc@ietfa.amsl.com
Delivered-To: tictoc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 18A5512D6F3 for <tictoc@ietfa.amsl.com>; Mon,  4 Apr 2016 22:21:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=isoc.onmicrosoft.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yEny4zqhoxI9 for <tictoc@ietfa.amsl.com>; Mon,  4 Apr 2016 22:21:47 -0700 (PDT)
Received: from na01-bn1-obe.outbound.protection.outlook.com (mail-bn1on0646.outbound.protection.outlook.com [IPv6:2a01:111:f400:fc10::646]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 773BA12D648 for <tictoc@ietf.org>; Mon,  4 Apr 2016 22:21:47 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=isoc.onmicrosoft.com;  s=selector1-isoc-org; h=From:To:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=wIIW0bypcBzxWozBXQLeOROBC5C5pe7mwJ2TlagKjjY=; b=kNgvjDOyyZPlgSerzNS+uu1KJpzRQwsuH9w2JZ1Y7mB01I1EE0pso07oN1kUpQdRPijFk6QxeKe7wQw0bu06I1+6w+/FDJWgkxffK6K8aUxwYv5jiRWwp8+5FRgfXBW44BGT7Eso59CvF2IgHfS5bPiKbgy3sKiuw4Y4EXCeWpU=
Received: from DM2PR0601MB1118.namprd06.prod.outlook.com (10.160.218.139) by DM2PR0601MB1119.namprd06.prod.outlook.com (10.160.218.14) with Microsoft SMTP Server (TLS) id 15.1.447.15; Tue, 5 Apr 2016 05:21:27 +0000
Received: from DM2PR0601MB1118.namprd06.prod.outlook.com ([10.160.218.139]) by DM2PR0601MB1118.namprd06.prod.outlook.com ([10.160.218.139]) with mapi id 15.01.0447.028; Tue, 5 Apr 2016 05:21:27 +0000
From: Karen O'Donoghue <odonoghue@isoc.org>
To: "tictoc@ietf.org" <tictoc@ietf.org>
Thread-Topic: Liaison Statement on ITU - T Q14/15 work on the management model for time and frequency synchronization 
Thread-Index: AQHRjvsAq7c1xv8OsEeGg11nRTYngA==
Date: Tue, 5 Apr 2016 05:21:27 +0000
Message-ID: <068C2671-3D35-45A6-A384-A4F382166240@isoc.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
authentication-results: ietf.org; dkim=none (message not signed) header.d=none;ietf.org; dmarc=none action=none header.from=isoc.org;
x-ms-exchange-messagesentrepresentingtype: 1
x-originating-ip: [2001:67c:370:136:d438:3c4d:fae5:8d42]
x-ms-office365-filtering-correlation-id: 50559a26-e457-4508-8a54-08d35d12237e
x-microsoft-exchange-diagnostics: 1; DM2PR0601MB1119; 5:B6BQpIHV6gniKOCgqCXx5/DH4xHAFUzjGA31k4rL+uyKkYNxskzCyDc57q8mcUzCy6efDGetCT0rrJNgKdFBMzQcNcH5DKgjJ2kS75Vu2yakY48KStD2XGJ1kcSlo8hn/ccXbrQ2QU+238QoVX43dg==; 24:HhG6u4wzO7qhSm21PuJxxVV91rfiLzqBo5uF9nwebTBaveiZ8mUZBv69xrSDHkgLMC9YjscIbvpxEUFj5BAb4AifkWs7yp2k5JFDOv50hnU=
x-microsoft-antispam: UriScan:;BCL:0;PCL:0;RULEID:;SRVR:DM2PR0601MB1119;
x-microsoft-antispam-prvs: <DM2PR0601MB1119956D358642BD75696AD2C29E0@DM2PR0601MB1119.namprd06.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:;
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(601004)(2401047)(8121501046)(5005006)(3002001)(10201501046); SRVR:DM2PR0601MB1119; BCL:0; PCL:0; RULEID:; SRVR:DM2PR0601MB1119; 
x-forefront-prvs: 0903DD1D85
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(52044002)(16236675004)(102836003)(6116002)(2351001)(1220700001)(1096002)(50986999)(5004730100002)(2501003)(82746002)(229853001)(1730700002)(11100500001)(36756003)(19617315012)(3660700001)(3280700002)(33656002)(10400500002)(2906002)(83716003)(54356999)(77096005)(15975445007)(81166005)(5640700001)(92566002)(106116001)(189998001)(107886002)(110136002)(2900100001)(87936001)(19580395003)(450100001)(86362001)(586003)(5002640100001)(99286002)(5008740100001)(122556002)(3826002); DIR:OUT; SFP:1101; SCL:1; SRVR:DM2PR0601MB1119; H:DM2PR0601MB1118.namprd06.prod.outlook.com; FPR:; SPF:None; MLV:sfv; LANG:en; 
spamdiagnosticoutput: 1:23
spamdiagnosticmetadata: NSPM
Content-Type: multipart/alternative; boundary="_000_068C26713D3545A6A384A4F382166240isocorg_"
MIME-Version: 1.0
X-OriginatorOrg: isoc.org
X-MS-Exchange-CrossTenant-originalarrivaltime: 05 Apr 2016 05:21:27.0349 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 89f84dfb-7285-4810-bc4d-8b9b5794554f
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DM2PR0601MB1119
Archived-At: <http://mailarchive.ietf.org/arch/msg/tictoc/YePBlUJ3gHaqj8za8hv7xV5ZvMs>
Subject: [TICTOC] Liaison Statement on ITU - T Q14/15 work on the management model for time and frequency synchronization
X-BeenThere: tictoc@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Timing over IP Connection and Transfer of Clock BOF <tictoc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tictoc>, <mailto:tictoc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tictoc/>
List-Post: <mailto:tictoc@ietf.org>
List-Help: <mailto:tictoc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tictoc>, <mailto:tictoc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 05 Apr 2016 05:21:50 -0000

--_000_068C26713D3545A6A384A4F382166240isocorg_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Folks,

The TICTOC working group has received a liaison statement from ITU-T SG 15 =
on their work on a UML management mode for time and frequency networks.

https://datatracker.ietf.org/liaison/1461/

This is part of the ongoing effort to keep all parties informed of the mana=
gement efforts in IEEE 802.1, IEEE 1588, IETF, and ITU-T. If you have any c=
omments please feel free to send them to me or to the mailing list. At this=
 point, this is for information purposes only.

Regards,
Karen

--_000_068C26713D3545A6A384A4F382166240isocorg_
Content-Type: text/html; charset="us-ascii"
Content-ID: <1EA1019498F56A43B468AF368EE4E436@namprd06.prod.outlook.com>
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
</head>
<body style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-lin=
e-break: after-white-space;" class=3D"">
Folks,
<div class=3D""><br class=3D"">
</div>
<div class=3D"">The TICTOC working group has received a liaison statement f=
rom ITU-T SG 15 on their work on a UML management mode for time and frequen=
cy networks.&nbsp;</div>
<div class=3D""><br class=3D"">
</div>
<div class=3D""><a href=3D"https://datatracker.ietf.org/liaison/1461/" clas=
s=3D"">https://datatracker.ietf.org/liaison/1461/</a></div>
<div class=3D""><br class=3D"">
</div>
<div class=3D"">This is part of the ongoing effort to keep all parties info=
rmed of the management efforts in IEEE 802.1, IEEE 1588, IETF, and ITU-T. I=
f you have any comments please feel free to send them to me or to the maili=
ng list. At this point, this is for
 information purposes only.&nbsp;</div>
<div class=3D""><br class=3D"">
</div>
<div class=3D"">Regards,</div>
<div class=3D"">Karen</div>
</body>
</html>

--_000_068C26713D3545A6A384A4F382166240isocorg_--


From nobody Tue Apr  5 09:06:25 2016
Return-Path: <odonoghue@isoc.org>
X-Original-To: tictoc@ietfa.amsl.com
Delivered-To: tictoc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 08D4B12D70A for <tictoc@ietfa.amsl.com>; Tue,  5 Apr 2016 09:06:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level: 
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=isoc.onmicrosoft.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id C0n4ejyXEHaI for <tictoc@ietfa.amsl.com>; Tue,  5 Apr 2016 09:06:21 -0700 (PDT)
Received: from na01-bl2-obe.outbound.protection.outlook.com (mail-bl2on0087.outbound.protection.outlook.com [65.55.169.87]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9837612D6CB for <tictoc@ietf.org>; Tue,  5 Apr 2016 09:06:20 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=isoc.onmicrosoft.com;  s=selector1-isoc-org; h=From:To:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=Gfzqphq5hhH71eBanCqxCArO8JYwLIehpMd6O0bC4Gs=; b=cBPrMz35iTFbJhNnw5SHR1AwsuQyuE7rL9t4aoQqgylXkeL1oDc1iVWxoofYpIz+uWhjuACo4o1mJFEkK/EqDFpeo7fpwQgi2/kQCq1+XyjAcynPCLXzUGzJk4eoBR7mPLi0Y3AQ2Y7LdIQ/ACjuR5lB29dEwcgnMziKXIytsMc=
Received: from DM2PR0601MB1118.namprd06.prod.outlook.com (10.160.218.139) by DM2PR0601MB1118.namprd06.prod.outlook.com (10.160.218.139) with Microsoft SMTP Server (TLS) id 15.1.447.15; Tue, 5 Apr 2016 16:06:19 +0000
Received: from DM2PR0601MB1118.namprd06.prod.outlook.com ([10.160.218.139]) by DM2PR0601MB1118.namprd06.prod.outlook.com ([10.160.218.139]) with mapi id 15.01.0447.028; Tue, 5 Apr 2016 16:06:19 +0000
From: Karen O'Donoghue <odonoghue@isoc.org>
To: "ntpwg@lists.ntp.org" <ntpwg@lists.ntp.org>, "tictoc@ietf.org" <tictoc@ietf.org>
Thread-Topic: final instructions for the NTP/TICTOC remote participation
Thread-Index: AQHRj1UWSjaBhpEHNU+8xws6WkVjMA==
Date: Tue, 5 Apr 2016 16:06:18 +0000
Message-ID: <2304D4FC-6CD1-422B-9F09-948C61E090E7@isoc.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
authentication-results: lists.ntp.org; dkim=none (message not signed) header.d=none;lists.ntp.org; dmarc=none action=none header.from=isoc.org;
x-ms-exchange-messagesentrepresentingtype: 1
x-originating-ip: [31.133.176.204]
x-ms-office365-filtering-correlation-id: b128a604-532c-4146-4bc7-08d35d6c397d
x-microsoft-exchange-diagnostics: 1; DM2PR0601MB1118; 5:ANlFmBLsQUA/Aw9Ipl3KwxS+Xk9hZktVhcTCIqLFIZ6bzLvc5P3rhuYtb3U1dMBgxf4t0sUFU+YfSkL/b8Vo6YgH2Y46mulk4CYuWs5CYu6y6eCFCH0mlSUY7SggglvzaFSkpQbBvmRM+pkUKbI9hA==; 24:5ULO8ZezIPvrNa0neLzgKEZllFoa2AYG94SWlTF7Rovol5u00FzSHuRt60uKrppfawcVJIWwvWwBru/4fwEjnuB66A+cjfc6pi7cQpFp2rk=
x-microsoft-antispam: UriScan:;BCL:0;PCL:0;RULEID:;SRVR:DM2PR0601MB1118;
x-microsoft-antispam-prvs: <DM2PR0601MB111898403C034F5A89EADD11C29E0@DM2PR0601MB1118.namprd06.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:;
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(601004)(2401047)(5005006)(8121501046)(3002001)(10201501046); SRVR:DM2PR0601MB1118; BCL:0; PCL:0; RULEID:; SRVR:DM2PR0601MB1118; 
x-forefront-prvs: 0903DD1D85
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(164054003)(81166005)(229853001)(83716003)(87936001)(5008740100001)(16236675004)(66066001)(107886002)(19617315012)(15975445007)(77096005)(5004730100002)(36756003)(5001770100001)(92566002)(189998001)(2900100001)(122556002)(2501003)(33656002)(54356999)(16799955002)(86362001)(5002640100001)(99286002)(3280700002)(106116001)(11100500001)(6116002)(1220700001)(3660700001)(1096002)(586003)(3846002)(10400500002)(2906002)(102836003)(19580395003)(82746002)(50986999); DIR:OUT; SFP:1101; SCL:1; SRVR:DM2PR0601MB1118; H:DM2PR0601MB1118.namprd06.prod.outlook.com; FPR:; SPF:None; MLV:sfv; LANG:en; 
spamdiagnosticoutput: 1:23
spamdiagnosticmetadata: NSPM
Content-Type: multipart/alternative; boundary="_000_2304D4FC6CD1422B9F09948C61E090E7isocorg_"
MIME-Version: 1.0
X-OriginatorOrg: isoc.org
X-MS-Exchange-CrossTenant-originalarrivaltime: 05 Apr 2016 16:06:18.9391 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 89f84dfb-7285-4810-bc4d-8b9b5794554f
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DM2PR0601MB1118
Archived-At: <http://mailarchive.ietf.org/arch/msg/tictoc/AEE-Dk3j5tYzLhP5Du5S2npwpl4>
Subject: [TICTOC] final instructions for the NTP/TICTOC remote participation
X-BeenThere: tictoc@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Timing over IP Connection and Transfer of Clock BOF <tictoc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tictoc>, <mailto:tictoc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tictoc/>
List-Post: <mailto:tictoc@ietf.org>
List-Help: <mailto:tictoc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tictoc>, <mailto:tictoc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 05 Apr 2016 16:06:24 -0000

--_000_2304D4FC6CD1422B9F09948C61E090E7isocorg_
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64

Rm9sa3MsDQoNClJlbWluZGVyIHRoYXQgdGhlIE5UUC9USUNUT0MgbWVldGluZyBzdGFydHMgaW4g
MSBob3VyLiBXZSBhcmUgd29ya2luZyBvbiBpbXByb3Zpbmcgb3VyIHJlbW90ZSBwYXJ0aWNpcGF0
aW9uIHRvb2xzLg0KDQpIZXJlIGlzIGEgbGluayB0byBhbGwgdGhlIGluZm9ybWF0aW9uIGFib3V0
IHRoZSBNZWV0ZWNobyB0b29sDQpodHRwOi8vaWV0Zjk1LmNvbmYubWVldGVjaG8uY29tL2luZGV4
LnBocC9SZW1vdGVfUGFydGljaXBhdGlvbg0KDQpJIHNlbnQgc29tZXRoaW5nIGVhcmxpZXIgYWJv
dXQgcmVxdWlyaW5nIHJlZ2lzdHJhdGlvbi4gVGhleSB3b3VsZCByZWFsbHkgbGlrZSB5b3UgdG8g
cmVnaXN0ZXIsIGJ1dCB5b3UgZG9u4oCZdCBoYXZlIHRv4oCmDQoNCkhvd2V2ZXIsIEkgd291bGQg
c3Ryb25nbHkgZW5jb3VyYWdlIHlvdSB0byBkbyB0aGUgc2VsZiB0ZXN0IHRvIGVuc3VyZSB0aGF0
IHlvdXIgYXVkaW8vdmlkZW8gYXJlIHdvcmtpbmcuIEnigJl2ZSBkb25lIGl0IHdpdGggdGhlIGNo
cm9tZSBicm93c2VyIGFuZCBpdCB3b3JrZWQgZmluZeKApiBubyBwbHVnaW5zIG9yIGFueXRoaW5n
4oCmDQoNClRoYW5rcywNCkthcmVuDQoNCg==

--_000_2304D4FC6CD1422B9F09948C61E090E7isocorg_
Content-Type: text/html; charset="utf-8"
Content-ID: <15F0BC9D2F432D4BAD59ED33C8FCE310@namprd06.prod.outlook.com>
Content-Transfer-Encoding: base64

PGh0bWw+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIgY29udGVudD0i
dGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjwvaGVhZD4NCjxib2R5IHN0eWxlPSJ3b3JkLXdy
YXA6IGJyZWFrLXdvcmQ7IC13ZWJraXQtbmJzcC1tb2RlOiBzcGFjZTsgLXdlYmtpdC1saW5lLWJy
ZWFrOiBhZnRlci13aGl0ZS1zcGFjZTsiIGNsYXNzPSIiPg0KPGRpdiBjbGFzcz0iIj5Gb2xrcyw8
L2Rpdj4NCjxkaXYgY2xhc3M9IiI+PGJyIGNsYXNzPSIiPg0KPC9kaXY+DQo8ZGl2IGNsYXNzPSIi
PlJlbWluZGVyIHRoYXQgdGhlIE5UUC9USUNUT0MgbWVldGluZyBzdGFydHMgaW4gMSBob3VyLiBX
ZSBhcmUgd29ya2luZyBvbiBpbXByb3Zpbmcgb3VyIHJlbW90ZSBwYXJ0aWNpcGF0aW9uIHRvb2xz
LiZuYnNwOzwvZGl2Pg0KPGRpdiBjbGFzcz0iIj48YnIgY2xhc3M9IiI+DQo8L2Rpdj4NCjxkaXYg
Y2xhc3M9IiI+SGVyZSBpcyBhIGxpbmsgdG8gYWxsIHRoZSBpbmZvcm1hdGlvbiBhYm91dCB0aGUg
TWVldGVjaG8gdG9vbDwvZGl2Pg0KPGRpdiBjbGFzcz0iIj48YSBocmVmPSJodHRwOi8vaWV0Zjk1
LmNvbmYubWVldGVjaG8uY29tL2luZGV4LnBocC9SZW1vdGVfUGFydGljaXBhdGlvbiIgY2xhc3M9
IiI+aHR0cDovL2lldGY5NS5jb25mLm1lZXRlY2hvLmNvbS9pbmRleC5waHAvUmVtb3RlX1BhcnRp
Y2lwYXRpb248L2E+PC9kaXY+DQo8ZGl2IGNsYXNzPSIiPjxiciBjbGFzcz0iIj4NCjwvZGl2Pg0K
PGRpdiBjbGFzcz0iIj5JIHNlbnQgc29tZXRoaW5nIGVhcmxpZXIgYWJvdXQgcmVxdWlyaW5nIHJl
Z2lzdHJhdGlvbi4gVGhleSB3b3VsZCByZWFsbHkgbGlrZSB5b3UgdG8gcmVnaXN0ZXIsIGJ1dCB5
b3UgZG9u4oCZdCBoYXZlIHRv4oCmJm5ic3A7PC9kaXY+DQo8ZGl2IGNsYXNzPSIiPjxiciBjbGFz
cz0iIj4NCjwvZGl2Pg0KPGRpdiBjbGFzcz0iIj5Ib3dldmVyLCBJIHdvdWxkIHN0cm9uZ2x5IGVu
Y291cmFnZSB5b3UgdG8gZG8gdGhlIHNlbGYgdGVzdCB0byBlbnN1cmUgdGhhdCB5b3VyIGF1ZGlv
L3ZpZGVvIGFyZSB3b3JraW5nLiBJ4oCZdmUgZG9uZSBpdCB3aXRoIHRoZSBjaHJvbWUgYnJvd3Nl
ciBhbmQgaXQgd29ya2VkIGZpbmXigKYgbm8gcGx1Z2lucyBvciBhbnl0aGluZ+KApiZuYnNwOzwv
ZGl2Pg0KPGRpdiBjbGFzcz0iIj48YnIgY2xhc3M9IiI+DQo8L2Rpdj4NCjxkaXYgY2xhc3M9IiI+
VGhhbmtzLDwvZGl2Pg0KPGRpdiBjbGFzcz0iIj5LYXJlbjwvZGl2Pg0KPGRpdiBjbGFzcz0iIj48
YnIgY2xhc3M9IiI+DQo8L2Rpdj4NCjwvYm9keT4NCjwvaHRtbD4NCg==

--_000_2304D4FC6CD1422B9F09948C61E090E7isocorg_--


From nobody Tue Apr  5 10:40:03 2016
Return-Path: <sharon.goldbe@gmail.com>
X-Original-To: tictoc@ietfa.amsl.com
Delivered-To: tictoc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CB35212D997 for <tictoc@ietfa.amsl.com>; Tue,  5 Apr 2016 10:40:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.399
X-Spam-Level: 
X-Spam-Status: No, score=-2.399 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.199, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BQX43o-7wY2z for <tictoc@ietfa.amsl.com>; Tue,  5 Apr 2016 10:40:00 -0700 (PDT)
Received: from mail-wm0-x235.google.com (mail-wm0-x235.google.com [IPv6:2a00:1450:400c:c09::235]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9344812D991 for <tictoc@ietf.org>; Tue,  5 Apr 2016 10:40:00 -0700 (PDT)
Received: by mail-wm0-x235.google.com with SMTP id u206so13959209wme.1 for <tictoc@ietf.org>; Tue, 05 Apr 2016 10:40:00 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:sender:from:date:message-id:subject:to; bh=pUKZCp9FIeFXJVo7uPeatovGgsym1Eywfb5As/KHtrs=; b=HsMBFCeLexWiBMcQmPipS4cw1eZ7HeuCKILebHzmo7aWxR5PUG6dYljo8kYUueLgB1 wb+cfCAkEXt1GqyUbxpmRsEZiehd5cSTQRPS65oTExjfjo+16l6FfOhzJjZnGXVunNDl 85ByXXZGZ46gXFnVawrYwvAZsM3GZGePUTqMTsc0MBu0YeWu3FlZs5IuIoYa0JWfMYd3 aDIJaE4siFu5zY3aH8ItcPgneL74YHfX0PJJQZkn7BTUCyVEfC9O/3NBs4XL22+7PtnU QUIkwzQNaicVpYH2CAXQwAEykcYVmGira81UUflNFA5mwJ/bBeKuv10g1iGDpE2ni2sB JOIA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:sender:from:date:message-id:subject :to; bh=pUKZCp9FIeFXJVo7uPeatovGgsym1Eywfb5As/KHtrs=; b=B9coF6au3XCpF45F8OoFnV371d0VB2mc39Vnvij2mBzfEq+a8hIeD07tV/cmeiwMnn wKVAPdpft43xhC71kFNwbV0NmkoZy/fW8HugEGwDMkbDQJ2gtW8/UZrqDuK40ioszabs /D1aBX5thbdwwCci16tBAmUny7WpFWmINgIbenpjMtFv3J6IIqayy3ubUNrIk09eLdq/ 65IfW3imd6P86HuELNyzYyLgi6DMcNYUEC3ZkF1/pjSFmNB8zGhCQ1BYzE4m+OSgKmym Sd2oX6KwQQqn/iynRWut6btkeuTA5dMSBPvGbkYxXOFWtUTItCgIjWs2TdUvy3tYOXmg eS4Q==
X-Gm-Message-State: AD7BkJLMIRFKS6s2iswbBWLiK0uajLsmy4FgevEFAhhw3wU6B8skgI0cIiKfwGxxtsjTj1lhEHn2hFps7QH5ag==
X-Received: by 10.194.178.233 with SMTP id db9mr7535395wjc.11.1459877999076; Tue, 05 Apr 2016 10:39:59 -0700 (PDT)
MIME-Version: 1.0
Sender: sharon.goldbe@gmail.com
Received: by 10.194.71.200 with HTTP; Tue, 5 Apr 2016 10:39:19 -0700 (PDT)
From: Sharon Goldberg <goldbe@cs.bu.edu>
Date: Tue, 5 Apr 2016 13:39:19 -0400
X-Google-Sender-Auth: VIDeUYYI1KC5PspTBsNYrgF5N38
Message-ID: <CAJHGrrT-noiSe2tk_AQ0czdHxs70enftwC3DOniyKTv_aVoQEg@mail.gmail.com>
To: NTP Working Group <ntpwg@lists.ntp.org>, tictoc@ietf.org
Content-Type: multipart/alternative; boundary=089e013d1a088cec6f052fc0551d
Archived-At: <http://mailarchive.ietf.org/arch/msg/tictoc/z7iLtkeUVSlOoWfOpJ1PCbTny2I>
Subject: [TICTOC] WGLC on NTS: Server seed key refresh
X-BeenThere: tictoc@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Timing over IP Connection and Transfer of Clock BOF <tictoc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tictoc>, <mailto:tictoc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tictoc/>
List-Post: <mailto:tictoc@ietf.org>
List-Help: <mailto:tictoc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tictoc>, <mailto:tictoc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 05 Apr 2016 17:40:03 -0000

--089e013d1a088cec6f052fc0551d
Content-Type: text/plain; charset=UTF-8

Just to follow up on my comment during the IETF'95 wg meeting right now:
 NTS requires a server-seed refresh, and uses the 5th and 6th message of
the KE protocol to do this.  What is the use case for server seed key
refresh?

Thanks,
Sharon

-- 
Sharon Goldberg
Computer Science, Boston University
http://www.cs.bu.edu/~goldbe

--089e013d1a088cec6f052fc0551d
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Just to follow up on my comment during the IETF&#39;95 wg =
meeting right now: =C2=A0NTS requires a server-seed refresh, and uses the 5=
th and 6th message of the KE protocol to do this.=C2=A0 What is the use cas=
e for server seed key refresh?=C2=A0<div><br><div>Thanks,</div><div>Sharon<=
/div><div><div><br></div>-- <br><div class=3D"gmail_signature">Sharon Goldb=
erg<br>Computer Science, Boston University<br><a href=3D"http://www.cs.bu.e=
du/~goldbe" target=3D"_blank">http://www.cs.bu.edu/~goldbe</a></div>
</div></div></div>

--089e013d1a088cec6f052fc0551d--


From nobody Tue Apr  5 11:28:51 2016
Return-Path: <sharon.goldbe@gmail.com>
X-Original-To: tictoc@ietfa.amsl.com
Delivered-To: tictoc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id ACEBF12D118 for <tictoc@ietfa.amsl.com>; Tue,  5 Apr 2016 11:28:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.399
X-Spam-Level: 
X-Spam-Status: No, score=-2.399 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.199, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id i1keHKFYzk7U for <tictoc@ietfa.amsl.com>; Tue,  5 Apr 2016 11:28:48 -0700 (PDT)
Received: from mail-wm0-x234.google.com (mail-wm0-x234.google.com [IPv6:2a00:1450:400c:c09::234]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7B8B612D0F5 for <tictoc@ietf.org>; Tue,  5 Apr 2016 11:28:48 -0700 (PDT)
Received: by mail-wm0-x234.google.com with SMTP id n3so32843361wmn.0 for <tictoc@ietf.org>; Tue, 05 Apr 2016 11:28:48 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:sender:from:date:message-id:subject:to; bh=Z51CzLKGXGPJeBZ9b8AD4D4GTSNjqpZA+PZZUI4/3xI=; b=BhQ7cxeT/GsE4P44USquz1xpJ0kEdKVcQ/7Xe/XcWxrOrYVcZrKSkyLEeFoSj4bSgb O2T5KjcC8aMhH0ug8XD3E5TK5PZQB9xbeNF576bBueUeQhMc7rS1Dn8MzzYD9MLNlYbL 7CkTLRIltwGasJMhN0+GZ8OLPE6TrzFhwZoiFEl1xF4mvZJRhaJitaRVxBzzBKcO7odS vVBYhkGED1zgoG9bRfN2l0rbYCIws+lCYgwU2bah0gp/4If78ASEzulzmLWlflHHf2or uo6kksPUyGdtGZ3U8+gv3bBjFSn587rLyzqPmjBXX8wfYpbSlS39B6R29+h7zyJ8CDq0 VctA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:sender:from:date:message-id:subject :to; bh=Z51CzLKGXGPJeBZ9b8AD4D4GTSNjqpZA+PZZUI4/3xI=; b=C9eKmzhK03wfWHIWbfUMQj2uVWhBv3cFXfRTfPHgupfgR+h27phWKJRhdenT6dUSIn nC8I8n9i1AReyKoeNRwv5Iz3l+6d2XK+Oo7X49tTgDvfUFFdzWXgHJ/Ufvir0J1v/B3D m60VBqClY3fXZSDwp7TEkALyuoZbF88wyxAo7ehjQR3equJIKikXRyohXoRcqurPpvRM /IqlRVs2aomomSc+uSlvve/U/lfrR+ua3qcxm9DGwlE0TD5Uei0sHjJ4rSe/vQNar9xX /V7zU4COD6eZJ4mvlWhj81LK2B9jMnBoui3m1pzPA9gJ6svQWMWy86cWDTU1i1Qg8P9n J9nQ==
X-Gm-Message-State: AD7BkJLO8sHhOInzivJvjMNzTIMNOzskbDrIbJD2eWcJMi7hrbX6o/YExsCatEesJDjAeivFO5eCxovbkfYRwA==
X-Received: by 10.28.227.130 with SMTP id a124mr19574809wmh.2.1459880926855; Tue, 05 Apr 2016 11:28:46 -0700 (PDT)
MIME-Version: 1.0
Sender: sharon.goldbe@gmail.com
Received: by 10.194.71.200 with HTTP; Tue, 5 Apr 2016 11:28:07 -0700 (PDT)
From: Sharon Goldberg <goldbe@cs.bu.edu>
Date: Tue, 5 Apr 2016 14:28:07 -0400
X-Google-Sender-Auth: bSVIivK_1HeqCLIq_AmRyULwB_A
Message-ID: <CAJHGrrQimUVqtRg6bowwBr5pxrSUh+mHkEzB0P1SBxP=nzczbg@mail.gmail.com>
To: NTP Working Group <ntpwg@lists.ntp.org>, tictoc@ietf.org
Content-Type: multipart/alternative; boundary=001a114ccbd40f479b052fc10468
Archived-At: <http://mailarchive.ietf.org/arch/msg/tictoc/aO2qbM2w7huSgQIFk8buwy5W2-Y>
Subject: [TICTOC] comments on draft-stenn-ntp-suggest-refid-00
X-BeenThere: tictoc@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Timing over IP Connection and Transfer of Clock BOF <tictoc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tictoc>, <mailto:tictoc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tictoc/>
List-Post: <mailto:tictoc@ietf.org>
List-Help: <mailto:tictoc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tictoc>, <mailto:tictoc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 05 Apr 2016 18:28:50 -0000

--001a114ccbd40f479b052fc10468
Content-Type: text/plain; charset=UTF-8

Dear WG,

To follow up on my comments on draft-stenn-ntp-suggest-refid-00 at the
IETF'95 WG meeting just now. The current draft requires the use of an
extension field.  I believe the goals of the draft can be accomplished
without using an extension field, in a backwards compatible fashion.

The goal of the draft is to limit the information exposed by the REFID
while still preserving robustness to "length-1" timing loops where system A
takes time from system B, but system B takes time from system A.
This proposal allow system A to limit the info it leaks in its refID,
without harming any of its legacy clients.

Suppose system A is taking time from system B. Then there are two cases:
1) If A gets a time query from system B, A puts the IP of B in the refID of
its response. This way, even a legacy B can tell it cannot take time from A
because this would cause a timing loop.

2) If A gets a time query from system C, A puts a "nonsense" value in its
refID.  Even a legacy C can see that its IP is not in the refID, and so it
is allowed to take time from A.

One question is what this "nonsense" value should be.  I think it should be
a fixed value. For example 0.0.0.0.  We would not want a randomly-chosen
value since this might collide with actual IP addresses on the network.

Thanks,
Sharon


-- 
Sharon Goldberg
Computer Science, Boston University
http://www.cs.bu.edu/~goldbe

--001a114ccbd40f479b052fc10468
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div>Dear WG,</div><div><br></div><div>To follow up on my =
comments on draft-stenn-ntp-suggest-refid-00 at the IETF&#39;95 WG meeting =
just now. The current draft requires the use of an extension field.=C2=A0 I=
 believe the goals of the draft can be accomplished without using an extens=
ion field, in a backwards compatible fashion.</div><div><br></div><div>The =
goal of the draft is to limit the information exposed by the REFID while st=
ill preserving robustness to &quot;length-1&quot; timing loops where system=
 A takes time from system B, but system B takes time from system A. =C2=A0<=
/div><div>This proposal allow system A to limit the info it leaks in its re=
fID, without harming any of its legacy clients.=C2=A0</div><div><br></div><=
div>Suppose system A is taking time from system B. Then there are two cases=
:</div><div>1) If A gets a time query from system B, A puts the IP of B in =
the refID of its response. This way, even a legacy B can tell it cannot tak=
e time from A because this would cause a timing loop.</div><div><br></div><=
div>2) If A gets a time query from system C, A puts a &quot;nonsense&quot; =
value in its refID.=C2=A0 Even a legacy C can see that its IP is not in the=
 refID, and so it is allowed to take time from A.=C2=A0</div><div><br></div=
><div>One question is what this &quot;nonsense&quot; value should be.=C2=A0=
 I think it should be a fixed value. For example 0.0.0.0.=C2=A0 We would no=
t want a randomly-chosen value since this might collide with actual IP addr=
esses on the network.</div><div><br></div><div>Thanks,</div><div>Sharon</di=
v><div><br></div><div><br></div>-- <br><div class=3D"gmail_signature">Sharo=
n Goldberg<br>Computer Science, Boston University<br><a href=3D"http://www.=
cs.bu.edu/~goldbe" target=3D"_blank">http://www.cs.bu.edu/~goldbe</a></div>
</div>

--001a114ccbd40f479b052fc10468--


From nobody Tue Apr  5 11:48:56 2016
Return-Path: <sharon.goldbe@gmail.com>
X-Original-To: tictoc@ietfa.amsl.com
Delivered-To: tictoc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A1D6C12D58B for <tictoc@ietfa.amsl.com>; Tue,  5 Apr 2016 11:48:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.399
X-Spam-Level: 
X-Spam-Status: No, score=-2.399 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.199, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id K5LA4RIFr_I8 for <tictoc@ietfa.amsl.com>; Tue,  5 Apr 2016 11:48:53 -0700 (PDT)
Received: from mail-wm0-x22e.google.com (mail-wm0-x22e.google.com [IPv6:2a00:1450:400c:c09::22e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DDC2A12D11C for <tictoc@ietf.org>; Tue,  5 Apr 2016 11:48:51 -0700 (PDT)
Received: by mail-wm0-x22e.google.com with SMTP id n3so33467534wmn.0 for <tictoc@ietf.org>; Tue, 05 Apr 2016 11:48:51 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to; bh=uw1p0zf3XlV9r9Aw+xicvVIvojKe+llgtPjRu+ZV9Ls=; b=bt2pIx7jt6hvBCSb7yciOGy6TCsVcAJHAe488VIj5VIOnzX09pQCt/4FmS8ghfW8vb /u9o6Wugw5rA2yLF6BgQDbT8zIk/UjliplHnzB9ACuFj+9p5VoSUlX6MTAq+/Me6YZww mZah9Sm5tLLFmQ7csrjFhIzVTxwqUEulE+e8+wQE3Lmtp89m/Tq+NoPhTx83sppU6EST z2EI7d+/08/PQiXdtw+AC6+T9QDDBLHKStemzbMTTW9PFgdD4ZR1/WWntJVLFf1coVrs 588RyetZAc8zYf+nTayby1AUuRK5lwqhTrjyAZGOvhm29SUi06Q+8Pl4dQU95IlZ9QGj FLhQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to; bh=uw1p0zf3XlV9r9Aw+xicvVIvojKe+llgtPjRu+ZV9Ls=; b=AltmNCmSUfuwFUIHKTD/2drTP/bEbkDnFvZN3nOexfQAgM3cmIUNuJuDPS3Huml4Gp pPEnV0Ztl1on1/cKkCjmUPxB+xseCaWOBP8u/BjIvfKsP/y0/7yI3mn/1w3yFawWmHIA I6+miRNV9i70PsfhhCfaPxWu+KLM3WcyGoFWBP5QRWTuHnri6i3030LCVMnAGZRAk9vE gALrjtBzHBDNqhTZCFF3OubD6R5Hd2QsUrfZIDkqxI8pcGQnKPY79bv8v4JGydgssoq3 tMfjenvCzKRAoEl7aeNANasqM7aFqxb4THnRjvaAeX7RwWH1YL/684/e6vV7+JjMMFnv KTEA==
X-Gm-Message-State: AD7BkJLjMIS6qdfg5KOLLGVb3jMFJVwZ9iqhXGGqlykvrTBv1OpiOQKqzP1p/NMOf9bEGdYDcx3Mf4W3gDzlIQ==
X-Received: by 10.28.227.130 with SMTP id a124mr19633695wmh.2.1459881787023; Tue, 05 Apr 2016 11:43:07 -0700 (PDT)
MIME-Version: 1.0
Sender: sharon.goldbe@gmail.com
Received: by 10.194.71.200 with HTTP; Tue, 5 Apr 2016 11:42:27 -0700 (PDT)
In-Reply-To: <CAJHGrrQimUVqtRg6bowwBr5pxrSUh+mHkEzB0P1SBxP=nzczbg@mail.gmail.com>
References: <CAJHGrrQimUVqtRg6bowwBr5pxrSUh+mHkEzB0P1SBxP=nzczbg@mail.gmail.com>
From: Sharon Goldberg <goldbe@cs.bu.edu>
Date: Tue, 5 Apr 2016 14:42:27 -0400
X-Google-Sender-Auth: Kg8tIK5wcIehrB1W2IKSJlYeJHU
Message-ID: <CAJHGrrSBj19-12UY=GyYsx5FaaCqTSixaFdt0Sf=ELNL4DXUew@mail.gmail.com>
To: NTP Working Group <ntpwg@lists.ntp.org>, tictoc@ietf.org
Content-Type: multipart/alternative; boundary=001a114ccbd4546512052fc137f9
Archived-At: <http://mailarchive.ietf.org/arch/msg/tictoc/ZCrB_yVze_3WFVw5d8hG39jDm08>
Subject: Re: [TICTOC] comments on draft-stenn-ntp-suggest-refid-00
X-BeenThere: tictoc@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Timing over IP Connection and Transfer of Clock BOF <tictoc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tictoc>, <mailto:tictoc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tictoc/>
List-Post: <mailto:tictoc@ietf.org>
List-Help: <mailto:tictoc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tictoc>, <mailto:tictoc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 05 Apr 2016 18:48:56 -0000

--001a114ccbd4546512052fc137f9
Content-Type: text/plain; charset=UTF-8

All, just to summarize the conversation on meetcho just now. I think  that
this proposal would also solve the problem hashed IPv6 addresses colliding
with IPv4 addresses on the same network, which is addressed
in draft-stenn-ntp-ipv6-refid-hash-00.

Why? Because the only time a server will put an IP address in the refID
field is when it is responding to a query from *that specific IP*.  (Else,
it puts the "nonsense" value in the refID.)  So even if a collision
happens, it should not matter, since the only party to see the collision is
the IP that sent the query.

Sharon

On Tue, Apr 5, 2016 at 2:28 PM, Sharon Goldberg <goldbe@cs.bu.edu> wrote:

> Dear WG,
>
> To follow up on my comments on draft-stenn-ntp-suggest-refid-00 at the
> IETF'95 WG meeting just now. The current draft requires the use of an
> extension field.  I believe the goals of the draft can be accomplished
> without using an extension field, in a backwards compatible fashion.
>
> The goal of the draft is to limit the information exposed by the REFID
> while still preserving robustness to "length-1" timing loops where system A
> takes time from system B, but system B takes time from system A.
> This proposal allow system A to limit the info it leaks in its refID,
> without harming any of its legacy clients.
>
> Suppose system A is taking time from system B. Then there are two cases:
> 1) If A gets a time query from system B, A puts the IP of B in the refID
> of its response. This way, even a legacy B can tell it cannot take time
> from A because this would cause a timing loop.
>
> 2) If A gets a time query from system C, A puts a "nonsense" value in its
> refID.  Even a legacy C can see that its IP is not in the refID, and so it
> is allowed to take time from A.
>
> One question is what this "nonsense" value should be.  I think it should
> be a fixed value. For example 0.0.0.0.  We would not want a randomly-chosen
> value since this might collide with actual IP addresses on the network.
>
> Thanks,
> Sharon
>
>
> --
> Sharon Goldberg
> Computer Science, Boston University
> http://www.cs.bu.edu/~goldbe
>



-- 
Sharon Goldberg
Computer Science, Boston University
http://www.cs.bu.edu/~goldbe

--001a114ccbd4546512052fc137f9
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">All, just to summarize the conversation on meetcho just no=
w. I think =C2=A0that this proposal would also solve the problem hashed IPv=
6 addresses colliding with IPv4 addresses on the same network, which is add=
ressed in=C2=A0draft-stenn-ntp-ipv6-refid-hash-00.<div><br></div><div>Why? =
Because the only time a server will put an IP address in the refID field is=
 when it is responding to a query from *that specific IP*. =C2=A0(Else, it =
puts the &quot;nonsense&quot; value in the refID.) =C2=A0So even if a colli=
sion happens, it should not matter, since the only party to see the collisi=
on is the IP that sent the query.</div><div><br></div><div>Sharon</div><div=
 class=3D"gmail_extra"><br><div class=3D"gmail_quote">On Tue, Apr 5, 2016 a=
t 2:28 PM, Sharon Goldberg <span dir=3D"ltr">&lt;<a href=3D"mailto:goldbe@c=
s.bu.edu" target=3D"_blank">goldbe@cs.bu.edu</a>&gt;</span> wrote:<br><bloc=
kquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #cc=
c solid;padding-left:1ex"><div dir=3D"ltr"><div>Dear WG,</div><div><br></di=
v><div>To follow up on my comments on draft-stenn-ntp-suggest-refid-00 at t=
he IETF&#39;95 WG meeting just now. The current draft requires the use of a=
n extension field.=C2=A0 I believe the goals of the draft can be accomplish=
ed without using an extension field, in a backwards compatible fashion.</di=
v><div><br></div><div>The goal of the draft is to limit the information exp=
osed by the REFID while still preserving robustness to &quot;length-1&quot;=
 timing loops where system A takes time from system B, but system B takes t=
ime from system A. =C2=A0</div><div>This proposal allow system A to limit t=
he info it leaks in its refID, without harming any of its legacy clients.=
=C2=A0</div><div><br></div><div>Suppose system A is taking time from system=
 B. Then there are two cases:</div><div>1) If A gets a time query from syst=
em B, A puts the IP of B in the refID of its response. This way, even a leg=
acy B can tell it cannot take time from A because this would cause a timing=
 loop.</div><div><br></div><div>2) If A gets a time query from system C, A =
puts a &quot;nonsense&quot; value in its refID.=C2=A0 Even a legacy C can s=
ee that its IP is not in the refID, and so it is allowed to take time from =
A.=C2=A0</div><div><br></div><div>One question is what this &quot;nonsense&=
quot; value should be.=C2=A0 I think it should be a fixed value. For exampl=
e 0.0.0.0.=C2=A0 We would not want a randomly-chosen value since this might=
 collide with actual IP addresses on the network.</div><div><br></div><div>=
Thanks,</div><div>Sharon</div><span><font color=3D"#888888"><div><br></div>=
<div><br></div>-- <br><div>Sharon Goldberg<br>Computer Science, Boston Univ=
ersity<br><a href=3D"http://www.cs.bu.edu/~goldbe" target=3D"_blank">http:/=
/www.cs.bu.edu/~goldbe</a></div>
</font></span></div>
</blockquote></div><br><br clear=3D"all"><div><br></div>-- <br><div>Sharon =
Goldberg<br>Computer Science, Boston University<br><a href=3D"http://www.cs=
.bu.edu/~goldbe" target=3D"_blank">http://www.cs.bu.edu/~goldbe</a></div>
</div></div>

--001a114ccbd4546512052fc137f9--


From nobody Tue Apr  5 12:00:35 2016
Return-Path: <mayer@pdmconsulting.net>
X-Original-To: tictoc@ietfa.amsl.com
Delivered-To: tictoc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5BE5712DA41 for <tictoc@ietfa.amsl.com>; Tue,  5 Apr 2016 12:00:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3Z-vptTR_SZ5 for <tictoc@ietfa.amsl.com>; Tue,  5 Apr 2016 12:00:32 -0700 (PDT)
Received: from chessie.everett.org (chessie.everett.org [66.220.13.234]) by ietfa.amsl.com (Postfix) with ESMTP id 06D6C12D9C1 for <tictoc@ietf.org>; Tue,  5 Apr 2016 12:00:22 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by chessie.everett.org (Postfix) with SMTP id 6E202B833 for <tictoc@ietf.org>; Tue,  5 Apr 2016 19:00:22 +0000 (UTC)
Received: from [10.2.64.150] (unknown [198.22.153.36]) by chessie.everett.org (Postfix) with ESMTPSA id 261CDB82B; Tue,  5 Apr 2016 19:00:21 +0000 (UTC)
References: <CAJHGrrQimUVqtRg6bowwBr5pxrSUh+mHkEzB0P1SBxP=nzczbg@mail.gmail.com>
To: Sharon Goldberg <goldbe@cs.bu.edu>, NTP Working Group <ntpwg@lists.ntp.org>, tictoc@ietf.org
From: Danny Mayer <mayer@pdmconsulting.net>
Message-ID: <57040B4A.4090301@pdmconsulting.net>
Date: Tue, 5 Apr 2016 15:00:26 -0400
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.7.0
MIME-Version: 1.0
In-Reply-To: <CAJHGrrQimUVqtRg6bowwBr5pxrSUh+mHkEzB0P1SBxP=nzczbg@mail.gmail.com>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 8bit
X-DSPAM-Result: Innocent
X-DSPAM-Processed: Tue Apr  5 19:00:22 2016
X-DSPAM-Confidence: 0.9899
X-DSPAM-Probability: 0.0000
X-DSPAM-Signature: 7205,57040b46829931973780240
Archived-At: <http://mailarchive.ietf.org/arch/msg/tictoc/dh1bMdi6ckhi9rWBYml1C7bMT5Y>
Subject: Re: [TICTOC] comments on draft-stenn-ntp-suggest-refid-00
X-BeenThere: tictoc@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
Reply-To: mayer@pdmconsulting.net
List-Id: Timing over IP Connection and Transfer of Clock BOF <tictoc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tictoc>, <mailto:tictoc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tictoc/>
List-Post: <mailto:tictoc@ietf.org>
List-Help: <mailto:tictoc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tictoc>, <mailto:tictoc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 05 Apr 2016 19:00:34 -0000

On 4/5/2016 2:28 PM, Sharon Goldberg wrote:
> Dear WG,
> 
> To follow up on my comments on draft-stenn-ntp-suggest-refid-00 at the
> IETF'95 WG meeting just now. The current draft requires the use of an
> extension field.Â  I believe the goals of the draft can be accomplished
> without using an extension field, in a backwards compatible fashion.
> 
> The goal of the draft is to limit the information exposed by the REFID
> while still preserving robustness to "length-1" timing loops where
> system A takes time from system B, but system B takes time from system A. Â 
> This proposal allow system A to limit the info it leaks in its refID,
> without harming any of its legacy clients.Â 
> 
> Suppose system A is taking time from system B. Then there are two cases:
> 1) If A gets a time query from system B, A puts the IP of B in the refID
> of its response. This way, even a legacy B can tell it cannot take time
> from A because this would cause a timing loop.
> 
> 2) If A gets a time query from system C, A puts a "nonsense" value in
> its refID.Â  Even a legacy C can see that its IP is not in the refID,
> and so it is allowed to take time from A.Â 
> 
> One question is what this "nonsense" value should be.Â  I think it
> should be a fixed value. For example 0.0.0.0.Â  We would not want a
> randomly-chosen value since this might collide with actual IP addresses
> on the network.
> 
> Thanks,
> Sharon

The problem that I was alluding to in the jabber room is this. I'll keep
the problem simple and to one example.

A takes its time from B over an IPv4 address. A then gets a time query
from C over IPv6. How does it know if B and C are the same system or
different system? A has no information about that.

Is this clearer?

Danny




From nobody Tue Apr  5 12:01:20 2016
Return-Path: <mayer@ntp.org>
X-Original-To: tictoc@ietfa.amsl.com
Delivered-To: tictoc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0956712DA2F for <tictoc@ietfa.amsl.com>; Tue,  5 Apr 2016 12:01:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8JNkhoJ7a39Z for <tictoc@ietfa.amsl.com>; Tue,  5 Apr 2016 12:01:18 -0700 (PDT)
Received: from chessie.everett.org (chessie.everett.org [66.220.13.234]) by ietfa.amsl.com (Postfix) with ESMTP id 3087F12DA85 for <tictoc@ietf.org>; Tue,  5 Apr 2016 12:00:58 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by chessie.everett.org (Postfix) with SMTP id E1D41B80E for <tictoc@ietf.org>; Tue,  5 Apr 2016 19:00:57 +0000 (UTC)
Received: from [10.2.64.150] (unknown [198.22.153.36]) by chessie.everett.org (Postfix) with ESMTPSA id 9656EB82B; Tue,  5 Apr 2016 19:00:56 +0000 (UTC)
From: Danny Mayer <mayer@ntp.org>
References: <CAJHGrrQimUVqtRg6bowwBr5pxrSUh+mHkEzB0P1SBxP=nzczbg@mail.gmail.com>
To: Sharon Goldberg <goldbe@cs.bu.edu>, NTP Working Group <ntpwg@lists.ntp.org>, tictoc@ietf.org
Message-ID: <57040B6E.6070104@ntp.org>
Date: Tue, 5 Apr 2016 15:01:02 -0400
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.7.0
MIME-Version: 1.0
In-Reply-To: <CAJHGrrQimUVqtRg6bowwBr5pxrSUh+mHkEzB0P1SBxP=nzczbg@mail.gmail.com>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 8bit
X-DSPAM-Result: Innocent
X-DSPAM-Processed: Tue Apr  5 19:00:57 2016
X-DSPAM-Confidence: 0.9899
X-DSPAM-Probability: 0.0000
X-DSPAM-Signature: 7205,57040b69829937125911628
Archived-At: <http://mailarchive.ietf.org/arch/msg/tictoc/NFzo8gYGyLXTAvQP6pRbo2T-Ano>
Subject: Re: [TICTOC] comments on draft-stenn-ntp-suggest-refid-00
X-BeenThere: tictoc@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Timing over IP Connection and Transfer of Clock BOF <tictoc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tictoc>, <mailto:tictoc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tictoc/>
List-Post: <mailto:tictoc@ietf.org>
List-Help: <mailto:tictoc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tictoc>, <mailto:tictoc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 05 Apr 2016 19:01:20 -0000

On 4/5/2016 2:28 PM, Sharon Goldberg wrote:
> Dear WG,
> 
> To follow up on my comments on draft-stenn-ntp-suggest-refid-00 at the
> IETF'95 WG meeting just now. The current draft requires the use of an
> extension field.Â  I believe the goals of the draft can be accomplished
> without using an extension field, in a backwards compatible fashion.
> 
> The goal of the draft is to limit the information exposed by the REFID
> while still preserving robustness to "length-1" timing loops where
> system A takes time from system B, but system B takes time from system A. Â 
> This proposal allow system A to limit the info it leaks in its refID,
> without harming any of its legacy clients.Â 
> 
> Suppose system A is taking time from system B. Then there are two cases:
> 1) If A gets a time query from system B, A puts the IP of B in the refID
> of its response. This way, even a legacy B can tell it cannot take time
> from A because this would cause a timing loop.
> 
> 2) If A gets a time query from system C, A puts a "nonsense" value in
> its refID.Â  Even a legacy C can see that its IP is not in the refID,
> and so it is allowed to take time from A.Â 
> 
> One question is what this "nonsense" value should be.Â  I think it
> should be a fixed value. For example 0.0.0.0.Â  We would not want a
> randomly-chosen value since this might collide with actual IP addresses
> on the network.
> 
> Thanks,
> Sharon

The problem that I was alluding to in the jabber room is this. I'll keep
the problem simple and to one example.

A takes its time from B over an IPv4 address. A then gets a time query
from C over IPv6. How does it know if B and C are the same system or
different system? A has no information about that.

Is this clearer?

Danny




From nobody Tue Apr  5 12:13:35 2016
Return-Path: <stenn@stenn.ntp.org>
X-Original-To: tictoc@ietfa.amsl.com
Delivered-To: tictoc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4DAA912D175 for <tictoc@ietfa.amsl.com>; Tue,  5 Apr 2016 12:13:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level: 
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YQ_HTow6QgZN for <tictoc@ietfa.amsl.com>; Tue,  5 Apr 2016 12:13:33 -0700 (PDT)
Received: from stenn.ntp.org (stenn.ntp.org [149.20.68.30]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A514A12D18E for <tictoc@ietf.org>; Tue,  5 Apr 2016 12:13:32 -0700 (PDT)
Received: from [::1] (helo=stenn.ntp.org) by stenn.ntp.org with esmtp (Exim 4.86_2 (FreeBSD)) (envelope-from <stenn@stenn.ntp.org>) id 1anWOe-0002gM-Gb; Tue, 05 Apr 2016 19:12:16 +0000
From: Harlan Stenn <stenn@ntp.org>
To: Sharon Goldberg <goldbe@cs.bu.edu>
In-reply-to: <CAJHGrrQimUVqtRg6bowwBr5pxrSUh+mHkEzB0P1SBxP=nzczbg@mail.gmail.com>
References: <CAJHGrrQimUVqtRg6bowwBr5pxrSUh+mHkEzB0P1SBxP=nzczbg@mail.gmail.com>
Comments: In-reply-to Sharon Goldberg <goldbe@cs.bu.edu> message dated "Tue, 05 Apr 2016 14:28:07 -0400."
X-Mailer: MH-E 7.4.2; nmh 1.6; XEmacs 21.4 (patch 24)
Mime-Version: 1.0 (generated by tm-edit 1.8)
Content-Type: text/plain; charset=US-ASCII
Date: Tue, 05 Apr 2016 19:12:16 +0000
Message-Id: <E1anWOe-0002gM-Gb@stenn.ntp.org>
Archived-At: <http://mailarchive.ietf.org/arch/msg/tictoc/2_Qoi6Hy_vVn-CTwDPj-OErQ1ew>
Cc: NTP Working Group <ntpwg@lists.ntp.org>, tictoc@ietf.org
Subject: Re: [TICTOC] [ntpwg] comments on draft-stenn-ntp-suggest-refid-00
X-BeenThere: tictoc@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Timing over IP Connection and Transfer of Clock BOF <tictoc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tictoc>, <mailto:tictoc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tictoc/>
List-Post: <mailto:tictoc@ietf.org>
List-Help: <mailto:tictoc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tictoc>, <mailto:tictoc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 05 Apr 2016 19:13:34 -0000

Sharon Goldberg writes:
> To follow up on my comments on draft-stenn-ntp-suggest-refid-00 at the
> IETF'95 WG meeting just now. The current draft requires the use of an
> extension field.  I believe the goals of the draft can be accomplished
> without using an extension field, in a backwards compatible fashion.
> 
> The goal of the draft is to limit the information exposed by the REFID
> while still preserving robustness to "length-1" timing loops where system A
> takes time from system B, but system B takes time from system A.
> This proposal allow system A to limit the info it leaks in its refID,
> without harming any of its legacy clients.
> 
> Suppose system A is taking time from system B. Then there are two cases:
> 1) If A gets a time query from system B, A puts the IP of B in the refID of
> its response. This way, even a legacy B can tell it cannot take time from A
> because this would cause a timing loop.
> 
> 2) If A gets a time query from system C, A puts a "nonsense" value in its
> refID.  Even a legacy C can see that its IP is not in the refID, and so it
> is allowed to take time from A.
> 
> One question is what this "nonsense" value should be.  I think it should be
> a fixed value. For example 0.0.0.0.  We would not want a randomly-chosen
> value since this might collide with actual IP addresses on the network.

I think your proposal will usually work.

There is a potential problem in that A does not have complete
information about what B and C are doing.  It may be that B and C are
effectively the same machine/source of time, and that B and C would look
at the REFID returned by A and decide that there is a timing loop if A
is getting its time from B and C (which is also effectively B) is
considering using A for time.

If we're going for a strictly clean paradigm here we need to note this.

H


From nobody Tue Apr  5 12:22:27 2016
Return-Path: <sharon.goldbe@gmail.com>
X-Original-To: tictoc@ietfa.amsl.com
Delivered-To: tictoc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6469C12D6C3 for <tictoc@ietfa.amsl.com>; Tue,  5 Apr 2016 12:22:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.399
X-Spam-Level: 
X-Spam-Status: No, score=-2.399 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.199, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id D4DLaHs2JSXT for <tictoc@ietfa.amsl.com>; Tue,  5 Apr 2016 12:22:23 -0700 (PDT)
Received: from mail-wm0-x230.google.com (mail-wm0-x230.google.com [IPv6:2a00:1450:400c:c09::230]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9929A12D18E for <tictoc@ietf.org>; Tue,  5 Apr 2016 12:22:19 -0700 (PDT)
Received: by mail-wm0-x230.google.com with SMTP id f198so44977049wme.0 for <tictoc@ietf.org>; Tue, 05 Apr 2016 12:22:19 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=9hleVfag85qhXGKAu3o7Qtdl2XTetRsfDp4W7I2eGDI=; b=Yeu5nX87HBFkP2NJdLs2DGHkliSm2FKcqk4gp8lrTefgp1Cx1s7sN+TlqVj5tOsLJF WPtjR/9hk9Hw0Ix5UFdAi7lTI050jE+azHRX+IA6G842GBFrufS8IXQuGtFB1l0Tubtl l38DlTJSKxA7VxO4BshxM9yW7Z8XCipKPDPNMOXcor+b0IwPqPHmV5uCI7teD174MHoU enSQvlUeKCcvQW6chBxsc00pDZ87q4zTzM848hvpI2+Eve1iLrgBspOBo2n0kRHP+msE gcYdz+OShjBWxq+u9XvIblnl46qce6XN5g3wnU+jl1mIvjY4IqT/a4I7ggyRnYjHbBV2 p3og==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=9hleVfag85qhXGKAu3o7Qtdl2XTetRsfDp4W7I2eGDI=; b=HVsvIjVBYTJX+cKBByPNmXNwuvhKXOEpKhq4OcNT+nBfwJNSEfvTApFf8ufkWFRLt3 QV0Idp3+NNqAmtPFUIp8O7KLr9KBgbn5bVMdne7OyRbIu3h3wfZW//5mCMSOqOcK4tdK 8mKMguVPrCPFCE3X7zoZqusb/A8r7Y+WdrJ5z+aItH7GtfdN2zGeTi+TmlTu02BBrpnH nkQacVbASug3Tvs0NOmNpqDSWxqVKai/2Cl7phNbITkkWq4BLsXS6OIrjlvGJ+IExaJE /Hohe2NnB5flPJed7HlbO4X42c+BB6mETRoVyht/ZwSPxWwknZC+jNSIPsXtuYOrT/9s CbjQ==
X-Gm-Message-State: AD7BkJISy3x159daCJiRHzF4/fMstw+LsxWizj8OwE0ilnNXt8Ydaxo5QUwjfmSQuGTxp9Wz0sp1mXcfp6ouDQ==
X-Received: by 10.194.178.233 with SMTP id db9mr7949956wjc.11.1459884115715; Tue, 05 Apr 2016 12:21:55 -0700 (PDT)
MIME-Version: 1.0
Sender: sharon.goldbe@gmail.com
Received: by 10.194.71.200 with HTTP; Tue, 5 Apr 2016 12:21:16 -0700 (PDT)
In-Reply-To: <57040B4A.4090301@pdmconsulting.net>
References: <CAJHGrrQimUVqtRg6bowwBr5pxrSUh+mHkEzB0P1SBxP=nzczbg@mail.gmail.com> <57040B4A.4090301@pdmconsulting.net>
From: Sharon Goldberg <goldbe@cs.bu.edu>
Date: Tue, 5 Apr 2016 15:21:16 -0400
X-Google-Sender-Auth: QgRpElxPujsqj12odFgLdtL1RyU
Message-ID: <CAJHGrrSSD7o6Hy_3e8dNTOSTYF5MkyGo-Bn5SqHxa87XWqFpHQ@mail.gmail.com>
To: mayer@pdmconsulting.net
Content-Type: multipart/alternative; boundary=089e013d1a08216ac4052fc1c2b2
Archived-At: <http://mailarchive.ietf.org/arch/msg/tictoc/3Lf5zM1WUepuEmnG_aVk5HpYs8I>
Cc: NTP Working Group <ntpwg@lists.ntp.org>, tictoc@ietf.org
Subject: Re: [TICTOC] comments on draft-stenn-ntp-suggest-refid-00
X-BeenThere: tictoc@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Timing over IP Connection and Transfer of Clock BOF <tictoc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tictoc>, <mailto:tictoc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tictoc/>
List-Post: <mailto:tictoc@ietf.org>
List-Help: <mailto:tictoc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tictoc>, <mailto:tictoc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 05 Apr 2016 19:22:25 -0000

--089e013d1a08216ac4052fc1c2b2
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

On Tue, Apr 5, 2016 at 3:00 PM, Danny Mayer <mayer@pdmconsulting.net> wrote=
:

> On 4/5/2016 2:28 PM, Sharon Goldberg wrote:
> > Dear WG,
> >
> > To follow up on my comments on draft-stenn-ntp-suggest-refid-00 at the
> > IETF'95 WG meeting just now. The current draft requires the use of an
> > extension field.=C3=82  I believe the goals of the draft can be accompl=
ished
> > without using an extension field, in a backwards compatible fashion.
> >
> > The goal of the draft is to limit the information exposed by the REFID
> > while still preserving robustness to "length-1" timing loops where
> > system A takes time from system B, but system B takes time from system
> A. =C3=82
> > This proposal allow system A to limit the info it leaks in its refID,
> > without harming any of its legacy clients.=C3=82
> >
> > Suppose system A is taking time from system B. Then there are two cases=
:
> > 1) If A gets a time query from system B, A puts the IP of B in the refI=
D
> > of its response. This way, even a legacy B can tell it cannot take time
> > from A because this would cause a timing loop.
> >
> > 2) If A gets a time query from system C, A puts a "nonsense" value in
> > its refID.=C3=82  Even a legacy C can see that its IP is not in the ref=
ID,
> > and so it is allowed to take time from A.=C3=82
> >
> > One question is what this "nonsense" value should be.=C3=82  I think it
> > should be a fixed value. For example 0.0.0.0.=C3=82  We would not want =
a
> > randomly-chosen value since this might collide with actual IP addresses
> > on the network.
> >
> > Thanks,
> > Sharon
>
> The problem that I was alluding to in the jabber room is this. I'll keep
> the problem simple and to one example.
>
> A takes its time from B over an IPv4 address. A then gets a time query
> from C over IPv6. How does it know if B and C are the same system or
> different system? A has no information about that.
>
> Is this clearer?
>
> Yes, it's clear. How does the current ntpd implementation deal with this
problem?

Sharon



--=20
Sharon Goldberg
Computer Science, Boston University
http://www.cs.bu.edu/~goldbe

--089e013d1a08216ac4052fc1c2b2
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote">On T=
ue, Apr 5, 2016 at 3:00 PM, Danny Mayer <span dir=3D"ltr">&lt;<a href=3D"ma=
ilto:mayer@pdmconsulting.net" target=3D"_blank">mayer@pdmconsulting.net</a>=
&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0=
 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class=3D"">On 4/=
5/2016 2:28 PM, Sharon Goldberg wrote:<br>
&gt; Dear WG,<br>
&gt;<br>
&gt; To follow up on my comments on draft-stenn-ntp-suggest-refid-00 at the=
<br>
&gt; IETF&#39;95 WG meeting just now. The current draft requires the use of=
 an<br>
</span>&gt; extension field.=C3=82=C2=A0 I believe the goals of the draft c=
an be accomplished<br>
<span class=3D"">&gt; without using an extension field, in a backwards comp=
atible fashion.<br>
&gt;<br>
&gt; The goal of the draft is to limit the information exposed by the REFID=
<br>
&gt; while still preserving robustness to &quot;length-1&quot; timing loops=
 where<br>
</span>&gt; system A takes time from system B, but system B takes time from=
 system A. =C3=82<br>
<span class=3D"">&gt; This proposal allow system A to limit the info it lea=
ks in its refID,<br>
</span>&gt; without harming any of its legacy clients.=C3=82<br>
<span class=3D"">&gt;<br>
&gt; Suppose system A is taking time from system B. Then there are two case=
s:<br>
&gt; 1) If A gets a time query from system B, A puts the IP of B in the ref=
ID<br>
&gt; of its response. This way, even a legacy B can tell it cannot take tim=
e<br>
&gt; from A because this would cause a timing loop.<br>
&gt;<br>
&gt; 2) If A gets a time query from system C, A puts a &quot;nonsense&quot;=
 value in<br>
</span>&gt; its refID.=C3=82=C2=A0 Even a legacy C can see that its IP is n=
ot in the refID,<br>
&gt; and so it is allowed to take time from A.=C3=82<br>
&gt;<br>
&gt; One question is what this &quot;nonsense&quot; value should be.=C3=82=
=C2=A0 I think it<br>
&gt; should be a fixed value. For example 0.0.0.0.=C3=82=C2=A0 We would not=
 want a<br>
<span class=3D"">&gt; randomly-chosen value since this might collide with a=
ctual IP addresses<br>
&gt; on the network.<br>
&gt;<br>
&gt; Thanks,<br>
&gt; Sharon<br>
<br>
</span>The problem that I was alluding to in the jabber room is this. I&#39=
;ll keep<br>
the problem simple and to one example.<br>
<br>
A takes its time from B over an IPv4 address. A then gets a time query<br>
from C over IPv6. How does it know if B and C are the same system or<br>
different system? A has no information about that.<br>
<br>
Is this clearer?<br><span class=3D"HOEnZb"><font color=3D"#888888"><br></fo=
nt></span></blockquote><div>Yes, it&#39;s clear. How does the current ntpd =
implementation deal with this problem? =C2=A0<br></div><div><br></div><div>=
Sharon</div></div><br><br clear=3D"all"><div><br></div>-- <br><div class=3D=
"gmail_signature">Sharon Goldberg<br>Computer Science, Boston University<br=
><a href=3D"http://www.cs.bu.edu/~goldbe" target=3D"_blank">http://www.cs.b=
u.edu/~goldbe</a></div>
</div></div>

--089e013d1a08216ac4052fc1c2b2--


From nobody Tue Apr  5 12:27:59 2016
Return-Path: <mayer@ntp.org>
X-Original-To: tictoc@ietfa.amsl.com
Delivered-To: tictoc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4E84312D174 for <tictoc@ietfa.amsl.com>; Tue,  5 Apr 2016 12:27:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level: 
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GoEBvc-MjpIp for <tictoc@ietfa.amsl.com>; Tue,  5 Apr 2016 12:27:55 -0700 (PDT)
Received: from mail1.ntp.org (mail1.ntp.org [IPv6:2001:4f8:fff7:1::5]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8EF3412D135 for <tictoc@ietf.org>; Tue,  5 Apr 2016 12:27:55 -0700 (PDT)
Received: from [198.22.153.36] (helo=[10.2.64.150]) by mail1.ntp.org with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.77 (FreeBSD)) (envelope-from <mayer@ntp.org>) id 1anWdm-000AeB-AI; Tue, 05 Apr 2016 19:27:55 +0000
References: <CAJHGrrQimUVqtRg6bowwBr5pxrSUh+mHkEzB0P1SBxP=nzczbg@mail.gmail.com> <57040B4A.4090301@pdmconsulting.net> <CAJHGrrSSD7o6Hy_3e8dNTOSTYF5MkyGo-Bn5SqHxa87XWqFpHQ@mail.gmail.com>
To: Sharon Goldberg <goldbe@cs.bu.edu>
From: Danny Mayer <mayer@ntp.org>
Organization: NTP
Message-ID: <570411C0.7000004@ntp.org>
Date: Tue, 5 Apr 2016 15:28:00 -0400
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.7.0
MIME-Version: 1.0
In-Reply-To: <CAJHGrrSSD7o6Hy_3e8dNTOSTYF5MkyGo-Bn5SqHxa87XWqFpHQ@mail.gmail.com>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 8bit
X-SA-Exim-Connect-IP: 198.22.153.36
X-SA-Exim-Rcpt-To: tictoc@ietf.org, ntpwg@lists.ntp.org, goldbe@cs.bu.edu
X-SA-Exim-Mail-From: mayer@ntp.org
X-SA-Exim-Version: 4.2
X-SA-Exim-Scanned: Yes (on mail1.ntp.org)
Archived-At: <http://mailarchive.ietf.org/arch/msg/tictoc/XyLedB-78sm4Ig4czC5KHBiHh-Y>
Cc: NTP Working Group <ntpwg@lists.ntp.org>, tictoc@ietf.org
Subject: Re: [TICTOC] comments on draft-stenn-ntp-suggest-refid-00
X-BeenThere: tictoc@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
Reply-To: mayer@ntp.org
List-Id: Timing over IP Connection and Transfer of Clock BOF <tictoc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tictoc>, <mailto:tictoc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tictoc/>
List-Post: <mailto:tictoc@ietf.org>
List-Help: <mailto:tictoc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tictoc>, <mailto:tictoc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 05 Apr 2016 19:27:57 -0000

On 4/5/2016 3:21 PM, Sharon Goldberg wrote:
> On Tue, Apr 5, 2016 at 3:00 PM, Danny Mayer <mayer@pdmconsulting.net
> <mailto:mayer@pdmconsulting.net>> wrote:
> 
>     On 4/5/2016 2:28 PM, Sharon Goldberg wrote:
>     > Dear WG,
>     >
>     > To follow up on my comments on draft-stenn-ntp-suggest-refid-00 at the
>     > IETF'95 WG meeting just now. The current draft requires the use of an
>     > extension field.Ã‚Â  I believe the goals of the draft can be
>     accomplished
>     > without using an extension field, in a backwards compatible fashion.
>     >
>     > The goal of the draft is to limit the information exposed by the REFID
>     > while still preserving robustness to "length-1" timing loops where
>     > system A takes time from system B, but system B takes time from
>     system A. Ã‚
>     > This proposal allow system A to limit the info it leaks in its refID,
>     > without harming any of its legacy clients.Ã‚
>     >
>     > Suppose system A is taking time from system B. Then there are two cases:
>     > 1) If A gets a time query from system B, A puts the IP of B in the refID
>     > of its response. This way, even a legacy B can tell it cannot take time
>     > from A because this would cause a timing loop.
>     >
>     > 2) If A gets a time query from system C, A puts a "nonsense" value in
>     > its refID.Ã‚Â  Even a legacy C can see that its IP is not in the
>     refID,
>     > and so it is allowed to take time from A.Ã‚
>     >
>     > One question is what this "nonsense" value should be.Ã‚Â  I think it
>     > should be a fixed value. For example 0.0.0.0.Ã‚Â  We would not want a
>     > randomly-chosen value since this might collide with actual IP addresses
>     > on the network.
>     >
>     > Thanks,
>     > Sharon
> 
>     The problem that I was alluding to in the jabber room is this. I'll keep
>     the problem simple and to one example.
> 
>     A takes its time from B over an IPv4 address. A then gets a time query
>     from C over IPv6. How does it know if B and C are the same system or
>     different system? A has no information about that.
> 
>     Is this clearer?
> 
> Yes, it's clear. How does the current ntpd implementation deal with this
> problem? Â 
> 

Currently it doesn't. One of my proposals is for each system to generate
a RefID and use that for all interfaces. I'm not sure if that works for
all cases or causes other issues.

Danny


From nobody Tue Apr  5 13:55:24 2016
Return-Path: <sharon.goldbe@gmail.com>
X-Original-To: tictoc@ietfa.amsl.com
Delivered-To: tictoc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3063512DA00 for <tictoc@ietfa.amsl.com>; Tue,  5 Apr 2016 13:55:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.399
X-Spam-Level: 
X-Spam-Status: No, score=-2.399 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.199, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id oBPgjnFLxicu for <tictoc@ietfa.amsl.com>; Tue,  5 Apr 2016 13:55:21 -0700 (PDT)
Received: from mail-wm0-x22d.google.com (mail-wm0-x22d.google.com [IPv6:2a00:1450:400c:c09::22d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DE0F912D9FA for <tictoc@ietf.org>; Tue,  5 Apr 2016 13:55:17 -0700 (PDT)
Received: by mail-wm0-x22d.google.com with SMTP id v188so1994207wme.1 for <tictoc@ietf.org>; Tue, 05 Apr 2016 13:55:17 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=klaq/yRkt2DLZEm233NvVly7pKO8XhOKtmMdPBO5zBY=; b=ZqfaASDonfx01f5Ip54nJCPjwP7S9vA/vTGGoC5SYDZnNt/FJIkzU4KalZ1lGxD3MX /mjgc+yPyzAyoNuQv4KekpL8fB8ONrIyeF/QWfQylP9vRZTX8z22VxxH44n+UWcU4rBn 6/HDsf3rZa9I3jDlAskGz2Cn9UrzKl2xjGtIFxtN/HqhZ2cQedeFddBSlZIvDApwl+MG m88/UBRiFgfKnXoZuQao9ZOTXcfiDKZ9pkaXH8XC0VghaIPiPukI53UnC8pe/KBktkL7 ToW6siua+5ypWeF1MIHEoEKMieTikIcimvJS9XhcUqZaI6Ju5s7Hn6uXOHMffkhECJq+ xtVw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=klaq/yRkt2DLZEm233NvVly7pKO8XhOKtmMdPBO5zBY=; b=GeSpHhL3r9GQYwDGGSo51svxWweLyrekKJbJdkLxp10mX+zmvCYZSjl5oVdMjLPh+I M2O5fInAY/cDehAIlO6LNW1Y01pRNjXubvX8aQk0mCQ1eJ/g6sPaZd6jTjfIZTGBc/9G RW4zlQthaO7+S5eytjZVmxS+6dYzBUdoxUwlmNsX+cPMbqktUR4ckf/5Qh1v88/BnL8L eMPGaQMvm5Uigi/tql2OhtjZ445fBHmDZqyAwlvPafzPCBiCuWV+VNLPFQ1Sh5CaMZK2 6pwGU8Z2hFAJei7BB0gKJ7U10lSfO3/44dF4B3Oafs+Vrp9br/9RLfsInxVCUdby97op qg3Q==
X-Gm-Message-State: AD7BkJJAN6sUivMt9l1JPldcrqQ9Ds/MJHstCo3pdIj51wC0kYrfgMQqL5+bCn6fiNVKNmOlcm3uNPqcxGbeAQ==
X-Received: by 10.28.60.197 with SMTP id j188mr10497047wma.68.1459889697424; Tue, 05 Apr 2016 13:54:57 -0700 (PDT)
MIME-Version: 1.0
Sender: sharon.goldbe@gmail.com
Received: by 10.194.71.200 with HTTP; Tue, 5 Apr 2016 13:54:17 -0700 (PDT)
In-Reply-To: <570411C0.7000004@ntp.org>
References: <CAJHGrrQimUVqtRg6bowwBr5pxrSUh+mHkEzB0P1SBxP=nzczbg@mail.gmail.com> <57040B4A.4090301@pdmconsulting.net> <CAJHGrrSSD7o6Hy_3e8dNTOSTYF5MkyGo-Bn5SqHxa87XWqFpHQ@mail.gmail.com> <570411C0.7000004@ntp.org>
From: Sharon Goldberg <goldbe@cs.bu.edu>
Date: Tue, 5 Apr 2016 16:54:17 -0400
X-Google-Sender-Auth: ouBxwbUZh5kgTYsDCY2JpF8KUPg
Message-ID: <CAJHGrrR=-uN7dD5S0hBnF3Mt9ZrO8dC5YJK9k+D8j+WBFvByRg@mail.gmail.com>
To: "Danny Mayer (mayer@ntp.org)" <mayer@ntp.org>
Content-Type: multipart/alternative; boundary=001a1148f200d3bc85052fc30e3b
Archived-At: <http://mailarchive.ietf.org/arch/msg/tictoc/20LmFC3JspbzJ46N9h4kDsxuXNo>
Cc: NTP Working Group <ntpwg@lists.ntp.org>, tictoc@ietf.org
Subject: Re: [TICTOC] comments on draft-stenn-ntp-suggest-refid-00
X-BeenThere: tictoc@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Timing over IP Connection and Transfer of Clock BOF <tictoc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tictoc>, <mailto:tictoc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tictoc/>
List-Post: <mailto:tictoc@ietf.org>
List-Help: <mailto:tictoc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tictoc>, <mailto:tictoc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 05 Apr 2016 20:55:24 -0000

--001a1148f200d3bc85052fc30e3b
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

>
> >     The problem that I was alluding to in the jabber room is this. I'll
> keep
> >     the problem simple and to one example.
> >
> >     A takes its time from B over an IPv4 address. A then gets a time
> query
> >     from C over IPv6. How does it know if B and C are the same system o=
r
> >     different system? A has no information about that.
> >
> >     Is this clearer?
> >
> > Yes, it's clear. How does the current ntpd implementation deal with thi=
s
> > problem? =C3=82
> >
>
> Currently it doesn't. One of my proposals is for each system to generate
> a RefID and use that for all interfaces. I'm not sure if that works for
> all cases or causes other issues.
>

OK. To clarify: you are proposing an extension to NTP where a server that
has multiple IP addresses can choose a special value as its refID, and
communicate that to its clients.  Then, if the clients choose to take time
from that server, they put that special value in as their refID, instead of
an IP address.

AFAIK this functionality is not part of NTP today, right? It would probably
require an extension field? Also its not backwards compatible, since a
server that chooses to do this would need to make sure that its clients
understand what it is doing. And currently clients don't know how to do
this, right?

Please clarify if I have misunderstood.

--=20
Sharon Goldberg
Computer Science, Boston University
http://www.cs.bu.edu/~goldbe

--001a1148f200d3bc85052fc30e3b
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote"><blo=
ckquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #c=
cc solid;padding-left:1ex"><span class=3D"">&gt;=C2=A0 =C2=A0 =C2=A0The pro=
blem that I was alluding to in the jabber room is this. I&#39;ll keep<br>
&gt;=C2=A0 =C2=A0 =C2=A0the problem simple and to one example.<br>
&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0A takes its time from B over an IPv4 address. A the=
n gets a time query<br>
&gt;=C2=A0 =C2=A0 =C2=A0from C over IPv6. How does it know if B and C are t=
he same system or<br>
&gt;=C2=A0 =C2=A0 =C2=A0different system? A has no information about that.<=
br>
&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0Is this clearer?<br>
&gt;<br>
&gt; Yes, it&#39;s clear. How does the current ntpd implementation deal wit=
h this<br>
</span>&gt; problem? =C3=82<br>
&gt;<br>
<br>
Currently it doesn&#39;t. One of my proposals is for each system to generat=
e<br>
a RefID and use that for all interfaces. I&#39;m not sure if that works for=
<br>
all cases or causes other issues.<br></blockquote><div><br></div><div>OK. T=
o clarify: you are proposing an extension to NTP where a server that has mu=
ltiple IP addresses can choose a special value as its refID, and communicat=
e that to its clients.=C2=A0 Then, if the clients choose to take time from =
that server, they put that special value in as their refID, instead of an I=
P address.</div><div><br></div><div>AFAIK this functionality is not part of=
 NTP today, right? It would probably require an extension field? Also its n=
ot backwards compatible, since a server that chooses to do this would need =
to make sure that its clients understand what it is doing. And currently cl=
ients don&#39;t know how to do this, right?</div></div><div><br></div><div>=
Please clarify if I have misunderstood.</div><div><br></div>-- <br><div cla=
ss=3D"gmail_signature">Sharon Goldberg<br>Computer Science, Boston Universi=
ty<br><a href=3D"http://www.cs.bu.edu/~goldbe" target=3D"_blank">http://www=
.cs.bu.edu/~goldbe</a></div>
</div></div>

--001a1148f200d3bc85052fc30e3b--


From nobody Tue Apr  5 14:17:07 2016
Return-Path: <stenn@stenn.ntp.org>
X-Original-To: tictoc@ietfa.amsl.com
Delivered-To: tictoc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 02CBE12D674 for <tictoc@ietfa.amsl.com>; Tue,  5 Apr 2016 14:17:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level: 
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZxkA2Kof8Si8 for <tictoc@ietfa.amsl.com>; Tue,  5 Apr 2016 14:17:02 -0700 (PDT)
Received: from stenn.ntp.org (stenn.ntp.org [149.20.68.30]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9CB4912D1BA for <tictoc@ietf.org>; Tue,  5 Apr 2016 14:16:53 -0700 (PDT)
Received: from [::1] (helo=stenn.ntp.org) by stenn.ntp.org with esmtp (Exim 4.86_2 (FreeBSD)) (envelope-from <stenn@stenn.ntp.org>) id 1anYIm-0002p4-59; Tue, 05 Apr 2016 21:14:20 +0000
From: Harlan Stenn <stenn@ntp.org>
To: mayer@ntp.org
In-reply-to: <570411C0.7000004@ntp.org>
References: <CAJHGrrQimUVqtRg6bowwBr5pxrSUh+mHkEzB0P1SBxP=nzczbg@mail.gmail.com> <57040B4A.4090301@pdmconsulting.net> <CAJHGrrSSD7o6Hy_3e8dNTOSTYF5MkyGo-Bn5SqHxa87XWqFpHQ@mail.gmail.com> <570411C0.7000004@ntp.org>
Comments: In-reply-to Danny Mayer <mayer@ntp.org> message dated "Tue, 05 Apr 2016 15:28:00 -0400."
X-Mailer: MH-E 7.4.2; nmh 1.6; XEmacs 21.4 (patch 24)
Mime-Version: 1.0 (generated by tm-edit 1.8)
Content-Type: text/plain; charset=US-ASCII
Date: Tue, 05 Apr 2016 21:14:20 +0000
Message-Id: <E1anYIm-0002p4-59@stenn.ntp.org>
Archived-At: <http://mailarchive.ietf.org/arch/msg/tictoc/z4zHTJKRWIspvvkgZAmZHo8Otb8>
Cc: Sharon Goldberg <goldbe@cs.bu.edu>, NTP Working Group <ntpwg@lists.ntp.org>, tictoc@ietf.org
Subject: Re: [TICTOC] [ntpwg]  comments on draft-stenn-ntp-suggest-refid-00
X-BeenThere: tictoc@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Timing over IP Connection and Transfer of Clock BOF <tictoc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tictoc>, <mailto:tictoc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tictoc/>
List-Post: <mailto:tictoc@ietf.org>
List-Help: <mailto:tictoc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tictoc>, <mailto:tictoc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 05 Apr 2016 21:17:06 -0000

Danny Mayer writes:
> On 4/5/2016 3:21 PM, Sharon Goldberg wrote:
> > On Tue, Apr 5, 2016 at 3:00 PM, Danny Mayer <mayer@pdmconsulting.net
> > <mailto:mayer@pdmconsulting.net>> wrote:
> > =
> 
> >     On 4/5/2016 2:28 PM, Sharon Goldberg wrote:
> >     > Dear WG,
> >     >
> >     > To follow up on my comments on draft-stenn-ntp-suggest-refid-00 at =
> the
> >     > IETF'95 WG meeting just now. The current draft requires the use of =
> an
> >     > extension field.=C3=82=C2  I believe the goals of the draft can be
> >     accomplished
> >     > without using an extension field, in a backwards compatible fashion.
> >     >
> >     > The goal of the draft is to limit the information exposed by the RE=
> FID
> >     > while still preserving robustness to "length-1" timing loops where
> >     > system A takes time from system B, but system B takes time from
> >     system A. =C3=82
> >     > This proposal allow system A to limit the info it leaks in its refI=
> D,
> >     > without harming any of its legacy clients.=C3=82
> >     >
> >     > Suppose system A is taking time from system B. Then there are two c=
> ases:
> >     > 1) If A gets a time query from system B, A puts the IP of B in the =
> refID
> >     > of its response. This way, even a legacy B can tell it cannot take =
> time
> >     > from A because this would cause a timing loop.
> >     >
> >     > 2) If A gets a time query from system C, A puts a "nonsense" value =
> in
> >     > its refID.=C3=82=C2  Even a legacy C can see that its IP is not in =
> the
> >     refID,
> >     > and so it is allowed to take time from A.=C3=82
> >     >
> >     > One question is what this "nonsense" value should be.=C3=82=C2  I t=
> hink it
> >     > should be a fixed value. For example 0.0.0.0.=C3=82=C2  We would no=
> t want a
> >     > randomly-chosen value since this might collide with actual IP addre=
> sses
> >     > on the network.
> >     >
> >     > Thanks,
> >     > Sharon
> > =
> 
> >     The problem that I was alluding to in the jabber room is this. I'll k=
> eep
> >     the problem simple and to one example.
> > =
> 
> >     A takes its time from B over an IPv4 address. A then gets a time query
> >     from C over IPv6. How does it know if B and C are the same system or
> >     different system? A has no information about that.
> > =
> 
> >     Is this clearer?
> > =
> 
> > Yes, it's clear. How does the current ntpd implementation deal with this
> > problem? =C2 =
> 
> > =
> 
> Currently it doesn't. One of my proposals is for each system to generate
> a RefID and use that for all interfaces. I'm not sure if that works for
> all cases or causes other issues.

It *hasn't* been an issue.  It would be easy enough to address it if
somebody felt there was a need to, however.

The point is that with your proposal, Sharon, I'm not seeing that it is
possible to address this case.  That is separate from whether or not
it's a problem that needs to be addressed, now or in the "near" future.

It's clear that if A has multiple IPs on it (very common now, not common
20 years' ago) that A could check all of its IPs when it saw B's refid
and decide if any of them meant B was sync'd to A.

In reality, we have only seen that if A sends a packet to B, B responds
to that same address on that same IP.  We have had cases where that
response has come over a different interface.

There are other possiblities, though.

Here are more scenarios.

A VM host maintains the primary clock, and "guests" use that clock.  In
this case, if A and B are on the same VM host, their underlying system
clock is actually the same one.

And that assumes one (common) scenario - the VMs are likely set up so
that all the VMs have tightly-synchronized time.

There's another use case I've been looking for - a VM setup where I
can configure each VM to have a clock that behaves independently, so I
can test wider behaviors more easily.

Is it sufficient to check for loops of degree 1?  Exactly what problems
are we solving here?

What about the situation where a single refclock is directly feeding
multiple servers?  If A and B are getting their time from the same
refclock, should that mean A and B should not fall back on each other if
one of them loses signal to their shared refclock?

If A and B are talking to the same type of refclock is that something
that should be addressed?  There have been cases where broken firmware
has caused a family of refclocks to all take simultaneous leaps to the
same spot in the weeds.

If A and B are both using GPS (for example) and there is a system glitch
where GPS time is affected, is that also a timing loop that we'd want to
avoid?  This happened in Jan 2016.

What about a group of systems that share a PPS signal?  The PPS signal
might become untrustworthy, or the "source of numbered seconds" might
break.

Many of these issues are currently(!) insignificant in a LAN setting
where we're looking at timing/frequency sync to around the millisecond
level (roughly).  I don't *know*, but I'd bet they are significant when
trying to get to the microsecond level, let alone the nanosecond level.
Hello PTP.  Hello RADclock and the work PHK is doing with the algorithms
he's using on Ntimed.  Once we learn more about these, we need to make
sure these different choices will "play nice" with each other.

Similarly, chrony uses algorithms that are slightly different from the
ones NTP uses.  We haven't seen studies of any potential loop
instabilities between these two approaches, either.

I mention this because 20 years' ago we thought we were doing well
getting clocks to sync to within a tenth of a second.  Now, getting
sub-millisecond sync on a LAN is common.  I've spoken with folks who
told me that with some care and support, they are getting sync levels
with NTP that are very close to what they get with PTP - down to the
range of nanoseconds.  Where will we be 10 years' time from now?

I recall PHK saying that with PTP (or PTP-like stuff), he was able to
get offset and frequency sync on cold start in less than a second.  He
was doing this with a poll interval of about -9, or about 500
polls/second.

I know DLM was solving a real and evidenced problem with the refid and
loop detection.

It's looking like we need to take a stronger look at this to decide if
those problems are still significant, and if different problems are
becoming significant.
-- 
Harlan Stenn <stenn@ntp.org>
http://networktimefoundation.org - be a member!


From nobody Tue Apr  5 14:36:34 2016
Return-Path: <stenn@stenn.ntp.org>
X-Original-To: tictoc@ietfa.amsl.com
Delivered-To: tictoc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4624C12D5F5 for <tictoc@ietfa.amsl.com>; Tue,  5 Apr 2016 14:36:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level: 
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id W-cxHur0xI7X for <tictoc@ietfa.amsl.com>; Tue,  5 Apr 2016 14:36:29 -0700 (PDT)
Received: from stenn.ntp.org (stenn.ntp.org [149.20.68.30]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D192D12D894 for <tictoc@ietf.org>; Tue,  5 Apr 2016 14:36:27 -0700 (PDT)
Received: from [::1] (helo=stenn.ntp.org) by stenn.ntp.org with esmtp (Exim 4.86_2 (FreeBSD)) (envelope-from <stenn@stenn.ntp.org>) id 1anYbk-0002qu-8u; Tue, 05 Apr 2016 21:33:56 +0000
From: Harlan Stenn <stenn@ntp.org>
To: Sharon Goldberg <goldbe@cs.bu.edu>
In-reply-to: <CAJHGrrR=-uN7dD5S0hBnF3Mt9ZrO8dC5YJK9k+D8j+WBFvByRg@mail.gmail.com>
References: <CAJHGrrQimUVqtRg6bowwBr5pxrSUh+mHkEzB0P1SBxP=nzczbg@mail.gmail.com> <57040B4A.4090301@pdmconsulting.net> <CAJHGrrSSD7o6Hy_3e8dNTOSTYF5MkyGo-Bn5SqHxa87XWqFpHQ@mail.gmail.com> <570411C0.7000004@ntp.org> <CAJHGrrR=-uN7dD5S0hBnF3Mt9ZrO8dC5YJK9k+D8j+WBFvByRg@mail.gmail.com>
Comments: In-reply-to Sharon Goldberg <goldbe@cs.bu.edu> message dated "Tue, 05 Apr 2016 16:54:17 -0400."
X-Mailer: MH-E 7.4.2; nmh 1.6; XEmacs 21.4 (patch 24)
Mime-Version: 1.0 (generated by tm-edit 1.8)
Content-Type: text/plain; charset=US-ASCII
Date: Tue, 05 Apr 2016 21:33:56 +0000
Message-Id: <E1anYbk-0002qu-8u@stenn.ntp.org>
Archived-At: <http://mailarchive.ietf.org/arch/msg/tictoc/LBmGV0GpxXISOFk8KME8iGDUsoE>
Cc: NTP Working Group <ntpwg@lists.ntp.org>, tictoc@ietf.org
Subject: Re: [TICTOC] [ntpwg]  comments on draft-stenn-ntp-suggest-refid-00
X-BeenThere: tictoc@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Timing over IP Connection and Transfer of Clock BOF <tictoc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tictoc>, <mailto:tictoc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tictoc/>
List-Post: <mailto:tictoc@ietf.org>
List-Help: <mailto:tictoc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tictoc>, <mailto:tictoc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 05 Apr 2016 21:36:32 -0000

Sharon Goldberg writes:
>>>     The problem that I was alluding to in the jabber room is >>>
>>>     this. I'll keep the problem simple and to one example.
>>>
>>>     A takes its time from B over an IPv4 address. A then gets a time
>>>     query from C over IPv6. How does it know if B and C are the same
>>>     system or different system? A has no information about that.
>>>
>>>     Is this clearer?
>>>
>>> Yes, it's clear. How does the current ntpd implementation deal with this
>>> problem?
>>
>> Currently it doesn't. One of my proposals is for each system to
>> generate a RefID and use that for all interfaces. I'm not sure if
>> that works for all cases or causes other issues.
> 
> OK. To clarify: you are proposing an extension to NTP where a server
> that has multiple IP addresses can choose a special value as its
> refID, and communicate that to its clients.  Then, if the clients
> choose to take time from that server, they put that special value in
> as their refID, instead of an IP address.

My proposal for SUGGEST-REFID is simply a mechanism for an NTP instance
to tell others "If you use me as your system peer, please use <FOO> as
your refid."

If a server chooses to suggest a single nonce for all of its interfaces
as its suggested refid, great.  If it chooses to use that same nonce for
all of its associations, that's great too.

For me, we're now in the realm of "policy", and there are tradeoffs
there.

My goal was to provide a robust mechanism to allow for these policy
choices.

> AFAIK this functionality is not part of NTP today, right? It would
> probably require an extension field? Also its not backwards
> compatible, since a server that chooses to do this would need to make
> sure that its clients understand what it is doing. And currently
> clients don't know how to do this, right?

Danny's (policy) proposal would most likely be implemented using the
suggest-refid EF proposal I made, so:

Yes, an EF

Nobody is doing this yet, unless somebody has implemented my proposal
and not told me.

As for backward compatibility, that's not really an issue.  An old
server will not understand the EF so it will use the current rules for
choosing its refid when selecting its system peer.

This is what I talked about in my first "set", covering the I-Do and
Last-EF proposals.  If I send you packets with I-Do and get back a plain
response, I know you can't or aren't willing to do these newer choices.
Either way, I need to be prepared to check the legacy and suggested
refid choices in responses I get from you.

If I send you an I-Do and get *no* response, then I don't know if you
never got my packet or you got it and dropped it because it had an
unrecognized EF in it.  Eventually I would just send plain packets.

H


From nobody Tue Apr  5 19:02:14 2016
Return-Path: <mayer@ntp.org>
X-Original-To: tictoc@ietfa.amsl.com
Delivered-To: tictoc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 10EEC12D0B3 for <tictoc@ietfa.amsl.com>; Tue,  5 Apr 2016 19:02:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level: 
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id r890M2vM8vkT for <tictoc@ietfa.amsl.com>; Tue,  5 Apr 2016 19:02:11 -0700 (PDT)
Received: from mail1.ntp.org (mail1.ntp.org [IPv6:2001:4f8:fff7:1::5]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 851A512D09A for <tictoc@ietf.org>; Tue,  5 Apr 2016 19:02:11 -0700 (PDT)
Received: from pool-71-174-223-70.bstnma.east.verizon.net ([71.174.223.70] helo=[10.10.10.102]) by mail1.ntp.org with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.77 (FreeBSD)) (envelope-from <mayer@ntp.org>) id 1ancnJ-000Gge-Hi; Wed, 06 Apr 2016 02:02:10 +0000
References: <CAJHGrrQimUVqtRg6bowwBr5pxrSUh+mHkEzB0P1SBxP=nzczbg@mail.gmail.com> <57040B4A.4090301@pdmconsulting.net> <CAJHGrrSSD7o6Hy_3e8dNTOSTYF5MkyGo-Bn5SqHxa87XWqFpHQ@mail.gmail.com> <570411C0.7000004@ntp.org> <CAJHGrrR=-uN7dD5S0hBnF3Mt9ZrO8dC5YJK9k+D8j+WBFvByRg@mail.gmail.com>
To: Sharon Goldberg <goldbe@cs.bu.edu>
From: Danny Mayer <mayer@ntp.org>
Organization: NTP
Message-ID: <57046E26.2050705@ntp.org>
Date: Tue, 5 Apr 2016 22:02:14 -0400
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.7.0
MIME-Version: 1.0
In-Reply-To: <CAJHGrrR=-uN7dD5S0hBnF3Mt9ZrO8dC5YJK9k+D8j+WBFvByRg@mail.gmail.com>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 8bit
X-SA-Exim-Connect-IP: 71.174.223.70
X-SA-Exim-Rcpt-To: tictoc@ietf.org, ntpwg@lists.ntp.org, goldbe@cs.bu.edu
X-SA-Exim-Mail-From: mayer@ntp.org
X-SA-Exim-Version: 4.2
X-SA-Exim-Scanned: Yes (on mail1.ntp.org)
Archived-At: <http://mailarchive.ietf.org/arch/msg/tictoc/7LfWL2ou8lrrNNWxZUDQ5vwYPoo>
Cc: NTP Working Group <ntpwg@lists.ntp.org>, tictoc@ietf.org
Subject: Re: [TICTOC] comments on draft-stenn-ntp-suggest-refid-00
X-BeenThere: tictoc@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
Reply-To: mayer@ntp.org
List-Id: Timing over IP Connection and Transfer of Clock BOF <tictoc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tictoc>, <mailto:tictoc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tictoc/>
List-Post: <mailto:tictoc@ietf.org>
List-Help: <mailto:tictoc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tictoc>, <mailto:tictoc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 06 Apr 2016 02:02:13 -0000

On 4/5/2016 4:54 PM, Sharon Goldberg wrote:
>     >Â  Â  Â The problem that I was alluding to in the jabber room is this. I'll keep
>     >Â  Â  Â the problem simple and to one example.
>     >
>     >Â  Â  Â A takes its time from B over an IPv4 address. A then gets a time query
>     >Â  Â  Â from C over IPv6. How does it know if B and C are the same system or
>     >Â  Â  Â different system? A has no information about that.
>     >
>     >Â  Â  Â Is this clearer?
>     >
>     > Yes, it's clear. How does the current ntpd implementation deal with this
>     > problem? Ã‚
>     >
> 
>     Currently it doesn't. One of my proposals is for each system to generate
>     a RefID and use that for all interfaces. I'm not sure if that works for
>     all cases or causes other issues.
> 
> 
> OK. To clarify: you are proposing an extension to NTP where a server
> that has multiple IP addresses can choose a special value as its refID,
> and communicate that to its clients.Â  Then, if the clients choose to
> take time from that server, they put that special value in as their
> refID, instead of an IP address.
> 
> AFAIK this functionality is not part of NTP today, right? It would
> probably require an extension field? Also its not backwards compatible,
> since a server that chooses to do this would need to make sure that its
> clients understand what it is doing. And currently clients don't know
> how to do this, right?
> 
> Please clarify if I have misunderstood.

You did misunderstand. I said the Refid itself and not an extension
field so it would be interoperable. I'm of the opinion that a server
should only have one refid for all interfaces no matter which one is
being used to send the packet. I recall that there is an issue that
Harlan had to explain to me in excruciating detail as to why the
existing refid is the way it is today but I don't recall now the
details. We already have a problem where the hash of the IPv6 address
can conflict with a real IPv4 address.

Danny


From nobody Tue Apr  5 21:00:16 2016
Return-Path: <stenn@stenn.ntp.org>
X-Original-To: tictoc@ietfa.amsl.com
Delivered-To: tictoc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B522712D10E for <tictoc@ietfa.amsl.com>; Tue,  5 Apr 2016 21:00:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level: 
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OlxWIK7-tpbu for <tictoc@ietfa.amsl.com>; Tue,  5 Apr 2016 21:00:13 -0700 (PDT)
Received: from stenn.ntp.org (stenn.ntp.org [149.20.68.30]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1BF1812D0F7 for <tictoc@ietf.org>; Tue,  5 Apr 2016 21:00:13 -0700 (PDT)
Received: from [::1] (helo=stenn.ntp.org) by stenn.ntp.org with esmtp (Exim 4.86_2 (FreeBSD)) (envelope-from <stenn@stenn.ntp.org>) id 1aneZs-0003LS-ST; Wed, 06 Apr 2016 03:56:24 +0000
From: Harlan Stenn <stenn@ntp.org>
To: mayer@ntp.org
In-reply-to: <57046E26.2050705@ntp.org>
References: <CAJHGrrQimUVqtRg6bowwBr5pxrSUh+mHkEzB0P1SBxP=nzczbg@mail.gmail.com> <57040B4A.4090301@pdmconsulting.net> <CAJHGrrSSD7o6Hy_3e8dNTOSTYF5MkyGo-Bn5SqHxa87XWqFpHQ@mail.gmail.com> <570411C0.7000004@ntp.org> <CAJHGrrR=-uN7dD5S0hBnF3Mt9ZrO8dC5YJK9k+D8j+WBFvByRg@mail.gmail.com> <57046E26.2050705@ntp.org>
Comments: In-reply-to Danny Mayer <mayer@ntp.org> message dated "Tue, 05 Apr 2016 22:02:14 -0400."
X-Mailer: MH-E 7.4.2; nmh 1.6; XEmacs 21.4 (patch 24)
Mime-Version: 1.0 (generated by tm-edit 1.8)
Content-Type: text/plain; charset=US-ASCII
Date: Wed, 06 Apr 2016 03:56:24 +0000
Message-Id: <E1aneZs-0003LS-ST@stenn.ntp.org>
Archived-At: <http://mailarchive.ietf.org/arch/msg/tictoc/ygGh4tnRPTYAiIL1LWMcOze19W8>
Cc: Sharon Goldberg <goldbe@cs.bu.edu>, NTP Working Group <ntpwg@lists.ntp.org>, tictoc@ietf.org
Subject: Re: [TICTOC] [ntpwg]  comments on draft-stenn-ntp-suggest-refid-00
X-BeenThere: tictoc@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Timing over IP Connection and Transfer of Clock BOF <tictoc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tictoc>, <mailto:tictoc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tictoc/>
List-Post: <mailto:tictoc@ietf.org>
List-Help: <mailto:tictoc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tictoc>, <mailto:tictoc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 06 Apr 2016 04:00:14 -0000

Danny Mayer writes:
> You did misunderstand. I said the Refid itself and not an extension
> field so it would be interoperable. I'm of the opinion that a server
> should only have one refid for all interfaces no matter which one is
> being used to send the packet. I recall that there is an issue that
> Harlan had to explain to me in excruciating detail as to why the
> existing refid is the way it is today but I don't recall now the
> details. We already have a problem where the hash of the IPv6 address
> can conflict with a real IPv4 address.

If that would be your policy then the way to implement it is with the
suggest-refid EF proposal I submitted.

The legacy behavior is that "For S2+, I use the IPv4 (or partial hash of
the IPv6) address of my system peer as the refid."

If this situation is not clearly described in my proposal please show
where that information could be improved.

H


From nobody Tue Apr  5 21:59:41 2016
Return-Path: <weiler@watson.org>
X-Original-To: tictoc@ietfa.amsl.com
Delivered-To: tictoc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B28A812D64C for <tictoc@ietfa.amsl.com>; Tue,  5 Apr 2016 21:26:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level: 
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id c5vsCWxVmODO for <tictoc@ietfa.amsl.com>; Tue,  5 Apr 2016 21:26:08 -0700 (PDT)
Received: from cyrus.watson.org (cyrus.watson.org [198.74.231.69]) by ietfa.amsl.com (Postfix) with ESMTP id E574512D641 for <tictoc@ietf.org>; Tue,  5 Apr 2016 21:26:07 -0700 (PDT)
Received: from fledge.watson.org (fledge.watson.org [198.74.231.63]) by cyrus.watson.org (Postfix) with ESMTPS id 8BDC246B1A; Wed,  6 Apr 2016 00:26:07 -0400 (EDT)
Received: from fledge.watson.org (weiler@localhost.watson.org [127.0.0.1]) by fledge.watson.org (8.15.2/8.15.2) with ESMTP id u364Q72J055173; Wed, 6 Apr 2016 00:26:07 -0400 (EDT) (envelope-from weiler@watson.org)
Received: from localhost (weiler@localhost) by fledge.watson.org (8.15.2/8.15.2/Submit) with ESMTP id u364Q69f055170; Wed, 6 Apr 2016 00:26:07 -0400 (EDT) (envelope-from weiler@watson.org)
X-Authentication-Warning: fledge.watson.org: weiler owned process doing -bs
Date: Wed, 6 Apr 2016 00:26:06 -0400 (EDT)
From: Samuel Weiler <weiler@watson.org>
To: Danny Mayer <mayer@ntp.org>
In-Reply-To: <56F98E6B.1000805@ntp.org>
Message-ID: <alpine.BSF.2.20.1604060009220.47293@fledge.watson.org>
References: <CAMbs7kvo80z0vVd5WvCkj876mEbUO8cu-Op6sYOGVxU9ykgFEg@mail.gmail.com> <56F98E6B.1000805@ntp.org>
User-Agent: Alpine 2.20 (BSF 67 2015-01-07)
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII; format=flowed
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.4.3 (fledge.watson.org [127.0.0.1]); Wed, 06 Apr 2016 00:26:07 -0400 (EDT)
Archived-At: <http://mailarchive.ietf.org/arch/msg/tictoc/u_RLzVQuUsR-He9PmlGFCz093Xc>
X-Mailman-Approved-At: Tue, 05 Apr 2016 21:59:40 -0700
Cc: ntpwg@lists.ntp.org, "tictoc@ietf.org" <tictoc@ietf.org>
Subject: Re: [TICTOC] [ntpwg] Cipher suites for NTS?
X-BeenThere: tictoc@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Timing over IP Connection and Transfer of Clock BOF <tictoc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tictoc>, <mailto:tictoc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tictoc/>
List-Post: <mailto:tictoc@ietf.org>
List-Help: <mailto:tictoc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tictoc>, <mailto:tictoc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 06 Apr 2016 04:26:09 -0000

On Mon, 28 Mar 2016, Danny Mayer wrote:

> We have to be careful here. I agree that at least some cipher suites 
> should be specified as a minimal subset in the draft but we also 
> need flexibility as new ciphers come out and older ones are found to 
> be vunerable. Otherwise we will need to create new RFC's to update 
> the RFC for either of these scenarios.

We should pick a cipher suite. Absent a compelling reason for more, 
let's just pick one (for now).

And we do need to provide for algorithm agility. Unfortunately, that 
is much trickier than merely parameterizing ciphers - we also need to 
understand the negotiation of cipher suites and prevent downgrade 
attacks.  Here's some discussion on the topic: 
https://tools.ietf.org/html/rfc7696

For good or ill, other negotiations (e.g. NTS version number) may also 
provide opportunities for downgrade. Which means we may be also to 
address multiple vulnerabilities at once.

One step toward addressing all of this might be to extend the ntp 
client config file to include a bit for "this name server is expected 
to use NTS (version #blah)".  Perhaps cipher suite info could be in 
the same config file or in the server's certs?

Lastly, do not be afraid to roll a new RFC to introduce a new 
algorithm. While it makes sense to have an IANA registry for cipher 
suites, "standards action" might be a good choice of policy to add a 
new entry into that registry.

-- Sam


From nobody Wed Apr  6 01:40:52 2016
Return-Path: <mlichvar@redhat.com>
X-Original-To: tictoc@ietfa.amsl.com
Delivered-To: tictoc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C451612D618 for <tictoc@ietfa.amsl.com>; Wed,  6 Apr 2016 01:40:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.932
X-Spam-Level: 
X-Spam-Status: No, score=-6.932 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4qBUtwcfvs17 for <tictoc@ietfa.amsl.com>; Wed,  6 Apr 2016 01:40:49 -0700 (PDT)
Received: from mx1.redhat.com (mx1.redhat.com [209.132.183.28]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2270512D16E for <tictoc@ietf.org>; Wed,  6 Apr 2016 01:40:49 -0700 (PDT)
Received: from int-mx10.intmail.prod.int.phx2.redhat.com (int-mx10.intmail.prod.int.phx2.redhat.com [10.5.11.23]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.redhat.com (Postfix) with ESMTPS id ABF2E92472; Wed,  6 Apr 2016 08:40:48 +0000 (UTC)
Received: from localhost (dhcp-24-154.brq.redhat.com [10.34.24.154]) by int-mx10.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4) with ESMTP id u368elqi024418; Wed, 6 Apr 2016 04:40:47 -0400
Date: Wed, 6 Apr 2016 10:40:46 +0200
From: Miroslav Lichvar <mlichvar@redhat.com>
To: Harlan Stenn <stenn@ntp.org>
Message-ID: <20160406084046.GB9802@localhost>
References: <CAJHGrrQimUVqtRg6bowwBr5pxrSUh+mHkEzB0P1SBxP=nzczbg@mail.gmail.com> <57040B4A.4090301@pdmconsulting.net> <CAJHGrrSSD7o6Hy_3e8dNTOSTYF5MkyGo-Bn5SqHxa87XWqFpHQ@mail.gmail.com> <570411C0.7000004@ntp.org> <CAJHGrrR=-uN7dD5S0hBnF3Mt9ZrO8dC5YJK9k+D8j+WBFvByRg@mail.gmail.com> <E1anYbk-0002qu-8u@stenn.ntp.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <E1anYbk-0002qu-8u@stenn.ntp.org>
User-Agent: Mutt/1.5.24 (2015-08-30)
X-Scanned-By: MIMEDefang 2.68 on 10.5.11.23
Archived-At: <http://mailarchive.ietf.org/arch/msg/tictoc/XKMtofPVnXxUUsVeLB8kHpzFNaM>
Cc: Sharon Goldberg <goldbe@cs.bu.edu>, NTP Working Group <ntpwg@lists.ntp.org>, tictoc@ietf.org
Subject: Re: [TICTOC] [ntpwg]  comments on draft-stenn-ntp-suggest-refid-00
X-BeenThere: tictoc@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Timing over IP Connection and Transfer of Clock BOF <tictoc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tictoc>, <mailto:tictoc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tictoc/>
List-Post: <mailto:tictoc@ietf.org>
List-Help: <mailto:tictoc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tictoc>, <mailto:tictoc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 06 Apr 2016 08:40:51 -0000

On Tue, Apr 05, 2016 at 09:33:56PM +0000, Harlan Stenn wrote:
> Sharon Goldberg writes:
> > OK. To clarify: you are proposing an extension to NTP where a server
> > that has multiple IP addresses can choose a special value as its
> > refID, and communicate that to its clients.  Then, if the clients
> > choose to take time from that server, they put that special value in
> > as their refID, instead of an IP address.
> 
> My proposal for SUGGEST-REFID is simply a mechanism for an NTP instance
> to tell others "If you use me as your system peer, please use <FOO> as
> your refid."

I think an extension field that would allow servers to announce their
own refids to clients is an excellent idea and I'm glad someone is
working on it.

However, I'm not sure about the intended security use case of the
proposal. I'm still not convinced that hiding refid would be a major
problem for an attacker. I think the number of servers that most
clients use on the Internet is fairly small, it probably consist of
pool.ntp.org and the list of public servers maintained on the ntp.org
wiki. The attacker can probably restrict the list by geo location of
the client to a country zone with few hundred of servers at most. I
suspect in most cases the attacker would be able to succeed by sending
spoofed packets from all these servers.

If there is a security issue with clients accepting spoofed packets, I
think it should be fixed directly instead of adding some security
through obscurity.

I'd rather see this extension field used as a way to improve the
robustness of the protocol. As Danny pointed out, if servers announced
the same refid to all clients, they could reliably detect multihomed
hosts.

My suggestion is to modify the field so it includes also refids of all
upstream servers. The clients could then prevent synchronisation loops
longer than 2. Loops between 3 peers polling one another can happen
easily and currently the best recommendation to prevent them is to
use a "line" configuration for the peers instead of a fully connected
mesh. Also, if the clients knew all upstream refids, they could detect
duplicate servers in the paths to the stratum 1 servers and ignore
them or decrease their weight.

-- 
Miroslav Lichvar


From nobody Wed Apr  6 02:13:55 2016
Return-Path: <stenn@stenn.ntp.org>
X-Original-To: tictoc@ietfa.amsl.com
Delivered-To: tictoc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7066A12D117 for <tictoc@ietfa.amsl.com>; Wed,  6 Apr 2016 02:13:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level: 
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3pPJGzPG2f3q for <tictoc@ietfa.amsl.com>; Wed,  6 Apr 2016 02:13:52 -0700 (PDT)
Received: from stenn.ntp.org (stenn.ntp.org [149.20.68.30]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id ECA2612D0E3 for <tictoc@ietf.org>; Wed,  6 Apr 2016 02:13:52 -0700 (PDT)
Received: from [::1] (helo=stenn.ntp.org) by stenn.ntp.org with esmtp (Exim 4.86_2 (FreeBSD)) (envelope-from <stenn@stenn.ntp.org>) id 1anjUd-0003hc-Ho; Wed, 06 Apr 2016 09:11:19 +0000
From: Harlan Stenn <stenn@ntp.org>
To: Miroslav Lichvar <mlichvar@redhat.com>
In-reply-to: <20160406084046.GB9802@localhost>
References: <CAJHGrrQimUVqtRg6bowwBr5pxrSUh+mHkEzB0P1SBxP=nzczbg@mail.gmail.com> <57040B4A.4090301@pdmconsulting.net> <CAJHGrrSSD7o6Hy_3e8dNTOSTYF5MkyGo-Bn5SqHxa87XWqFpHQ@mail.gmail.com> <570411C0.7000004@ntp.org> <CAJHGrrR=-uN7dD5S0hBnF3Mt9ZrO8dC5YJK9k+D8j+WBFvByRg@mail.gmail.com> <E1anYbk-0002qu-8u@stenn.ntp.org> <20160406084046.GB9802@localhost>
Comments: In-reply-to Miroslav Lichvar <mlichvar@redhat.com> message dated "Wed, 06 Apr 2016 10:40:46 +0200."
X-Mailer: MH-E 7.4.2; nmh 1.6; XEmacs 21.4 (patch 24)
Mime-Version: 1.0 (generated by tm-edit 1.8)
Content-Type: text/plain; charset=US-ASCII
Date: Wed, 06 Apr 2016 09:11:19 +0000
Message-Id: <E1anjUd-0003hc-Ho@stenn.ntp.org>
Archived-At: <http://mailarchive.ietf.org/arch/msg/tictoc/hluZAuipUAB71HVyNXsulNzCysE>
Cc: Sharon Goldberg <goldbe@cs.bu.edu>, Harlan Stenn <stenn@ntp.org>, tictoc@ietf.org, NTP Working Group <ntpwg@lists.ntp.org>
Subject: Re: [TICTOC] [ntpwg]  comments on draft-stenn-ntp-suggest-refid-00
X-BeenThere: tictoc@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Timing over IP Connection and Transfer of Clock BOF <tictoc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tictoc>, <mailto:tictoc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tictoc/>
List-Post: <mailto:tictoc@ietf.org>
List-Help: <mailto:tictoc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tictoc>, <mailto:tictoc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 06 Apr 2016 09:13:54 -0000

Miroslav Lichvar writes:
> I think an extension field that would allow servers to announce their
> own refids to clients is an excellent idea and I'm glad someone is
> working on it.
> 
> However, I'm not sure about the intended security use case of the
> proposal. I'm still not convinced that hiding refid would be a major
> problem for an attacker. I think the number of servers that most
> clients use on the Internet is fairly small, it probably consist of
> pool.ntp.org and the list of public servers maintained on the ntp.org
> wiki. The attacker can probably restrict the list by geo location of
> the client to a country zone with few hundred of servers at most. I
> suspect in most cases the attacker would be able to succeed by sending
> spoofed packets from all these servers.

How do you define "the attacker would be able to succeed" in this case?

Refclocks are increasingly easy to use, too, and this sort of
knowledge/attack is not useful if somebody has a local refclock.

I don't know how valid it is to assume your geo location claim.

Finally, if an attacker is going after somebody's servers that means
the "victim" will be getting unsolicited responses, and we now alert on
that case.

There are other protections against these attacks in the current
codebase, too.

> If there is a security issue with clients accepting spoofed packets, I
> think it should be fixed directly instead of adding some security
> through obscurity.

What do you suggest?  How does the current proposal make things worse in
any way?

> I'd rather see this extension field used as a way to improve the
> robustness of the protocol.

Huh?  I think you are conflating things here.  The proposal is a
*mechanism* and the value it contains is *policy*.

> As Danny pointed out, if servers announced
> the same refid to all clients, they could reliably detect multihomed
> hosts.

Then all a bad guy has to do is to send a time request to a target, see
what refid it gets, and then use that knowledge as an attack vector.

Also, there has been no demonstrated benefit that this "wider scope"
loop detection will be of any useful value.

> My suggestion is to modify the field so it includes also refids of all
> upstream servers. The clients could then prevent synchronisation loops
> longer than 2. Loops between 3 peers polling one another can happen
> easily and currently the best recommendation to prevent them is to
> use a "line" configuration for the peers instead of a fully connected
> mesh. Also, if the clients knew all upstream refids, they could detect
> duplicate servers in the paths to the stratum 1 servers and ignore
> them or decrease their weight.

Can you demonstrate tangible problems with the current scheme and
tangible benefit with your solution?  Please also consider the security
ramifications.

I've seen lots of mesh setups - they have all worked fine.

H


From nobody Wed Apr  6 03:39:22 2016
Return-Path: <mlichvar@redhat.com>
X-Original-To: tictoc@ietfa.amsl.com
Delivered-To: tictoc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8874212D0B9 for <tictoc@ietfa.amsl.com>; Wed,  6 Apr 2016 03:39:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.932
X-Spam-Level: 
X-Spam-Status: No, score=-6.932 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id s20h_0VunREg for <tictoc@ietfa.amsl.com>; Wed,  6 Apr 2016 03:39:14 -0700 (PDT)
Received: from mx1.redhat.com (mx1.redhat.com [209.132.183.28]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 87E7412D13B for <tictoc@ietf.org>; Wed,  6 Apr 2016 03:39:14 -0700 (PDT)
Received: from int-mx10.intmail.prod.int.phx2.redhat.com (int-mx10.intmail.prod.int.phx2.redhat.com [10.5.11.23]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.redhat.com (Postfix) with ESMTPS id F23181441B1; Wed,  6 Apr 2016 10:39:13 +0000 (UTC)
Received: from localhost (dhcp-24-154.brq.redhat.com [10.34.24.154]) by int-mx10.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4) with ESMTP id u36AdCsE026994; Wed, 6 Apr 2016 06:39:13 -0400
Date: Wed, 6 Apr 2016 12:39:12 +0200
From: Miroslav Lichvar <mlichvar@redhat.com>
To: Harlan Stenn <stenn@ntp.org>
Message-ID: <20160406103912.GA11632@localhost>
References: <CAJHGrrQimUVqtRg6bowwBr5pxrSUh+mHkEzB0P1SBxP=nzczbg@mail.gmail.com> <57040B4A.4090301@pdmconsulting.net> <CAJHGrrSSD7o6Hy_3e8dNTOSTYF5MkyGo-Bn5SqHxa87XWqFpHQ@mail.gmail.com> <570411C0.7000004@ntp.org> <CAJHGrrR=-uN7dD5S0hBnF3Mt9ZrO8dC5YJK9k+D8j+WBFvByRg@mail.gmail.com> <E1anYbk-0002qu-8u@stenn.ntp.org> <20160406084046.GB9802@localhost> <E1anjUd-0003hc-Ho@stenn.ntp.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <E1anjUd-0003hc-Ho@stenn.ntp.org>
User-Agent: Mutt/1.5.24 (2015-08-30)
X-Scanned-By: MIMEDefang 2.68 on 10.5.11.23
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.16 (mx1.redhat.com [10.5.110.38]); Wed, 06 Apr 2016 10:39:14 +0000 (UTC)
Archived-At: <http://mailarchive.ietf.org/arch/msg/tictoc/9sBeNRcbaojOueGqSc2xtFSFPJw>
Cc: Sharon Goldberg <goldbe@cs.bu.edu>, NTP Working Group <ntpwg@lists.ntp.org>, tictoc@ietf.org
Subject: Re: [TICTOC] [ntpwg]  comments on draft-stenn-ntp-suggest-refid-00
X-BeenThere: tictoc@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Timing over IP Connection and Transfer of Clock BOF <tictoc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tictoc>, <mailto:tictoc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tictoc/>
List-Post: <mailto:tictoc@ietf.org>
List-Help: <mailto:tictoc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tictoc>, <mailto:tictoc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 06 Apr 2016 10:39:20 -0000

On Wed, Apr 06, 2016 at 09:11:19AM +0000, Harlan Stenn wrote:
> Miroslav Lichvar writes:
> > wiki. The attacker can probably restrict the list by geo location of
> > the client to a country zone with few hundred of servers at most. I
> > suspect in most cases the attacker would be able to succeed by sending
> > spoofed packets from all these servers.
> 
> How do you define "the attacker would be able to succeed" in this case?

Sending a packet that will be accepted by the client and disrupting
the synchronisation.

> Refclocks are increasingly easy to use, too, and this sort of
> knowledge/attack is not useful if somebody has a local refclock.

Well, if everyone had a reliable refclock, we wouldn't need NTP. :)

> > If there is a security issue with clients accepting spoofed packets, I
> > think it should be fixed directly instead of adding some security
> > through obscurity.
> 
> What do you suggest?  How does the current proposal make things worse in
> any way?

If the implementation follows the recommendation to change the refid
randomly, a client can't detect if it's talking to the same server as
its server for instance.

> > I'd rather see this extension field used as a way to improve the
> > robustness of the protocol.
> 
> Huh?  I think you are conflating things here.  The proposal is a
> *mechanism* and the value it contains is *policy*.

>From how I read the draft, it seems to suggest it's a security
mechanism. The word "attacker" is used quite a few times. I'd rather
see the proposal going in the other direction, giving clients a better
view of the NTP network instead of hiding information.

If you don't see the benefits, that's ok. I just thought I should
write my suggestions and see if anyone agrees with that.

> > As Danny pointed out, if servers announced
> > the same refid to all clients, they could reliably detect multihomed
> > hosts.
> 
> Then all a bad guy has to do is to send a time request to a target, see
> what refid it gets, and then use that knowledge as an attack vector.

If the client is fixed to not accept spoofed packets, what exactly the
attacker can do with that information?

> Also, there has been no demonstrated benefit that this "wider scope"
> loop detection will be of any useful value.
> 
> > My suggestion is to modify the field so it includes also refids of all
> > upstream servers. The clients could then prevent synchronisation loops
> > longer than 2. Loops between 3 peers polling one another can happen
> > easily and currently the best recommendation to prevent them is to
> > use a "line" configuration for the peers instead of a fully connected
> > mesh. Also, if the clients knew all upstream refids, they could detect
> > duplicate servers in the paths to the stratum 1 servers and ignore
> > them or decrease their weight.
> 
> Can you demonstrate tangible problems with the current scheme and
> tangible benefit with your solution?  Please also consider the security
> ramifications.

For instance, if the client knew the same stratum 1 server is used by
multiple stratum 3 servers and they didn't agree with other sources,
they could be rejected as one assuming the stratum 1 server is bad.

> I've seen lots of mesh setups - they have all worked fine.

I've received reports on loops forming between three peers that
were polling one another when they stopped receiving time from their
upstream sources. I was able to reproduce that. It's not a critical
issue, but I think it would be nice if NTP could prevent that.

-- 
Miroslav Lichvar


From nobody Wed Apr  6 12:55:13 2016
Return-Path: <jiangyuanlong@huawei.com>
X-Original-To: tictoc@ietfa.amsl.com
Delivered-To: tictoc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 797F612D62E for <tictoc@ietfa.amsl.com>; Wed,  6 Apr 2016 12:55:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.231
X-Spam-Level: 
X-Spam-Status: No, score=-4.231 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xweyjys0IszS for <tictoc@ietfa.amsl.com>; Wed,  6 Apr 2016 12:55:08 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8048E12D561 for <tictoc@ietf.org>; Wed,  6 Apr 2016 12:55:07 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml708-cah.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id CGY74562; Wed, 06 Apr 2016 19:55:05 +0000 (GMT)
Received: from SZXEMA411-HUB.china.huawei.com (10.82.72.70) by lhreml708-cah.china.huawei.com (10.201.5.202) with Microsoft SMTP Server (TLS) id 14.3.235.1; Wed, 6 Apr 2016 20:55:05 +0100
Received: from SZXEMA506-MBS.china.huawei.com ([169.254.4.160]) by szxema411-hub.china.huawei.com ([10.82.72.70]) with mapi id 14.03.0235.001; Thu, 7 Apr 2016 03:54:54 +0800
From: Jiangyuanlong <jiangyuanlong@huawei.com>
To: "ntpwg@lists.ntp.org" <ntpwg@lists.ntp.org>, "tictoc@ietf.org" <tictoc@ietf.org>
Thread-Topic: Non-WG Mailing List: Scsn -- Scalable Clock Synchronization Network- Discussion of Scalable Clock Synchronization Network
Thread-Index: AdGQPZcXxcd0J3IJRve4Kx7p/ZDHxg==
Date: Wed, 6 Apr 2016 19:54:53 +0000
Message-ID: <3B0A1BED22CAD649A1B3E97BE5DDD68B91686D4B@szxema506-mbs.china.huawei.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.212.197.56]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
X-Mirapoint-Virus-RAPID-Raw: score=unknown(0), refid=str=0001.0A090205.57056999.00A1, ss=1, re=0.000, recu=0.000, reip=0.000,  cl=1, cld=1, fgs=0, ip=169.254.4.160, so=2013-06-18 04:22:30, dmn=2013-03-21 17:37:32
X-Mirapoint-Loop-Id: 23be31e1952c13dca9709aa145a1f863
Archived-At: <http://mailarchive.ietf.org/arch/msg/tictoc/09NkJ7T74DfuQYQcgjhGWii3BQY>
Subject: [TICTOC] Non-WG Mailing List: Scsn -- Scalable Clock Synchronization Network- Discussion of Scalable Clock Synchronization Network
X-BeenThere: tictoc@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Timing over IP Connection and Transfer of Clock BOF <tictoc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tictoc>, <mailto:tictoc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tictoc/>
List-Post: <mailto:tictoc@ietf.org>
List-Help: <mailto:tictoc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tictoc>, <mailto:tictoc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 06 Apr 2016 19:55:11 -0000

Hi NTPers and TICTOCers,

You may have interest to join the SCSN mailing list, which is allocated to =
discuss the Scalable Clock Synchronization Network.

Following is the SCSN list information:

A new IETF non-working group email list has been created.

List address: scsn@ietf.org
Archive: https://mailarchive.ietf.org/arch/search/?email_list=3Dscsn
To subscribe: https://www.ietf.org/mailman/listinfo/scsn

Purpose:

The purpose of this mailing list is to discuss the operational and manageme=
nt challenges found in large-scale clock synchronization networks. There ap=
pear to be challenges in configuring, determining faults within, and monito=
ring the performance of such networks. Several examples of a large-scale cl=
ock synchronization network include mobile backhaul networks, industrial au=
tomation networks, and utility networks. Typically these networks employ IE=
EE 1588v2 and SyncE, which have been widely deployed in existing networks. =
The goal of these discussions is to determine if there is IETF-related work=
 needed to improve the management and operation of these clock synchronizat=
ion networks.

Regards,
Yuanlong


From nobody Wed Apr  6 13:20:55 2016
Return-Path: <hmurray@megapathdsl.net>
X-Original-To: tictoc@ietfa.amsl.com
Delivered-To: tictoc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2A53712D667 for <tictoc@ietfa.amsl.com>; Wed,  6 Apr 2016 13:20:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.033
X-Spam-Level: *
X-Spam-Status: No, score=1.033 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_DYNAMIC_IPADDR=1.951, RDNS_DYNAMIC=0.982] autolearn=no autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3d3YjRqsmp1Z for <tictoc@ietfa.amsl.com>; Wed,  6 Apr 2016 13:20:54 -0700 (PDT)
Received: from ip-64-139-1-69.sjc.megapath.net (ip-64-139-1-69.sjc.megapath.net [64.139.1.69]) by ietfa.amsl.com (Postfix) with ESMTP id 7D03112D0BC for <tictoc@ietf.org>; Wed,  6 Apr 2016 13:20:53 -0700 (PDT)
Received: from shuksan (localhost [127.0.0.1]) by ip-64-139-1-69.sjc.megapath.net (Postfix) with ESMTP id 43AB6406061; Wed,  6 Apr 2016 13:20:48 -0700 (PDT)
X-Mailer: exmh version 2.7.2 01/07/2005 with nmh-1.3
To: Miroslav Lichvar <mlichvar@redhat.com>
From: Hal Murray <hmurray@megapathdsl.net>
In-Reply-To: Message from Miroslav Lichvar <mlichvar@redhat.com> of "Wed, 06 Apr 2016 12:39:12 +0200." <20160406103912.GA11632@localhost>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Wed, 06 Apr 2016 13:20:48 -0700
Message-Id: <20160406202048.43AB6406061@ip-64-139-1-69.sjc.megapath.net>
Archived-At: <http://mailarchive.ietf.org/arch/msg/tictoc/x_ckS1hu5orxT21Nu4PWHd7BASI>
Cc: NTP Working Group <ntpwg@lists.ntp.org>, hmurray@megapathdsl.net, tictoc@ietf.org
Subject: Re: [TICTOC] [ntpwg]  comments on draft-stenn-ntp-suggest-refid-00
X-BeenThere: tictoc@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Timing over IP Connection and Transfer of Clock BOF <tictoc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tictoc>, <mailto:tictoc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tictoc/>
List-Post: <mailto:tictoc@ietf.org>
List-Help: <mailto:tictoc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tictoc>, <mailto:tictoc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 06 Apr 2016 20:20:55 -0000

[refid discussion]

mlichvar@redhat.com said:
> If you don't see the benefits, that's ok. I just thought I should write my
> suggestions and see if anyone agrees with that. 

I think that's an important idea.  We need to consider the trade-offs between 
security from hiding the real refid compared to the forensic value of being 
able to figure out what is or was going on.

On the other hand, I don't have a handful of stories where it has been 
helpful so maybe it isn't really important.  Is a warm-fuzzy feeling worth 
anything?
 


mlichvar@redhat.com said:
> If the client is fixed to not accept spoofed packets, what exactly the
> attacker can do with that information? 

It tells the bad guys one of the servers a system is using.  That is probably 
useful targeting information, either for DoS or for infiltration via phishing 
or exploit.


mlichvar@redhat.com said:
> I've received reports on loops forming between three peers that were polling
> one another when they stopped receiving time from their upstream sources. I
> was able to reproduce that. It's not a critical issue, but I think it would
> be nice if NTP could prevent that. 

Doesn't that case bump the stratum level each time around the loop until is 
falls off the end?


-- 
These are my opinions.  I hate spam.




From nobody Wed Apr  6 14:55:07 2016
Return-Path: <stenn@stenn.ntp.org>
X-Original-To: tictoc@ietfa.amsl.com
Delivered-To: tictoc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3F65412D53D for <tictoc@ietfa.amsl.com>; Wed,  6 Apr 2016 14:55:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level: 
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01] autolearn=unavailable autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id g0NyF6Kd1UvJ for <tictoc@ietfa.amsl.com>; Wed,  6 Apr 2016 14:55:03 -0700 (PDT)
Received: from stenn.ntp.org (stenn.ntp.org [149.20.68.30]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E229712D1E0 for <tictoc@ietf.org>; Wed,  6 Apr 2016 14:55:03 -0700 (PDT)
Received: from [::1] (helo=stenn.ntp.org) by stenn.ntp.org with esmtp (Exim 4.86_2 (FreeBSD)) (envelope-from <stenn@stenn.ntp.org>) id 1anvNF-0004Ro-NV; Wed, 06 Apr 2016 21:52:29 +0000
From: Harlan Stenn <stenn@ntp.org>
To: Miroslav Lichvar <mlichvar@redhat.com>
In-reply-to: <20160406103912.GA11632@localhost>
References: <CAJHGrrQimUVqtRg6bowwBr5pxrSUh+mHkEzB0P1SBxP=nzczbg@mail.gmail.com> <57040B4A.4090301@pdmconsulting.net> <CAJHGrrSSD7o6Hy_3e8dNTOSTYF5MkyGo-Bn5SqHxa87XWqFpHQ@mail.gmail.com> <570411C0.7000004@ntp.org> <CAJHGrrR=-uN7dD5S0hBnF3Mt9ZrO8dC5YJK9k+D8j+WBFvByRg@mail.gmail.com> <E1anYbk-0002qu-8u@stenn.ntp.org> <20160406084046.GB9802@localhost> <E1anjUd-0003hc-Ho@stenn.ntp.org> <20160406103912.GA11632@localhost>
Comments: In-reply-to Miroslav Lichvar <mlichvar@redhat.com> message dated "Wed, 06 Apr 2016 12:39:12 +0200."
X-Mailer: MH-E 7.4.2; nmh 1.6; XEmacs 21.4 (patch 24)
Mime-Version: 1.0 (generated by tm-edit 1.8)
Content-Type: text/plain; charset=US-ASCII
Date: Wed, 06 Apr 2016 21:52:29 +0000
Message-Id: <E1anvNF-0004Ro-NV@stenn.ntp.org>
Archived-At: <http://mailarchive.ietf.org/arch/msg/tictoc/VOujKjHEhqpCGzBzuua2Td7Kimg>
Cc: Sharon Goldberg <goldbe@cs.bu.edu>, Harlan Stenn <stenn@ntp.org>, tictoc@ietf.org, NTP Working Group <ntpwg@lists.ntp.org>
Subject: Re: [TICTOC] [ntpwg]  comments on draft-stenn-ntp-suggest-refid-00
X-BeenThere: tictoc@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Timing over IP Connection and Transfer of Clock BOF <tictoc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tictoc>, <mailto:tictoc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tictoc/>
List-Post: <mailto:tictoc@ietf.org>
List-Help: <mailto:tictoc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tictoc>, <mailto:tictoc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 06 Apr 2016 21:55:05 -0000

Miroslav Lichvar writes:
> On Wed, Apr 06, 2016 at 09:11:19AM +0000, Harlan Stenn wrote:
> > Miroslav Lichvar writes:
> > > wiki. The attacker can probably restrict the list by geo location of
> > > the client to a country zone with few hundred of servers at most. I
> > > suspect in most cases the attacker would be able to succeed by sending
> > > spoofed packets from all these servers.
> > 
> > How do you define "the attacker would be able to succeed" in this case?
> 
> Sending a packet that will be accepted by the client and disrupting
> the synchronisation.

I think we're approaching a workable definition there.  It depends on
"accepted by the client" and "disrupting".

To me, the goal of the protocol includes (and this needs more tweaking,
too):

- weed out flagrantly bad packets
- update some core peer state data
- perform  thorough packet checks
- if these checks pass, send the packet to the filters

Even then, bogus or otherwise bad packets will get thru.  The algorithms
are designed to deal with these problems.

> > Refclocks are increasingly easy to use, too, and this sort of
> > knowledge/attack is not useful if somebody has a local refclock.
> 
> Well, if everyone had a reliable refclock, we wouldn't need NTP. :)

I notice the smiley.  Even so, that's an incomplete, myopic, and
insufficient oversimplication.

> > > If there is a security issue with clients accepting spoofed packets, I
> > > think it should be fixed directly instead of adding some security
> > > through obscurity.
> > 
> > What do you suggest?  How does the current proposal make things worse in
> > any way?
> 
> If the implementation follows the recommendation to change the refid
> randomly, a client can't detect if it's talking to the same server as
> its server for instance.

I'm not seeing where you think the current proposal is worse in any way.

As for your response/suggestion, where is this recommendation to change
the refid randomly?

In the case where I suggest a refid and you choose me as your server and
use my suggested refid as your system peer, even if I change this on
every poll interval it will be pretty easy for me to track these random
refids and still detect a loop.  Yes, it means saving some state.  The
server suggesting the refid has control over if it uses the same refid
for everybody or not, and also for how often it chooses to change its
suggested refid.  This is a local policy choice.

Even if the client is broken and uses us as their server giving us a
refid we do not understand, in that case there will be a timing loop and
each poll interval the stratum on each side will increase.  Eventually,
these systems will either find another peer to get time from or they'll
both become unsync'd (because there is no other source of time).  This
is no different from A noticing that B is getting its time from A,
refusing to take time from B, and either getting time from somewhere
else or just changing its state to unsynch'd (S16).

> > > I'd rather see this extension field used as a way to improve the
> > > robustness of the protocol.
> > 
> > Huh?  I think you are conflating things here.  The proposal is a
> > *mechanism* and the value it contains is *policy*.
> 
> From how I read the draft, it seems to suggest it's a security
> mechanism. The word "attacker" is used quite a few times. I'd rather
> see the proposal going in the other direction, giving clients a better
> view of the NTP network instead of hiding information.

Yes, it's a security mechanism.  And please remember that we're trying
to get away from the expectation that an S2+ refid is an IPv4 address,
because that is increasingly incorrect.  Also note we're about to make
it easy to control "who can see what", so if you want to know who my
upstream server really is and you have the authorization to get that
information, that would be made available thru a mode 6 query.

> If you don't see the benefits, that's ok. I just thought I should
> write my suggestions and see if anyone agrees with that.

I wouldn't do what you and Danny are suggesting, but if you want to do
things that way it's your choice - that's why I'm saying my proposal
offers a mechanism, and while we'll provide a default policy choice on
what that suggested refid will be, there will also be mechanism in the
config file to allow you to specify your local policy on what that
suggested refid will be and the circumstances under which that
suggesteed refid will change.

> > > As Danny pointed out, if servers announced
> > > the same refid to all clients, they could reliably detect multihomed
> > > hosts.
> > 
> > Then all a bad guy has to do is to send a time request to a target, see
> > what refid it gets, and then use that knowledge as an attack vector.
> 
> If the client is fixed to not accept spoofed packets, what exactly the
> attacker can do with that information?

How can anybody detect that an incoming packet has a forged source
address?

> > Also, there has been no demonstrated benefit that this "wider scope"
> > loop detection will be of any useful value.
> > 
> > > My suggestion is to modify the field so it includes also refids of all
> > > upstream servers. The clients could then prevent synchronisation loops
> > > longer than 2. Loops between 3 peers polling one another can happen
> > > easily and currently the best recommendation to prevent them is to
> > > use a "line" configuration for the peers instead of a fully connected
> > > mesh. Also, if the clients knew all upstream refids, they could detect
> > > duplicate servers in the paths to the stratum 1 servers and ignore
> > > them or decrease their weight.
> > 
> > Can you demonstrate tangible problems with the current scheme and
> > tangible benefit with your solution?  Please also consider the security
> > ramifications.
> 
> For instance, if the client knew the same stratum 1 server is used by
> multiple stratum 3 servers and they didn't agree with other sources,
> they could be rejected as one assuming the stratum 1 server is bad.

How would you propose this work in practice?

This seems to be a special case of a Sybil attack.  I think the overhead
this would introduce would be huge and is better addressed elsewhere, by
proper monitoring and having enough upstream servers.

> > I've seen lots of mesh setups - they have all worked fine.
> 
> I've received reports on loops forming between three peers that
> were polling one another when they stopped receiving time from their
> upstream sources. I was able to reproduce that. It's not a critical
> issue, but I think it would be nice if NTP could prevent that.

Were these 3 machines the only source of time?  Are they set up in
orphan mode?

What would have happened if this loop had been prevented?

H


From nobody Wed Apr  6 22:49:58 2016
Return-Path: <stenn@stenn.ntp.org>
X-Original-To: tictoc@ietfa.amsl.com
Delivered-To: tictoc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0F44312D1EC for <tictoc@ietfa.amsl.com>; Wed,  6 Apr 2016 22:49:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level: 
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Pdgy_K1s-k1f for <tictoc@ietfa.amsl.com>; Wed,  6 Apr 2016 22:49:56 -0700 (PDT)
Received: from stenn.ntp.org (stenn.ntp.org [149.20.68.30]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E985B12D127 for <tictoc@ietf.org>; Wed,  6 Apr 2016 22:49:56 -0700 (PDT)
Received: from [::1] (helo=stenn.ntp.org) by stenn.ntp.org with esmtp (Exim 4.86_2 (FreeBSD)) (envelope-from <stenn@stenn.ntp.org>) id 1ao2o0-00053F-SP; Thu, 07 Apr 2016 05:48:36 +0000
From: Harlan Stenn <stenn@ntp.org>
To: Hal Murray <hmurray@megapathdsl.net>
In-reply-to: <20160406202048.43AB6406061@ip-64-139-1-69.sjc.megapath.net>
References: <20160406202048.43AB6406061@ip-64-139-1-69.sjc.megapath.net>
Comments: In-reply-to Hal Murray <hmurray@megapathdsl.net> message dated "Wed, 06 Apr 2016 13:20:48 -0700."
X-Mailer: MH-E 7.4.2; nmh 1.6; XEmacs 21.4 (patch 24)
Mime-Version: 1.0 (generated by tm-edit 1.8)
Content-Type: text/plain; charset=US-ASCII
Date: Thu, 07 Apr 2016 05:48:36 +0000
Message-Id: <E1ao2o0-00053F-SP@stenn.ntp.org>
Archived-At: <http://mailarchive.ietf.org/arch/msg/tictoc/yBc3yo3cwCcG_IKGHWJWgXVgZtE>
Cc: NTP Working Group <ntpwg@lists.ntp.org>, Miroslav Lichvar <mlichvar@redhat.com>, tictoc@ietf.org
Subject: Re: [TICTOC] [ntpwg]  comments on draft-stenn-ntp-suggest-refid-00
X-BeenThere: tictoc@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Timing over IP Connection and Transfer of Clock BOF <tictoc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tictoc>, <mailto:tictoc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tictoc/>
List-Post: <mailto:tictoc@ietf.org>
List-Help: <mailto:tictoc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tictoc>, <mailto:tictoc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 07 Apr 2016 05:49:58 -0000

Hal Murray writes:
> [refid discussion]
> 
> mlichvar@redhat.com said:
> > If you don't see the benefits, that's ok. I just thought I should write my
> > suggestions and see if anyone agrees with that. 
> 
> I think that's an important idea.  We need to consider the trade-offs
> between security from hiding the real refid compared to the forensic
> value of being able to figure out what is or was going on.

As I said before, the real source of time is available from a mode 6
query.

How can y'all not know this, even without my pointing it out?

H


From nobody Wed Apr  6 23:21:39 2016
Return-Path: <hmurray@megapathdsl.net>
X-Original-To: tictoc@ietfa.amsl.com
Delivered-To: tictoc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0B10712D569 for <tictoc@ietfa.amsl.com>; Wed,  6 Apr 2016 23:21:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.033
X-Spam-Level: *
X-Spam-Status: No, score=1.033 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_DYNAMIC_IPADDR=1.951, RDNS_DYNAMIC=0.982] autolearn=no autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QRjZtWBzGBZG for <tictoc@ietfa.amsl.com>; Wed,  6 Apr 2016 23:21:38 -0700 (PDT)
Received: from ip-64-139-1-69.sjc.megapath.net (ip-64-139-1-69.sjc.megapath.net [64.139.1.69]) by ietfa.amsl.com (Postfix) with ESMTP id 092D312D555 for <tictoc@ietf.org>; Wed,  6 Apr 2016 23:21:37 -0700 (PDT)
Received: from shuksan (localhost [127.0.0.1]) by ip-64-139-1-69.sjc.megapath.net (Postfix) with ESMTP id 2395D406074; Wed,  6 Apr 2016 23:21:37 -0700 (PDT)
X-Mailer: exmh version 2.7.2 01/07/2005 with nmh-1.3
To: Harlan Stenn <stenn@ntp.org>
From: Hal Murray <hmurray@megapathdsl.net>
In-Reply-To: Message from Harlan Stenn <stenn@ntp.org> of "Thu, 07 Apr 2016 05:48:36 -0000." <E1ao2o0-00053F-SP@stenn.ntp.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Wed, 06 Apr 2016 23:21:37 -0700
Message-Id: <20160407062137.2395D406074@ip-64-139-1-69.sjc.megapath.net>
Archived-At: <http://mailarchive.ietf.org/arch/msg/tictoc/XX5Yct3n763ErW-02-iWgqtts70>
Cc: NTP Working Group <ntpwg@lists.ntp.org>, Hal Murray <hmurray@megapathdsl.net>, tictoc@ietf.org
Subject: Re: [TICTOC] [ntpwg]  comments on draft-stenn-ntp-suggest-refid-00
X-BeenThere: tictoc@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Timing over IP Connection and Transfer of Clock BOF <tictoc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tictoc>, <mailto:tictoc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tictoc/>
List-Post: <mailto:tictoc@ietf.org>
List-Help: <mailto:tictoc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tictoc>, <mailto:tictoc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 07 Apr 2016 06:21:39 -0000

stenn@ntp.org said:
> As I said before, the real source of time is available from a mode 6 query. 

My system doesn't automatically log that.  The remove system probably does 
log it, but I probably don't have convenient access to those log files.

If the reason the remove server is hiding the real refid is to prevent the 
bad guys from figuring out which servers it is using, then mode 6 access is 
probably blocked.


-- 
These are my opinions.  I hate spam.




From nobody Wed Apr  6 23:38:10 2016
Return-Path: <stenn@stenn.ntp.org>
X-Original-To: tictoc@ietfa.amsl.com
Delivered-To: tictoc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BE09A12D56A for <tictoc@ietfa.amsl.com>; Wed,  6 Apr 2016 23:38:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level: 
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id esF4RnzZYSlQ for <tictoc@ietfa.amsl.com>; Wed,  6 Apr 2016 23:38:02 -0700 (PDT)
Received: from stenn.ntp.org (stenn.ntp.org [149.20.68.30]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 235FE12D555 for <tictoc@ietf.org>; Wed,  6 Apr 2016 23:38:02 -0700 (PDT)
Received: from [::1] (helo=stenn.ntp.org) by stenn.ntp.org with esmtp (Exim 4.86_2 (FreeBSD)) (envelope-from <stenn@stenn.ntp.org>) id 1ao3XO-00057A-Rw; Thu, 07 Apr 2016 06:35:30 +0000
From: Harlan Stenn <stenn@ntp.org>
To: Hal Murray <hmurray@megapathdsl.net>
In-reply-to: <20160407062137.2395D406074@ip-64-139-1-69.sjc.megapath.net>
References: <20160407062137.2395D406074@ip-64-139-1-69.sjc.megapath.net>
Comments: In-reply-to Hal Murray <hmurray@megapathdsl.net> message dated "Wed, 06 Apr 2016 23:21:37 -0700."
X-Mailer: MH-E 7.4.2; nmh 1.6; XEmacs 21.4 (patch 24)
Mime-Version: 1.0 (generated by tm-edit 1.8)
Content-Type: text/plain; charset=US-ASCII
Date: Thu, 07 Apr 2016 06:35:30 +0000
Message-Id: <E1ao3XO-00057A-Rw@stenn.ntp.org>
Archived-At: <http://mailarchive.ietf.org/arch/msg/tictoc/z0hLoZjl1HYxkNWTyE5qYJ9dpSA>
Cc: NTP Working Group <ntpwg@lists.ntp.org>, Harlan Stenn <stenn@ntp.org>, tictoc@ietf.org
Subject: Re: [TICTOC] [ntpwg]  comments on draft-stenn-ntp-suggest-refid-00
X-BeenThere: tictoc@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Timing over IP Connection and Transfer of Clock BOF <tictoc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tictoc>, <mailto:tictoc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tictoc/>
List-Post: <mailto:tictoc@ietf.org>
List-Help: <mailto:tictoc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tictoc>, <mailto:tictoc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 07 Apr 2016 06:38:08 -0000

Hal Murray writes:
> 
> stenn@ntp.org said:
> > As I said before, the real source of time is available from a mode 6 query.
>  
> 
> My system doesn't automatically log that.  The remove system probably
> does log it, but I probably don't have convenient access to those log
> files.

How did you get from a mode 6 query to a log file?

> If the reason the remove server is hiding the real refid is to prevent
> the bad guys from figuring out which servers it is using, then mode 6
> access is probably blocked.

a) the "real refid" is not being hidden.  The express purpose of the
refid is maintained.

b) if you have a valid reason for issuing mode 6 queries and the "other
side" doesn't choose to allow this, that's their policy choice.  In that
case you can continue to use them for time, or not.  Your policy choice.

H


From nobody Thu Apr  7 01:32:23 2016
Return-Path: <hmurray@megapathdsl.net>
X-Original-To: tictoc@ietfa.amsl.com
Delivered-To: tictoc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D3EC912D5CA for <tictoc@ietfa.amsl.com>; Thu,  7 Apr 2016 01:32:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.033
X-Spam-Level: *
X-Spam-Status: No, score=1.033 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_DYNAMIC_IPADDR=1.951, RDNS_DYNAMIC=0.982] autolearn=no autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id h2296Bs_y_Ix for <tictoc@ietfa.amsl.com>; Thu,  7 Apr 2016 01:32:22 -0700 (PDT)
Received: from ip-64-139-1-69.sjc.megapath.net (ip-64-139-1-69.sjc.megapath.net [64.139.1.69]) by ietfa.amsl.com (Postfix) with ESMTP id E67FA12D1E8 for <tictoc@ietf.org>; Thu,  7 Apr 2016 01:32:21 -0700 (PDT)
Received: from shuksan (localhost [127.0.0.1]) by ip-64-139-1-69.sjc.megapath.net (Postfix) with ESMTP id 1F3B2406074; Thu,  7 Apr 2016 01:32:21 -0700 (PDT)
X-Mailer: exmh version 2.7.2 01/07/2005 with nmh-1.3
To: Harlan Stenn <stenn@ntp.org>
From: Hal Murray <hmurray@megapathdsl.net>
In-Reply-To: Message from Harlan Stenn <stenn@ntp.org> of "Thu, 07 Apr 2016 06:35:30 -0000." <E1ao3XO-00057A-Rw@stenn.ntp.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Thu, 07 Apr 2016 01:32:21 -0700
Message-Id: <20160407083221.1F3B2406074@ip-64-139-1-69.sjc.megapath.net>
Archived-At: <http://mailarchive.ietf.org/arch/msg/tictoc/9uXrUC5V2cVKcXicXXLALfUS6iY>
Cc: NTP Working Group <ntpwg@lists.ntp.org>, Hal Murray <hmurray@megapathdsl.net>, tictoc@ietf.org
Subject: Re: [TICTOC] [ntpwg]  comments on draft-stenn-ntp-suggest-refid-00
X-BeenThere: tictoc@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Timing over IP Connection and Transfer of Clock BOF <tictoc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tictoc>, <mailto:tictoc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tictoc/>
List-Post: <mailto:tictoc@ietf.org>
List-Help: <mailto:tictoc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tictoc>, <mailto:tictoc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 07 Apr 2016 08:32:23 -0000

> How did you get from a mode 6 query to a log file?

You said I could get the real refid via mode 6,
  
The context I was thinking about was forensics.  I'm often interested in what 
has happened rather than what is happening.  In that case, all the evidence 
that is available is what's in the log files.


-- 
These are my opinions.  I hate spam.




From nobody Thu Apr  7 01:55:06 2016
Return-Path: <stenn@stenn.ntp.org>
X-Original-To: tictoc@ietfa.amsl.com
Delivered-To: tictoc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DE70B12D10E for <tictoc@ietfa.amsl.com>; Thu,  7 Apr 2016 01:55:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level: 
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id f2bBnhoVzXlo for <tictoc@ietfa.amsl.com>; Thu,  7 Apr 2016 01:55:03 -0700 (PDT)
Received: from stenn.ntp.org (stenn.ntp.org [149.20.68.30]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CFBDD12D105 for <tictoc@ietf.org>; Thu,  7 Apr 2016 01:55:03 -0700 (PDT)
Received: from [::1] (helo=stenn.ntp.org) by stenn.ntp.org with esmtp (Exim 4.86_2 (FreeBSD)) (envelope-from <stenn@stenn.ntp.org>) id 1ao5fz-0005GE-Mx; Thu, 07 Apr 2016 08:52:31 +0000
From: Harlan Stenn <stenn@ntp.org>
To: Hal Murray <hmurray@megapathdsl.net>
In-reply-to: <20160407083221.1F3B2406074@ip-64-139-1-69.sjc.megapath.net>
References: <20160407083221.1F3B2406074@ip-64-139-1-69.sjc.megapath.net>
Comments: In-reply-to Hal Murray <hmurray@megapathdsl.net> message dated "Thu, 07 Apr 2016 01:32:21 -0700."
X-Mailer: MH-E 7.4.2; nmh 1.6; XEmacs 21.4 (patch 24)
Mime-Version: 1.0 (generated by tm-edit 1.8)
Content-Type: text/plain; charset=US-ASCII
Date: Thu, 07 Apr 2016 08:52:31 +0000
Message-Id: <E1ao5fz-0005GE-Mx@stenn.ntp.org>
Archived-At: <http://mailarchive.ietf.org/arch/msg/tictoc/IJclI_RyCTjPuBS9giLbMV440eA>
Cc: NTP Working Group <ntpwg@lists.ntp.org>, Harlan Stenn <stenn@ntp.org>, tictoc@ietf.org
Subject: Re: [TICTOC] [ntpwg]  comments on draft-stenn-ntp-suggest-refid-00
X-BeenThere: tictoc@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Timing over IP Connection and Transfer of Clock BOF <tictoc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tictoc>, <mailto:tictoc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tictoc/>
List-Post: <mailto:tictoc@ietf.org>
List-Help: <mailto:tictoc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tictoc>, <mailto:tictoc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 07 Apr 2016 08:55:05 -0000

Hal Murray writes:
> > How did you get from a mode 6 query to a log file?
> 
> You said I could get the real refid via mode 6,

No, I said you could get the address of the upstream peer with mode 6.

> The context I was thinking about was forensics.  I'm often interested
> in what has happened rather than what is happening.  In that case, all
> the evidence that is available is what's in the log files.

That may be OK with IPv4 refids, but how do the current logfiles help
you with IPv6-based refids?

H


From nobody Thu Apr  7 01:57:10 2016
Return-Path: <mlichvar@redhat.com>
X-Original-To: tictoc@ietfa.amsl.com
Delivered-To: tictoc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CDE1612D53D for <tictoc@ietfa.amsl.com>; Thu,  7 Apr 2016 01:57:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.932
X-Spam-Level: 
X-Spam-Status: No, score=-6.932 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id c0ebmJ8PhhCz for <tictoc@ietfa.amsl.com>; Thu,  7 Apr 2016 01:57:08 -0700 (PDT)
Received: from mx1.redhat.com (mx1.redhat.com [209.132.183.28]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 605B612D10E for <tictoc@ietf.org>; Thu,  7 Apr 2016 01:57:08 -0700 (PDT)
Received: from int-mx14.intmail.prod.int.phx2.redhat.com (int-mx14.intmail.prod.int.phx2.redhat.com [10.5.11.27]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.redhat.com (Postfix) with ESMTPS id 2464DC04B319; Thu,  7 Apr 2016 08:57:08 +0000 (UTC)
Received: from localhost (dhcp-24-154.brq.redhat.com [10.34.24.154]) by int-mx14.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4) with ESMTP id u378v7jU005673; Thu, 7 Apr 2016 04:57:07 -0400
Date: Thu, 7 Apr 2016 10:57:06 +0200
From: Miroslav Lichvar <mlichvar@redhat.com>
To: Hal Murray <hmurray@megapathdsl.net>
Message-ID: <20160407085706.GC20410@localhost>
References: <mlichvar@redhat.com> <20160406103912.GA11632@localhost> <20160406202048.43AB6406061@ip-64-139-1-69.sjc.megapath.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20160406202048.43AB6406061@ip-64-139-1-69.sjc.megapath.net>
User-Agent: Mutt/1.5.24 (2015-08-30)
X-Scanned-By: MIMEDefang 2.68 on 10.5.11.27
Archived-At: <http://mailarchive.ietf.org/arch/msg/tictoc/Ta-fSzadP-4wWjbHotISciTfif8>
Cc: NTP Working Group <ntpwg@lists.ntp.org>, tictoc@ietf.org
Subject: Re: [TICTOC] [ntpwg]  comments on draft-stenn-ntp-suggest-refid-00
X-BeenThere: tictoc@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Timing over IP Connection and Transfer of Clock BOF <tictoc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tictoc>, <mailto:tictoc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tictoc/>
List-Post: <mailto:tictoc@ietf.org>
List-Help: <mailto:tictoc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tictoc>, <mailto:tictoc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 07 Apr 2016 08:57:10 -0000

On Wed, Apr 06, 2016 at 01:20:48PM -0700, Hal Murray wrote:
> mlichvar@redhat.com said:
> > If you don't see the benefits, that's ok. I just thought I should write my
> > suggestions and see if anyone agrees with that. 
> 
> I think that's an important idea.  We need to consider the trade-offs between 
> security from hiding the real refid compared to the forensic value of being 
> able to figure out what is or was going on.

I agree.

> On the other hand, I don't have a handful of stories where it has been 
> helpful so maybe it isn't really important.  Is a warm-fuzzy feeling worth 
> anything?

I think it could be more than just a warm-fuzzy feeling. I think
knowing refids up to stratum 1 could be useful for NTP clients to make
better decision in the source selection and also for administrators
when debugging problems.

Harlan referred to mode 6. That's not always available. It's not a
part of the current NTPv4 spec (it was optional in the NTPv3 spec) and
AFAIK only ntpd implements it. Also, on servers accessible from
Internet it's normally disabled as it allows amplification.

> mlichvar@redhat.com said:
> > I've received reports on loops forming between three peers that were polling
> > one another when they stopped receiving time from their upstream sources. I
> > was able to reproduce that. It's not a critical issue, but I think it would
> > be nice if NTP could prevent that. 
> 
> Doesn't that case bump the stratum level each time around the loop until is 
> falls off the end?

It does. The trouble is that unless the servers have a local reference
enabled (e.g. orphan mode), they will stuck to stratum 16, 15, ... and
will be unusable for clients one, two, ... layers below.

As I said, I don't think it's a huge deal, but it would be nice if NTP
could prevent that.

-- 
Miroslav Lichvar


From nobody Thu Apr  7 02:39:11 2016
Return-Path: <mlichvar@redhat.com>
X-Original-To: tictoc@ietfa.amsl.com
Delivered-To: tictoc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 58B9C12D0EC for <tictoc@ietfa.amsl.com>; Thu,  7 Apr 2016 02:39:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.932
X-Spam-Level: 
X-Spam-Status: No, score=-6.932 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0jnN0v45v9SA for <tictoc@ietfa.amsl.com>; Thu,  7 Apr 2016 02:39:07 -0700 (PDT)
Received: from mx1.redhat.com (mx1.redhat.com [209.132.183.28]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C369612D0DC for <tictoc@ietf.org>; Thu,  7 Apr 2016 02:39:07 -0700 (PDT)
Received: from int-mx11.intmail.prod.int.phx2.redhat.com (int-mx11.intmail.prod.int.phx2.redhat.com [10.5.11.24]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.redhat.com (Postfix) with ESMTPS id 2BA1FD571A; Thu,  7 Apr 2016 09:39:07 +0000 (UTC)
Received: from localhost (dhcp-24-154.brq.redhat.com [10.34.24.154]) by int-mx11.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4) with ESMTP id u379WPqQ032046; Thu, 7 Apr 2016 05:32:32 -0400
Date: Thu, 7 Apr 2016 11:32:25 +0200
From: Miroslav Lichvar <mlichvar@redhat.com>
To: Harlan Stenn <stenn@ntp.org>
Message-ID: <20160407093225.GD20410@localhost>
References: <CAJHGrrQimUVqtRg6bowwBr5pxrSUh+mHkEzB0P1SBxP=nzczbg@mail.gmail.com> <57040B4A.4090301@pdmconsulting.net> <CAJHGrrSSD7o6Hy_3e8dNTOSTYF5MkyGo-Bn5SqHxa87XWqFpHQ@mail.gmail.com> <570411C0.7000004@ntp.org> <CAJHGrrR=-uN7dD5S0hBnF3Mt9ZrO8dC5YJK9k+D8j+WBFvByRg@mail.gmail.com> <E1anYbk-0002qu-8u@stenn.ntp.org> <20160406084046.GB9802@localhost> <E1anjUd-0003hc-Ho@stenn.ntp.org> <20160406103912.GA11632@localhost> <E1anvNF-0004Ro-NV@stenn.ntp.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <E1anvNF-0004Ro-NV@stenn.ntp.org>
User-Agent: Mutt/1.5.24 (2015-08-30)
X-Scanned-By: MIMEDefang 2.68 on 10.5.11.24
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.16 (mx1.redhat.com [10.5.110.38]); Thu, 07 Apr 2016 09:39:07 +0000 (UTC)
Archived-At: <http://mailarchive.ietf.org/arch/msg/tictoc/yBB5npwPMYxJ4r4XeQEGN9bDiSc>
Cc: Sharon Goldberg <goldbe@cs.bu.edu>, NTP Working Group <ntpwg@lists.ntp.org>, tictoc@ietf.org
Subject: Re: [TICTOC] [ntpwg]  comments on draft-stenn-ntp-suggest-refid-00
X-BeenThere: tictoc@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Timing over IP Connection and Transfer of Clock BOF <tictoc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tictoc>, <mailto:tictoc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tictoc/>
List-Post: <mailto:tictoc@ietf.org>
List-Help: <mailto:tictoc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tictoc>, <mailto:tictoc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 07 Apr 2016 09:39:09 -0000

On Wed, Apr 06, 2016 at 09:52:29PM +0000, Harlan Stenn wrote:
> Miroslav Lichvar writes:
> > If the implementation follows the recommendation to change the refid
> > randomly, a client can't detect if it's talking to the same server as
> > its server for instance.
> 
> I'm not seeing where you think the current proposal is worse in any way.
> 
> As for your response/suggestion, where is this recommendation to change
> the refid randomly?

Your draft says:
  A system that decides to send a Suggested REFID extension field
  SHOULD generate a new Suggested REFID for each new association.

I'm assuming this is about client associations distinguished by IP
address (ignoring the fact the multiple clients may be behind one
address). If the server sends different refids to different clients,
the clients won't be able to detect that they are a client of another
client of the same server.

Older ntpd versions had a check for that. While we may argue about how
useful it really is, it will no longer be possible if the suggestion
is implemented.

> > If the client is fixed to not accept spoofed packets, what exactly the
> > attacker can do with that information?
> 
> How can anybody detect that an incoming packet has a forged source
> address?

The cookie (aka origin timestamp) in the reply doesn't match the request.

> > For instance, if the client knew the same stratum 1 server is used by
> > multiple stratum 3 servers and they didn't agree with other sources,
> > they could be rejected as one assuming the stratum 1 server is bad.
> 
> How would you propose this work in practice?
> 
> This seems to be a special case of a Sybil attack.  I think the overhead
> this would introduce would be huge and is better addressed elsewhere, by
> proper monitoring and having enough upstream servers.

It would complicate the selection algorithm, no doubt about that,
but that's the choice of the implementation.

> > I've received reports on loops forming between three peers that
> > were polling one another when they stopped receiving time from their
> > upstream sources. I was able to reproduce that. It's not a critical
> > issue, but I think it would be nice if NTP could prevent that.
> 
> Were these 3 machines the only source of time?

Yes.

> Are they set up in orphan mode?

No.

> What would have happened if this loop had been prevented?

Alarms monitoring the synchronisation would not be triggered. The
servers would stay in a synchronised state with a real reference and
could be used by their clients and clients of their clients for few
hours until the upstream servers were reachable again.

-- 
Miroslav Lichvar


From nobody Thu Apr  7 03:29:16 2016
Return-Path: <sharon.goldbe@gmail.com>
X-Original-To: tictoc@ietfa.amsl.com
Delivered-To: tictoc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1545412D696 for <tictoc@ietfa.amsl.com>; Thu,  7 Apr 2016 03:29:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.399
X-Spam-Level: 
X-Spam-Status: No, score=-2.399 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.199, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ESU1uZsGCbhR for <tictoc@ietfa.amsl.com>; Thu,  7 Apr 2016 03:29:08 -0700 (PDT)
Received: from mail-wm0-x236.google.com (mail-wm0-x236.google.com [IPv6:2a00:1450:400c:c09::236]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6876C12D0F7 for <tictoc@ietf.org>; Thu,  7 Apr 2016 03:29:08 -0700 (PDT)
Received: by mail-wm0-x236.google.com with SMTP id u206so80854427wme.1 for <tictoc@ietf.org>; Thu, 07 Apr 2016 03:29:08 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=7Xe323ZiUSfYcVUHqIl0PcjrJfm7j7/REYPR2uc+65Q=; b=moQO7wjfoOTwvh18uZ9qZTXToNJvY7sU9ulpBbh0ubPk0ujU+9pSiboI8SBybJ7ZWr bYxBRHUN71QgyPHAJEV5WtJ+LcLN2fZ8KLYGKiDQqqxWtdkZCWHDpGs8AFms8jrIkZ/n YIADuXT+XjLYTWQtX7BfXq9gmyXcRzUsJxAC/18Aw56KQqL9D8uAnDq2vIad3wTkCjUX /3jmKABEBZKPLCrxUtZyuzzR4uaPkCWmxmf4/5oFDnxi//FCr2Szk6HXgo6IQaDH4gtQ S/8zxpssBwEjAOAA7CO8lxveLS5igCjKQ1vCooPofuQ+afKkmSb/kq21pfplTXNbJxG4 qLgg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=7Xe323ZiUSfYcVUHqIl0PcjrJfm7j7/REYPR2uc+65Q=; b=mpngB3j8AtFsfuzKA+7A8JOzCQouOLJ37kjdSy2cKTKFMftAOvvzSZjll0+aBpHqdH aPOoehLwIsth/itHZEvzW6hBl16LFZ8D7/hl/yn7Eg65Po8ZprXWdpq4IKQ+XkFnk766 9iIm2bxk55kerfSJd7m8qaZbVv9R5wx4ZuBokxzEWdU1q5zLlWax2VPjfU2UnFE6PlAh +E/yCaU4UVTfvLdoab62q9zsHUedfvjaNDESUWlveruDWr5GvQRqZLn6Rg91bS+4RbUa XmEvHM3Mf0FOnrzD69Yd33zz2muLduTwUkQXCzRf2rolr6Ux9/V1eCNzedC5YD0q/cTc AOxw==
X-Gm-Message-State: AD7BkJKH6Hu2nisccpcgl2WrKOs1pv/VKqo2boCfDY+i+w4N4YqYzdsi74SUTUE/MMoYUZ0qOwb+0b9wQk1M9w==
X-Received: by 10.28.54.148 with SMTP id y20mr3073247wmh.68.1460024946887; Thu, 07 Apr 2016 03:29:06 -0700 (PDT)
MIME-Version: 1.0
Sender: sharon.goldbe@gmail.com
Received: by 10.194.71.200 with HTTP; Thu, 7 Apr 2016 03:28:27 -0700 (PDT)
In-Reply-To: <20160407093225.GD20410@localhost>
References: <CAJHGrrQimUVqtRg6bowwBr5pxrSUh+mHkEzB0P1SBxP=nzczbg@mail.gmail.com> <57040B4A.4090301@pdmconsulting.net> <CAJHGrrSSD7o6Hy_3e8dNTOSTYF5MkyGo-Bn5SqHxa87XWqFpHQ@mail.gmail.com> <570411C0.7000004@ntp.org> <CAJHGrrR=-uN7dD5S0hBnF3Mt9ZrO8dC5YJK9k+D8j+WBFvByRg@mail.gmail.com> <E1anYbk-0002qu-8u@stenn.ntp.org> <20160406084046.GB9802@localhost> <E1anjUd-0003hc-Ho@stenn.ntp.org> <20160406103912.GA11632@localhost> <E1anvNF-0004Ro-NV@stenn.ntp.org> <20160407093225.GD20410@localhost>
From: Sharon Goldberg <goldbe@cs.bu.edu>
Date: Thu, 7 Apr 2016 06:28:27 -0400
X-Google-Sender-Auth: 2QwRSil116QKgvFNV82524C07v4
Message-ID: <CAJHGrrQs=amt6yLeoz+mta_wDRsfCbTtZUruudox7VJesVq9nQ@mail.gmail.com>
To: NTP Working Group <ntpwg@lists.ntp.org>
Content-Type: multipart/alternative; boundary=001a1142b68e529239052fe28ce7
Archived-At: <http://mailarchive.ietf.org/arch/msg/tictoc/0Mq1MOspM02hPPrx6UoMuKTwH1w>
Cc: Miroslav Lichvar <mlichvar@redhat.com>, Matthew Van Gundy <mvangund@cisco.com>, tictoc@ietf.org
Subject: Re: [TICTOC] [ntpwg]  comments on draft-stenn-ntp-suggest-refid-00
X-BeenThere: tictoc@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Timing over IP Connection and Transfer of Clock BOF <tictoc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tictoc>, <mailto:tictoc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tictoc/>
List-Post: <mailto:tictoc@ietf.org>
List-Help: <mailto:tictoc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tictoc>, <mailto:tictoc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 07 Apr 2016 10:29:15 -0000

--001a1142b68e529239052fe28ce7
Content-Type: text/plain; charset=UTF-8

My proposal is orthogonal to what is being discussed here.   I believe it
can be implemented alongside Harlan's proposal in suggest-refid.

I want to emphasize that my proposal is backwards compatible and can be
implemented today without an extension field.  Whereas Harlan's idea is
super clever but it requires both the client and the server to understand
an extension field.

First off, to reiterate why I care about this, pretty much all the off-path
attacks that we and Cisco have done have the following first step:

Query the target client. Get the response. Learn its refID. Now you know
the client's server. $Attack the server. (Potentially rinse and repeat if
the client moves to another server.)

Sure, mode 6 reveals this information but modern NTP configurations should
prevent remote IPs from launching mode 6 queries, as it is not only an
amplification vector and also leaks state making it easier to attack the
system.  (See also Cisco's "origin leak" bug [1].)  So I do not have a
"warm fuzzy" feeling when I see NTP leaking information. Especially since
most NTP traffic is not usually cryptographically protected.  I think NTP
should leak less information, not more.

My proposal offers a backwards compatible way for a system to limit the
information leaked in its reference ID. It solves the IPv6 refID collision
problem.  And it seems to be compatible with what NTP is doing today.

Some exceptions could be made for stratum 1 servers to broadcast to all
clients that your refID is GPS or some other external source, if this
really a problem.  But we should be sure its really a problem, because
information leakage always makes it easier to launch attacks.

Much of this discussion has been regarding a future use case in which a
client had two IP addresses B and C.   This client sends a query from
interface B and wants to make sure it is not in a timing loop with another
system A who is taking time from interface B.

One could deal with this usecase using Harlan's proposal, but this does not
preclude my proposal running in parallel.  To deal with this, the client "B
and C"  uses Harlan's extension field to signal "if you take time from me,
put this nonce as your refID."   If it decided to signal the *same* nonce
to all clients, it has explicitly taken on the risk than an attacker can
use this information as a first step in an attack, as I have described
above.  If it signals a different nonce to all clients, then it is
protected from this.

This non-backwards compatible feature would therefore only be used by
systems that need it, eg those that have two IP addresses. All other
systems could limit the amount of information being leaked in their refID
by using my proposal.

Sharon

[1] http://www.talosintel.com/reports/TALOS-2016-0078/

--001a1142b68e529239052fe28ce7
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div><div><div><div>My proposal is orthogonal to what is b=
eing discussed here.=C2=A0=C2=A0 I believe it can be implemented alongside =
Harlan&#39;s proposal in suggest-refid.<br><br>I want to emphasize that my =
proposal is backwards compatible and can be implemented today without an ex=
tension field.=C2=A0 Whereas Harlan&#39;s idea is super clever but it requi=
res both the client and the server to understand an extension field.<br></d=
iv><br>First off, to reiterate why I care about this, pretty much all the o=
ff-path attacks that we and Cisco have done have the following first step:<=
br><br></div>Query the target client. Get the response. Learn its refID. No=
w you know the client&#39;s server. $Attack the server. (Potentially rinse =
and repeat if the client moves to another server.)<br><br></div><div>Sure, =
mode 6 reveals this information but modern NTP configurations should preven=
t remote IPs from launching mode 6 queries, as it is not only an amplificat=
ion vector and also leaks state making it easier to attack the system.=C2=
=A0 (See also Cisco&#39;s &quot;origin leak&quot; bug [1].)=C2=A0 So I do n=
ot have a &quot;warm fuzzy&quot; feeling when I see NTP leaking information=
. Especially since most NTP traffic is not usually cryptographically protec=
ted.=C2=A0 I think NTP should leak less information, not more.<br><br></div=
><div>My proposal offers a backwards compatible way for a system to limit t=
he information leaked in its reference ID. It solves the IPv6 refID collisi=
on problem.=C2=A0 And it seems to be compatible with what NTP is doing toda=
y.<br></div><div><div><br></div>Some exceptions could be made for stratum 1=
 servers=20
to broadcast to all clients that your refID is GPS or some other=20
external source, if this really a problem.=C2=A0 But we should be sure its=
=20
really a problem, because information leakage always makes it easier to=20
launch attacks. <br><br></div><div>Much of this discussion has been regardi=
ng a future use case in which a client had two IP addresses B and C.=C2=A0=
=C2=A0 This client sends a query from interface B and wants to make sure it
 is not in a timing loop with another system A who is taking time from=20
interface B.=C2=A0 <br><br>One could deal with this usecase using Harlan&#3=
9;s proposal, but this does not preclude my proposal running in parallel.=
=C2=A0 To deal with this, the client &quot;B and C&quot;=C2=A0 uses Harlan&=
#39;s extension field to signal &quot;if you take time from me, put this no=
nce as your refID.&quot;=C2=A0=C2=A0 If it decided to signal the *same* non=
ce to all clients, it has explicitly taken on the risk than an attacker can=
 use this information as a first step in an attack, as I have described abo=
ve.=C2=A0 If it signals a different nonce to all clients, then it is protec=
ted from this.</div><br></div>This non-backwards compatible feature would t=
herefore only be used by systems that need it, eg those that have two IP ad=
dresses. All other systems could limit the amount of information being leak=
ed in their refID by using my proposal.<br><div><br><div>Sharon<br><br>[1] =
<a href=3D"http://www.talosintel.com/reports/TALOS-2016-0078/">http://www.t=
alosintel.com/reports/TALOS-2016-0078/</a><br></div><br><div><br></div></di=
v></div>

--001a1142b68e529239052fe28ce7--


From nobody Thu Apr  7 10:48:26 2016
Return-Path: <mayer@pdmconsulting.net>
X-Original-To: tictoc@ietfa.amsl.com
Delivered-To: tictoc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0DF8D12D5B3 for <tictoc@ietfa.amsl.com>; Thu,  7 Apr 2016 10:48:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BnRwiMOLcvDc for <tictoc@ietfa.amsl.com>; Thu,  7 Apr 2016 10:48:22 -0700 (PDT)
Received: from chessie.everett.org (chessie.everett.org [66.220.13.234]) by ietfa.amsl.com (Postfix) with ESMTP id B41D912D586 for <tictoc@ietf.org>; Thu,  7 Apr 2016 10:48:22 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by chessie.everett.org (Postfix) with SMTP id D6810B82C for <tictoc@ietf.org>; Thu,  7 Apr 2016 17:48:21 +0000 (UTC)
Received: from [10.2.64.150] (unknown [198.22.153.36]) by chessie.everett.org (Postfix) with ESMTPSA id BE6CAB80E; Thu,  7 Apr 2016 17:48:19 +0000 (UTC)
References: <CAJHGrrQimUVqtRg6bowwBr5pxrSUh+mHkEzB0P1SBxP=nzczbg@mail.gmail.com> <57040B4A.4090301@pdmconsulting.net> <CAJHGrrSSD7o6Hy_3e8dNTOSTYF5MkyGo-Bn5SqHxa87XWqFpHQ@mail.gmail.com> <570411C0.7000004@ntp.org> <CAJHGrrR=-uN7dD5S0hBnF3Mt9ZrO8dC5YJK9k+D8j+WBFvByRg@mail.gmail.com> <E1anYbk-0002qu-8u@stenn.ntp.org> <20160406084046.GB9802@localhost> <E1anjUd-0003hc-Ho@stenn.ntp.org> <20160406103912.GA11632@localhost> <E1anvNF-0004Ro-NV@stenn.ntp.org> <20160407093225.GD20410@localhost> <CAJHGrrQs=amt6yLeoz+mta_wDRsfCbTtZUruudox7VJesVq9nQ@mail.gmail.com>
To: Sharon Goldberg <goldbe@cs.bu.edu>, NTP Working Group <ntpwg@lists.ntp.org>
From: Danny Mayer <mayer@pdmconsulting.net>
Message-ID: <57069D6A.8030407@pdmconsulting.net>
Date: Thu, 7 Apr 2016 13:48:26 -0400
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.7.2
MIME-Version: 1.0
In-Reply-To: <CAJHGrrQs=amt6yLeoz+mta_wDRsfCbTtZUruudox7VJesVq9nQ@mail.gmail.com>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 7bit
X-DSPAM-Result: Innocent
X-DSPAM-Processed: Thu Apr  7 17:48:21 2016
X-DSPAM-Confidence: 0.9899
X-DSPAM-Probability: 0.0000
X-DSPAM-Signature: 7205,57069d65829937583220277
Archived-At: <http://mailarchive.ietf.org/arch/msg/tictoc/48hluRLEd1Z0lC02XB1pe2blyHI>
Cc: Miroslav Lichvar <mlichvar@redhat.com>, Matthew Van Gundy <mvangund@cisco.com>, tictoc@ietf.org
Subject: Re: [TICTOC] [ntpwg] comments on draft-stenn-ntp-suggest-refid-00
X-BeenThere: tictoc@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
Reply-To: mayer@pdmconsulting.net
List-Id: Timing over IP Connection and Transfer of Clock BOF <tictoc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tictoc>, <mailto:tictoc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tictoc/>
List-Post: <mailto:tictoc@ietf.org>
List-Help: <mailto:tictoc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tictoc>, <mailto:tictoc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 07 Apr 2016 17:48:24 -0000

On 4/7/2016 6:28 AM, Sharon Goldberg wrote:
> 
> This non-backwards compatible feature would therefore only be used by
> systems that need it, eg those that have two IP addresses. All other
> systems could limit the amount of information being leaked in their
> refID by using my proposal.
> 

The number of systems that don't have multiple addresses these days can
probably be counted on one hand. All newer O/S's support both IPv4 and
IPv6 addresses. Furthermore NTP has broadcast and multicast modes so
packets can also arrive over those addresses as well.

Harlan and I had a discussion on this yesterday and now I remember why
the current preferred server's address is being used in the refID. At
the time it was implemented it was meant to prevent timing loops and
security was not a worry. In today's world that's the primary worry.

Danny


From nobody Thu Apr  7 11:31:24 2016
Return-Path: <mayer@ntp.org>
X-Original-To: tictoc@ietfa.amsl.com
Delivered-To: tictoc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 95E4612D6A1 for <tictoc@ietfa.amsl.com>; Thu,  7 Apr 2016 11:31:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level: 
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RWNLqBmykr17 for <tictoc@ietfa.amsl.com>; Thu,  7 Apr 2016 11:31:16 -0700 (PDT)
Received: from mail1.ntp.org (mail1.ntp.org [IPv6:2001:4f8:fff7:1::5]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 40A0512D69B for <tictoc@ietf.org>; Thu,  7 Apr 2016 11:31:16 -0700 (PDT)
Received: from [198.22.153.36] (helo=[10.2.64.150]) by mail1.ntp.org with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.77 (FreeBSD)) (envelope-from <mayer@ntp.org>) id 1aoEi3-000C7G-0C; Thu, 07 Apr 2016 18:31:16 +0000
From: Danny Mayer <mayer@ntp.org>
References: <CAJHGrrQimUVqtRg6bowwBr5pxrSUh+mHkEzB0P1SBxP=nzczbg@mail.gmail.com> <57040B4A.4090301@pdmconsulting.net> <CAJHGrrSSD7o6Hy_3e8dNTOSTYF5MkyGo-Bn5SqHxa87XWqFpHQ@mail.gmail.com> <570411C0.7000004@ntp.org> <CAJHGrrR=-uN7dD5S0hBnF3Mt9ZrO8dC5YJK9k+D8j+WBFvByRg@mail.gmail.com> <E1anYbk-0002qu-8u@stenn.ntp.org> <20160406084046.GB9802@localhost> <E1anjUd-0003hc-Ho@stenn.ntp.org> <20160406103912.GA11632@localhost> <E1anvNF-0004Ro-NV@stenn.ntp.org> <20160407093225.GD20410@localhost> <CAJHGrrQs=amt6yLeoz+mta_wDRsfCbTtZUruudox7VJesVq9nQ@mail.gmail.com>
To: Sharon Goldberg <goldbe@cs.bu.edu>, NTP Working Group <ntpwg@lists.ntp.org>
Organization: NTP
Message-ID: <5706A779.8030505@ntp.org>
Date: Thu, 7 Apr 2016 14:31:21 -0400
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.7.2
MIME-Version: 1.0
In-Reply-To: <CAJHGrrQs=amt6yLeoz+mta_wDRsfCbTtZUruudox7VJesVq9nQ@mail.gmail.com>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 7bit
X-SA-Exim-Connect-IP: 198.22.153.36
X-SA-Exim-Rcpt-To: tictoc@ietf.org, mvangund@cisco.com, mlichvar@redhat.com, ntpwg@lists.ntp.org, goldbe@cs.bu.edu
X-SA-Exim-Mail-From: mayer@ntp.org
X-SA-Exim-Version: 4.2
X-SA-Exim-Scanned: Yes (on mail1.ntp.org)
Archived-At: <http://mailarchive.ietf.org/arch/msg/tictoc/mPxFipi5ri3M3m9p2Wx7qFO6bNM>
Cc: Miroslav Lichvar <mlichvar@redhat.com>, Matthew Van Gundy <mvangund@cisco.com>, tictoc@ietf.org
Subject: Re: [TICTOC] [ntpwg] comments on draft-stenn-ntp-suggest-refid-00
X-BeenThere: tictoc@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
Reply-To: mayer@ntp.org
List-Id: Timing over IP Connection and Transfer of Clock BOF <tictoc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tictoc>, <mailto:tictoc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tictoc/>
List-Post: <mailto:tictoc@ietf.org>
List-Help: <mailto:tictoc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tictoc>, <mailto:tictoc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 07 Apr 2016 18:31:23 -0000

On 4/7/2016 6:28 AM, Sharon Goldberg wrote:
> 
> This non-backwards compatible feature would therefore only be used by
> systems that need it, eg those that have two IP addresses. All other
> systems could limit the amount of information being leaked in their
> refID by using my proposal.
> 

The number of systems that don't have multiple addresses these days can
probably be counted on one hand. All newer O/S's support both IPv4 and
IPv6 addresses. Furthermore NTP has broadcast and multicast modes so
packets can also arrive over those addresses as well.

Harlan and I had a discussion on this yesterday and now I remember why
the current preferred server's address is being used in the refID. At
the time it was implemented it was meant to prevent timing loops and
security was not a worry. In today's world that's the primary worry.

Danny


From nobody Thu Apr  7 11:54:33 2016
Return-Path: <stenn@stenn.ntp.org>
X-Original-To: tictoc@ietfa.amsl.com
Delivered-To: tictoc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9B97212D66E for <tictoc@ietfa.amsl.com>; Thu,  7 Apr 2016 11:54:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level: 
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01] autolearn=unavailable autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mzIyat5fqZeY for <tictoc@ietfa.amsl.com>; Thu,  7 Apr 2016 11:54:21 -0700 (PDT)
Received: from stenn.ntp.org (stenn.ntp.org [149.20.68.30]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id ED5CA12D5AF for <tictoc@ietf.org>; Thu,  7 Apr 2016 11:54:20 -0700 (PDT)
Received: from [::1] (helo=stenn.ntp.org) by stenn.ntp.org with esmtp (Exim 4.86_2 (FreeBSD)) (envelope-from <stenn@stenn.ntp.org>) id 1aoF39-0005oO-6j; Thu, 07 Apr 2016 18:53:03 +0000
From: Harlan Stenn <stenn@ntp.org>
To: Sharon Goldberg <goldbe@cs.bu.edu>
In-reply-to: <CAJHGrrQs=amt6yLeoz+mta_wDRsfCbTtZUruudox7VJesVq9nQ@mail.gmail.com>
References: <CAJHGrrQimUVqtRg6bowwBr5pxrSUh+mHkEzB0P1SBxP=nzczbg@mail.gmail.com> <57040B4A.4090301@pdmconsulting.net> <CAJHGrrSSD7o6Hy_3e8dNTOSTYF5MkyGo-Bn5SqHxa87XWqFpHQ@mail.gmail.com> <570411C0.7000004@ntp.org> <CAJHGrrR=-uN7dD5S0hBnF3Mt9ZrO8dC5YJK9k+D8j+WBFvByRg@mail.gmail.com> <E1anYbk-0002qu-8u@stenn.ntp.org> <20160406084046.GB9802@localhost> <E1anjUd-0003hc-Ho@stenn.ntp.org> <20160406103912.GA11632@localhost> <E1anvNF-0004Ro-NV@stenn.ntp.org> <20160407093225.GD20410@localhost> <CAJHGrrQs=amt6yLeoz+mta_wDRsfCbTtZUruudox7VJesVq9nQ@mail.gmail.com>
Comments: In-reply-to Sharon Goldberg <goldbe@cs.bu.edu> message dated "Thu, 07 Apr 2016 06:28:27 -0400."
X-Mailer: MH-E 7.4.2; nmh 1.6; XEmacs 21.4 (patch 24)
Mime-Version: 1.0 (generated by tm-edit 1.8)
Content-Type: text/plain; charset=US-ASCII
Date: Thu, 07 Apr 2016 18:53:02 +0000
Message-Id: <E1aoF39-0005oO-6j@stenn.ntp.org>
Archived-At: <http://mailarchive.ietf.org/arch/msg/tictoc/M-BZJOVKvhdneRF4KQouTt5vAdo>
Cc: NTP Working Group <ntpwg@lists.ntp.org>, Matthew Van Gundy <mvangund@cisco.com>, tictoc@ietf.org
Subject: Re: [TICTOC] [ntpwg]  comments on draft-stenn-ntp-suggest-refid-00
X-BeenThere: tictoc@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Timing over IP Connection and Transfer of Clock BOF <tictoc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tictoc>, <mailto:tictoc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tictoc/>
List-Post: <mailto:tictoc@ietf.org>
List-Help: <mailto:tictoc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tictoc>, <mailto:tictoc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 07 Apr 2016 18:54:23 -0000

Sharon Goldberg writes:
> My proposal is orthogonal to what is being discussed here.   I believe it
> can be implemented alongside Harlan's proposal in suggest-refid.

Agreed.

> I want to emphasize that my proposal is backwards compatible and can be
> implemented today without an extension field.  Whereas Harlan's idea is
> super clever but it requires both the client and the server to understand
> an extension field.
> 
> First off, to reiterate why I care about this, pretty much all the off-path
> attacks that we and Cisco have done have the following first step:
> 
> Query the target client. Get the response. Learn its refID. Now you know
> the client's server. $Attack the server. (Potentially rinse and repeat if
> the client moves to another server.)

The bad guy can impersonate the client and "vex" the server, and the bad
guy can also impersonate the server and "vex" the client.

> Sure, mode 6 reveals this information but modern NTP configurations should
> prevent remote IPs from launching mode 6 queries, as it is not only an
> amplification vector and also leaks state making it easier to attack the
> system.  (See also Cisco's "origin leak" bug [1].)  So I do not have a
> "warm fuzzy" feeling when I see NTP leaking information. Especially since
> most NTP traffic is not usually cryptographically protected.  I think NTP
> should leak less information, not more.
> 
> My proposal offers a backwards compatible way for a system to limit the
> information leaked in its reference ID. It solves the IPv6 refID collision
> problem.  And it seems to be compatible with what NTP is doing today.
> 
> Some exceptions could be made for stratum 1 servers to broadcast to all
> clients that your refID is GPS or some other external source, if this
> really a problem.  But we should be sure its really a problem, because
> information leakage always makes it easier to launch attacks.

The refid changes affect S2+ only, we'd leave S1 refids alone.

> Much of this discussion has been regarding a future use case in which a
> client had two IP addresses B and C.   This client sends a query from
> interface B and wants to make sure it is not in a timing loop with another
> system A who is taking time from interface B.

The timing loop issue has 2 aspects (at least).  I'll talk about one of
them now.

One reason to avoid a timing loop has to do with sailing off into the
weeds.  I'm not sure how significant this case is anymore.  If I only
have 1 source of time, well, we know what that means.  If that source of
time only has me as their source of time then the timing loop stuff
means we'll detect this immedately and we'll both go out-of-sync.  But
if we do not detect this loop, if A is at S2 then B is at S3.  When
we're down to no additional sources of time, at that point A will become
S4 and B will be come S5, then it goes to S6/S7, ... until the machines
go out of sync.  In this case that will happen in 6 poll intervals.

If there are no other sources of time available, then is it significant
that the machines go out of sync after 1 or 2 poll intervals instead of
6?

I'm using round numbers here.

A semblance of order would be in place if the boxes were configured
using orphan mode, or even local refclocks.

So I'd really like to know exactly what the concerns are about this
particular "failure mode".

H
--
> One could deal with this usecase using Harlan's proposal, but this does not
> preclude my proposal running in parallel.  To deal with this, the client "B
> and C"  uses Harlan's extension field to signal "if you take time from me,
> put this nonce as your refID."   If it decided to signal the *same* nonce
> to all clients, it has explicitly taken on the risk than an attacker can
> use this information as a first step in an attack, as I have described
> above.  If it signals a different nonce to all clients, then it is
> protected from this.
> 
> This non-backwards compatible feature would therefore only be used by
> systems that need it, eg those that have two IP addresses. All other
> systems could limit the amount of information being leaked in their refID
> by using my proposal.
> 
> Sharon
> 
> [1] http://www.talosintel.com/reports/TALOS-2016-0078/
> 
> --001a1142b68e529239052fe28ce7
> Content-Type: text/html; charset=UTF-8
> Content-Transfer-Encoding: quoted-printable
> 
> <div dir=3D"ltr"><div><div><div><div>My proposal is orthogonal to what is b=
> eing discussed here.=C2=A0=C2=A0 I believe it can be implemented alongside =
> Harlan&#39;s proposal in suggest-refid.<br><br>I want to emphasize that my =
> proposal is backwards compatible and can be implemented today without an ex=
> tension field.=C2=A0 Whereas Harlan&#39;s idea is super clever but it requi=
> res both the client and the server to understand an extension field.<br></d=
> iv><br>First off, to reiterate why I care about this, pretty much all the o=
> ff-path attacks that we and Cisco have done have the following first step:<=
> br><br></div>Query the target client. Get the response. Learn its refID. No=
> w you know the client&#39;s server. $Attack the server. (Potentially rinse =
> and repeat if the client moves to another server.)<br><br></div><div>Sure, =
> mode 6 reveals this information but modern NTP configurations should preven=
> t remote IPs from launching mode 6 queries, as it is not only an amplificat=
> ion vector and also leaks state making it easier to attack the system.=C2=
> =A0 (See also Cisco&#39;s &quot;origin leak&quot; bug [1].)=C2=A0 So I do n=
> ot have a &quot;warm fuzzy&quot; feeling when I see NTP leaking information=
> . Especially since most NTP traffic is not usually cryptographically protec=
> ted.=C2=A0 I think NTP should leak less information, not more.<br><br></div=
> ><div>My proposal offers a backwards compatible way for a system to limit t=
> he information leaked in its reference ID. It solves the IPv6 refID collisi=
> on problem.=C2=A0 And it seems to be compatible with what NTP is doing toda=
> y.<br></div><div><div><br></div>Some exceptions could be made for stratum 1=
>  servers=20
> to broadcast to all clients that your refID is GPS or some other=20
> external source, if this really a problem.=C2=A0 But we should be sure its=
> =20
> really a problem, because information leakage always makes it easier to=20
> launch attacks. <br><br></div><div>Much of this discussion has been regardi=
> ng a future use case in which a client had two IP addresses B and C.=C2=A0=
> =C2=A0 This client sends a query from interface B and wants to make sure it
>  is not in a timing loop with another system A who is taking time from=20
> interface B.=C2=A0 <br><br>One could deal with this usecase using Harlan&#3=
> 9;s proposal, but this does not preclude my proposal running in parallel.=
> =C2=A0 To deal with this, the client &quot;B and C&quot;=C2=A0 uses Harlan&=
> #39;s extension field to signal &quot;if you take time from me, put this no=
> nce as your refID.&quot;=C2=A0=C2=A0 If it decided to signal the *same* non=
> ce to all clients, it has explicitly taken on the risk than an attacker can=
>  use this information as a first step in an attack, as I have described abo=
> ve.=C2=A0 If it signals a different nonce to all clients, then it is protec=
> ted from this.</div><br></div>This non-backwards compatible feature would t=
> herefore only be used by systems that need it, eg those that have two IP ad=
> dresses. All other systems could limit the amount of information being leak=
> ed in their refID by using my proposal.<br><div><br><div>Sharon<br><br>[1] =
> <a href=3D"http://www.talosintel.com/reports/TALOS-2016-0078/">http://www.t=
> alosintel.com/reports/TALOS-2016-0078/</a><br></div><br><div><br></div></di=
> v></div>
> 
> --001a1142b68e529239052fe28ce7--
> 
> --===============5243542199967168099==
> Content-Type: text/plain; charset="us-ascii"
> MIME-Version: 1.0
> Content-Transfer-Encoding: 7bit
> Content-Disposition: inline
> 
> _______________________________________________
> ntpwg mailing list
> ntpwg@lists.ntp.org
> http://lists.ntp.org/listinfo/ntpwg
> --===============5243542199967168099==--
> 


From nobody Mon Apr 18 04:55:21 2016
Return-Path: <internet-drafts@ietf.org>
X-Original-To: tictoc@ietf.org
Delivered-To: tictoc@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 2F57F12D0C4; Mon, 18 Apr 2016 04:55:17 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: <i-d-announce@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.19.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20160418115517.9267.16399.idtracker@ietfa.amsl.com>
Date: Mon, 18 Apr 2016 04:55:17 -0700
Archived-At: <http://mailarchive.ietf.org/arch/msg/tictoc/HddsaoNirNNhtSDA5qChdqQpISM>
Cc: tictoc@ietf.org
Subject: [TICTOC] I-D Action: draft-ietf-tictoc-multi-path-synchronization-04.txt
X-BeenThere: tictoc@ietf.org
X-Mailman-Version: 2.1.17
List-Id: Timing over IP Connection and Transfer of Clock BOF <tictoc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tictoc>, <mailto:tictoc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tictoc/>
List-Post: <mailto:tictoc@ietf.org>
List-Help: <mailto:tictoc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tictoc>, <mailto:tictoc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 18 Apr 2016 11:55:17 -0000

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Timing over IP Connection and Transfer of Clock of the IETF.

        Title           : Multi-Path Time Synchronization
        Authors         : Alex Shpiner
                          Richard Tse
                          Craig Schelp
                          Tal Mizrahi
	Filename        : draft-ietf-tictoc-multi-path-synchronization-04.txt
	Pages           : 15
	Date            : 2016-04-18

Abstract:
   Clock synchronization protocols are very widely used in IP-based
   networks. The Network Time Protocol (NTP) has been commonly deployed
   for many years, and the last few years have seen an increasingly
   rapid deployment of the Precision Time Protocol (PTP). As time-
   sensitive applications evolve, clock accuracy requirements are
   becoming increasingly stringent, requiring the time synchronization
   protocols to provide high accuracy. Slave Diversity is a recently
   introduced approach, where the master and slave clocks (also known as
   server and client) are connected through multiple network paths, and
   the slave combines the information received through all paths to
   obtain a higher clock accuracy compared to the conventional one-path
   approach.  This document describes a multi-path approach to PTP and
   NTP over IP networks, allowing the protocols to run concurrently over
   multiple communication paths between the master and slave clocks. The
   multi-path approach can significantly contribute to clock accuracy,
   security and fault tolerance. The Multi-Path Precision Time Protocol
   (MPPTP) and Multi-Path Network Time Protocol (MPNTP) define an
   additional layer that extends the existing PTP and NTP without the
   need to modify these protocols. MPPTP and MPNTP also allow backward
   compatibility with nodes that do not support the multi-path
   extension.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-tictoc-multi-path-synchronization/

There's also a htmlized version available at:
https://tools.ietf.org/html/draft-ietf-tictoc-multi-path-synchronization-04

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-tictoc-multi-path-synchronization-04


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/


From nobody Mon Apr 18 09:10:41 2016
Return-Path: <Kathleen.Moriarty.ietf@gmail.com>
X-Original-To: tictoc@ietf.org
Delivered-To: tictoc@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id BC54A12E17B; Mon, 18 Apr 2016 09:10:37 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: "Kathleen Moriarty" <Kathleen.Moriarty.ietf@gmail.com>
To: "The IESG" <iesg@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.19.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20160418161037.9310.53260.idtracker@ietfa.amsl.com>
Date: Mon, 18 Apr 2016 09:10:37 -0700
Archived-At: <http://mailarchive.ietf.org/arch/msg/tictoc/blkuvG5zJReHV6vGCzoBbvxjQl8>
Cc: tictoc-chairs@ietf.org, tictoc@ietf.org, draft-ietf-tictoc-ptp-mib@ietf.org, kodonog@pobox.com
Subject: [TICTOC] Kathleen Moriarty's No Objection on draft-ietf-tictoc-ptp-mib-08: (with COMMENT)
X-BeenThere: tictoc@ietf.org
X-Mailman-Version: 2.1.17
List-Id: Timing over IP Connection and Transfer of Clock BOF <tictoc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tictoc>, <mailto:tictoc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tictoc/>
List-Post: <mailto:tictoc@ietf.org>
List-Help: <mailto:tictoc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tictoc>, <mailto:tictoc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 18 Apr 2016 16:10:38 -0000

Kathleen Moriarty has entered the following ballot position for
draft-ietf-tictoc-ptp-mib-08: No Objection

When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)


Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html
for more information about IESG DISCUSS and COMMENT positions.


The document, along with other ballot positions, can be found here:
https://datatracker.ietf.org/doc/draft-ietf-tictoc-ptp-mib/



----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------

It looks like the SecDir review may not have gotten a response.  Here's
the review:
https://www.ietf.org/mail-archive/web/secdir/current/msg06401.html

I'm fine with the mention of this being read only as it is in the
introduction and also fine with the mention of SNMPv1 and v2 in the
abstract as it provides context and background.



From nobody Tue Apr 19 10:12:29 2016
Return-Path: <alissa@cooperw.in>
X-Original-To: tictoc@ietf.org
Delivered-To: tictoc@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id E5FB912ED3B; Tue, 19 Apr 2016 10:12:16 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: "Alissa Cooper" <alissa@cooperw.in>
To: "The IESG" <iesg@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.19.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20160419171216.31521.25135.idtracker@ietfa.amsl.com>
Date: Tue, 19 Apr 2016 10:12:16 -0700
Archived-At: <http://mailarchive.ietf.org/arch/msg/tictoc/rZdfsKIjtrNxXpZcjh74zLFlN_I>
Cc: tictoc-chairs@ietf.org, tictoc@ietf.org, draft-ietf-tictoc-ptp-mib@ietf.org, kodonog@pobox.com
Subject: [TICTOC] Alissa Cooper's No Objection on draft-ietf-tictoc-ptp-mib-08: (with COMMENT)
X-BeenThere: tictoc@ietf.org
X-Mailman-Version: 2.1.17
List-Id: Timing over IP Connection and Transfer of Clock BOF <tictoc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tictoc>, <mailto:tictoc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tictoc/>
List-Post: <mailto:tictoc@ietf.org>
List-Help: <mailto:tictoc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tictoc>, <mailto:tictoc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 19 Apr 2016 17:12:17 -0000

Alissa Cooper has entered the following ballot position for
draft-ietf-tictoc-ptp-mib-08: No Objection

When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)


Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html
for more information about IESG DISCUSS and COMMENT positions.


The document, along with other ballot positions, can be found here:
https://datatracker.ietf.org/doc/draft-ietf-tictoc-ptp-mib/



----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------

(1) The ClockIdentity is described as being generated based on an EUI-64
address as described in IEEE 1588-2008 Section 7.5.2.2.2. But in IEEE
1588-2008, there are two different ways the clock identifier can be
generated, the other being a non-EUI-64 address defined in 7.5.2.2.3. Why
is that option left out of the ClockIdentity description?

In general I was dismayed to see the re-use of EUI-64 for clock identity
for the security and privacy drawbacks, since it's not particularly clear
that re-using those identifiers is necessary here. But if such a fix is
warranted this MIB is not the place to do it in any event.

(2) Looking at
https://trac.tools.ietf.org/area/ops/trac/wiki/mib-security I recall that
other MIB documents we've reviewed recently have listed out the specific
tables/objects that may be considered vulnerable or sensitive, even if
those objects are read-only. Why doesn't this document do that? I would
think all of the clock identity objects would belong in that bucket at a
minimum.



From nobody Tue Apr 19 11:41:20 2016
Return-Path: <stephen.farrell@cs.tcd.ie>
X-Original-To: tictoc@ietfa.amsl.com
Delivered-To: tictoc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 79EC312E2E1; Tue, 19 Apr 2016 11:41:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.297
X-Spam-Level: 
X-Spam-Status: No, score=-5.297 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.996, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cs.tcd.ie
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sfqTytwfrh_N; Tue, 19 Apr 2016 11:41:11 -0700 (PDT)
Received: from mercury.scss.tcd.ie (mercury.scss.tcd.ie [134.226.56.6]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A302812E290; Tue, 19 Apr 2016 11:41:07 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id A87E9BE57; Tue, 19 Apr 2016 19:41:05 +0100 (IST)
X-Virus-Scanned: Debian amavisd-new at scss.tcd.ie
Received: from mercury.scss.tcd.ie ([127.0.0.1]) by localhost (mercury.scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id e4FgZFGVfYwx; Tue, 19 Apr 2016 19:41:02 +0100 (IST)
Received: from [10.87.49.100] (unknown [86.46.28.69]) by mercury.scss.tcd.ie (Postfix) with ESMTPSA id 5D0BABE39; Tue, 19 Apr 2016 19:40:57 +0100 (IST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cs.tcd.ie; s=mail; t=1461091258; bh=oSnxzaVtFKN3kbPyRzOKObxGliJHJNOgQqOMI6M8pjM=; h=Subject:To:References:Cc:From:Date:In-Reply-To:From; b=omH8YuclU/s9lfw1ODJZXhQiw9UsrLzeMCD7kRcT50OPW0wod6STNj9H3To5r+O66 vqo7j8/Zr4REPKzrOdwn8e6QG+iyh7mFRqLhV5Y6EA9EkcGjUUX8dL8Ck+aIYiljZt 3owA1knYGs+TV6nAhgQ4Kl2zaMXa8te9UDWBZMF4=
To: Alissa Cooper <alissa@cooperw.in>, The IESG <iesg@ietf.org>
References: <20160419171216.31521.25135.idtracker@ietfa.amsl.com>
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Openpgp: id=D66EA7906F0B897FB2E97D582F3C8736805F8DA2; url=
Message-ID: <57167BB8.1080300@cs.tcd.ie>
Date: Tue, 19 Apr 2016 19:40:56 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.6.0
MIME-Version: 1.0
In-Reply-To: <20160419171216.31521.25135.idtracker@ietfa.amsl.com>
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha-256; boundary="------------ms030900020304030502070106"
Archived-At: <http://mailarchive.ietf.org/arch/msg/tictoc/E8S-o_59mqJdVIIyIfIheKVzmFo>
Cc: tictoc-chairs@ietf.org, kodonog@pobox.com, tictoc@ietf.org, draft-ietf-tictoc-ptp-mib@ietf.org
Subject: Re: [TICTOC] Alissa Cooper's No Objection on draft-ietf-tictoc-ptp-mib-08: (with COMMENT)
X-BeenThere: tictoc@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Timing over IP Connection and Transfer of Clock BOF <tictoc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tictoc>, <mailto:tictoc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tictoc/>
List-Post: <mailto:tictoc@ietf.org>
List-Help: <mailto:tictoc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tictoc>, <mailto:tictoc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 19 Apr 2016 18:41:14 -0000

This is a cryptographically signed message in MIME format.

--------------ms030900020304030502070106
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


Good catch wrt the EUI. I missed that.

S.

On 19/04/16 18:12, Alissa Cooper wrote:
> Alissa Cooper has entered the following ballot position for
> draft-ietf-tictoc-ptp-mib-08: No Objection
>=20
> When responding, please keep the subject line intact and reply to all
> email addresses included in the To and CC lines. (Feel free to cut this=

> introductory paragraph, however.)
>=20
>=20
> Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.ht=
ml
> for more information about IESG DISCUSS and COMMENT positions.
>=20
>=20
> The document, along with other ballot positions, can be found here:
> https://datatracker.ietf.org/doc/draft-ietf-tictoc-ptp-mib/
>=20
>=20
>=20
> ----------------------------------------------------------------------
> COMMENT:
> ----------------------------------------------------------------------
>=20
> (1) The ClockIdentity is described as being generated based on an EUI-6=
4
> address as described in IEEE 1588-2008 Section 7.5.2.2.2. But in IEEE
> 1588-2008, there are two different ways the clock identifier can be
> generated, the other being a non-EUI-64 address defined in 7.5.2.2.3. W=
hy
> is that option left out of the ClockIdentity description?
>=20
> In general I was dismayed to see the re-use of EUI-64 for clock identit=
y
> for the security and privacy drawbacks, since it's not particularly cle=
ar
> that re-using those identifiers is necessary here. But if such a fix is=

> warranted this MIB is not the place to do it in any event.
>=20
> (2) Looking at
> https://trac.tools.ietf.org/area/ops/trac/wiki/mib-security I recall th=
at
> other MIB documents we've reviewed recently have listed out the specifi=
c
> tables/objects that may be considered vulnerable or sensitive, even if
> those objects are read-only. Why doesn't this document do that? I would=

> think all of the clock identity objects would belong in that bucket at =
a
> minimum.
>=20
>=20


--------------ms030900020304030502070106
Content-Type: application/pkcs7-signature; name="smime.p7s"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="smime.p7s"
Content-Description: S/MIME Cryptographic Signature

MIAGCSqGSIb3DQEHAqCAMIACAQExDzANBglghkgBZQMEAgEFADCABgkqhkiG9w0BBwEAAKCC
CvIwggUIMIID8KADAgECAhBPzaE7pzYviUJyhmHTFBdnMA0GCSqGSIb3DQEBCwUAMHUxCzAJ
BgNVBAYTAklMMRYwFAYDVQQKEw1TdGFydENvbSBMdGQuMSkwJwYDVQQLEyBTdGFydENvbSBD
ZXJ0aWZpY2F0aW9uIEF1dGhvcml0eTEjMCEGA1UEAxMaU3RhcnRDb20gQ2xhc3MgMSBDbGll
bnQgQ0EwHhcNMTYwMjA5MDkyODE1WhcNMTcwMjA5MDkyODE1WjBOMSIwIAYDVQQDDBlzdGVw
aGVuLmZhcnJlbGxAY3MudGNkLmllMSgwJgYJKoZIhvcNAQkBFhlzdGVwaGVuLmZhcnJlbGxA
Y3MudGNkLmllMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAtuC0rYze/2JinSra
C9F2RjGdQZjNALLcW9C3WKTwYII3wBslobmHuPEYE5JaGItmzuKnAW619R1rD/kfoNWC19N3
rBZ6UX9Cmb9D9exCwYIwVuSwjrCQWGxgCtNQTrwKzCCpI790GRiMTvxvO7UmzmBrCaBLiZW5
R0fBjK5Yn6hUhAzGBkNbkIEL28cLJqH0yVz7Kl92OlzrQqTPEts5m6cDnNdY/ADfeAX18c1r
dxZqcAxhLotrCqgsVA4ilbQDMMXGTLlB5TP35HeWZuGBU7xu003rLcFLdOkD8xvpJoYZy9Kt
3oABXPS5yqtMK+XCNdqmMn+4mOtLwQSMmPCSiQIDAQABo4IBuTCCAbUwCwYDVR0PBAQDAgSw
MB0GA1UdJQQWMBQGCCsGAQUFBwMCBggrBgEFBQcDBDAJBgNVHRMEAjAAMB0GA1UdDgQWBBQJ
QhvwQ5Fl372Z6xqo6fdn8XejTTAfBgNVHSMEGDAWgBQkgWw5Yb5JD4+3G0YrySi1J0htaDBv
BggrBgEFBQcBAQRjMGEwJAYIKwYBBQUHMAGGGGh0dHA6Ly9vY3NwLnN0YXJ0c3NsLmNvbTA5
BggrBgEFBQcwAoYtaHR0cDovL2FpYS5zdGFydHNzbC5jb20vY2VydHMvc2NhLmNsaWVudDEu
Y3J0MDgGA1UdHwQxMC8wLaAroCmGJ2h0dHA6Ly9jcmwuc3RhcnRzc2wuY29tL3NjYS1jbGll
bnQxLmNybDAkBgNVHREEHTAbgRlzdGVwaGVuLmZhcnJlbGxAY3MudGNkLmllMCMGA1UdEgQc
MBqGGGh0dHA6Ly93d3cuc3RhcnRzc2wuY29tLzBGBgNVHSAEPzA9MDsGCysGAQQBgbU3AQIE
MCwwKgYIKwYBBQUHAgEWHmh0dHA6Ly93d3cuc3RhcnRzc2wuY29tL3BvbGljeTANBgkqhkiG
9w0BAQsFAAOCAQEArzrSv2C8PlBBmGuiGrzm2Wma46/KHtXmZYS0bsd43pM66Pc/MsqPE0HD
C1GzMFfwB6BfkJn8ijNSIhlgj898WzjvnpM/SO8KStjlB8719ig/xKISrOl5mX55XbFlQtX9
U6MrqRgbDIATxhD9IDr+ryvovDzChqgQj7mt2jYr4mdlRjsjod3H1VY6XglRmaaNGZfsCARM
aE/TU5SXIiqauwt5KxNGYAY67QkOBs7O1FkSXpTk7+1MmzJMF4nP8QQ5n8vhVNseF+/Wm7ai
9mtnrkLbaznMsy/ULo/C2yuLUWTbZZbf4EKNmVdme6tUDgYkFjAFOblfA7W1fSPiQGagYzCC
BeIwggPKoAMCAQICEGunin0K14jWUQr5WeTntOEwDQYJKoZIhvcNAQELBQAwfTELMAkGA1UE
BhMCSUwxFjAUBgNVBAoTDVN0YXJ0Q29tIEx0ZC4xKzApBgNVBAsTIlNlY3VyZSBEaWdpdGFs
IENlcnRpZmljYXRlIFNpZ25pbmcxKTAnBgNVBAMTIFN0YXJ0Q29tIENlcnRpZmljYXRpb24g
QXV0aG9yaXR5MB4XDTE1MTIxNjAxMDAwNVoXDTMwMTIxNjAxMDAwNVowdTELMAkGA1UEBhMC
SUwxFjAUBgNVBAoTDVN0YXJ0Q29tIEx0ZC4xKTAnBgNVBAsTIFN0YXJ0Q29tIENlcnRpZmlj
YXRpb24gQXV0aG9yaXR5MSMwIQYDVQQDExpTdGFydENvbSBDbGFzcyAxIENsaWVudCBDQTCC
ASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBAL192vfDon2D9luC/dtbX64eG3XAtRmv
mCSsu1d52DXsCR58zJQbCtB2/A5uFqNxWacpXGGtTCRk9dEDBlmixEd8QiLkUfvHpJX/xKnm
VkS6Iye8wUbYzMsDzgnpazlPg19dnSqfhM+Cevdfa89VLnUztRr2cgmCfyO9Otrh7LJDPG+4
D8ZnAqDtVB8MKYJL6QgKyVhhaBc4y3bGWxKyXEtx7QIZZGxPwSkzK3WIN+VKNdkiwTubW5PI
dopmykwvIjLPqbJK7yPwFZYekKE015OsW6FV+s4DIM8UlVS8pkIsoGGJtMuWjLL4tq2hYQuu
N0jhrxK1ljz50hH23gA9cbMCAwEAAaOCAWQwggFgMA4GA1UdDwEB/wQEAwIBBjAdBgNVHSUE
FjAUBggrBgEFBQcDAgYIKwYBBQUHAwQwEgYDVR0TAQH/BAgwBgEB/wIBADAyBgNVHR8EKzAp
MCegJaAjhiFodHRwOi8vY3JsLnN0YXJ0c3NsLmNvbS9zZnNjYS5jcmwwZgYIKwYBBQUHAQEE
WjBYMCQGCCsGAQUFBzABhhhodHRwOi8vb2NzcC5zdGFydHNzbC5jb20wMAYIKwYBBQUHMAKG
JGh0dHA6Ly9haWEuc3RhcnRzc2wuY29tL2NlcnRzL2NhLmNydDAdBgNVHQ4EFgQUJIFsOWG+
SQ+PtxtGK8kotSdIbWgwHwYDVR0jBBgwFoAUTgvvGqRAW6UXaYcwyjRoQ9BBrvIwPwYDVR0g
BDgwNjA0BgRVHSAAMCwwKgYIKwYBBQUHAgEWHmh0dHA6Ly93d3cuc3RhcnRzc2wuY29tL3Bv
bGljeTANBgkqhkiG9w0BAQsFAAOCAgEAi+P3h+wBi4StDwECW5zhIycjBL008HACblIf26HY
0JdOruKbrWDsXUsiI0j/7Crft9S5oxvPiDtVqspBOB/y5uzSns1lZwh7sG96bYBZpcGzGxpF
NjDmQbcM3yl3WFIRS4WhNrsOY14V7y2IrUGsvetsD+bjyOngCIVeC/GmsmtbuLOzJ606tEc9
uRbhjTu/b0x2Fo+/e7UkQvKzNeo7OMhijixaULyINBfCBJb+e29bLafgu6JqjOUJ9eXXj20p
6q/CW+uVrZiSW57+q5an2P2i7hP85jQJcy5j4HzA0rSiF3YPhKGAWUxKPMAVGgcYoXzWydOv
Z3UDsTDTagXpRDIKQLZo02wrlxY6iMFqvlzsemVf1odhQJmi7Eh5TbxI40kDGcBOBHhwnaOu
mZhLP+SWJQnjpLpSlUOj95uf1zo9oz9e0NgIJoz/tdfrBzez76xtDsK0KfUDHt1/q59BvDI7
RX6gVr0fQoCyMczNzCTcRXYHY0tq2J0oT+bsb6sH2b4WVWAiJKnSYaWDjdA70qHX4mq9MIjO
/ZskmSY8wtAk24orAc0vwXgYanqNsBX5Yv4sN4Z9VyrwMdLcusP7HJgRdAGKpkR2I9U4zEsN
JQJewM7S4Jalo1DyPrLpL2nTET8ZrSl5Utp1UeGp/2deoprGevfnxWB+vHNQiu85o6MxggPM
MIIDyAIBATCBiTB1MQswCQYDVQQGEwJJTDEWMBQGA1UEChMNU3RhcnRDb20gTHRkLjEpMCcG
A1UECxMgU3RhcnRDb20gQ2VydGlmaWNhdGlvbiBBdXRob3JpdHkxIzAhBgNVBAMTGlN0YXJ0
Q29tIENsYXNzIDEgQ2xpZW50IENBAhBPzaE7pzYviUJyhmHTFBdnMA0GCWCGSAFlAwQCAQUA
oIICEzAYBgkqhkiG9w0BCQMxCwYJKoZIhvcNAQcBMBwGCSqGSIb3DQEJBTEPFw0xNjA0MTkx
ODQwNTZaMC8GCSqGSIb3DQEJBDEiBCCkR6AFpQbcEoCg+2iMTA47ZOV0sbAKFK+IXyFZYqOD
mjBsBgkqhkiG9w0BCQ8xXzBdMAsGCWCGSAFlAwQBKjALBglghkgBZQMEAQIwCgYIKoZIhvcN
AwcwDgYIKoZIhvcNAwICAgCAMA0GCCqGSIb3DQMCAgFAMAcGBSsOAwIHMA0GCCqGSIb3DQMC
AgEoMIGaBgkrBgEEAYI3EAQxgYwwgYkwdTELMAkGA1UEBhMCSUwxFjAUBgNVBAoTDVN0YXJ0
Q29tIEx0ZC4xKTAnBgNVBAsTIFN0YXJ0Q29tIENlcnRpZmljYXRpb24gQXV0aG9yaXR5MSMw
IQYDVQQDExpTdGFydENvbSBDbGFzcyAxIENsaWVudCBDQQIQT82hO6c2L4lCcoZh0xQXZzCB
nAYLKoZIhvcNAQkQAgsxgYyggYkwdTELMAkGA1UEBhMCSUwxFjAUBgNVBAoTDVN0YXJ0Q29t
IEx0ZC4xKTAnBgNVBAsTIFN0YXJ0Q29tIENlcnRpZmljYXRpb24gQXV0aG9yaXR5MSMwIQYD
VQQDExpTdGFydENvbSBDbGFzcyAxIENsaWVudCBDQQIQT82hO6c2L4lCcoZh0xQXZzANBgkq
hkiG9w0BAQEFAASCAQBYu14xXsb/lNo/659nR7VCmVKO+8KTUSoUazrSIs/WMjSSFJb/XM7D
7X8Jiba0PAUl2x6IN/8up4arBwMdYyOomDVXxKQStqZuXJW+jzhEWjNgiArO60C/MampN0AY
G3/KBpW8YQyMhxUwo7eJ8E7AVoBUhPRmIBQKza1ccNIdeREZ45Tttmtfn6ZfmwS5jwPN5JN/
ZCJxFv/5ADryn6I38Gl05Ux8xuI0qRXjUWDzHDr2TItiQNGv1g/TnvDEDK28SwKYZ1ULocwZ
7JbOQ1w8mgFcmPNuNwNSNLpD1lpH5OJUTSO//IIKNkjSdczBHlxyQzbF8Px42fFiZVpTg2lX
AAAAAAAA
--------------ms030900020304030502070106--


From nobody Tue Apr 19 13:23:32 2016
Return-Path: <joelja@bogus.com>
X-Original-To: tictoc@ietfa.amsl.com
Delivered-To: tictoc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 41B6012DA84; Tue, 19 Apr 2016 13:23:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.896
X-Spam-Level: 
X-Spam-Status: No, score=-7.896 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.996] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UWpXdIgKe8WR; Tue, 19 Apr 2016 13:23:23 -0700 (PDT)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9124412B048; Tue, 19 Apr 2016 13:23:23 -0700 (PDT)
Received: from mb-2.local ([IPv6:2620:11a:c081:20:dd9e:698d:9698:e8a6]) (authenticated bits=0) by nagasaki.bogus.com (8.14.9/8.14.9) with ESMTP id u3JKNIXr021945 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Tue, 19 Apr 2016 20:23:19 GMT (envelope-from joelja@bogus.com)
To: Alissa Cooper <alissa@cooperw.in>, The IESG <iesg@ietf.org>
References: <20160419171216.31521.25135.idtracker@ietfa.amsl.com>
From: joel jaeggli <joelja@bogus.com>
Message-ID: <60449605-8547-4b73-e3aa-0c17c2c0a25e@bogus.com>
Date: Tue, 19 Apr 2016 13:23:16 -0700
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:45.0) Gecko/20100101 Thunderbird/45.0
MIME-Version: 1.0
In-Reply-To: <20160419171216.31521.25135.idtracker@ietfa.amsl.com>
Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="JBHOUJDm6bKR7Gar74EnGCpbf7f8L7ubH"
Archived-At: <http://mailarchive.ietf.org/arch/msg/tictoc/GXI_ntcoSCgIzTsFM7G8EL8EIr4>
Cc: tictoc-chairs@ietf.org, kodonog@pobox.com, tictoc@ietf.org, draft-ietf-tictoc-ptp-mib@ietf.org
Subject: Re: [TICTOC] Alissa Cooper's No Objection on draft-ietf-tictoc-ptp-mib-08: (with COMMENT)
X-BeenThere: tictoc@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Timing over IP Connection and Transfer of Clock BOF <tictoc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tictoc>, <mailto:tictoc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tictoc/>
List-Post: <mailto:tictoc@ietf.org>
List-Help: <mailto:tictoc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tictoc>, <mailto:tictoc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 19 Apr 2016 20:23:25 -0000

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--JBHOUJDm6bKR7Gar74EnGCpbf7f8L7ubH
Content-Type: multipart/mixed; boundary="Md8nvnPnWuiVx0cKgesaQO72ckqcsDMfg"
From: joel jaeggli <joelja@bogus.com>
To: Alissa Cooper <alissa@cooperw.in>, The IESG <iesg@ietf.org>
Cc: tictoc-chairs@ietf.org, tictoc@ietf.org,
 draft-ietf-tictoc-ptp-mib@ietf.org, kodonog@pobox.com
Message-ID: <60449605-8547-4b73-e3aa-0c17c2c0a25e@bogus.com>
Subject: Re: Alissa Cooper's No Objection on draft-ietf-tictoc-ptp-mib-08:
 (with COMMENT)
References: <20160419171216.31521.25135.idtracker@ietfa.amsl.com>
In-Reply-To: <20160419171216.31521.25135.idtracker@ietfa.amsl.com>

--Md8nvnPnWuiVx0cKgesaQO72ckqcsDMfg
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable

On 4/19/16 10:12 AM, Alissa Cooper wrote:
> Alissa Cooper has entered the following ballot position for
> draft-ietf-tictoc-ptp-mib-08: No Objection
>=20
> When responding, please keep the subject line intact and reply to all
> email addresses included in the To and CC lines. (Feel free to cut this=

> introductory paragraph, however.)
>=20
>=20
> Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.ht=
ml
> for more information about IESG DISCUSS and COMMENT positions.
>=20
>=20
> The document, along with other ballot positions, can be found here:
> https://datatracker.ietf.org/doc/draft-ietf-tictoc-ptp-mib/
>=20
>=20
>=20
> ----------------------------------------------------------------------
> COMMENT:
> ----------------------------------------------------------------------
>=20
> (1) The ClockIdentity is described as being generated based on an EUI-6=
4
> address as described in IEEE 1588-2008 Section 7.5.2.2.2. But in IEEE
> 1588-2008, there are two different ways the clock identifier can be
> generated, the other being a non-EUI-64 address defined in 7.5.2.2.3. W=
hy
> is that option left out of the ClockIdentity description?
>=20
> In general I was dismayed to see the re-use of EUI-64 for clock identit=
y
> for the security and privacy drawbacks, since it's not particularly cle=
ar
> that re-using those identifiers is necessary here. But if such a fix is=

> warranted this MIB is not the place to do it in any event.

I don't see a whole lot wrong with using a mac address as an identifier
in a management system. 1588 speakers are frequently adjecent to each
other and almost always within the same management domain,

> (2) Looking at
> https://trac.tools.ietf.org/area/ops/trac/wiki/mib-security I recall th=
at
> other MIB documents we've reviewed recently have listed out the specifi=
c
> tables/objects that may be considered vulnerable or sensitive, even if
> those objects are read-only. Why doesn't this document do that? I would=

> think all of the clock identity objects would belong in that bucket at =
a
> minimum.
>=20
>=20



--Md8nvnPnWuiVx0cKgesaQO72ckqcsDMfg--

--JBHOUJDm6bKR7Gar74EnGCpbf7f8L7ubH
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2
Comment: GPGTools - http://gpgtools.org

iEYEARECAAYFAlcWk7UACgkQ8AA1q7Z/VrL0oQCeL/hm62iI13uu1Wc1cHYp1tJY
ZFgAn2EFrYWv/jxJpiCq/0O9SYJg7Ymc
=+hFi
-----END PGP SIGNATURE-----

--JBHOUJDm6bKR7Gar74EnGCpbf7f8L7ubH--


From nobody Tue Apr 19 15:24:58 2016
Return-Path: <db3546@att.com>
X-Original-To: tictoc@ietf.org
Delivered-To: tictoc@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 9C75B12D0EC; Tue, 19 Apr 2016 15:24:55 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: "Deborah Brungard" <db3546@att.com>
To: "The IESG" <iesg@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.19.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20160419222455.31513.67460.idtracker@ietfa.amsl.com>
Date: Tue, 19 Apr 2016 15:24:55 -0700
Archived-At: <http://mailarchive.ietf.org/arch/msg/tictoc/w3d3WmWQ21LsF5pYj0-4kwgw1-c>
Cc: tictoc-chairs@ietf.org, tictoc@ietf.org, draft-ietf-tictoc-ptp-mib@ietf.org, kodonog@pobox.com
Subject: [TICTOC] Deborah Brungard's No Objection on draft-ietf-tictoc-ptp-mib-08: (with COMMENT)
X-BeenThere: tictoc@ietf.org
X-Mailman-Version: 2.1.17
List-Id: Timing over IP Connection and Transfer of Clock BOF <tictoc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tictoc>, <mailto:tictoc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tictoc/>
List-Post: <mailto:tictoc@ietf.org>
List-Help: <mailto:tictoc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tictoc>, <mailto:tictoc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 19 Apr 2016 22:24:55 -0000

Deborah Brungard has entered the following ballot position for
draft-ietf-tictoc-ptp-mib-08: No Objection

When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)


Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html
for more information about IESG DISCUSS and COMMENT positions.


The document, along with other ballot positions, can be found here:
https://datatracker.ietf.org/doc/draft-ietf-tictoc-ptp-mib/



----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------

As Alissa commented, the ops wiki has recommended MIB-security section
text. Specific tables/objects need to be listed for MAX-ACCESS which may
be considered sensitive. Also I prefer the stronger wording (extra
capitals) on use of SNMPv3. A MIB RFC in CCAMP, RFC 6825, has examples of
both.



From nobody Wed Apr 20 00:09:11 2016
Return-Path: <odonoghue@isoc.org>
X-Original-To: tictoc@ietfa.amsl.com
Delivered-To: tictoc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3A45212DCF2 for <tictoc@ietfa.amsl.com>; Wed, 20 Apr 2016 00:09:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level: 
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=isoc.onmicrosoft.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ditoYR7be0_h for <tictoc@ietfa.amsl.com>; Wed, 20 Apr 2016 00:09:07 -0700 (PDT)
Received: from na01-bn1-obe.outbound.protection.outlook.com (mail-bn1bon0659.outbound.protection.outlook.com [IPv6:2a01:111:f400:fc10::1:659]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D67E912D79B for <tictoc@ietf.org>; Wed, 20 Apr 2016 00:09:04 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=isoc.onmicrosoft.com;  s=selector1-isoc-org; h=From:To:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=wIVrUTH4aa1S1X5XbOhLSoteFHdtjQuA2bZbpG9BwIE=; b=g3ycDiQb8ag5wj8ptINDjjXEYTJIo7jbD/VqnQcOySx79WpnVDbdmkDQYdjfdRS3dGfyDemOlbuOzOYWL1hJKXOSUq5CkWT8XNCZaJq4KX0dlkz0mBKIzOnsDI9pKwhUHMyMXr45n4mC375zBdLmM/zlU6riUnBzHvi9iuk3vLk=
Received: from DM2PR0601MB1118.namprd06.prod.outlook.com (10.160.218.139) by DM2PR0601MB1119.namprd06.prod.outlook.com (10.160.218.14) with Microsoft SMTP Server (TLS) id 15.1.453.26; Wed, 20 Apr 2016 07:08:48 +0000
Received: from DM2PR0601MB1118.namprd06.prod.outlook.com ([10.160.218.139]) by DM2PR0601MB1118.namprd06.prod.outlook.com ([10.160.218.139]) with mapi id 15.01.0466.022; Wed, 20 Apr 2016 07:08:47 +0000
From: Karen O'Donoghue <odonoghue@isoc.org>
To: "ntpwg@lists.ntp.org" <ntpwg@lists.ntp.org>, "tictoc@ietf.org" <tictoc@ietf.org>
Thread-Topic: draft minutes from NTP/TICTOC meeting @ IETF 95 (4 April 2016)
Thread-Index: AQHRmtN73K3BWcnq30SExm5Zhy3X2g==
Date: Wed, 20 Apr 2016 07:08:47 +0000
Message-ID: <CC1E32D0-0449-4188-A1A3-F88599009153@isoc.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
authentication-results: lists.ntp.org; dkim=none (message not signed) header.d=none;lists.ntp.org; dmarc=none action=none header.from=isoc.org;
x-ms-exchange-messagesentrepresentingtype: 1
x-originating-ip: [46.218.58.213]
x-ms-office365-filtering-correlation-id: 92cbdcb9-5e4d-4bcd-438c-08d368ea9e6f
x-microsoft-exchange-diagnostics: 1; DM2PR0601MB1119; 5:mL2Jqic0B7DuaRBJ1DTnMzvwG22guEX4Y23rI9/NTKQdZK8jqPtFl+57CuSaE5BCkdF//Rzfq4IC2FQuRohpIxPibfvG81wslVABXQtyt3km56tmBFebSqPPYWd3Tdbopm6v+Ja+JuSh/Pdg30Q0uQ==; 24:6XmJQu1os3tguLXfvGJF/t7nxQkEXFcyL/g7u+G+I/mN4FhMuLoSx0TuxSRwLd1Vez0FWPjNmwXOE16KhT2dNG0QLzhDVmYl5bX9SRxmFTQ=
x-microsoft-antispam: UriScan:;BCL:0;PCL:0;RULEID:;SRVR:DM2PR0601MB1119;
x-microsoft-antispam-prvs: <DM2PR0601MB111927663F449235CC77AA7BC26D0@DM2PR0601MB1119.namprd06.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:;
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(9101521026)(601004)(2401047)(8121501046)(5005006)(10201501046)(3002001); SRVR:DM2PR0601MB1119; BCL:0; PCL:0; RULEID:; SRVR:DM2PR0601MB1119; 
x-forefront-prvs: 0918748D70
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(6009001)(54356999)(50986999)(33656002)(82746002)(2501003)(5008740100001)(3846002)(1096002)(87936001)(92566002)(586003)(102836003)(1220700001)(83716003)(6116002)(86362001)(122556002)(77096005)(107886002)(36756003)(66066001)(189998001)(99286002)(10400500002)(2900100001)(229853001)(106116001)(5004730100002)(2906002)(5001770100001)(3280700002)(3660700001)(5002640100001)(81166005)(104396002); DIR:OUT; SFP:1101; SCL:1; SRVR:DM2PR0601MB1119; H:DM2PR0601MB1118.namprd06.prod.outlook.com; FPR:; SPF:None; MLV:sfv; LANG:en; 
spamdiagnosticoutput: 1:23
spamdiagnosticmetadata: NSPM
Content-Type: text/plain; charset="us-ascii"
Content-ID: <01BAF6153405AA4B9200C6BB4062E209@namprd06.prod.outlook.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: isoc.org
X-MS-Exchange-CrossTenant-originalarrivaltime: 20 Apr 2016 07:08:47.4880 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 89f84dfb-7285-4810-bc4d-8b9b5794554f
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DM2PR0601MB1119
Archived-At: <http://mailarchive.ietf.org/arch/msg/tictoc/Wng8AjSGtu2nMYeO76iBFA0x3tE>
Subject: [TICTOC] draft minutes from NTP/TICTOC meeting @ IETF 95 (4 April 2016)
X-BeenThere: tictoc@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Timing over IP Connection and Transfer of Clock BOF <tictoc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tictoc>, <mailto:tictoc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tictoc/>
List-Post: <mailto:tictoc@ietf.org>
List-Help: <mailto:tictoc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tictoc>, <mailto:tictoc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 20 Apr 2016 07:09:10 -0000

Folks,

I have uploaded (and provided below) draft minutes from our meeting @ IETF =
95. If you have any comments or changes please speak up. Our next meeting w=
ill be 5 May 2016. Watch for the coming announcement.=20

Regards,
Karen

*************
NTP/TICTOC joint meeting
5 April 2016
Samuel Weiler as scribe

Karen gave an update on WG status.

Kristof gave an update on NTS, consistent with the slideware.

Sam (your scribe): what's the use case for client/mutual auth?  Are we
just creating an unneeded/unused code path?

Kristof: paid service.

Jared: cost of hardware for NTP is so low that the idea of a paid
service is not commmercially viable.  Can't imagine a case where we
need this in the protocol (v. IP filtering).  This just adds complexity
and opportunities for abuse.

Harlan: re: why do server auth: [didn't understand answer]

Karen proposes to set up a design team to resolve some of these
issues.  Send her mail if you're interested.

Brian Haberman (AD): asks that Karen be clear about what design team
is dealing with, and tell the WG that. Karen: is it okay if we say
"address WGLC comments"?  Brian: Yes, if it is scoped that narrowly.

Sharon Goldberg: Why do we have periodic server seed refresh?
(address this in design team?)

Karen: send that one to the list. =20

Karen: send any other issues to the list NOW, so we can assign them to
the design team, if appropriate.

--

Denis gave an update on the NTP BCP.  Karen asked when Denis thought
this might be ready for WGLC; Denis thinks MAYBE in July.

Harlan spoke sans slides, giving some background on the i-do,
last-extension, and mac-extension-field drafts. Danny continued the
discussion of the mac-extension-field draft.  Karen: does it make
sense to combine these?  Danny believes they are stand-alone.  Eric
Raymond thinks this design looks good; he'll supply a second
interoperable implementation.

Harlan, again sans slideware, gave short briefs on his three REFID
drafts.  Sharon asks if nonces are per-client or reused. Harlan
expects them to be per-client. Sharon sees issues with backwards
compatibility. Sharon counter-proposes that since a client knows where
it got its time, it can put put jibberish in REFIDs EXCEPT if it gets
asked for time by the server it knows it's using.  Harlan says that
might work, but he's not sure. Karen asks Sharon to summarize this on
list, and Harlan and Sharon to work on a combined statement.

Karen thinks these docs can proceed independently.

--

TICTOC part of meeting.

Karen gave a briefing on doc status.

Yuanlong Jiang presented on a YANG data model for IEEE 1588v2.  No one
in the room admitted to having read the document. Karen suggests
taking this to the list because the prople who might be paying
attention aren't in the meeting today. Karen explains that this may,
at some point, be fully transferred to 1588.

Yuanlong Jiang also presented on Scalable Synchronization Networks
(SCSN) Problems and Analysis. Karen pointed out that there is a
separate mailing list set up for this week; 5-6 people in the room are
aware of that list. Karen does not think adding this to the
(rechartered) WG's work plan is wise. Brian Haberman asks how much
this as been discussed with OPS/MGT folks. Brian would like to avoid
point solutions for different protocols. Karen suggests pulling
OPS/MGT types into the conversation on that mailing list.

--

Next steps.

Suresh will be the new AD.

Karen plans to continue monthly virtual interim schedule. Recharter
will presumably include NTPv4 items but not NTPv5 (yet). There are
several holes left in the current documentation set, including
interleave and mode 6. There are opportunities for those newer to the
IETF to edit documents. Karen is supportive of using little drafts to
clarify and correct issues.

Next virtual interim will be May 5th.


From nobody Wed Apr 20 05:04:38 2016
Return-Path: <bclaise@cisco.com>
X-Original-To: tictoc@ietf.org
Delivered-To: tictoc@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 3BA3112D130; Wed, 20 Apr 2016 05:04:34 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: "Benoit Claise" <bclaise@cisco.com>
To: "The IESG" <iesg@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.19.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20160420120434.32329.12375.idtracker@ietfa.amsl.com>
Date: Wed, 20 Apr 2016 05:04:34 -0700
Archived-At: <http://mailarchive.ietf.org/arch/msg/tictoc/Fn-K134Z3mIqwJdYoWw5jlnjKhk>
Cc: draft-ietf-tictoc-ptp-mib@ietf.org, dromasca@avaya.com, tictoc-chairs@ietf.org, tictoc@ietf.org, kodonog@pobox.com, rick.casarez@gmail.com
Subject: [TICTOC] Benoit Claise's Discuss on draft-ietf-tictoc-ptp-mib-08: (with DISCUSS)
X-BeenThere: tictoc@ietf.org
X-Mailman-Version: 2.1.17
List-Id: Timing over IP Connection and Transfer of Clock BOF <tictoc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tictoc>, <mailto:tictoc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tictoc/>
List-Post: <mailto:tictoc@ietf.org>
List-Help: <mailto:tictoc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tictoc>, <mailto:tictoc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 20 Apr 2016 12:04:34 -0000

Benoit Claise has entered the following ballot position for
draft-ietf-tictoc-ptp-mib-08: Discuss

When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)


Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html
for more information about IESG DISCUSS and COMMENT positions.


The document, along with other ballot positions, can be found here:
https://datatracker.ietf.org/doc/draft-ietf-tictoc-ptp-mib/



----------------------------------------------------------------------
DISCUSS:
----------------------------------------------------------------------

As stressed by Dan Romascanu part of his MIB doctor review, clearly not
ready to go

This is the MIB Doctor Review for draft-ietf-tictoc-ptp-mib-08.txt. 

Note that this document has a long history. A MIB Doctor review was
performed already by Bert Wijnen back in 2011. 

I do not believe that this document is ready for approval in its current
form. 

Here are my findings. 

 

1.       PARSING

Using smilint:

smistrip -d mibs docs/draft-ietf-tictoc-ptp-mib-08.txt

timeout 10 smilint -s -e -l 5 mibs/PTPBASE-MIB 2>report.txt

You can access any intermediately created files, the processing report
(which might be empty if no errors or warnings have been found), and
output files (in case of a conversion request) for reading and download
from a temporary server directory for approx. 24 hours.

While processing your request the following errors and/or warnings have
been found:

mibs/PTPBASE-MIB:426: [2] {bad-identifier-case} `XXX' should start with a
lower case letter

mibs/PTPBASE-MIB:426: [2] {object-identifier-not-prefix} Object
identifier element `XXX' name only allowed as first element

mibs/PTPBASE-MIB:26: [2] {module-identity-registration} illegal module
identity registration

Using smicng (thanks to Bert Wijnen):

C:\bw\smicng\work>smicng ptpbase.inc

Successful parsing

 

C:\bw\smicng\work>

 

**** now setup for STRICT checking:

 

C:\bw\smicng\work>smicstrict

 

C:\bw\smicng\work>smicng ptpbase.inc

W: f(rfc2863.mi2), (274,17) Item "ifPhysAddress" should have SIZE
specified

E: f(rfc2863.mi2), (1092,23) Index item "ifRcvAddressAddress" must be
defined with syntax that includes a SIZE

W: f(rfc2863.mi2), (1084,1) Row "ifRcvAddressEntry" has indexing that may
create variables with more than 128 sub-ids

W: f(rfc2863.mi2), (1103,17) Item "ifRcvAddressAddress" should have SIZE
specified

W: f(rfc2863.mi2), (1146,15) Variable "ifIndex" in notification
"linkDown" is an index for a table

W: f(rfc2863.mi2), (1158,15) Variable "ifIndex" in notification "linkUp"
is an index for a table

W: f(rfc2863.mi2), (1691,1) OBJECT-GROUP "ifOldObjectsGroup" is not used
in a MODULE-COMPLIANCE in current module

E: f(ptpbase.mi2), (413,19) Sub-Id for item "ptpbaseMIB" must be "number"
or "name(number)" format

 

*** 2 errors and 6 warnings in parsing

 

C:\bw\smicng\work>

 

As the two errors refer to the RFC 2863 module rather than to the
PTBASE-MIB: the compilation seems clean. 

2.       TEXTUAL CONVENTIONS are prefixed differently than the MIB
objects. This is not forbidden, but it creates inconsistency. Also the
prefix â€˜Clockâ€™ for the TCs hints to a more generic functionality,
although the TCs seem to be PTP-related. I would suggest prefixing the
TCs also with PTP or Ptp

3.       The following TC

ClockIdentity ::= TEXTUAL-CONVENTION

    STATUS          current

    DESCRIPTION

        "The clock Identity is an 8-octet array...

    REFERENCE       "Section 7.5.2.2.1 from [IEEE

    SYNTAX          OCTET STRING (SIZE (1..255))

If this is 8-Octet why is the OCTET STRING size 255?

4.       I see in the Abstract: 

   This memo specifies a MIB module in a manner that is both compliant
   to the SNMPv2 SMI, and semantically identical to the peer SNMPv1
   definitions.

 

Do you actually mean SMIv2 rather than SNMPv2 SMI? I am not sure why this
is important, but if this is important, please provide a reference to the
document that includes the â€˜peer SNMPv1â€™ definitions (probably SMIv1)

 

5.       Most of the document speaks about PTP, but in the DESCRIPTION
clause at page 7 it mentions:

 

        [IEEE 1588-2008] defines a protocol enabling precise
        synchronization of clocks in measurement and control systems
        implemented with packet-based networks, the Precision Time
        Protocol Version 2 (PTPv2).  This MIB does not address the
        earlier version IEEE Std. 1588(TM)-2002 (PTPv1). 

 

So, when it says â€˜PTPâ€™ does it mean PTPv2 or any version of PTP? It would
be good to clarify.

 

6.        The document uses the improper terminology â€˜MIBâ€™ when it means
MIB module. For example â€˜Relationship to other Profiles and MIBsâ€™ or
â€˜This MIB is intended to be used â€¦â€™ etc., etc.,

7.       Idnits complains about an obsolete reference to RFC 1906: 

-- Obsolete informational reference (is this intentional?): RFC 1906

     (Obsoleted by RFC 3417)

8.       I do not believe that Section 3 includes any useful information.


9.       The DESCRIPTION clause is unusually long and includes a lot of
abbreviations, terminology, architectural details and other pieces of
information which is not clear why they need to be hardcoded in the MIB
module. Maybe the place for all these is in the currently empty-content
section 3? 

10.   I do not understand how the ClockPortTransportTypeAddress TC works.
If this TC defines an address type why is it not an enumeration? What is
the string that for example indicates IPv6? Is it â€˜IPv6â€™? who guarantees
that a manager and an agent spell the same? Or is the intention to use
the list of identifiers for â€˜Well Known transport types for PTP
communicationâ€™at page 64? If yes, how is this extended? Probably an IANA
maintained enumerated TC would be a better solution.  

11.   Why is not the SYNTAX of ClockQualityClassType an enumeration, when
the DESCRIPTION indicates clearly that this is an enumeration. 

12.   I do not understand how ClockTimeInterval works. The example does
not help either. It says â€˜For example, 2.5 ns is expressed as 0000 0000
0002 8000 in Base16.â€™ and than the SYNTAX is

SYNTAX          OCTET STRING (SIZE (1..255))

What is the STRING for the object in this example? 

13.   For objects like ptpDomainIndex there is no need to copy again the
possible values in the DESCRIPTION clause, because these are already
listed in the TC.

14.   Why is ptpDomainClockPortsTotal of SYNTAX Gauge32? Does this value
change all the time? Does it latch at a max value? 

15.   There is no indication of behavior for counter discontinuity, or
object for counter discontinuity â€“ see section 4.6.1.2 in RFC 4181

16.   Why is the SYNATX of ptpbaseClockTransDefaultDSNumOfPorts
Counter32? This does not seem to be a counter, but an unsigned integer.

17.   The DESCRIPTION clause of the ptpbaseClockPortDSPTPVersion objects
reads: "This object specifies the PTP version being used.â€� However, the
DESCRIPTION clause of the MIB module says that this module refers only to
PTPv2. So what does this object stand for? And in any case, how is this
coded? (1) for v1 and (2) for v2? Then why is it not an enumerated
value?

18.   How does ptpbaseClockPortAssociateAddressType work? What would be
included under the AutonomousType SYNTAX to make possible
interoperability?

19.   The Security Considerations section does not follow the template
defined at http://trac.tools.ietf.org/area/ops/trac/wiki/mib-security.





From nobody Wed Apr 20 07:59:55 2016
Return-Path: <odonoghue@isoc.org>
X-Original-To: tictoc@ietfa.amsl.com
Delivered-To: tictoc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9292F12D9E9 for <tictoc@ietfa.amsl.com>; Wed, 20 Apr 2016 07:59:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.903
X-Spam-Level: 
X-Spam-Status: No, score=-1.903 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=isoc.onmicrosoft.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id V_IjXlUvVIkW for <tictoc@ietfa.amsl.com>; Wed, 20 Apr 2016 07:59:52 -0700 (PDT)
Received: from na01-bl2-obe.outbound.protection.outlook.com (mail-bl2on0073.outbound.protection.outlook.com [65.55.169.73]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 19F3412D587 for <tictoc@ietf.org>; Wed, 20 Apr 2016 07:59:52 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=isoc.onmicrosoft.com;  s=selector1-isoc-org; h=From:To:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=KxuQMUFWZZKgVmE975axvGxpPIvPYkbhAc0OBYmMp48=; b=oiK6xX58EuttfRi7UjV5O+KgsaZ8tsFHWOILd2qaYCMjwKkYGmotRFPyMsvoVFTiTRyiJVun7659Tw7N4Ikx409b7zSl7M/tlwQU5RDRuM4L0vANQB8bkYzkvGUvhOVD0MSa874w/isiL+bMd2KcUhugFKSmF1J9jIeSsbiYS4E=
Received: from DM2PR0601MB1118.namprd06.prod.outlook.com (10.160.218.139) by DM2PR0601MB1119.namprd06.prod.outlook.com (10.160.218.14) with Microsoft SMTP Server (TLS) id 15.1.453.26; Wed, 20 Apr 2016 14:59:49 +0000
Received: from DM2PR0601MB1118.namprd06.prod.outlook.com ([10.160.218.139]) by DM2PR0601MB1118.namprd06.prod.outlook.com ([10.160.218.139]) with mapi id 15.01.0466.022; Wed, 20 Apr 2016 14:59:49 +0000
From: Karen O'Donoghue <odonoghue@isoc.org>
To: "tictoc@ietf.org" <tictoc@ietf.org>
Thread-Topic: WGLC on draft-ietf-tictoc-ptp-enterprise-profile-06
Thread-Index: AQHRmxVIxH0uTbr/rUq9StTgt++Pgw==
Date: Wed, 20 Apr 2016 14:59:49 +0000
Message-ID: <15556A59-F26E-41DE-BF9E-BF6344F534A6@isoc.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
authentication-results: ietf.org; dkim=none (message not signed) header.d=none;ietf.org; dmarc=none action=none header.from=isoc.org;
x-ms-exchange-messagesentrepresentingtype: 1
x-originating-ip: [46.218.58.213]
x-ms-office365-filtering-correlation-id: 4df93c18-46c3-4add-bd4b-08d3692c6bba
x-microsoft-exchange-diagnostics: 1; DM2PR0601MB1119; 5:ZNfO8CtCNNrQWvDcL5f1bZdu8ddAFqwbn2kMvXAmbBB4L1Rw8XTRZGDK+c3h3Zb4fP2+nc+8ouX1SYfZ4wmu4BhvJc/KZGDvja6GxK1pb5REPEfggJIZ977vHlDuVMXayASTeyh/v2YSwqwNqvKsug==; 24:gMv2DkRt0eR797Wc4xrFayljvDra14ZqLl4591LE9tgdvuzKVu9m7+2yUyAAzBOUszcxjg2K+ihJGj8OHSVYrk2ZM4c8v+NLny/ITNkE7+4=
x-microsoft-antispam: UriScan:;BCL:0;PCL:0;RULEID:;SRVR:DM2PR0601MB1119;
x-microsoft-antispam-prvs: <DM2PR0601MB111902CCAD910464B3C30A86C26D0@DM2PR0601MB1119.namprd06.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:;
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(9101521026)(601004)(2401047)(8121501046)(5005006)(10201501046)(3002001); SRVR:DM2PR0601MB1119; BCL:0; PCL:0; RULEID:; SRVR:DM2PR0601MB1119; 
x-forefront-prvs: 0918748D70
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(6009001)(5640700001)(99286002)(10400500002)(229853001)(2900100001)(106116001)(2351001)(15975445007)(110136002)(77096005)(122556002)(189998001)(36756003)(230783001)(66066001)(5002640100001)(3660700001)(3280700002)(81166005)(5004730100002)(11100500001)(2906002)(5008740100001)(82746002)(2501003)(1096002)(3846002)(87936001)(19580395003)(54356999)(33656002)(4326007)(50986999)(83716003)(102836003)(1220700001)(86362001)(6116002)(92566002)(586003); DIR:OUT; SFP:1101; SCL:1; SRVR:DM2PR0601MB1119; H:DM2PR0601MB1118.namprd06.prod.outlook.com; FPR:; SPF:None; MLV:sfv; LANG:en; 
spamdiagnosticoutput: 1:23
spamdiagnosticmetadata: NSPM
Content-Type: text/plain; charset="us-ascii"
Content-ID: <25BE3A9857A4E847976138D39F970BFF@namprd06.prod.outlook.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: isoc.org
X-MS-Exchange-CrossTenant-originalarrivaltime: 20 Apr 2016 14:59:49.1874 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 89f84dfb-7285-4810-bc4d-8b9b5794554f
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DM2PR0601MB1119
Archived-At: <http://mailarchive.ietf.org/arch/msg/tictoc/xCgHtXz5JsyEwDY0gbmDp4UxeFg>
Cc: "ntpwg@lists.ntp.org" <ntpwg@lists.ntp.org>
Subject: [TICTOC] WGLC on draft-ietf-tictoc-ptp-enterprise-profile-06
X-BeenThere: tictoc@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Timing over IP Connection and Transfer of Clock BOF <tictoc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tictoc>, <mailto:tictoc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tictoc/>
List-Post: <mailto:tictoc@ietf.org>
List-Help: <mailto:tictoc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tictoc>, <mailto:tictoc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 20 Apr 2016 14:59:54 -0000

Folks,=20

This message begins a 2 week WGLC on the following document:=20

Enterprise Profile for the Precision Time Protocol With Mixed Multicast and=
 Unicast Messages
https://tools.ietf.org/html/draft-ietf-tictoc-ptp-enterprise-profile-06

Please review the referenced document and send any comments to the mailing =
list including your assessment of whether this document is mature enough to=
 proceed to the IESG. Please note that these messages of support for progre=
ssion to the mailing list will be used to determine WG consensus to proceed=
.=20

Please send all comments in by Wednesday 4 May 2016.=20

Thank you!
Karen



From nobody Wed Apr 20 08:12:28 2016
Return-Path: <odonoghue@isoc.org>
X-Original-To: tictoc@ietfa.amsl.com
Delivered-To: tictoc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 995C412E59C; Wed, 20 Apr 2016 08:12:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level: 
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=isoc.onmicrosoft.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id E755ameojG0G; Wed, 20 Apr 2016 08:12:25 -0700 (PDT)
Received: from na01-bn1-obe.outbound.protection.outlook.com (mail-bn1bon0624.outbound.protection.outlook.com [IPv6:2a01:111:f400:fc10::1:624]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8735412E58A; Wed, 20 Apr 2016 08:12:24 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=isoc.onmicrosoft.com;  s=selector1-isoc-org; h=From:To:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=pk8tJ541eDME2R51JJbmASG+HtKiLIQZiPslVd5sLjQ=; b=WI39Jdb5n7cSrxMhc9cHoKXQC6lDNUIxTThs99GLzYq789Z5IjVBt6Oo/Vp80Ii29sXpFiJZsAQPHzSZdJ6g0OpQauYlEes0+1jiau051bovhLiPmj0FbSwe3bYcsuxQPgzxU9QQCWr9aodaD51oRfWklwxf3PUP3a6mtrZKTJ8=
Received: from DM2PR0601MB1118.namprd06.prod.outlook.com (10.160.218.139) by DM2PR0601MB1119.namprd06.prod.outlook.com (10.160.218.14) with Microsoft SMTP Server (TLS) id 15.1.453.26; Wed, 20 Apr 2016 15:12:06 +0000
Received: from DM2PR0601MB1118.namprd06.prod.outlook.com ([10.160.218.139]) by DM2PR0601MB1118.namprd06.prod.outlook.com ([10.160.218.139]) with mapi id 15.01.0466.022; Wed, 20 Apr 2016 15:12:06 +0000
From: Karen O'Donoghue <odonoghue@isoc.org>
To: "ntpwg@lists.ntp.org" <ntpwg@lists.ntp.org>, "tictoc@ietf.org" <tictoc@ietf.org>
Thread-Topic: Joint NTP/TICTOC working group virtual interim meeting - 5 May 2016 @ 1530 UTC 
Thread-Index: AQHRmxcAz9ELFD9DGkydX0PB4WDJAA==
Date: Wed, 20 Apr 2016 15:12:06 +0000
Message-ID: <E64F7DBF-A248-43B8-9EEE-76F05BC443B7@isoc.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
authentication-results: lists.ntp.org; dkim=none (message not signed) header.d=none;lists.ntp.org; dmarc=none action=none header.from=isoc.org;
x-ms-exchange-messagesentrepresentingtype: 1
x-originating-ip: [46.218.58.213]
x-ms-office365-filtering-correlation-id: 190979c5-d958-49f1-7e81-08d3692e22ce
x-microsoft-exchange-diagnostics: 1; DM2PR0601MB1119; 5:YH7QkmZ6HKLb8t414SUlC22S8jdAesNhlvL+FyWo4EP+1O0V4MjGISvvZOiIHHGlExo3cQ8UKhO1TfKTuj7NN7NAVTDGZaYf7NyXWk01es3CcjM5c8J9LSqeKHDw5wvmYZPhBZlIIaqqpH27yO4E4g==; 24:YQbaKlLrqqFVUulxS44NMRHmg7c/gd1dNw8TomoKIFV1ioZUdGJfrEZhcKoIECKG1zzUfBxYyJrXFQWfY3+WZ3qdOh+8oMuQArjAPQ6AYhs=
x-microsoft-antispam: UriScan:;BCL:0;PCL:0;RULEID:;SRVR:DM2PR0601MB1119;
x-microsoft-antispam-prvs: <DM2PR0601MB1119C87E52C1299ACF996FC3C26D0@DM2PR0601MB1119.namprd06.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:;
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(9101521026)(601004)(2401047)(8121501046)(5005006)(10201501046)(3002001); SRVR:DM2PR0601MB1119; BCL:0; PCL:0; RULEID:; SRVR:DM2PR0601MB1119; 
x-forefront-prvs: 0918748D70
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(6009001)(377454003)(54356999)(19580395003)(16799955002)(50986999)(33656002)(4326007)(82746002)(2501003)(5008740100001)(3846002)(1096002)(87936001)(92566002)(586003)(1220700001)(83716003)(6116002)(86362001)(102836003)(77096005)(122556002)(66066001)(36756003)(189998001)(99286002)(10400500002)(2900100001)(229853001)(106116001)(15975445007)(11100500001)(2906002)(5004730100002)(5001770100001)(3280700002)(3660700001)(5002640100001)(551544002)(81166005); DIR:OUT; SFP:1101; SCL:1; SRVR:DM2PR0601MB1119; H:DM2PR0601MB1118.namprd06.prod.outlook.com; FPR:; SPF:None; MLV:sfv; LANG:en; 
spamdiagnosticoutput: 1:23
spamdiagnosticmetadata: NSPM
Content-Type: text/plain; charset="us-ascii"
Content-ID: <E85AE9FA5406AE48B1380B837317598C@namprd06.prod.outlook.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: isoc.org
X-MS-Exchange-CrossTenant-originalarrivaltime: 20 Apr 2016 15:12:06.0867 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 89f84dfb-7285-4810-bc4d-8b9b5794554f
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DM2PR0601MB1119
Archived-At: <http://mailarchive.ietf.org/arch/msg/tictoc/TEsNMeBe81imkR7VemFW6pncid4>
Cc: "iesg-secretary@ietf.org" <iesg-secretary@ietf.org>, Suresh Krishnan <suresh.krishnan@ericsson.com>
Subject: [TICTOC] Joint NTP/TICTOC working group virtual interim meeting - 5 May 2016 @ 1530 UTC
X-BeenThere: tictoc@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Timing over IP Connection and Transfer of Clock BOF <tictoc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tictoc>, <mailto:tictoc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tictoc/>
List-Post: <mailto:tictoc@ietf.org>
List-Help: <mailto:tictoc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tictoc>, <mailto:tictoc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 20 Apr 2016 15:12:26 -0000

There will be a joint meeting of the NTP and TICTOC working groups on=20
Thursday 5 May 2016 @ 11:30 am EDT (15:30 UTC)

The agenda of this meeting will include:=20
- NTP WG Status
- Preliminary report from NTS WGLC design team
- NTS implementation updates
- NTP BCP
- Next steps for extension field and REFID drafts
- TICTOC WG Status
- PTP Profile WGLC Comments
- AOB & Next meeting planning

NTP/TICTOC joint virtual interim meeting
Thursday, May 5, 2016
11:30 am  |  Eastern Daylight Time (New York, GMT-04:00)  |  1 hr 30 mins
=20
https://isoc.webex.com/isoc/j.php?MTID=3Dmcde7866f39032e6d059b3dcba4c0456e
Meeting number:	921 731 640
Meeting password:	timesynch
=20
Join by phone
1-877-668-4493 Call-in toll-free number (US/Canada)
1-650-479-3208 Call-in toll number (US/Canada)

Access code: 921 731 640

Global call-in numbers =20
https://isoc.webex.com/isoc/globalcallin.php?serviceType=3DMC&ED=3D43826471=
7&tollFree=3D1

Toll-free calling restrictions
https://www.webex.com/pdf/tollfree_restrictions.pdf

Add to your calendar
https://isoc.webex.com/isoc/j.php?MTID=3Dme2102d9d25ca6882983e05d80aa5a861=
=20


From nobody Wed Apr 20 13:35:57 2016
Return-Path: <iesg-secretary@ietf.org>
X-Original-To: tictoc@ietf.org
Delivered-To: tictoc@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id B018712E8DF; Wed, 20 Apr 2016 13:35:55 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: IESG Secretary <iesg-secretary@ietf.org>
To: "IETF Announcement List" <ietf-announce@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.19.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20160420203555.907.61462.idtracker@ietfa.amsl.com>
Date: Wed, 20 Apr 2016 13:35:55 -0700
Archived-At: <http://mailarchive.ietf.org/arch/msg/tictoc/qHeZFHcShbVyw-P09E54SZ1cBQw>
Cc: ntpwg@lists.ntp.org, tictoc@ietf.org
Subject: [TICTOC] Joint NTP/TICTOC working group virtual interim meeting - 5 May 2016 @ 1530 UTC
X-BeenThere: tictoc@ietf.org
X-Mailman-Version: 2.1.17
Reply-To: ietf@ietf.org
List-Id: Timing over IP Connection and Transfer of Clock BOF <tictoc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tictoc>, <mailto:tictoc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tictoc/>
List-Post: <mailto:tictoc@ietf.org>
List-Help: <mailto:tictoc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tictoc>, <mailto:tictoc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 20 Apr 2016 20:35:55 -0000

There will be a joint meeting of the Network Time Protocol (ntp) and 
Timing over IP Connection and Transfer of Clock (tictoc) working groups 
on Thursday 5 May 2016 @ 11:30 am EDT (15:30 UTC)

The agenda of this meeting will include:
- NTP WG Status
- Preliminary report from NTS WGLC design team
- NTS implementation updates
- NTP BCP
- Next steps for extension field and REFID drafts
- TICTOC WG Status
- PTP Profile WGLC Comments
- AOB & Next meeting planning

NTP/TICTOC joint virtual interim meeting
Thursday, May 5, 2016
11:30 am | Eastern Daylight Time (New York, GMT-04:00) | 1 hr 30 mins

https://isoc.webex.com/isoc/j.php?MTID=mcde7866f39032e6d059b3dcba4c0456e
Meeting number: 921 731 640
Meeting password: timesynch

Join by phone
1-877-668-4493 Call-in toll-free number (US/Canada)
1-650-479-3208 Call-in toll number (US/Canada)

Access code: 921 731 640

Global call-in numbers
https://isoc.webex.com/isoc/globalcallin.php?serviceType=MC&ED=438264717&tollFree=1

Toll-free calling restrictions
https://www.webex.com/pdf/tollfree_restrictions.pdf

Add to your calendar
https://isoc.webex.com/isoc/j.php?MTID=me2102d9d25ca6882983e05d80aa5a861 


From nobody Wed Apr 20 15:57:36 2016
Return-Path: <alissa@cooperw.in>
X-Original-To: tictoc@ietfa.amsl.com
Delivered-To: tictoc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F1C7012E7AA for <tictoc@ietfa.amsl.com>; Wed, 20 Apr 2016 15:57:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.72
X-Spam-Level: 
X-Spam-Status: No, score=-2.72 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cooperw.in header.b=nqjmWaaI; dkim=pass (1024-bit key) header.d=messagingengine.com header.b=ILLCxXuQ
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NdeYDuhpgycs for <tictoc@ietfa.amsl.com>; Wed, 20 Apr 2016 15:57:27 -0700 (PDT)
Received: from out2-smtp.messagingengine.com (out2-smtp.messagingengine.com [66.111.4.26]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 93AF412E796 for <tictoc@ietf.org>; Wed, 20 Apr 2016 15:57:27 -0700 (PDT)
Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id 292D021004 for <tictoc@ietf.org>; Wed, 20 Apr 2016 18:50:47 -0400 (EDT)
Received: from frontend2 ([10.202.2.161]) by compute1.internal (MEProxy); Wed, 20 Apr 2016 18:50:47 -0400
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=cooperw.in; h=cc :content-type:date:from:in-reply-to:message-id:mime-version :references:subject:to:x-sasl-enc:x-sasl-enc; s=mesmtp; bh=d1X/I n376IZz3wXAQRpXTIfRymY=; b=nqjmWaaIjatcWMtf+OXCb1G1FD4h8Sv5KLUY9 Itsd1LeguakQVZUKJJ/HJLHfROyaZCarTRbgJdkzPxdBOlToaG2xL1PXDvbdfajc u3pipVWKltiaKjvvIR/SP/S+x7Ub3TR3pKvvVXq8CrnESspt6m7odXkpicUZBazj 8q+t5w=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-sasl-enc :x-sasl-enc; s=smtpout; bh=d1X/In376IZz3wXAQRpXTIfRymY=; b=ILLCx XuQqQR0xjdzaeK2nN2N6CLGYQQcVKB9iriZmwNhm9CG/VYtFFBlCkwPjmqkmmYua gsjAHYfSZmX0RKnDRI/2rTi9I0meclie8JukwH+AednPlwwovQHwrRSQ2dh4Kj3o SjA54tjoM6U0uO24iF8kDjj0lylJl5gxlSarK0=
X-Sasl-enc: 3aPOUST7iULI28PgGGakMCCEIL2LAc+//FfC9CKID6+D 1461192646
Received: from dhcp-171-68-20-83.cisco.com (dhcp-171-68-20-83.cisco.com [171.68.20.83]) by mail.messagingengine.com (Postfix) with ESMTPA id 52B336801D1; Wed, 20 Apr 2016 18:50:46 -0400 (EDT)
Content-Type: multipart/alternative; boundary="Apple-Mail=_6CADB2B8-72C0-4B72-BE56-753D908ECB8A"
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
From: Alissa Cooper <alissa@cooperw.in>
In-Reply-To: <60449605-8547-4b73-e3aa-0c17c2c0a25e@bogus.com>
Date: Wed, 20 Apr 2016 15:50:46 -0700
Message-Id: <0A8B7D71-8F40-420F-81B0-C1E109DD2D55@cooperw.in>
References: <20160419171216.31521.25135.idtracker@ietfa.amsl.com> <60449605-8547-4b73-e3aa-0c17c2c0a25e@bogus.com>
To: joel jaeggli <joelja@bogus.com>
X-Mailer: Apple Mail (2.3124)
Archived-At: <http://mailarchive.ietf.org/arch/msg/tictoc/rzxFv6L7fgUZZsnS8E_7FdAxEfk>
Cc: draft-ietf-tictoc-ptp-mib@ietf.org, tictoc-chairs@ietf.org, kodonog@pobox.com, IESG <iesg@ietf.org>, tictoc@ietf.org
Subject: Re: [TICTOC] Alissa Cooper's No Objection on draft-ietf-tictoc-ptp-mib-08: (with COMMENT)
X-BeenThere: tictoc@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Timing over IP Connection and Transfer of Clock BOF <tictoc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tictoc>, <mailto:tictoc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tictoc/>
List-Post: <mailto:tictoc@ietf.org>
List-Help: <mailto:tictoc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tictoc>, <mailto:tictoc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 20 Apr 2016 22:57:29 -0000

--Apple-Mail=_6CADB2B8-72C0-4B72-BE56-753D908ECB8A
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8


> On Apr 19, 2016, at 1:23 PM, joel jaeggli <joelja@bogus.com> wrote:
>=20
> On 4/19/16 10:12 AM, Alissa Cooper wrote:
>> Alissa Cooper has entered the following ballot position for
>> draft-ietf-tictoc-ptp-mib-08: No Objection
>>=20
>> When responding, please keep the subject line intact and reply to all
>> email addresses included in the To and CC lines. (Feel free to cut =
this
>> introductory paragraph, however.)
>>=20
>>=20
>> Please refer to =
https://www.ietf.org/iesg/statement/discuss-criteria.html
>> for more information about IESG DISCUSS and COMMENT positions.
>>=20
>>=20
>> The document, along with other ballot positions, can be found here:
>> https://datatracker.ietf.org/doc/draft-ietf-tictoc-ptp-mib/
>>=20
>>=20
>>=20
>> =
----------------------------------------------------------------------
>> COMMENT:
>> =
----------------------------------------------------------------------
>>=20
>> (1) The ClockIdentity is described as being generated based on an =
EUI-64
>> address as described in IEEE 1588-2008 Section 7.5.2.2.2. But in IEEE
>> 1588-2008, there are two different ways the clock identifier can be
>> generated, the other being a non-EUI-64 address defined in 7.5.2.2.3. =
Why
>> is that option left out of the ClockIdentity description?
>>=20
>> In general I was dismayed to see the re-use of EUI-64 for clock =
identity
>> for the security and privacy drawbacks, since it's not particularly =
clear
>> that re-using those identifiers is necessary here. But if such a fix =
is
>> warranted this MIB is not the place to do it in any event.
>=20
> I don't see a whole lot wrong with using a mac address as an =
identifier
> in a management system. 1588 speakers are frequently adjecent to each
> other and almost always within the same management domain,

Are you saying you don=E2=80=99t see a problem with not reflecting the =
mechanisms from 7.5.2.2.3 here? Or just generally that you don=E2=80=99t =
see a problem with using a MAC address as an identifier in this case?

Alissa

>=20
>> (2) Looking at
>> https://trac.tools.ietf.org/area/ops/trac/wiki/mib-security I recall =
that
>> other MIB documents we've reviewed recently have listed out the =
specific
>> tables/objects that may be considered vulnerable or sensitive, even =
if
>> those objects are read-only. Why doesn't this document do that? I =
would
>> think all of the clock identity objects would belong in that bucket =
at a
>> minimum.


--Apple-Mail=_6CADB2B8-72C0-4B72-BE56-753D908ECB8A
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=utf-8

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html =
charset=3Dutf-8"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" =
class=3D""><br class=3D""><div><blockquote type=3D"cite" class=3D""><div =
class=3D"">On Apr 19, 2016, at 1:23 PM, joel jaeggli &lt;<a =
href=3D"mailto:joelja@bogus.com" class=3D"">joelja@bogus.com</a>&gt; =
wrote:</div><br class=3D"Apple-interchange-newline"><div class=3D""><span =
style=3D"font-family: Helvetica; font-size: 12px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
orphans: auto; text-align: start; text-indent: 0px; text-transform: =
none; white-space: normal; widows: auto; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; float: none; display: inline =
!important;" class=3D"">On 4/19/16 10:12 AM, Alissa Cooper =
wrote:</span><br style=3D"font-family: Helvetica; font-size: 12px; =
font-style: normal; font-variant-caps: normal; font-weight: normal; =
letter-spacing: normal; orphans: auto; text-align: start; text-indent: =
0px; text-transform: none; white-space: normal; widows: auto; =
word-spacing: 0px; -webkit-text-stroke-width: 0px;" class=3D""><blockquote=
 type=3D"cite" style=3D"font-family: Helvetica; font-size: 12px; =
font-style: normal; font-variant-caps: normal; font-weight: normal; =
letter-spacing: normal; orphans: auto; text-align: start; text-indent: =
0px; text-transform: none; white-space: normal; widows: auto; =
word-spacing: 0px; -webkit-text-stroke-width: 0px;" class=3D"">Alissa =
Cooper has entered the following ballot position for<br =
class=3D"">draft-ietf-tictoc-ptp-mib-08: No Objection<br class=3D""><br =
class=3D"">When responding, please keep the subject line intact and =
reply to all<br class=3D"">email addresses included in the To and CC =
lines. (Feel free to cut this<br class=3D"">introductory paragraph, =
however.)<br class=3D""><br class=3D""><br class=3D"">Please refer to <a =
href=3D"https://www.ietf.org/iesg/statement/discuss-criteria.html" =
class=3D"">https://www.ietf.org/iesg/statement/discuss-criteria.html</a><b=
r class=3D"">for more information about IESG DISCUSS and COMMENT =
positions.<br class=3D""><br class=3D""><br class=3D"">The document, =
along with other ballot positions, can be found here:<br class=3D""><a =
href=3D"https://datatracker.ietf.org/doc/draft-ietf-tictoc-ptp-mib/" =
class=3D"">https://datatracker.ietf.org/doc/draft-ietf-tictoc-ptp-mib/</a>=
<br class=3D""><br class=3D""><br class=3D""><br =
class=3D"">---------------------------------------------------------------=
-------<br class=3D"">COMMENT:<br =
class=3D"">---------------------------------------------------------------=
-------<br class=3D""><br class=3D"">(1) The ClockIdentity is described =
as being generated based on an EUI-64<br class=3D"">address as described =
in IEEE 1588-2008 Section 7.5.2.2.2. But in IEEE<br class=3D"">1588-2008, =
there are two different ways the clock identifier can be<br =
class=3D"">generated, the other being a non-EUI-64 address defined in =
7.5.2.2.3. Why<br class=3D"">is that option left out of the =
ClockIdentity description?<br class=3D""><br class=3D"">In general I was =
dismayed to see the re-use of EUI-64 for clock identity<br class=3D"">for =
the security and privacy drawbacks, since it's not particularly clear<br =
class=3D"">that re-using those identifiers is necessary here. But if =
such a fix is<br class=3D"">warranted this MIB is not the place to do it =
in any event.<br class=3D""></blockquote><br style=3D"font-family: =
Helvetica; font-size: 12px; font-style: normal; font-variant-caps: =
normal; font-weight: normal; letter-spacing: normal; orphans: auto; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: =
0px;" class=3D""><span style=3D"font-family: Helvetica; font-size: 12px; =
font-style: normal; font-variant-caps: normal; font-weight: normal; =
letter-spacing: normal; orphans: auto; text-align: start; text-indent: =
0px; text-transform: none; white-space: normal; widows: auto; =
word-spacing: 0px; -webkit-text-stroke-width: 0px; float: none; display: =
inline !important;" class=3D"">I don't see a whole lot wrong with using =
a mac address as an identifier</span><br style=3D"font-family: =
Helvetica; font-size: 12px; font-style: normal; font-variant-caps: =
normal; font-weight: normal; letter-spacing: normal; orphans: auto; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: =
0px;" class=3D""><span style=3D"font-family: Helvetica; font-size: 12px; =
font-style: normal; font-variant-caps: normal; font-weight: normal; =
letter-spacing: normal; orphans: auto; text-align: start; text-indent: =
0px; text-transform: none; white-space: normal; widows: auto; =
word-spacing: 0px; -webkit-text-stroke-width: 0px; float: none; display: =
inline !important;" class=3D"">in a management system. 1588 speakers are =
frequently adjecent to each</span><br style=3D"font-family: Helvetica; =
font-size: 12px; font-style: normal; font-variant-caps: normal; =
font-weight: normal; letter-spacing: normal; orphans: auto; text-align: =
start; text-indent: 0px; text-transform: none; white-space: normal; =
widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;" =
class=3D""><span style=3D"font-family: Helvetica; font-size: 12px; =
font-style: normal; font-variant-caps: normal; font-weight: normal; =
letter-spacing: normal; orphans: auto; text-align: start; text-indent: =
0px; text-transform: none; white-space: normal; widows: auto; =
word-spacing: 0px; -webkit-text-stroke-width: 0px; float: none; display: =
inline !important;" class=3D"">other and almost always within the same =
management domain,</span><br style=3D"font-family: Helvetica; font-size: =
12px; font-style: normal; font-variant-caps: normal; font-weight: =
normal; letter-spacing: normal; orphans: auto; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; widows: =
auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;" =
class=3D""></div></blockquote><div><br class=3D""></div><div>Are you =
saying you don=E2=80=99t see a problem with not reflecting the =
mechanisms from 7.5.2.2.3 here? Or just generally that you don=E2=80=99t =
see a problem with using a MAC address as an identifier in this =
case?</div><div><br class=3D""></div><div>Alissa</div><br =
class=3D""><blockquote type=3D"cite" class=3D""><div class=3D""><br =
style=3D"font-family: Helvetica; font-size: 12px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
orphans: auto; text-align: start; text-indent: 0px; text-transform: =
none; white-space: normal; widows: auto; word-spacing: 0px; =
-webkit-text-stroke-width: 0px;" class=3D""><blockquote type=3D"cite" =
style=3D"font-family: Helvetica; font-size: 12px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
orphans: auto; text-align: start; text-indent: 0px; text-transform: =
none; white-space: normal; widows: auto; word-spacing: 0px; =
-webkit-text-stroke-width: 0px;" class=3D"">(2) Looking at<br =
class=3D""><a =
href=3D"https://trac.tools.ietf.org/area/ops/trac/wiki/mib-security" =
class=3D"">https://trac.tools.ietf.org/area/ops/trac/wiki/mib-security</a>=
 I recall that<br class=3D"">other MIB documents we've reviewed recently =
have listed out the specific<br class=3D"">tables/objects that may be =
considered vulnerable or sensitive, even if<br class=3D"">those objects =
are read-only. Why doesn't this document do that? I would<br =
class=3D"">think all of the clock identity objects would belong in that =
bucket at a<br =
class=3D"">minimum.</blockquote></div></blockquote></div><br =
class=3D""></body></html>=

--Apple-Mail=_6CADB2B8-72C0-4B72-BE56-753D908ECB8A--


From nobody Wed Apr 20 16:04:43 2016
Return-Path: <joelja@bogus.com>
X-Original-To: tictoc@ietfa.amsl.com
Delivered-To: tictoc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 51D5612DC7A; Wed, 20 Apr 2016 16:04:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.896
X-Spam-Level: 
X-Spam-Status: No, score=-7.896 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.996] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CqrMzNKxWNx5; Wed, 20 Apr 2016 16:04:39 -0700 (PDT)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9634312DA0B; Wed, 20 Apr 2016 16:04:39 -0700 (PDT)
Received: from mb-2.local ([IPv6:2601:647:4204:51:bc83:5fac:994b:9466]) (authenticated bits=0) by nagasaki.bogus.com (8.14.9/8.14.9) with ESMTP id u3KN4YGP039901 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Wed, 20 Apr 2016 23:04:35 GMT (envelope-from joelja@bogus.com)
To: Alissa Cooper <alissa@cooperw.in>
References: <20160419171216.31521.25135.idtracker@ietfa.amsl.com> <60449605-8547-4b73-e3aa-0c17c2c0a25e@bogus.com> <0A8B7D71-8F40-420F-81B0-C1E109DD2D55@cooperw.in>
From: joel jaeggli <joelja@bogus.com>
Message-ID: <bae007da-a3b0-c004-1db6-d376b6022f67@bogus.com>
Date: Wed, 20 Apr 2016 16:04:32 -0700
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:45.0) Gecko/20100101 Thunderbird/45.0
MIME-Version: 1.0
In-Reply-To: <0A8B7D71-8F40-420F-81B0-C1E109DD2D55@cooperw.in>
Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="HeAlJdMjRJIpodamq8R4rDRAHUBar5PEb"
Archived-At: <http://mailarchive.ietf.org/arch/msg/tictoc/07z7kWNw0U3DgowEwB0QuwTHcNU>
Cc: draft-ietf-tictoc-ptp-mib@ietf.org, tictoc-chairs@ietf.org, kodonog@pobox.com, IESG <iesg@ietf.org>, tictoc@ietf.org
Subject: Re: [TICTOC] Alissa Cooper's No Objection on draft-ietf-tictoc-ptp-mib-08: (with COMMENT)
X-BeenThere: tictoc@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Timing over IP Connection and Transfer of Clock BOF <tictoc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tictoc>, <mailto:tictoc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tictoc/>
List-Post: <mailto:tictoc@ietf.org>
List-Help: <mailto:tictoc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tictoc>, <mailto:tictoc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 20 Apr 2016 23:04:41 -0000

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--HeAlJdMjRJIpodamq8R4rDRAHUBar5PEb
Content-Type: multipart/mixed; boundary="nSW9StxirmVkM1PVfFwDMS6lWWeMqHmTv"
From: joel jaeggli <joelja@bogus.com>
To: Alissa Cooper <alissa@cooperw.in>
Cc: IESG <iesg@ietf.org>, tictoc-chairs@ietf.org, tictoc@ietf.org,
 draft-ietf-tictoc-ptp-mib@ietf.org, kodonog@pobox.com
Message-ID: <bae007da-a3b0-c004-1db6-d376b6022f67@bogus.com>
Subject: Re: Alissa Cooper's No Objection on draft-ietf-tictoc-ptp-mib-08:
 (with COMMENT)
References: <20160419171216.31521.25135.idtracker@ietfa.amsl.com>
 <60449605-8547-4b73-e3aa-0c17c2c0a25e@bogus.com>
 <0A8B7D71-8F40-420F-81B0-C1E109DD2D55@cooperw.in>
In-Reply-To: <0A8B7D71-8F40-420F-81B0-C1E109DD2D55@cooperw.in>

--nSW9StxirmVkM1PVfFwDMS6lWWeMqHmTv
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable

On 4/20/16 3:50 PM, Alissa Cooper wrote:
>=20
>> On Apr 19, 2016, at 1:23 PM, joel jaeggli <joelja@bogus.com
>> <mailto:joelja@bogus.com>> wrote:
>>
>> On 4/19/16 10:12 AM, Alissa Cooper wrote:
>>> Alissa Cooper has entered the following ballot position for
>>> draft-ietf-tictoc-ptp-mib-08: No Objection
>>>
>>> When responding, please keep the subject line intact and reply to all=

>>> email addresses included in the To and CC lines. (Feel free to cut th=
is
>>> introductory paragraph, however.)
>>>
>>>
>>> Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.=
html
>>> for more information about IESG DISCUSS and COMMENT positions.
>>>
>>>
>>> The document, along with other ballot positions, can be found here:
>>> https://datatracker.ietf.org/doc/draft-ietf-tictoc-ptp-mib/
>>>
>>>
>>>
>>> ---------------------------------------------------------------------=
-
>>> COMMENT:
>>> ---------------------------------------------------------------------=
-
>>>
>>> (1) The ClockIdentity is described as being generated based on an EUI=
-64
>>> address as described in IEEE 1588-2008 Section 7.5.2.2.2. But in IEEE=

>>> 1588-2008, there are two different ways the clock identifier can be
>>> generated, the other being a non-EUI-64 address defined in 7.5.2.2.3.=
 Why
>>> is that option left out of the ClockIdentity description?
>>>
>>> In general I was dismayed to see the re-use of EUI-64 for clock ident=
ity
>>> for the security and privacy drawbacks, since it's not particularly c=
lear
>>> that re-using those identifiers is necessary here. But if such a fix =
is
>>> warranted this MIB is not the place to do it in any event.
>>
>> I don't see a whole lot wrong with using a mac address as an identifie=
r
>> in a management system. 1588 speakers are frequently adjecent to each
>> other and almost always within the same management domain,
>=20
> Are you saying you don=E2=80=99t see a problem with not reflecting the
> mechanisms from 7.5.2.2.3 here? Or just generally that you don=E2=80=99=
t see a
> problem with using a MAC address as an identifier in this case?

I don't see a problem generally with using a mac address as a unique
identifier in a management system. sources of actual genuine uniqueness
that are preserved across firmware upgrades, reboots and config wipes
and which are common across all platforms are hard enough to come by
without ruling them out. they're not of course immutable if you're
disinclined to expose them.

Are they appropriate in general for exposure on the internet or in local
but untrusted environments? No; 1588 master-slave relationships  are
also inappropriate under such circumstances.

> Alissa
>=20
>>
>>> (2) Looking at
>>> https://trac.tools.ietf.org/area/ops/trac/wiki/mib-security I recall =
that
>>> other MIB documents we've reviewed recently have listed out the speci=
fic
>>> tables/objects that may be considered vulnerable or sensitive, even i=
f
>>> those objects are read-only. Why doesn't this document do that? I wou=
ld
>>> think all of the clock identity objects would belong in that bucket a=
t a
>>> minimum.
>=20



--nSW9StxirmVkM1PVfFwDMS6lWWeMqHmTv--

--HeAlJdMjRJIpodamq8R4rDRAHUBar5PEb
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2
Comment: GPGTools - http://gpgtools.org

iEYEARECAAYFAlcYCwEACgkQ8AA1q7Z/VrKW8wCeNI8DOoRcWHhWLhgiV9+CNHDa
NhIAnjVmpAhByfn5LrkD28XcHqggejXQ
=QNvs
-----END PGP SIGNATURE-----

--HeAlJdMjRJIpodamq8R4rDRAHUBar5PEb--


From nobody Thu Apr 21 02:02:30 2016
Return-Path: <rodney.cummings@ni.com>
X-Original-To: tictoc@ietfa.amsl.com
Delivered-To: tictoc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A817512E1CE; Thu, 21 Apr 2016 02:02:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level: 
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=nio365.onmicrosoft.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Af8gvZRkrDfW; Thu, 21 Apr 2016 02:02:21 -0700 (PDT)
Received: from na01-bn1-obe.outbound.protection.outlook.com (mail-bn1on0724.outbound.protection.outlook.com [IPv6:2a01:111:f400:fc10::724]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7760412E1B8; Thu, 21 Apr 2016 02:02:18 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nio365.onmicrosoft.com; s=selector1-ni-com; h=From:To:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=wYEEEg+ZbqA96dgxuzN3hPq8KozE1kh7Rqf2yfzB/FQ=; b=DBAYjnFzo605vtM82nxNt6Jg27Ly+z3SpnPUZbJ4l5krF6z0tYbzN4Is4LxiQ34nPjfkxuysPX0vPJhci6qlF5LE9wkewf9K5sa7G1wZMc2N3zCrJ36z39nDfLPGtPhBgsi1Gij0cj1wxoaDksy8f/Fm6Xchq2VIIQHsqUJQQVk=
Received: from BN1PR04MB424.namprd04.prod.outlook.com (10.141.58.153) by BN1PR04MB421.namprd04.prod.outlook.com (10.141.58.143) with Microsoft SMTP Server (TLS) id 15.1.453.26; Thu, 21 Apr 2016 09:02:01 +0000
Received: from BN1PR04MB424.namprd04.prod.outlook.com ([169.254.6.121]) by BN1PR04MB424.namprd04.prod.outlook.com ([169.254.6.121]) with mapi id 15.01.0453.032; Thu, 21 Apr 2016 09:02:01 +0000
From: Rodney Cummings <rodney.cummings@ni.com>
To: Alissa Cooper <alissa@cooperw.in>, The IESG <iesg@ietf.org>
Thread-Topic: [TICTOC] Alissa Cooper's No Objection on draft-ietf-tictoc-ptp-mib-08: (with COMMENT)
Thread-Index: AQHRml6wNoodf1IOOkSV/2jDeDYBP5+UH37A
Date: Thu, 21 Apr 2016 09:02:01 +0000
Message-ID: <BN1PR04MB424C24A38191FA75B5A5F07926E0@BN1PR04MB424.namprd04.prod.outlook.com>
References: <20160419171216.31521.25135.idtracker@ietfa.amsl.com>
In-Reply-To: <20160419171216.31521.25135.idtracker@ietfa.amsl.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
authentication-results: cooperw.in; dkim=none (message not signed) header.d=none;cooperw.in; dmarc=none action=none header.from=ni.com;
x-originating-ip: [46.218.58.213]
x-ms-office365-filtering-correlation-id: 50a54efa-4445-45c2-023c-08d369c39a38
x-microsoft-exchange-diagnostics: 1; BN1PR04MB421; 5:GLWwMXA7oY95+a6ZwAQZ3CtI3ZzkTlPmcTuhDCtRaC2NiVgcrDZiP4lHj+ZUgoEvxSHk+hSd41g8A8lWf+UnYwg2AAWb37h/tJdLxvmYyjO8ifXf1QWAN+BkqXtNsTf9+xgxSrXDmlhWSCy/jXOIJg==; 24:sc24Owsasp6BvvwAILwdtFp4mUcPoV74k66KM0KZ96K4C63Mz5J4OzLWS5+zW4PBUm8F2/yBFSUasJDGcrzQnoNMQxwYpAG3D/dE96lFfU8=
x-microsoft-antispam: UriScan:;BCL:0;PCL:0;RULEID:;SRVR:BN1PR04MB421;
x-microsoft-antispam-prvs: <BN1PR04MB4219286249068FE430AEB66926E0@BN1PR04MB421.namprd04.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:;
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(9101521026)(601004)(2401047)(8121501046)(5005006)(3002001)(10201501046)(6055026); SRVR:BN1PR04MB421; BCL:0; PCL:0; RULEID:; SRVR:BN1PR04MB421; 
x-forefront-prvs: 091949432C
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(979002)(6009001)(377454003)(54014002)(52044002)(13464003)(122556002)(97736004)(5001770100001)(189998001)(19580405001)(2906002)(19580395003)(11100500001)(86362001)(66066001)(3280700002)(6116002)(586003)(102836003)(5002640100001)(5008740100001)(1096002)(99286002)(1220700001)(106116001)(3846002)(74316001)(4326007)(3660700001)(33656002)(87936001)(54356999)(76176999)(50986999)(92566002)(9686002)(15975445007)(5003600100002)(10400500002)(2950100001)(5004730100002)(230783001)(76576001)(2900100001)(81166005)(7059030)(969003)(989001)(999001)(1009001)(1019001); DIR:OUT; SFP:1102; SCL:1; SRVR:BN1PR04MB421; H:BN1PR04MB424.namprd04.prod.outlook.com; FPR:; SPF:None; MLV:ovrnspm; PTR:InfoNoRecords; LANG:en; 
spamdiagnosticoutput: 1:23
spamdiagnosticmetadata: NSPM
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: ni.com
X-MS-Exchange-CrossTenant-originalarrivaltime: 21 Apr 2016 09:02:01.5336 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 87ba1f9a-44cd-43a6-b008-6fdb45a5204e
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BN1PR04MB421
Archived-At: <http://mailarchive.ietf.org/arch/msg/tictoc/ySF8tLlqO5FdkuSAU99NP_9iaWo>
Cc: "tictoc-chairs@ietf.org" <tictoc-chairs@ietf.org>, "kodonog@pobox.com" <kodonog@pobox.com>, "tictoc@ietf.org" <tictoc@ietf.org>, "draft-ietf-tictoc-ptp-mib@ietf.org" <draft-ietf-tictoc-ptp-mib@ietf.org>
Subject: Re: [TICTOC] Alissa Cooper's No Objection on draft-ietf-tictoc-ptp-mib-08: (with COMMENT)
X-BeenThere: tictoc@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Timing over IP Connection and Transfer of Clock BOF <tictoc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tictoc>, <mailto:tictoc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tictoc/>
List-Post: <mailto:tictoc@ietf.org>
List-Help: <mailto:tictoc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tictoc>, <mailto:tictoc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 21 Apr 2016 09:02:23 -0000

Please keep in mind that this MIB is based on IEEE Std 1588-2008, and as su=
ch, the description of data set members like clockIdentity was copied from =
that standard.

There is ongoing work in the revision of IEEE 1588 to update clockIdentity =
to align with current IEEE RA rules. Although this project could certainly =
attempt to make similar updates, that runs the risk of contradicting the fu=
ture IEEE 1588 revision.

I recommend to stay with IEEE Std 1588-2008 text.

Rodney Cummings
Co-chair of Architecture subcommittee, IEEE 1588 Working Group

> -----Original Message-----
> From: TICTOC [mailto:tictoc-bounces@ietf.org] On Behalf Of Alissa Cooper
> Sent: Tuesday, April 19, 2016 12:12 PM
> To: The IESG <iesg@ietf.org>
> Cc: tictoc-chairs@ietf.org; tictoc@ietf.org; draft-ietf-tictoc-ptp-
> mib@ietf.org; kodonog@pobox.com
> Subject: [TICTOC] Alissa Cooper's No Objection on draft-ietf-tictoc-ptp-
> mib-08: (with COMMENT)
>=20
> Alissa Cooper has entered the following ballot position for
> draft-ietf-tictoc-ptp-mib-08: No Objection
>=20
> When responding, please keep the subject line intact and reply to all
> email addresses included in the To and CC lines. (Feel free to cut this
> introductory paragraph, however.)
>=20
>=20
> Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html
> for more information about IESG DISCUSS and COMMENT positions.
>=20
>=20
> The document, along with other ballot positions, can be found here:
> https://datatracker.ietf.org/doc/draft-ietf-tictoc-ptp-mib/
>=20
>=20
>=20
> ----------------------------------------------------------------------
> COMMENT:
> ----------------------------------------------------------------------
>=20
> (1) The ClockIdentity is described as being generated based on an EUI-64
> address as described in IEEE 1588-2008 Section 7.5.2.2.2. But in IEEE
> 1588-2008, there are two different ways the clock identifier can be
> generated, the other being a non-EUI-64 address defined in 7.5.2.2.3. Why
> is that option left out of the ClockIdentity description?
>=20
> In general I was dismayed to see the re-use of EUI-64 for clock identity
> for the security and privacy drawbacks, since it's not particularly clear
> that re-using those identifiers is necessary here. But if such a fix is
> warranted this MIB is not the place to do it in any event.
>=20
> (2) Looking at
> https://trac.tools.ietf.org/area/ops/trac/wiki/mib-security I recall that
> other MIB documents we've reviewed recently have listed out the specific
> tables/objects that may be considered vulnerable or sensitive, even if
> those objects are read-only. Why doesn't this document do that? I would
> think all of the clock identity objects would belong in that bucket at a
> minimum.
>=20
>=20
> _______________________________________________
> TICTOC mailing list
> TICTOC@ietf.org
> https://www.ietf.org/mailman/listinfo/tictoc


From nobody Thu Apr 21 04:11:26 2016
Return-Path: <internet-drafts@ietf.org>
X-Original-To: tictoc@ietf.org
Delivered-To: tictoc@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id A9CAC12E5CB; Thu, 21 Apr 2016 04:11:24 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: <i-d-announce@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.19.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20160421111124.19606.46464.idtracker@ietfa.amsl.com>
Date: Thu, 21 Apr 2016 04:11:24 -0700
Archived-At: <http://mailarchive.ietf.org/arch/msg/tictoc/V2tjXJzKt-M6rxzqVzoF0Lq20Ck>
Cc: tictoc@ietf.org
Subject: [TICTOC] I-D Action: draft-ietf-tictoc-ptp-mib-09.txt
X-BeenThere: tictoc@ietf.org
X-Mailman-Version: 2.1.17
List-Id: Timing over IP Connection and Transfer of Clock BOF <tictoc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tictoc>, <mailto:tictoc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tictoc/>
List-Post: <mailto:tictoc@ietf.org>
List-Help: <mailto:tictoc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tictoc>, <mailto:tictoc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 21 Apr 2016 11:11:24 -0000

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Timing over IP Connection and Transfer of Clock of the IETF.

        Title           : Precision Time Protocol Version 2 (PTPv2) Management Information Base
        Authors         : Vinay Shankarkumar
                          Laurent Montini
                          Tim Frost
                          Greg Dowd
	Filename        : draft-ietf-tictoc-ptp-mib-09.txt
	Pages           : 80
	Date            : 2016-04-21

Abstract:
   This memo defines a portion of the Management Information Base (MIB)
   for use with network management protocols in TCP/IP-based internets.
   In particular, it defines objects for managing networks using
   Precision Time Protocol, specified in IEEE Std. 1588(TM)-2008.

   This memo specifies a MIB module in a manner that is both compliant
   to the SMIv2, and semantically identical to the peer SMIv1
   definitions.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-tictoc-ptp-mib/

There's also a htmlized version available at:
https://tools.ietf.org/html/draft-ietf-tictoc-ptp-mib-09

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-tictoc-ptp-mib-09


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/


From nobody Fri Apr 22 08:18:46 2016
Return-Path: <tim.frost@calnexsol.com>
X-Original-To: tictoc@ietfa.amsl.com
Delivered-To: tictoc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AFC0112E352; Fri, 22 Apr 2016 08:18:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level: 
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=calnexsolutions.onmicrosoft.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id srvElxIz3ham; Fri, 22 Apr 2016 08:18:38 -0700 (PDT)
Received: from emea01-db3-obe.outbound.protection.outlook.com (mail-db3on0723.outbound.protection.outlook.com [IPv6:2a01:111:f400:fe04::723]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 08A8612E39A; Fri, 22 Apr 2016 08:18:36 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=calnexsolutions.onmicrosoft.com; s=selector1-calnexsol-com; h=From:To:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=Q6fRO+So5ZJnIUSTalYVLueM8OmBF9aWhVmQb9NCGZs=; b=Cl/fOxiL6vnYShcPB0kmljHgEhzTYfDMcnfqLtQjY0JdOEwNyVc0Ndua1XZyTBC+rFyohX4oEPKt9G1Xi6+BPdXvUvyjyFVntzM/TVE8WG/9OyQO7xDkeCD0rqhlfsns+roXk6nqBMhd73DArr5VWa0TjvzgB+K02jMfU8rlIlA=
Received: from DB5PR05MB1382.eurprd05.prod.outlook.com (10.162.157.28) by DB5PR05MB1383.eurprd05.prod.outlook.com (10.162.157.29) with Microsoft SMTP Server (TLS) id 15.1.466.19; Fri, 22 Apr 2016 15:18:19 +0000
Received: from DB5PR05MB1382.eurprd05.prod.outlook.com ([10.162.157.28]) by DB5PR05MB1382.eurprd05.prod.outlook.com ([10.162.157.28]) with mapi id 15.01.0466.023; Fri, 22 Apr 2016 15:18:19 +0000
From: Tim Frost <tim.frost@calnexsol.com>
To: Rodney Cummings <rodney.cummings@ni.com>, Alissa Cooper <alissa@cooperw.in>, The IESG <iesg@ietf.org>
Thread-Topic: [TICTOC] Alissa Cooper's No Objection on draft-ietf-tictoc-ptp-mib-08: (with COMMENT)
Thread-Index: AQHRml6h8h9nbSF2w0u9dZpEjBABxp+UJDGAgAH53AA=
Date: Fri, 22 Apr 2016 15:18:18 +0000
Message-ID: <DB5PR05MB1382678AF64F17992CC5F6D7FA6F0@DB5PR05MB1382.eurprd05.prod.outlook.com>
References: <20160419171216.31521.25135.idtracker@ietfa.amsl.com> <BN1PR04MB424C24A38191FA75B5A5F07926E0@BN1PR04MB424.namprd04.prod.outlook.com>
In-Reply-To: <BN1PR04MB424C24A38191FA75B5A5F07926E0@BN1PR04MB424.namprd04.prod.outlook.com>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
authentication-results: ni.com; dkim=none (message not signed) header.d=none;ni.com; dmarc=none action=none header.from=calnexsol.com;
x-originating-ip: [88.110.253.196]
x-ms-office365-filtering-correlation-id: c7af8ac2-028d-4e89-3569-08d36ac155d7
x-microsoft-exchange-diagnostics: 1; DB5PR05MB1383; 5:CRdZZuXREsyBAv5Vgk1pFzCmb8KE4ZuUfeJ35oh+OO2/jafgm4YzRQ6WHuh+4I/u2a9sLrPXcXPAZ+USUixYcz9e4f9CnnbxHaMOcZI8YI0B73mLVahkMvkrOQAhzJfCZNq5gRC+FWYtAxJmprcKj5kGLgPQ8vhIGIzsH1p1L0GmmOToVCR2FwfdvMR+9KeH; 24:uwtcQesGIPEsXbEWVoC+jx3jqARXG5yGTwqoLAezuHKgtNsiZj+rw7jzZPhEBXbbyi26y0xgFc5+y0hCcdvlmA7xB0uWOfAvFwmkGM5yZyQ=; 7:SdPWAOy9C+bzBxvhMmWCEmaVG6iEmsp3LWLK9pYHqkCceueQSBU6ht2wmXiXvySYdUfjscObu0Ovu5RQG1qE39kJRKfrLtKsKAfYpRQgffqKhG7t6scnvJNfLmDkYV6XFEkpUyTy9J/yyKeVIPc8jYlmGe701GZvnhAry09eKVtWOflIQyEH5MdLvNOcbI00AlDR9dSyeL29F2A2X4TP+8lyI5gaG0jdzItX3DuPsoo=
x-microsoft-antispam: UriScan:;BCL:0;PCL:0;RULEID:;SRVR:DB5PR05MB1383;
x-microsoft-antispam-prvs: <DB5PR05MB13838880E41CF5E2F8196C21FA6F0@DB5PR05MB1383.eurprd05.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:;
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(9101521026)(6040130)(601004)(2401047)(5005006)(8121501046)(3002001)(10201501046)(6041072)(6043046); SRVR:DB5PR05MB1383; BCL:0; PCL:0; RULEID:; SRVR:DB5PR05MB1383; 
x-forefront-prvs: 0920602B08
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(6009001)(377454003)(13464003)(52044002)(6116002)(102836003)(19580395003)(106116001)(5002640100001)(3846002)(122556002)(19580405001)(15974865002)(3660700001)(3280700002)(33656002)(1096002)(1220700001)(5003600100002)(92566002)(86362001)(87936001)(74316001)(66066001)(2906002)(5008740100001)(4326007)(76176999)(54356999)(81166005)(15975445007)(50986999)(586003)(230783001)(77096005)(189998001)(5001770100001)(2900100001)(2950100001)(10400500002)(5004730100002)(9686002)(11100500001)(7059030); DIR:OUT; SFP:1102; SCL:1; SRVR:DB5PR05MB1383; H:DB5PR05MB1382.eurprd05.prod.outlook.com; FPR:; SPF:None; MLV:sfv; LANG:en; 
spamdiagnosticoutput: 1:23
spamdiagnosticmetadata: NSPM
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: calnexsol.com
X-MS-Exchange-CrossTenant-originalarrivaltime: 22 Apr 2016 15:18:18.9834 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: fbb4e2fb-f802-4d55-beca-b7149551e928
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DB5PR05MB1383
Archived-At: <http://mailarchive.ietf.org/arch/msg/tictoc/cKIXiG95TnMdUAnjqvyW4xrarh0>
Cc: "tictoc-chairs@ietf.org" <tictoc-chairs@ietf.org>, "kodonog@pobox.com" <kodonog@pobox.com>, "tictoc@ietf.org" <tictoc@ietf.org>, "draft-ietf-tictoc-ptp-mib@ietf.org" <draft-ietf-tictoc-ptp-mib@ietf.org>
Subject: Re: [TICTOC] Alissa Cooper's No Objection on draft-ietf-tictoc-ptp-mib-08: (with COMMENT)
X-BeenThere: tictoc@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Timing over IP Connection and Transfer of Clock BOF <tictoc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tictoc>, <mailto:tictoc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tictoc/>
List-Post: <mailto:tictoc@ietf.org>
List-Help: <mailto:tictoc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tictoc>, <mailto:tictoc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 22 Apr 2016 15:18:41 -0000

I agree with Rodney, since the MIB is based on IEEE1588-2008, we should sti=
ck with the methods adopted there, and that today means EUI-64.

As for the non-EUI-64 methods in 7.5.2.2.3, I don't remember consciously re=
jecting these, but they are for use with non-Ethernet networks, e.g. Device=
Net, ControlNet, PROFINet etc.
I'm not really familiar with the architectures of these networks.  Would su=
ch devices have IP connectivity and use SNMP to access management informati=
on? If so we should probably include these, if not, then I'm comfortable wi=
th restricting it to devices with an Ethernet-style MAC address.

Best regards,
Tim


Tim Frost=A0=A0 | =A0=A0Calnex Solutions Ltd.   |=A0=A0 +44 (0) 7825 706 95=
2  =A0|=A0=A0 www.calnexsol.com

-----Original Message-----
From: Rodney Cummings [mailto:rodney.cummings@ni.com]=20
Sent: 21 April 2016 10:02
To: Alissa Cooper <alissa@cooperw.in>; The IESG <iesg@ietf.org>
Cc: tictoc-chairs@ietf.org; tictoc@ietf.org; draft-ietf-tictoc-ptp-mib@ietf=
.org; kodonog@pobox.com
Subject: RE: [TICTOC] Alissa Cooper's No Objection on draft-ietf-tictoc-ptp=
-mib-08: (with COMMENT)

Please keep in mind that this MIB is based on IEEE Std 1588-2008, and as su=
ch, the description of data set members like clockIdentity was copied from =
that standard.

There is ongoing work in the revision of IEEE 1588 to update clockIdentity =
to align with current IEEE RA rules. Although this project could certainly =
attempt to make similar updates, that runs the risk of contradicting the fu=
ture IEEE 1588 revision.

I recommend to stay with IEEE Std 1588-2008 text.

Rodney Cummings
Co-chair of Architecture subcommittee, IEEE 1588 Working Group

> -----Original Message-----
> From: TICTOC [mailto:tictoc-bounces@ietf.org] On Behalf Of Alissa=20
> Cooper
> Sent: Tuesday, April 19, 2016 12:12 PM
> To: The IESG <iesg@ietf.org>
> Cc: tictoc-chairs@ietf.org; tictoc@ietf.org; draft-ietf-tictoc-ptp-=20
> mib@ietf.org; kodonog@pobox.com
> Subject: [TICTOC] Alissa Cooper's No Objection on=20
> draft-ietf-tictoc-ptp-
> mib-08: (with COMMENT)
>=20
> Alissa Cooper has entered the following ballot position for
> draft-ietf-tictoc-ptp-mib-08: No Objection
>=20
> When responding, please keep the subject line intact and reply to all=20
> email addresses included in the To and CC lines. (Feel free to cut=20
> this introductory paragraph, however.)
>=20
>=20
> Please refer to=20
> https://www.ietf.org/iesg/statement/discuss-criteria.html
> for more information about IESG DISCUSS and COMMENT positions.
>=20
>=20
> The document, along with other ballot positions, can be found here:
> https://datatracker.ietf.org/doc/draft-ietf-tictoc-ptp-mib/
>=20
>=20
>=20
> ----------------------------------------------------------------------
> COMMENT:
> ----------------------------------------------------------------------
>=20
> (1) The ClockIdentity is described as being generated based on an=20
> EUI-64 address as described in IEEE 1588-2008 Section 7.5.2.2.2. But=20
> in IEEE 1588-2008, there are two different ways the clock identifier=20
> can be generated, the other being a non-EUI-64 address defined in=20
> 7.5.2.2.3. Why is that option left out of the ClockIdentity description?
>=20
> In general I was dismayed to see the re-use of EUI-64 for clock=20
> identity for the security and privacy drawbacks, since it's not=20
> particularly clear that re-using those identifiers is necessary here.=20
> But if such a fix is warranted this MIB is not the place to do it in any =
event.
>=20
> (2) Looking at
> https://trac.tools.ietf.org/area/ops/trac/wiki/mib-security I recall=20
> that other MIB documents we've reviewed recently have listed out the=20
> specific tables/objects that may be considered vulnerable or=20
> sensitive, even if those objects are read-only. Why doesn't this=20
> document do that? I would think all of the clock identity objects=20
> would belong in that bucket at a minimum.
>=20
>=20
> _______________________________________________
> TICTOC mailing list
> TICTOC@ietf.org
> https://www.ietf.org/mailman/listinfo/tictoc


From nobody Thu Apr 28 13:53:46 2016
Return-Path: <gregory.mirsky@ericsson.com>
X-Original-To: tictoc@ietfa.amsl.com
Delivered-To: tictoc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1110312D584; Thu, 28 Apr 2016 13:53:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.202
X-Spam-Level: 
X-Spam-Status: No, score=-4.202 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XTASIWNtQNcn; Thu, 28 Apr 2016 13:53:38 -0700 (PDT)
Received: from usplmg21.ericsson.net (usplmg21.ericsson.net [198.24.6.65]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D03C812D573; Thu, 28 Apr 2016 13:53:37 -0700 (PDT)
X-AuditID: c6180641-f796f6d000000e1e-a4-57227824be8e
Received: from EUSAAHC006.ericsson.se (Unknown_Domain [147.117.188.90]) by usplmg21.ericsson.net (Symantec Mail Security) with SMTP id 3A.5C.03614.42872275; Thu, 28 Apr 2016 22:52:52 +0200 (CEST)
Received: from EUSAAMB103.ericsson.se ([147.117.188.120]) by EUSAAHC006.ericsson.se ([147.117.188.90]) with mapi id 14.03.0248.002; Thu, 28 Apr 2016 16:53:36 -0400
From: Gregory Mirsky <gregory.mirsky@ericsson.com>
To: Loa Andersson <loa@pi.nu>, "lberger@labn.net" <lberger@labn.net>, "mpls@ietf.org" <mpls@ietf.org>, TEAS WG <teas@ietf.org>, "tictoc@ietf.org" <tictoc@ietf.org>, "Acee Lindem (acee) (acee@cisco.com)" <acee@cisco.com>
Thread-Topic: [mpls] I-D Action: draft-ietf-mpls-residence-time-08.txt
Thread-Index: AQHRoY8q390nPF0LtUuImRWKzDmMap+f3AJw
Date: Thu, 28 Apr 2016 20:53:35 +0000
Message-ID: <7347100B5761DC41A166AC17F22DF11221A626CE@eusaamb103.ericsson.se>
References: <20160428204715.5490.96999.idtracker@ietfa.amsl.com>
In-Reply-To: <20160428204715.5490.96999.idtracker@ietfa.amsl.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [147.117.188.10]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFtrOIsWRmVeSWpSXmKPExsUyuXRPlK5KhVK4weML+haT385jtpi69QOz xZy7zhYdzW9ZLP7NncNscWvpSlaLUw8SLVp/7GCx+Nvcw+7A6THl90ZWj03/jjN67Jx1l91j yZKfTB7Xm66ye3zY1MzmMWt6G1sAexSXTUpqTmZZapG+XQJXxvZZsQVvBCse/7zP2MC4j7eL kZNDQsBEYsuOvcwQtpjEhXvr2boYuTiEBI4ySlzoOs4E4SxnlOj6+I8NpIpNwEjixcYedpCE iMB9RonJ7S8ZQRxmgX1MEmsW3GQHqRIWcJWY1r0SrENEwE1ib9tcKNtI4u6F7SwgNouAqsTR p2dZQWxeAV+J1nVLmUBsIQEHif5fE8BsTgFHiavr94LNZAS67/upNWBxZgFxiVtP5jNB3C0g sWTPeagfRCVePv7HCmErSUxaeo4Vol5HYsHuT2wQtrbEsoWvmSH2CkqcnPmEZQKj2CwkY2ch aZmFpGUWkpYFjCyrGDlKiwtyctONDDcxAqPzmASb4w7Gvb2ehxgFOBiVeHgX5CmGC7EmlhVX 5h5ilOBgVhLhDSlWChfiTUmsrEotyo8vKs1JLT7EKM3BoiTOq/8SqFogPbEkNTs1tSC1CCbL xMEp1cA4Y2nf9MPsLjOXt7DWmui2ObdL5km+y20Q+rP0ndR5Y+mD0gE+AsvYmjct3sqoJaqj 21OwZafa4W/7o5jke5d9adzzUtq34uXEzFVi/UJvG2buWyaufkvurIm1wDIzzqKfTgwh82Un XXP12F/IZ2zQEn/4oq/fDPWD6w62hXnciGdPv3HSyVaJpTgj0VCLuag4EQB1z8gsygIAAA==
Archived-At: <http://mailarchive.ietf.org/arch/msg/tictoc/YIEpy2U38tFhaGpvm3Tep09hmHg>
Cc: "Stewart Bryant \(stewart.bryant@gmail.com\)" <stewart.bryant@gmail.com>, Eric Gray <eric.gray@ericsson.com>
Subject: [TICTOC] FW: [mpls] I-D Action: draft-ietf-mpls-residence-time-08.txt
X-BeenThere: tictoc@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Timing over IP Connection and Transfer of Clock BOF <tictoc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tictoc>, <mailto:tictoc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tictoc/>
List-Post: <mailto:tictoc@ietf.org>
List-Help: <mailto:tictoc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tictoc>, <mailto:tictoc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 28 Apr 2016 20:53:40 -0000

Dear All,
updates in the new version clarify use of the I flag in the RTM_SET TLV.
Authors believe that all comments we've received from Acee and Lou now have=
 been addressed.

	Regards,
		Greg

-----Original Message-----
From: mpls [mailto:mpls-bounces@ietf.org] On Behalf Of internet-drafts@ietf=
.org
Sent: Thursday, April 28, 2016 1:47 PM
To: i-d-announce@ietf.org
Cc: mpls@ietf.org
Subject: [mpls] I-D Action: draft-ietf-mpls-residence-time-08.txt


A New Internet-Draft is available from the on-line Internet-Drafts director=
ies.
This draft is a work item of the Multiprotocol Label Switching of the IETF.

        Title           : Residence Time Measurement in MPLS network
        Authors         : Greg Mirsky
                          Stefano Ruffini
                          Eric Gray
                          John Drake
                          Stewart Bryant
                          Alexander Vainshtein
	Filename        : draft-ietf-mpls-residence-time-08.txt
	Pages           : 27
	Date            : 2016-04-28

Abstract:
   This document specifies G-ACh based Residence Time Measurement and
   how it can be used by time synchronization protocols being
   transported over MPLS domain.

   Residence time is the variable part of propagation delay of timing
   and synchronization messages and knowing what this delay is for each
   message allows for a more accurate determination of the delay to be
   taken into account in applying the value included in a PTP event
   message.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-mpls-residence-time/

There's also a htmlized version available at:
https://tools.ietf.org/html/draft-ietf-mpls-residence-time-08

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-mpls-residence-time-08


Please note that it may take a couple of minutes from the time of submissio=
n until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

_______________________________________________
mpls mailing list
mpls@ietf.org
https://www.ietf.org/mailman/listinfo/mpls


From nobody Thu Apr 28 13:58:53 2016
Return-Path: <lberger@labn.net>
X-Original-To: tictoc@ietfa.amsl.com
Delivered-To: tictoc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 49B5B12B00F for <tictoc@ietfa.amsl.com>; Thu, 28 Apr 2016 13:58:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.001
X-Spam-Level: 
X-Spam-Status: No, score=-2.001 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (768-bit key) header.d=labn.net
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id U565CCvO6DFq for <tictoc@ietfa.amsl.com>; Thu, 28 Apr 2016 13:58:37 -0700 (PDT)
Received: from gproxy7-pub.mail.unifiedlayer.com (gproxy7-pub.mail.unifiedlayer.com [70.40.196.235]) by ietfa.amsl.com (Postfix) with SMTP id 18CE112D1D1 for <tictoc@ietf.org>; Thu, 28 Apr 2016 13:58:37 -0700 (PDT)
Received: (qmail 12816 invoked by uid 0); 28 Apr 2016 20:58:33 -0000
Received: from unknown (HELO cmgw4) (10.0.90.85) by gproxy7.mail.unifiedlayer.com with SMTP; 28 Apr 2016 20:58:33 -0000
Received: from box313.bluehost.com ([69.89.31.113]) by cmgw4 with  id nwyP1s00w2SSUrH01wySWl; Thu, 28 Apr 2016 14:58:33 -0600
X-Authority-Analysis: v=2.1 cv=aJ5j99Nm c=1 sm=1 tr=0 a=h1BC+oY+fLhyFmnTBx92Jg==:117 a=N659UExz7-8A:10 a=-NfooI8aBGcA:10 a=uEJ9t1CZtbIA:10 a=kziv93cY1bsA:10 a=48vgC7mUAAAA:8 a=pe07b3NTbGBt4aplo2YA:9 a=Sfpe1sfZ2QWo5lbg:21 a=hDdnFZzf8-CIZ_vu:21 a=pILNOxqGKmIA:10
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=labn.net; s=default; h=Content-Transfer-Encoding:Content-Type:In-Reply-To:MIME-Version :Date:Message-ID:From:Cc:References:To:Subject; bh=l18ld1uSMTpKLkCALn1iAN7V0uv25dsTD7p695NGAGs=; b=I3i8ZgBosflmXA4jAVd/zJodGo LOjXj2AGV+G5Hw1U5IyaHaYQ975za0bNrpQlzF8lejhGGrsoyyjtjWJGnoDERxyiaktkzlaXCyCV3 e06QmHYMfJwVC1vyYUvTGAd3F;
Received: from box313.bluehost.com ([69.89.31.113]:53441 helo=[127.0.0.1]) by box313.bluehost.com with esmtpa (Exim 4.86_2) (envelope-from <lberger@labn.net>) id 1avt0x-0007If-Mj; Thu, 28 Apr 2016 14:58:23 -0600
To: Gregory Mirsky <gregory.mirsky@ericsson.com>, Loa Andersson <loa@pi.nu>, "mpls@ietf.org" <mpls@ietf.org>, TEAS WG <teas@ietf.org>, "tictoc@ietf.org" <tictoc@ietf.org>, "Acee Lindem (acee) (acee@cisco.com)" <acee@cisco.com>
References: <20160428204715.5490.96999.idtracker@ietfa.amsl.com> <7347100B5761DC41A166AC17F22DF11221A626CE@eusaamb103.ericsson.se>
From: Lou Berger <lberger@labn.net>
Message-ID: <5722795D.1030008@labn.net>
Date: Thu, 28 Apr 2016 16:58:05 -0400
User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.7.2
MIME-Version: 1.0
In-Reply-To: <7347100B5761DC41A166AC17F22DF11221A626CE@eusaamb103.ericsson.se>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 7bit
X-Identified-User: {1038:box313.bluehost.com:labnmobi:labn.net} {sentby:smtp auth 69.89.31.113 authed with lberger@labn.net}
Archived-At: <http://mailarchive.ietf.org/arch/msg/tictoc/LcMpZf8hmgFS3jEzlntps8zY49Y>
Cc: Eric Gray <eric.gray@ericsson.com>, "Stewart Bryant \(stewart.bryant@gmail.com\)" <stewart.bryant@gmail.com>
Subject: Re: [TICTOC] [Teas] FW: [mpls] I-D Action: draft-ietf-mpls-residence-time-08.txt
X-BeenThere: tictoc@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Timing over IP Connection and Transfer of Clock BOF <tictoc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tictoc>, <mailto:tictoc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tictoc/>
List-Post: <mailto:tictoc@ietf.org>
List-Help: <mailto:tictoc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tictoc>, <mailto:tictoc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 28 Apr 2016 20:58:50 -0000

I agree. 

There is one minor typo: s/could been/could be/

This can be picked up in the next rev, i.e., no need to spin a rev now
to fix this minor typo.

Thanks for all the good work.
Lou

On 4/28/2016 4:53 PM, Gregory Mirsky wrote:
> Dear All,
> updates in the new version clarify use of the I flag in the RTM_SET TLV.
> Authors believe that all comments we've received from Acee and Lou now have been addressed.
>
> 	Regards,
> 		Greg
>
> -----Original Message-----
> From: mpls [mailto:mpls-bounces@ietf.org] On Behalf Of internet-drafts@ietf.org
> Sent: Thursday, April 28, 2016 1:47 PM
> To: i-d-announce@ietf.org
> Cc: mpls@ietf.org
> Subject: [mpls] I-D Action: draft-ietf-mpls-residence-time-08.txt
>
>
> A New Internet-Draft is available from the on-line Internet-Drafts directories.
> This draft is a work item of the Multiprotocol Label Switching of the IETF.
>
>         Title           : Residence Time Measurement in MPLS network
>         Authors         : Greg Mirsky
>                           Stefano Ruffini
>                           Eric Gray
>                           John Drake
>                           Stewart Bryant
>                           Alexander Vainshtein
> 	Filename        : draft-ietf-mpls-residence-time-08.txt
> 	Pages           : 27
> 	Date            : 2016-04-28
>
> Abstract:
>    This document specifies G-ACh based Residence Time Measurement and
>    how it can be used by time synchronization protocols being
>    transported over MPLS domain.
>
>    Residence time is the variable part of propagation delay of timing
>    and synchronization messages and knowing what this delay is for each
>    message allows for a more accurate determination of the delay to be
>    taken into account in applying the value included in a PTP event
>    message.
>
>
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-ietf-mpls-residence-time/
>
> There's also a htmlized version available at:
> https://tools.ietf.org/html/draft-ietf-mpls-residence-time-08
>
> A diff from the previous version is available at:
> https://www.ietf.org/rfcdiff?url2=draft-ietf-mpls-residence-time-08
>
>
> Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org.
>
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
>
> _______________________________________________
> mpls mailing list
> mpls@ietf.org
> https://www.ietf.org/mailman/listinfo/mpls
>
> _______________________________________________
> Teas mailing list
> Teas@ietf.org
> https://www.ietf.org/mailman/listinfo/teas
>



From nobody Thu Apr 28 17:55:42 2016
Return-Path: <loa@pi.nu>
X-Original-To: tictoc@ietfa.amsl.com
Delivered-To: tictoc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5BF0C12B006; Thu, 28 Apr 2016 17:55:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.896
X-Spam-Level: 
X-Spam-Status: No, score=-2.896 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.996] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UrOmdNuAX4BV; Thu, 28 Apr 2016 17:55:34 -0700 (PDT)
Received: from pipi.pi.nu (pipi.pi.nu [83.168.239.141]) (using TLSv1.1 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2D0C312D509; Thu, 28 Apr 2016 17:55:33 -0700 (PDT)
Received: from [192.168.1.6] (unknown [122.53.41.246]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: loa@pi.nu) by pipi.pi.nu (Postfix) with ESMTPSA id 5F97F1802AB9; Fri, 29 Apr 2016 02:55:27 +0200 (CEST)
To: Lou Berger <lberger@labn.net>, Gregory Mirsky <gregory.mirsky@ericsson.com>, "mpls@ietf.org" <mpls@ietf.org>, TEAS WG <teas@ietf.org>, "tictoc@ietf.org" <tictoc@ietf.org>, "Acee Lindem (acee) (acee@cisco.com)" <acee@cisco.com>
References: <20160428204715.5490.96999.idtracker@ietfa.amsl.com> <7347100B5761DC41A166AC17F22DF11221A626CE@eusaamb103.ericsson.se> <5722795D.1030008@labn.net>
From: Loa Andersson <loa@pi.nu>
Message-ID: <5722B0FC.7020609@pi.nu>
Date: Fri, 29 Apr 2016 08:55:24 +0800
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.7.2
MIME-Version: 1.0
In-Reply-To: <5722795D.1030008@labn.net>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/tictoc/fB5QNQyPGSUP_a5_ovDuXxyQrXg>
Cc: "Stewart Bryant \(stewart.bryant@gmail.com\)" <stewart.bryant@gmail.com>, Eric Gray <eric.gray@ericsson.com>
Subject: Re: [TICTOC] [Teas] FW: [mpls] I-D Action: draft-ietf-mpls-residence-time-08.txt
X-BeenThere: tictoc@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Timing over IP Connection and Transfer of Clock BOF <tictoc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tictoc>, <mailto:tictoc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tictoc/>
List-Post: <mailto:tictoc@ietf.org>
List-Help: <mailto:tictoc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tictoc>, <mailto:tictoc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 29 Apr 2016 00:55:38 -0000

Authors, reviewers, et.al.,

Thanks for all the work in getting this draft ready for wglc, I will
start the procedures later today, beginning with an IPR poll and follow
up with the wglc as soon as tht has concluded.

/Loa

On 2016-04-29 04:58, Lou Berger wrote:
> I agree.
>
> There is one minor typo: s/could been/could be/
>
> This can be picked up in the next rev, i.e., no need to spin a rev now
> to fix this minor typo.
>
> Thanks for all the good work.
> Lou
>
> On 4/28/2016 4:53 PM, Gregory Mirsky wrote:
>> Dear All,
>> updates in the new version clarify use of the I flag in the RTM_SET TLV.
>> Authors believe that all comments we've received from Acee and Lou now have been addressed.
>>
>> 	Regards,
>> 		Greg
>>
>> -----Original Message-----
>> From: mpls [mailto:mpls-bounces@ietf.org] On Behalf Of internet-drafts@ietf.org
>> Sent: Thursday, April 28, 2016 1:47 PM
>> To: i-d-announce@ietf.org
>> Cc: mpls@ietf.org
>> Subject: [mpls] I-D Action: draft-ietf-mpls-residence-time-08.txt
>>
>>
>> A New Internet-Draft is available from the on-line Internet-Drafts directories.
>> This draft is a work item of the Multiprotocol Label Switching of the IETF.
>>
>>          Title           : Residence Time Measurement in MPLS network
>>          Authors         : Greg Mirsky
>>                            Stefano Ruffini
>>                            Eric Gray
>>                            John Drake
>>                            Stewart Bryant
>>                            Alexander Vainshtein
>> 	Filename        : draft-ietf-mpls-residence-time-08.txt
>> 	Pages           : 27
>> 	Date            : 2016-04-28
>>
>> Abstract:
>>     This document specifies G-ACh based Residence Time Measurement and
>>     how it can be used by time synchronization protocols being
>>     transported over MPLS domain.
>>
>>     Residence time is the variable part of propagation delay of timing
>>     and synchronization messages and knowing what this delay is for each
>>     message allows for a more accurate determination of the delay to be
>>     taken into account in applying the value included in a PTP event
>>     message.
>>
>>
>> The IETF datatracker status page for this draft is:
>> https://datatracker.ietf.org/doc/draft-ietf-mpls-residence-time/
>>
>> There's also a htmlized version available at:
>> https://tools.ietf.org/html/draft-ietf-mpls-residence-time-08
>>
>> A diff from the previous version is available at:
>> https://www.ietf.org/rfcdiff?url2=draft-ietf-mpls-residence-time-08
>>
>>
>> Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org.
>>
>> Internet-Drafts are also available by anonymous FTP at:
>> ftp://ftp.ietf.org/internet-drafts/
>>
>> _______________________________________________
>> mpls mailing list
>> mpls@ietf.org
>> https://www.ietf.org/mailman/listinfo/mpls
>>
>> _______________________________________________
>> Teas mailing list
>> Teas@ietf.org
>> https://www.ietf.org/mailman/listinfo/teas
>>
>
>
> _______________________________________________
> Teas mailing list
> Teas@ietf.org
> https://www.ietf.org/mailman/listinfo/teas
>


From nobody Fri Apr 29 13:30:18 2016
Return-Path: <denis.reilly@spectracom.orolia.com>
X-Original-To: tictoc@ietfa.amsl.com
Delivered-To: tictoc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5070212D10E for <tictoc@ietfa.amsl.com>; Fri, 29 Apr 2016 13:30:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level: 
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=oroliagroup.onmicrosoft.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qOcVbTKm6QL5 for <tictoc@ietfa.amsl.com>; Fri, 29 Apr 2016 13:30:13 -0700 (PDT)
Received: from emea01-db3-obe.outbound.protection.outlook.com (mail-db3on0605.outbound.protection.outlook.com [IPv6:2a01:111:f400:fe04::605]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3B5A012D096 for <tictoc@ietf.org>; Fri, 29 Apr 2016 13:30:12 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=OROLIAGROUP.onmicrosoft.com; s=selector1-spectracom-orolia-com; h=From:To:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=hkz4aUwioNLqHWAJO7uFMiUAv9xfDHLzROdfnwaf9so=; b=bGWMRmTPbA0n5z4RsPjDcmh7rqqfh2eccseCIRPObjh+qPM8W/NR+kyf/fX6gYAXoke5l6uuIJcYiAbuPrlR/kjoW3xk03/BlbbLZ70Xikdr4TnW9UyAug4Rcixu4H5MsP3kOHmZ+EZLIcr+szDJuR2oo6VBK8WNMYBAu3vzzdI=
Received: from AM3PR06MB1202.eurprd06.prod.outlook.com (2a01:111:e400:58a0::28) by AM3PR06MB1204.eurprd06.prod.outlook.com (2a01:111:e400:58a0::30) with Microsoft SMTP Server (TLS) id 15.1.466.19; Fri, 29 Apr 2016 20:29:54 +0000
Received: from AM3PR06MB1202.eurprd06.prod.outlook.com ([fe80::18f6:dc6:e8d5:2bc1]) by AM3PR06MB1202.eurprd06.prod.outlook.com ([fe80::18f6:dc6:e8d5:2bc1%14]) with mapi id 15.01.0466.028; Fri, 29 Apr 2016 20:29:54 +0000
From: Denis Reilly <denis.reilly@spectracom.orolia.com>
To: Karen O'Donoghue <odonoghue@isoc.org>, "tictoc@ietf.org" <tictoc@ietf.org>
Thread-Topic: WGLC on draft-ietf-tictoc-ptp-enterprise-profile-06
Thread-Index: AQHRmxVIxH0uTbr/rUq9StTgt++Pg5+hdQyg
Date: Fri, 29 Apr 2016 20:29:54 +0000
Message-ID: <AM3PR06MB1202F9B04F7C5F8905CB5EC3D2660@AM3PR06MB1202.eurprd06.prod.outlook.com>
References: <15556A59-F26E-41DE-BF9E-BF6344F534A6@isoc.org>
In-Reply-To: <15556A59-F26E-41DE-BF9E-BF6344F534A6@isoc.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
authentication-results: isoc.org; dkim=none (message not signed) header.d=none;isoc.org; dmarc=none action=none header.from=spectracom.orolia.com;
x-originating-ip: [66.193.84.98]
x-ms-office365-filtering-correlation-id: 60e12e63-b0e2-4ce6-7ef6-08d3706d0656
x-microsoft-exchange-diagnostics: 1; AM3PR06MB1204; 5:YsK5A1Fk6XOizcFnxjHANOtvuY4gdVN63qkYnBT5kR1pSZiDI4KvK5vvlsga/bFr9WWzarhukmm4+ezc+r/AihzHtoL3XO4fty2do8wfarxwqcVNvCBr9tHIxO76zp1T66VA9E9TPoai/ktsPr+K0GRqMeEne68vYm5uySAJcsb9VaaHlZb8Ygn5CNh2mFME; 24:DLZQngoUsNP//JIPzsTMMwu55OH+miejw9JdvQWxAo7DN+y+PuHQpEVUIc208Db0T60DsynRJBpqCl3LOd/YInMINV4BXsjqrBL+NiyrSDo=; 7:/tr+ekAT6Ko2jxWm1/g0ZBoZmRzEuqbSApmmRRfRsSV+ivsPZ33ZO62YiZHPCsPCDQMZ78M3PPzkPn5Yh7IQXxwudGveGNyEOOGiwiGIQ08dbbYAn2+EGByHm38Vhdkz7qTdnixoGKZ4E17Vc1GGmPiwnU4j6utBzPsRLJW56f25RwRCwfcPv1jefgAfYArSNJmv8Tzo4HOTz7nnXS0i/yPU7g7xetqhu8RAZrpqNUg=
x-microsoft-antispam: UriScan:;BCL:0;PCL:0;RULEID:;SRVR:AM3PR06MB1204;
x-microsoft-antispam-prvs: <AM3PR06MB120491AEC03C6CD2FCB4A35DD2660@AM3PR06MB1204.eurprd06.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:;
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(9101521072)(601004)(2401047)(8121501046)(5005006)(3002001)(10201501046); SRVR:AM3PR06MB1204; BCL:0; PCL:0; RULEID:; SRVR:AM3PR06MB1204; 
x-forefront-prvs: 0927AA37C7
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(6009001)(377454003)(13464003)(19580395003)(19580405001)(2906002)(3660700001)(5008740100001)(189998001)(74316001)(2501003)(106116001)(87936001)(66066001)(230783001)(86362001)(5003600100002)(3280700002)(33656002)(76576001)(102836003)(3846002)(6116002)(2950100001)(11100500001)(92566002)(81166005)(2900100001)(15975445007)(1220700001)(1096002)(5001770100001)(1720100001)(9686002)(5250100002)(50986999)(5002640100001)(76176999)(54356999)(586003)(7059030); DIR:OUT; SFP:1101; SCL:1; SRVR:AM3PR06MB1204; H:AM3PR06MB1202.eurprd06.prod.outlook.com; FPR:; SPF:None; MLV:sfv; LANG:en; 
spamdiagnosticoutput: 1:23
spamdiagnosticmetadata: NSPM
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: spectracom.orolia.com
X-MS-Exchange-CrossTenant-originalarrivaltime: 29 Apr 2016 20:29:54.8199 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: a263030c-9c1b-421f-9471-1dec0b29c664
X-MS-Exchange-Transport-CrossTenantHeadersStamped: AM3PR06MB1204
Archived-At: <http://mailarchive.ietf.org/arch/msg/tictoc/lzIDG4z-DCgSewSM_cQHtdg3if8>
Cc: "ntpwg@lists.ntp.org" <ntpwg@lists.ntp.org>
Subject: Re: [TICTOC] WGLC on draft-ietf-tictoc-ptp-enterprise-profile-06
X-BeenThere: tictoc@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Timing over IP Connection and Transfer of Clock BOF <tictoc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tictoc>, <mailto:tictoc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tictoc/>
List-Post: <mailto:tictoc@ietf.org>
List-Help: <mailto:tictoc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tictoc>, <mailto:tictoc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 29 Apr 2016 20:30:16 -0000

All,

I like this version of the document (draft-ietf-tictoc-ptp-enterprise-profi=
le-06) and would support it moving on to the next phase.

Best Regards,

--
Denis Reilly  |  Lead Engineer  |  denis.reilly@spectracom.orolia.com (585)=
321-5837

This e-mail and any files transmitted with it are confidential and are inte=
nded solely for the use of the individual or entity to which they are addre=
ssed. If you received this e-mail in error please note that any use, dissem=
ination, forwarding, printing, or copying of this e-mail is strictly prohib=
ited.


-----Original Message-----
From: ntpwg [mailto:ntpwg-bounces+denis.reilly=3Dspectracom.orolia.com@list=
s.ntp.org] On Behalf Of Karen O'Donoghue
Sent: Wednesday, April 20, 2016 11:00 AM
To: tictoc@ietf.org
Cc: ntpwg@lists.ntp.org
Subject: [ntpwg] WGLC on draft-ietf-tictoc-ptp-enterprise-profile-06

Folks,=20

This message begins a 2 week WGLC on the following document:=20

Enterprise Profile for the Precision Time Protocol With Mixed Multicast and=
 Unicast Messages
https://tools.ietf.org/html/draft-ietf-tictoc-ptp-enterprise-profile-06

Please review the referenced document and send any comments to the mailing =
list including your assessment of whether this document is mature enough to=
 proceed to the IESG. Please note that these messages of support for progre=
ssion to the mailing list will be used to determine WG consensus to proceed=
.=20

Please send all comments in by Wednesday 4 May 2016.=20

Thank you!
Karen


_______________________________________________
ntpwg mailing list
ntpwg@lists.ntp.org
http://lists.ntp.org/listinfo/ntpwg

