[TICTOC] Mirja Kühlewind's No Objection on draft-ietf-tictoc-multi-path-synchronization-06: (with COMMENT)

"Mirja Kuehlewind" <ietf@kuehlewind.net> Wed, 19 October 2016 15:39 UTC

Return-Path: <ietf@kuehlewind.net>
X-Original-To: tictoc@ietf.org
Delivered-To: tictoc@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id EF67D12965A; Wed, 19 Oct 2016 08:39:16 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: "Mirja Kuehlewind" <ietf@kuehlewind.net>
To: "The IESG" <iesg@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.35.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <147689155697.8944.16723703796628114617.idtracker@ietfa.amsl.com>
Date: Wed, 19 Oct 2016 08:39:16 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/tictoc/AvPPo9JMn84r6W8Q7iZSXHPQrQU>
Cc: draft-ietf-tictoc-multi-path-synchronization@ietf.org, tictoc@ietf.org, odonoghue@isoc.org, tictoc-chairs@ietf.org
Subject: [TICTOC] =?utf-8?q?Mirja_K=C3=BChlewind=27s_No_Objection_on_draft?= =?utf-8?q?-ietf-tictoc-multi-path-synchronization-06=3A_=28with_COMMENT?= =?utf-8?q?=29?=
X-BeenThere: tictoc@ietf.org
X-Mailman-Version: 2.1.17
List-Id: Timing over IP Connection and Transfer of Clock BOF <tictoc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tictoc>, <mailto:tictoc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tictoc/>
List-Post: <mailto:tictoc@ietf.org>
List-Help: <mailto:tictoc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tictoc>, <mailto:tictoc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 19 Oct 2016 15:39:17 -0000

Mirja Kühlewind has entered the following ballot position for
draft-ietf-tictoc-multi-path-synchronization-06: No Objection

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


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


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



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

Thanks for addressing my comments. I still think this draft reads a
little like a research paper but it improved. I would still recommend to
consider informational instead of experimental. If this draft stays
experimental, it would actually benefit from an own section that
describes what this experiment is about. Which parts should be evaluated
and what are the expected outcomes?

I have one remaining comments  on the security section:

"The security aspects of time synchronization protocols are discussed
   in detail in [TICTOCSEC].“

TICTOCSEC is a reference to RFC 7384 on "Security Requirements of Time
Protocols in Packet Switched Networks“. As this RFC species requirements,
it would be much more useful to document how these requirements have bee
addressed by this proposal rather than just referring to it and leave
this exercise to the reader.

And some remaining editorial comments:

I would still recommend to further shorten the abstract by removing or
moving the first part, potentially into the introduction instead, and
only leave this part:

"This document describes a multi-path approach to the Network Time
Protocol (NTP) and the
   Precision Time Protocol (PTP) over IP networks, allowing the protocols
to run concurrently over
   multiple communication paths between the master and slave clocks. The
   multi-path approach can significantly contribute to clock accuracy,
   security and fault tolerance."

Also section 3 and 4 could be completely removed or shorten to 2-3
paragraph that could also be integarted into the introdcution.