IETF Logo Mail Archive

Re: [TICTOC] WGLC for draft-ietf-ntp-using-nts-for-ntp

Jiangyuanlong <jiangyuanlong@huawei.com> Thu, 31 August 2017 05:40 UTC

Return-Path: <jiangyuanlong@huawei.com>
X-Original-To: tictoc@ietfa.amsl.com
Delivered-To: tictoc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3956F1323B6; Wed, 30 Aug 2017 22:40:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.22
X-Spam-Level:
X-Spam-Status: No, score=-4.22 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id E02KUnJ_Xh1w; Wed, 30 Aug 2017 22:40:18 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 90A661323B9; Wed, 30 Aug 2017 22:40:17 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml706-cah.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id DNQ49000; Thu, 31 Aug 2017 05:40:15 +0000 (GMT)
Received: from DGGEML401-HUB.china.huawei.com (10.3.17.32) by lhreml706-cah.china.huawei.com (10.201.108.47) with Microsoft SMTP Server (TLS) id 14.3.301.0; Thu, 31 Aug 2017 06:40:14 +0100
Received: from DGGEML507-MBX.china.huawei.com ([169.254.2.7]) by DGGEML401-HUB.china.huawei.com ([fe80::89ed:853e:30a9:2a79%31]) with mapi id 14.03.0301.000; Thu, 31 Aug 2017 13:40:02 +0800
From: Jiangyuanlong <jiangyuanlong@huawei.com>
To: Karen O'Donoghue <odonoghue@isoc.org>, "ntp@ietf.org" <ntp@ietf.org>
CC: "tictoc@ietf.org" <tictoc@ietf.org>
Thread-Topic: WGLC for draft-ietf-ntp-using-nts-for-ntp
Thread-Index: AQHTEMnCM2s3Nc34m0O8jzUH1rPjTqKd5GhQ
Date: Thu, 31 Aug 2017 05:40:01 +0000
Message-ID: <3B0A1BED22CAD649A1B3E97BE5DDD68BBB59A424@dggeml507-mbx.china.huawei.com>
References: <9D367122-EFFD-4C2E-9AE1-49FD5C694166@isoc.org>
In-Reply-To: <9D367122-EFFD-4C2E-9AE1-49FD5C694166@isoc.org>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.74.202.215]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
X-Mirapoint-Virus-RAPID-Raw: score=unknown(0), refid=str=0001.0A090201.59A7A140.0008, ss=1, re=0.000, recu=0.000, reip=0.000, cl=1, cld=1, fgs=0, ip=169.254.2.7, so=2013-06-18 04:22:30, dmn=2013-03-21 17:37:32
X-Mirapoint-Loop-Id: 666b641cd5f3b740c4f82b08a209ee43
Archived-At: <https://mailarchive.ietf.org/arch/msg/tictoc/eKRkU2HVXA4JqdTR_M6MDgHnpJA>
Subject: Re: [TICTOC] WGLC for draft-ietf-ntp-using-nts-for-ntp
X-BeenThere: tictoc@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Timing over IP Connection and Transfer of Clock BOF <tictoc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tictoc>, <mailto:tictoc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tictoc/>
List-Post: <mailto:tictoc@ietf.org>
List-Help: <mailto:tictoc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tictoc>, <mailto:tictoc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 31 Aug 2017 05:40:20 -0000

Hi, after going through this draft, I am not sure whether ietf-ntp-data-minimization-00 should be listed in the Normative Reference, or not at all.
Usually, an unpublished normative reference will dramatically slow the process of turning a draft into a RFC (they need to be published as a cluster at the same time).
It seems also ietf-ntp-data-minimization solves the problem of unlinkability, not necessarily a part of NTS, but a complement (just as the relationship of Section 9 "Security Considerations" and Section 10 "Privacy Considerations" ). 

Minor editorial comments:
1. IETF requirement languages can be used in Section 4 more frequently.
2. "both parties should attempt to initiate a DTLS session with their peer" can be rephrased into "each party SHOULD attempt to initiate a DTLS session with its peer" in Page 7.
3. " an Warning record " to "a Warning record" in Section 5.1.4.

Kind regards,
Yuanlong

-----Original Message-----
From: TICTOC [mailto:tictoc-bounces@ietf.org] On Behalf Of Karen O'Donoghue
Sent: Wednesday, August 09, 2017 12:41 PM
To: ntp@ietf.org
Cc: tictoc@ietf.org
Subject: [TICTOC] WGLC for draft-ietf-ntp-using-nts-for-ntp

Folks,

This begins a three week working group last call (WGLC) for "Network Time Security for the Network Time Protocol”.

https://datatracker.ietf.org/doc/draft-ietf-ntp-using-nts-for-ntp/

Please review and provide comments to the mailing list by no later than 31 August 2017. Earlier comments and discussion would be appreciated. Please note that the chairs will be using this WGLC to determine consensus to move this document forward to the IESG. 

Also, as a reminder, we have migrated the working group mailing list to IETF infrastructure. Please respond to ntp@ietf.org. ]

Regards,
Karen and Dieter
_______________________________________________
TICTOC mailing list
TICTOC@ietf.org
https://www.ietf.org/mailman/listinfo/tictoc

v2.23.0 | Report a Bug | By Email