IETF Logo Mail Archive

[TICTOC] NTP in draft-ietf-tictoc-1588overmpls-04

Gregory Mirsky <gregory.mirsky@ericsson.com> Thu, 06 June 2013 18:23 UTC

Return-Path: <prvs=486962002d=gregory.mirsky@ericsson.com>
X-Original-To: tictoc@ietfa.amsl.com
Delivered-To: tictoc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A492E21F9954 for <tictoc@ietfa.amsl.com>; Thu, 6 Jun 2013 11:23:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level:
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0gCQxdc+DXj6 for <tictoc@ietfa.amsl.com>; Thu, 6 Jun 2013 11:23:16 -0700 (PDT)
Received: from usevmg21.ericsson.net (usevmg21.ericsson.net [198.24.6.65]) by ietfa.amsl.com (Postfix) with ESMTP id ED5E021F995A for <tictoc@ietf.org>; Thu, 6 Jun 2013 11:23:15 -0700 (PDT)
X-AuditID: c6180641-b7f0e6d0000015f1-4c-51b0d3925fa5
Received: from EUSAAHC005.ericsson.se (Unknown_Domain [147.117.188.87]) by usevmg21.ericsson.net (Symantec Mail Security) with SMTP id F3.8B.05617.293D0B15; Thu, 6 Jun 2013 20:23:14 +0200 (CEST)
Received: from EUSAAMB103.ericsson.se ([147.117.188.120]) by EUSAAHC005.ericsson.se ([147.117.188.87]) with mapi id 14.02.0328.009; Thu, 6 Jun 2013 14:23:14 -0400
From: Gregory Mirsky <gregory.mirsky@ericsson.com>
To: Shahram Davari <davari@broadcom.com>, "amito@broadcom.com" <amito@broadcom.com>, "Bhatia, Manav (Manav)" <manav.bhatia@alcatel-lucent.com>, "Roberts, Peter (Peter)" <peter.roberts@alcatel-lucent.com>, "lmontini@cisco.com" <lmontini@cisco.com>, "tictoc@ietf.org" <tictoc@ietf.org>
Thread-Topic: NTP in draft-ietf-tictoc-1588overmpls-04
Thread-Index: Ac5i4ubOrT57JHkXTgC9GUzpraB4EA==
Date: Thu, 06 Jun 2013 18:23:12 +0000
Message-ID: <7347100B5761DC41A166AC17F22DF1121B4A0754@eusaamb103.ericsson.se>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [147.117.188.134]
Content-Type: multipart/alternative; boundary="_000_7347100B5761DC41A166AC17F22DF1121B4A0754eusaamb103erics_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFnrKLMWRmVeSWpSXmKPExsUyuXRPuO6kyxsCDaa9NbfYcznDYn2vp8Xd zy+ZLObcu8dqcXvTU1aLv8097A5sHq3P9rJ6zLp/ls1jyu+NrB5LlvxkCmCJ4rZJSiwpC85M z9O3S+DOWPr4BHvBT9GKnl/HWRoYLwl1MXJySAiYSEyZuJQVwhaTuHBvPVsXIxeHkMBRRok/ Ty6zQjjLGCVervwGVsUmYCTxYmMPO0hCRGAxk8TxaW9YQBLCAoYSPY0z2EBsEQEziYfPNrNA 2HoS9x90MILYLAIqEtsWTAEbxCvgK7Gu4RAziM0ItPr7qTVMIDazgLjErSfzmSBOEpBYsuc8 M4QtKvHy8T+oU5UlljzZzwJRny9xqPs+E8RMQYmTM5+wTGAUmoVk1CwkZbOQlEHEdSQW7P7E BmFrSyxb+JoZxj5z4DETsvgCRvZVjBylxalluelGhpsYgbF0TILNcQfjgk+WhxilOViUxHl1 eBcHCgmkJ5akZqemFqQWxReV5qQWH2Jk4uAEEVxSDYzeGlf1VcUmVk0o3S3CLs4/m+lN3Ok4 iysZKu7bTjXc5f4yy63u6TTvyPluJg/slMQ3NKup5jHnSBdn8nytvR6e/qLTSsxNoGnzZvUV u2/mZVnJbFBWVMuQYQswe/Zh+zKPmDW5r/dvWmM3NdJw/+vr+abaG8x7tB7Gp27f8uebwoHC HM4ri5RYijMSDbWYi4oTAWJb/nx4AgAA
Subject: [TICTOC] NTP in draft-ietf-tictoc-1588overmpls-04
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, 06 Jun 2013 18:23:22 -0000

Dear Authors, et al.,
The draft-ietf-tictoc-1588overmpls-04 is currently titled as "Transporting Timing messages over MPLS Networks" and states that both timing synchronization protocols, PTP and NTP, require use of PTP LSP to transport timing messages over an MPLS network. After reading RFC 5905 I am not sure that PTP LSP, with its constraints and additional complexity, is required to transport NTPv4 messages over an MPLS network. And first paragraph in Section 3 Problem Statement of draft-ietf-tictoc-1588overmpls-04 explains motivation for the PTP as
"There is a need to transport Timing messages over MPLS networks while supporting the Transparent Clock (TC), Boundary Clock (BC) and Ordinary Clock (OC) functionality in the LER and LSRs in the MPLS network."
 but says nothing of a kind about NTP.

        Regards,
                Greg

v2.46.0 | Report a Bug | By Email | System Status