
From odonoghue@isoc.org  Mon Nov  5 15:44:36 2012
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 EEF1311E80B8 for <tictoc@ietfa.amsl.com>; Mon,  5 Nov 2012 15:44:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.264
X-Spam-Level: 
X-Spam-Status: No, score=-103.264 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, IP_NOT_FRIENDLY=0.334, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aLiIY-09uPPH for <tictoc@ietfa.amsl.com>; Mon,  5 Nov 2012 15:44:36 -0800 (PST)
Received: from smtp185.dfw.emailsrvr.com (smtp185.dfw.emailsrvr.com [67.192.241.185]) by ietfa.amsl.com (Postfix) with ESMTP id 2A60411E80A3 for <tictoc@ietf.org>; Mon,  5 Nov 2012 15:44:36 -0800 (PST)
Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp8.relay.dfw1a.emailsrvr.com (SMTP Server) with ESMTP id E5E0D8416; Mon,  5 Nov 2012 18:44:34 -0500 (EST)
X-Virus-Scanned: OK
Received: by smtp8.relay.dfw1a.emailsrvr.com (Authenticated sender: odonoghue-AT-isoc.org) with ESMTPSA id ABE828132;  Mon,  5 Nov 2012 18:44:34 -0500 (EST)
Message-ID: <50984F62.4080309@isoc.org>
Date: Mon, 05 Nov 2012 18:44:34 -0500
From: Karen O'Donoghue <odonoghue@isoc.org>
Organization: ISOC
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:16.0) Gecko/20121010 Thunderbird/16.0.1
MIME-Version: 1.0
To: NTP Working Group <ntpwg@lists.ntp.org>,  "tictoc@ietf.org" <tictoc@ietf.org>
References: <20121101121722.29094.73706.idtracker@ietfa.amsl.com>
In-Reply-To: <20121101121722.29094.73706.idtracker@ietfa.amsl.com>
X-Forwarded-Message-Id: <20121101121722.29094.73706.idtracker@ietfa.amsl.com>
Content-Type: multipart/alternative; boundary="------------060404040602000808000601"
Subject: [TICTOC] Fwd: CORRECTION: Help the NomCom
X-BeenThere: tictoc@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: odonoghue@isoc.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: <http://www.ietf.org/mail-archive/web/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, 05 Nov 2012 23:44:37 -0000

This is a multi-part message in MIME format.
--------------060404040602000808000601
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit

Folks,

Just a reminder, nomcom feedback requested by 11 Nov 2012. See Matt's 
message below.

Karen


-------- Original Message --------
Subject: 	CORRECTION: Help the NomCom
Date: 	Thu, 01 Nov 2012 05:17:22 -0700
From: 	NomCom Chair <nomcom-chair@ietf.org>
To: 	Working Group Chairs <wgchairs@ietf.org>



I sent a message several hours ago requesting that you help and make
your working group aware that the NomCom is looking for input from the
community. This message had a minor error. The NomCom needs to
receive community input by November 11, 2012.

The full text of the corrected message is below
---------------------------------------------------

The IETF Nominations Committee (NomCom) continues to seek input from
the IETF Community. The NomCom would greatly appreciate any help you
could provide in making members of your working group aware of ways in
which they can provide valuable feedback to the NomCom.

In order to ensure that your input is received in time to be useful, the
NomCom needs to receive community feedback on or before Sunday, November 11.

The final list of candidates (as per RFC 5680) that the NomCom is
considering for open positions can be found at:
https://www.ietf.org/group/nomcom/2012/input/

The NomCom will be holding office hours during IETF 85, Monday-
Thursday from 1:00pm to 3:00pm in Room 305. The NomCom welcomes
comments on specific individuals, as well as general feedback related to
any of the positions that NomCom is considering.

Note: A list of leadership positions that the NomCom is considering can be
found at: https://www.ietf.org/group/nomcom/2012/

If the NomCom office hours are inconvenient for you or if you cannot
attend IETF 85, the NomCom is happy to take community input via email
to nomcom12 at ietf.org. Additionally, the NomCom is happy to arrange a
meeting outside of office hours, just send us email and we can set
something up.

Comments on specific candidates can also be provided to the NomCom
via the web feedback tool:
https://www.ietf.org/group/nomcom/2012/input/

Thank you for your help,
- Matt Lepinski
   nomcom-chair at ietf.org





--------------060404040602000808000601
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 bgcolor="#FFFFFF" text="#000000">
    Folks,<br>
    <br>
    Just a reminder, nomcom feedback requested by 11 Nov 2012. See
    Matt's message below.<br>
    <br>
    Karen<br>
    <div class="moz-forward-container"><br>
      <br>
      -------- Original Message --------
      <table class="moz-email-headers-table" border="0" cellpadding="0"
        cellspacing="0">
        <tbody>
          <tr>
            <th align="RIGHT" nowrap="nowrap" valign="BASELINE">Subject:
            </th>
            <td>CORRECTION: Help the NomCom</td>
          </tr>
          <tr>
            <th align="RIGHT" nowrap="nowrap" valign="BASELINE">Date: </th>
            <td>Thu, 01 Nov 2012 05:17:22 -0700</td>
          </tr>
          <tr>
            <th align="RIGHT" nowrap="nowrap" valign="BASELINE">From: </th>
            <td>NomCom Chair <a class="moz-txt-link-rfc2396E" href="mailto:nomcom-chair@ietf.org">&lt;nomcom-chair@ietf.org&gt;</a></td>
          </tr>
          <tr>
            <th align="RIGHT" nowrap="nowrap" valign="BASELINE">To: </th>
            <td>Working Group Chairs <a class="moz-txt-link-rfc2396E" href="mailto:wgchairs@ietf.org">&lt;wgchairs@ietf.org&gt;</a></td>
          </tr>
        </tbody>
      </table>
      <br>
      <br>
      <pre>I sent a message several hours ago requesting that you help and make 
your working group aware that the NomCom is looking for input from the 
community. This message had a minor error. The NomCom needs to 
receive community input by November 11, 2012. 

The full text of the corrected message is below
---------------------------------------------------

The IETF Nominations Committee (NomCom) continues to seek input from
the IETF Community. The NomCom would greatly appreciate any help you
could provide in making members of your working group aware of ways in
which they can provide valuable feedback to the NomCom.

In order to ensure that your input is received in time to be useful, the 
NomCom needs to receive community feedback on or before Sunday, November 11.

The final list of candidates (as per RFC 5680) that the NomCom is 
considering for open positions can be found at: 
<a class="moz-txt-link-freetext" href="https://www.ietf.org/group/nomcom/2012/input/">https://www.ietf.org/group/nomcom/2012/input/</a>

The NomCom will be holding office hours during IETF 85, Monday-
Thursday from 1:00pm to 3:00pm in Room 305. The NomCom welcomes 
comments on specific individuals, as well as general feedback related to 
any of the positions that NomCom is considering.

Note: A list of leadership positions that the NomCom is considering can be 
found at: <a class="moz-txt-link-freetext" href="https://www.ietf.org/group/nomcom/2012/">https://www.ietf.org/group/nomcom/2012/</a>

If the NomCom office hours are inconvenient for you or if you cannot 
attend IETF 85, the NomCom is happy to take community input via email 
to nomcom12 at ietf.org. Additionally, the NomCom is happy to arrange a 
meeting outside of office hours, just send us email and we can set 
something up.

Comments on specific candidates can also be provided to the NomCom
via the web feedback tool: 
<a class="moz-txt-link-freetext" href="https://www.ietf.org/group/nomcom/2012/input/">https://www.ietf.org/group/nomcom/2012/input/</a>

Thank you for your help,
- Matt Lepinski
  nomcom-chair at ietf.org
</pre>
      <br>
      <br>
    </div>
    <br>
  </body>
</html>

--------------060404040602000808000601--

From talmi@marvell.com  Tue Nov  6 10:01:22 2012
Return-Path: <talmi@marvell.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 9EC3921F8A27 for <tictoc@ietfa.amsl.com>; Tue,  6 Nov 2012 10:01:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.999
X-Spam-Level: 
X-Spam-Status: No, score=-2.999 tagged_above=-999 required=5 tests=[AWL=-0.400, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4dO8nx8rvCYf for <tictoc@ietfa.amsl.com>; Tue,  6 Nov 2012 10:01:21 -0800 (PST)
Received: from galiil.marvell.com (galiil.marvell.com [199.203.130.254]) by ietfa.amsl.com (Postfix) with ESMTP id E388221F894E for <tictoc@ietf.org>; Tue,  6 Nov 2012 10:01:20 -0800 (PST)
From: Tal Mizrahi <talmi@marvell.com>
To: Doug Arnold <darnold@symmetricom.com>, "kodonog@pobox.com" <kodonog@pobox.com>
Date: Tue, 6 Nov 2012 20:01:14 +0200
Thread-Topic: [TICTOC] [ntpwg] I-D Action: draft-ietf-tictoc-1588overmpls-03.txt
Thread-Index: AQHNsTCbPW2EX9L8MU2crsweK4HziJfdFWrwgAAYy0A=
Message-ID: <74470498B659FA4687F0B0018C19A89C01A0F8E3363E@IL-MB01.marvell.com>
References: <20121022082804.12835.73453.idtracker@ietfa.amsl.com> <74470498B659FA4687F0B0018C19A89C01A0F8D26CAB@IL-MB01.marvell.com>, <4A6CE49E6084B141B15C0713B8993F281BD0E582@SJEXCHMB12.corp.ad.broadcom.com> <74470498B659FA4687F0B0018C19A89C01A0F842952E@IL-MB01.marvell.com> <5086B371.6020700@pobox.com> <D2CC4074A4E35B43A4EE2CA7859D567B69333E0D@SJC-MBX-01.symmetricom.com>
In-Reply-To: <D2CC4074A4E35B43A4EE2CA7859D567B69333E0D@SJC-MBX-01.symmetricom.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "ntpwg@lists.ntp.org" <ntpwg@lists.ntp.org>, "tictoc@ietf.org" <tictoc@ietf.org>, "draft-ietf-tictoc-1588overmpls@tools.ietf.org" <draft-ietf-tictoc-1588overmpls@tools.ietf.org>
Subject: Re: [TICTOC] [ntpwg] I-D Action:	draft-ietf-tictoc-1588overmpls-03.txt
X-BeenThere: tictoc@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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, 06 Nov 2012 18:01:22 -0000

Right, I agree.
My point was just that we may be provisioning for something that will come =
out completely different than what we currently expect.
It is kind of like buying the tires before you decide which car you want to=
 buy.  :)

Tal.


-----Original Message-----
From: Doug Arnold [mailto:darnold@symmetricom.com]=20
Sent: Tuesday, November 06, 2012 11:31 AM
To: kodonog@pobox.com; Tal Mizrahi
Cc: ntpwg@lists.ntp.org; tictoc@ietf.org; draft-ietf-tictoc-1588overmpls@to=
ols.ietf.org
Subject: RE: [TICTOC] [ntpwg] I-D Action: draft-ietf-tictoc-1588overmpls-03=
.txt

There is also some value in having these the treatment of NTP and PTP in on=
e place.

//Doug Arnold

-----Original Message-----
From: tictoc-bounces@ietf.org [mailto:tictoc-bounces@ietf.org] On Behalf Of=
 Karen O'Donoghue
Sent: Tuesday, October 23, 2012 8:11 AM
To: Tal Mizrahi
Cc: ntpwg@lists.ntp.org; tictoc@ietf.org; draft-ietf-tictoc-1588overmpls@to=
ols.ietf.org
Subject: Re: [TICTOC] [ntpwg] I-D Action: draft-ietf-tictoc-1588overmpls-03=
.txt

Tal,

It is true that developing an NTP option in parallel would potentially be m=
ore efficient and coherent; however, we have thus far had no volunteers to =
work on that document. The current approach is flexible enough to support P=
TP, NTP, and possibly other timing methods which is a generalization of the=
 solution originally proposed.

We welcome proposals and volunteer document editors who wish to pursue the =
NTP option.

Regards,
Karen

On 10/22/12 4:35 PM, Tal Mizrahi wrote:
> Hi Shahram,
>
> Thanks for the prompt response.
> I would suggest to add some text to explain the scope of this draft in th=
e context of NTP, i.e., your explanation below.
>
> A question to the WG chairs: if NTP TCs are indeed on the agenda, wouldn'=
t it be best to define these entities in parallel to the MPLS draft? It see=
ms more natural, and more likely to produce a coherent mechanism.
>
> Thanks,
> Tal.
>
> ________________________________________
> From: Shahram Davari [davari@broadcom.com]
> Sent: Monday, October 22, 2012 6:46 PM
> To: Tal Mizrahi; draft-ietf-tictoc-1588overmpls@tools.ietf.org
> Cc: tictoc@ietf.org; ntpwg@lists.ntp.org
> Subject: RE: [TICTOC] I-D Action:=20
> draft-ietf-tictoc-1588overmpls-03.txt
>
> Hi Tal,
>
> If you recall the Area director asked for generalizing this draft to NTP =
and other possible future Timing methods such as a Shim header that can car=
ry Timing. I know NTP does not have TC, but IETF may add TC in future. Also=
 on the egress LER the timing Label (defined in the draft) may be used as a=
n indicator to sample ToD at the port level.
>
> Thanks
> Shahram
>
> -----Original Message-----
> From: Tal Mizrahi [mailto:talmi@marvell.com]
> Sent: Monday, October 22, 2012 7:47 AM
> To: draft-ietf-tictoc-1588overmpls@tools.ietf.org
> Cc: tictoc@ietf.org; ntpwg@lists.ntp.org
> Subject: RE: [TICTOC] I-D Action:=20
> draft-ietf-tictoc-1588overmpls-03.txt
>
> Hi Shahram et al.
>
> What is the motivation for adding NTP to this draft?
> Are we planning to define something similar to a correctionField in NTP?
>
> Regards,
> Tal.
>
>
> -----Original Message-----
> From: tictoc-bounces@ietf.org [mailto:tictoc-bounces@ietf.org] On=20
> Behalf Of internet-drafts@ietf.org
> Sent: Monday, October 22, 2012 10:28 AM
> To: i-d-announce@ietf.org
> Cc: tictoc@ietf.org
> Subject: [TICTOC] I-D Action: draft-ietf-tictoc-1588overmpls-03.txt
>
>
> A New Internet-Draft is available from the on-line Internet-Drafts direct=
ories.
>   This draft is a work item of the Timing over IP Connection and Transfer=
 of Clock Working Group of the IETF.
>
>          Title           : Transporting Timing messages over MPLS Network=
s
>          Author(s)       : Shahram Davari
>                            Amit Oren
>                            Manav Bhatia
>                            Peter Roberts
>                            Laurent Montini
>          Filename        : draft-ietf-tictoc-1588overmpls-03.txt
>          Pages           : 36
>          Date            : 2012-10-22
>
> Abstract:
>     This document defines the method for transporting Timing messages
>     such as PTP and NTP over an MPLS network.  The method allows for the
>     easy identification of these PDUs at the port level to allow for port
>     level processing of these PDUs in both LERs and LSRs.
>
>     The basic idea is to transport Timing messages inside dedicated MPLS
>     LSPs.  These LSPs only carry timing messages and possibly Control and
>     Management packets, but they do not carry customer traffic.
>
>     Two methods for transporting Timing messages over MPLS are defined.
>     The first method is to transport Timing messages directly over the
>     dedicated MPLS LSP via UDP/IP encapsulation, which is suitable for
>     MPLS networks.  The second method is to transport Timing messages
>     inside a PW via Ethernet encapsulation, which is suitable for both
>     MPLS and MPLS-TP networks.
>
>
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-ietf-tictoc-1588overmpls
>
> There's also a htmlized version available at:
> http://tools.ietf.org/html/draft-ietf-tictoc-1588overmpls-03
>
> A diff from the previous version is available at:
> http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-tictoc-1588overmpls-03
>
>
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
>
> _______________________________________________
> TICTOC mailing list
> TICTOC@ietf.org
> https://www.ietf.org/mailman/listinfo/tictoc
> _______________________________________________
> ntpwg mailing list
> ntpwg@lists.ntp.org
> http://lists.ntp.org/listinfo/ntpwg

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

From davari@broadcom.com  Tue Nov  6 11:59:22 2012
Return-Path: <davari@broadcom.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 4B0AF21F8AC4 for <tictoc@ietfa.amsl.com>; Tue,  6 Nov 2012 11:59:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8vn4Jhk2MGbc for <tictoc@ietfa.amsl.com>; Tue,  6 Nov 2012 11:59:20 -0800 (PST)
Received: from mms3.broadcom.com (mms3.broadcom.com [216.31.210.19]) by ietfa.amsl.com (Postfix) with ESMTP id 9E18D21F894E for <tictoc@ietf.org>; Tue,  6 Nov 2012 11:59:20 -0800 (PST)
Received: from [10.16.192.232] by mms3.broadcom.com with ESMTP (Broadcom SMTP Relay (Email Firewall v6.5)); Tue, 06 Nov 2012 11:55:24 -0800
X-Server-Uuid: B86B6450-0931-4310-942E-F00ED04CA7AF
Received: from SJEXCHCAS02.corp.ad.broadcom.com (10.16.192.37) by SJEXCHHUB02.corp.ad.broadcom.com (10.16.192.232) with Microsoft SMTP Server (TLS) id 8.2.247.2; Tue, 6 Nov 2012 11:58:49 -0800
Received: from SJEXCHMB12.corp.ad.broadcom.com ( [fe80::bc15:c1e1:c29a:36f7]) by sjexchcas02.corp.ad.broadcom.com ( [::1]) with mapi id 14.01.0355.002; Tue, 6 Nov 2012 11:58:28 -0800
From: "Shahram Davari" <davari@broadcom.com>
To: "Tal Mizrahi" <talmi@marvell.com>, "Doug Arnold" <darnold@symmetricom.com>, "kodonog@pobox.com" <kodonog@pobox.com>
Thread-Topic: [TICTOC] [ntpwg] I-D Action: draft-ietf-tictoc-1588overmpls-03.txt
Thread-Index: AQHNvDwwqGLXjSexyEefba1PRRGg25fdnw8A//+ZqFA=
Date: Tue, 6 Nov 2012 19:58:27 +0000
Message-ID: <4A6CE49E6084B141B15C0713B8993F281BD1926C@SJEXCHMB12.corp.ad.broadcom.com>
References: <20121022082804.12835.73453.idtracker@ietfa.amsl.com> <74470498B659FA4687F0B0018C19A89C01A0F8D26CAB@IL-MB01.marvell.com>, <4A6CE49E6084B141B15C0713B8993F281BD0E582@SJEXCHMB12.corp.ad.broadcom.com> <74470498B659FA4687F0B0018C19A89C01A0F842952E@IL-MB01.marvell.com> <5086B371.6020700@pobox.com> <D2CC4074A4E35B43A4EE2CA7859D567B69333E0D@SJC-MBX-01.symmetricom.com> <74470498B659FA4687F0B0018C19A89C01A0F8E3363E@IL-MB01.marvell.com>
In-Reply-To: <74470498B659FA4687F0B0018C19A89C01A0F8E3363E@IL-MB01.marvell.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.16.203.100]
MIME-Version: 1.0
X-WSS-ID: 7C87B4A63T43267962-01-01
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Cc: "ntpwg@lists.ntp.org" <ntpwg@lists.ntp.org>, "tictoc@ietf.org" <tictoc@ietf.org>, "draft-ietf-tictoc-1588overmpls@tools.ietf.org" <draft-ietf-tictoc-1588overmpls@tools.ietf.org>
Subject: Re: [TICTOC] [ntpwg] I-D Action: draft-ietf-tictoc-1588overmpls-03.txt
X-BeenThere: tictoc@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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, 06 Nov 2012 19:59:22 -0000

Tal,

This draft just leaves the possibility for NTP and other Timing protocols t=
o use the same mechanism. It does not define anything specific to NTP. Usin=
g your analogy, it basically defines a method for ordering a Tire, but does=
 not define the Actual tire spec. So any tire could be purchased with this =
method, or alternatively another method.

Thanks
Shahram

-----Original Message-----
From: tictoc-bounces@ietf.org [mailto:tictoc-bounces@ietf.org] On Behalf Of=
 Tal Mizrahi
Sent: Tuesday, November 06, 2012 10:01 AM
To: Doug Arnold; kodonog@pobox.com
Cc: ntpwg@lists.ntp.org; tictoc@ietf.org; draft-ietf-tictoc-1588overmpls@to=
ols.ietf.org
Subject: Re: [TICTOC] [ntpwg] I-D Action: draft-ietf-tictoc-1588overmpls-03=
.txt

Right, I agree.
My point was just that we may be provisioning for something that will come =
out completely different than what we currently expect.
It is kind of like buying the tires before you decide which car you want to=
 buy.  :)

Tal.


-----Original Message-----
From: Doug Arnold [mailto:darnold@symmetricom.com]=20
Sent: Tuesday, November 06, 2012 11:31 AM
To: kodonog@pobox.com; Tal Mizrahi
Cc: ntpwg@lists.ntp.org; tictoc@ietf.org; draft-ietf-tictoc-1588overmpls@to=
ols.ietf.org
Subject: RE: [TICTOC] [ntpwg] I-D Action: draft-ietf-tictoc-1588overmpls-03=
.txt

There is also some value in having these the treatment of NTP and PTP in on=
e place.

//Doug Arnold

-----Original Message-----
From: tictoc-bounces@ietf.org [mailto:tictoc-bounces@ietf.org] On Behalf Of=
 Karen O'Donoghue
Sent: Tuesday, October 23, 2012 8:11 AM
To: Tal Mizrahi
Cc: ntpwg@lists.ntp.org; tictoc@ietf.org; draft-ietf-tictoc-1588overmpls@to=
ols.ietf.org
Subject: Re: [TICTOC] [ntpwg] I-D Action: draft-ietf-tictoc-1588overmpls-03=
.txt

Tal,

It is true that developing an NTP option in parallel would potentially be m=
ore efficient and coherent; however, we have thus far had no volunteers to =
work on that document. The current approach is flexible enough to support P=
TP, NTP, and possibly other timing methods which is a generalization of the=
 solution originally proposed.

We welcome proposals and volunteer document editors who wish to pursue the =
NTP option.

Regards,
Karen

On 10/22/12 4:35 PM, Tal Mizrahi wrote:
> Hi Shahram,
>
> Thanks for the prompt response.
> I would suggest to add some text to explain the scope of this draft in th=
e context of NTP, i.e., your explanation below.
>
> A question to the WG chairs: if NTP TCs are indeed on the agenda, wouldn'=
t it be best to define these entities in parallel to the MPLS draft? It see=
ms more natural, and more likely to produce a coherent mechanism.
>
> Thanks,
> Tal.
>
> ________________________________________
> From: Shahram Davari [davari@broadcom.com]
> Sent: Monday, October 22, 2012 6:46 PM
> To: Tal Mizrahi; draft-ietf-tictoc-1588overmpls@tools.ietf.org
> Cc: tictoc@ietf.org; ntpwg@lists.ntp.org
> Subject: RE: [TICTOC] I-D Action:=20
> draft-ietf-tictoc-1588overmpls-03.txt
>
> Hi Tal,
>
> If you recall the Area director asked for generalizing this draft to NTP =
and other possible future Timing methods such as a Shim header that can car=
ry Timing. I know NTP does not have TC, but IETF may add TC in future. Also=
 on the egress LER the timing Label (defined in the draft) may be used as a=
n indicator to sample ToD at the port level.
>
> Thanks
> Shahram
>
> -----Original Message-----
> From: Tal Mizrahi [mailto:talmi@marvell.com]
> Sent: Monday, October 22, 2012 7:47 AM
> To: draft-ietf-tictoc-1588overmpls@tools.ietf.org
> Cc: tictoc@ietf.org; ntpwg@lists.ntp.org
> Subject: RE: [TICTOC] I-D Action:=20
> draft-ietf-tictoc-1588overmpls-03.txt
>
> Hi Shahram et al.
>
> What is the motivation for adding NTP to this draft?
> Are we planning to define something similar to a correctionField in NTP?
>
> Regards,
> Tal.
>
>
> -----Original Message-----
> From: tictoc-bounces@ietf.org [mailto:tictoc-bounces@ietf.org] On=20
> Behalf Of internet-drafts@ietf.org
> Sent: Monday, October 22, 2012 10:28 AM
> To: i-d-announce@ietf.org
> Cc: tictoc@ietf.org
> Subject: [TICTOC] I-D Action: draft-ietf-tictoc-1588overmpls-03.txt
>
>
> A New Internet-Draft is available from the on-line Internet-Drafts direct=
ories.
>   This draft is a work item of the Timing over IP Connection and Transfer=
 of Clock Working Group of the IETF.
>
>          Title           : Transporting Timing messages over MPLS Network=
s
>          Author(s)       : Shahram Davari
>                            Amit Oren
>                            Manav Bhatia
>                            Peter Roberts
>                            Laurent Montini
>          Filename        : draft-ietf-tictoc-1588overmpls-03.txt
>          Pages           : 36
>          Date            : 2012-10-22
>
> Abstract:
>     This document defines the method for transporting Timing messages
>     such as PTP and NTP over an MPLS network.  The method allows for the
>     easy identification of these PDUs at the port level to allow for port
>     level processing of these PDUs in both LERs and LSRs.
>
>     The basic idea is to transport Timing messages inside dedicated MPLS
>     LSPs.  These LSPs only carry timing messages and possibly Control and
>     Management packets, but they do not carry customer traffic.
>
>     Two methods for transporting Timing messages over MPLS are defined.
>     The first method is to transport Timing messages directly over the
>     dedicated MPLS LSP via UDP/IP encapsulation, which is suitable for
>     MPLS networks.  The second method is to transport Timing messages
>     inside a PW via Ethernet encapsulation, which is suitable for both
>     MPLS and MPLS-TP networks.
>
>
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-ietf-tictoc-1588overmpls
>
> There's also a htmlized version available at:
> http://tools.ietf.org/html/draft-ietf-tictoc-1588overmpls-03
>
> A diff from the previous version is available at:
> http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-tictoc-1588overmpls-03
>
>
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
>
> _______________________________________________
> TICTOC mailing list
> TICTOC@ietf.org
> https://www.ietf.org/mailman/listinfo/tictoc
> _______________________________________________
> ntpwg mailing list
> ntpwg@lists.ntp.org
> http://lists.ntp.org/listinfo/ntpwg

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



From odonoghue@isoc.org  Tue Nov 13 03:00:27 2012
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 3B2D121F8485 for <tictoc@ietfa.amsl.com>; Tue, 13 Nov 2012 03:00:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.599
X-Spam-Level: 
X-Spam-Status: No, score=-103.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id p-dOPS4-axcc for <tictoc@ietfa.amsl.com>; Tue, 13 Nov 2012 03:00:26 -0800 (PST)
Received: from smtp175.iad.emailsrvr.com (smtp175.iad.emailsrvr.com [207.97.245.175]) by ietfa.amsl.com (Postfix) with ESMTP id 3F3B221F847F for <tictoc@ietf.org>; Tue, 13 Nov 2012 03:00:26 -0800 (PST)
Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp47.relay.iad1a.emailsrvr.com (SMTP Server) with ESMTP id 48E393A837E for <tictoc@ietf.org>; Tue, 13 Nov 2012 06:00:24 -0500 (EST)
X-Virus-Scanned: OK
Received: by smtp47.relay.iad1a.emailsrvr.com (Authenticated sender: odonoghue-AT-isoc.org) with ESMTPSA id F246C3A8A83 for <tictoc@ietf.org>; Tue, 13 Nov 2012 06:00:23 -0500 (EST)
Message-ID: <50A22846.3080609@isoc.org>
Date: Tue, 13 Nov 2012 06:00:22 -0500
From: Karen O'Donoghue <odonoghue@isoc.org>
Organization: ISOC
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:16.0) Gecko/20121010 Thunderbird/16.0.1
MIME-Version: 1.0
To: "tictoc@ietf.org" <tictoc@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: [TICTOC] consensus question on change of scope for the 1588 mib document
X-BeenThere: tictoc@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: odonoghue@isoc.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: <http://www.ietf.org/mail-archive/web/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, 13 Nov 2012 11:00:27 -0000

During last week's tictoc meeting at ietf85, it was decided that the mib 
would be changed from a read only mib to a read/write mib for 
configuration purposes.

The authors proposed this change, and they believe this will not 
significantly delay publication of the mib.

The current draft is available at: 
http://tools.ietf.org/wg/tictoc/draft-ietf-tictoc-ptp-mib/

The feeling in the room was that this was an acceptable change. This 
email is to confirm that decision and to solicit comments or concerns 
from the mailing list.

Regards,
Karen



From yaakov_s@rad.com  Thu Nov 15 00:53:37 2012
Return-Path: <yaakov_s@rad.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 295AA21F85EB for <tictoc@ietfa.amsl.com>; Thu, 15 Nov 2012 00:53:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.597
X-Spam-Level: 
X-Spam-Status: No, score=-102.597 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, UNPARSEABLE_RELAY=0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id t2T3N5GtAAPM for <tictoc@ietfa.amsl.com>; Thu, 15 Nov 2012 00:53:36 -0800 (PST)
Received: from rad.co.il (mailrelay01.rad.co.il [62.0.23.252]) by ietfa.amsl.com (Postfix) with ESMTP id 05C9621F85E3 for <tictoc@ietf.org>; Thu, 15 Nov 2012 00:53:33 -0800 (PST)
Received: from Internal Mail-Server by MailRelay01 (envelope-from yaakov?s@rad.com) with AES128-SHA encrypted SMTP; 15 Nov 2012 11:02:41 +0200
Received: from EXRAD5.ad.rad.co.il ([192.114.24.28]) by EXRAD5.ad.rad.co.il ([192.114.24.28]) with mapi id 14.02.0298.004; Thu, 15 Nov 2012 10:53:29 +0200
From: Yaakov Stein <yaakov_s@rad.com>
To: "tictoc@ietf.org" <tictoc@ietf.org>
Thread-Topic: [TICTOC] consensus question on change of scope for the 1588 mib	document
Thread-Index: AQHNwY4fmq0dnBFmnUCRHLQMzW0mdJfqmeKg
Date: Thu, 15 Nov 2012 08:53:29 +0000
Message-ID: <07F7D7DED63154409F13298786A2ADC904647348@EXRAD5.ad.rad.co.il>
References: <50A22846.3080609@isoc.org>
In-Reply-To: <50A22846.3080609@isoc.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [192.115.243.62]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Commtouch-Refid: str=0001.0A090205.50A4AD8A.0054,ss=1,fgs=0
Subject: Re: [TICTOC] consensus question on change of scope for the 1588 mib	document
X-BeenThere: tictoc@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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, 15 Nov 2012 08:53:37 -0000

With chair hat off -

I am in favor of the change as long as it remains a minor change,
and introduce radically new functionality.

Y(J)S=20

-----Original Message-----
From: tictoc-bounces@ietf.org [mailto:tictoc-bounces@ietf.org] On Behalf Of=
 Karen O'Donoghue
Sent: Tuesday, November 13, 2012 13:00
To: tictoc@ietf.org
Subject: [TICTOC] consensus question on change of scope for the 1588 mib do=
cument

During last week's tictoc meeting at ietf85, it was decided that the mib=20
would be changed from a read only mib to a read/write mib for=20
configuration purposes.

The authors proposed this change, and they believe this will not=20
significantly delay publication of the mib.

The current draft is available at:=20
http://tools.ietf.org/wg/tictoc/draft-ietf-tictoc-ptp-mib/

The feeling in the room was that this was an acceptable change. This=20
email is to confirm that decision and to solicit comments or concerns=20
from the mailing list.

Regards,
Karen


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

From gregimirsky@gmail.com  Thu Nov 15 09:57:16 2012
Return-Path: <gregimirsky@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 5B73C21F8896 for <tictoc@ietfa.amsl.com>; Thu, 15 Nov 2012 09:57:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.598
X-Spam-Level: 
X-Spam-Status: No, score=-3.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4WsgrX8WZNTV for <tictoc@ietfa.amsl.com>; Thu, 15 Nov 2012 09:57:13 -0800 (PST)
Received: from mail-ea0-f172.google.com (mail-ea0-f172.google.com [209.85.215.172]) by ietfa.amsl.com (Postfix) with ESMTP id 9F54221F88A9 for <tictoc@ietf.org>; Thu, 15 Nov 2012 09:57:12 -0800 (PST)
Received: by mail-ea0-f172.google.com with SMTP id k13so854126eaa.31 for <tictoc@ietf.org>; Thu, 15 Nov 2012 09:57:11 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=4nEfMiHED5jB8QZDmY0Or2Mj2RsNz8fjLib9FWtooms=; b=WNr/ZkUOCqScdHnt+fy9XIIMeGo7vyNbt5Wok6aGQQalteTzwJ8zjWGCOCHkUcAS5v J5QFbHx7lKTEjODOflQPxwgVYZjeUqNswzh77WmehpQF4oTrmwLvzCluHvsc1we6zASV bAL1hnpsFq3t8ipd1tdJA5KMUg6Xyf27rpjTlz0lRpmC2mlgtec+k9SrcUB9jUPvYrba TayrKw6Kk6zP4NH+whLWF1pGgnbnllzf9Z3U04p6zA8Hb3wmAefFWyfpVUBZOH0v7fXJ PmX4hAfCj3o6SRRn0tdqiae529l8KuZAf8dqqLbUmH7Hm3g/ox8RxLLxNIszqkhoiLqu dS2w==
MIME-Version: 1.0
Received: by 10.14.184.2 with SMTP id r2mr5909111eem.43.1353002231816; Thu, 15 Nov 2012 09:57:11 -0800 (PST)
Received: by 10.14.180.70 with HTTP; Thu, 15 Nov 2012 09:57:11 -0800 (PST)
In-Reply-To: <07F7D7DED63154409F13298786A2ADC904647348@EXRAD5.ad.rad.co.il>
References: <50A22846.3080609@isoc.org> <07F7D7DED63154409F13298786A2ADC904647348@EXRAD5.ad.rad.co.il>
Date: Thu, 15 Nov 2012 09:57:11 -0800
Message-ID: <CA+RyBmWNmxMTcOBjUqJwMVDbwoErvd1J9xMzhP2EC-G1VuSanw@mail.gmail.com>
From: Greg Mirsky <gregimirsky@gmail.com>
To: Yaakov Stein <yaakov_s@rad.com>
Content-Type: multipart/alternative; boundary=047d7b3439346861a104ce8c6169
Cc: "tictoc@ietf.org" <tictoc@ietf.org>
Subject: Re: [TICTOC] consensus question on change of scope for the 1588 mib document
X-BeenThere: tictoc@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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, 15 Nov 2012 17:57:16 -0000

--047d7b3439346861a104ce8c6169
Content-Type: text/plain; charset=ISO-8859-1

Dear Yaakov, et al.,
changing from R/O paradigm to R/W is never a small deal. It is, IMHO, an
endeavor. Had the R/O version been through MIB Doctor review? I'd expect it
to be ran though again once R/W objects introduced.

Regards,
Greg

On Thu, Nov 15, 2012 at 12:53 AM, Yaakov Stein <yaakov_s@rad.com> wrote:

> With chair hat off -
>
> I am in favor of the change as long as it remains a minor change,
> and introduce radically new functionality.
>
> Y(J)S
>
> -----Original Message-----
> From: tictoc-bounces@ietf.org [mailto:tictoc-bounces@ietf.org] On Behalf
> Of Karen O'Donoghue
> Sent: Tuesday, November 13, 2012 13:00
> To: tictoc@ietf.org
> Subject: [TICTOC] consensus question on change of scope for the 1588 mib
> document
>
> During last week's tictoc meeting at ietf85, it was decided that the mib
> would be changed from a read only mib to a read/write mib for
> configuration purposes.
>
> The authors proposed this change, and they believe this will not
> significantly delay publication of the mib.
>
> The current draft is available at:
> http://tools.ietf.org/wg/tictoc/draft-ietf-tictoc-ptp-mib/
>
> The feeling in the room was that this was an acceptable change. This
> email is to confirm that decision and to solicit comments or concerns
> from the mailing list.
>
> Regards,
> Karen
>
>
> _______________________________________________
> TICTOC mailing list
> TICTOC@ietf.org
> https://www.ietf.org/mailman/listinfo/tictoc
> _______________________________________________
> TICTOC mailing list
> TICTOC@ietf.org
> https://www.ietf.org/mailman/listinfo/tictoc
>

--047d7b3439346861a104ce8c6169
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Dear Yaakov, et al.,<br>changing from R/O paradigm to R/W is never a small =
deal. It is, IMHO, an endeavor. Had the R/O version been through MIB Doctor=
 review? I&#39;d expect it to be ran though again once R/W objects introduc=
ed.<br>
<br>Regards,<br>Greg<br><br><div class=3D"gmail_quote">On Thu, Nov 15, 2012=
 at 12:53 AM, Yaakov Stein <span dir=3D"ltr">&lt;<a href=3D"mailto:yaakov_s=
@rad.com" target=3D"_blank">yaakov_s@rad.com</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">
With chair hat off -<br>
<br>
I am in favor of the change as long as it remains a minor change,<br>
and introduce radically new functionality.<br>
<br>
Y(J)S<br>
<br>
-----Original Message-----<br>
From: <a href=3D"mailto:tictoc-bounces@ietf.org">tictoc-bounces@ietf.org</a=
> [mailto:<a href=3D"mailto:tictoc-bounces@ietf.org">tictoc-bounces@ietf.or=
g</a>] On Behalf Of Karen O&#39;Donoghue<br>
Sent: Tuesday, November 13, 2012 13:00<br>
To: <a href=3D"mailto:tictoc@ietf.org">tictoc@ietf.org</a><br>
Subject: [TICTOC] consensus question on change of scope for the 1588 mib do=
cument<br>
<br>
During last week&#39;s tictoc meeting at ietf85, it was decided that the mi=
b<br>
would be changed from a read only mib to a read/write mib for<br>
configuration purposes.<br>
<br>
The authors proposed this change, and they believe this will not<br>
significantly delay publication of the mib.<br>
<br>
The current draft is available at:<br>
<a href=3D"http://tools.ietf.org/wg/tictoc/draft-ietf-tictoc-ptp-mib/" targ=
et=3D"_blank">http://tools.ietf.org/wg/tictoc/draft-ietf-tictoc-ptp-mib/</a=
><br>
<br>
The feeling in the room was that this was an acceptable change. This<br>
email is to confirm that decision and to solicit comments or concerns<br>
from the mailing list.<br>
<br>
Regards,<br>
Karen<br>
<br>
<br>
_______________________________________________<br>
TICTOC mailing list<br>
<a href=3D"mailto:TICTOC@ietf.org">TICTOC@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/tictoc" target=3D"_blank">=
https://www.ietf.org/mailman/listinfo/tictoc</a><br>
_______________________________________________<br>
TICTOC mailing list<br>
<a href=3D"mailto:TICTOC@ietf.org">TICTOC@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/tictoc" target=3D"_blank">=
https://www.ietf.org/mailman/listinfo/tictoc</a><br>
</blockquote></div><br>

--047d7b3439346861a104ce8c6169--

From brian@innovationslab.net  Thu Nov 15 11:34:53 2012
Return-Path: <brian@innovationslab.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 32B9421F8530 for <tictoc@ietfa.amsl.com>; Thu, 15 Nov 2012 11:34:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.466
X-Spam-Level: 
X-Spam-Status: No, score=-102.466 tagged_above=-999 required=5 tests=[AWL=0.133, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id oOgVXB7KrsID for <tictoc@ietfa.amsl.com>; Thu, 15 Nov 2012 11:34:52 -0800 (PST)
Received: from uillean.fuaim.com (uillean.fuaim.com [206.197.161.140]) by ietfa.amsl.com (Postfix) with ESMTP id 5D25221F852D for <tictoc@ietf.org>; Thu, 15 Nov 2012 11:34:52 -0800 (PST)
Received: from clairseach.fuaim.com (clairseach-high.fuaim.com [206.197.161.158]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by uillean.fuaim.com (Postfix) with ESMTP id 521568809E for <tictoc@ietf.org>; Thu, 15 Nov 2012 11:34:52 -0800 (PST)
Received: from clemson.local (c-69-140-213-249.hsd1.md.comcast.net [69.140.213.249]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by clairseach.fuaim.com (Postfix) with ESMTP id 15725160180 for <tictoc@ietf.org>; Thu, 15 Nov 2012 11:34:51 -0800 (PST)
Message-ID: <50A543DA.9050702@innovationslab.net>
Date: Thu, 15 Nov 2012 14:34:50 -0500
From: Brian Haberman <brian@innovationslab.net>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:16.0) Gecko/20121026 Thunderbird/16.0.2
MIME-Version: 1.0
To: tictoc@ietf.org
References: <50A22846.3080609@isoc.org> <07F7D7DED63154409F13298786A2ADC904647348@EXRAD5.ad.rad.co.il> <CA+RyBmWNmxMTcOBjUqJwMVDbwoErvd1J9xMzhP2EC-G1VuSanw@mail.gmail.com>
In-Reply-To: <CA+RyBmWNmxMTcOBjUqJwMVDbwoErvd1J9xMzhP2EC-G1VuSanw@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [TICTOC] consensus question on change of scope for the 1588 mib document
X-BeenThere: tictoc@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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, 15 Nov 2012 19:34:53 -0000

On 11/15/12 12:57 PM, Greg Mirsky wrote:
> Dear Yaakov, et al.,
> changing from R/O paradigm to R/W is never a small deal. It is, IMHO, an
> endeavor. Had the R/O version been through MIB Doctor review? I'd expect it
> to be ran though again once R/W objects introduced.

Formal MIB Doctor reviews only occur when a draft reaches the IETF Last 
Call.

Regards,
Brian

>
> Regards,
> Greg
>
> On Thu, Nov 15, 2012 at 12:53 AM, Yaakov Stein <yaakov_s@rad.com> wrote:
>
>> With chair hat off -
>>
>> I am in favor of the change as long as it remains a minor change,
>> and introduce radically new functionality.
>>
>> Y(J)S
>>
>> -----Original Message-----
>> From: tictoc-bounces@ietf.org [mailto:tictoc-bounces@ietf.org] On Behalf
>> Of Karen O'Donoghue
>> Sent: Tuesday, November 13, 2012 13:00
>> To: tictoc@ietf.org
>> Subject: [TICTOC] consensus question on change of scope for the 1588 mib
>> document
>>
>> During last week's tictoc meeting at ietf85, it was decided that the mib
>> would be changed from a read only mib to a read/write mib for
>> configuration purposes.
>>
>> The authors proposed this change, and they believe this will not
>> significantly delay publication of the mib.
>>
>> The current draft is available at:
>> http://tools.ietf.org/wg/tictoc/draft-ietf-tictoc-ptp-mib/
>>
>> The feeling in the room was that this was an acceptable change. This
>> email is to confirm that decision and to solicit comments or concerns
>> from the mailing list.
>>
>> Regards,
>> Karen
>>
>>
>> _______________________________________________
>> TICTOC mailing list
>> TICTOC@ietf.org
>> https://www.ietf.org/mailman/listinfo/tictoc
>> _______________________________________________
>> TICTOC mailing list
>> TICTOC@ietf.org
>> https://www.ietf.org/mailman/listinfo/tictoc
>>
>
>
>
> _______________________________________________
> TICTOC mailing list
> TICTOC@ietf.org
> https://www.ietf.org/mailman/listinfo/tictoc
>


From kodonog@gmail.com  Thu Nov 15 15:02:54 2012
Return-Path: <kodonog@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 A401321F8522 for <tictoc@ietfa.amsl.com>; Thu, 15 Nov 2012 15:02:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.598
X-Spam-Level: 
X-Spam-Status: No, score=-103.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RpKl-XbFqQs9 for <tictoc@ietfa.amsl.com>; Thu, 15 Nov 2012 15:02:54 -0800 (PST)
Received: from mail-ee0-f44.google.com (mail-ee0-f44.google.com [74.125.83.44]) by ietfa.amsl.com (Postfix) with ESMTP id 91BE221F8A28 for <tictoc@ietf.org>; Thu, 15 Nov 2012 15:02:53 -0800 (PST)
Received: by mail-ee0-f44.google.com with SMTP id b47so1424767eek.31 for <tictoc@ietf.org>; Thu, 15 Nov 2012 15:02:52 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:message-id:date:from:reply-to:user-agent:mime-version:to :subject:references:in-reply-to:content-type; bh=FIBMEf3DDuLCKxvuXOluJuV3xFl1b4gHV1mTcfledcE=; b=rYLUYA+3PdZnOWUvBt54NwHOyY0yBT+xiJRDyII/+bHYfrFB/odOqkTMep0eE0kQ16 w3DkH4eZHLGSWZ7FJELd9IWB4VELzurLlqgahdTZ/RCCPTBjJR/QKeOaawtCdygua0Pt qTSi1ie58bgYHiFX/GvynIM5rA/wm2A0tF1257slKdxNpoaZ+DVLKORc8rsa4Lb+Oa70 UkeZuAZ9NKn6DdaRPfHLpMr5FWIwlpFS7NVIY37p5buLD1R1bXYFY9yzUCI4Ibp3ZKyC fYOqn/X17rH3RJjkQrjxrDMOfreDXqPTqMFoAl1r6MExbfiRDvOTDCyQKKJjmKcvDgIJ skoA==
Received: by 10.14.179.6 with SMTP id g6mr7837224eem.46.1353020572529; Thu, 15 Nov 2012 15:02:52 -0800 (PST)
Received: from kodonog-mac.local ([193.85.202.194]) by mx.google.com with ESMTPS id b44sm38930869eep.12.2012.11.15.15.02.51 (version=SSLv3 cipher=OTHER); Thu, 15 Nov 2012 15:02:52 -0800 (PST)
Sender: Karen ODonoghue <kodonog@gmail.com>
Message-ID: <50A57494.40306@pobox.com>
Date: Thu, 15 Nov 2012 18:02:44 -0500
From: Karen O'Donoghue <kodonog@pobox.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:16.0) Gecko/20121010 Thunderbird/16.0.1
MIME-Version: 1.0
To: tictoc@ietf.org
References: <50A22846.3080609@isoc.org> <07F7D7DED63154409F13298786A2ADC904647348@EXRAD5.ad.rad.co.il> <CA+RyBmWNmxMTcOBjUqJwMVDbwoErvd1J9xMzhP2EC-G1VuSanw@mail.gmail.com>
In-Reply-To: <CA+RyBmWNmxMTcOBjUqJwMVDbwoErvd1J9xMzhP2EC-G1VuSanw@mail.gmail.com>
Content-Type: multipart/alternative; boundary="------------040903040100070906010307"
Subject: Re: [TICTOC] consensus question on change of scope for the 1588 mib document
X-BeenThere: tictoc@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: kodonog@pobox.com
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: <http://www.ietf.org/mail-archive/web/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, 15 Nov 2012 23:02:54 -0000

This is a multi-part message in MIME format.
--------------040903040100070906010307
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Greg,

I don't expect this change to be a small deal. However, the authors have 
indicated they can accomplish the change without a significant delay in 
getting the document to WGLC. The reviews we've had thus far are 
informal, and the formal MIB Doctor review won't occur until the 
document goes to the IESG.

Karen

On 11/15/12 12:57 PM, Greg Mirsky wrote:
> Dear Yaakov, et al.,
> changing from R/O paradigm to R/W is never a small deal. It is, IMHO, 
> an endeavor. Had the R/O version been through MIB Doctor review? I'd 
> expect it to be ran though again once R/W objects introduced.
>
> Regards,
> Greg
>
> On Thu, Nov 15, 2012 at 12:53 AM, Yaakov Stein <yaakov_s@rad.com 
> <mailto:yaakov_s@rad.com>> wrote:
>
>     With chair hat off -
>
>     I am in favor of the change as long as it remains a minor change,
>     and introduce radically new functionality.
>
>     Y(J)S
>
>     -----Original Message-----
>     From: tictoc-bounces@ietf.org <mailto:tictoc-bounces@ietf.org>
>     [mailto:tictoc-bounces@ietf.org <mailto:tictoc-bounces@ietf.org>]
>     On Behalf Of Karen O'Donoghue
>     Sent: Tuesday, November 13, 2012 13:00
>     To: tictoc@ietf.org <mailto:tictoc@ietf.org>
>     Subject: [TICTOC] consensus question on change of scope for the
>     1588 mib document
>
>     During last week's tictoc meeting at ietf85, it was decided that
>     the mib
>     would be changed from a read only mib to a read/write mib for
>     configuration purposes.
>
>     The authors proposed this change, and they believe this will not
>     significantly delay publication of the mib.
>
>     The current draft is available at:
>     http://tools.ietf.org/wg/tictoc/draft-ietf-tictoc-ptp-mib/
>
>     The feeling in the room was that this was an acceptable change. This
>     email is to confirm that decision and to solicit comments or concerns
>     from the mailing list.
>
>     Regards,
>     Karen
>
>
>     _______________________________________________
>     TICTOC mailing list
>     TICTOC@ietf.org <mailto:TICTOC@ietf.org>
>     https://www.ietf.org/mailman/listinfo/tictoc
>     _______________________________________________
>     TICTOC mailing list
>     TICTOC@ietf.org <mailto:TICTOC@ietf.org>
>     https://www.ietf.org/mailman/listinfo/tictoc
>
>
>
>
> _______________________________________________
> TICTOC mailing list
> TICTOC@ietf.org
> https://www.ietf.org/mailman/listinfo/tictoc


--------------040903040100070906010307
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

<html>
  <head>
    <meta content="text/html; charset=ISO-8859-1"
      http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    <div class="moz-cite-prefix">Greg,<br>
      <br>
      I don't expect this change to be a small deal. However, the
      authors have indicated they can accomplish the change without a
      significant delay in getting the document to WGLC. The reviews
      we've had thus far are informal, and the formal MIB Doctor review
      won't occur until the document goes to the IESG.<br>
      <br>
      Karen<br>
      <br>
      On 11/15/12 12:57 PM, Greg Mirsky wrote:<br>
    </div>
    <blockquote
cite="mid:CA+RyBmWNmxMTcOBjUqJwMVDbwoErvd1J9xMzhP2EC-G1VuSanw@mail.gmail.com"
      type="cite">Dear Yaakov, et al.,<br>
      changing from R/O paradigm to R/W is never a small deal. It is,
      IMHO, an endeavor. Had the R/O version been through MIB Doctor
      review? I'd expect it to be ran though again once R/W objects
      introduced.<br>
      <br>
      Regards,<br>
      Greg<br>
      <br>
      <div class="gmail_quote">On Thu, Nov 15, 2012 at 12:53 AM, Yaakov
        Stein <span dir="ltr">&lt;<a moz-do-not-send="true"
            href="mailto:yaakov_s@rad.com" target="_blank">yaakov_s@rad.com</a>&gt;</span>
        wrote:<br>
        <blockquote class="gmail_quote" style="margin:0 0 0
          .8ex;border-left:1px #ccc solid;padding-left:1ex">
          With chair hat off -<br>
          <br>
          I am in favor of the change as long as it remains a minor
          change,<br>
          and introduce radically new functionality.<br>
          <br>
          Y(J)S<br>
          <br>
          -----Original Message-----<br>
          From: <a moz-do-not-send="true"
            href="mailto:tictoc-bounces@ietf.org">tictoc-bounces@ietf.org</a>
          [mailto:<a moz-do-not-send="true"
            href="mailto:tictoc-bounces@ietf.org">tictoc-bounces@ietf.org</a>]
          On Behalf Of Karen O'Donoghue<br>
          Sent: Tuesday, November 13, 2012 13:00<br>
          To: <a moz-do-not-send="true" href="mailto:tictoc@ietf.org">tictoc@ietf.org</a><br>
          Subject: [TICTOC] consensus question on change of scope for
          the 1588 mib document<br>
          <br>
          During last week's tictoc meeting at ietf85, it was decided
          that the mib<br>
          would be changed from a read only mib to a read/write mib for<br>
          configuration purposes.<br>
          <br>
          The authors proposed this change, and they believe this will
          not<br>
          significantly delay publication of the mib.<br>
          <br>
          The current draft is available at:<br>
          <a moz-do-not-send="true"
            href="http://tools.ietf.org/wg/tictoc/draft-ietf-tictoc-ptp-mib/"
            target="_blank">http://tools.ietf.org/wg/tictoc/draft-ietf-tictoc-ptp-mib/</a><br>
          <br>
          The feeling in the room was that this was an acceptable
          change. This<br>
          email is to confirm that decision and to solicit comments or
          concerns<br>
          from the mailing list.<br>
          <br>
          Regards,<br>
          Karen<br>
          <br>
          <br>
          _______________________________________________<br>
          TICTOC mailing list<br>
          <a moz-do-not-send="true" href="mailto:TICTOC@ietf.org">TICTOC@ietf.org</a><br>
          <a moz-do-not-send="true"
            href="https://www.ietf.org/mailman/listinfo/tictoc"
            target="_blank">https://www.ietf.org/mailman/listinfo/tictoc</a><br>
          _______________________________________________<br>
          TICTOC mailing list<br>
          <a moz-do-not-send="true" href="mailto:TICTOC@ietf.org">TICTOC@ietf.org</a><br>
          <a moz-do-not-send="true"
            href="https://www.ietf.org/mailman/listinfo/tictoc"
            target="_blank">https://www.ietf.org/mailman/listinfo/tictoc</a><br>
        </blockquote>
      </div>
      <br>
      <br>
      <fieldset class="mimeAttachmentHeader"></fieldset>
      <br>
      <pre wrap="">_______________________________________________
TICTOC mailing list
<a class="moz-txt-link-abbreviated" href="mailto:TICTOC@ietf.org">TICTOC@ietf.org</a>
<a class="moz-txt-link-freetext" href="https://www.ietf.org/mailman/listinfo/tictoc">https://www.ietf.org/mailman/listinfo/tictoc</a>
</pre>
    </blockquote>
    <br>
  </body>
</html>

--------------040903040100070906010307--

From kevin.gross@avanw.com  Fri Nov 16 15:02:20 2012
Return-Path: <kevin.gross@avanw.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 E59F421F8525 for <tictoc@ietfa.amsl.com>; Fri, 16 Nov 2012 15:02:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.384
X-Spam-Level: *
X-Spam-Status: No, score=1.384 tagged_above=-999 required=5 tests=[AWL=-0.693,  BAYES_00=-2.599, FH_HOST_EQ_D_D_D_D=0.765, FH_HOST_EQ_D_D_D_DB=0.888,  FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, MANGLED_SHOP=2.3, RDNS_DYNAMIC=0.1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id IIvfJGk5W3ZR for <tictoc@ietfa.amsl.com>; Fri, 16 Nov 2012 15:02:20 -0800 (PST)
Received: from oproxy12-pub.bluehost.com (50-87-16-10.unifiedlayer.com [50.87.16.10]) by ietfa.amsl.com (Postfix) with SMTP id CF77321F8514 for <TICTOC@ietf.org>; Fri, 16 Nov 2012 15:02:16 -0800 (PST)
Received: (qmail 7232 invoked by uid 0); 16 Nov 2012 23:01:54 -0000
Received: from unknown (HELO host291.hostmonster.com) (74.220.215.91) by oproxy12.bluehost.com with SMTP; 16 Nov 2012 23:01:53 -0000
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=avanw.com; s=default;  h=Content-Type:To:From:Subject:Message-ID:Date:MIME-Version; bh=Vl7GUyMyeTS9dhDpP7JhITwn4BCEoaGXxinqXZZzOJg=;  b=ae/8PqV6dzleBeDIjWyQrrHayympladYfeQw8txVHLGpaEEsO91gPaCH0AxMRMd1Qr+ADgXEimXAxb1zyaCeK1Oa1emfXrIfdwiEbFW/g/NHZ6bSsD2xyR7sLfsyPFKW;
Received: from [209.85.215.172] (port=47675 helo=mail-ea0-f172.google.com) by host291.hostmonster.com with esmtpsa (TLSv1:RC4-SHA:128) (Exim 4.76) (envelope-from <kevin.gross@avanw.com>) id 1TZUv3-0001W4-H4 for TICTOC@ietf.org; Fri, 16 Nov 2012 16:01:53 -0700
Received: by mail-ea0-f172.google.com with SMTP id a1so525350eaa.31 for <TICTOC@ietf.org>; Fri, 16 Nov 2012 15:01:52 -0800 (PST)
MIME-Version: 1.0
Received: by 10.14.213.7 with SMTP id z7mr1369024eeo.39.1353106912094; Fri, 16 Nov 2012 15:01:52 -0800 (PST)
Received: by 10.223.152.201 with HTTP; Fri, 16 Nov 2012 15:01:51 -0800 (PST)
Date: Fri, 16 Nov 2012 16:01:51 -0700
Message-ID: <CALw1_Q0zi7jZGzwESQGfrgOH_+CwgkCfSZZ7yAhQGL1ZhxLcjA@mail.gmail.com>
From: Kevin Gross <kevin.gross@avanw.com>
To: "TICTOC@ietf.org" <TICTOC@ietf.org>
Content-Type: multipart/alternative; boundary=047d7b603bb0d6a8ba04cea4c0b4
X-Identified-User: {1416:host291.hostmonster.com:avanwcom:avanw.com} {sentby:smtp auth 209.85.215.172 authed with kevin.gross@avanw.com}
Subject: [TICTOC] Comments on draft-ietf-tictoc-security-requirements-03
X-BeenThere: tictoc@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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, 16 Nov 2012 23:02:21 -0000

--047d7b603bb0d6a8ba04cea4c0b4
Content-Type: text/plain; charset=ISO-8859-1

Thanks for putting this draft together. I found it to be well written, well
organized and very informative. I have some comments.

General:

Use MITM acronym defined in 2.2 instead of spelling it out many times

By sections:

1 - Add playback to the list of attacks when synchronization is compromised.

1 - s/The IEEE 1588 includes/IEEE 1588 includes/

1 - Provide definition or example for "packet timing deployments"

2.1 - s/"protocol packets" is refers/"protocol packets" refers/

3.1 - s/documents/document/

3.1.1 - Authentication and encryption can be used together. s/by an
encryption or an authentication mechanism./by an encryption or an
authentication mechanism or both.

3.1.2 - s/eavesdrop to protocol/eavesdrop on protocol/

3.2 - Other threats to consider:
Rogue transparent clock. A remedy is discussed in 4.1.4 but it is not
documented as a threat.
Rogue boundary clock
Unauthorized receipt

3.2.9 - s/spoof the GPS satellites/spoof GPS satellite signals/

3.3 s/Attacket/Attacker/

Table 1 - Add a couple +'s:
Replay attack can be perpetrated by an external injector
Packet delay manipulation can cause accuracy degradation

4 - Add references for IPsec and MACsec

4.1.4 - Discuss TC authentication can prevent rogue TC from degrading
accuracy. Mention that this whole section is not applicable to NTP.

4.1.5 - Repeats discussion in 4.1. These two sections should at least
acknowledge each other.

4.1.5 - s/prevent malicious master/prevent rogue master/

4.2 - s/ensures the authenticity and completeness/ensures the integrity and
completeness/

4.2.1.1 - s/Hop by Hop Integrity Protection/Hop-by-Hop Integrity Protection

4.2.1.1 - s/allows malicious TCs/allows rogue TCs/

4.2.1.1 - a/End to End Integrity Protection/End-to-End Integrity Protection/

4.3 - I guess depends on the scope of these recommendations but I don't
think is it feasible to require DoS protection. Also, you don't protect a
protocol from DoS you protect a device or a service. We SHOULD be
protecting the device and its network stack from DoS. Or the device and its
network interface MUST recover once a DoS has resolved.

4.4 - "MUST be resistant" is not a well-defined requirement

4.4 - This section is missing a Discussion sub-section

4.5.3 - This section is missing a Discussion sub-section

4.6 - "SHOULD be relatively lightweight" is not a well-defined requirement.
Suggestion: "SHOULD minimize computational load".

4.6 - "SHOULD not require excessive storage" is not a well-defined
requirement. Suggestion: "SHOULD minimize storage requirements".

4.6 - Move "as client restrictions often dictate a low processing and
memory footprint, and    because the server may have extensive fan-out."
from requirements to discussion sub-section

4.7 - s/against packet delay attacks/against packet delay, manipulation and
interception and removal attacks/

4.9 - s/a gradual process/incremental deployment/

6.1 - No packets are required to be modified on reception. The requirement
is to record and associate an arrival timestamp with received packets.
Remove discussion of reception modifications. Suggested modified text:

   Time synchronization protocols often require protocol packets to be
   modified during transmission. Both NTP and PTP in one-
   step mode require clocks to modify protocol packets with the time of
   transmission.

   In the presence of a security mechanism, whether encryption or
   integrity protection:

   o During transmission the security protocol must be applied after
      integrating the timestamp into the packet.

   To allow high accuracy, timestamping is typically performed as close
   to the transmission time as possible. However, since the
   security engine must be placed between the timestamping function and
   the physical interface, it may introduce non-
   deterministic latency that causes accuracy degradation. These
   performance aspects have been analyzed in the literature, e.g., in
   [1588IPsec] and [Tunnel].

6.2 - Two-step pertains only to transmission times. Suggested modified text:

   PTP supports a two-step mode of operation, where the time of
   transmission of protocol packets are
   communicated without modifying the packets. As opposed to one-step mode,
   two step timestamping can be performed without the requirement to
encrypt after timestamping.

6.5 - Discuss bootstrapping issue. You need a certificate to receive time.
You need time to validate a certificate.


Kevin Gross
+1-303-447-0517
Media Network Consultant
AVA Networks - www.AVAnw.com, www.X192.org

--047d7b603bb0d6a8ba04cea4c0b4
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div><div>Thanks for putting this draft together. I found it to be well wri=
tten, well organized and very informative. I have some comments.</div><div>=
<br></div><div>General:</div><div><br></div><div>Use MITM acronym defined i=
n 2.2 instead of spelling it out many times</div>
<div><br></div><div>By sections:</div><div><br></div><div>1 - Add playback =
to the list of attacks when synchronization is compromised.</div><div><br><=
/div><div>1 - s/The IEEE 1588 includes/IEEE 1588 includes/</div><div><br>
</div><div>1 - Provide definition or example for &quot;packet timing deploy=
ments&quot;</div><div><br></div><div>2.1 - s/&quot;protocol packets&quot; i=
s refers/&quot;protocol packets&quot; refers/</div><div><br></div><div>
3.1 - s/documents/document/</div><div><br></div><div>3.1.1 - Authentication=
 and encryption can be used together. s/by an encryption or an authenticati=
on mechanism./by an encryption or an authentication mechanism or both.</div=
>
<div><br></div><div>3.1.2 - s/eavesdrop to protocol/eavesdrop on protocol/<=
/div><div><br></div><div>3.2 - Other threats to consider:</div><div><span c=
lass=3D"" style=3D"white-space:pre">	</span>Rogue transparent clock. A reme=
dy is discussed in 4.1.4 but it is not documented as a threat.</div>
<div><span class=3D"" style=3D"white-space:pre">	</span>Rogue boundary cloc=
k</div><div><span class=3D"" style=3D"white-space:pre">	</span>Unauthorized=
 receipt</div><div><br></div><div>3.2.9 - s/spoof the GPS satellites/spoof =
GPS satellite signals/</div>
<div><br></div><div>3.3 s/Attacket/Attacker/</div><div><br></div><div>Table=
 1 - Add a couple +&#39;s:=A0</div><div><span class=3D"" style=3D"white-spa=
ce:pre">	</span>Replay attack can be perpetrated by an external injector</d=
iv>
<div><span class=3D"" style=3D"white-space:pre">	</span>Packet delay manipu=
lation can cause accuracy degradation</div><div><br></div><div>4 - Add refe=
rences for IPsec and MACsec</div><div><br></div><div>4.1.4 - Discuss TC aut=
hentication can prevent rogue TC from degrading accuracy. Mention that this=
 whole section is not applicable to NTP.</div>
<div><br></div><div>4.1.5 - Repeats discussion in 4.1. These two sections s=
hould at least acknowledge each other.</div><div><br></div><div>4.1.5 - s/p=
revent malicious master/prevent rogue master/</div><div><br></div><div>
4.2 - s/ensures the authenticity and completeness/ensures the integrity and=
 completeness/</div><div><br></div><div>4.2.1.1 - s/Hop by Hop Integrity Pr=
otection/Hop-by-Hop Integrity Protection</div><div><br></div><div>4.2.1.1 -=
 s/allows malicious TCs/allows rogue TCs/</div>
<div><br></div><div>4.2.1.1 - a/End to End Integrity Protection/End-to-End =
Integrity Protection/</div><div><br></div><div>4.3 - I guess depends on the=
 scope of these recommendations but I don&#39;t think is it feasible to req=
uire DoS protection. Also, you don&#39;t protect a protocol from DoS you pr=
otect a device or a service. We SHOULD be protecting the device and its net=
work stack from DoS. Or the device and its network interface MUST recover o=
nce a DoS has resolved.</div>
<div><br></div><div>4.4 - &quot;MUST be resistant&quot; is not a well-defin=
ed requirement</div><div><br></div><div>4.4 - This section is missing a Dis=
cussion sub-section</div><div><br></div><div>4.5.3 - This section is missin=
g a Discussion sub-section</div>
<div><br></div><div>4.6 - &quot;SHOULD be relatively lightweight&quot; is n=
ot a well-defined requirement. Suggestion: &quot;SHOULD minimize computatio=
nal load&quot;.</div><div><br></div><div>4.6 - &quot;SHOULD not require exc=
essive storage&quot; is not a well-defined requirement. Suggestion: &quot;S=
HOULD minimize storage requirements&quot;.</div>
<div><br></div><div>4.6 - Move &quot;as client restrictions often dictate a=
 low processing and memory footprint, and =A0 =A0because the server may hav=
e extensive fan-out.&quot; from requirements to discussion sub-section</div=
>
<div><br></div><div>4.7 - s/against packet delay attacks/against packet del=
ay, manipulation and interception and removal attacks/</div><div><br></div>=
<div>4.9 - s/a gradual process/incremental deployment/</div><div><br></div>
<div>6.1 - No packets are required to be modified on reception. The require=
ment is to record and associate an arrival timestamp with received packets.=
 Remove discussion of reception modifications. Suggested modified text:</di=
v>
<div><br></div><div>=A0 =A0Time synchronization protocols often require pro=
tocol packets to be</div><div>=A0 =A0modified during transmission. Both NTP=
 and PTP in one-</div><div>=A0 =A0step mode require clocks to modify protoc=
ol packets with the time of</div>
<div>=A0 =A0transmission.</div><div><br></div><div>=A0 =A0In the presence o=
f a security mechanism, whether encryption or</div><div>=A0 =A0integrity pr=
otection:</div><div><br></div><div>=A0 =A0o During transmission the securit=
y protocol must be applied after</div>
<div>=A0 =A0 =A0 integrating the timestamp into the packet.</div><div><br><=
/div><div>=A0 =A0To allow high accuracy, timestamping is typically performe=
d as close</div><div>=A0 =A0to the transmission time as possible. However, =
since the</div>
<div>=A0 =A0security engine must be placed between the timestamping functio=
n and</div><div>=A0 =A0the physical interface, it may introduce non-</div><=
div>=A0 =A0deterministic latency that causes accuracy degradation. These</d=
iv><div>
=A0 =A0performance aspects have been analyzed in the literature, e.g., in</=
div><div>=A0 =A0[1588IPsec] and [Tunnel].</div><div><br></div><div>6.2 - Tw=
o-step pertains only to transmission times. Suggested modified text:</div><=
div>
<br></div><div>=A0 =A0PTP supports a two-step mode of operation, where the =
time of</div><div>=A0 =A0transmission of protocol packets are</div><div>=A0=
 =A0communicated without modifying the packets. As opposed to one-step mode=
,</div><div>
=A0 =A0two step timestamping can be performed without the requirement to en=
crypt after timestamping.</div><div>=A0 =A0</div><div>6.5 - Discuss bootstr=
apping issue. You need a certificate to receive time. You need time to vali=
date a certificate.</div>
<div><br></div><div><br></div><div>Kevin Gross</div><div>+1-303-447-0517</d=
iv><div>Media Network Consultant</div><div>AVA Networks - <a href=3D"http:/=
/www.AVAnw.com">www.AVAnw.com</a>, <a href=3D"http://www.X192.org">www.X192=
.org</a></div>
</div><div><br></div>

--047d7b603bb0d6a8ba04cea4c0b4--

From talmi@marvell.com  Wed Nov 21 23:32:31 2012
Return-Path: <talmi@marvell.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 102E221F87A4 for <tictoc@ietfa.amsl.com>; Wed, 21 Nov 2012 23:32:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.909
X-Spam-Level: 
X-Spam-Status: No, score=-3.909 tagged_above=-999 required=5 tests=[AWL=0.689,  BAYES_00=-2.599, GB_I_LETTER=-2, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4hHmqv-qoj47 for <tictoc@ietfa.amsl.com>; Wed, 21 Nov 2012 23:32:27 -0800 (PST)
Received: from galiil.marvell.com (galiil.marvell.com [199.203.130.254]) by ietfa.amsl.com (Postfix) with ESMTP id C89D921F879C for <tictoc@ietf.org>; Wed, 21 Nov 2012 23:32:24 -0800 (PST)
From: Tal Mizrahi <talmi@marvell.com>
To: "tictoc@ietf.org" <tictoc@ietf.org>
Date: Thu, 22 Nov 2012 09:32:22 +0200
Thread-Topic: Comments about draft-ietf-tictoc-1588overmpls-03
Thread-Index: Ac3IdxhWO8MVLCnHQeK3HNfzL5bq4g==
Message-ID: <74470498B659FA4687F0B0018C19A89C01A0F8F40896@IL-MB01.marvell.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: multipart/alternative; boundary="_000_74470498B659FA4687F0B0018C19A89C01A0F8F40896ILMB01marve_"
MIME-Version: 1.0
Subject: [TICTOC] Comments about draft-ietf-tictoc-1588overmpls-03
X-BeenThere: tictoc@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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, 22 Nov 2012 07:32:31 -0000

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

Hi,

I believe this document is very important and valuable.
I believe there are a few issues that need to be clarified and further expl=
ained, as detailed below.


Major Issues:
------------------

1.       Some more details about the deployment scenarios are necessary (es=
pecially in Section 4 and Section 18). For example, it is important to expl=
ain whether the LER can serve multiple customers. If the MPLS cloud (mainta=
ined by a service provider) provides timing services to multiple customers,=
 this document must discuss the fact that LER BCs need to interact with mul=
tiple grandmasters, and consequently multiple time references. Similarly, i=
f LSR TCs are syntonized to the master, it implies that they need to choose=
 one master to syntonize to.


2.       Figure 1 and Figure 2 describe point-to-point scenarios, but it is=
 important to clarify also point-to-multipoint scenarios, when there are mo=
re than two LER BCs. For example, is it assumed that there is a full-mesh o=
f timing LSPs between all LER BCs?


3.       More specifically, I could not find a discussion in the document a=
bout how PTP multicast event messages are distributed over the timing LSP. =
Maybe it is implicitly assumed that event messages are sent as unicast? A d=
iscussion about this issue is essential.


4.       In PTP the BMC algorithm is based on multicast Announce messages, =
which allow master election, and allow the slaves to discover the master. I=
t is important to add some description about how Announce messages are dist=
ributed in the architecture proposed by this document.


5.       The IEEE 1588 uses the term "port". Each PTP "port" has a state, w=
hich can be master, slave, or passive. The state is determined according to=
 the BMC algorithm. The BMC algorithm determines whether a port is a slave =
or a master based on the announce messages received through this port.
In the current draft, I assume a "port" is in fact defined by a specific ti=
ming LSP (corresponding to a specific peer BC/OC), and the set of Announce =
messages received through it. This implies that Announce messages must eith=
er be sent through the timing LSP, or somehow be traceable to a specific ti=
ming LSP. This must be well defined in the document to allow consistent imp=
lementations.


6.       Section 19 currently suggests a few possible solutions. It is impo=
rtant that this document will define a single solution.



7.       "Such peer delay measurement messages SHALL NOT use the Timing LSP=
 that runs between two LERs." --> This statement is problematic. It appears=
 you have to use the timing LSP for peer-delay messages, since you want the=
 PDelay_Resp to use the same path as Sync messages, to guarantee that the p=
acket is subject to the same path delay in both cases.



8.       A P2P TCs sends PDelay_Req messages to its adjacent clock. However=
, since TCs do not distribute Announce messages, a TC does not necessarily =
know who its adjacent TCs are. This is why PDelay_Req is usually sent as mu=
lticast (e.g. in 802.1AS).
in PTP over MPLS, I am guessing that the TC must maintain a list of all the=
 "neighbors" it needs to send a PDelay_Req to, each "neighbor" correspondin=
g to a timing label. The current document must explain how the TC sends a P=
Delay_Req (unicast / multicast? To whom?).



9.       Security considerations:

-          If the MPLS network (provider network) serves multiple customers=
, it is important to analyze the cross-customer effects. For example:

o   If an LER  BC is synchronized to a specific grandmaster, belonging to c=
ustomer A, then customer A can attack other customers by manipulating its t=
ime.

o   Similarly for a TC that is syntonized to a specfici customer.

-          The document must discuss the fact that customer timing messages=
 (as opposed to "regular" customer data) cannot be encrypted or authenticat=
ed on an end-to-end basis.

o   Alternatively, authentication/integrity verification mechanism can be u=
sed by a shared secret between the customer and provider nodes.



10.   Section 18.1 must include more details about the issues listed above =
(Announce message distribution, PDelay_Req message transmission, etc.).


Less major Issues:
-----------------------


11.   Some terms in the document are used inconsistently, for example, the =
terms "time-stamping" and "timestamping" are used intermittently.


12.   There is some inconsistency about capitalization, for example, the wo=
rd "Timing" is sometimes capitalized and sometimes not. Since you are using=
 the term "Timing messages" quite often, I would suggest to add it to the t=
erminology section, and to be consistent about its capitalization, whereas =
if the word "timing" is used on its own lowercase letters would be more app=
ropriate.


13.   Section 1:
"Annex F of  [IEEE- 1588]" --> "Annex F of  [IEEE]"


14.   "...NTP messages for clock and time synchronization.  The PTP..." -->=
 "...NTP messages for clock and time synchronization. The NTP..."


15.   It appears that some of the sections are only applicable to PTP (e.g.=
, Section 4, Section 18, Section 19). That is reasonable, but it should be =
pointed out explicitly that these sections apply only to PTP.


16.   Section 4:
"Transparent clocks do not terminate the Timing messages but they do
   modify the contents of the Timing messages as they transit across the
   transparent clock"
   -->  This is not true for P2P transparent clocks.


17.Section 7:
"For example the following PTP messages (called Event messages) require tim=
e-stamping, while other Non-Event PTP messages do not need time-stamping.  =
 o  Announce"
  --> Announce is not an event message, so it should be excluded from this =
list.


18.Section 7:
"and PDELAY_RESP_FOLLOW_UP messages must..." --> "and PDELAY_RESP_FOLLOW_UP=
 messages MUST..."


19.Section 12:
"IIn order to manage Timing LSPs" --> "In order to monitor timing LSPs" (OA=
M protocols monitor connections, rather than manage them).


20.Section 15:
It would be worth to mention that IPv6 zero checksum may be used, and quote=
 draft-ietf-6man-udpzero.


Tal.


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

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40"><head><meta http-equiv=3DContent-Type content=
=3D"text/html; charset=3Dus-ascii"><meta name=3DGenerator content=3D"Micros=
oft Word 14 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:Wingdings;
	panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
	{font-family:Wingdings;
	panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
pre
	{mso-style-priority:99;
	mso-style-link:"HTML Preformatted Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Courier New";}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
	{mso-style-priority:34;
	margin-top:0in;
	margin-right:0in;
	margin-bottom:0in;
	margin-left:.5in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.HTMLPreformattedChar
	{mso-style-name:"HTML Preformatted Char";
	mso-style-priority:99;
	mso-style-link:"HTML Preformatted";
	font-family:"Courier New";}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri","sans-serif";}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;}
div.WordSection1
	{page:WordSection1;}
/* List Definitions */
@list l0
	{mso-list-id:24213193;
	mso-list-type:hybrid;
	mso-list-template-ids:-374540322 67698703 67698713 67698715 67698703 67698=
713 67698715 67698703 67698713 67698715;}
@list l0:level1
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level2
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level3
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l0:level4
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level5
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level6
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l0:level7
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level8
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level9
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l1
	{mso-list-id:1784109923;
	mso-list-type:hybrid;
	mso-list-template-ids:-1873269566 -1315538808 67698691 67698693 67698689 6=
7698691 67698693 67698689 67698691 67698693;}
@list l1:level1
	{mso-level-start-at:19;
	mso-level-number-format:bullet;
	mso-level-text:-;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	margin-left:.75in;
	text-indent:-.25in;
	font-family:"Calibri","sans-serif";
	mso-fareast-font-family:Calibri;}
@list l1:level2
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	margin-left:1.25in;
	text-indent:-.25in;
	font-family:"Courier New";}
@list l1:level3
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	margin-left:1.75in;
	text-indent:-.25in;
	font-family:Wingdings;}
@list l1:level4
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	margin-left:2.25in;
	text-indent:-.25in;
	font-family:Symbol;}
@list l1:level5
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	margin-left:2.75in;
	text-indent:-.25in;
	font-family:"Courier New";}
@list l1:level6
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	margin-left:3.25in;
	text-indent:-.25in;
	font-family:Wingdings;}
@list l1:level7
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	margin-left:3.75in;
	text-indent:-.25in;
	font-family:Symbol;}
@list l1:level8
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	margin-left:4.25in;
	text-indent:-.25in;
	font-family:"Courier New";}
@list l1:level9
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	margin-left:4.75in;
	text-indent:-.25in;
	font-family:Wingdings;}
ol
	{margin-bottom:0in;}
ul
	{margin-bottom:0in;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DEN-US link=3Dblue vli=
nk=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal>Hi,<o:p></o:p></=
p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal>I believe =
this document is very important and valuable. <o:p></o:p></p><p class=3DMso=
Normal>I believe there are a few issues that need to be clarified and furth=
er explained, as detailed below.<o:p></o:p></p><p class=3DMsoNormal><o:p>&n=
bsp;</o:p></p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNorma=
l>Major Issues:<o:p></o:p></p><p class=3DMsoNormal>------------------<o:p><=
/o:p></p><p class=3DMsoListParagraph style=3D'text-indent:-.25in;mso-list:l=
0 level1 lfo1'><![if !supportLists]><span style=3D'mso-list:Ignore'>1.<span=
 style=3D'font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
; </span></span><![endif]><span dir=3DLTR></span>Some more details about th=
e deployment scenarios are necessary (especially in Section 4 and Section 1=
8). For example, it is important to explain whether the LER can serve multi=
ple customers. If the MPLS cloud (maintained by a service provider) provide=
s timing services to multiple customers, this document must discuss the fac=
t that LER BCs need to interact with multiple grandmasters, and consequentl=
y multiple time references. Similarly, if LSR TCs are syntonized to the mas=
ter, it implies that they need to choose one master to syntonize to.<o:p></=
o:p></p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoListParagra=
ph style=3D'text-indent:-.25in;mso-list:l0 level1 lfo1'><![if !supportLists=
]><span style=3D'mso-list:Ignore'>2.<span style=3D'font:7.0pt "Times New Ro=
man"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span></span><![endif]><span di=
r=3DLTR></span>Figure 1 and Figure 2 describe point-to-point scenarios, but=
 it is important to clarify also point-to-multipoint scenarios, when there =
are more than two LER BCs. For example, is it assumed that there is a full-=
mesh of timing LSPs between all LER BCs?<o:p></o:p></p><p class=3DMsoNormal=
><o:p>&nbsp;</o:p></p><p class=3DMsoListParagraph style=3D'text-indent:-.25=
in;mso-list:l0 level1 lfo1'><![if !supportLists]><span style=3D'mso-list:Ig=
nore'>3.<span style=3D'font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp; </span></span><![endif]><span dir=3DLTR></span>More specific=
ally, I could not find a discussion in the document about how PTP multicast=
 event messages are distributed over the timing LSP. Maybe it is implicitly=
 assumed that event messages are sent as unicast? A discussion about this i=
ssue is essential.<o:p></o:p></p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p>=
<p class=3DMsoListParagraph style=3D'text-indent:-.25in;mso-list:l0 level1 =
lfo1'><![if !supportLists]><span style=3D'mso-list:Ignore'>4.<span style=3D=
'font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span>=
</span><![endif]><span dir=3DLTR></span>In PTP the BMC algorithm is based o=
n multicast Announce messages, which allow master election, and allow the s=
laves to discover the master. It is important to add some description about=
 how Announce messages are distributed in the architecture proposed by this=
 document.<o:p></o:p></p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=
=3DMsoListParagraph style=3D'text-indent:-.25in;mso-list:l0 level1 lfo1'><!=
[if !supportLists]><span style=3D'mso-list:Ignore'>5.<span style=3D'font:7.=
0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span></span><=
![endif]><span dir=3DLTR></span>The IEEE 1588 uses the term &#8220;port&#82=
21;. Each PTP &#8220;port&#8221; has a state, which can be master, slave, o=
r passive. The state is determined according to the BMC algorithm. The BMC =
algorithm determines whether a port is a slave or a master based on the ann=
ounce messages received through this port. <br>In the current draft, I assu=
me a &#8220;port&#8221; is in fact defined by a specific timing LSP (corres=
ponding to a specific peer BC/OC), and the set of Announce messages receive=
d through it. This implies that Announce messages must either be sent throu=
gh the timing LSP, or somehow be traceable to a specific timing LSP. This m=
ust be well defined in the document to allow consistent implementations.<o:=
p></o:p></p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoListPar=
agraph style=3D'text-indent:-.25in;mso-list:l0 level1 lfo1'><![if !supportL=
ists]><span style=3D'mso-list:Ignore'>6.<span style=3D'font:7.0pt "Times Ne=
w Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span></span><![endif]><spa=
n dir=3DLTR></span>Section 19 currently suggests a few possible solutions. =
It is important that this document will define a single solution.<o:p></o:p=
></p><p class=3DMsoListParagraph><o:p>&nbsp;</o:p></p><p class=3DMsoListPar=
agraph style=3D'text-indent:-.25in;mso-list:l0 level1 lfo1'><![if !supportL=
ists]><span style=3D'mso-list:Ignore'>7.<span style=3D'font:7.0pt "Times Ne=
w Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span></span><![endif]><spa=
n dir=3DLTR></span>&#8220;Such peer delay measurement messages SHALL NOT us=
e the Timing LSP that runs between two LERs.&#8221; --&gt; This statement i=
s problematic. It appears you have to use the timing LSP for peer-delay mes=
sages, since you want the PDelay_Resp to use the same path as Sync messages=
, to guarantee that the packet is subject to the same path delay in both ca=
ses.<o:p></o:p></p><p class=3DMsoListParagraph><o:p>&nbsp;</o:p></p><p clas=
s=3DMsoListParagraph style=3D'text-indent:-.25in;mso-list:l0 level1 lfo1'><=
![if !supportLists]><span style=3D'mso-list:Ignore'>8.<span style=3D'font:7=
.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span></span>=
<![endif]><span dir=3DLTR></span>A P2P TCs sends PDelay_Req messages to its=
 adjacent clock. However, since TCs do not distribute Announce messages, a =
TC does not necessarily know who its adjacent TCs are. This is why PDelay_R=
eq is usually sent as multicast (e.g. in 802.1AS). <br>in PTP over MPLS, I =
am guessing that the TC must maintain a list of all the &#8220;neighbors&#8=
221; it needs to send a PDelay_Req to, each &#8220;neighbor&#8221; correspo=
nding to a timing label. The current document must explain how the TC sends=
 a PDelay_Req (unicast / multicast? To whom?).<o:p></o:p></p><p class=3DMso=
ListParagraph><o:p>&nbsp;</o:p></p><p class=3DMsoListParagraph style=3D'tex=
t-indent:-.25in;mso-list:l0 level1 lfo1'><![if !supportLists]><span style=
=3D'mso-list:Ignore'>9.<span style=3D'font:7.0pt "Times New Roman"'>&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span></span><![endif]><span dir=3DLTR></spa=
n>Security considerations: <o:p></o:p></p><p class=3DMsoListParagraph style=
=3D'margin-left:.75in;text-indent:-.25in;mso-list:l1 level1 lfo2'><![if !su=
pportLists]><span style=3D'mso-list:Ignore'>-<span style=3D'font:7.0pt "Tim=
es New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </spa=
n></span><![endif]><span dir=3DLTR></span>If the MPLS network (provider net=
work) serves multiple customers, it is important to analyze the cross-custo=
mer effects. For example:<o:p></o:p></p><p class=3DMsoListParagraph style=
=3D'margin-left:1.25in;text-indent:-.25in;mso-list:l1 level2 lfo2'><![if !s=
upportLists]><span style=3D'font-family:"Courier New"'><span style=3D'mso-l=
ist:Ignore'>o<span style=3D'font:7.0pt "Times New Roman"'>&nbsp;&nbsp; </sp=
an></span></span><![endif]><span dir=3DLTR></span>If an LER&nbsp; BC is syn=
chronized to a specific grandmaster, belonging to customer A, then customer=
 A can attack other customers by manipulating its time.<o:p></o:p></p><p cl=
ass=3DMsoListParagraph style=3D'margin-left:1.25in;text-indent:-.25in;mso-l=
ist:l1 level2 lfo2'><![if !supportLists]><span style=3D'font-family:"Courie=
r New"'><span style=3D'mso-list:Ignore'>o<span style=3D'font:7.0pt "Times N=
ew Roman"'>&nbsp;&nbsp; </span></span></span><![endif]><span dir=3DLTR></sp=
an>Similarly for a TC that is syntonized to a specfici customer.<o:p></o:p>=
</p><p class=3DMsoListParagraph style=3D'margin-left:.75in;text-indent:-.25=
in;mso-list:l1 level1 lfo2'><![if !supportLists]><span style=3D'mso-list:Ig=
nore'>-<span style=3D'font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span></span><![endif]><span dir=3DLTR></s=
pan>The document must discuss the fact that customer timing messages (as op=
posed to &#8220;regular&#8221; customer data) cannot be encrypted or authen=
ticated on an end-to-end basis.<o:p></o:p></p><p class=3DMsoListParagraph s=
tyle=3D'margin-left:1.25in;text-indent:-.25in;mso-list:l1 level2 lfo2'><![i=
f !supportLists]><span style=3D'font-family:"Courier New"'><span style=3D'm=
so-list:Ignore'>o<span style=3D'font:7.0pt "Times New Roman"'>&nbsp;&nbsp; =
</span></span></span><![endif]><span dir=3DLTR></span>Alternatively, authen=
tication/integrity verification mechanism can be used by a shared secret be=
tween the customer and provider nodes.<o:p></o:p></p><p class=3DMsoListPara=
graph style=3D'margin-left:.75in'><o:p>&nbsp;</o:p></p><p class=3DMsoListPa=
ragraph style=3D'text-indent:-.25in;mso-list:l0 level1 lfo1'><![if !support=
Lists]><span style=3D'mso-list:Ignore'>10.<span style=3D'font:7.0pt "Times =
New Roman"'>&nbsp;&nbsp; </span></span><![endif]><span dir=3DLTR></span>Sec=
tion 18.1 must include more details about the issues listed above (Announce=
 message distribution, PDelay_Req message transmission, etc.).<o:p></o:p></=
p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal><o:p>&nbsp=
;</o:p></p><p class=3DMsoNormal>Less major Issues:<o:p></o:p></p><p class=
=3DMsoNormal>-----------------------<o:p></o:p></p><p class=3DMsoNormal><o:=
p>&nbsp;</o:p></p><p class=3DMsoListParagraph style=3D'text-indent:-.25in;m=
so-list:l0 level1 lfo1'><![if !supportLists]><span style=3D'mso-list:Ignore=
'>11.<span style=3D'font:7.0pt "Times New Roman"'>&nbsp;&nbsp; </span></spa=
n><![endif]><span dir=3DLTR></span>Some terms in the document are used inco=
nsistently, for example, the terms &#8220;time-stamping&#8221; and &#8220;t=
imestamping&#8221; are used intermittently.<o:p></o:p></p><p class=3DMsoNor=
mal><o:p>&nbsp;</o:p></p><p class=3DMsoListParagraph style=3D'text-indent:-=
.25in;mso-list:l0 level1 lfo1'><![if !supportLists]><span style=3D'mso-list=
:Ignore'>12.<span style=3D'font:7.0pt "Times New Roman"'>&nbsp;&nbsp; </spa=
n></span><![endif]><span dir=3DLTR></span>There is some inconsistency about=
 capitalization, for example, the word &#8220;Timing&#8221; is sometimes ca=
pitalized and sometimes not. Since you are using the term &#8220;Timing mes=
sages&#8221; quite often, I would suggest to add it to the terminology sect=
ion, and to be consistent about its capitalization, whereas if the word &#8=
220;timing&#8221; is used on its own lowercase letters would be more approp=
riate.<o:p></o:p></p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DM=
soListParagraph style=3D'text-indent:-.25in;mso-list:l0 level1 lfo1'><![if =
!supportLists]><span style=3D'mso-list:Ignore'>13.<span style=3D'font:7.0pt=
 "Times New Roman"'>&nbsp;&nbsp; </span></span><![endif]><span dir=3DLTR></=
span>Section 1:<br>&#8220;Annex F of &nbsp;[IEEE- 1588]&#8221; --&gt; &#822=
0;Annex F of &nbsp;[IEEE]&#8221;<o:p></o:p></p><p class=3DMsoNormal><o:p>&n=
bsp;</o:p></p><p class=3DMsoListParagraph style=3D'text-indent:-.25in;mso-l=
ist:l0 level1 lfo1'><![if !supportLists]><span style=3D'mso-list:Ignore'>14=
.<span style=3D'font:7.0pt "Times New Roman"'>&nbsp;&nbsp; </span></span><!=
[endif]><span dir=3DLTR></span>&#8220;&#8230;NTP messages for clock and tim=
e synchronization. &nbsp;The PTP&#8230;&#8221; --&gt; &#8220;...NTP message=
s for clock and time synchronization. The NTP&#8230;&#8221;<o:p></o:p></p><=
p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoListParagraph style=
=3D'text-indent:-.25in;mso-list:l0 level1 lfo1'><![if !supportLists]><span =
style=3D'mso-list:Ignore'>15.<span style=3D'font:7.0pt "Times New Roman"'>&=
nbsp;&nbsp; </span></span><![endif]><span dir=3DLTR></span>It appears that =
some of the sections are only applicable to PTP (e.g., Section 4, Section 1=
8, Section 19). That is reasonable, but it should be pointed out explicitly=
 that these sections apply only to PTP.<br><br><o:p></o:p></p><p class=3DMs=
oListParagraph style=3D'text-indent:-.25in;mso-list:l0 level1 lfo1'><![if !=
supportLists]><span style=3D'mso-list:Ignore'>16.<span style=3D'font:7.0pt =
"Times New Roman"'>&nbsp;&nbsp; </span></span><![endif]><span dir=3DLTR></s=
pan>Section 4:<br> &#8220;Transparent clocks do not terminate the Timing me=
ssages but they do<br>&nbsp;&nbsp; modify the contents of the Timing messag=
es as they transit across the<br>&nbsp;&nbsp; transparent clock&#8221;<br>&=
nbsp;&nbsp; --&gt;&nbsp; This is not true for P2P transparent clocks.<o:p><=
/o:p></p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoListParagr=
aph style=3D'text-indent:-.25in;page-break-before:always;mso-list:l0 level1=
 lfo1'><![if !supportLists]><span lang=3DEN style=3D'font-size:10.0pt;font-=
family:"Courier New"'><span style=3D'mso-list:Ignore'>17.</span></span><![e=
ndif]><span dir=3DLTR></span>Section 7:<br><span lang=3DEN style=3D'font-si=
ze:10.0pt;font-family:"Courier New"'>&#8220;For example the following PTP m=
essages (called Event messages) require time-stamping, while other Non-Even=
t PTP messages do not need time-stamping.&nbsp;&nbsp; o&nbsp; Announce&#822=
1;<br>&nbsp; --&gt; Announce is not an event message, so it should be exclu=
ded from this list.<o:p></o:p></span></p><p class=3DMsoNormal style=3D'page=
-break-before:always'><span lang=3DEN style=3D'font-size:10.0pt;font-family=
:"Courier New"'><o:p>&nbsp;</o:p></span></p><p class=3DMsoListParagraph sty=
le=3D'text-indent:-.25in;page-break-before:always;mso-list:l0 level1 lfo1'>=
<![if !supportLists]><span lang=3DEN style=3D'font-size:10.0pt;font-family:=
"Courier New"'><span style=3D'mso-list:Ignore'>18.</span></span><![endif]><=
span dir=3DLTR></span>Section 7:<br><span style=3D'font-size:10.0pt;font-fa=
mily:"Courier New"'> <span lang=3DEN>&#8220;and PDELAY_RESP_FOLLOW_UP messa=
ges must...&#8221; --&gt; &#8220;and PDELAY_RESP_FOLLOW_UP messages MUST...=
&#8221;<o:p></o:p></span></span></p><p class=3DMsoNormal style=3D'page-brea=
k-before:always'><span lang=3DEN style=3D'font-size:10.0pt;font-family:"Cou=
rier New"'><o:p>&nbsp;</o:p></span></p><p class=3DMsoListParagraph style=3D=
'text-indent:-.25in;page-break-before:always;mso-list:l0 level1 lfo1'><![if=
 !supportLists]><span lang=3DEN style=3D'font-size:10.0pt;font-family:"Cour=
ier New"'><span style=3D'mso-list:Ignore'>19.</span></span><![endif]><span =
dir=3DLTR></span><span lang=3DEN style=3D'font-size:10.0pt;font-family:"Cou=
rier New"'>Section 12:<br>&#8220;IIn order to manage Timing LSPs&#8221; --&=
gt; &#8220;In order to monitor timing LSPs&#8221; (OAM protocols monitor co=
nnections, rather than manage them).<o:p></o:p></span></p><p class=3DMsoNor=
mal style=3D'page-break-before:always'><span lang=3DEN style=3D'font-size:1=
0.0pt;font-family:"Courier New"'><o:p>&nbsp;</o:p></span></p><p class=3DMso=
ListParagraph style=3D'text-indent:-.25in;page-break-before:always;mso-list=
:l0 level1 lfo1'><![if !supportLists]><span lang=3DEN style=3D'font-size:10=
.0pt;font-family:"Courier New"'><span style=3D'mso-list:Ignore'>20.</span><=
/span><![endif]><span dir=3DLTR></span><span lang=3DEN style=3D'font-size:1=
0.0pt;font-family:"Courier New"'>Section 15:<br>It would be worth to mentio=
n that IPv6 zero checksum may be used, and quote draft-ietf-6man-udpzero.<o=
:p></o:p></span></p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMs=
oNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal><span style=3D'font-size:=
10.0pt;font-family:"Arial","sans-serif"'>Tal.<o:p></o:p></span></p><p class=
=3DMsoNormal><o:p>&nbsp;</o:p></p></div></body></html>=

--_000_74470498B659FA4687F0B0018C19A89C01A0F8F40896ILMB01marve_--

From davari@broadcom.com  Sat Nov 24 08:29:53 2012
Return-Path: <davari@broadcom.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 AE44421F84F6 for <tictoc@ietfa.amsl.com>; Sat, 24 Nov 2012 08:29:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.478
X-Spam-Level: 
X-Spam-Status: No, score=-7.478 tagged_above=-999 required=5 tests=[AWL=1.120,  BAYES_00=-2.599, GB_I_LETTER=-2, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ayq1OYdw2Bz4 for <tictoc@ietfa.amsl.com>; Sat, 24 Nov 2012 08:29:52 -0800 (PST)
Received: from mms1.broadcom.com (mms1.broadcom.com [216.31.210.17]) by ietfa.amsl.com (Postfix) with ESMTP id 6BE9521F84DC for <tictoc@ietf.org>; Sat, 24 Nov 2012 08:29:52 -0800 (PST)
Received: from [10.16.192.232] by mms1.broadcom.com with ESMTP (Broadcom SMTP Relay (Email Firewall v6.5)); Sat, 24 Nov 2012 08:27:17 -0800
X-Server-Uuid: 06151B78-6688-425E-9DE2-57CB27892261
Received: from SJEXCHCAS02.corp.ad.broadcom.com (10.16.192.37) by SJEXCHHUB02.corp.ad.broadcom.com (10.16.192.232) with Microsoft SMTP Server (TLS) id 8.2.247.2; Sat, 24 Nov 2012 08:29:06 -0800
Received: from SJEXCHMB12.corp.ad.broadcom.com ( [fe80::bc15:c1e1:c29a:36f7]) by sjexchcas02.corp.ad.broadcom.com ( [::1]) with mapi id 14.01.0355.002; Sat, 24 Nov 2012 08:28:45 -0800
From: "Shahram Davari" <davari@broadcom.com>
To: "Tal Mizrahi" <talmi@marvell.com>
Thread-Topic: [TICTOC] Comments about draft-ietf-tictoc-1588overmpls-03
Thread-Index: AQHNymDGNSNmWHcU2EGufY0zhIouQA==
Date: Sat, 24 Nov 2012 16:28:45 +0000
Message-ID: <5D2C91F2-FE33-4CB9-BE10-0F96CBA9DC12@broadcom.com>
References: <74470498B659FA4687F0B0018C19A89C01A0F8F40896@IL-MB01.marvell.com>
In-Reply-To: <74470498B659FA4687F0B0018C19A89C01A0F8F40896@IL-MB01.marvell.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
MIME-Version: 1.0
X-WSS-ID: 7CAE2AEF1QK8578974-01-01
Content-Type: multipart/alternative; boundary=_000_5D2C91F2FE334CB9BE100F96CBA9DC12broadcomcom_
Cc: "tictoc@ietf.org" <tictoc@ietf.org>
Subject: Re: [TICTOC] Comments about draft-ietf-tictoc-1588overmpls-03
X-BeenThere: tictoc@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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, 24 Nov 2012 16:29:53 -0000

--_000_5D2C91F2FE334CB9BE100F96CBA9DC12broadcomcom_
Content-Type: text/plain;
 charset=windows-1252
Content-Transfer-Encoding: quoted-printable

Hi Tal,

Thanks for your extensive feedback. I will talk to you offline in how to im=
prove the draft. I will most likely need you to propose text and or figures=
.

Regards,
Shahram


On Nov 21, 2012, at 11:32 PM, "Tal Mizrahi" <talmi@marvell.com<mailto:talmi=
@marvell.com>> wrote:

Hi,

I believe this document is very important and valuable.
I believe there are a few issues that need to be clarified and further expl=
ained, as detailed below.


Major Issues:
------------------

1.       Some more details about the deployment scenarios are necessary (es=
pecially in Section 4 and Section 18). For example, it is important to expl=
ain whether the LER can serve multiple customers. If the MPLS cloud (mainta=
ined by a service provider) provides timing services to multiple customers,=
 this document must discuss the fact that LER BCs need to interact with mul=
tiple grandmasters, and consequently multiple time references. Similarly, i=
f LSR TCs are syntonized to the master, it implies that they need to choose=
 one master to syntonize to.


2.       Figure 1 and Figure 2 describe point-to-point scenarios, but it is=
 important to clarify also point-to-multipoint scenarios, when there are mo=
re than two LER BCs. For example, is it assumed that there is a full-mesh o=
f timing LSPs between all LER BCs?


3.       More specifically, I could not find a discussion in the document a=
bout how PTP multicast event messages are distributed over the timing LSP. =
Maybe it is implicitly assumed that event messages are sent as unicast? A d=
iscussion about this issue is essential.


4.       In PTP the BMC algorithm is based on multicast Announce messages, =
which allow master election, and allow the slaves to discover the master. I=
t is important to add some description about how Announce messages are dist=
ributed in the architecture proposed by this document.


5.       The IEEE 1588 uses the term =93port=94. Each PTP =93port=94 has a =
state, which can be master, slave, or passive. The state is determined acco=
rding to the BMC algorithm. The BMC algorithm determines whether a port is =
a slave or a master based on the announce messages received through this po=
rt.
In the current draft, I assume a =93port=94 is in fact defined by a specifi=
c timing LSP (corresponding to a specific peer BC/OC), and the set of Annou=
nce messages received through it. This implies that Announce messages must =
either be sent through the timing LSP, or somehow be traceable to a specifi=
c timing LSP. This must be well defined in the document to allow consistent=
 implementations.


6.       Section 19 currently suggests a few possible solutions. It is impo=
rtant that this document will define a single solution.



7.       =93Such peer delay measurement messages SHALL NOT use the Timing L=
SP that runs between two LERs.=94 --> This statement is problematic. It app=
ears you have to use the timing LSP for peer-delay messages, since you want=
 the PDelay_Resp to use the same path as Sync messages, to guarantee that t=
he packet is subject to the same path delay in both cases.



8.       A P2P TCs sends PDelay_Req messages to its adjacent clock. However=
, since TCs do not distribute Announce messages, a TC does not necessarily =
know who its adjacent TCs are. This is why PDelay_Req is usually sent as mu=
lticast (e.g. in 802.1AS).
in PTP over MPLS, I am guessing that the TC must maintain a list of all the=
 =93neighbors=94 it needs to send a PDelay_Req to, each =93neighbor=94 corr=
esponding to a timing label. The current document must explain how the TC s=
ends a PDelay_Req (unicast / multicast? To whom?).



9.       Security considerations:

-          If the MPLS network (provider network) serves multiple customers=
, it is important to analyze the cross-customer effects. For example:

o   If an LER  BC is synchronized to a specific grandmaster, belonging to c=
ustomer A, then customer A can attack other customers by manipulating its t=
ime.

o   Similarly for a TC that is syntonized to a specfici customer.

-          The document must discuss the fact that customer timing messages=
 (as opposed to =93regular=94 customer data) cannot be encrypted or authent=
icated on an end-to-end basis.

o   Alternatively, authentication/integrity verification mechanism can be u=
sed by a shared secret between the customer and provider nodes.



10.   Section 18.1 must include more details about the issues listed above =
(Announce message distribution, PDelay_Req message transmission, etc.).


Less major Issues:
-----------------------


11.   Some terms in the document are used inconsistently, for example, the =
terms =93time-stamping=94 and =93timestamping=94 are used intermittently.


12.   There is some inconsistency about capitalization, for example, the wo=
rd =93Timing=94 is sometimes capitalized and sometimes not. Since you are u=
sing the term =93Timing messages=94 quite often, I would suggest to add it =
to the terminology section, and to be consistent about its capitalization, =
whereas if the word =93timing=94 is used on its own lowercase letters would=
 be more appropriate.


13.   Section 1:
=93Annex F of  [IEEE- 1588]=94 --> =93Annex F of  [IEEE]=94


14.   =93=85NTP messages for clock and time synchronization.  The PTP=85=94=
 --> =93...NTP messages for clock and time synchronization. The NTP=85=94


15.   It appears that some of the sections are only applicable to PTP (e.g.=
, Section 4, Section 18, Section 19). That is reasonable, but it should be =
pointed out explicitly that these sections apply only to PTP.


16.   Section 4:
=93Transparent clocks do not terminate the Timing messages but they do
   modify the contents of the Timing messages as they transit across the
   transparent clock=94
   -->  This is not true for P2P transparent clocks.


17.Section 7:
=93For example the following PTP messages (called Event messages) require t=
ime-stamping, while other Non-Event PTP messages do not need time-stamping.=
   o  Announce=94
  --> Announce is not an event message, so it should be excluded from this =
list.


18.Section 7:
=93and PDELAY_RESP_FOLLOW_UP messages must...=94 --> =93and PDELAY_RESP_FOL=
LOW_UP messages MUST...=94


19.Section 12:
=93IIn order to manage Timing LSPs=94 --> =93In order to monitor timing LSP=
s=94 (OAM protocols monitor connections, rather than manage them).


20.Section 15:
It would be worth to mention that IPv6 zero checksum may be used, and quote=
 draft-ietf-6man-udpzero.


Tal.

_______________________________________________
TICTOC mailing list
TICTOC@ietf.org<mailto:TICTOC@ietf.org>
https://www.ietf.org/mailman/listinfo/tictoc

--_000_5D2C91F2FE334CB9BE100F96CBA9DC12broadcomcom_
Content-Type: text/html;
 charset=windows-1252
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3DWindows-1=
252">
</head>
<body dir=3D"auto">
<div>Hi Tal,</div>
<div><br>
</div>
<div>Thanks for your extensive feedback. I will talk to you offline in how =
to improve the draft. I will most likely need you to propose text and or fi=
gures.<br>
<br>
Regards,
<div>Shahram</div>
<div><br>
</div>
</div>
<div><br>
On Nov 21, 2012, at 11:32 PM, &quot;Tal Mizrahi&quot; &lt;<a href=3D"mailto=
:talmi@marvell.com">talmi@marvell.com</a>&gt; wrote:<br>
<br>
</div>
<blockquote type=3D"cite">
<div>
<meta name=3D"Generator" content=3D"Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:Wingdings;
	panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
	{font-family:Wingdings;
	panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
pre
	{mso-style-priority:99;
	mso-style-link:"HTML Preformatted Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Courier New";}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
	{mso-style-priority:34;
	margin-top:0in;
	margin-right:0in;
	margin-bottom:0in;
	margin-left:.5in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.HTMLPreformattedChar
	{mso-style-name:"HTML Preformatted Char";
	mso-style-priority:99;
	mso-style-link:"HTML Preformatted";
	font-family:"Courier New";}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri","sans-serif";}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;}
div.WordSection1
	{page:WordSection1;}
/* List Definitions */
@list l0
	{mso-list-id:24213193;
	mso-list-type:hybrid;
	mso-list-template-ids:-374540322 67698703 67698713 67698715 67698703 67698=
713 67698715 67698703 67698713 67698715;}
@list l0:level1
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level2
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level3
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l0:level4
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level5
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level6
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l0:level7
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level8
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level9
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l1
	{mso-list-id:1784109923;
	mso-list-type:hybrid;
	mso-list-template-ids:-1873269566 -1315538808 67698691 67698693 67698689 6=
7698691 67698693 67698689 67698691 67698693;}
@list l1:level1
	{mso-level-start-at:19;
	mso-level-number-format:bullet;
	mso-level-text:-;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	margin-left:.75in;
	text-indent:-.25in;
	font-family:"Calibri","sans-serif";
	mso-fareast-font-family:Calibri;}
@list l1:level2
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	margin-left:1.25in;
	text-indent:-.25in;
	font-family:"Courier New";}
@list l1:level3
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	margin-left:1.75in;
	text-indent:-.25in;
	font-family:Wingdings;}
@list l1:level4
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	margin-left:2.25in;
	text-indent:-.25in;
	font-family:Symbol;}
@list l1:level5
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	margin-left:2.75in;
	text-indent:-.25in;
	font-family:"Courier New";}
@list l1:level6
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	margin-left:3.25in;
	text-indent:-.25in;
	font-family:Wingdings;}
@list l1:level7
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	margin-left:3.75in;
	text-indent:-.25in;
	font-family:Symbol;}
@list l1:level8
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	margin-left:4.25in;
	text-indent:-.25in;
	font-family:"Courier New";}
@list l1:level9
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	margin-left:4.75in;
	text-indent:-.25in;
	font-family:Wingdings;}
ol
	{margin-bottom:0in;}
ul
	{margin-bottom:0in;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
<div class=3D"WordSection1">
<p class=3D"MsoNormal">Hi,<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">I believe this document is very important and valuab=
le. <o:p>
</o:p></p>
<p class=3D"MsoNormal">I believe there are a few issues that need to be cla=
rified and further explained, as detailed below.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Major Issues:<o:p></o:p></p>
<p class=3D"MsoNormal">------------------<o:p></o:p></p>
<p class=3D"MsoListParagraph" style=3D"text-indent:-.25in;mso-list:l0 level=
1 lfo1"><!--[if !supportLists]--><span style=3D"mso-list:Ignore">1.<span st=
yle=3D"font:7.0pt &quot;Times New Roman&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;
</span></span><!--[endif]--><span dir=3D"LTR"></span>Some more details abou=
t the deployment scenarios are necessary (especially in Section 4 and Secti=
on 18). For example, it is important to explain whether the LER can serve m=
ultiple customers. If the MPLS cloud
 (maintained by a service provider) provides timing services to multiple cu=
stomers, this document must discuss the fact that LER BCs need to interact =
with multiple grandmasters, and consequently multiple time references. Simi=
larly, if LSR TCs are syntonized
 to the master, it implies that they need to choose one master to syntonize=
 to.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoListParagraph" style=3D"text-indent:-.25in;mso-list:l0 level=
1 lfo1"><!--[if !supportLists]--><span style=3D"mso-list:Ignore">2.<span st=
yle=3D"font:7.0pt &quot;Times New Roman&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;
</span></span><!--[endif]--><span dir=3D"LTR"></span>Figure 1 and Figure 2 =
describe point-to-point scenarios, but it is important to clarify also poin=
t-to-multipoint scenarios, when there are more than two LER BCs. For exampl=
e, is it assumed that there is a full-mesh
 of timing LSPs between all LER BCs?<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoListParagraph" style=3D"text-indent:-.25in;mso-list:l0 level=
1 lfo1"><!--[if !supportLists]--><span style=3D"mso-list:Ignore">3.<span st=
yle=3D"font:7.0pt &quot;Times New Roman&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;
</span></span><!--[endif]--><span dir=3D"LTR"></span>More specifically, I c=
ould not find a discussion in the document about how PTP multicast event me=
ssages are distributed over the timing LSP. Maybe it is implicitly assumed =
that event messages are sent as unicast?
 A discussion about this issue is essential.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoListParagraph" style=3D"text-indent:-.25in;mso-list:l0 level=
1 lfo1"><!--[if !supportLists]--><span style=3D"mso-list:Ignore">4.<span st=
yle=3D"font:7.0pt &quot;Times New Roman&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;
</span></span><!--[endif]--><span dir=3D"LTR"></span>In PTP the BMC algorit=
hm is based on multicast Announce messages, which allow master election, an=
d allow the slaves to discover the master. It is important to add some desc=
ription about how Announce messages
 are distributed in the architecture proposed by this document.<o:p></o:p><=
/p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoListParagraph" style=3D"text-indent:-.25in;mso-list:l0 level=
1 lfo1"><!--[if !supportLists]--><span style=3D"mso-list:Ignore">5.<span st=
yle=3D"font:7.0pt &quot;Times New Roman&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;
</span></span><!--[endif]--><span dir=3D"LTR"></span>The IEEE 1588 uses the=
 term =93port=94. Each PTP =93port=94 has a state, which can be master, sla=
ve, or passive. The state is determined according to the BMC algorithm. The=
 BMC algorithm determines whether a port is
 a slave or a master based on the announce messages received through this p=
ort. <br>
In the current draft, I assume a =93port=94 is in fact defined by a specifi=
c timing LSP (corresponding to a specific peer BC/OC), and the set of Annou=
nce messages received through it. This implies that Announce messages must =
either be sent through the timing LSP,
 or somehow be traceable to a specific timing LSP. This must be well define=
d in the document to allow consistent implementations.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoListParagraph" style=3D"text-indent:-.25in;mso-list:l0 level=
1 lfo1"><!--[if !supportLists]--><span style=3D"mso-list:Ignore">6.<span st=
yle=3D"font:7.0pt &quot;Times New Roman&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;
</span></span><!--[endif]--><span dir=3D"LTR"></span>Section 19 currently s=
uggests a few possible solutions. It is important that this document will d=
efine a single solution.<o:p></o:p></p>
<p class=3D"MsoListParagraph"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoListParagraph" style=3D"text-indent:-.25in;mso-list:l0 level=
1 lfo1"><!--[if !supportLists]--><span style=3D"mso-list:Ignore">7.<span st=
yle=3D"font:7.0pt &quot;Times New Roman&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;
</span></span><!--[endif]--><span dir=3D"LTR"></span>=93Such peer delay mea=
surement messages SHALL NOT use the Timing LSP that runs between two LERs.=
=94 --&gt; This statement is problematic. It appears you have to use the ti=
ming LSP for peer-delay messages, since you
 want the PDelay_Resp to use the same path as Sync messages, to guarantee t=
hat the packet is subject to the same path delay in both cases.<o:p></o:p><=
/p>
<p class=3D"MsoListParagraph"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoListParagraph" style=3D"text-indent:-.25in;mso-list:l0 level=
1 lfo1"><!--[if !supportLists]--><span style=3D"mso-list:Ignore">8.<span st=
yle=3D"font:7.0pt &quot;Times New Roman&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;
</span></span><!--[endif]--><span dir=3D"LTR"></span>A P2P TCs sends PDelay=
_Req messages to its adjacent clock. However, since TCs do not distribute A=
nnounce messages, a TC does not necessarily know who its adjacent TCs are. =
This is why PDelay_Req is usually
 sent as multicast (e.g. in 802.1AS). <br>
in PTP over MPLS, I am guessing that the TC must maintain a list of all the=
 =93neighbors=94 it needs to send a PDelay_Req to, each =93neighbor=94 corr=
esponding to a timing label. The current document must explain how the TC s=
ends a PDelay_Req (unicast / multicast?
 To whom?).<o:p></o:p></p>
<p class=3D"MsoListParagraph"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoListParagraph" style=3D"text-indent:-.25in;mso-list:l0 level=
1 lfo1"><!--[if !supportLists]--><span style=3D"mso-list:Ignore">9.<span st=
yle=3D"font:7.0pt &quot;Times New Roman&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;
</span></span><!--[endif]--><span dir=3D"LTR"></span>Security consideration=
s: <o:p>
</o:p></p>
<p class=3D"MsoListParagraph" style=3D"margin-left:.75in;text-indent:-.25in=
;mso-list:l1 level1 lfo2">
<!--[if !supportLists]--><span style=3D"mso-list:Ignore">-<span style=3D"fo=
nt:7.0pt &quot;Times New Roman&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;
</span></span><!--[endif]--><span dir=3D"LTR"></span>If the MPLS network (p=
rovider network) serves multiple customers, it is important to analyze the =
cross-customer effects. For example:<o:p></o:p></p>
<p class=3D"MsoListParagraph" style=3D"margin-left:1.25in;text-indent:-.25i=
n;mso-list:l1 level2 lfo2">
<!--[if !supportLists]--><span style=3D"font-family:&quot;Courier New&quot;=
"><span style=3D"mso-list:Ignore">o<span style=3D"font:7.0pt &quot;Times Ne=
w Roman&quot;">&nbsp;&nbsp;
</span></span></span><!--[endif]--><span dir=3D"LTR"></span>If an LER&nbsp;=
 BC is synchronized to a specific grandmaster, belonging to customer A, the=
n customer A can attack other customers by manipulating its time.<o:p></o:p=
></p>
<p class=3D"MsoListParagraph" style=3D"margin-left:1.25in;text-indent:-.25i=
n;mso-list:l1 level2 lfo2">
<!--[if !supportLists]--><span style=3D"font-family:&quot;Courier New&quot;=
"><span style=3D"mso-list:Ignore">o<span style=3D"font:7.0pt &quot;Times Ne=
w Roman&quot;">&nbsp;&nbsp;
</span></span></span><!--[endif]--><span dir=3D"LTR"></span>Similarly for a=
 TC that is syntonized to a specfici customer.<o:p></o:p></p>
<p class=3D"MsoListParagraph" style=3D"margin-left:.75in;text-indent:-.25in=
;mso-list:l1 level1 lfo2">
<!--[if !supportLists]--><span style=3D"mso-list:Ignore">-<span style=3D"fo=
nt:7.0pt &quot;Times New Roman&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;
</span></span><!--[endif]--><span dir=3D"LTR"></span>The document must disc=
uss the fact that customer timing messages (as opposed to =93regular=94 cus=
tomer data) cannot be encrypted or authenticated on an end-to-end basis.<o:=
p></o:p></p>
<p class=3D"MsoListParagraph" style=3D"margin-left:1.25in;text-indent:-.25i=
n;mso-list:l1 level2 lfo2">
<!--[if !supportLists]--><span style=3D"font-family:&quot;Courier New&quot;=
"><span style=3D"mso-list:Ignore">o<span style=3D"font:7.0pt &quot;Times Ne=
w Roman&quot;">&nbsp;&nbsp;
</span></span></span><!--[endif]--><span dir=3D"LTR"></span>Alternatively, =
authentication/integrity verification mechanism can be used by a shared sec=
ret between the customer and provider nodes.<o:p></o:p></p>
<p class=3D"MsoListParagraph" style=3D"margin-left:.75in"><o:p>&nbsp;</o:p>=
</p>
<p class=3D"MsoListParagraph" style=3D"text-indent:-.25in;mso-list:l0 level=
1 lfo1"><!--[if !supportLists]--><span style=3D"mso-list:Ignore">10.<span s=
tyle=3D"font:7.0pt &quot;Times New Roman&quot;">&nbsp;&nbsp;
</span></span><!--[endif]--><span dir=3D"LTR"></span>Section 18.1 must incl=
ude more details about the issues listed above (Announce message distributi=
on, PDelay_Req message transmission, etc.).<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Less major Issues:<o:p></o:p></p>
<p class=3D"MsoNormal">-----------------------<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoListParagraph" style=3D"text-indent:-.25in;mso-list:l0 level=
1 lfo1"><!--[if !supportLists]--><span style=3D"mso-list:Ignore">11.<span s=
tyle=3D"font:7.0pt &quot;Times New Roman&quot;">&nbsp;&nbsp;
</span></span><!--[endif]--><span dir=3D"LTR"></span>Some terms in the docu=
ment are used inconsistently, for example, the terms =93time-stamping=94 an=
d =93timestamping=94 are used intermittently.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoListParagraph" style=3D"text-indent:-.25in;mso-list:l0 level=
1 lfo1"><!--[if !supportLists]--><span style=3D"mso-list:Ignore">12.<span s=
tyle=3D"font:7.0pt &quot;Times New Roman&quot;">&nbsp;&nbsp;
</span></span><!--[endif]--><span dir=3D"LTR"></span>There is some inconsis=
tency about capitalization, for example, the word =93Timing=94 is sometimes=
 capitalized and sometimes not. Since you are using the term =93Timing mess=
ages=94 quite often, I would suggest to add
 it to the terminology section, and to be consistent about its capitalizati=
on, whereas if the word =93timing=94 is used on its own lowercase letters w=
ould be more appropriate.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoListParagraph" style=3D"text-indent:-.25in;mso-list:l0 level=
1 lfo1"><!--[if !supportLists]--><span style=3D"mso-list:Ignore">13.<span s=
tyle=3D"font:7.0pt &quot;Times New Roman&quot;">&nbsp;&nbsp;
</span></span><!--[endif]--><span dir=3D"LTR"></span>Section 1:<br>
=93Annex F of &nbsp;[IEEE- 1588]=94 --&gt; =93Annex F of &nbsp;[IEEE]=94<o:=
p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoListParagraph" style=3D"text-indent:-.25in;mso-list:l0 level=
1 lfo1"><!--[if !supportLists]--><span style=3D"mso-list:Ignore">14.<span s=
tyle=3D"font:7.0pt &quot;Times New Roman&quot;">&nbsp;&nbsp;
</span></span><!--[endif]--><span dir=3D"LTR"></span>=93=85NTP messages for=
 clock and time synchronization. &nbsp;The PTP=85=94 --&gt; =93...NTP messa=
ges for clock and time synchronization. The NTP=85=94<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoListParagraph" style=3D"text-indent:-.25in;mso-list:l0 level=
1 lfo1"><!--[if !supportLists]--><span style=3D"mso-list:Ignore">15.<span s=
tyle=3D"font:7.0pt &quot;Times New Roman&quot;">&nbsp;&nbsp;
</span></span><!--[endif]--><span dir=3D"LTR"></span>It appears that some o=
f the sections are only applicable to PTP (e.g., Section 4, Section 18, Sec=
tion 19). That is reasonable, but it should be pointed out explicitly that =
these sections apply only to PTP.<br>
<br>
<o:p></o:p></p>
<p class=3D"MsoListParagraph" style=3D"text-indent:-.25in;mso-list:l0 level=
1 lfo1"><!--[if !supportLists]--><span style=3D"mso-list:Ignore">16.<span s=
tyle=3D"font:7.0pt &quot;Times New Roman&quot;">&nbsp;&nbsp;
</span></span><!--[endif]--><span dir=3D"LTR"></span>Section 4:<br>
=93Transparent clocks do not terminate the Timing messages but they do<br>
&nbsp;&nbsp; modify the contents of the Timing messages as they transit acr=
oss the<br>
&nbsp;&nbsp; transparent clock=94<br>
&nbsp;&nbsp; --&gt;&nbsp; This is not true for P2P transparent clocks.<o:p>=
</o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoListParagraph" style=3D"text-indent:-.25in;page-break-before=
:always;mso-list:l0 level1 lfo1">
<!--[if !supportLists]--><span lang=3D"EN" style=3D"font-size:10.0pt;font-f=
amily:&quot;Courier New&quot;"><span style=3D"mso-list:Ignore">17.</span></=
span><!--[endif]--><span dir=3D"LTR"></span>Section 7:<br>
<span lang=3D"EN" style=3D"font-size:10.0pt;font-family:&quot;Courier New&q=
uot;">=93For example the following PTP messages (called Event messages) req=
uire time-stamping, while other Non-Event PTP messages do not need time-sta=
mping.&nbsp;&nbsp; o&nbsp; Announce=94<br>
&nbsp; --&gt; Announce is not an event message, so it should be excluded fr=
om this list.<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"page-break-before:always"><span lang=3D"EN"=
 style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;"><o:p>&nbsp;=
</o:p></span></p>
<p class=3D"MsoListParagraph" style=3D"text-indent:-.25in;page-break-before=
:always;mso-list:l0 level1 lfo1">
<!--[if !supportLists]--><span lang=3D"EN" style=3D"font-size:10.0pt;font-f=
amily:&quot;Courier New&quot;"><span style=3D"mso-list:Ignore">18.</span></=
span><!--[endif]--><span dir=3D"LTR"></span>Section 7:<br>
<span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;"><span =
lang=3D"EN">=93and PDELAY_RESP_FOLLOW_UP messages must...=94 --&gt; =93and =
PDELAY_RESP_FOLLOW_UP messages MUST...=94<o:p></o:p></span></span></p>
<p class=3D"MsoNormal" style=3D"page-break-before:always"><span lang=3D"EN"=
 style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;"><o:p>&nbsp;=
</o:p></span></p>
<p class=3D"MsoListParagraph" style=3D"text-indent:-.25in;page-break-before=
:always;mso-list:l0 level1 lfo1">
<!--[if !supportLists]--><span lang=3D"EN" style=3D"font-size:10.0pt;font-f=
amily:&quot;Courier New&quot;"><span style=3D"mso-list:Ignore">19.</span></=
span><!--[endif]--><span dir=3D"LTR"></span><span lang=3D"EN" style=3D"font=
-size:10.0pt;font-family:&quot;Courier New&quot;">Section 12:<br>
=93IIn order to manage Timing LSPs=94 --&gt; =93In order to monitor timing =
LSPs=94 (OAM protocols monitor connections, rather than manage them).<o:p><=
/o:p></span></p>
<p class=3D"MsoNormal" style=3D"page-break-before:always"><span lang=3D"EN"=
 style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;"><o:p>&nbsp;=
</o:p></span></p>
<p class=3D"MsoListParagraph" style=3D"text-indent:-.25in;page-break-before=
:always;mso-list:l0 level1 lfo1">
<!--[if !supportLists]--><span lang=3D"EN" style=3D"font-size:10.0pt;font-f=
amily:&quot;Courier New&quot;"><span style=3D"mso-list:Ignore">20.</span></=
span><!--[endif]--><span dir=3D"LTR"></span><span lang=3D"EN" style=3D"font=
-size:10.0pt;font-family:&quot;Courier New&quot;">Section 15:<br>
It would be worth to mention that IPv6 zero checksum may be used, and quote=
 draft-ietf-6man-udpzero.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Ar=
ial&quot;,&quot;sans-serif&quot;">Tal.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
</div>
</blockquote>
<blockquote type=3D"cite">
<div><span>_______________________________________________</span><br>
<span>TICTOC mailing list</span><br>
<span><a href=3D"mailto:TICTOC@ietf.org">TICTOC@ietf.org</a></span><br>
<span><a href=3D"https://www.ietf.org/mailman/listinfo/tictoc">https://www.=
ietf.org/mailman/listinfo/tictoc</a></span><br>
</div>
</blockquote>
</body>
</html>

--_000_5D2C91F2FE334CB9BE100F96CBA9DC12broadcomcom_--

