
From ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org  Wed Apr  1 01:24:14 2015
Return-Path: <ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org>
X-Original-To: ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com
Delivered-To: ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 898071A8A7C for <ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com>; Wed,  1 Apr 2015 01:24:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.21
X-Spam-Level:
X-Spam-Status: No, score=-4.21 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 SCjv1aRKPPIB for <ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com>; Wed,  1 Apr 2015 01:24:13 -0700 (PDT)
Received: from lists.ntp.org (lists.ntp.org [149.20.68.7]) by ietfa.amsl.com (Postfix) with ESMTP id 1562B1A8A85 for <ntp-archives-ahFae6za@lists.ietf.org>; Wed,  1 Apr 2015 01:24:13 -0700 (PDT)
Received: from lists.ntp.org (lists.ntp.org [149.20.68.7]) by lists.ntp.org (Postfix) with ESMTP id 0198086DAB9 for <ntp-archives-ahFae6za@lists.ietf.org>; Wed,  1 Apr 2015 08:24:12 +0000 (UTC)
X-Original-To: ntpwg@lists.ntp.org
Delivered-To: ntpwg@lists.ntp.org
Received: from mail1.ntp.org (mail1.ntp.org [IPv6:2001:4f8:fff7:1::5]) by lists.ntp.org (Postfix) with ESMTP id 9195286D343 for <ntpwg@lists.ntp.org>; Wed,  1 Apr 2015 08:24:00 +0000 (UTC)
Received: from mail.ietf.org ([4.31.198.44]) by mail1.ntp.org with esmtps (TLSv1:AES256-SHA:256) (Exim 4.77 (FreeBSD)) (envelope-from <internet-drafts@ietf.org>) id 1YdDwG-000KHz-CG for ntpwg@lists.ntp.org; Wed, 01 Apr 2015 08:24:00 +0000
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3B2F21A8A85 for <ntpwg@lists.ntp.org>; Wed,  1 Apr 2015 01:23:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1_xHiBOelNTF; Wed,  1 Apr 2015 01:23:46 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 180F41A89B4; Wed,  1 Apr 2015 01:23:45 -0700 (PDT)
MIME-Version: 1.0
From: internet-drafts@ietf.org
To: <i-d-announce@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 5.13.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20150401082345.17463.56209.idtracker@ietfa.amsl.com>
Date: Wed, 01 Apr 2015 01:23:45 -0700
X-SA-Exim-Connect-IP: 4.31.198.44
X-SA-Exim-Rcpt-To: ntpwg@lists.ntp.org
X-SA-Exim-Mail-From: internet-drafts@ietf.org
X-SA-Exim-Version: 4.2
X-SA-Exim-Scanned: Yes (on mail1.ntp.org)
Cc: ntpwg@lists.ntp.org
Subject: [ntpwg] I-D Action: draft-ietf-ntp-cms-for-nts-message-03.txt
X-BeenThere: ntpwg@lists.ntp.org
X-Mailman-Version: 2.1.14
List-Id: IETF Working Group for Network Time Protocol <ntpwg.lists.ntp.org>
List-Unsubscribe: <http://lists.ntp.org/options/ntpwg>, <mailto:ntpwg-request@lists.ntp.org?subject=unsubscribe>
List-Archive: <http://lists.ntp.org/pipermail/ntpwg>
List-Post: <mailto:ntpwg@lists.ntp.org>
List-Help: <mailto:ntpwg-request@lists.ntp.org?subject=help>
List-Subscribe: <http://lists.ntp.org/listinfo/ntpwg>, <mailto:ntpwg-request@lists.ntp.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org
Sender: ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org

A New Internet-Draft is available from the on-line Internet-Drafts directories.
 This draft is a work item of the Network Time Protocol Working Group of the IETF.

        Title           : Protecting Network Time Security Messages with the Cryptographic Message Syntax (CMS)
        Authors         : Dieter Sibold
                          Kristof Teichel
                          Stephen Roettger
                          Russ Housley
	Filename        : draft-ietf-ntp-cms-for-nts-message-03.txt
	Pages           : 15
	Date            : 2015-04-01

Abstract:
   This document describes a convention for using the Cryptographic
   Message Syntax (CMS) to protect the messages in the Network Time
   Security (NTS) protocol.  NTS provides authentication of time servers
   as well as integrity protection of time synchronization messages
   using Network Time Protocol (NTP) or Precision Time Protocol (PTP).



The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-ntp-cms-for-nts-message/

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-ietf-ntp-cms-for-nts-message-03

A diff from the previous version is available at:
http://www.ietf.org/rfcdiff?url2=draft-ietf-ntp-cms-for-nts-message-03


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

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

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

From ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org  Wed Apr  1 18:16:12 2015
Return-Path: <ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org>
X-Original-To: ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com
Delivered-To: ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 862AA1AD084 for <ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com>; Wed,  1 Apr 2015 18:16:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.21
X-Spam-Level:
X-Spam-Status: No, score=-4.21 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 SoFB8o4fIfSt for <ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com>; Wed,  1 Apr 2015 18:16:10 -0700 (PDT)
Received: from lists.ntp.org (lists.ntp.org [149.20.68.7]) by ietfa.amsl.com (Postfix) with ESMTP id B1B391A88FE for <ntp-archives-ahFae6za@lists.ietf.org>; Wed,  1 Apr 2015 18:16:10 -0700 (PDT)
Received: from lists.ntp.org (lists.ntp.org [149.20.68.7]) by lists.ntp.org (Postfix) with ESMTP id 8949686DB29 for <ntp-archives-ahFae6za@lists.ietf.org>; Thu,  2 Apr 2015 01:16:10 +0000 (UTC)
X-Original-To: ntpwg@lists.ntp.org
Delivered-To: ntpwg@lists.ntp.org
Received: from mail1.ntp.org (mail1.ntp.org [IPv6:2001:4f8:fff7:1::5]) by lists.ntp.org (Postfix) with ESMTP id E50D786D343 for <ntpwg@lists.ntp.org>; Tue, 31 Mar 2015 17:57:17 +0000 (UTC)
Received: from mail-db3on0098.outbound.protection.outlook.com ([157.55.234.98] helo=emea01-db3-obe.outbound.protection.outlook.com) by mail1.ntp.org with esmtps (TLSv1:AES256-SHA:256) (Exim 4.77 (FreeBSD)) (envelope-from <denis.reilly@spectracom.orolia.com>) id 1Yd0PU-0000xQ-QG for ntpwg@lists.ntp.org; Tue, 31 Mar 2015 17:57:17 +0000
Received: from AM3PR06MB1202.eurprd06.prod.outlook.com (25.163.60.28) by AM3PR06MB1203.eurprd06.prod.outlook.com (25.163.60.29) with Microsoft SMTP Server (TLS) id 15.1.118.21; Tue, 31 Mar 2015 17:56:59 +0000
Received: from AM3PR06MB1202.eurprd06.prod.outlook.com ([25.163.60.28]) by AM3PR06MB1202.eurprd06.prod.outlook.com ([25.163.60.28]) with mapi id 15.01.0118.022; Tue, 31 Mar 2015 17:56:59 +0000
From: Denis Reilly <denis.reilly@spectracom.orolia.com>
To: Yaakov Stein <yaakov_s@rad.com>, "ntpwg@lists.ntp.org" <ntpwg@lists.ntp.org>
Thread-Topic: TICTOC wiki page
Thread-Index: AdBnH/jN8Zcpq+KqQyKXV59K43AI3gEu7gyg
Date: Tue, 31 Mar 2015 17:56:58 +0000
Message-ID: <AM3PR06MB1202AF4AA0461F08757D12ECD2F40@AM3PR06MB1202.eurprd06.prod.outlook.com>
References: <DB5PR03MB0999879FC625523135DDD301E50B0@DB5PR03MB0999.eurprd03.prod.outlook.com>
In-Reply-To: <DB5PR03MB0999879FC625523135DDD301E50B0@DB5PR03MB0999.eurprd03.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [66.193.84.98]
authentication-results: rad.com; dkim=none (message not signed) header.d=none; 
x-microsoft-antispam: UriScan:;BCL:0;PCL:0;RULEID:;SRVR:AM3PR06MB1203;
x-microsoft-antispam-prvs: <AM3PR06MB1203269FE2B7C12DB8470A60D2F40@AM3PR06MB1203.eurprd06.prod.outlook.com>
x-forefront-antispam-report: BMV:1; SFV:NSPM; SFS:(10009020)(6009001)(13464003)(377454003)(52044002)(1720100001)(46102003)(87936001)(62966003)(2900100001)(2950100001)(40100003)(50986999)(77156002)(76176999)(54356999)(92566002)(102836002)(86362001)(74316001)(19580405001)(15975445007)(2501003)(33656002)(107886001)(122556002)(2656002)(19580395003)(76576001)(66066001)(7059030); DIR:OUT; SFP:1101; SCL:1; SRVR:AM3PR06MB1203; H:AM3PR06MB1202.eurprd06.prod.outlook.com; FPR:; SPF:None; MLV:sfv; LANG:en; 
x-exchange-antispam-report-test: UriScan:;
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(601004)(5005006)(5002010); SRVR:AM3PR06MB1203; BCL:0; PCL:0; RULEID:; SRVR:AM3PR06MB1203; 
x-forefront-prvs: 0532BF6DC2
MIME-Version: 1.0
X-OriginatorOrg: spectracom.orolia.com
X-MS-Exchange-CrossTenant-originalarrivaltime: 31 Mar 2015 17:56:58.9616 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: a263030c-9c1b-421f-9471-1dec0b29c664
X-MS-Exchange-Transport-CrossTenantHeadersStamped: AM3PR06MB1203
X-SA-Exim-Connect-IP: 157.55.234.98
X-SA-Exim-Rcpt-To: ntpwg@lists.ntp.org
X-SA-Exim-Mail-From: denis.reilly@spectracom.orolia.com
X-SA-Exim-Version: 4.2
X-SA-Exim-Scanned: Yes (on mail1.ntp.org)
X-Mailman-Approved-At: Thu, 02 Apr 2015 01:15:40 +0000
Subject: Re: [ntpwg] TICTOC wiki page
X-BeenThere: ntpwg@lists.ntp.org
X-Mailman-Version: 2.1.14
Precedence: list
List-Id: IETF Working Group for Network Time Protocol <ntpwg.lists.ntp.org>
List-Unsubscribe: <http://lists.ntp.org/options/ntpwg>, <mailto:ntpwg-request@lists.ntp.org?subject=unsubscribe>
List-Archive: <http://lists.ntp.org/pipermail/ntpwg>
List-Post: <mailto:ntpwg@lists.ntp.org>
List-Help: <mailto:ntpwg-request@lists.ntp.org?subject=help>
List-Subscribe: <http://lists.ntp.org/listinfo/ntpwg>, <mailto:ntpwg-request@lists.ntp.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org
Sender: ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org

I like the idea of using a wiki to exchange ideas (in addition to the list).  In fact, it would be nice if we could start up a wiki to take suggestions for the NTP BCP document that we discussed last week.

Karen, I've looked at http://trac.tools.ietf.org/wg/ntp/ and there does not seem to be a Wiki active. Is that something that we can start there? 

Regards,

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

This e-mail and any files transmitted with it are confidential and are intended solely for the use of the individual or entity to which they are addressed. If you received this e-mail in error please note that any use, dissemination, forwarding, printing, or copying of this e-mail is strictly prohibited.


-----Original Message-----
From: ntpwg-bounces+denis.reilly=spectracom.orolia.com@lists.ntp.org [mailto:ntpwg-bounces+denis.reilly=spectracom.orolia.com@lists.ntp.org] On Behalf Of Yaakov Stein
Sent: Wednesday, March 25, 2015 1:25 PM
To: tictoc@ietf.org
Cc: ntpwg@lists.ntp.org
Subject: [ntpwg] TICTOC wiki page

All, 

As proposed by our AD at today's session, I jotted down some ideas related to management of timing distribution protocols in general on the TICTOC Wiki http://trac.tools.ietf.org/wg/tictoc/trac/wiki .

I didn't put too much time or thought into this, so please consider this a very rough first draft of things to be considered.

Please feel free to comment, add, change, etc.

Let's see if this Wiki can be a good tool for exchanging ideas.

Y(J)S

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

From ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org  Thu Apr  2 21:03:35 2015
Return-Path: <ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org>
X-Original-To: ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com
Delivered-To: ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3958F1A017E for <ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com>; Thu,  2 Apr 2015 21:03:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.21
X-Spam-Level:
X-Spam-Status: No, score=-4.21 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 qIOAs8fw1rJP for <ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com>; Thu,  2 Apr 2015 21:03:33 -0700 (PDT)
Received: from lists.ntp.org (lists.ntp.org [149.20.68.7]) by ietfa.amsl.com (Postfix) with ESMTP id 3052B1A017C for <ntp-archives-ahFae6za@lists.ietf.org>; Thu,  2 Apr 2015 21:03:33 -0700 (PDT)
Received: from lists.ntp.org (lists.ntp.org [149.20.68.7]) by lists.ntp.org (Postfix) with ESMTP id 2209886DAE3 for <ntp-archives-ahFae6za@lists.ietf.org>; Fri,  3 Apr 2015 04:03:33 +0000 (UTC)
X-Original-To: ntpwg@lists.ntp.org
Delivered-To: ntpwg@lists.ntp.org
Received: from mail1.ntp.org (mail1.ntp.org [IPv6:2001:4f8:fff7:1::5]) by lists.ntp.org (Postfix) with ESMTP id DBFCC86D4F1 for <ntpwg@lists.ntp.org>; Thu,  2 Apr 2015 09:52:29 +0000 (UTC)
Received: from mx1.redhat.com ([209.132.183.28]) by mail1.ntp.org with esmtps (TLSv1:AES256-SHA:256) (Exim 4.77 (FreeBSD)) (envelope-from <fweimer@redhat.com>) id 1YdbnP-000I4e-Sr for ntpwg@lists.ntp.org; Thu, 02 Apr 2015 09:52:29 +0000
Received: from int-mx09.intmail.prod.int.phx2.redhat.com (int-mx09.intmail.prod.int.phx2.redhat.com [10.5.11.22]) by mx1.redhat.com (Postfix) with ESMTPS id D38902B649C for <ntpwg@lists.ntp.org>; Thu,  2 Apr 2015 09:52:18 +0000 (UTC)
Received: from oldenburg.str.redhat.com (oldenburg.str.redhat.com [10.33.200.60]) by int-mx09.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4) with ESMTP id t329qHhg018720 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <ntpwg@lists.ntp.org>; Thu, 2 Apr 2015 05:52:18 -0400
Message-ID: <551D1150.5080500@redhat.com>
Date: Thu, 02 Apr 2015 11:52:16 +0200
From: Florian Weimer <fweimer@redhat.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.5.0
MIME-Version: 1.0
To: ntpwg@lists.ntp.org
X-Scanned-By: MIMEDefang 2.68 on 10.5.11.22
X-SA-Exim-Connect-IP: 209.132.183.28
X-SA-Exim-Rcpt-To: ntpwg@lists.ntp.org
X-SA-Exim-Mail-From: fweimer@redhat.com
X-SA-Exim-Version: 4.2
X-SA-Exim-Scanned: Yes (on mail1.ntp.org)
X-Mailman-Approved-At: Fri, 03 Apr 2015 04:01:38 +0000
Subject: [ntpwg] Comments on various NTS drafts
X-BeenThere: ntpwg@lists.ntp.org
X-Mailman-Version: 2.1.14
Precedence: list
List-Id: IETF Working Group for Network Time Protocol <ntpwg.lists.ntp.org>
List-Unsubscribe: <http://lists.ntp.org/options/ntpwg>, <mailto:ntpwg-request@lists.ntp.org?subject=unsubscribe>
List-Archive: <http://lists.ntp.org/pipermail/ntpwg>
List-Post: <mailto:ntpwg@lists.ntp.org>
List-Help: <mailto:ntpwg-request@lists.ntp.org?subject=help>
List-Subscribe: <http://lists.ntp.org/listinfo/ntpwg>, <mailto:ntpwg-request@lists.ntp.org?subject=subscribe>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
Errors-To: ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org
Sender: ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org

SGVyZSBhcmUgYSBmZXcgY29tbWVudHMgb24gdGhvc2UgZHJhZnRzLiAgSSBob3BlIHRoZXkgYXJl
IHVzZWZ1bC4KCkkgc3Ryb25nbHkgcmVjb21tZW5kIHJldXNpbmcgKEQpVExTIGluc3RlYWQgb2Yg
aW1wbGVtZW50aW5nIHlvdXIgb3duCmNyeXB0b2dyYXBoaWMgcHJvdG9jb2wuICBJIGhhdmUgbWFy
a2VkIHRoZSBpc3N1ZXMgd2hpY2ggd291bGQgZ28gYXdheQp3aXRoIGEgcHJvcGVyIGltcGxlbWVu
dGF0aW9uIG9mIChEKVRMUyB3aXRoIOKAnChEKeKAnS4gIFdpdGggRFRMUywgdGhlCnNlcnZlciBj
b3VsZCBqdXN0IHNlbmQgdGhlIGNsaWVudCBjb29raWUgYW5kIHRoZSBITUFDIGtleSwgZGlzcmVn
YXJkaW5nCnRoZSBjbGllbnQgY2VydGlmaWNhdGUuCgojIFJGQyA3Mzg0IGNvbXBsaWFuY2UKCkZp
cnN0IG9mIGFsbCwgdGhlIHByb3Bvc2VkIHByb3RvY29sIGZhaWxzIHRvIGltcGxlbWVudCB0aGUg
cmVxdWlyZW1lbnRzCm9mIFJGQyA3Mzg0LiAgVGhpcyBpcyBtb3N0bHkgZHVlIHRvIHRoZSBmYWN0
IHRoYXQgc2V2ZXJhbCBvZiBpdHMKcmVxdWlyZW1lbnRzIGFyZSAqaW1wb3NzaWJsZSogdG8gaW1w
bGVtZW50OgoKU2VjdGlvbiA1LjEuMiBpcyBsaWtlbHkgYm9ndXMgYmVjYXVzZSBpdCBpcyBub3Qg
aW1wbGVtZW50YWJsZSBpbgpwcmFjdGljZSAoZW5kLXRvLWVuZCBzZWN1cml0eSBtYWtlcyBpbnRl
cm1lZGlhdGUgY2xvY2tzIG9ic29sZXRlKS4KClNlY3Rpb24gNS42LjEgcmVxdWlyZXMgZnJlcXVl
bnQga2V5IHJlZnJlc2guIFRoaXMgaXMgaW1wb3NzaWJsZSB0bwppbXBsZW1lbnQgaW4gcHJhY3Rp
Y2UgKHVsdGltYXRlIGtleXMgY2Fubm90IGJlIHJlZnJlc2hlZCB3aXRob3V0Cm9wZXJhdG9yIGlu
dGVydmVudGlvbiksIGFuZCBub3QgbmVjZXNzYXJ5IGFzIGxvbmcgYXMgc3VmZmljaWVudGx5IHN0
cm9uZwpjcnlwdG9ncmFwaGljIHByaW1pdGl2ZXMgKG5vbi1icm9rZW4gYWxnb3JpdGhtcykgYXJl
IHVzZWQuCgpTZWN0aW9uIDUuOSBpcyBpbXBvc3NpYmxlIHRvIGltcGxlbWVudC4gVGhlcmUgaXMg
bm8gcHJvdGVjdGlvbiBhZ2FpbnN0CkRvUyBmcm9tIE1JVE0gYXR0YWNrcy4gUHJvdGVjdGlvbiBh
Z2FpbnN0IGxvdy1yYXRlIG1lc3NhZ2Ugc3Bvb2ZpbmcKd2l0aG91dCBrbm93bGVkZ2Ugb2YgdGhl
IGtleXMgc2VlbXMgcmVhc29uYWJsZSwgdGhvdWdoLgoKSW4gYWRkaXRpb24sIFJGQyA3Mzg0LCBT
ZWN0aW9uIDMuMi4xMCBpbmRpY2F0ZXMgdGhhdCBzZWN1cmluZyB0aGUgdGltZQpzb3VyY2Ugb2Yg
YW4gZW50aXJlIG9yZ2FuaXphdGlvbiBmcm9tIGFuIGV4dGVybmFsIHNvdXJjZSBpcyBvdXQgb2YK
c2NvcGUuIEhvd2V2ZXIsIHRoaXMgaXMgbGlrZWx5IHRoZSBtb3N0IGNvbW1vbiBhcHBsaWNhdGlv
biBvZiBhIHNlY3VyaXR5CnRpbWUgcHJvdG9jb2wuCgojIGRyYWZ0LWlldGYtbnRwLW5ldHdvcmst
dGltZS1zZWN1cml0eS0wOAoKKiBUaGUgY2xpZW50IGhvc3QgbmFtZSBpbiB0aGUgY2xpZW50X2Fz
c29jIGlzIGFuIHVubmVjZXNzYXJ5IGluZm9ybWF0aW9uCmxlYWsuCgoqIFRoZSBjbGllbnRfYXNz
b2MgbWVzc2FnZSBuZWVkcyBhIG1lY2hhbmlzbSB0byBzZWxlY3QgdGhlIHNlcnZlcgpjZXJ0aWZp
Y2F0ZS4gVGhpcyBpcyBkZXNpcmFibGUgZm9yIG1ldHJpY3MgYW5kIHJlcXVpcmVkIGZvciBzZXJ2
ZXIga2V5CnJvbGxvdmVyIHdpdGhvdXQgbG9ja2luZyBvdXQgdGhlIGV4aXN0aW5nIGNsaWVudHMu
IFdpdGhvdXQgdGhpcwptZWNoYW5pc20sIGl0IGlzIG5lY2Vzc2FyeSB0byB1c2UgbXVsdGlwbGUg
SVAgYWRkcmVzc2VzLiAoRCkgdmlhIFNOSS4KCiogVGhlIGludGVncml0eSBjaGVja3Mgb24gdGhl
IHNlcnZlcl9hc3NvYyByZXNwb25zZSBhcmUgdW5jbGVhci4gSXQgaXMKbm90IHNwZWNpZmllZCBp
ZiBob3N0IG5hbWUgdmVyaWZpY2F0aW9uIGlzIHBlcmZvcm1lZC4gKEQpCgoqIEluIGEgdHJpdmlh
bCBVRFAtYmFzZWQgaW1wbGVtZW50YXRpb24sIHRoZSBzZXJ2ZXJfYXNzb2MgcmVzcG9uc2UgaXMK
Y29tcHV0ZWQgYmVmb3JlIHR3by13YXkgY29tbXVuaWNhdGlvbiB3aXRoIHRoZSBjbGllbnQgSVAg
YWRkcmVzcyBoYXMKYmVlbiBwcm92ZW4sIHJlc3VsdGluZyBpbiBhIGRlbmlhbCBvZiBzZXJ2aWNl
IHZ1bG5lcmFiaWxpdHkgKENQVQpvdmVybG9hZCBkdWUgdG8gc2lnbmF0dXJlIGNvbXB1dGF0aW9u
IGZvciBzcG9vZmVkIGNsaWVudHMsIHRyYWZmaWMKYW1wbGlmaWNhdGlvbiBkdWUgdG8gbGFyZ2Vy
IHNlcnZlciByZXNwb25zZSkuIFRoaXMgYWxzbyBhZmZlY3RzIHRoZQpzZXJ2ZXJfY29vayBtZXNz
YWdlIGdlbmVyYXRpb24uIFBob3R1cmlzIGNvb2tpZXMgd291bGQgYWRkcmVzcyB0aGlzLiAoRCkK
CiogVGhlIHNlcnZlcl9jb29rIG1lc3NhZ2UgdXNlcyBub24taHlicmlkIGFzeW1tZXRyaWMgZW5j
cnlwdGlvbi4gV2l0aApFQ0MsIHRoaXMgZG9lcyBub3Qgd29yayBiZWNhdXNlIHRoZSBwcm92aWRl
ZCBwYXlsb2FkIHNwYWNlIGlzIG5vdCBsYXJnZQplbm91Z2guIFRoZSB1c3VhbCBoeWJyaWQgc2No
ZW1lIHNob3VsZCBiZSB1c2VkIGluc3RlYWQuIFRoaXMgbWVhbnMgdGhhdAphbiBhZGRpdGlvbmFs
IGNyeXB0b2dyYXBoaWMgcHJpbWl0aXZlIGhhcyB0byBiZSBuZWdvdGlhdGVkLiAoRCkKCiogQ2xp
ZW50IGNlcnRpZmljYXRlIG1hbmFnZW1lbnQgaXMgYSByZWQgZmxhZyBmb3IgbWFueSBvcmdhbml6
YXRpb25zLiBJdAp3b3VsZCBiZSBiZXR0ZXIgaWYgdGhlIHByb3RvY29sIHdvdWxkIG5vdCB1c2Ug
YSBjbGllbnQgY2VydGlmaWNhdGUgYXQKYWxsLCBhbmQgc29tZSBvdGhlciBrZXkgYWdyZWVtZW50
IHNjaGVtZSAoZS5nLiwgYXBwbGljYXRpb24ga2V5CmV4dHJhY3Rpb24gd2l0aCBUTFMvRFRMUywg
d2l0aG91dCBjbGllbnQgY2VydGlmaWNhdGVzLCBvciBhIFRMUyByZXNwb25zZQpjb250YWluaW5n
IGFuIGVuY3J5cHRlZCBzZXNzaW9uIGtleSkuIChEKQoKKiBXaXRoIGEgc2VydmVyIHdpdGhvdXQg
cGVyLWNsaWVudCBzdGF0ZSwgdGhlIEhNQUMga2V5IHNldHVwIGhhcyB0byBiZQpwZXJmb3JtZWQg
b24gZWFjaCByZXNwb25zZS4gIFRoaXMgaXMgcXVpdGUgY29zdGx5LiAgQSBkaWZmZXJlbnQgTUFD
CmNvdWxkIGJlIHF1aXRlIGEgYml0IGNoZWFwZXIgaW4gdGVybXMgb2YgQ1BVIG92ZXJoZWFkLgoK
KiBJIGhhdmUgZG91YnRzIGFib3V0IHRoZSB1c2Ugb2YgVEVTTEEuCgogIC4gSXMgdGhlcmUgc3Vm
ZmljaWVudCBvcGVyYXRpb25hbCBleHBlcmllbmNlIHdpdGggdGhpcyBwcm90b2NvbD8KCiAgLiBJ
dCBpcyBuZXZlciBzdGF0ZWQgZXhwbGljaXRseSwgYnV0IHJlYWRpbmcgdGhlIHByb3RvY29sCmRl
c2NyaXB0aW9ucywgaXQgaXMgZXhwZWN0ZWQgdGhhdCBURVNMQSBpcyBzZWN1cmUgYWdhaW5zdCBt
YWxpY2lvdXMKcmVjaXBpZW50cy4KCiAgLiBURVNMQSB1c2VzIGEgcmFjZSBjb25kaXRpb24gZm9y
IHNlY3VyaXR5LCB3aGljaCBzZWVtcyBpbmhlcmVudGx5IHJpc2t5LgoKICAuIFRoZSB1c2Ugb2Yg
dGltZSBmb3Igc2VjdXJpdHkgcHVycG9zZXMgaW50ZXJhY3RzIGluIGEgY29tcGxleCB3YXkKd2l0
aCB1c2luZyBURVNMQSBmb3IgdGltZSBzeW5jaHJvbml6YXRpb24uCgojIGRyYWZ0LWlldGYtbnRw
LWNtcy1mb3ItbnRzLW1lc3NhZ2UtMDIKCiogREVSIGlzIHVzZWQgZXZlbiBmb3IgZmFzdC1wYXRo
IHRpbWUgc3luY2hyb25pemF0aW9uIG1lc3NhZ2VzIChub3QganVzdApmb3IgdGhlIGhhbmRzaGFr
ZSkuICBUaGlzIHNlZW1zIHVubmVjZXNzYXJ5LgoKKiBSZXF1aXJpbmcgYSBuZXcgT0lEIGluIHRo
ZSBFeHRlbmRlZCBLZXkgVXNhZ2VzIGF0dHJpYnV0ZSBvZgpjZXJ0aWZpY2F0ZXMgKHNlY3Rpb24g
NCkgbWVhbnMgdGhhdCB0aGUgYnJvd3NlciBQS0kgY2Fubm90IGJlIHVzZWQgdG8KYXV0aGVudGlj
YXRlIGhvc3RzLiBUaGlzIHNlZW1zIHF1aXRlIHdyb25nLgoKKiBOb3QgYWxsIENNUyBhbGdvcml0
aG0gcGFyYW1ldGVycyBhcmUgbmVnb3RpYXRlZCBhdCB0aGUgTlRTIGxheWVyLCBhcwpzdXNwZWN0
ZWQuIChEKQoKIyBkcmFmdC1pZXRmLW50cC11c2luZy1udHMtZm9yLW50cC0wMAoKKiBUaGVyZSBp
cyBubyBjb29raWUgcHJvdGVjdGlvbiBvZiBzZXJ2ZXJfYXNzb2Mvc2VydmVyX2Nvb2sgcmVzcG9u
c2VzLAphcyBleHBsYWluZWQgYWJvdmUuIFRoaXMgaXMgcXVpdGUgYmFkLiAoRCkKCiogVGhlIHBy
b3Bvc2VkIHByb3RvY29sIGRvZXMgbm90IGFkZHJlc3MgVURQIG1lc3NhZ2Ugc2l6ZSBsaW1pdGF0
aW9ucy4KVURQIGZyYWdtZW50YXRpb24gaXMgZnVuZGFtZW50YWxseSBicm9rZW4uIChEKQoKLS0g
CkZsb3JpYW4gV2VpbWVyIC8gUmVkIEhhdCBQcm9kdWN0IFNlY3VyaXR5Cl9fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fCm50cHdnIG1haWxpbmcgbGlzdApudHB3
Z0BsaXN0cy5udHAub3JnCmh0dHA6Ly9saXN0cy5udHAub3JnL2xpc3RpbmZvL250cHdn

From ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org  Fri Apr  3 06:47:26 2015
Return-Path: <ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org>
X-Original-To: ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com
Delivered-To: ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9E1AE1A92FA for <ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com>; Fri,  3 Apr 2015 06:47:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.21
X-Spam-Level:
X-Spam-Status: No, score=-4.21 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 HubN_SBSLq2j for <ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com>; Fri,  3 Apr 2015 06:47:25 -0700 (PDT)
Received: from lists.ntp.org (lists.ntp.org [149.20.68.7]) by ietfa.amsl.com (Postfix) with ESMTP id 626A31A92F9 for <ntp-archives-ahFae6za@lists.ietf.org>; Fri,  3 Apr 2015 06:47:25 -0700 (PDT)
Received: from lists.ntp.org (lists.ntp.org [149.20.68.7]) by lists.ntp.org (Postfix) with ESMTP id 4E31686DAEB for <ntp-archives-ahFae6za@lists.ietf.org>; Fri,  3 Apr 2015 13:47:25 +0000 (UTC)
X-Original-To: ntpwg@lists.ntp.org
Delivered-To: ntpwg@lists.ntp.org
Received: from mail1.ntp.org (mail1.ntp.org [IPv6:2001:4f8:fff7:1::5]) by lists.ntp.org (Postfix) with ESMTP id 784A386D489 for <ntpwg@lists.ntp.org>; Fri,  3 Apr 2015 13:28:15 +0000 (UTC)
Received: from uillean.fuaim.com ([206.197.161.140]) by mail1.ntp.org with esmtps (TLSv1:AES256-SHA:256) (Exim 4.77 (FreeBSD)) (envelope-from <brian@innovationslab.net>) id 1Ye1dl-000A3T-7g for ntpwg@lists.ntp.org; Fri, 03 Apr 2015 13:28:15 +0000
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 1C0C18810D for <ntpwg@lists.ntp.org>; Fri,  3 Apr 2015 06:28:05 -0700 (PDT)
Received: from clemson.local (unknown [76.21.129.88]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by clairseach.fuaim.com (Postfix) with ESMTP id D1CDA136833C for <ntpwg@lists.ntp.org>; Fri,  3 Apr 2015 06:28:04 -0700 (PDT)
Message-ID: <551E9563.1080608@innovationslab.net>
Date: Fri, 03 Apr 2015 09:28:03 -0400
From: Brian Haberman <brian@innovationslab.net>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:31.0) Gecko/20100101 Thunderbird/31.6.0
MIME-Version: 1.0
To: ntpwg@lists.ntp.org
References: <DB5PR03MB0999879FC625523135DDD301E50B0@DB5PR03MB0999.eurprd03.prod.outlook.com> <AM3PR06MB1202AF4AA0461F08757D12ECD2F40@AM3PR06MB1202.eurprd06.prod.outlook.com>
In-Reply-To: <AM3PR06MB1202AF4AA0461F08757D12ECD2F40@AM3PR06MB1202.eurprd06.prod.outlook.com>
X-SA-Exim-Connect-IP: 206.197.161.140
X-SA-Exim-Rcpt-To: ntpwg@lists.ntp.org
X-SA-Exim-Mail-From: brian@innovationslab.net
X-SA-Exim-Version: 4.2
X-SA-Exim-Scanned: Yes (on mail1.ntp.org)
Subject: Re: [ntpwg] TICTOC wiki page
X-BeenThere: ntpwg@lists.ntp.org
X-Mailman-Version: 2.1.14
Precedence: list
List-Id: IETF Working Group for Network Time Protocol <ntpwg.lists.ntp.org>
List-Unsubscribe: <http://lists.ntp.org/options/ntpwg>, <mailto:ntpwg-request@lists.ntp.org?subject=unsubscribe>
List-Archive: <http://lists.ntp.org/pipermail/ntpwg>
List-Post: <mailto:ntpwg@lists.ntp.org>
List-Help: <mailto:ntpwg-request@lists.ntp.org?subject=help>
List-Subscribe: <http://lists.ntp.org/listinfo/ntpwg>, <mailto:ntpwg-request@lists.ntp.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============2622927680636997666=="
Errors-To: ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org
Sender: ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--===============2622927680636997666==
Content-Type: multipart/signed; micalg=pgp-sha512;
 protocol="application/pgp-signature";
 boundary="WmiO5vva1TuB9ghmOWROOWp6nbAxHEUKv"

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--WmiO5vva1TuB9ghmOWROOWp6nbAxHEUKv
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable



On 3/31/15 1:56 PM, Denis Reilly wrote:
> I like the idea of using a wiki to exchange ideas (in addition to the
> list).  In fact, it would be nice if we could start up a wiki to take
> suggestions for the NTP BCP document that we discussed last week.
>=20
> Karen, I've looked at http://trac.tools.ietf.org/wg/ntp/ and there
> does not seem to be a Wiki active. Is that something that we can
> start there?

The NTP WG wiki is now available at:

http://tools.ietf.org/wg/ntp/

Regards,
Brian


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

-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2.0.20 (Darwin)
Comment: GPGTools - https://gpgtools.org

iQEcBAEBCgAGBQJVHpVjAAoJEBOZRqCi7goqC4wIAKQAlDjoeyw4TCvRIOvjQen+
UWVeBYN5remNMVyIMytSQ/YHjMUCvyxSV4Ieq2l2QM5SVmthwoDVSsyLBFItEFON
1/hcToV+myv9gPKSjUEzUrsfXtTyZNDmf633j7fVCGDOX7daHx0B2ZiTM4ElW8be
Xy+fBZHUYq+r6X/lqwZUhbOuZEKkTOufybjOdOuraYTgwYXWt6qdBAJ6l8JvItG9
czQrxgbx6ow7UJMnjYk0nL33CiHK6gaiyXC7mNSckCjooXYYYxs4I1cV91VRD2Yy
Gj+O3ELEKAiaLBycjCS+2aoWBFalbcImrsLuZpSkR+TOTZCnWzftls8rM3tboT4=
=nefJ
-----END PGP SIGNATURE-----

--WmiO5vva1TuB9ghmOWROOWp6nbAxHEUKv--

--===============2622927680636997666==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

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

From ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org  Fri Apr  3 10:47:08 2015
Return-Path: <ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org>
X-Original-To: ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com
Delivered-To: ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BB9121ACE1C for <ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com>; Fri,  3 Apr 2015 10:47:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level:
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 lPowo5fzbowN for <ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com>; Fri,  3 Apr 2015 10:47:07 -0700 (PDT)
Received: from lists.ntp.org (lists.ntp.org [IPv6:2001:4f8:fff7:1::7]) by ietfa.amsl.com (Postfix) with ESMTP id 9FF321ACE13 for <ntp-archives-ahFae6za@lists.ietf.org>; Fri,  3 Apr 2015 10:47:07 -0700 (PDT)
Received: from lists.ntp.org (lists.ntp.org [149.20.68.7]) by lists.ntp.org (Postfix) with ESMTP id 93D9686DAD1 for <ntp-archives-ahFae6za@lists.ietf.org>; Fri,  3 Apr 2015 17:47:07 +0000 (UTC)
X-Original-To: ntpwg@lists.ntp.org
Delivered-To: ntpwg@lists.ntp.org
Received: from stenn.ntp.org (stenn.ntp.org [IPv6:2001:4f8:fff7:1::30]) by lists.ntp.org (Postfix) with ESMTP id 6E47786D489 for <ntpwg@lists.ntp.org>; Fri,  3 Apr 2015 17:23:12 +0000 (UTC)
Received: from localhost.ntp.org ([::1] helo=stenn.ntp.org) by stenn.ntp.org with esmtp (Exim 4.84 (FreeBSD)) (envelope-from <stenn@stenn.ntp.org>) id 1Ye5JI-000NDd-2i; Fri, 03 Apr 2015 17:23:12 +0000
From: Harlan Stenn <stenn@ntp.org>
To: Brian Haberman <brian@innovationslab.net>
In-reply-to: <551E9563.1080608@innovationslab.net>
References: <DB5PR03MB0999879FC625523135DDD301E50B0@DB5PR03MB0999.eurprd03.prod.outlook.com> <AM3PR06MB1202AF4AA0461F08757D12ECD2F40@AM3PR06MB1202.eurprd06.prod.outlook.com> <551E9563.1080608@innovationslab.net>
Comments: In-reply-to Brian Haberman <brian@innovationslab.net> message dated "Fri, 03 Apr 2015 09:28:03 -0400."
X-Mailer: MH-E 7.4.2; nmh 1.6; XEmacs 21.4 (patch 22)
Mime-Version: 1.0 (generated by tm-edit 1.8)
Date: Fri, 03 Apr 2015 17:23:12 +0000
Message-Id: <E1Ye5JI-000NDd-2i@stenn.ntp.org>
Cc: ntpwg@lists.ntp.org
Subject: Re: [ntpwg] TICTOC wiki page
X-BeenThere: ntpwg@lists.ntp.org
X-Mailman-Version: 2.1.14
Precedence: list
List-Id: IETF Working Group for Network Time Protocol <ntpwg.lists.ntp.org>
List-Unsubscribe: <http://lists.ntp.org/options/ntpwg>, <mailto:ntpwg-request@lists.ntp.org?subject=unsubscribe>
List-Archive: <http://lists.ntp.org/pipermail/ntpwg>
List-Post: <mailto:ntpwg@lists.ntp.org>
List-Help: <mailto:ntpwg-request@lists.ntp.org?subject=help>
List-Subscribe: <http://lists.ntp.org/listinfo/ntpwg>, <mailto:ntpwg-request@lists.ntp.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org
Sender: ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org

And if anybody thinks content from the previous wiki at:

 http://support.ntp.org/bin/view/IETF/WebHome

should be moved to the new wiki, please feel free...
-- 
Harlan Stenn <stenn@ntp.org>
http://networktimefoundation.org - be a member!
_______________________________________________
ntpwg mailing list
ntpwg@lists.ntp.org
http://lists.ntp.org/listinfo/ntpwg

From ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org  Sun Apr  5 21:03:58 2015
Return-Path: <ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org>
X-Original-To: ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com
Delivered-To: ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 78B3C1A00F4 for <ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com>; Sun,  5 Apr 2015 21:03:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.011
X-Spam-Level:
X-Spam-Status: No, score=-0.011 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 Le-s-BT1aVY9 for <ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com>; Sun,  5 Apr 2015 21:03:56 -0700 (PDT)
Received: from psp3.ntp.org (psp3.ntp.org [149.20.68.23]) by ietfa.amsl.com (Postfix) with ESMTP id D9E0E1A00F3 for <ntp-archives-ahFae6za@lists.ietf.org>; Sun,  5 Apr 2015 21:03:56 -0700 (PDT)
Received: from psp3.ntp.org (localhost.ntp.org [127.0.0.1]) by psp3.ntp.org (Postfix) with ESMTP id 22647398F6 for <ntp-archives-ahFae6za@lists.ietf.org>; Sun,  5 Apr 2015 21:03:55 -0700 (PDT)
X-Original-To: ntpwg@lists.ntp.org
Delivered-To: ntpwg@lists.ntp.org
Received: from mail1.ntp.org (mail1.ntp.org [IPv6:2001:4f8:fff7:1::5]) by lists.ntp.org (Postfix) with ESMTP id 8133D86D2C0 for <ntpwg@lists.ntp.org>; Sun,  5 Apr 2015 16:25:53 +0000 (UTC)
Received: from chessie.everett.org ([2001:470:1:205::234]) by mail1.ntp.org with esmtp (Exim 4.77 (FreeBSD)) (envelope-from <rwelty@nwtime.org>) id 1YenMm-0003ct-HW for ntpwg@lists.ntp.org; Sun, 05 Apr 2015 16:25:53 +0000
Received: from localhost (localhost [127.0.0.1]) by chessie.everett.org (Postfix) with SMTP id 30A14B80B for <ntpwg@lists.ntp.org>; Sun,  5 Apr 2015 16:25:39 +0000 (UTC)
Received: from Richards-MacBook-Air-2.local (cpe-74-70-243-84.nycap.res.rr.com [74.70.243.84]) by chessie.everett.org (Postfix) with ESMTPSA id 794C3B808 for <ntpwg@lists.ntp.org>; Sun,  5 Apr 2015 16:25:38 +0000 (UTC)
Message-ID: <55216200.8030708@nwtime.org>
Date: Sun, 05 Apr 2015 12:25:36 -0400
From: Richard Welty <rwelty@nwtime.org>
Organization: Network Time Foundation
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:31.0) Gecko/20100101 Thunderbird/31.6.0
MIME-Version: 1.0
To: ntpwg@lists.ntp.org
References: <551D1150.5080500@redhat.com>
In-Reply-To: <551D1150.5080500@redhat.com>
X-DSPAM-Result: Innocent
X-DSPAM-Processed: Sun Apr  5 16:25:38 2015
X-DSPAM-Confidence: 1.0000
X-DSPAM-Probability: 0.0023
X-DSPAM-Signature: 6384,55216202473991114312177
X-SA-Exim-Connect-IP: 2001:470:1:205::234
X-SA-Exim-Rcpt-To: ntpwg@lists.ntp.org
X-SA-Exim-Mail-From: rwelty@nwtime.org
X-SA-Exim-Version: 4.2
X-SA-Exim-Scanned: Yes (on mail1.ntp.org)
X-Mailman-Approved-At: Mon, 06 Apr 2015 04:03:52 +0000
Subject: Re: [ntpwg] Comments on various NTS drafts
X-BeenThere: ntpwg@lists.ntp.org
X-Mailman-Version: 2.1.20
Precedence: list
List-Id: IETF Working Group for Network Time Protocol <ntpwg.lists.ntp.org>
List-Unsubscribe: <http://lists.ntp.org/options/ntpwg>, <mailto:ntpwg-request@lists.ntp.org?subject=unsubscribe>
List-Archive: <http://lists.ntp.org/pipermail/ntpwg/>
List-Post: <mailto:ntpwg@lists.ntp.org>
List-Help: <mailto:ntpwg-request@lists.ntp.org?subject=help>
List-Subscribe: <http://lists.ntp.org/listinfo/ntpwg>, <mailto:ntpwg-request@lists.ntp.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org
Sender: "ntpwg" <ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

On 4/2/15 5:52 AM, Florian Weimer wrote:
> Here are a few comments on those drafts.  I hope they are useful.

thanks for the comments. i will defer to others on the security
considerations; my role here is as an implementer. specifically,
i'm supposed to start on modifications to to the ntpd reference
implementation sometime in the next week or so with an eye towards
reporting massive progress (hopefully completion of the first
version) at the next IETF.

so i have concerns about these kinds of changes in the draft
as they will effectively prevent that effort from starting for
some time. speaking as the developer, i suspect that a DTLS based
version would be easier to write at the end of the day - but it
won't get finished per the current schedule because there is no
spec for it and wouldn't be for a while.

richard

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - http://gpgtools.org

iQIcBAEBCAAGBQJVIWH/AAoJEBg+LdNh/YEcNFsQAJpdfPysMhT3R+7AD1/NWFsM
uq2SB7xqtHaRkLs7wGMAQKQOOwPRJhfmU9BgXU4dVI78akgJ4rD12i8vmpdfVXf9
FtYd7yUSTvh7KMcuCPLxt56av2ZM3kUkVnZJ1YxIl3VIOBq2XpbsUUnpEFIwc2gN
uobBaQF++P1FUdIwPuiSiHKHx3ykdtOiuY3VHmIzEOpm7LLMAFyEAqKEBVBp2D96
h+dlv6GiMQH3pwO7f5CTC8q2n3TG9kVyV5srq+KYy/bFFLlfqEOQWXT5H9gUogQW
Z6Zkb2byd/benEE+GBeEUkEwz+TT6Cx7KCK3fALAxZ5jMVyW7jk4B4A0sq8+Pp7I
j+RFnhocsvWja3CPt9UOtseaEZiHmnIxOKvbtcEhr9XBdidURmKk9nDmK5iQGeTW
60OHSJh1HE0UZzY85fGihHu45rdgmw/jukN8IJe55KglDyJTsq1fCMpqXYwVRQkg
asv20JNU4EOPzCgYdcR8Ah1LnUI0ou7jbEKTd6M/tpf78DY1QbF8LSGet5GthQBp
q8B5axfkKbXIjHRR9EwwvTg+4SsLzVAv7Ec0Ejq/S/ANTCUeorvRwjol/XE9qqGK
UIyLaqsTwycfZLrwLhgOW93ONc34de38kVUt2UgEL4CtYeHAmW6Cr9aUUtHYz7NF
TJajjNzxswdoy/N/zt8f
=6byy
-----END PGP SIGNATURE-----

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

From ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org  Tue Apr  7 02:15:30 2015
Return-Path: <ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org>
X-Original-To: ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com
Delivered-To: ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 547DF1B334E for <ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com>; Tue,  7 Apr 2015 02:15:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level:
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 qvzltGSEOjRP for <ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com>; Tue,  7 Apr 2015 02:15:28 -0700 (PDT)
Received: from psp3.ntp.org (psp3.ntp.org [149.20.68.23]) by ietfa.amsl.com (Postfix) with ESMTP id DC38B1B334C for <ntp-archives-ahFae6za@lists.ietf.org>; Tue,  7 Apr 2015 02:15:28 -0700 (PDT)
Received: from psp3.ntp.org (localhost.ntp.org [127.0.0.1]) by psp3.ntp.org (Postfix) with ESMTP id 7A6DF3991C for <ntp-archives-ahFae6za@lists.ietf.org>; Tue,  7 Apr 2015 02:15:28 -0700 (PDT)
X-Original-To: ntpwg@lists.ntp.org
Delivered-To: ntpwg@lists.ntp.org
Received: from mail1.ntp.org (mail1.ntp.org [IPv6:2001:4f8:fff7:1::5]) by lists.ntp.org (Postfix) with ESMTP id 3BBA086D39A for <ntpwg@lists.ntp.org>; Tue,  7 Apr 2015 09:15:25 +0000 (UTC)
Received: from mx1.redhat.com ([209.132.183.28]) by mail1.ntp.org with esmtps (TLSv1:AES256-SHA:256) (Exim 4.77 (FreeBSD)) (envelope-from <fweimer@redhat.com>) id 1YfPbH-000CLH-ID for ntpwg@lists.ntp.org; Tue, 07 Apr 2015 09:15:25 +0000
Received: from int-mx11.intmail.prod.int.phx2.redhat.com (int-mx11.intmail.prod.int.phx2.redhat.com [10.5.11.24]) by mx1.redhat.com (8.14.4/8.14.4) with ESMTP id t379FEGX030036 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=FAIL); Tue, 7 Apr 2015 05:15:15 -0400
Received: from oldenburg.str.redhat.com (oldenburg.str.redhat.com [10.33.200.60]) by int-mx11.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4) with ESMTP id t379FDYW023654 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 7 Apr 2015 05:15:14 -0400
Message-ID: <5523A020.8090505@redhat.com>
Date: Tue, 07 Apr 2015 11:15:12 +0200
From: Florian Weimer <fweimer@redhat.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.6.0
MIME-Version: 1.0
To: rwelty@nwtime.org
References: <551D1150.5080500@redhat.com> <55216200.8030708@nwtime.org>
In-Reply-To: <55216200.8030708@nwtime.org>
X-Scanned-By: MIMEDefang 2.68 on 10.5.11.24
X-SA-Exim-Connect-IP: 209.132.183.28
X-SA-Exim-Rcpt-To: ntpwg@lists.ntp.org
X-SA-Exim-Mail-From: fweimer@redhat.com
X-SA-Exim-Version: 4.2
X-SA-Exim-Scanned: Yes (on mail1.ntp.org)
Subject: Re: [ntpwg] Comments on various NTS drafts
X-BeenThere: ntpwg@lists.ntp.org
X-Mailman-Version: 2.1.20
Precedence: list
List-Id: IETF Working Group for Network Time Protocol <ntpwg.lists.ntp.org>
List-Unsubscribe: <http://lists.ntp.org/options/ntpwg>, <mailto:ntpwg-request@lists.ntp.org?subject=unsubscribe>
List-Archive: <http://lists.ntp.org/pipermail/ntpwg/>
List-Post: <mailto:ntpwg@lists.ntp.org>
List-Help: <mailto:ntpwg-request@lists.ntp.org?subject=help>
List-Subscribe: <http://lists.ntp.org/listinfo/ntpwg>, <mailto:ntpwg-request@lists.ntp.org?subject=subscribe>
Cc: ntpwg@lists.ntp.org
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org
Sender: "ntpwg" <ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org>

On 04/05/2015 06:25 PM, Richard Welty wrote:
> On 4/2/15 5:52 AM, Florian Weimer wrote:
>> Here are a few comments on those drafts.  I hope they are
>> useful.
> 
> thanks for the comments. i will defer to others on the security 
> considerations; my role here is as an implementer. specifically, 
> i'm supposed to start on modifications to to the ntpd reference 
> implementation sometime in the next week or so with an eye towards 
> reporting massive progress (hopefully completion of the first 
> version) at the next IETF.
> 
> so i have concerns about these kinds of changes in the draft as
> they will effectively prevent that effort from starting for some
> time. speaking as the developer, i suspect that a DTLS based 
> version would be easier to write at the end of the day - but it 
> won't get finished per the current schedule because there is no 
> spec for it and wouldn't be for a while.

I can see that this is a problem.

Do you plan to use the CMS support in OpenSSL, or write it from
scratch (perhaps on top of the OpenSSL ASN.1/DER framework)?

Unfortunately, I don't know how controversial a switch to DTLS would
be.  The downside is that the per-client state the server has to keep
is more visible.  (The current proposal probably needs per-client
state in the form of kernel IP reassembly buffers, too, depending on
what kind of PKI is used.)

-- 
Florian Weimer / Red Hat Product Security
_______________________________________________
ntpwg mailing list
ntpwg@lists.ntp.org
http://lists.ntp.org/listinfo/ntpwg

From ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org  Tue Apr  7 17:54:20 2015
Return-Path: <ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org>
X-Original-To: ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com
Delivered-To: ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 439811B2A68 for <ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com>; Tue,  7 Apr 2015 17:54:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level:
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 7p9ZPPWJs-nd for <ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com>; Tue,  7 Apr 2015 17:54:12 -0700 (PDT)
Received: from psp3.ntp.org (psp3.ntp.org [149.20.68.23]) by ietfa.amsl.com (Postfix) with ESMTP id 63E0A1B2A69 for <ntp-archives-ahFae6za@lists.ietf.org>; Tue,  7 Apr 2015 17:54:12 -0700 (PDT)
Received: from psp3.ntp.org (localhost.ntp.org [127.0.0.1]) by psp3.ntp.org (Postfix) with ESMTP id B670F398E1 for <ntp-archives-ahFae6za@lists.ietf.org>; Tue,  7 Apr 2015 17:54:10 -0700 (PDT)
X-Original-To: ntpwg@lists.ntp.org
Delivered-To: ntpwg@lists.ntp.org
Received: from mail1.ntp.org (mail1.ntp.org [IPv6:2001:4f8:fff7:1::5]) by lists.ntp.org (Postfix) with ESMTP id 0A8F386D2C0 for <ntpwg@lists.ntp.org>; Wed,  8 Apr 2015 00:54:07 +0000 (UTC)
Received: from chessie.everett.org ([2001:470:1:205::234]) by mail1.ntp.org with esmtp (Exim 4.77 (FreeBSD)) (envelope-from <rwelty@nwtime.org>) id 1YfeFj-0000jg-0j for ntpwg@lists.ntp.org; Wed, 08 Apr 2015 00:54:07 +0000
Received: from localhost (localhost [127.0.0.1]) by chessie.everett.org (Postfix) with SMTP id 2F636B80D for <ntpwg@lists.ntp.org>; Wed,  8 Apr 2015 00:53:53 +0000 (UTC)
Received: from Richards-MacBook-Air-2.local (cpe-74-70-243-84.nycap.res.rr.com [74.70.243.84]) by chessie.everett.org (Postfix) with ESMTPSA id CEC80B80B; Wed,  8 Apr 2015 00:53:51 +0000 (UTC)
Message-ID: <55247C1D.7000803@nwtime.org>
Date: Tue, 07 Apr 2015 20:53:49 -0400
From: Richard Welty <rwelty@nwtime.org>
Organization: Network Time Foundation
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:31.0) Gecko/20100101 Thunderbird/31.6.0
MIME-Version: 1.0
To: Florian Weimer <fweimer@redhat.com>
References: <551D1150.5080500@redhat.com> <55216200.8030708@nwtime.org> <5523A020.8090505@redhat.com>
In-Reply-To: <5523A020.8090505@redhat.com>
X-DSPAM-Result: Innocent
X-DSPAM-Processed: Wed Apr  8 00:53:52 2015
X-DSPAM-Confidence: 1.0000
X-DSPAM-Probability: 0.0023
X-DSPAM-Signature: 6384,55247c20473991956315895
X-SA-Exim-Connect-IP: 2001:470:1:205::234
X-SA-Exim-Rcpt-To: ntpwg@lists.ntp.org
X-SA-Exim-Mail-From: rwelty@nwtime.org
X-SA-Exim-Version: 4.2
X-SA-Exim-Scanned: Yes (on mail1.ntp.org)
Subject: Re: [ntpwg] Comments on various NTS drafts
X-BeenThere: ntpwg@lists.ntp.org
X-Mailman-Version: 2.1.20
Precedence: list
List-Id: IETF Working Group for Network Time Protocol <ntpwg.lists.ntp.org>
List-Unsubscribe: <http://lists.ntp.org/options/ntpwg>, <mailto:ntpwg-request@lists.ntp.org?subject=unsubscribe>
List-Archive: <http://lists.ntp.org/pipermail/ntpwg/>
List-Post: <mailto:ntpwg@lists.ntp.org>
List-Help: <mailto:ntpwg-request@lists.ntp.org?subject=help>
List-Subscribe: <http://lists.ntp.org/listinfo/ntpwg>, <mailto:ntpwg-request@lists.ntp.org?subject=subscribe>
Cc: ntpwg@lists.ntp.org
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org
Sender: "ntpwg" <ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

[for some reason, thunderbird sent this originally with wrong
from address; resending from the right one]

On 4/7/15 5:15 AM, Florian Weimer wrote:
> I can see that this is a problem.
> 
> Do you plan to use the CMS support in OpenSSL, or write it from 
> scratch (perhaps on top of the OpenSSL ASN.1/DER framework)?

i was planning to use the support in OpenSSL. it is incompletely
documented, but the developers on openssl-dev are responsive
so that's ok.

richard

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - http://gpgtools.org

iQIcBAEBCAAGBQJVJHwdAAoJEBg+LdNh/YEcohYP/1NDth/jYi7z1THQMIEo6qmr
BKrxFhvoyLoednOAu9DKLzR4DI3Be6PxMTQ+pUWijHYBPDJ3feDgvYg7hKZYXzEM
v57xEoWJoFHzcKZa8qQgbq7WbToOSxfE2ka7e4aJonY4h8sbjHtShH1bWhcx00Og
YUUgwxFzNJrWQRcztBmXsFyVaTRrZZKjttKjAzzBMnlHHAi2nRlR3T6dIJJDIAYy
oD5HYpbwO2IRFvo1dmRSePXJ+kPwt87XTX1jHhfcZ7F2cSVoT2wJMMxhmGkGyEZA
a4GfaMRLnx6I9gSzCZde8rvm9dmu14hQojGF9hPoq654155+ucdt3FAW7+ZYpwsw
Ql7K0omdceHCNMpdrTWC7qL9Mw+nxtxC50og1RRzEKZU7DZIE7Z8a96qxE5wLfbS
VpvOOhPS705G4lztOosy/pdeDFUWOZxceiyaDckofuWGHKL7v6BB9xlcaqCuE4UH
nPdckYduJKb/kG2N4lG6Mmy9W+/JqN9s/wP55A0A3XL/zMF7nVn+CiqPbR72gc/m
lfdy4I5KZ4FV0Gopli/EVXTXIw2YAkIsm1WIE5C0xqtCIAqY6OH03mW/D3CE0wkH
tPiAJblz0Tg2C7T8629uYaN9DT7nBsPai1mWpdm61pMZ/+sgDSCPlWWDgTzpggb1
/JnvCqYyJ8HnyLTr440i
=1RKP
-----END PGP SIGNATURE-----

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

From ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org  Tue Apr 14 21:09:22 2015
Return-Path: <ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org>
X-Original-To: ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com
Delivered-To: ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7906D1B2B9E for <ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com>; Tue, 14 Apr 2015 21:09:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.01
X-Spam-Level:
X-Spam-Status: No, score=-0.01 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, HTML_MESSAGE=0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 KexPwDRxUg2n for <ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com>; Tue, 14 Apr 2015 21:09:19 -0700 (PDT)
Received: from psp3.ntp.org (psp3.ntp.org [149.20.68.23]) by ietfa.amsl.com (Postfix) with ESMTP id 324E21B2B9F for <ntp-archives-ahFae6za@lists.ietf.org>; Tue, 14 Apr 2015 21:09:19 -0700 (PDT)
Received: from psp3.ntp.org (localhost.ntp.org [127.0.0.1]) by psp3.ntp.org (Postfix) with ESMTP id 09466398FB for <ntp-archives-ahFae6za@lists.ietf.org>; Tue, 14 Apr 2015 21:09:19 -0700 (PDT)
X-Original-To: ntpwg@lists.ntp.org
Delivered-To: ntpwg@lists.ntp.org
Received: from mail1.ntp.org (mail1.ntp.org [IPv6:2001:4f8:fff7:1::5]) by lists.ntp.org (Postfix) with ESMTP id F149086D33C for <ntpwg@lists.ntp.org>; Sun, 12 Apr 2015 03:06:35 +0000 (UTC)
Received: from mx1.bs.ptb.de ([192.53.103.106]) by mail1.ntp.org with esmtps (TLSv1:AES256-SHA:256) (Exim 4.77 (FreeBSD)) (envelope-from <dieter.sibold@ptb.de>) id 1Yh8E4-0002tU-GW for ntpwg@lists.ntp.org; Sun, 12 Apr 2015 03:06:35 +0000
Received: from mx1.bs.ptb.de (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id 7D0F3D6E3ED; Fri, 10 Apr 2015 16:53:52 +0200 (CEST)
Received: from rose.bs.ptb.de (rose.bs.ptb.de [141.25.85.201]) by mx1.bs.ptb.de (Postfix) with ESMTP id 69541D6DF95; Fri, 10 Apr 2015 16:53:52 +0200 (CEST)
In-Reply-To: <552663D3.7040005@redhat.com>
References: <551D1150.5080500@redhat.com> <OF1F8E2A91.0B970EC7-ONC1257E22.00357A53-C1257E22.00381DAC@ptb.de> <552663D3.7040005@redhat.com>
To: Florian Weimer <fweimer@redhat.com>
MIME-Version: 1.0
X-KeepSent: 8C2E5A2A:E24A2F5A-C1257E23:00500707; type=4; name=$KeepSent
X-Mailer: IBM Notes Release 9.0.1FP3 January  12, 2015
Message-ID: <OF8C2E5A2A.E24A2F5A-ONC1257E23.00500707-C1257E23.0051D4E9@ptb.de>
From: dieter.sibold@ptb.de
Date: Fri, 10 Apr 2015 16:53:49 +0200
X-MIMETrack: S/MIME Sign by eclipse on Dieter Sibold/PTB(Release 9.0.1FP3|January 12, 2015) at 10.04.2015 16:53:49, Serialize by eclipse on Dieter Sibold/PTB(Release 9.0.1FP3|January  12, 2015) at 10.04.2015 16:53:49, Serialize complete at 10.04.2015 16:53:49, Itemize by eclipse on Dieter Sibold/PTB(Release 9.0.1FP3|January  12, 2015) at 10.04.2015 16:53:50, S/MIME Sign complete at 10.04.2015 16:53:50, Serialize by Router on ROSE/PTB(Release 9.0.1FP3HF79 | February 9, 2015) at 04/10/2015 16:53:52, Serialize complete at 04/10/2015 16:53:52
X-SA-Exim-Connect-IP: 192.53.103.106
X-SA-Exim-Rcpt-To: ntpwg@lists.ntp.org
X-SA-Exim-Mail-From: dieter.sibold@ptb.de
X-SA-Exim-Version: 4.2
X-SA-Exim-Scanned: Yes (on mail1.ntp.org)
Subject: [ntpwg] Antwort: Re:  Comments on various NTS drafts
X-BeenThere: ntpwg@lists.ntp.org
X-Mailman-Version: 2.1.20
Precedence: list
List-Id: IETF Working Group for Network Time Protocol <ntpwg.lists.ntp.org>
List-Unsubscribe: <http://lists.ntp.org/options/ntpwg>, <mailto:ntpwg-request@lists.ntp.org?subject=unsubscribe>
List-Archive: <http://lists.ntp.org/pipermail/ntpwg/>
List-Post: <mailto:ntpwg@lists.ntp.org>
List-Help: <mailto:ntpwg-request@lists.ntp.org?subject=help>
List-Subscribe: <http://lists.ntp.org/listinfo/ntpwg>, <mailto:ntpwg-request@lists.ntp.org?subject=subscribe>
Cc: ntpwg@lists.ntp.org
Content-Type: multipart/mixed; boundary="===============6533233339730305613=="
Errors-To: ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org
Sender: "ntpwg" <ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org>

This is an S/MIME signed message.

--===============6533233339730305613==
Content-Type: multipart/signed;
	 protocol="application/x-pkcs7-signature";
	 micalg=sha1;
	 boundary=-------z35978_boundary_sign

This is an S/MIME signed message.

---------z35978_boundary_sign
Content-Type: multipart/alternative; boundary="=_alternative 0051D4E8C1257E23_="

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

Thanks for comments. See replies inline.


Florian Weimer <fweimer@redhat.com> schrieb am 09.04.2015 13:34:43:

> Von: Florian Weimer <fweimer@redhat.com>
> An: dieter.sibold@ptb.de
> Kopie: ntpwg@lists.ntp.org
> Datum: 09.04.2015 13:34
> Betreff: Re: [ntpwg] Comments on various NTS drafts
> 
> On 04/09/2015 12:12 PM, dieter.sibold@ptb.de wrote:
> 
> > thanks for your comments and recommendations. We'll carefully look 
into 
> > your comments. We already addressed some of your comments (see 
inline). 
> 
> Thanks.
> 
> > Regarding DTLS. Please keep in mind that DTLS requires a layer 3 
> > communication. With PTP we also have to consider layer 2 communication 

> > channels where DTLS is not applicable.
> 
> I think this is based on a misconception.  DTLS requires a datagram
> transport, and it has its own fragmentation support, so it should be
> perfectly possible to run it on top of a layer 2 transport which has
> sufficient frame size (such as Ethernet).
> 
> Per-client server-side state would only need to be maintained during the
> initial handshake, and not to answer subsequent time queries from
> clients (but maintaining such state may be a performance optimization).
> 
> >> Section 5.6.1 requires frequent key refresh. This is impossible to
> >> implement in practice (ultimate keys cannot be refreshed without
> >> operator intervention), and not necessary as long as sufficiently 
strong
> >> cryptographic primitives (non-broken algorithms) are used.
> > 
> > We don't see a problem with this requirement.
> 
> You do not periodically refresh asymmetric keys used for the initial
> handshake.

No, not the asymmetric keys but for example a random seed value, which 
will result in a key refreshment.

> 
> > For clarification. Do you propose to abandon key refreshment at all?
> 
> Yes, the message rate is not sufficiently high that this would pose a
> problem.  You just have to use cryptographic primitives which are not
> known to be broken.
> 
> >> In addition, RFC 7384, Section 3.2.10 indicates that securing the 
time
> >> source of an entire organization from an external source is out of
> >> scope. However, this is likely the most common application of a 
security
> >> time protocol.
> > 
> > Please note, that 3.2.10 refers to the connection of reference time 
(such 
> > as GPS, Radio transmitter, ...) to the PTP grandmaster or NTP stratum 
1 
> > server. These are basically non-IP or non-Ethernet connections and 
> > therefore out of scope. 
> 
> I expect that rather soon, there will be a requirement to import time in
> a secure way from one of the national time sources such as PTB or NIST.
>  (NIST already offers an authenticated time service.)
>
Time is already disseminated by the national laboratories by means of NTP. 
One of the intention of NTS is to secure this process. Yes, it is true 
that NIST is offering a secured NTP access. But this is done by means of 
the symmetric pre-shared key approach which is available since NTP version 
3. Also PTB is going to offer this service for a limited number of 
applications.  Therefore secure time dissemination of national 
laboratories is not out of scope of this section. But out of scope is the 
cryptographic protections of protocols like GPS, IRIG-B, etc. which are 
often used to provide time information to the national time servers. That 
is what section 3.2.10 is talking about.

> 
> I still haven't read the relevant regulation, though, and it's likely
> still ambiguous in this regard.
> 
> >> * The integrity checks on the server_assoc response are unclear. It 
is
> >> not specified if host name verification is performed. (D)
> > 
> > This should be ensured via CMS. But we will check this.
> 
> Host name checks are out of scope for CMS, so you have to specify
> something on your own.
> 
> >> * Client certificate management is a red flag for many organizations. 
It
> >> would be better if the protocol would not use a client certificate at
> >> all, and some other key agreement scheme (e.g., application key
> >> extraction with TLS/DTLS, without client certificates, or a TLS 
response
> >> containing an encrypted session key). (D)
> > 
> > We want to have certificates in order to have a mean to provide 
> > authorization.
> 
> I think it would be best to make them optional.
> 
> >> * With a server without per-client state, the HMAC key setup has to 
be
> >> performed on each response.  This is quite costly.  A different MAC
> >> could be quite a bit cheaper in terms of CPU overhead.
> >
> > Which MAC do you propose?
> 
> I'd have to do some research on this matter and will report back.  Not
> all technical choices will be acceptable to the IETF.
> 
> >> * I have doubts about the use of TESLA.
> 
> > For us TESLA seems to be an appropriate approach. Do you know a good 
> > alternative?
> 
> I'm afraid I do not.  (To be clear: If you do not have operational
> experience with TESLA that says otherwise, I suspect it will not work in
> practice.)
> 
> >> * Requiring a new OID in the Extended Key Usages attribute of
> >> certificates (section 4) means that the browser PKI cannot be used to
> >> authenticate hosts. This seems quite wrong.
> > 
> > Please describe the problem in more detail.
> 
> The existing guidelines for browser CAs discourage signing subscriber
> certificates with strange extKeyUsage fields, see these requirements
> documents: <https://cabforum.org/baseline-requirements-documents/>
> 
> >> # draft-ietf-ntp-using-nts-for-ntp-00
> >>
> >> * There is no cookie protection of server_assoc/server_cook 
responses,
> >> as explained above. This is quite bad. (D)
> > 
> > What exactly do you mean by cookie protection?
> 
> This is the lack of a Photuris cookie mentioned above.#

Thanks for clarification.

> 
> -- 
> Florian Weimer / Red Hat Product Security

--=_alternative 0051D4E8C1257E23_=
Content-Type: text/html; charset="US-ASCII"

<font size=2 face="sans-serif">Thanks for comments. See replies inline.<br>
</font>
<br>
<br><tt><font size=2>Florian Weimer &lt;fweimer@redhat.com&gt; schrieb
am 09.04.2015 13:34:43:<br>
<br>
&gt; Von: Florian Weimer &lt;fweimer@redhat.com&gt;</font></tt>
<br><tt><font size=2>&gt; An: dieter.sibold@ptb.de</font></tt>
<br><tt><font size=2>&gt; Kopie: ntpwg@lists.ntp.org</font></tt>
<br><tt><font size=2>&gt; Datum: 09.04.2015 13:34</font></tt>
<br><tt><font size=2>&gt; Betreff: Re: [ntpwg] Comments on various NTS
drafts</font></tt>
<br><tt><font size=2>&gt; <br>
&gt; On 04/09/2015 12:12 PM, dieter.sibold@ptb.de wrote:<br>
&gt; <br>
&gt; &gt; thanks for your comments and recommendations. We'll carefully
look into <br>
&gt; &gt; your comments. We already addressed some of your comments (see
inline). <br>
&gt; <br>
&gt; Thanks.<br>
&gt; <br>
&gt; &gt; Regarding DTLS. Please keep in mind that DTLS requires a layer
3 <br>
&gt; &gt; communication. With PTP we also have to consider layer 2 communication
<br>
&gt; &gt; channels where DTLS is not applicable.<br>
&gt; <br>
&gt; I think this is based on a misconception. &nbsp;DTLS requires a datagram<br>
&gt; transport, and it has its own fragmentation support, so it should
be<br>
&gt; perfectly possible to run it on top of a layer 2 transport which has<br>
&gt; sufficient frame size (such as Ethernet).<br>
&gt; <br>
&gt; Per-client server-side state would only need to be maintained during
the<br>
&gt; initial handshake, and not to answer subsequent time queries from<br>
&gt; clients (but maintaining such state may be a performance optimization).<br>
&gt; <br>
&gt; &gt;&gt; Section 5.6.1 requires frequent key refresh. This is impossible
to<br>
&gt; &gt;&gt; implement in practice (ultimate keys cannot be refreshed
without<br>
&gt; &gt;&gt; operator intervention), and not necessary as long as sufficiently
strong<br>
&gt; &gt;&gt; cryptographic primitives (non-broken algorithms) are used.<br>
&gt; &gt; <br>
&gt; &gt; We don't see a problem with this requirement.<br>
&gt; <br>
&gt; You do not periodically refresh asymmetric keys used for the initial<br>
&gt; handshake.</font></tt>
<br>
<br><tt><font size=2>No, not the asymmetric keys but for example a random
seed value, which will result in a key refreshment.</font></tt>
<br><tt><font size=2><br>
&gt; <br>
&gt; &gt; For clarification. Do you propose to abandon key refreshment
at all?<br>
&gt; <br>
&gt; Yes, the message rate is not sufficiently high that this would pose
a<br>
&gt; problem. &nbsp;You just have to use cryptographic primitives which
are not<br>
&gt; known to be broken.<br>
&gt; <br>
&gt; &gt;&gt; In addition, RFC 7384, Section 3.2.10 indicates that securing
the time<br>
&gt; &gt;&gt; source of an entire organization from an external source
is out of<br>
&gt; &gt;&gt; scope. However, this is likely the most common application
of a security<br>
&gt; &gt;&gt; time protocol.<br>
&gt; &gt; <br>
&gt; &gt; Please note, that 3.2.10 refers to the connection of reference
time (such <br>
&gt; &gt; as GPS, Radio transmitter, ...) to the PTP grandmaster or NTP
stratum 1 <br>
&gt; &gt; server. These are basically non-IP or non-Ethernet connections
and <br>
&gt; &gt; therefore out of scope. <br>
&gt; <br>
&gt; I expect that rather soon, there will be a requirement to import time
in<br>
&gt; a secure way from one of the national time sources such as PTB or
NIST.<br>
&gt; &nbsp;(NIST already offers an authenticated time service.)<br>
&gt;</font></tt>
<br><tt><font size=2>Time is already disseminated by the national laboratories
by means of NTP. One of the intention of NTS is to secure this process.
Yes, it is true that NIST is offering a secured NTP access. But this is
done by means of the symmetric pre-shared key approach which is available
since NTP version 3. Also PTB is going to offer this service for a limited
number of applications. &nbsp;Therefore secure time dissemination of national
laboratories is not out of scope of this section. But out of scope is the
cryptographic protections of protocols like GPS, IRIG-B, etc. which are
often used to provide time information to the national time servers. That
is what section 3.2.10 is talking about.</font></tt>
<br>
<br><tt><font size=2>&gt; <br>
&gt; I still haven't read the relevant regulation, though, and it's likely<br>
&gt; still ambiguous in this regard.<br>
&gt; <br>
&gt; &gt;&gt; * The integrity checks on the server_assoc response are unclear.
It is<br>
&gt; &gt;&gt; not specified if host name verification is performed. (D)<br>
&gt; &gt; <br>
&gt; &gt; This should be ensured via CMS. But we will check this.<br>
&gt; <br>
&gt; Host name checks are out of scope for CMS, so you have to specify<br>
&gt; something on your own.<br>
&gt; <br>
&gt; &gt;&gt; * Client certificate management is a red flag for many organizations.
It<br>
&gt; &gt;&gt; would be better if the protocol would not use a client certificate
at<br>
&gt; &gt;&gt; all, and some other key agreement scheme (e.g., application
key<br>
&gt; &gt;&gt; extraction with TLS/DTLS, without client certificates, or
a TLS response<br>
&gt; &gt;&gt; containing an encrypted session key). (D)<br>
&gt; &gt; <br>
&gt; &gt; We want to have certificates in order to have a mean to provide
<br>
&gt; &gt; authorization.<br>
&gt; <br>
&gt; I think it would be best to make them optional.<br>
&gt; <br>
&gt; &gt;&gt; * With a server without per-client state, the HMAC key setup
has to be<br>
&gt; &gt;&gt; performed on each response. &nbsp;This is quite costly. &nbsp;A
different MAC<br>
&gt; &gt;&gt; could be quite a bit cheaper in terms of CPU overhead.<br>
&gt; &gt;<br>
&gt; &gt; Which MAC do you propose?<br>
&gt; <br>
&gt; I'd have to do some research on this matter and will report back.
&nbsp;Not<br>
&gt; all technical choices will be acceptable to the IETF.<br>
&gt; <br>
&gt; &gt;&gt; * I have doubts about the use of TESLA.<br>
&gt; <br>
&gt; &gt; For us TESLA seems to be an appropriate approach. Do you know
a good <br>
&gt; &gt; alternative?<br>
&gt; <br>
&gt; I'm afraid I do not. &nbsp;(To be clear: If you do not have operational<br>
&gt; experience with TESLA that says otherwise, I suspect it will not work
in<br>
&gt; practice.)<br>
&gt; <br>
&gt; &gt;&gt; * Requiring a new OID in the Extended Key Usages attribute
of<br>
&gt; &gt;&gt; certificates (section 4) means that the browser PKI cannot
be used to<br>
&gt; &gt;&gt; authenticate hosts. This seems quite wrong.<br>
&gt; &gt; <br>
&gt; &gt; Please describe the problem in more detail.<br>
&gt; <br>
&gt; The existing guidelines for browser CAs discourage signing subscriber<br>
&gt; certificates with strange extKeyUsage fields, see these requirements<br>
&gt; documents: &lt;</font></tt><a href="https://cabforum.org/baseline-requirements-documents/"><tt><font size=2>https://cabforum.org/baseline-requirements-documents/</font></tt></a><tt><font size=2>&gt;<br>
&gt; <br>
&gt; &gt;&gt; # draft-ietf-ntp-using-nts-for-ntp-00<br>
&gt; &gt;&gt;<br>
&gt; &gt;&gt; * There is no cookie protection of server_assoc/server_cook
responses,<br>
&gt; &gt;&gt; as explained above. This is quite bad. (D)<br>
&gt; &gt; <br>
&gt; &gt; What exactly do you mean by cookie protection?<br>
&gt; <br>
&gt; This is the lack of a Photuris cookie mentioned above.#</font></tt>
<br>
<br><tt><font size=2>Thanks for clarification.</font></tt>
<br><tt><font size=2><br>
&gt; <br>
&gt; -- <br>
&gt; Florian Weimer / Red Hat Product Security<br>
</font></tt>
--=_alternative 0051D4E8C1257E23_=--

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

MIAGCSqGSIb3DQEHAqCAMIImzgIBATELMAkGBSsOAwIaBQAwCwYJKoZIhvcNAQcBoIIj4DCCA58w
ggKHoAMCAQICASYwDQYJKoZIhvcNAQEFBQAwcTELMAkGA1UEBhMCREUxHDAaBgNVBAoTE0RldXRz
Y2hlIFRlbGVrb20gQUcxHzAdBgNVBAsTFlQtVGVsZVNlYyBUcnVzdCBDZW50ZXIxIzAhBgNVBAMT
GkRldXRzY2hlIFRlbGVrb20gUm9vdCBDQSAyMB4XDTk5MDcwOTEyMTEwMFoXDTE5MDcwOTIzNTkw
MFowcTELMAkGA1UEBhMCREUxHDAaBgNVBAoTE0RldXRzY2hlIFRlbGVrb20gQUcxHzAdBgNVBAsT
FlQtVGVsZVNlYyBUcnVzdCBDZW50ZXIxIzAhBgNVBAMTGkRldXRzY2hlIFRlbGVrb20gUm9vdCBD
QSAyMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAqwujNeCLKRSxFIWvPBDkOW81XUqu
3ephjZVJ9G9koxpgZqSpQCKE2dSl5XiTDmgBrblNXDrO07ioQkDfz6O6gllqkhusHJraCCslJ/lp
I0fx4Ossepv1EwLQfjR8wp48AFmr9doM9TI8K6xQ2tbD3oOUyqgMmTIOCEhWW2r72uFYWAFJX3JB
PBUGAY5draq4k7TNnuun6GotUjTbOu9cdVHa2/Mx+e5xmDLEVBVEDPmbVe2t3xgIoKOGiknuUwWP
GUzV3lh5m9JqHEKrxdWnz2gPluThYZh2YciRfNY+AOKRUIfhnQrmrZfSHcY6fcu82gM01Y5bAfVq
B7cWtm5KfwIDAQABo0IwQDAdBgNVHQ4EFgQUMcN5G7r1U9cX4Il6LRdsCrMrnTMwDwYDVR0TBAgw
BgEB/wIBBTAOBgNVHQ8BAf8EBAMCAQYwDQYJKoZIhvcNAQEFBQADggEBAJRkWa05ZOcp6xP+WsOL
E1fIBCTwdHfAYONn++mJpoO/loJ8btTDPe+egG67KbSYerE7VOs5F0d+Go4L/B8xWTEEss4X8yzH
YjZV4iLYiVW0mEiqZPrWHDbYRHhaWiM6V5f1ejBPrp9qTEsrjqAD4z7gqdTSe9KzqOJyPK2e/4BZ
5JtFtPY7sM05GZgy5eohYZDkMSGONLH3LzVKhRDa54o3Ib5ZY+DyhYgxU9RUFIVwefQuBncndS8f
uIr5/sW62Dbkg+znZbe/Y1rzRq+BlDfUQYzWI9Yez/VoG0Rjolq6pzVZoeVwBZsOI1eZlAptujlj
KIaS8xiE2PvRzwVWZFcwggOfMIICh6ADAgECAgEmMA0GCSqGSIb3DQEBBQUAMHExCzAJBgNVBAYT
AkRFMRwwGgYDVQQKExNEZXV0c2NoZSBUZWxla29tIEFHMR8wHQYDVQQLExZULVRlbGVTZWMgVHJ1
c3QgQ2VudGVyMSMwIQYDVQQDExpEZXV0c2NoZSBUZWxla29tIFJvb3QgQ0EgMjAeFw05OTA3MDkx
MjExMDBaFw0xOTA3MDkyMzU5MDBaMHExCzAJBgNVBAYTAkRFMRwwGgYDVQQKExNEZXV0c2NoZSBU
ZWxla29tIEFHMR8wHQYDVQQLExZULVRlbGVTZWMgVHJ1c3QgQ2VudGVyMSMwIQYDVQQDExpEZXV0
c2NoZSBUZWxla29tIFJvb3QgQ0EgMjCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBAKsL
ozXgiykUsRSFrzwQ5DlvNV1Krt3qYY2VSfRvZKMaYGakqUAihNnUpeV4kw5oAa25TVw6ztO4qEJA
38+juoJZapIbrBya2ggrJSf5aSNH8eDrLHqb9RMC0H40fMKePABZq/XaDPUyPCusUNrWw96DlMqo
DJkyDghIVltq+9rhWFgBSV9yQTwVBgGOXa2quJO0zZ7rp+hqLVI02zrvXHVR2tvzMfnucZgyxFQV
RAz5m1Xtrd8YCKCjhopJ7lMFjxlM1d5YeZvSahxCq8XVp89oD5bk4WGYdmHIkXzWPgDikVCH4Z0K
5q2X0h3GOn3LvNoDNNWOWwH1age3FrZuSn8CAwEAAaNCMEAwHQYDVR0OBBYEFDHDeRu69VPXF+CJ
ei0XbAqzK50zMA8GA1UdEwQIMAYBAf8CAQUwDgYDVR0PAQH/BAQDAgEGMA0GCSqGSIb3DQEBBQUA
A4IBAQCUZFmtOWTnKesT/lrDixNXyAQk8HR3wGDjZ/vpiaaDv5aCfG7Uwz3vnoBuuym0mHqxO1Tr
ORdHfhqOC/wfMVkxBLLOF/Msx2I2VeIi2IlVtJhIqmT61hw22ER4WlojOleX9XowT66fakxLK46g
A+M+4KnU0nvSs6jicjytnv+AWeSbRbT2O7DNORmYMuXqIWGQ5DEhjjSx9y81SoUQ2ueKNyG+WWPg
8oWIMVPUVBSFcHn0LgZ3J3UvH7iK+f7Futg25IPs52W3v2Na80avgZQ31EGM1iPWHs/1aBtEY6Ja
uqc1WaHlcAWbDiNXmZQKbbo5YyiGkvMYhNj70c8FVmRXMIIEITCCAwmgAwIBAgICAMcwDQYJKoZI
hvcNAQEFBQAwcTELMAkGA1UEBhMCREUxHDAaBgNVBAoTE0RldXRzY2hlIFRlbGVrb20gQUcxHzAd
BgNVBAsTFlQtVGVsZVNlYyBUcnVzdCBDZW50ZXIxIzAhBgNVBAMTGkRldXRzY2hlIFRlbGVrb20g
Um9vdCBDQSAyMB4XDTA2MTIxOTEwMjkwMFoXDTE5MDYzMDIzNTkwMFowWjELMAkGA1UEBhMCREUx
EzARBgNVBAoTCkRGTi1WZXJlaW4xEDAOBgNVBAsTB0RGTi1QS0kxJDAiBgNVBAMTG0RGTi1WZXJl
aW4gUENBIEdsb2JhbCAtIEcwMTCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBAOmbw2eF
+Q2u9Y1Uw5ZQNT1i6W5M7ZTXAFuVInTUIOs0j9bswDEEC5mB4qYU0lKgKCOEi3SJBF5b4OJ4wXjL
FssoNTl7LZBF0O2gAHp8v0oOGwDDhulcKzERewzzgiRDjBw4i2poAJru3E94q9LGE5t2re7eJujv
Aa90D8EJovZrzr3TzRQwT/Xl46TIYpuCGgMnMA0CZWBN7dEJIyqWNVgn03bGcbaQHcTt/zWGfW8z
s9sPxRHCioOhlF1Ba9jSEPVM/cpRrNm975KDu9rrixZWVkPP4dUTPaYfJzDNSVTbyRM0mnF1xWzq
pwuY+SGdJ68+ozk5SGqMrcmZ+8MS8r0CAwEAAaOB2TCB1jBwBgNVHR8EaTBnMGWgY6Bhhl9odHRw
Oi8vcGtpLnRlbGVzZWMuZGUvY2dpLWJpbi9zZXJ2aWNlL2FmX0Rvd25sb2FkQVJMLmNybD8tY3Js
X2Zvcm1hdD1YXzUwOSYtaXNzdWVyPURUX1JPT1RfQ0FfMjAdBgNVHQ4EFgQUSbfGz+g9H3/qRHsT
KffxCnA+3mQwHwYDVR0jBBgwFoAUMcN5G7r1U9cX4Il6LRdsCrMrnTMwDgYDVR0PAQH/BAQDAgEG
MBIGA1UdEwEB/wQIMAYBAf8CAQIwDQYJKoZIhvcNAQEFBQADggEBADvhWnfASBfcqRjsga9aifC9
KJKmylkYEnDsKPLnrn+WLOfyXRkx9hMrdL29gLK592fJOaJ5O+EREe5reJEzfjtfJid1U2WOM2Pu
z3PDsJIjSSFQdSOhHxjilIU9PzPpdyCNor3moYUpQPY/czJYDQlrptqFbMA/u41mZFYkTq4NPzI1
AVvpjILZcllPsYaF8XSFVuXD+Fzzje5Hs1MFcOflTYppgyjhEwmGnl7I6lgeDB/5pNRaBGj9KD6L
ArZYtfahLDdXAGerI2iNY6XvmWtc/UtW9qtAhzTUEZJs7IfFCgsHM3K0bwwdVCzYUcfMvzDTQ3Lx
Mr+MzkljqAD38hwwggQhMIIDCaADAgECAgIAxzANBgkqhkiG9w0BAQUFADBxMQswCQYDVQQGEwJE
RTEcMBoGA1UEChMTRGV1dHNjaGUgVGVsZWtvbSBBRzEfMB0GA1UECxMWVC1UZWxlU2VjIFRydXN0
IENlbnRlcjEjMCEGA1UEAxMaRGV1dHNjaGUgVGVsZWtvbSBSb290IENBIDIwHhcNMDYxMjE5MTAy
OTAwWhcNMTkwNjMwMjM1OTAwWjBaMQswCQYDVQQGEwJERTETMBEGA1UEChMKREZOLVZlcmVpbjEQ
MA4GA1UECxMHREZOLVBLSTEkMCIGA1UEAxMbREZOLVZlcmVpbiBQQ0EgR2xvYmFsIC0gRzAxMIIB
IjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEA6ZvDZ4X5Da71jVTDllA1PWLpbkztlNcAW5Ui
dNQg6zSP1uzAMQQLmYHiphTSUqAoI4SLdIkEXlvg4njBeMsWyyg1OXstkEXQ7aAAeny/Sg4bAMOG
6VwrMRF7DPOCJEOMHDiLamgAmu7cT3ir0sYTm3at7t4m6O8Br3QPwQmi9mvOvdPNFDBP9eXjpMhi
m4IaAycwDQJlYE3t0QkjKpY1WCfTdsZxtpAdxO3/NYZ9bzOz2w/FEcKKg6GUXUFr2NIQ9Uz9ylGs
2b3vkoO72uuLFlZWQ8/h1RM9ph8nMM1JVNvJEzSacXXFbOqnC5j5IZ0nrz6jOTlIaoytyZn7wxLy
vQIDAQABo4HZMIHWMHAGA1UdHwRpMGcwZaBjoGGGX2h0dHA6Ly9wa2kudGVsZXNlYy5kZS9jZ2kt
YmluL3NlcnZpY2UvYWZfRG93bmxvYWRBUkwuY3JsPy1jcmxfZm9ybWF0PVhfNTA5Ji1pc3N1ZXI9
RFRfUk9PVF9DQV8yMB0GA1UdDgQWBBRJt8bP6D0ff+pEexMp9/EKcD7eZDAfBgNVHSMEGDAWgBQx
w3kbuvVT1xfgiXotF2wKsyudMzAOBgNVHQ8BAf8EBAMCAQYwEgYDVR0TAQH/BAgwBgEB/wIBAjAN
BgkqhkiG9w0BAQUFAAOCAQEAO+Fad8BIF9ypGOyBr1qJ8L0okqbKWRgScOwo8ueuf5Ys5/JdGTH2
Eyt0vb2Asrn3Z8k5onk74RER7mt4kTN+O18mJ3VTZY4zY+7Pc8OwkiNJIVB1I6EfGOKUhT0/M+l3
II2iveahhSlA9j9zMlgNCWum2oVswD+7jWZkViROrg0/MjUBW+mMgtlyWU+xhoXxdIVW5cP4XPON
7kezUwVw5+VNimmDKOETCYaeXsjqWB4MH/mk1FoEaP0oPosCtli19qEsN1cAZ6sjaI1jpe+Za1z9
S1b2q0CHNNQRkmzsh8UKCwczcrRvDB1ULNhRx8y/MNNDcvEyv4zOSWOoAPfyHDCCBO8wggPXoAMC
AQICBA0hCk0wDQYJKoZIhvcNAQEFBQAwWjELMAkGA1UEBhMCREUxEzARBgNVBAoTCkRGTi1WZXJl
aW4xEDAOBgNVBAsTB0RGTi1QS0kxJDAiBgNVBAMTG0RGTi1WZXJlaW4gUENBIEdsb2JhbCAtIEcw
MTAeFw0wODEwMjQwODUyMTNaFw0xOTA2MzAwMDAwMDBaMGkxCzAJBgNVBAYTAkRFMS4wLAYDVQQK
EyVQaHlzaWthbGlzY2gtVGVjaG5pc2NoZSBCdW5kZXNhbnN0YWx0MQ8wDQYDVQQDEwZQVEIgQ0Ex
GTAXBgkqhkiG9w0BCQEWCnBraUBwdGIuZGUwggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIB
AQC8CsKDOSrDYswBi5TfxUlODIYEL4+n66/DnYua0jowQyIWvTFjpITNhwMbfPk1KiFmKx2cvtu7
wR7swUPdNlfWNUGJ7/9Q0AmpdsedTMTyFslgJHnJ1v1aojOhPk/MbTuolZuVuJ1ytlVwJAR5/1XU
JpHJ9e6qJJM6CJuo4Ms/3w3uMwgibPaKlSAx2gbI6BKH+p2zlIzoJSDAx64njZClg2i32uLUgoDB
7KEghrdMA2y7nqxzL4Vzb5dY5+y4iZ54txqK7ock+TpfnlBP6RZoChB/qonIle/xv+fqXWeZMhTY
BjYHkSc7+shP4Nb4wnLvv8c77uu3BrOe6e1cyDK3AgMBAAGjggGsMIIBqDASBgNVHRMBAf8ECDAG
AQH/AgEBMAsGA1UdDwQEAwIBBjAdBgNVHQ4EFgQUxIDQbigVaDFa7HBfeI7hMEM46jQwHwYDVR0j
BBgwFoAUSbfGz+g9H3/qRHsTKffxCnA+3mQwFQYDVR0RBA4wDIEKcGtpQHB0Yi5kZTCBiAYDVR0f
BIGAMH4wPaA7oDmGN2h0dHA6Ly9jZHAxLnBjYS5kZm4uZGUvZ2xvYmFsLXJvb3QtY2EvcHViL2Ny
bC9jYWNybC5jcmwwPaA7oDmGN2h0dHA6Ly9jZHAyLnBjYS5kZm4uZGUvZ2xvYmFsLXJvb3QtY2Ev
cHViL2NybC9jYWNybC5jcmwwgaIGCCsGAQUFBwEBBIGVMIGSMEcGCCsGAQUFBzAChjtodHRwOi8v
Y2RwMS5wY2EuZGZuLmRlL2dsb2JhbC1yb290LWNhL3B1Yi9jYWNlcnQvY2FjZXJ0LmNydDBHBggr
BgEFBQcwAoY7aHR0cDovL2NkcDIucGNhLmRmbi5kZS9nbG9iYWwtcm9vdC1jYS9wdWIvY2FjZXJ0
L2NhY2VydC5jcnQwDQYJKoZIhvcNAQEFBQADggEBAJ3KSKdj6GjgE6pSuE74pBcKLfmC2Phy1Gfj
83Lzx9leQX67sL6uTIV5NTQgQDsjTlqyxRQJ5eYhj+ZjwfVS02pDdD+trg2iGp1WdFFsqyhts+oS
M4SpRUuZ83FHEieuWq9teT7bcWPUzckYy4k17u9LAp7+V1h7s6aOpk9RCyA1sSlFTP33O9tpLwXq
KpXHK+zG9JOV7kPDHYLAi2Krw5LB91EBSyXWLu7xK4i6prEUGRWVblckx116ikhBFy3cNr2NGfhh
KiOCphAeIFPCCxOEvRk/LkZRnZaMnHQsUHVuAs2SBB08coYSjF7/NZAXprZlpI2KZiUfeo6JU9bS
UbowggTvMIID16ADAgECAgQNIQpNMA0GCSqGSIb3DQEBBQUAMFoxCzAJBgNVBAYTAkRFMRMwEQYD
VQQKEwpERk4tVmVyZWluMRAwDgYDVQQLEwdERk4tUEtJMSQwIgYDVQQDExtERk4tVmVyZWluIFBD
QSBHbG9iYWwgLSBHMDEwHhcNMDgxMDI0MDg1MjEzWhcNMTkwNjMwMDAwMDAwWjBpMQswCQYDVQQG
EwJERTEuMCwGA1UEChMlUGh5c2lrYWxpc2NoLVRlY2huaXNjaGUgQnVuZGVzYW5zdGFsdDEPMA0G
A1UEAxMGUFRCIENBMRkwFwYJKoZIhvcNAQkBFgpwa2lAcHRiLmRlMIIBIjANBgkqhkiG9w0BAQEF
AAOCAQ8AMIIBCgKCAQEAvArCgzkqw2LMAYuU38VJTgyGBC+Pp+uvw52LmtI6MEMiFr0xY6SEzYcD
G3z5NSohZisdnL7bu8Ee7MFD3TZX1jVBie//UNAJqXbHnUzE8hbJYCR5ydb9WqIzoT5PzG07qJWb
lbidcrZVcCQEef9V1CaRyfXuqiSTOgibqODLP98N7jMIImz2ipUgMdoGyOgSh/qds5SM6CUgwMeu
J42QpYNot9ri1IKAweyhIIa3TANsu56scy+Fc2+XWOfsuImeeLcaiu6HJPk6X55QT+kWaAoQf6qJ
yJXv8b/n6l1nmTIU2AY2B5EnO/rIT+DW+MJy77/HO+7rtwaznuntXMgytwIDAQABo4IBrDCCAagw
EgYDVR0TAQH/BAgwBgEB/wIBATALBgNVHQ8EBAMCAQYwHQYDVR0OBBYEFMSA0G4oFWgxWuxwX3iO
4TBDOOo0MB8GA1UdIwQYMBaAFEm3xs/oPR9/6kR7Eyn38QpwPt5kMBUGA1UdEQQOMAyBCnBraUBw
dGIuZGUwgYgGA1UdHwSBgDB+MD2gO6A5hjdodHRwOi8vY2RwMS5wY2EuZGZuLmRlL2dsb2JhbC1y
b290LWNhL3B1Yi9jcmwvY2FjcmwuY3JsMD2gO6A5hjdodHRwOi8vY2RwMi5wY2EuZGZuLmRlL2ds
b2JhbC1yb290LWNhL3B1Yi9jcmwvY2FjcmwuY3JsMIGiBggrBgEFBQcBAQSBlTCBkjBHBggrBgEF
BQcwAoY7aHR0cDovL2NkcDEucGNhLmRmbi5kZS9nbG9iYWwtcm9vdC1jYS9wdWIvY2FjZXJ0L2Nh
Y2VydC5jcnQwRwYIKwYBBQUHMAKGO2h0dHA6Ly9jZHAyLnBjYS5kZm4uZGUvZ2xvYmFsLXJvb3Qt
Y2EvcHViL2NhY2VydC9jYWNlcnQuY3J0MA0GCSqGSIb3DQEBBQUAA4IBAQCdykinY+ho4BOqUrhO
+KQXCi35gtj4ctRn4/Ny88fZXkF+u7C+rkyFeTU0IEA7I05assUUCeXmIY/mY8H1UtNqQ3Q/ra4N
ohqdVnRRbKsobbPqEjOEqUVLmfNxRxInrlqvbXk+23Fj1M3JGMuJNe7vSwKe/ldYe7OmjqZPUQsg
NbEpRUz99zvbaS8F6iqVxyvsxvSTle5Dwx2CwItiq8OSwfdRAUsl1i7u8SuIuqaxFBkVlW5XJMdd
eopIQRct3Da9jRn4YSojgqYQHiBTwgsThL0ZPy5GUZ2WjJx0LFB1bgLNkgQdPHKGEoxe/zWQF6a2
ZaSNimYlH3qOiVPW0lG6MIIFMTCCBBmgAwIBAgIHF5wEkEK5CzANBgkqhkiG9w0BAQUFADBpMQsw
CQYDVQQGEwJERTEuMCwGA1UEChMlUGh5c2lrYWxpc2NoLVRlY2huaXNjaGUgQnVuZGVzYW5zdGFs
dDEPMA0GA1UEAxMGUFRCIENBMRkwFwYJKoZIhvcNAQkBFgpwa2lAcHRiLmRlMB4XDTE0MDUyMTEw
NTkxMloXDTE3MDUyMDEwNTkxMlowaDELMAkGA1UEBhMCREUxLjAsBgNVBAoTJVBoeXNpa2FsaXNj
aC1UZWNobmlzY2hlIEJ1bmRlc2Fuc3RhbHQxDTALBgNVBAsTBFEuNDIxGjAYBgNVBAMTEURyLiBE
aWV0ZXIgU2lib2xkMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAyYt5z0GIwexbe7Vv
kf+wpeCfISmM1FzPfdbR5jJ2l2AjGNAzqJ+aWKL0adslYl8m7JQE7pPXiTZ6sDiOhICg6XVVlLQl
j3ILO6pkvlIk9auqhRC+9Oo1yXSbbrX8BoFbHF0UdV65MtfzuIzvdInq1mpNW7/sZtlWBxen/HbC
QgVDRkXd5U0OU8wF4RW0OYnF5hxOnMsFIugFHq4oMA92zLk6j5Esk4syOiyJzuf3dDoLzTKg7n+K
3wRl0HvrE9mUgR/nuijICWdETRwKotQu27+VOjWU27w5Flpd8MYiSeV7sJEPukT11m0aQRE4h4VN
2yh24/aRJCxJOA25sW/I5QIDAQABo4IB3TCCAdkwLwYDVR0gBCgwJjARBg8rBgEEAYGtIYIsAQEE
AwEwEQYPKwYBBAGBrSGCLAIBBAMBMAkGA1UdEwQCMAAwCwYDVR0PBAQDAgXgMB8GA1UdJQQYMBYG
CCsGAQUFBwMEBgorBgEEAYI3FAICMB0GA1UdDgQWBBRsyFeB8XX9H0eJUJysSheMBkFZrzAfBgNV
HSMEGDAWgBTEgNBuKBVoMVrscF94juEwQzjqNDAfBgNVHREEGDAWgRRkaWV0ZXIuc2lib2xkQHB0
Yi5kZTB3BgNVHR8EcDBuMDWgM6Axhi9odHRwOi8vY2RwMS5wY2EuZGZuLmRlL3B0Yi1jYS9wdWIv
Y3JsL2NhY3JsLmNybDA1oDOgMYYvaHR0cDovL2NkcDIucGNhLmRmbi5kZS9wdGItY2EvcHViL2Ny
bC9jYWNybC5jcmwwgZIGCCsGAQUFBwEBBIGFMIGCMD8GCCsGAQUFBzAChjNodHRwOi8vY2RwMS5w
Y2EuZGZuLmRlL3B0Yi1jYS9wdWIvY2FjZXJ0L2NhY2VydC5jcnQwPwYIKwYBBQUHMAKGM2h0dHA6
Ly9jZHAyLnBjYS5kZm4uZGUvcHRiLWNhL3B1Yi9jYWNlcnQvY2FjZXJ0LmNydDANBgkqhkiG9w0B
AQUFAAOCAQEAt2XdEe0IxYuz1v6WhXz1+EfnFC3S0Yvx4J438lbPYHFkablzHsgedeZzURxl221T
5SC4i6lC36otU7xZkVuSfyJWkMbozxgE4aA+sTJW37IdRVzQSYXFZa95DPj4B7iw+RHGBTFxbVJm
USzMG8nvykOYcpRkxxLUAZglAPfmvu/X/ixsuy4oA/0OHvpIOG1SumSb325hiP9/dMxHFwjbdyqE
nxQAkGbV5kHE77yaydGlQftM5xheKiPOBzbS2ZlzPP8L8kGPrcLK0/mdW3aW+r35aru5E+515qKm
9O0r7SiTCoNbpGCwo4o+aPDVBSe/BBxTW7St2alvIpSKZjyW6TCCBTEwggQZoAMCAQICBxecBJBC
uQswDQYJKoZIhvcNAQEFBQAwaTELMAkGA1UEBhMCREUxLjAsBgNVBAoTJVBoeXNpa2FsaXNjaC1U
ZWNobmlzY2hlIEJ1bmRlc2Fuc3RhbHQxDzANBgNVBAMTBlBUQiBDQTEZMBcGCSqGSIb3DQEJARYK
cGtpQHB0Yi5kZTAeFw0xNDA1MjExMDU5MTJaFw0xNzA1MjAxMDU5MTJaMGgxCzAJBgNVBAYTAkRF
MS4wLAYDVQQKEyVQaHlzaWthbGlzY2gtVGVjaG5pc2NoZSBCdW5kZXNhbnN0YWx0MQ0wCwYDVQQL
EwRRLjQyMRowGAYDVQQDExFEci4gRGlldGVyIFNpYm9sZDCCASIwDQYJKoZIhvcNAQEBBQADggEP
ADCCAQoCggEBAMmLec9BiMHsW3u1b5H/sKXgnyEpjNRcz33W0eYydpdgIxjQM6ifmlii9GnbJWJf
JuyUBO6T14k2erA4joSAoOl1VZS0JY9yCzuqZL5SJPWrqoUQvvTqNcl0m261/AaBWxxdFHVeuTLX
87iM73SJ6tZqTVu/7GbZVgcXp/x2wkIFQ0ZF3eVNDlPMBeEVtDmJxeYcTpzLBSLoBR6uKDAPdsy5
Oo+RLJOLMjosic7n93Q6C80yoO5/it8EZdB76xPZlIEf57ooyAlnRE0cCqLULtu/lTo1lNu8ORZa
XfDGIknle7CRD7pE9dZtGkEROIeFTdsoduP2kSQsSTgNubFvyOUCAwEAAaOCAd0wggHZMC8GA1Ud
IAQoMCYwEQYPKwYBBAGBrSGCLAEBBAMBMBEGDysGAQQBga0hgiwCAQQDATAJBgNVHRMEAjAAMAsG
A1UdDwQEAwIF4DAfBgNVHSUEGDAWBggrBgEFBQcDBAYKKwYBBAGCNxQCAjAdBgNVHQ4EFgQUbMhX
gfF1/R9HiVCcrEoXjAZBWa8wHwYDVR0jBBgwFoAUxIDQbigVaDFa7HBfeI7hMEM46jQwHwYDVR0R
BBgwFoEUZGlldGVyLnNpYm9sZEBwdGIuZGUwdwYDVR0fBHAwbjA1oDOgMYYvaHR0cDovL2NkcDEu
cGNhLmRmbi5kZS9wdGItY2EvcHViL2NybC9jYWNybC5jcmwwNaAzoDGGL2h0dHA6Ly9jZHAyLnBj
YS5kZm4uZGUvcHRiLWNhL3B1Yi9jcmwvY2FjcmwuY3JsMIGSBggrBgEFBQcBAQSBhTCBgjA/Bggr
BgEFBQcwAoYzaHR0cDovL2NkcDEucGNhLmRmbi5kZS9wdGItY2EvcHViL2NhY2VydC9jYWNlcnQu
Y3J0MD8GCCsGAQUFBzAChjNodHRwOi8vY2RwMi5wY2EuZGZuLmRlL3B0Yi1jYS9wdWIvY2FjZXJ0
L2NhY2VydC5jcnQwDQYJKoZIhvcNAQEFBQADggEBALdl3RHtCMWLs9b+loV89fhH5xQt0tGL8eCe
N/JWz2BxZGm5cx7IHnXmc1EcZdttU+UguIupQt+qLVO8WZFbkn8iVpDG6M8YBOGgPrEyVt+yHUVc
0EmFxWWveQz4+Ae4sPkRxgUxcW1SZlEszBvJ78pDmHKUZMcS1AGYJQD35r7v1/4sbLsuKAP9Dh76
SDhtUrpkm99uYYj/f3TMRxcI23cqhJ8UAJBm1eZBxO+8msnRpUH7TOcYXiojzgc20tmZczz/C/JB
j63CytP5nVt2lvq9+Wq7uRPudeaipvTtK+0okwqDW6RgsKOKPmjw1QUnvwQcU1u0rdmpbyKUimY8
lukxggLJMIICxQIBATB0MGkxCzAJBgNVBAYTAkRFMS4wLAYDVQQKEyVQaHlzaWthbGlzY2gtVGVj
aG5pc2NoZSBCdW5kZXNhbnN0YWx0MQ8wDQYDVQQDEwZQVEIgQ0ExGTAXBgkqhkiG9w0BCQEWCnBr
aUBwdGIuZGUCBxecBJBCuQswCQYFKw4DAhoFAKCCASowGAYJKoZIhvcNAQkDMQsGCSqGSIb3DQEH
ATAcBgkqhkiG9w0BCQUxDxcNMTUwNDEwMTQ1MzUwWjAjBgkqhkiG9w0BCQQxFgQU8fof3hzncXsD
LSNj4vyaYYpWO+AwQwYJKoZIhvcNAQkPMTYwNDAHBgUrDgMCHTAOBggqhkiG9w0DAgICAIAwCgYI
KoZIhvcNAwcwDQYIKoZIhvcNAwICASgwgYUGCyqGSIb3DQEJEAILMXagdDBpMQswCQYDVQQGEwJE
RTEuMCwGA1UEChMlUGh5c2lrYWxpc2NoLVRlY2huaXNjaGUgQnVuZGVzYW5zdGFsdDEPMA0GA1UE
AxMGUFRCIENBMRkwFwYJKoZIhvcNAQkBFgpwa2lAcHRiLmRlAgcXnASQQrkLMA0GCSqGSIb3DQEB
AQUABIIBALrjUZyIZg4SImSgsgGbGa771zuv3+PKGi6gs/JqDz6+a32I3V/bz4gl4K5w1RC8LkcM
WRWVWhGfk76TZBeOgZODA8S26bepTpEzzAaFiGmLUFZRb/kOWVVyQV9aZ0L68SjJnIJA5IYZN2Ft
1QLWHsuAFJbHy3yg68oSPvtMWy0pZQyvpcJBivGbQdPRERb5JhyJCkjXPxL9t6DbhOuBpmr9VRHr
7O7m8UPVYla1LF4sMXcQCZYejvGvG7uEza45EJ3UR52+gaGqGj59nVxzjholybRhpi9q6jJZPKN5
PlrCKA5ig40rrOUm3Q8MtdsHn8u98LjV55YxmPlJl7mgYP4AAAAA

---------z35978_boundary_sign--

--===============6533233339730305613==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

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

From ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org  Tue Apr 14 21:09:31 2015
Return-Path: <ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org>
X-Original-To: ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com
Delivered-To: ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 298DF1B2B9E for <ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com>; Tue, 14 Apr 2015 21:09:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.909
X-Spam-Level:
X-Spam-Status: No, score=-1.909 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 3WtwSb3eDJ2L for <ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com>; Tue, 14 Apr 2015 21:09:22 -0700 (PDT)
Received: from psp3.ntp.org (psp3.ntp.org [149.20.68.23]) by ietfa.amsl.com (Postfix) with ESMTP id 985691B2B9F for <ntp-archives-ahFae6za@lists.ietf.org>; Tue, 14 Apr 2015 21:09:22 -0700 (PDT)
Received: from psp3.ntp.org (localhost.ntp.org [127.0.0.1]) by psp3.ntp.org (Postfix) with ESMTP id 8FEB939877 for <ntp-archives-ahFae6za@lists.ietf.org>; Tue, 14 Apr 2015 21:09:22 -0700 (PDT)
X-Original-To: ntpwg@lists.ntp.org
Delivered-To: ntpwg@lists.ntp.org
Received: from mail1.ntp.org (mail1.ntp.org [IPv6:2001:4f8:fff7:1::5]) by lists.ntp.org (Postfix) with ESMTP id D1ACA86D48C for <ntpwg@lists.ntp.org>; Sun, 12 Apr 2015 03:06:39 +0000 (UTC)
Received: from mx1.bs.ptb.de ([192.53.103.106]) by mail1.ntp.org with esmtps (TLSv1:AES256-SHA:256) (Exim 4.77 (FreeBSD)) (envelope-from <dieter.sibold@ptb.de>) id 1Yh8E4-0002tT-GU for ntpwg@lists.ntp.org; Sun, 12 Apr 2015 03:06:39 +0000
Received: from mx1.bs.ptb.de (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id 5AEBFD6E5DB; Fri, 10 Apr 2015 16:11:41 +0200 (CEST)
Received: from rose.bs.ptb.de (rose.bs.ptb.de [141.25.85.201]) by mx1.bs.ptb.de (Postfix) with ESMTP id 3A65ED69E2D; Fri, 10 Apr 2015 16:11:41 +0200 (CEST)
In-Reply-To: <551D1150.5080500@redhat.com>
References: <551D1150.5080500@redhat.com>
To: Florian Weimer <fweimer@redhat.com>
MIME-Version: 1.0
X-KeepSent: EC232DE6:A8D2B0E6-C1257E23:004D3B95; type=4; name=$KeepSent
X-Mailer: IBM Notes Release 9.0.1FP3 January  12, 2015
Message-ID: <OFEC232DE6.A8D2B0E6-ONC1257E23.004D3B95-C1257E23.004DF89C@ptb.de>
From: dieter.sibold@ptb.de
Date: Fri, 10 Apr 2015 16:11:39 +0200
X-MIMETrack: S/MIME Sign by eclipse on Dieter Sibold/PTB(Release 9.0.1FP3|January 12, 2015) at 10.04.2015 16:11:39, Serialize by eclipse on Dieter Sibold/PTB(Release 9.0.1FP3|January  12, 2015) at 10.04.2015 16:11:39, Serialize complete at 10.04.2015 16:11:39, Itemize by eclipse on Dieter Sibold/PTB(Release 9.0.1FP3|January  12, 2015) at 10.04.2015 16:11:40, S/MIME Sign complete at 10.04.2015 16:11:40, Serialize by Router on ROSE/PTB(Release 9.0.1FP3HF79 | February 9, 2015) at 04/10/2015 16:11:41, Serialize complete at 04/10/2015 16:11:41
X-SA-Exim-Connect-IP: 192.53.103.106
X-SA-Exim-Rcpt-To: ntpwg@lists.ntp.org
X-SA-Exim-Mail-From: dieter.sibold@ptb.de
X-SA-Exim-Version: 4.2
X-SA-Exim-Scanned: Yes (on mail1.ntp.org)
Subject: [ntpwg] Antwort:  Comments on various NTS drafts
X-BeenThere: ntpwg@lists.ntp.org
X-Mailman-Version: 2.1.20
Precedence: list
List-Id: IETF Working Group for Network Time Protocol <ntpwg.lists.ntp.org>
List-Unsubscribe: <http://lists.ntp.org/options/ntpwg>, <mailto:ntpwg-request@lists.ntp.org?subject=unsubscribe>
List-Archive: <http://lists.ntp.org/pipermail/ntpwg/>
List-Post: <mailto:ntpwg@lists.ntp.org>
List-Help: <mailto:ntpwg-request@lists.ntp.org?subject=help>
List-Subscribe: <http://lists.ntp.org/listinfo/ntpwg>, <mailto:ntpwg-request@lists.ntp.org?subject=subscribe>
Cc: ntpwg@lists.ntp.org
Content-Type: multipart/mixed; boundary="===============6148188470893215293=="
Errors-To: ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org
Sender: "ntpwg" <ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org>

This is an S/MIME signed message.

--===============6148188470893215293==
Content-Type: multipart/signed;
	 protocol="application/x-pkcs7-signature";
	 micalg=sha1;
	 boundary=-------z48323_boundary_sign

This is an S/MIME signed message.

---------z48323_boundary_sign
Content-Type: multipart/alternative; boundary="=_alternative 004DF89AC1257E23_="

Dies ist eine mehrteilige Nachricht im MIME-Format.
--=_alternative 004DF89AC1257E23_=
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable

Hello Florian,
we added some mor questions to your initial comments.





ntpwg-bounces+dieter.sibold=3Dptb.de@lists.ntp.org schrieb am 02.04.2015=20
11:52:16:

> Von: Florian Weimer <fweimer@redhat.com>
> An: ntpwg@lists.ntp.org
> Datum: 03.04.2015 06:03
> Betreff: [ntpwg] Comments on various NTS drafts
> Gesendet von: ntpwg-bounces+dieter.sibold=3Dptb.de@lists.ntp.org
>=20
> Here are a few comments on those drafts.  I hope they are useful.
>=20
> I strongly recommend reusing (D)TLS instead of implementing your own
> cryptographic protocol.  I have marked the issues which would go away
> with a proper implementation of (D)TLS with ?(D)?.  With DTLS, the
> server could just send the client cookie and the HMAC key, disregarding
> the client certificate.

Do I understand it correctly that you're proposing something like:
* do the key exchange via dtls
* the server creates a random client cookie and calculates the client=20
specific key from that (using a server secret as well) and sends both to=20
the client
* the time sync packets would just send the rand in the request and the=20
server can calculate the shared key for the response

>=20
> # RFC 7384 compliance
>=20
> First of all, the proposed protocol fails to implement the requirements
> of RFC 7384.  This is mostly due to the fact that several of its
> requirements are *impossible* to implement:
>=20
> Section 5.1.2 is likely bogus because it is not implementable in
> practice (end-to-end security makes intermediate clocks obsolete).
>=20
> Section 5.6.1 requires frequent key refresh. This is impossible to
> implement in practice (ultimate keys cannot be refreshed without
> operator intervention), and not necessary as long as sufficiently strong
> cryptographic primitives (non-broken algorithms) are used.
>=20
> Section 5.9 is impossible to implement. There is no protection against
> DoS from MITM attacks. Protection against low-rate message spoofing
> without knowledge of the keys seems reasonable, though.
>=20
> In addition, RFC 7384, Section 3.2.10 indicates that securing the time
> source of an entire organization from an external source is out of
> scope. However, this is likely the most common application of a security
> time protocol.
>=20
> # draft-ietf-ntp-network-time-security-08
>=20
> * The client host name in the client=5Fassoc is an unnecessary information
> leak.
>=20
> * The client=5Fassoc message needs a mechanism to select the server
> certificate. This is desirable for metrics and required for server key
> rollover without locking out the existing clients. Without this
> mechanism, it is necessary to use multiple IP addresses. (D) via SNI.
>=20
> * The integrity checks on the server=5Fassoc response are unclear. It is
> not specified if host name verification is performed. (D)
>=20
> * In a trivial UDP-based implementation, the server=5Fassoc response is
> computed before two-way communication with the client IP address has
> been proven, resulting in a denial of service vulnerability (CPU
> overload due to signature computation for spoofed clients, traffic
> amplification due to larger server response). This also affects the
> server=5Fcook message generation. Photuris cookies would address this. (D)
>=20
> * The server=5Fcook message uses non-hybrid asymmetric encryption. With
> ECC, this does not work because the provided payload space is not large
> enough. The usual hybrid scheme should be used instead. This means that
> an additional cryptographic primitive has to be negotiated. (D)
>=20
> * Client certificate management is a red flag for many organizations. It
> would be better if the protocol would not use a client certificate at
> all, and some other key agreement scheme (e.g., application key
> extraction with TLS/DTLS, without client certificates, or a TLS response
> containing an encrypted session key). (D)

The client certificates can just be generated on the fly and don't have to =

be managed by the organization, i.e. they are self-signed. Actually, a=20
random public key would be enough at this point, the cert is just there=20
since it's easier to handle.


>=20
> * With a server without per-client state, the HMAC key setup has to be
> performed on each response.  This is quite costly.  A different MAC
> could be quite a bit cheaper in terms of CPU overhead.
>=20
> * I have doubts about the use of TESLA.
>=20
>   . Is there sufficient operational experience with this protocol?
>=20
>   . It is never stated explicitly, but reading the protocol
> descriptions, it is expected that TESLA is secure against malicious
> recipients.
>=20
>   . TESLA uses a race condition for security, which seems inherently=20
risky.
>=20
>   . The use of time for security purposes interacts in a complex way
> with using TESLA for time synchronization.
>=20
> # draft-ietf-ntp-cms-for-nts-message-02
>=20
> * DER is used even for fast-path time synchronization messages (not just
> for the handshake).  This seems unnecessary.
>=20
> * Requiring a new OID in the Extended Key Usages attribute of
> certificates (section 4) means that the browser PKI cannot be used to
> authenticate hosts. This seems quite wrong.
>=20
> * Not all CMS algorithm parameters are negotiated at the NTS layer, as
> suspected. (D)
>=20
> # draft-ietf-ntp-using-nts-for-ntp-00
>=20
> * There is no cookie protection of server=5Fassoc/server=5Fcook responses,
> as explained above. This is quite bad. (D)
>=20
> * The proposed protocol does not address UDP message size limitations.
> UDP fragmentation is fundamentally broken. (D)

Actually, that is on our To Do list.


>=20
> --=20
> Florian Weimer / Red Hat Product Security
> =5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=
=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F
> ntpwg mailing list
> ntpwg@lists.ntp.org
> http://lists.ntp.org/listinfo/ntpwg
--=_alternative 004DF89AC1257E23_=
Content-Type: text/html; charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable

<font size=3D2 face=3D"Vorgabe Mehrsprachig">Hello Florian,</font>
<br><font size=3D2 face=3D"Vorgabe Mehrsprachig">we added some mor questions
to your initial comments.</font>
<br><font size=3D2 face=3D"sans-serif"><br>
<br>
<br>
</font>
<br>
<br><tt><font size=3D2>ntpwg-bounces+dieter.sibold=3Dptb.de@lists.ntp.org s=
chrieb
am 02.04.2015 11:52:16:<br>
<br>
&gt; Von: Florian Weimer &lt;fweimer@redhat.com&gt;</font></tt>
<br><tt><font size=3D2>&gt; An: ntpwg@lists.ntp.org</font></tt>
<br><tt><font size=3D2>&gt; Datum: 03.04.2015 06:03</font></tt>
<br><tt><font size=3D2>&gt; Betreff: [ntpwg] Comments on various NTS drafts=
</font></tt>
<br><tt><font size=3D2>&gt; Gesendet von: ntpwg-bounces+dieter.sibold=3Dptb=
.de@lists.ntp.org</font></tt>
<br><tt><font size=3D2>&gt; <br>
&gt; Here are a few comments on those drafts. &nbsp;I hope they are useful.=
<br>
&gt; <br>
&gt; I strongly recommend reusing (D)TLS instead of implementing your own<b=
r>
&gt; cryptographic protocol. &nbsp;I have marked the issues which would
go away<br>
&gt; with a proper implementation of (D)TLS with &#8220;(D)&#8221;. &nbsp;W=
ith DTLS,
the<br>
&gt; server could just send the client cookie and the HMAC key, disregardin=
g<br>
&gt; the client certificate.</font></tt>
<br>
<br><font size=3D3>Do I understand it correctly that you're proposing somet=
hing
like:<br>
* do the key exchange via dtls</font>
<br><font size=3D3>* the server creates a random client cookie and calculat=
es
the client specific key from that (using a server secret as well) and sends
both to the client</font>
<br><font size=3D3>* the time sync packets would just send the rand in the
request and the server can calculate the shared key for the response</font>
<br><tt><font size=3D2><br>
&gt; <br>
&gt; # RFC 7384 compliance<br>
&gt; <br>
&gt; First of all, the proposed protocol fails to implement the requirement=
s<br>
&gt; of RFC 7384. &nbsp;This is mostly due to the fact that several of
its<br>
&gt; requirements are *impossible* to implement:<br>
&gt; <br>
&gt; Section 5.1.2 is likely bogus because it is not implementable in<br>
&gt; practice (end-to-end security makes intermediate clocks obsolete).<br>
&gt; <br>
&gt; Section 5.6.1 requires frequent key refresh. This is impossible to<br>
&gt; implement in practice (ultimate keys cannot be refreshed without<br>
&gt; operator intervention), and not necessary as long as sufficiently
strong<br>
&gt; cryptographic primitives (non-broken algorithms) are used.<br>
&gt; <br>
&gt; Section 5.9 is impossible to implement. There is no protection against=
<br>
&gt; DoS from MITM attacks. Protection against low-rate message spoofing<br>
&gt; without knowledge of the keys seems reasonable, though.<br>
&gt; <br>
&gt; In addition, RFC 7384, Section 3.2.10 indicates that securing the
time<br>
&gt; source of an entire organization from an external source is out of<br>
&gt; scope. However, this is likely the most common application of a securi=
ty<br>
&gt; time protocol.<br>
&gt; <br>
&gt; # draft-ietf-ntp-network-time-security-08<br>
&gt; <br>
&gt; * The client host name in the client=5Fassoc is an unnecessary informa=
tion<br>
&gt; leak.<br>
&gt; <br>
&gt; * The client=5Fassoc message needs a mechanism to select the server<br>
&gt; certificate. This is desirable for metrics and required for server
key<br>
&gt; rollover without locking out the existing clients. Without this<br>
&gt; mechanism, it is necessary to use multiple IP addresses. (D) via SNI.<=
br>
&gt; <br>
&gt; * The integrity checks on the server=5Fassoc response are unclear. It
is<br>
&gt; not specified if host name verification is performed. (D)<br>
&gt; <br>
&gt; * In a trivial UDP-based implementation, the server=5Fassoc response
is<br>
&gt; computed before two-way communication with the client IP address has<b=
r>
&gt; been proven, resulting in a denial of service vulnerability (CPU<br>
&gt; overload due to signature computation for spoofed clients, traffic<br>
&gt; amplification due to larger server response). This also affects the<br>
&gt; server=5Fcook message generation. Photuris cookies would address this.
(D)<br>
&gt; <br>
&gt; * The server=5Fcook message uses non-hybrid asymmetric encryption. Wit=
h<br>
&gt; ECC, this does not work because the provided payload space is not
large<br>
&gt; enough. The usual hybrid scheme should be used instead. This means
that<br>
&gt; an additional cryptographic primitive has to be negotiated. (D)<br>
&gt; <br>
&gt; * Client certificate management is a red flag for many organizations.
It<br>
&gt; would be better if the protocol would not use a client certificate
at<br>
&gt; all, and some other key agreement scheme (e.g., application key<br>
&gt; extraction with TLS/DTLS, without client certificates, or a TLS respon=
se<br>
&gt; containing an encrypted session key). (D)</font></tt>
<br>
<br><font size=3D3>The client certificates can just be generated on the fly
and don't have to be managed by the organization, i.e. they are self-signed.
Actually, a random public key would be enough at this point, the cert is
just there since it's easier to handle.</font>
<br>
<br><tt><font size=3D2><br>
&gt; <br>
&gt; * With a server without per-client state, the HMAC key setup has to
be<br>
&gt; performed on each response. &nbsp;This is quite costly. &nbsp;A differ=
ent
MAC<br>
&gt; could be quite a bit cheaper in terms of CPU overhead.<br>
&gt; <br>
&gt; * I have doubts about the use of TESLA.<br>
&gt; <br>
&gt; &nbsp; . Is there sufficient operational experience with this protocol=
?<br>
&gt; <br>
&gt; &nbsp; . It is never stated explicitly, but reading the protocol<br>
&gt; descriptions, it is expected that TESLA is secure against malicious<br>
&gt; recipients.<br>
&gt; <br>
&gt; &nbsp; . TESLA uses a race condition for security, which seems inheren=
tly
risky.<br>
&gt; <br>
&gt; &nbsp; . The use of time for security purposes interacts in a complex
way<br>
&gt; with using TESLA for time synchronization.<br>
&gt; <br>
&gt; # draft-ietf-ntp-cms-for-nts-message-02<br>
&gt; <br>
&gt; * DER is used even for fast-path time synchronization messages (not
just<br>
&gt; for the handshake). &nbsp;This seems unnecessary.<br>
&gt; <br>
&gt; * Requiring a new OID in the Extended Key Usages attribute of<br>
&gt; certificates (section 4) means that the browser PKI cannot be used
to<br>
&gt; authenticate hosts. This seems quite wrong.<br>
&gt; <br>
&gt; * Not all CMS algorithm parameters are negotiated at the NTS layer,
as<br>
&gt; suspected. (D)<br>
&gt; <br>
&gt; # draft-ietf-ntp-using-nts-for-ntp-00<br>
&gt; <br>
&gt; * There is no cookie protection of server=5Fassoc/server=5Fcook respon=
ses,<br>
&gt; as explained above. This is quite bad. (D)<br>
&gt; <br>
&gt; * The proposed protocol does not address UDP message size limitations.=
<br>
&gt; UDP fragmentation is fundamentally broken. (D)</font></tt>
<br>
<br><tt><font size=3D2>Actually, that is on our To Do list.</font></tt>
<br>
<br><tt><font size=3D2><br>
&gt; <br>
&gt; -- <br>
&gt; Florian Weimer / Red Hat Product Security<br>
&gt; =5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=
=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F<br>
&gt; ntpwg mailing list<br>
&gt; ntpwg@lists.ntp.org<br>
&gt; </font></tt><a href=3Dhttp://lists.ntp.org/listinfo/ntpwg><tt><font si=
ze=3D2>http://lists.ntp.org/listinfo/ntpwg</font></tt></a>
--=_alternative 004DF89AC1257E23_=--

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

MIAGCSqGSIb3DQEHAqCAMIImzgIBATELMAkGBSsOAwIaBQAwCwYJKoZIhvcNAQcBoIIj4DCCA58w
ggKHoAMCAQICASYwDQYJKoZIhvcNAQEFBQAwcTELMAkGA1UEBhMCREUxHDAaBgNVBAoTE0RldXRz
Y2hlIFRlbGVrb20gQUcxHzAdBgNVBAsTFlQtVGVsZVNlYyBUcnVzdCBDZW50ZXIxIzAhBgNVBAMT
GkRldXRzY2hlIFRlbGVrb20gUm9vdCBDQSAyMB4XDTk5MDcwOTEyMTEwMFoXDTE5MDcwOTIzNTkw
MFowcTELMAkGA1UEBhMCREUxHDAaBgNVBAoTE0RldXRzY2hlIFRlbGVrb20gQUcxHzAdBgNVBAsT
FlQtVGVsZVNlYyBUcnVzdCBDZW50ZXIxIzAhBgNVBAMTGkRldXRzY2hlIFRlbGVrb20gUm9vdCBD
QSAyMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAqwujNeCLKRSxFIWvPBDkOW81XUqu
3ephjZVJ9G9koxpgZqSpQCKE2dSl5XiTDmgBrblNXDrO07ioQkDfz6O6gllqkhusHJraCCslJ/lp
I0fx4Ossepv1EwLQfjR8wp48AFmr9doM9TI8K6xQ2tbD3oOUyqgMmTIOCEhWW2r72uFYWAFJX3JB
PBUGAY5draq4k7TNnuun6GotUjTbOu9cdVHa2/Mx+e5xmDLEVBVEDPmbVe2t3xgIoKOGiknuUwWP
GUzV3lh5m9JqHEKrxdWnz2gPluThYZh2YciRfNY+AOKRUIfhnQrmrZfSHcY6fcu82gM01Y5bAfVq
B7cWtm5KfwIDAQABo0IwQDAdBgNVHQ4EFgQUMcN5G7r1U9cX4Il6LRdsCrMrnTMwDwYDVR0TBAgw
BgEB/wIBBTAOBgNVHQ8BAf8EBAMCAQYwDQYJKoZIhvcNAQEFBQADggEBAJRkWa05ZOcp6xP+WsOL
E1fIBCTwdHfAYONn++mJpoO/loJ8btTDPe+egG67KbSYerE7VOs5F0d+Go4L/B8xWTEEss4X8yzH
YjZV4iLYiVW0mEiqZPrWHDbYRHhaWiM6V5f1ejBPrp9qTEsrjqAD4z7gqdTSe9KzqOJyPK2e/4BZ
5JtFtPY7sM05GZgy5eohYZDkMSGONLH3LzVKhRDa54o3Ib5ZY+DyhYgxU9RUFIVwefQuBncndS8f
uIr5/sW62Dbkg+znZbe/Y1rzRq+BlDfUQYzWI9Yez/VoG0Rjolq6pzVZoeVwBZsOI1eZlAptujlj
KIaS8xiE2PvRzwVWZFcwggOfMIICh6ADAgECAgEmMA0GCSqGSIb3DQEBBQUAMHExCzAJBgNVBAYT
AkRFMRwwGgYDVQQKExNEZXV0c2NoZSBUZWxla29tIEFHMR8wHQYDVQQLExZULVRlbGVTZWMgVHJ1
c3QgQ2VudGVyMSMwIQYDVQQDExpEZXV0c2NoZSBUZWxla29tIFJvb3QgQ0EgMjAeFw05OTA3MDkx
MjExMDBaFw0xOTA3MDkyMzU5MDBaMHExCzAJBgNVBAYTAkRFMRwwGgYDVQQKExNEZXV0c2NoZSBU
ZWxla29tIEFHMR8wHQYDVQQLExZULVRlbGVTZWMgVHJ1c3QgQ2VudGVyMSMwIQYDVQQDExpEZXV0
c2NoZSBUZWxla29tIFJvb3QgQ0EgMjCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBAKsL
ozXgiykUsRSFrzwQ5DlvNV1Krt3qYY2VSfRvZKMaYGakqUAihNnUpeV4kw5oAa25TVw6ztO4qEJA
38+juoJZapIbrBya2ggrJSf5aSNH8eDrLHqb9RMC0H40fMKePABZq/XaDPUyPCusUNrWw96DlMqo
DJkyDghIVltq+9rhWFgBSV9yQTwVBgGOXa2quJO0zZ7rp+hqLVI02zrvXHVR2tvzMfnucZgyxFQV
RAz5m1Xtrd8YCKCjhopJ7lMFjxlM1d5YeZvSahxCq8XVp89oD5bk4WGYdmHIkXzWPgDikVCH4Z0K
5q2X0h3GOn3LvNoDNNWOWwH1age3FrZuSn8CAwEAAaNCMEAwHQYDVR0OBBYEFDHDeRu69VPXF+CJ
ei0XbAqzK50zMA8GA1UdEwQIMAYBAf8CAQUwDgYDVR0PAQH/BAQDAgEGMA0GCSqGSIb3DQEBBQUA
A4IBAQCUZFmtOWTnKesT/lrDixNXyAQk8HR3wGDjZ/vpiaaDv5aCfG7Uwz3vnoBuuym0mHqxO1Tr
ORdHfhqOC/wfMVkxBLLOF/Msx2I2VeIi2IlVtJhIqmT61hw22ER4WlojOleX9XowT66fakxLK46g
A+M+4KnU0nvSs6jicjytnv+AWeSbRbT2O7DNORmYMuXqIWGQ5DEhjjSx9y81SoUQ2ueKNyG+WWPg
8oWIMVPUVBSFcHn0LgZ3J3UvH7iK+f7Futg25IPs52W3v2Na80avgZQ31EGM1iPWHs/1aBtEY6Ja
uqc1WaHlcAWbDiNXmZQKbbo5YyiGkvMYhNj70c8FVmRXMIIEITCCAwmgAwIBAgICAMcwDQYJKoZI
hvcNAQEFBQAwcTELMAkGA1UEBhMCREUxHDAaBgNVBAoTE0RldXRzY2hlIFRlbGVrb20gQUcxHzAd
BgNVBAsTFlQtVGVsZVNlYyBUcnVzdCBDZW50ZXIxIzAhBgNVBAMTGkRldXRzY2hlIFRlbGVrb20g
Um9vdCBDQSAyMB4XDTA2MTIxOTEwMjkwMFoXDTE5MDYzMDIzNTkwMFowWjELMAkGA1UEBhMCREUx
EzARBgNVBAoTCkRGTi1WZXJlaW4xEDAOBgNVBAsTB0RGTi1QS0kxJDAiBgNVBAMTG0RGTi1WZXJl
aW4gUENBIEdsb2JhbCAtIEcwMTCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBAOmbw2eF
+Q2u9Y1Uw5ZQNT1i6W5M7ZTXAFuVInTUIOs0j9bswDEEC5mB4qYU0lKgKCOEi3SJBF5b4OJ4wXjL
FssoNTl7LZBF0O2gAHp8v0oOGwDDhulcKzERewzzgiRDjBw4i2poAJru3E94q9LGE5t2re7eJujv
Aa90D8EJovZrzr3TzRQwT/Xl46TIYpuCGgMnMA0CZWBN7dEJIyqWNVgn03bGcbaQHcTt/zWGfW8z
s9sPxRHCioOhlF1Ba9jSEPVM/cpRrNm975KDu9rrixZWVkPP4dUTPaYfJzDNSVTbyRM0mnF1xWzq
pwuY+SGdJ68+ozk5SGqMrcmZ+8MS8r0CAwEAAaOB2TCB1jBwBgNVHR8EaTBnMGWgY6Bhhl9odHRw
Oi8vcGtpLnRlbGVzZWMuZGUvY2dpLWJpbi9zZXJ2aWNlL2FmX0Rvd25sb2FkQVJMLmNybD8tY3Js
X2Zvcm1hdD1YXzUwOSYtaXNzdWVyPURUX1JPT1RfQ0FfMjAdBgNVHQ4EFgQUSbfGz+g9H3/qRHsT
KffxCnA+3mQwHwYDVR0jBBgwFoAUMcN5G7r1U9cX4Il6LRdsCrMrnTMwDgYDVR0PAQH/BAQDAgEG
MBIGA1UdEwEB/wQIMAYBAf8CAQIwDQYJKoZIhvcNAQEFBQADggEBADvhWnfASBfcqRjsga9aifC9
KJKmylkYEnDsKPLnrn+WLOfyXRkx9hMrdL29gLK592fJOaJ5O+EREe5reJEzfjtfJid1U2WOM2Pu
z3PDsJIjSSFQdSOhHxjilIU9PzPpdyCNor3moYUpQPY/czJYDQlrptqFbMA/u41mZFYkTq4NPzI1
AVvpjILZcllPsYaF8XSFVuXD+Fzzje5Hs1MFcOflTYppgyjhEwmGnl7I6lgeDB/5pNRaBGj9KD6L
ArZYtfahLDdXAGerI2iNY6XvmWtc/UtW9qtAhzTUEZJs7IfFCgsHM3K0bwwdVCzYUcfMvzDTQ3Lx
Mr+MzkljqAD38hwwggQhMIIDCaADAgECAgIAxzANBgkqhkiG9w0BAQUFADBxMQswCQYDVQQGEwJE
RTEcMBoGA1UEChMTRGV1dHNjaGUgVGVsZWtvbSBBRzEfMB0GA1UECxMWVC1UZWxlU2VjIFRydXN0
IENlbnRlcjEjMCEGA1UEAxMaRGV1dHNjaGUgVGVsZWtvbSBSb290IENBIDIwHhcNMDYxMjE5MTAy
OTAwWhcNMTkwNjMwMjM1OTAwWjBaMQswCQYDVQQGEwJERTETMBEGA1UEChMKREZOLVZlcmVpbjEQ
MA4GA1UECxMHREZOLVBLSTEkMCIGA1UEAxMbREZOLVZlcmVpbiBQQ0EgR2xvYmFsIC0gRzAxMIIB
IjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEA6ZvDZ4X5Da71jVTDllA1PWLpbkztlNcAW5Ui
dNQg6zSP1uzAMQQLmYHiphTSUqAoI4SLdIkEXlvg4njBeMsWyyg1OXstkEXQ7aAAeny/Sg4bAMOG
6VwrMRF7DPOCJEOMHDiLamgAmu7cT3ir0sYTm3at7t4m6O8Br3QPwQmi9mvOvdPNFDBP9eXjpMhi
m4IaAycwDQJlYE3t0QkjKpY1WCfTdsZxtpAdxO3/NYZ9bzOz2w/FEcKKg6GUXUFr2NIQ9Uz9ylGs
2b3vkoO72uuLFlZWQ8/h1RM9ph8nMM1JVNvJEzSacXXFbOqnC5j5IZ0nrz6jOTlIaoytyZn7wxLy
vQIDAQABo4HZMIHWMHAGA1UdHwRpMGcwZaBjoGGGX2h0dHA6Ly9wa2kudGVsZXNlYy5kZS9jZ2kt
YmluL3NlcnZpY2UvYWZfRG93bmxvYWRBUkwuY3JsPy1jcmxfZm9ybWF0PVhfNTA5Ji1pc3N1ZXI9
RFRfUk9PVF9DQV8yMB0GA1UdDgQWBBRJt8bP6D0ff+pEexMp9/EKcD7eZDAfBgNVHSMEGDAWgBQx
w3kbuvVT1xfgiXotF2wKsyudMzAOBgNVHQ8BAf8EBAMCAQYwEgYDVR0TAQH/BAgwBgEB/wIBAjAN
BgkqhkiG9w0BAQUFAAOCAQEAO+Fad8BIF9ypGOyBr1qJ8L0okqbKWRgScOwo8ueuf5Ys5/JdGTH2
Eyt0vb2Asrn3Z8k5onk74RER7mt4kTN+O18mJ3VTZY4zY+7Pc8OwkiNJIVB1I6EfGOKUhT0/M+l3
II2iveahhSlA9j9zMlgNCWum2oVswD+7jWZkViROrg0/MjUBW+mMgtlyWU+xhoXxdIVW5cP4XPON
7kezUwVw5+VNimmDKOETCYaeXsjqWB4MH/mk1FoEaP0oPosCtli19qEsN1cAZ6sjaI1jpe+Za1z9
S1b2q0CHNNQRkmzsh8UKCwczcrRvDB1ULNhRx8y/MNNDcvEyv4zOSWOoAPfyHDCCBO8wggPXoAMC
AQICBA0hCk0wDQYJKoZIhvcNAQEFBQAwWjELMAkGA1UEBhMCREUxEzARBgNVBAoTCkRGTi1WZXJl
aW4xEDAOBgNVBAsTB0RGTi1QS0kxJDAiBgNVBAMTG0RGTi1WZXJlaW4gUENBIEdsb2JhbCAtIEcw
MTAeFw0wODEwMjQwODUyMTNaFw0xOTA2MzAwMDAwMDBaMGkxCzAJBgNVBAYTAkRFMS4wLAYDVQQK
EyVQaHlzaWthbGlzY2gtVGVjaG5pc2NoZSBCdW5kZXNhbnN0YWx0MQ8wDQYDVQQDEwZQVEIgQ0Ex
GTAXBgkqhkiG9w0BCQEWCnBraUBwdGIuZGUwggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIB
AQC8CsKDOSrDYswBi5TfxUlODIYEL4+n66/DnYua0jowQyIWvTFjpITNhwMbfPk1KiFmKx2cvtu7
wR7swUPdNlfWNUGJ7/9Q0AmpdsedTMTyFslgJHnJ1v1aojOhPk/MbTuolZuVuJ1ytlVwJAR5/1XU
JpHJ9e6qJJM6CJuo4Ms/3w3uMwgibPaKlSAx2gbI6BKH+p2zlIzoJSDAx64njZClg2i32uLUgoDB
7KEghrdMA2y7nqxzL4Vzb5dY5+y4iZ54txqK7ock+TpfnlBP6RZoChB/qonIle/xv+fqXWeZMhTY
BjYHkSc7+shP4Nb4wnLvv8c77uu3BrOe6e1cyDK3AgMBAAGjggGsMIIBqDASBgNVHRMBAf8ECDAG
AQH/AgEBMAsGA1UdDwQEAwIBBjAdBgNVHQ4EFgQUxIDQbigVaDFa7HBfeI7hMEM46jQwHwYDVR0j
BBgwFoAUSbfGz+g9H3/qRHsTKffxCnA+3mQwFQYDVR0RBA4wDIEKcGtpQHB0Yi5kZTCBiAYDVR0f
BIGAMH4wPaA7oDmGN2h0dHA6Ly9jZHAxLnBjYS5kZm4uZGUvZ2xvYmFsLXJvb3QtY2EvcHViL2Ny
bC9jYWNybC5jcmwwPaA7oDmGN2h0dHA6Ly9jZHAyLnBjYS5kZm4uZGUvZ2xvYmFsLXJvb3QtY2Ev
cHViL2NybC9jYWNybC5jcmwwgaIGCCsGAQUFBwEBBIGVMIGSMEcGCCsGAQUFBzAChjtodHRwOi8v
Y2RwMS5wY2EuZGZuLmRlL2dsb2JhbC1yb290LWNhL3B1Yi9jYWNlcnQvY2FjZXJ0LmNydDBHBggr
BgEFBQcwAoY7aHR0cDovL2NkcDIucGNhLmRmbi5kZS9nbG9iYWwtcm9vdC1jYS9wdWIvY2FjZXJ0
L2NhY2VydC5jcnQwDQYJKoZIhvcNAQEFBQADggEBAJ3KSKdj6GjgE6pSuE74pBcKLfmC2Phy1Gfj
83Lzx9leQX67sL6uTIV5NTQgQDsjTlqyxRQJ5eYhj+ZjwfVS02pDdD+trg2iGp1WdFFsqyhts+oS
M4SpRUuZ83FHEieuWq9teT7bcWPUzckYy4k17u9LAp7+V1h7s6aOpk9RCyA1sSlFTP33O9tpLwXq
KpXHK+zG9JOV7kPDHYLAi2Krw5LB91EBSyXWLu7xK4i6prEUGRWVblckx116ikhBFy3cNr2NGfhh
KiOCphAeIFPCCxOEvRk/LkZRnZaMnHQsUHVuAs2SBB08coYSjF7/NZAXprZlpI2KZiUfeo6JU9bS
UbowggTvMIID16ADAgECAgQNIQpNMA0GCSqGSIb3DQEBBQUAMFoxCzAJBgNVBAYTAkRFMRMwEQYD
VQQKEwpERk4tVmVyZWluMRAwDgYDVQQLEwdERk4tUEtJMSQwIgYDVQQDExtERk4tVmVyZWluIFBD
QSBHbG9iYWwgLSBHMDEwHhcNMDgxMDI0MDg1MjEzWhcNMTkwNjMwMDAwMDAwWjBpMQswCQYDVQQG
EwJERTEuMCwGA1UEChMlUGh5c2lrYWxpc2NoLVRlY2huaXNjaGUgQnVuZGVzYW5zdGFsdDEPMA0G
A1UEAxMGUFRCIENBMRkwFwYJKoZIhvcNAQkBFgpwa2lAcHRiLmRlMIIBIjANBgkqhkiG9w0BAQEF
AAOCAQ8AMIIBCgKCAQEAvArCgzkqw2LMAYuU38VJTgyGBC+Pp+uvw52LmtI6MEMiFr0xY6SEzYcD
G3z5NSohZisdnL7bu8Ee7MFD3TZX1jVBie//UNAJqXbHnUzE8hbJYCR5ydb9WqIzoT5PzG07qJWb
lbidcrZVcCQEef9V1CaRyfXuqiSTOgibqODLP98N7jMIImz2ipUgMdoGyOgSh/qds5SM6CUgwMeu
J42QpYNot9ri1IKAweyhIIa3TANsu56scy+Fc2+XWOfsuImeeLcaiu6HJPk6X55QT+kWaAoQf6qJ
yJXv8b/n6l1nmTIU2AY2B5EnO/rIT+DW+MJy77/HO+7rtwaznuntXMgytwIDAQABo4IBrDCCAagw
EgYDVR0TAQH/BAgwBgEB/wIBATALBgNVHQ8EBAMCAQYwHQYDVR0OBBYEFMSA0G4oFWgxWuxwX3iO
4TBDOOo0MB8GA1UdIwQYMBaAFEm3xs/oPR9/6kR7Eyn38QpwPt5kMBUGA1UdEQQOMAyBCnBraUBw
dGIuZGUwgYgGA1UdHwSBgDB+MD2gO6A5hjdodHRwOi8vY2RwMS5wY2EuZGZuLmRlL2dsb2JhbC1y
b290LWNhL3B1Yi9jcmwvY2FjcmwuY3JsMD2gO6A5hjdodHRwOi8vY2RwMi5wY2EuZGZuLmRlL2ds
b2JhbC1yb290LWNhL3B1Yi9jcmwvY2FjcmwuY3JsMIGiBggrBgEFBQcBAQSBlTCBkjBHBggrBgEF
BQcwAoY7aHR0cDovL2NkcDEucGNhLmRmbi5kZS9nbG9iYWwtcm9vdC1jYS9wdWIvY2FjZXJ0L2Nh
Y2VydC5jcnQwRwYIKwYBBQUHMAKGO2h0dHA6Ly9jZHAyLnBjYS5kZm4uZGUvZ2xvYmFsLXJvb3Qt
Y2EvcHViL2NhY2VydC9jYWNlcnQuY3J0MA0GCSqGSIb3DQEBBQUAA4IBAQCdykinY+ho4BOqUrhO
+KQXCi35gtj4ctRn4/Ny88fZXkF+u7C+rkyFeTU0IEA7I05assUUCeXmIY/mY8H1UtNqQ3Q/ra4N
ohqdVnRRbKsobbPqEjOEqUVLmfNxRxInrlqvbXk+23Fj1M3JGMuJNe7vSwKe/ldYe7OmjqZPUQsg
NbEpRUz99zvbaS8F6iqVxyvsxvSTle5Dwx2CwItiq8OSwfdRAUsl1i7u8SuIuqaxFBkVlW5XJMdd
eopIQRct3Da9jRn4YSojgqYQHiBTwgsThL0ZPy5GUZ2WjJx0LFB1bgLNkgQdPHKGEoxe/zWQF6a2
ZaSNimYlH3qOiVPW0lG6MIIFMTCCBBmgAwIBAgIHF5wEkEK5CzANBgkqhkiG9w0BAQUFADBpMQsw
CQYDVQQGEwJERTEuMCwGA1UEChMlUGh5c2lrYWxpc2NoLVRlY2huaXNjaGUgQnVuZGVzYW5zdGFs
dDEPMA0GA1UEAxMGUFRCIENBMRkwFwYJKoZIhvcNAQkBFgpwa2lAcHRiLmRlMB4XDTE0MDUyMTEw
NTkxMloXDTE3MDUyMDEwNTkxMlowaDELMAkGA1UEBhMCREUxLjAsBgNVBAoTJVBoeXNpa2FsaXNj
aC1UZWNobmlzY2hlIEJ1bmRlc2Fuc3RhbHQxDTALBgNVBAsTBFEuNDIxGjAYBgNVBAMTEURyLiBE
aWV0ZXIgU2lib2xkMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAyYt5z0GIwexbe7Vv
kf+wpeCfISmM1FzPfdbR5jJ2l2AjGNAzqJ+aWKL0adslYl8m7JQE7pPXiTZ6sDiOhICg6XVVlLQl
j3ILO6pkvlIk9auqhRC+9Oo1yXSbbrX8BoFbHF0UdV65MtfzuIzvdInq1mpNW7/sZtlWBxen/HbC
QgVDRkXd5U0OU8wF4RW0OYnF5hxOnMsFIugFHq4oMA92zLk6j5Esk4syOiyJzuf3dDoLzTKg7n+K
3wRl0HvrE9mUgR/nuijICWdETRwKotQu27+VOjWU27w5Flpd8MYiSeV7sJEPukT11m0aQRE4h4VN
2yh24/aRJCxJOA25sW/I5QIDAQABo4IB3TCCAdkwLwYDVR0gBCgwJjARBg8rBgEEAYGtIYIsAQEE
AwEwEQYPKwYBBAGBrSGCLAIBBAMBMAkGA1UdEwQCMAAwCwYDVR0PBAQDAgXgMB8GA1UdJQQYMBYG
CCsGAQUFBwMEBgorBgEEAYI3FAICMB0GA1UdDgQWBBRsyFeB8XX9H0eJUJysSheMBkFZrzAfBgNV
HSMEGDAWgBTEgNBuKBVoMVrscF94juEwQzjqNDAfBgNVHREEGDAWgRRkaWV0ZXIuc2lib2xkQHB0
Yi5kZTB3BgNVHR8EcDBuMDWgM6Axhi9odHRwOi8vY2RwMS5wY2EuZGZuLmRlL3B0Yi1jYS9wdWIv
Y3JsL2NhY3JsLmNybDA1oDOgMYYvaHR0cDovL2NkcDIucGNhLmRmbi5kZS9wdGItY2EvcHViL2Ny
bC9jYWNybC5jcmwwgZIGCCsGAQUFBwEBBIGFMIGCMD8GCCsGAQUFBzAChjNodHRwOi8vY2RwMS5w
Y2EuZGZuLmRlL3B0Yi1jYS9wdWIvY2FjZXJ0L2NhY2VydC5jcnQwPwYIKwYBBQUHMAKGM2h0dHA6
Ly9jZHAyLnBjYS5kZm4uZGUvcHRiLWNhL3B1Yi9jYWNlcnQvY2FjZXJ0LmNydDANBgkqhkiG9w0B
AQUFAAOCAQEAt2XdEe0IxYuz1v6WhXz1+EfnFC3S0Yvx4J438lbPYHFkablzHsgedeZzURxl221T
5SC4i6lC36otU7xZkVuSfyJWkMbozxgE4aA+sTJW37IdRVzQSYXFZa95DPj4B7iw+RHGBTFxbVJm
USzMG8nvykOYcpRkxxLUAZglAPfmvu/X/ixsuy4oA/0OHvpIOG1SumSb325hiP9/dMxHFwjbdyqE
nxQAkGbV5kHE77yaydGlQftM5xheKiPOBzbS2ZlzPP8L8kGPrcLK0/mdW3aW+r35aru5E+515qKm
9O0r7SiTCoNbpGCwo4o+aPDVBSe/BBxTW7St2alvIpSKZjyW6TCCBTEwggQZoAMCAQICBxecBJBC
uQswDQYJKoZIhvcNAQEFBQAwaTELMAkGA1UEBhMCREUxLjAsBgNVBAoTJVBoeXNpa2FsaXNjaC1U
ZWNobmlzY2hlIEJ1bmRlc2Fuc3RhbHQxDzANBgNVBAMTBlBUQiBDQTEZMBcGCSqGSIb3DQEJARYK
cGtpQHB0Yi5kZTAeFw0xNDA1MjExMDU5MTJaFw0xNzA1MjAxMDU5MTJaMGgxCzAJBgNVBAYTAkRF
MS4wLAYDVQQKEyVQaHlzaWthbGlzY2gtVGVjaG5pc2NoZSBCdW5kZXNhbnN0YWx0MQ0wCwYDVQQL
EwRRLjQyMRowGAYDVQQDExFEci4gRGlldGVyIFNpYm9sZDCCASIwDQYJKoZIhvcNAQEBBQADggEP
ADCCAQoCggEBAMmLec9BiMHsW3u1b5H/sKXgnyEpjNRcz33W0eYydpdgIxjQM6ifmlii9GnbJWJf
JuyUBO6T14k2erA4joSAoOl1VZS0JY9yCzuqZL5SJPWrqoUQvvTqNcl0m261/AaBWxxdFHVeuTLX
87iM73SJ6tZqTVu/7GbZVgcXp/x2wkIFQ0ZF3eVNDlPMBeEVtDmJxeYcTpzLBSLoBR6uKDAPdsy5
Oo+RLJOLMjosic7n93Q6C80yoO5/it8EZdB76xPZlIEf57ooyAlnRE0cCqLULtu/lTo1lNu8ORZa
XfDGIknle7CRD7pE9dZtGkEROIeFTdsoduP2kSQsSTgNubFvyOUCAwEAAaOCAd0wggHZMC8GA1Ud
IAQoMCYwEQYPKwYBBAGBrSGCLAEBBAMBMBEGDysGAQQBga0hgiwCAQQDATAJBgNVHRMEAjAAMAsG
A1UdDwQEAwIF4DAfBgNVHSUEGDAWBggrBgEFBQcDBAYKKwYBBAGCNxQCAjAdBgNVHQ4EFgQUbMhX
gfF1/R9HiVCcrEoXjAZBWa8wHwYDVR0jBBgwFoAUxIDQbigVaDFa7HBfeI7hMEM46jQwHwYDVR0R
BBgwFoEUZGlldGVyLnNpYm9sZEBwdGIuZGUwdwYDVR0fBHAwbjA1oDOgMYYvaHR0cDovL2NkcDEu
cGNhLmRmbi5kZS9wdGItY2EvcHViL2NybC9jYWNybC5jcmwwNaAzoDGGL2h0dHA6Ly9jZHAyLnBj
YS5kZm4uZGUvcHRiLWNhL3B1Yi9jcmwvY2FjcmwuY3JsMIGSBggrBgEFBQcBAQSBhTCBgjA/Bggr
BgEFBQcwAoYzaHR0cDovL2NkcDEucGNhLmRmbi5kZS9wdGItY2EvcHViL2NhY2VydC9jYWNlcnQu
Y3J0MD8GCCsGAQUFBzAChjNodHRwOi8vY2RwMi5wY2EuZGZuLmRlL3B0Yi1jYS9wdWIvY2FjZXJ0
L2NhY2VydC5jcnQwDQYJKoZIhvcNAQEFBQADggEBALdl3RHtCMWLs9b+loV89fhH5xQt0tGL8eCe
N/JWz2BxZGm5cx7IHnXmc1EcZdttU+UguIupQt+qLVO8WZFbkn8iVpDG6M8YBOGgPrEyVt+yHUVc
0EmFxWWveQz4+Ae4sPkRxgUxcW1SZlEszBvJ78pDmHKUZMcS1AGYJQD35r7v1/4sbLsuKAP9Dh76
SDhtUrpkm99uYYj/f3TMRxcI23cqhJ8UAJBm1eZBxO+8msnRpUH7TOcYXiojzgc20tmZczz/C/JB
j63CytP5nVt2lvq9+Wq7uRPudeaipvTtK+0okwqDW6RgsKOKPmjw1QUnvwQcU1u0rdmpbyKUimY8
lukxggLJMIICxQIBATB0MGkxCzAJBgNVBAYTAkRFMS4wLAYDVQQKEyVQaHlzaWthbGlzY2gtVGVj
aG5pc2NoZSBCdW5kZXNhbnN0YWx0MQ8wDQYDVQQDEwZQVEIgQ0ExGTAXBgkqhkiG9w0BCQEWCnBr
aUBwdGIuZGUCBxecBJBCuQswCQYFKw4DAhoFAKCCASowGAYJKoZIhvcNAQkDMQsGCSqGSIb3DQEH
ATAcBgkqhkiG9w0BCQUxDxcNMTUwNDEwMTQxMTQwWjAjBgkqhkiG9w0BCQQxFgQU4xGjLcs8HQQf
wQ0hhvPKhOe39/wwQwYJKoZIhvcNAQkPMTYwNDAHBgUrDgMCHTAOBggqhkiG9w0DAgICAIAwCgYI
KoZIhvcNAwcwDQYIKoZIhvcNAwICASgwgYUGCyqGSIb3DQEJEAILMXagdDBpMQswCQYDVQQGEwJE
RTEuMCwGA1UEChMlUGh5c2lrYWxpc2NoLVRlY2huaXNjaGUgQnVuZGVzYW5zdGFsdDEPMA0GA1UE
AxMGUFRCIENBMRkwFwYJKoZIhvcNAQkBFgpwa2lAcHRiLmRlAgcXnASQQrkLMA0GCSqGSIb3DQEB
AQUABIIBAHFZSa3S6+jrTQcVqy6xcd77C2laZLFqNGZUH+D5fOUAFOMEo/S9ma3TzmIWhDOVq+XC
3K8+nwSvyAg65MfilMgbVKxnfUoJwxVM4fKMS5rgqFJ2r+vP8WwGpVPozgZOPkwlhmoUneUCDMnx
rN4gzOWVRVjDmONpVvI7sRLOWawzmmHCvGZIwvfnKbjN9SCehYBBFF0Hepu1s0VKglSFPZgdGDi2
msNMpazhRK82ddmk13mgkvoNIntsvMWNj1s8oRu61EVWlT8rPf/dzyDvFTx6jbg3KaU2xVxjhrg/
tZCnde0OomCwPAN5RFAZEFt7hAHuPGRwAoeNwTh4dNSWKXoAAAAA

---------z48323_boundary_sign--

--===============6148188470893215293==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

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

From ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org  Tue Apr 14 21:09:38 2015
Return-Path: <ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org>
X-Original-To: ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com
Delivered-To: ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2A1011B2BA0 for <ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com>; Tue, 14 Apr 2015 21:09:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level:
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 aEwjHwBkVRA8 for <ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com>; Tue, 14 Apr 2015 21:09:32 -0700 (PDT)
Received: from psp3.ntp.org (psp3.ntp.org [149.20.68.23]) by ietfa.amsl.com (Postfix) with ESMTP id 1EC2E1B2B9F for <ntp-archives-ahFae6za@lists.ietf.org>; Tue, 14 Apr 2015 21:09:32 -0700 (PDT)
Received: from psp3.ntp.org (localhost.ntp.org [127.0.0.1]) by psp3.ntp.org (Postfix) with ESMTP id E96F2398FA for <ntp-archives-ahFae6za@lists.ietf.org>; Tue, 14 Apr 2015 21:09:31 -0700 (PDT)
X-Original-To: ntpwg@lists.ntp.org
Delivered-To: ntpwg@lists.ntp.org
Received: from mail1.ntp.org (mail1.ntp.org [IPv6:2001:4f8:fff7:1::5]) by lists.ntp.org (Postfix) with ESMTP id 4547086D33C for <ntpwg@lists.ntp.org>; Sun, 12 Apr 2015 03:17:24 +0000 (UTC)
Received: from mx1.redhat.com ([209.132.183.28]) by mail1.ntp.org with esmtps (TLSv1:AES256-SHA:256) (Exim 4.77 (FreeBSD)) (envelope-from <fweimer@redhat.com>) id 1Yh8Oa-0003gP-W7 for ntpwg@lists.ntp.org; Sun, 12 Apr 2015 03:17:24 +0000
Received: from int-mx10.intmail.prod.int.phx2.redhat.com (int-mx10.intmail.prod.int.phx2.redhat.com [10.5.11.23]) by mx1.redhat.com (8.14.4/8.14.4) with ESMTP id t3AEWRM5026365 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=FAIL); Fri, 10 Apr 2015 10:32:27 -0400
Received: from oldenburg.str.redhat.com (oldenburg.str.redhat.com [10.33.200.60]) by int-mx10.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4) with ESMTP id t3AEWPPh006434 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 10 Apr 2015 10:32:26 -0400
Message-ID: <5527DEF8.2010305@redhat.com>
Date: Fri, 10 Apr 2015 16:32:24 +0200
From: Florian Weimer <fweimer@redhat.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.6.0
MIME-Version: 1.0
To: dieter.sibold@ptb.de
References: <551D1150.5080500@redhat.com> <OFEC232DE6.A8D2B0E6-ONC1257E23.004D3B95-C1257E23.004DF89C@ptb.de>
In-Reply-To: <OFEC232DE6.A8D2B0E6-ONC1257E23.004D3B95-C1257E23.004DF89C@ptb.de>
X-Scanned-By: MIMEDefang 2.68 on 10.5.11.23
X-SA-Exim-Connect-IP: 209.132.183.28
X-SA-Exim-Rcpt-To: ntpwg@lists.ntp.org
X-SA-Exim-Mail-From: fweimer@redhat.com
X-SA-Exim-Version: 4.2
X-SA-Exim-Scanned: Yes (on mail1.ntp.org)
Subject: Re: [ntpwg] Antwort:  Comments on various NTS drafts
X-BeenThere: ntpwg@lists.ntp.org
X-Mailman-Version: 2.1.20
Precedence: list
List-Id: IETF Working Group for Network Time Protocol <ntpwg.lists.ntp.org>
List-Unsubscribe: <http://lists.ntp.org/options/ntpwg>, <mailto:ntpwg-request@lists.ntp.org?subject=unsubscribe>
List-Archive: <http://lists.ntp.org/pipermail/ntpwg/>
List-Post: <mailto:ntpwg@lists.ntp.org>
List-Help: <mailto:ntpwg-request@lists.ntp.org?subject=help>
List-Subscribe: <http://lists.ntp.org/listinfo/ntpwg>, <mailto:ntpwg-request@lists.ntp.org?subject=subscribe>
Cc: ntpwg@lists.ntp.org
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org
Sender: "ntpwg" <ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org>

On 04/10/2015 04:11 PM, dieter.sibold@ptb.de wrote:
> Hello Florian,
> we added some mor questions to your initial comments.

Thanks.  Note that the NTP WG list at ntp.org appears to be down at the
moment.  I pinged Karen about this because the listmaster address
doesn't seem to work either.

>> I strongly recommend reusing (D)TLS instead of implementing your own
>> cryptographic protocol.  I have marked the issues which would go away
>> with a proper implementation of (D)TLS with ?(D)?.  With DTLS, the
>> server could just send the client cookie and the HMAC key, disregarding
>> the client certificate.
> 
> Do I understand it correctly that you're proposing something like:
> * do the key exchange via dtls
> * the server creates a random client cookie and calculates the client 
> specific key from that (using a server secret as well) and sends both to 
> the client
> * the time sync packets would just send the rand in the request and the 
> server can calculate the shared key for the response

Yes, that's the approach I recommend.  You'd have to design something
pretty much similar to DTLS anyway.

>> * Client certificate management is a red flag for many organizations. It
>> would be better if the protocol would not use a client certificate at
>> all, and some other key agreement scheme (e.g., application key
>> extraction with TLS/DTLS, without client certificates, or a TLS response
>> containing an encrypted session key). (D)
> 
> The client certificates can just be generated on the fly and don't have to 
> be managed by the organization, i.e. they are self-signed. Actually, a 
> random public key would be enough at this point, the cert is just there 
> since it's easier to handle.

Good point.  This is actually what happens behind the scenes in DTLS
with the ephemeral DH cipher suites (which are recommended these days
because they provide forward secrecy).

-- 
Florian Weimer / Red Hat Product Security
_______________________________________________
ntpwg mailing list
ntpwg@lists.ntp.org
http://lists.ntp.org/listinfo/ntpwg

From ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org  Tue Apr 14 21:10:22 2015
Return-Path: <ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org>
X-Original-To: ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com
Delivered-To: ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9C4361B2BA3 for <ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com>; Tue, 14 Apr 2015 21:10:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level:
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 v0HIEq5hgAIJ for <ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com>; Tue, 14 Apr 2015 21:10:21 -0700 (PDT)
Received: from psp3.ntp.org (psp3.ntp.org [149.20.68.23]) by ietfa.amsl.com (Postfix) with ESMTP id 1243B1B2BA2 for <ntp-archives-ahFae6za@lists.ietf.org>; Tue, 14 Apr 2015 21:10:21 -0700 (PDT)
Received: from psp3.ntp.org (localhost.ntp.org [127.0.0.1]) by psp3.ntp.org (Postfix) with ESMTP id 0CFCE39DE1 for <ntp-archives-ahFae6za@lists.ietf.org>; Tue, 14 Apr 2015 21:09:54 -0700 (PDT)
X-Original-To: ntpwg@lists.ntp.org
Delivered-To: ntpwg@lists.ntp.org
Received: from mail1.ntp.org (mail1.ntp.org [IPv6:2001:4f8:fff7:1::5]) by lists.ntp.org (Postfix) with ESMTP id DD65386D33C for <ntpwg@lists.ntp.org>; Sun, 12 Apr 2015 04:57:09 +0000 (UTC)
Received: from mx1.redhat.com ([209.132.183.28]) by mail1.ntp.org with esmtps (TLSv1:AES256-SHA:256) (Exim 4.77 (FreeBSD)) (envelope-from <fweimer@redhat.com>) id 1Yh9x6-0009CN-V0 for ntpwg@lists.ntp.org; Sun, 12 Apr 2015 04:57:09 +0000
Received: from int-mx14.intmail.prod.int.phx2.redhat.com (int-mx14.intmail.prod.int.phx2.redhat.com [10.5.11.27]) by mx1.redhat.com (8.14.4/8.14.4) with ESMTP id t3AF1FJS030102 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=FAIL); Fri, 10 Apr 2015 11:01:15 -0400
Received: from oldenburg.str.redhat.com (oldenburg.str.redhat.com [10.33.200.60]) by int-mx14.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4) with ESMTP id t3AF1DY5008298 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 10 Apr 2015 11:01:14 -0400
Message-ID: <5527E5B9.3000509@redhat.com>
Date: Fri, 10 Apr 2015 17:01:13 +0200
From: Florian Weimer <fweimer@redhat.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.6.0
MIME-Version: 1.0
To: dieter.sibold@ptb.de
References: <551D1150.5080500@redhat.com> <OF1F8E2A91.0B970EC7-ONC1257E22.00357A53-C1257E22.00381DAC@ptb.de> <552663D3.7040005@redhat.com> <OF8C2E5A2A.E24A2F5A-ONC1257E23.00500707-C1257E23.0051D4E9@ptb.de>
In-Reply-To: <OF8C2E5A2A.E24A2F5A-ONC1257E23.00500707-C1257E23.0051D4E9@ptb.de>
X-Scanned-By: MIMEDefang 2.68 on 10.5.11.27
X-SA-Exim-Connect-IP: 209.132.183.28
X-SA-Exim-Rcpt-To: ntpwg@lists.ntp.org
X-SA-Exim-Mail-From: fweimer@redhat.com
X-SA-Exim-Version: 4.2
X-SA-Exim-Scanned: Yes (on mail1.ntp.org)
Subject: Re: [ntpwg] Antwort: Re:  Comments on various NTS drafts
X-BeenThere: ntpwg@lists.ntp.org
X-Mailman-Version: 2.1.20
Precedence: list
List-Id: IETF Working Group for Network Time Protocol <ntpwg.lists.ntp.org>
List-Unsubscribe: <http://lists.ntp.org/options/ntpwg>, <mailto:ntpwg-request@lists.ntp.org?subject=unsubscribe>
List-Archive: <http://lists.ntp.org/pipermail/ntpwg/>
List-Post: <mailto:ntpwg@lists.ntp.org>
List-Help: <mailto:ntpwg-request@lists.ntp.org?subject=help>
List-Subscribe: <http://lists.ntp.org/listinfo/ntpwg>, <mailto:ntpwg-request@lists.ntp.org?subject=subscribe>
Cc: ntpwg@lists.ntp.org
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org
Sender: "ntpwg" <ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org>

On 04/10/2015 04:53 PM, dieter.sibold@ptb.de wrote:

>> You do not periodically refresh asymmetric keys used for the initial
>> handshake.
> 
> No, not the asymmetric keys but for example a random seed value, which 
> will result in a key refreshment.

I'm not sure if that's what is meant by key refresh.  Anyway, I think
periodic refresh is unnecessary with the moderate data rates used for
time synchronization.

>> I expect that rather soon, there will be a requirement to import time in
>> a secure way from one of the national time sources such as PTB or NIST.
>>  (NIST already offers an authenticated time service.)
>>
> Time is already disseminated by the national laboratories by means of NTP. 
> One of the intention of NTS is to secure this process. Yes, it is true 
> that NIST is offering a secured NTP access. But this is done by means of 
> the symmetric pre-shared key approach which is available since NTP version 
> 3.

Yes, and I find this effort rather heroic.  I hope they will chime in
later, once the mailing list service is restored.

> Also PTB is going to offer this service for a limited number of 
> applications. 

Will it be publicly available, perhaps for a fee, or will access be
restricted to certain industries subject to regulation regarding the
synchronization of business clocks?

> Therefore secure time dissemination of national 
> laboratories is not out of scope of this section.

Good to know.

> But out of scope is the 
> cryptographic protections of protocols like GPS, IRIG-B, etc. which are 
> often used to provide time information to the national time servers. That 
> is what section 3.2.10 is talking about.

That wasn't immediately apparent to me.  Thanks for the clarification.

-- 
Florian Weimer / Red Hat Product Security
_______________________________________________
ntpwg mailing list
ntpwg@lists.ntp.org
http://lists.ntp.org/listinfo/ntpwg

From ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org  Tue Apr 14 21:10:29 2015
Return-Path: <ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org>
X-Original-To: ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com
Delivered-To: ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4BAF41B2BA3 for <ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com>; Tue, 14 Apr 2015 21:10:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level:
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 Ya8Uwi3JJv11 for <ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com>; Tue, 14 Apr 2015 21:10:24 -0700 (PDT)
Received: from psp3.ntp.org (psp3.ntp.org [149.20.68.23]) by ietfa.amsl.com (Postfix) with ESMTP id D83E11B2BA1 for <ntp-archives-ahFae6za@lists.ietf.org>; Tue, 14 Apr 2015 21:10:24 -0700 (PDT)
Received: from psp3.ntp.org (localhost.ntp.org [127.0.0.1]) by psp3.ntp.org (Postfix) with ESMTP id 3920C39E9A for <ntp-archives-ahFae6za@lists.ietf.org>; Tue, 14 Apr 2015 21:09:59 -0700 (PDT)
X-Original-To: ntpwg@lists.ntp.org
Delivered-To: ntpwg@lists.ntp.org
Received: from mail1.ntp.org (mail1.ntp.org [IPv6:2001:4f8:fff7:1::5]) by lists.ntp.org (Postfix) with ESMTP id B99B386D33C for <ntpwg@lists.ntp.org>; Sun, 12 Apr 2015 05:49:45 +0000 (UTC)
Received: from mx1.redhat.com ([209.132.183.28]) by mail1.ntp.org with esmtps (TLSv1:AES256-SHA:256) (Exim 4.77 (FreeBSD)) (envelope-from <fweimer@redhat.com>) id 1YhAm1-000C6W-8Z for ntpwg@lists.ntp.org; Sun, 12 Apr 2015 05:49:45 +0000
Received: from int-mx09.intmail.prod.int.phx2.redhat.com (int-mx09.intmail.prod.int.phx2.redhat.com [10.5.11.22]) by mx1.redhat.com (8.14.4/8.14.4) with ESMTP id t39BYkSi032153 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=FAIL); Thu, 9 Apr 2015 07:34:46 -0400
Received: from oldenburg.str.redhat.com (oldenburg.str.redhat.com [10.33.200.60]) by int-mx09.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4) with ESMTP id t39BYifF006012 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 9 Apr 2015 07:34:45 -0400
Message-ID: <552663D3.7040005@redhat.com>
Date: Thu, 09 Apr 2015 13:34:43 +0200
From: Florian Weimer <fweimer@redhat.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.6.0
MIME-Version: 1.0
To: dieter.sibold@ptb.de
References: <551D1150.5080500@redhat.com> <OF1F8E2A91.0B970EC7-ONC1257E22.00357A53-C1257E22.00381DAC@ptb.de>
In-Reply-To: <OF1F8E2A91.0B970EC7-ONC1257E22.00357A53-C1257E22.00381DAC@ptb.de>
X-Scanned-By: MIMEDefang 2.68 on 10.5.11.22
X-SA-Exim-Connect-IP: 209.132.183.28
X-SA-Exim-Rcpt-To: ntpwg@lists.ntp.org
X-SA-Exim-Mail-From: fweimer@redhat.com
X-SA-Exim-Version: 4.2
X-SA-Exim-Scanned: Yes (on mail1.ntp.org)
Subject: Re: [ntpwg] Comments on various NTS drafts
X-BeenThere: ntpwg@lists.ntp.org
X-Mailman-Version: 2.1.20
Precedence: list
List-Id: IETF Working Group for Network Time Protocol <ntpwg.lists.ntp.org>
List-Unsubscribe: <http://lists.ntp.org/options/ntpwg>, <mailto:ntpwg-request@lists.ntp.org?subject=unsubscribe>
List-Archive: <http://lists.ntp.org/pipermail/ntpwg/>
List-Post: <mailto:ntpwg@lists.ntp.org>
List-Help: <mailto:ntpwg-request@lists.ntp.org?subject=help>
List-Subscribe: <http://lists.ntp.org/listinfo/ntpwg>, <mailto:ntpwg-request@lists.ntp.org?subject=subscribe>
Cc: ntpwg@lists.ntp.org
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org
Sender: "ntpwg" <ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org>

On 04/09/2015 12:12 PM, dieter.sibold@ptb.de wrote:

> thanks for your comments and recommendations. We'll carefully look into 
> your comments. We already addressed some of your comments (see inline). 

Thanks.

> Regarding DTLS. Please keep in mind that DTLS requires a layer 3 
> communication. With PTP we also have to consider layer 2 communication 
> channels where DTLS is not applicable.

I think this is based on a misconception.  DTLS requires a datagram
transport, and it has its own fragmentation support, so it should be
perfectly possible to run it on top of a layer 2 transport which has
sufficient frame size (such as Ethernet).

Per-client server-side state would only need to be maintained during the
initial handshake, and not to answer subsequent time queries from
clients (but maintaining such state may be a performance optimization).

>> Section 5.6.1 requires frequent key refresh. This is impossible to
>> implement in practice (ultimate keys cannot be refreshed without
>> operator intervention), and not necessary as long as sufficiently strong
>> cryptographic primitives (non-broken algorithms) are used.
> 
> We don't see a problem with this requirement.

You do not periodically refresh asymmetric keys used for the initial
handshake.

> For clarification. Do you propose to abandon key refreshment at all?

Yes, the message rate is not sufficiently high that this would pose a
problem.  You just have to use cryptographic primitives which are not
known to be broken.

>> In addition, RFC 7384, Section 3.2.10 indicates that securing the time
>> source of an entire organization from an external source is out of
>> scope. However, this is likely the most common application of a security
>> time protocol.
> 
> Please note, that 3.2.10 refers to the connection of reference time (such 
> as GPS, Radio transmitter, ...) to the PTP grandmaster or NTP stratum 1 
> server. These are basically non-IP or non-Ethernet connections and 
> therefore out of scope. 

I expect that rather soon, there will be a requirement to import time in
a secure way from one of the national time sources such as PTB or NIST.
 (NIST already offers an authenticated time service.)

I still haven't read the relevant regulation, though, and it's likely
still ambiguous in this regard.

>> * The integrity checks on the server_assoc response are unclear. It is
>> not specified if host name verification is performed. (D)
> 
> This should be ensured via CMS. But we will check this.

Host name checks are out of scope for CMS, so you have to specify
something on your own.

>> * Client certificate management is a red flag for many organizations. It
>> would be better if the protocol would not use a client certificate at
>> all, and some other key agreement scheme (e.g., application key
>> extraction with TLS/DTLS, without client certificates, or a TLS response
>> containing an encrypted session key). (D)
> 
> We want to have certificates in order to have a mean to provide 
> authorization.

I think it would be best to make them optional.

>> * With a server without per-client state, the HMAC key setup has to be
>> performed on each response.  This is quite costly.  A different MAC
>> could be quite a bit cheaper in terms of CPU overhead.
>
> Which MAC do you propose?

I'd have to do some research on this matter and will report back.  Not
all technical choices will be acceptable to the IETF.

>> * I have doubts about the use of TESLA.

> For us TESLA seems to be an appropriate approach. Do you know a good 
> alternative?

I'm afraid I do not.  (To be clear: If you do not have operational
experience with TESLA that says otherwise, I suspect it will not work in
practice.)

>> * Requiring a new OID in the Extended Key Usages attribute of
>> certificates (section 4) means that the browser PKI cannot be used to
>> authenticate hosts. This seems quite wrong.
> 
> Please describe the problem in more detail.

The existing guidelines for browser CAs discourage signing subscriber
certificates with strange extKeyUsage fields, see these requirements
documents: <https://cabforum.org/baseline-requirements-documents/>

>> # draft-ietf-ntp-using-nts-for-ntp-00
>>
>> * There is no cookie protection of server_assoc/server_cook responses,
>> as explained above. This is quite bad. (D)
> 
> What exactly do you mean by cookie protection?

This is the lack of a Photuris cookie mentioned above.

-- 
Florian Weimer / Red Hat Product Security
_______________________________________________
ntpwg mailing list
ntpwg@lists.ntp.org
http://lists.ntp.org/listinfo/ntpwg

From ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org  Tue Apr 14 21:11:31 2015
Return-Path: <ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org>
X-Original-To: ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com
Delivered-To: ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C72BC1B2BA9 for <ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com>; Tue, 14 Apr 2015 21:11:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.909
X-Spam-Level:
X-Spam-Status: No, score=-1.909 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 rzqkwuHblX2G for <ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com>; Tue, 14 Apr 2015 21:11:30 -0700 (PDT)
Received: from psp3.ntp.org (psp3.ntp.org [149.20.68.23]) by ietfa.amsl.com (Postfix) with ESMTP id 2437D1B2BAE for <ntp-archives-ahFae6za@lists.ietf.org>; Tue, 14 Apr 2015 21:11:30 -0700 (PDT)
Received: from psp3.ntp.org (localhost.ntp.org [127.0.0.1]) by psp3.ntp.org (Postfix) with ESMTP id 50B793A589 for <ntp-archives-ahFae6za@lists.ietf.org>; Tue, 14 Apr 2015 21:10:37 -0700 (PDT)
X-Original-To: ntpwg@lists.ntp.org
Delivered-To: ntpwg@lists.ntp.org
Received: from mail1.ntp.org (mail1.ntp.org [IPv6:2001:4f8:fff7:1::5]) by lists.ntp.org (Postfix) with ESMTP id 4DD1286D33C for <ntpwg@lists.ntp.org>; Tue, 14 Apr 2015 16:25:12 +0000 (UTC)
Received: from mx1.bs.ptb.de ([192.53.103.106]) by mail1.ntp.org with esmtps (TLSv1:AES256-SHA:256) (Exim 4.77 (FreeBSD)) (envelope-from <dieter.sibold@ptb.de>) id 1Yi3e4-000Bv2-Ao for ntpwg@lists.ntp.org; Tue, 14 Apr 2015 16:25:12 +0000
Received: from mx1.bs.ptb.de (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id 8FFD4D6A531; Tue, 14 Apr 2015 18:23:45 +0200 (CEST)
Received: from rose.bs.ptb.de (rose.bs.ptb.de [141.25.85.201]) by mx1.bs.ptb.de (Postfix) with ESMTP id 7DF00D6A59C; Tue, 14 Apr 2015 18:23:45 +0200 (CEST)
In-Reply-To: <552663D3.7040005@redhat.com>
References: <551D1150.5080500@redhat.com> <OF1F8E2A91.0B970EC7-ONC1257E22.00357A53-C1257E22.00381DAC@ptb.de> <552663D3.7040005@redhat.com>
To: Florian Weimer <fweimer@redhat.com>
MIME-Version: 1.0
X-KeepSent: 4709762A:D10331C0-C1257E27:0059C998; type=4; name=$KeepSent
X-Mailer: IBM Notes Release 9.0.1FP3 January  12, 2015
Message-ID: <OF4709762A.D10331C0-ONC1257E27.0059C998-C1257E27.005A0FCF@ptb.de>
From: dieter.sibold@ptb.de
Date: Tue, 14 Apr 2015 18:23:42 +0200
X-MIMETrack: S/MIME Sign by eclipse on Dieter Sibold/PTB(Release 9.0.1FP3|January 12, 2015) at 14.04.2015 18:23:42, Serialize by eclipse on Dieter Sibold/PTB(Release 9.0.1FP3|January  12, 2015) at 14.04.2015 18:23:42, Serialize complete at 14.04.2015 18:23:42, Itemize by eclipse on Dieter Sibold/PTB(Release 9.0.1FP3|January  12, 2015) at 14.04.2015 18:23:44, S/MIME Sign complete at 14.04.2015 18:23:44, Serialize by Router on ROSE/PTB(Release 9.0.1FP3HF79 | February 9, 2015) at 04/14/2015 18:23:45, Serialize complete at 04/14/2015 18:23:45
X-SA-Exim-Connect-IP: 192.53.103.106
X-SA-Exim-Rcpt-To: ntpwg@lists.ntp.org
X-SA-Exim-Mail-From: dieter.sibold@ptb.de
X-SA-Exim-Version: 4.2
X-SA-Exim-Scanned: Yes (on mail1.ntp.org)
Subject: [ntpwg] Antwort: Re:  Comments on various NTS drafts
X-BeenThere: ntpwg@lists.ntp.org
X-Mailman-Version: 2.1.20
Precedence: list
List-Id: IETF Working Group for Network Time Protocol <ntpwg.lists.ntp.org>
List-Unsubscribe: <http://lists.ntp.org/options/ntpwg>, <mailto:ntpwg-request@lists.ntp.org?subject=unsubscribe>
List-Archive: <http://lists.ntp.org/pipermail/ntpwg/>
List-Post: <mailto:ntpwg@lists.ntp.org>
List-Help: <mailto:ntpwg-request@lists.ntp.org?subject=help>
List-Subscribe: <http://lists.ntp.org/listinfo/ntpwg>, <mailto:ntpwg-request@lists.ntp.org?subject=subscribe>
Cc: ntpwg@lists.ntp.org
Content-Type: multipart/mixed; boundary="===============6166945497415422967=="
Errors-To: ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org
Sender: "ntpwg" <ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org>

This is an S/MIME signed message.

--===============6166945497415422967==
Content-Type: multipart/signed;
	 protocol="application/x-pkcs7-signature";
	 micalg=sha1;
	 boundary=-------z3808_boundary_sign

This is an S/MIME signed message.

---------z3808_boundary_sign
Content-Type: multipart/alternative; boundary="=_alternative 005A0FCEC1257E27_="

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

Florian Weimer <fweimer@redhat.com> schrieb am 09.04.2015 13:34:43:

> Von: Florian Weimer <fweimer@redhat.com>
> An: dieter.sibold@ptb.de
> Kopie: ntpwg@lists.ntp.org
> Datum: 09.04.2015 13:34
> Betreff: Re: [ntpwg] Comments on various NTS drafts
> 
> On 04/09/2015 12:12 PM, dieter.sibold@ptb.de wrote:
> 
> > thanks for your comments and recommendations. We'll carefully look 
into 
> > your comments. We already addressed some of your comments (see 
inline). 
> 
> Thanks.
> 
> > Regarding DTLS. Please keep in mind that DTLS requires a layer 3 
> > communication. With PTP we also have to consider layer 2 communication 

> > channels where DTLS is not applicable.
> 
> I think this is based on a misconception.  DTLS requires a datagram
> transport, and it has its own fragmentation support, so it should be
> perfectly possible to run it on top of a layer 2 transport which has
> sufficient frame size (such as Ethernet).

Okay, I didn't know this. Do you know if there are implementations 
available to use DTLS over Ethernet?


> 
> Per-client server-side state would only need to be maintained during the
> initial handshake, and not to answer subsequent time queries from
> clients (but maintaining such state may be a performance optimization).
> 

--=_alternative 005A0FCEC1257E27_=
Content-Type: text/html; charset="US-ASCII"

<font size=2 face="sans-serif"><br>
</font>
<br>
<br><tt><font size=2>Florian Weimer &lt;fweimer@redhat.com&gt; schrieb
am 09.04.2015 13:34:43:<br>
<br>
&gt; Von: Florian Weimer &lt;fweimer@redhat.com&gt;</font></tt>
<br><tt><font size=2>&gt; An: dieter.sibold@ptb.de</font></tt>
<br><tt><font size=2>&gt; Kopie: ntpwg@lists.ntp.org</font></tt>
<br><tt><font size=2>&gt; Datum: 09.04.2015 13:34</font></tt>
<br><tt><font size=2>&gt; Betreff: Re: [ntpwg] Comments on various NTS
drafts</font></tt>
<br><tt><font size=2>&gt; <br>
&gt; On 04/09/2015 12:12 PM, dieter.sibold@ptb.de wrote:<br>
&gt; <br>
&gt; &gt; thanks for your comments and recommendations. We'll carefully
look into <br>
&gt; &gt; your comments. We already addressed some of your comments (see
inline). <br>
&gt; <br>
&gt; Thanks.<br>
&gt; <br>
&gt; &gt; Regarding DTLS. Please keep in mind that DTLS requires a layer
3 <br>
&gt; &gt; communication. With PTP we also have to consider layer 2 communication
<br>
&gt; &gt; channels where DTLS is not applicable.<br>
&gt; <br>
&gt; I think this is based on a misconception. &nbsp;DTLS requires a datagram<br>
&gt; transport, and it has its own fragmentation support, so it should
be<br>
&gt; perfectly possible to run it on top of a layer 2 transport which has<br>
&gt; sufficient frame size (such as Ethernet).</font></tt>
<br>
<br><tt><font size=2>Okay, I didn't know this. Do you know if there are
implementations available to use DTLS over Ethernet?</font></tt>
<br>
<br><tt><font size=2><br>
&gt; <br>
&gt; Per-client server-side state would only need to be maintained during
the<br>
&gt; initial handshake, and not to answer subsequent time queries from<br>
&gt; clients (but maintaining such state may be a performance optimization).<br>
&gt; <br>
</font></tt>
--=_alternative 005A0FCEC1257E27_=--

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

MIAGCSqGSIb3DQEHAqCAMIImzgIBATELMAkGBSsOAwIaBQAwCwYJKoZIhvcNAQcBoIIj4DCCA58w
ggKHoAMCAQICASYwDQYJKoZIhvcNAQEFBQAwcTELMAkGA1UEBhMCREUxHDAaBgNVBAoTE0RldXRz
Y2hlIFRlbGVrb20gQUcxHzAdBgNVBAsTFlQtVGVsZVNlYyBUcnVzdCBDZW50ZXIxIzAhBgNVBAMT
GkRldXRzY2hlIFRlbGVrb20gUm9vdCBDQSAyMB4XDTk5MDcwOTEyMTEwMFoXDTE5MDcwOTIzNTkw
MFowcTELMAkGA1UEBhMCREUxHDAaBgNVBAoTE0RldXRzY2hlIFRlbGVrb20gQUcxHzAdBgNVBAsT
FlQtVGVsZVNlYyBUcnVzdCBDZW50ZXIxIzAhBgNVBAMTGkRldXRzY2hlIFRlbGVrb20gUm9vdCBD
QSAyMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAqwujNeCLKRSxFIWvPBDkOW81XUqu
3ephjZVJ9G9koxpgZqSpQCKE2dSl5XiTDmgBrblNXDrO07ioQkDfz6O6gllqkhusHJraCCslJ/lp
I0fx4Ossepv1EwLQfjR8wp48AFmr9doM9TI8K6xQ2tbD3oOUyqgMmTIOCEhWW2r72uFYWAFJX3JB
PBUGAY5draq4k7TNnuun6GotUjTbOu9cdVHa2/Mx+e5xmDLEVBVEDPmbVe2t3xgIoKOGiknuUwWP
GUzV3lh5m9JqHEKrxdWnz2gPluThYZh2YciRfNY+AOKRUIfhnQrmrZfSHcY6fcu82gM01Y5bAfVq
B7cWtm5KfwIDAQABo0IwQDAdBgNVHQ4EFgQUMcN5G7r1U9cX4Il6LRdsCrMrnTMwDwYDVR0TBAgw
BgEB/wIBBTAOBgNVHQ8BAf8EBAMCAQYwDQYJKoZIhvcNAQEFBQADggEBAJRkWa05ZOcp6xP+WsOL
E1fIBCTwdHfAYONn++mJpoO/loJ8btTDPe+egG67KbSYerE7VOs5F0d+Go4L/B8xWTEEss4X8yzH
YjZV4iLYiVW0mEiqZPrWHDbYRHhaWiM6V5f1ejBPrp9qTEsrjqAD4z7gqdTSe9KzqOJyPK2e/4BZ
5JtFtPY7sM05GZgy5eohYZDkMSGONLH3LzVKhRDa54o3Ib5ZY+DyhYgxU9RUFIVwefQuBncndS8f
uIr5/sW62Dbkg+znZbe/Y1rzRq+BlDfUQYzWI9Yez/VoG0Rjolq6pzVZoeVwBZsOI1eZlAptujlj
KIaS8xiE2PvRzwVWZFcwggOfMIICh6ADAgECAgEmMA0GCSqGSIb3DQEBBQUAMHExCzAJBgNVBAYT
AkRFMRwwGgYDVQQKExNEZXV0c2NoZSBUZWxla29tIEFHMR8wHQYDVQQLExZULVRlbGVTZWMgVHJ1
c3QgQ2VudGVyMSMwIQYDVQQDExpEZXV0c2NoZSBUZWxla29tIFJvb3QgQ0EgMjAeFw05OTA3MDkx
MjExMDBaFw0xOTA3MDkyMzU5MDBaMHExCzAJBgNVBAYTAkRFMRwwGgYDVQQKExNEZXV0c2NoZSBU
ZWxla29tIEFHMR8wHQYDVQQLExZULVRlbGVTZWMgVHJ1c3QgQ2VudGVyMSMwIQYDVQQDExpEZXV0
c2NoZSBUZWxla29tIFJvb3QgQ0EgMjCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBAKsL
ozXgiykUsRSFrzwQ5DlvNV1Krt3qYY2VSfRvZKMaYGakqUAihNnUpeV4kw5oAa25TVw6ztO4qEJA
38+juoJZapIbrBya2ggrJSf5aSNH8eDrLHqb9RMC0H40fMKePABZq/XaDPUyPCusUNrWw96DlMqo
DJkyDghIVltq+9rhWFgBSV9yQTwVBgGOXa2quJO0zZ7rp+hqLVI02zrvXHVR2tvzMfnucZgyxFQV
RAz5m1Xtrd8YCKCjhopJ7lMFjxlM1d5YeZvSahxCq8XVp89oD5bk4WGYdmHIkXzWPgDikVCH4Z0K
5q2X0h3GOn3LvNoDNNWOWwH1age3FrZuSn8CAwEAAaNCMEAwHQYDVR0OBBYEFDHDeRu69VPXF+CJ
ei0XbAqzK50zMA8GA1UdEwQIMAYBAf8CAQUwDgYDVR0PAQH/BAQDAgEGMA0GCSqGSIb3DQEBBQUA
A4IBAQCUZFmtOWTnKesT/lrDixNXyAQk8HR3wGDjZ/vpiaaDv5aCfG7Uwz3vnoBuuym0mHqxO1Tr
ORdHfhqOC/wfMVkxBLLOF/Msx2I2VeIi2IlVtJhIqmT61hw22ER4WlojOleX9XowT66fakxLK46g
A+M+4KnU0nvSs6jicjytnv+AWeSbRbT2O7DNORmYMuXqIWGQ5DEhjjSx9y81SoUQ2ueKNyG+WWPg
8oWIMVPUVBSFcHn0LgZ3J3UvH7iK+f7Futg25IPs52W3v2Na80avgZQ31EGM1iPWHs/1aBtEY6Ja
uqc1WaHlcAWbDiNXmZQKbbo5YyiGkvMYhNj70c8FVmRXMIIEITCCAwmgAwIBAgICAMcwDQYJKoZI
hvcNAQEFBQAwcTELMAkGA1UEBhMCREUxHDAaBgNVBAoTE0RldXRzY2hlIFRlbGVrb20gQUcxHzAd
BgNVBAsTFlQtVGVsZVNlYyBUcnVzdCBDZW50ZXIxIzAhBgNVBAMTGkRldXRzY2hlIFRlbGVrb20g
Um9vdCBDQSAyMB4XDTA2MTIxOTEwMjkwMFoXDTE5MDYzMDIzNTkwMFowWjELMAkGA1UEBhMCREUx
EzARBgNVBAoTCkRGTi1WZXJlaW4xEDAOBgNVBAsTB0RGTi1QS0kxJDAiBgNVBAMTG0RGTi1WZXJl
aW4gUENBIEdsb2JhbCAtIEcwMTCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBAOmbw2eF
+Q2u9Y1Uw5ZQNT1i6W5M7ZTXAFuVInTUIOs0j9bswDEEC5mB4qYU0lKgKCOEi3SJBF5b4OJ4wXjL
FssoNTl7LZBF0O2gAHp8v0oOGwDDhulcKzERewzzgiRDjBw4i2poAJru3E94q9LGE5t2re7eJujv
Aa90D8EJovZrzr3TzRQwT/Xl46TIYpuCGgMnMA0CZWBN7dEJIyqWNVgn03bGcbaQHcTt/zWGfW8z
s9sPxRHCioOhlF1Ba9jSEPVM/cpRrNm975KDu9rrixZWVkPP4dUTPaYfJzDNSVTbyRM0mnF1xWzq
pwuY+SGdJ68+ozk5SGqMrcmZ+8MS8r0CAwEAAaOB2TCB1jBwBgNVHR8EaTBnMGWgY6Bhhl9odHRw
Oi8vcGtpLnRlbGVzZWMuZGUvY2dpLWJpbi9zZXJ2aWNlL2FmX0Rvd25sb2FkQVJMLmNybD8tY3Js
X2Zvcm1hdD1YXzUwOSYtaXNzdWVyPURUX1JPT1RfQ0FfMjAdBgNVHQ4EFgQUSbfGz+g9H3/qRHsT
KffxCnA+3mQwHwYDVR0jBBgwFoAUMcN5G7r1U9cX4Il6LRdsCrMrnTMwDgYDVR0PAQH/BAQDAgEG
MBIGA1UdEwEB/wQIMAYBAf8CAQIwDQYJKoZIhvcNAQEFBQADggEBADvhWnfASBfcqRjsga9aifC9
KJKmylkYEnDsKPLnrn+WLOfyXRkx9hMrdL29gLK592fJOaJ5O+EREe5reJEzfjtfJid1U2WOM2Pu
z3PDsJIjSSFQdSOhHxjilIU9PzPpdyCNor3moYUpQPY/czJYDQlrptqFbMA/u41mZFYkTq4NPzI1
AVvpjILZcllPsYaF8XSFVuXD+Fzzje5Hs1MFcOflTYppgyjhEwmGnl7I6lgeDB/5pNRaBGj9KD6L
ArZYtfahLDdXAGerI2iNY6XvmWtc/UtW9qtAhzTUEZJs7IfFCgsHM3K0bwwdVCzYUcfMvzDTQ3Lx
Mr+MzkljqAD38hwwggQhMIIDCaADAgECAgIAxzANBgkqhkiG9w0BAQUFADBxMQswCQYDVQQGEwJE
RTEcMBoGA1UEChMTRGV1dHNjaGUgVGVsZWtvbSBBRzEfMB0GA1UECxMWVC1UZWxlU2VjIFRydXN0
IENlbnRlcjEjMCEGA1UEAxMaRGV1dHNjaGUgVGVsZWtvbSBSb290IENBIDIwHhcNMDYxMjE5MTAy
OTAwWhcNMTkwNjMwMjM1OTAwWjBaMQswCQYDVQQGEwJERTETMBEGA1UEChMKREZOLVZlcmVpbjEQ
MA4GA1UECxMHREZOLVBLSTEkMCIGA1UEAxMbREZOLVZlcmVpbiBQQ0EgR2xvYmFsIC0gRzAxMIIB
IjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEA6ZvDZ4X5Da71jVTDllA1PWLpbkztlNcAW5Ui
dNQg6zSP1uzAMQQLmYHiphTSUqAoI4SLdIkEXlvg4njBeMsWyyg1OXstkEXQ7aAAeny/Sg4bAMOG
6VwrMRF7DPOCJEOMHDiLamgAmu7cT3ir0sYTm3at7t4m6O8Br3QPwQmi9mvOvdPNFDBP9eXjpMhi
m4IaAycwDQJlYE3t0QkjKpY1WCfTdsZxtpAdxO3/NYZ9bzOz2w/FEcKKg6GUXUFr2NIQ9Uz9ylGs
2b3vkoO72uuLFlZWQ8/h1RM9ph8nMM1JVNvJEzSacXXFbOqnC5j5IZ0nrz6jOTlIaoytyZn7wxLy
vQIDAQABo4HZMIHWMHAGA1UdHwRpMGcwZaBjoGGGX2h0dHA6Ly9wa2kudGVsZXNlYy5kZS9jZ2kt
YmluL3NlcnZpY2UvYWZfRG93bmxvYWRBUkwuY3JsPy1jcmxfZm9ybWF0PVhfNTA5Ji1pc3N1ZXI9
RFRfUk9PVF9DQV8yMB0GA1UdDgQWBBRJt8bP6D0ff+pEexMp9/EKcD7eZDAfBgNVHSMEGDAWgBQx
w3kbuvVT1xfgiXotF2wKsyudMzAOBgNVHQ8BAf8EBAMCAQYwEgYDVR0TAQH/BAgwBgEB/wIBAjAN
BgkqhkiG9w0BAQUFAAOCAQEAO+Fad8BIF9ypGOyBr1qJ8L0okqbKWRgScOwo8ueuf5Ys5/JdGTH2
Eyt0vb2Asrn3Z8k5onk74RER7mt4kTN+O18mJ3VTZY4zY+7Pc8OwkiNJIVB1I6EfGOKUhT0/M+l3
II2iveahhSlA9j9zMlgNCWum2oVswD+7jWZkViROrg0/MjUBW+mMgtlyWU+xhoXxdIVW5cP4XPON
7kezUwVw5+VNimmDKOETCYaeXsjqWB4MH/mk1FoEaP0oPosCtli19qEsN1cAZ6sjaI1jpe+Za1z9
S1b2q0CHNNQRkmzsh8UKCwczcrRvDB1ULNhRx8y/MNNDcvEyv4zOSWOoAPfyHDCCBO8wggPXoAMC
AQICBA0hCk0wDQYJKoZIhvcNAQEFBQAwWjELMAkGA1UEBhMCREUxEzARBgNVBAoTCkRGTi1WZXJl
aW4xEDAOBgNVBAsTB0RGTi1QS0kxJDAiBgNVBAMTG0RGTi1WZXJlaW4gUENBIEdsb2JhbCAtIEcw
MTAeFw0wODEwMjQwODUyMTNaFw0xOTA2MzAwMDAwMDBaMGkxCzAJBgNVBAYTAkRFMS4wLAYDVQQK
EyVQaHlzaWthbGlzY2gtVGVjaG5pc2NoZSBCdW5kZXNhbnN0YWx0MQ8wDQYDVQQDEwZQVEIgQ0Ex
GTAXBgkqhkiG9w0BCQEWCnBraUBwdGIuZGUwggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIB
AQC8CsKDOSrDYswBi5TfxUlODIYEL4+n66/DnYua0jowQyIWvTFjpITNhwMbfPk1KiFmKx2cvtu7
wR7swUPdNlfWNUGJ7/9Q0AmpdsedTMTyFslgJHnJ1v1aojOhPk/MbTuolZuVuJ1ytlVwJAR5/1XU
JpHJ9e6qJJM6CJuo4Ms/3w3uMwgibPaKlSAx2gbI6BKH+p2zlIzoJSDAx64njZClg2i32uLUgoDB
7KEghrdMA2y7nqxzL4Vzb5dY5+y4iZ54txqK7ock+TpfnlBP6RZoChB/qonIle/xv+fqXWeZMhTY
BjYHkSc7+shP4Nb4wnLvv8c77uu3BrOe6e1cyDK3AgMBAAGjggGsMIIBqDASBgNVHRMBAf8ECDAG
AQH/AgEBMAsGA1UdDwQEAwIBBjAdBgNVHQ4EFgQUxIDQbigVaDFa7HBfeI7hMEM46jQwHwYDVR0j
BBgwFoAUSbfGz+g9H3/qRHsTKffxCnA+3mQwFQYDVR0RBA4wDIEKcGtpQHB0Yi5kZTCBiAYDVR0f
BIGAMH4wPaA7oDmGN2h0dHA6Ly9jZHAxLnBjYS5kZm4uZGUvZ2xvYmFsLXJvb3QtY2EvcHViL2Ny
bC9jYWNybC5jcmwwPaA7oDmGN2h0dHA6Ly9jZHAyLnBjYS5kZm4uZGUvZ2xvYmFsLXJvb3QtY2Ev
cHViL2NybC9jYWNybC5jcmwwgaIGCCsGAQUFBwEBBIGVMIGSMEcGCCsGAQUFBzAChjtodHRwOi8v
Y2RwMS5wY2EuZGZuLmRlL2dsb2JhbC1yb290LWNhL3B1Yi9jYWNlcnQvY2FjZXJ0LmNydDBHBggr
BgEFBQcwAoY7aHR0cDovL2NkcDIucGNhLmRmbi5kZS9nbG9iYWwtcm9vdC1jYS9wdWIvY2FjZXJ0
L2NhY2VydC5jcnQwDQYJKoZIhvcNAQEFBQADggEBAJ3KSKdj6GjgE6pSuE74pBcKLfmC2Phy1Gfj
83Lzx9leQX67sL6uTIV5NTQgQDsjTlqyxRQJ5eYhj+ZjwfVS02pDdD+trg2iGp1WdFFsqyhts+oS
M4SpRUuZ83FHEieuWq9teT7bcWPUzckYy4k17u9LAp7+V1h7s6aOpk9RCyA1sSlFTP33O9tpLwXq
KpXHK+zG9JOV7kPDHYLAi2Krw5LB91EBSyXWLu7xK4i6prEUGRWVblckx116ikhBFy3cNr2NGfhh
KiOCphAeIFPCCxOEvRk/LkZRnZaMnHQsUHVuAs2SBB08coYSjF7/NZAXprZlpI2KZiUfeo6JU9bS
UbowggTvMIID16ADAgECAgQNIQpNMA0GCSqGSIb3DQEBBQUAMFoxCzAJBgNVBAYTAkRFMRMwEQYD
VQQKEwpERk4tVmVyZWluMRAwDgYDVQQLEwdERk4tUEtJMSQwIgYDVQQDExtERk4tVmVyZWluIFBD
QSBHbG9iYWwgLSBHMDEwHhcNMDgxMDI0MDg1MjEzWhcNMTkwNjMwMDAwMDAwWjBpMQswCQYDVQQG
EwJERTEuMCwGA1UEChMlUGh5c2lrYWxpc2NoLVRlY2huaXNjaGUgQnVuZGVzYW5zdGFsdDEPMA0G
A1UEAxMGUFRCIENBMRkwFwYJKoZIhvcNAQkBFgpwa2lAcHRiLmRlMIIBIjANBgkqhkiG9w0BAQEF
AAOCAQ8AMIIBCgKCAQEAvArCgzkqw2LMAYuU38VJTgyGBC+Pp+uvw52LmtI6MEMiFr0xY6SEzYcD
G3z5NSohZisdnL7bu8Ee7MFD3TZX1jVBie//UNAJqXbHnUzE8hbJYCR5ydb9WqIzoT5PzG07qJWb
lbidcrZVcCQEef9V1CaRyfXuqiSTOgibqODLP98N7jMIImz2ipUgMdoGyOgSh/qds5SM6CUgwMeu
J42QpYNot9ri1IKAweyhIIa3TANsu56scy+Fc2+XWOfsuImeeLcaiu6HJPk6X55QT+kWaAoQf6qJ
yJXv8b/n6l1nmTIU2AY2B5EnO/rIT+DW+MJy77/HO+7rtwaznuntXMgytwIDAQABo4IBrDCCAagw
EgYDVR0TAQH/BAgwBgEB/wIBATALBgNVHQ8EBAMCAQYwHQYDVR0OBBYEFMSA0G4oFWgxWuxwX3iO
4TBDOOo0MB8GA1UdIwQYMBaAFEm3xs/oPR9/6kR7Eyn38QpwPt5kMBUGA1UdEQQOMAyBCnBraUBw
dGIuZGUwgYgGA1UdHwSBgDB+MD2gO6A5hjdodHRwOi8vY2RwMS5wY2EuZGZuLmRlL2dsb2JhbC1y
b290LWNhL3B1Yi9jcmwvY2FjcmwuY3JsMD2gO6A5hjdodHRwOi8vY2RwMi5wY2EuZGZuLmRlL2ds
b2JhbC1yb290LWNhL3B1Yi9jcmwvY2FjcmwuY3JsMIGiBggrBgEFBQcBAQSBlTCBkjBHBggrBgEF
BQcwAoY7aHR0cDovL2NkcDEucGNhLmRmbi5kZS9nbG9iYWwtcm9vdC1jYS9wdWIvY2FjZXJ0L2Nh
Y2VydC5jcnQwRwYIKwYBBQUHMAKGO2h0dHA6Ly9jZHAyLnBjYS5kZm4uZGUvZ2xvYmFsLXJvb3Qt
Y2EvcHViL2NhY2VydC9jYWNlcnQuY3J0MA0GCSqGSIb3DQEBBQUAA4IBAQCdykinY+ho4BOqUrhO
+KQXCi35gtj4ctRn4/Ny88fZXkF+u7C+rkyFeTU0IEA7I05assUUCeXmIY/mY8H1UtNqQ3Q/ra4N
ohqdVnRRbKsobbPqEjOEqUVLmfNxRxInrlqvbXk+23Fj1M3JGMuJNe7vSwKe/ldYe7OmjqZPUQsg
NbEpRUz99zvbaS8F6iqVxyvsxvSTle5Dwx2CwItiq8OSwfdRAUsl1i7u8SuIuqaxFBkVlW5XJMdd
eopIQRct3Da9jRn4YSojgqYQHiBTwgsThL0ZPy5GUZ2WjJx0LFB1bgLNkgQdPHKGEoxe/zWQF6a2
ZaSNimYlH3qOiVPW0lG6MIIFMTCCBBmgAwIBAgIHF5wEkEK5CzANBgkqhkiG9w0BAQUFADBpMQsw
CQYDVQQGEwJERTEuMCwGA1UEChMlUGh5c2lrYWxpc2NoLVRlY2huaXNjaGUgQnVuZGVzYW5zdGFs
dDEPMA0GA1UEAxMGUFRCIENBMRkwFwYJKoZIhvcNAQkBFgpwa2lAcHRiLmRlMB4XDTE0MDUyMTEw
NTkxMloXDTE3MDUyMDEwNTkxMlowaDELMAkGA1UEBhMCREUxLjAsBgNVBAoTJVBoeXNpa2FsaXNj
aC1UZWNobmlzY2hlIEJ1bmRlc2Fuc3RhbHQxDTALBgNVBAsTBFEuNDIxGjAYBgNVBAMTEURyLiBE
aWV0ZXIgU2lib2xkMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAyYt5z0GIwexbe7Vv
kf+wpeCfISmM1FzPfdbR5jJ2l2AjGNAzqJ+aWKL0adslYl8m7JQE7pPXiTZ6sDiOhICg6XVVlLQl
j3ILO6pkvlIk9auqhRC+9Oo1yXSbbrX8BoFbHF0UdV65MtfzuIzvdInq1mpNW7/sZtlWBxen/HbC
QgVDRkXd5U0OU8wF4RW0OYnF5hxOnMsFIugFHq4oMA92zLk6j5Esk4syOiyJzuf3dDoLzTKg7n+K
3wRl0HvrE9mUgR/nuijICWdETRwKotQu27+VOjWU27w5Flpd8MYiSeV7sJEPukT11m0aQRE4h4VN
2yh24/aRJCxJOA25sW/I5QIDAQABo4IB3TCCAdkwLwYDVR0gBCgwJjARBg8rBgEEAYGtIYIsAQEE
AwEwEQYPKwYBBAGBrSGCLAIBBAMBMAkGA1UdEwQCMAAwCwYDVR0PBAQDAgXgMB8GA1UdJQQYMBYG
CCsGAQUFBwMEBgorBgEEAYI3FAICMB0GA1UdDgQWBBRsyFeB8XX9H0eJUJysSheMBkFZrzAfBgNV
HSMEGDAWgBTEgNBuKBVoMVrscF94juEwQzjqNDAfBgNVHREEGDAWgRRkaWV0ZXIuc2lib2xkQHB0
Yi5kZTB3BgNVHR8EcDBuMDWgM6Axhi9odHRwOi8vY2RwMS5wY2EuZGZuLmRlL3B0Yi1jYS9wdWIv
Y3JsL2NhY3JsLmNybDA1oDOgMYYvaHR0cDovL2NkcDIucGNhLmRmbi5kZS9wdGItY2EvcHViL2Ny
bC9jYWNybC5jcmwwgZIGCCsGAQUFBwEBBIGFMIGCMD8GCCsGAQUFBzAChjNodHRwOi8vY2RwMS5w
Y2EuZGZuLmRlL3B0Yi1jYS9wdWIvY2FjZXJ0L2NhY2VydC5jcnQwPwYIKwYBBQUHMAKGM2h0dHA6
Ly9jZHAyLnBjYS5kZm4uZGUvcHRiLWNhL3B1Yi9jYWNlcnQvY2FjZXJ0LmNydDANBgkqhkiG9w0B
AQUFAAOCAQEAt2XdEe0IxYuz1v6WhXz1+EfnFC3S0Yvx4J438lbPYHFkablzHsgedeZzURxl221T
5SC4i6lC36otU7xZkVuSfyJWkMbozxgE4aA+sTJW37IdRVzQSYXFZa95DPj4B7iw+RHGBTFxbVJm
USzMG8nvykOYcpRkxxLUAZglAPfmvu/X/ixsuy4oA/0OHvpIOG1SumSb325hiP9/dMxHFwjbdyqE
nxQAkGbV5kHE77yaydGlQftM5xheKiPOBzbS2ZlzPP8L8kGPrcLK0/mdW3aW+r35aru5E+515qKm
9O0r7SiTCoNbpGCwo4o+aPDVBSe/BBxTW7St2alvIpSKZjyW6TCCBTEwggQZoAMCAQICBxecBJBC
uQswDQYJKoZIhvcNAQEFBQAwaTELMAkGA1UEBhMCREUxLjAsBgNVBAoTJVBoeXNpa2FsaXNjaC1U
ZWNobmlzY2hlIEJ1bmRlc2Fuc3RhbHQxDzANBgNVBAMTBlBUQiBDQTEZMBcGCSqGSIb3DQEJARYK
cGtpQHB0Yi5kZTAeFw0xNDA1MjExMDU5MTJaFw0xNzA1MjAxMDU5MTJaMGgxCzAJBgNVBAYTAkRF
MS4wLAYDVQQKEyVQaHlzaWthbGlzY2gtVGVjaG5pc2NoZSBCdW5kZXNhbnN0YWx0MQ0wCwYDVQQL
EwRRLjQyMRowGAYDVQQDExFEci4gRGlldGVyIFNpYm9sZDCCASIwDQYJKoZIhvcNAQEBBQADggEP
ADCCAQoCggEBAMmLec9BiMHsW3u1b5H/sKXgnyEpjNRcz33W0eYydpdgIxjQM6ifmlii9GnbJWJf
JuyUBO6T14k2erA4joSAoOl1VZS0JY9yCzuqZL5SJPWrqoUQvvTqNcl0m261/AaBWxxdFHVeuTLX
87iM73SJ6tZqTVu/7GbZVgcXp/x2wkIFQ0ZF3eVNDlPMBeEVtDmJxeYcTpzLBSLoBR6uKDAPdsy5
Oo+RLJOLMjosic7n93Q6C80yoO5/it8EZdB76xPZlIEf57ooyAlnRE0cCqLULtu/lTo1lNu8ORZa
XfDGIknle7CRD7pE9dZtGkEROIeFTdsoduP2kSQsSTgNubFvyOUCAwEAAaOCAd0wggHZMC8GA1Ud
IAQoMCYwEQYPKwYBBAGBrSGCLAEBBAMBMBEGDysGAQQBga0hgiwCAQQDATAJBgNVHRMEAjAAMAsG
A1UdDwQEAwIF4DAfBgNVHSUEGDAWBggrBgEFBQcDBAYKKwYBBAGCNxQCAjAdBgNVHQ4EFgQUbMhX
gfF1/R9HiVCcrEoXjAZBWa8wHwYDVR0jBBgwFoAUxIDQbigVaDFa7HBfeI7hMEM46jQwHwYDVR0R
BBgwFoEUZGlldGVyLnNpYm9sZEBwdGIuZGUwdwYDVR0fBHAwbjA1oDOgMYYvaHR0cDovL2NkcDEu
cGNhLmRmbi5kZS9wdGItY2EvcHViL2NybC9jYWNybC5jcmwwNaAzoDGGL2h0dHA6Ly9jZHAyLnBj
YS5kZm4uZGUvcHRiLWNhL3B1Yi9jcmwvY2FjcmwuY3JsMIGSBggrBgEFBQcBAQSBhTCBgjA/Bggr
BgEFBQcwAoYzaHR0cDovL2NkcDEucGNhLmRmbi5kZS9wdGItY2EvcHViL2NhY2VydC9jYWNlcnQu
Y3J0MD8GCCsGAQUFBzAChjNodHRwOi8vY2RwMi5wY2EuZGZuLmRlL3B0Yi1jYS9wdWIvY2FjZXJ0
L2NhY2VydC5jcnQwDQYJKoZIhvcNAQEFBQADggEBALdl3RHtCMWLs9b+loV89fhH5xQt0tGL8eCe
N/JWz2BxZGm5cx7IHnXmc1EcZdttU+UguIupQt+qLVO8WZFbkn8iVpDG6M8YBOGgPrEyVt+yHUVc
0EmFxWWveQz4+Ae4sPkRxgUxcW1SZlEszBvJ78pDmHKUZMcS1AGYJQD35r7v1/4sbLsuKAP9Dh76
SDhtUrpkm99uYYj/f3TMRxcI23cqhJ8UAJBm1eZBxO+8msnRpUH7TOcYXiojzgc20tmZczz/C/JB
j63CytP5nVt2lvq9+Wq7uRPudeaipvTtK+0okwqDW6RgsKOKPmjw1QUnvwQcU1u0rdmpbyKUimY8
lukxggLJMIICxQIBATB0MGkxCzAJBgNVBAYTAkRFMS4wLAYDVQQKEyVQaHlzaWthbGlzY2gtVGVj
aG5pc2NoZSBCdW5kZXNhbnN0YWx0MQ8wDQYDVQQDEwZQVEIgQ0ExGTAXBgkqhkiG9w0BCQEWCnBr
aUBwdGIuZGUCBxecBJBCuQswCQYFKw4DAhoFAKCCASowGAYJKoZIhvcNAQkDMQsGCSqGSIb3DQEH
ATAcBgkqhkiG9w0BCQUxDxcNMTUwNDE0MTYyMzQ0WjAjBgkqhkiG9w0BCQQxFgQU+FoLwE8E4nUI
cZOq2DWcZmAoZOswQwYJKoZIhvcNAQkPMTYwNDAHBgUrDgMCHTAOBggqhkiG9w0DAgICAIAwCgYI
KoZIhvcNAwcwDQYIKoZIhvcNAwICASgwgYUGCyqGSIb3DQEJEAILMXagdDBpMQswCQYDVQQGEwJE
RTEuMCwGA1UEChMlUGh5c2lrYWxpc2NoLVRlY2huaXNjaGUgQnVuZGVzYW5zdGFsdDEPMA0GA1UE
AxMGUFRCIENBMRkwFwYJKoZIhvcNAQkBFgpwa2lAcHRiLmRlAgcXnASQQrkLMA0GCSqGSIb3DQEB
AQUABIIBADfFjyFwM6LOfiZ01jYhMpy5Mbp/OtojhDkfLgO2aAmNeTlnmy5Mn8sZyFdUXXt1ivyp
6hbr/UcTfAhmm5ic5Ws6xrTj/zshesyfK7hAH46o8NgkyfLIKbKH6sxM3pn1KJv0Byz+3vZys7n2
liNwcPppZ5vP7TNQn6E8KS6C4IKIF2YBcncUhpPfacPzEub3aK2KXtU1j58mBJl7nSQT1jDv66VV
pou5GoBRU8sYjVW2q8fiTrGPF4Ukk45zdeVzHNbkHI47ZTdxUGhnVdz/8XZD2Dm4WnoGn/uN7iAn
jH4wrbmKmDUacLHMJMhqipr1RFPc+vDfDoPoMDYoKSegWccAAAAA

---------z3808_boundary_sign--

--===============6166945497415422967==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

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

From ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org  Tue Apr 14 21:41:05 2015
Return-Path: <ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org>
X-Original-To: ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com
Delivered-To: ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AE8141B2C06 for <ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com>; Tue, 14 Apr 2015 21:41:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.011
X-Spam-Level:
X-Spam-Status: No, score=-0.011 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 NtTnd6j6toLn for <ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com>; Tue, 14 Apr 2015 21:41:04 -0700 (PDT)
Received: from psp3.ntp.org (psp3.ntp.org [149.20.68.23]) by ietfa.amsl.com (Postfix) with ESMTP id 0F88A1B2C02 for <ntp-archives-ahFae6za@lists.ietf.org>; Tue, 14 Apr 2015 21:41:04 -0700 (PDT)
Received: from psp3.ntp.org (localhost.ntp.org [127.0.0.1]) by psp3.ntp.org (Postfix) with ESMTP id AAB9C39951 for <ntp-archives-ahFae6za@lists.ietf.org>; Tue, 14 Apr 2015 21:41:03 -0700 (PDT)
X-Original-To: ntpwg@lists.ntp.org
Delivered-To: ntpwg@lists.ntp.org
Received: from mail1.ntp.org (mail1.ntp.org [IPv6:2001:4f8:fff7:1::5]) by lists.ntp.org (Postfix) with ESMTP id 2C76A86D33C for <ntpwg@lists.ntp.org>; Wed, 15 Apr 2015 04:41:00 +0000 (UTC)
Received: from smtp-nf-106.his.com ([216.194.251.35]) by mail1.ntp.org with esmtp (Exim 4.77 (FreeBSD)) (envelope-from <brad@shub-internet.org>) id 1YiF84-000EUr-Fr for ntpwg@lists.ntp.org; Wed, 15 Apr 2015 04:41:00 +0000
Received: from cuda201.his.com (cuda201.his.com [216.194.248.226]) by smtp-nf-106.his.com (Postfix) with ESMTPS id B12BA610E9 for <ntpwg@lists.ntp.org>; Wed, 15 Apr 2015 00:39:32 -0400 (EDT)
X-ASG-Debug-ID: 1429072771-061c4124206595a0001-dac64w
Received: from smtp-nf-202.his.com (smtp-nf-202.his.com [216.194.248.252]) by cuda201.his.com with ESMTP id S0ZiGqtOUnuU9Fq2; Wed, 15 Apr 2015 00:39:31 -0400 (EDT)
X-Barracuda-Envelope-From: brad@shub-internet.org
X-Barracuda-RBL-Trusted-Forwarder: 216.194.248.252
Received: from mail-sterling.his.com (mail-sterling.his.com [216.194.248.141]) by smtp-nf-202.his.com (Postfix) with ESMTP id BCC3360129; Wed, 15 Apr 2015 00:39:29 -0400 (EDT)
Received: from localhost (localhost.localdomain [127.0.0.1]) by mail-sterling.his.com (Postfix) with ESMTP id 14AD33FB0008; Wed, 15 Apr 2015 00:39:29 -0400 (EDT)
X-Barracuda-RBL-Trusted-Forwarder: 216.194.248.141
X-Virus-Scanned: amavisd-new at mail-sterling.his.com
Received: from mail-sterling.his.com ([127.0.0.1]) by localhost (mail-sterling.his.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FVU7cPQIfx3t; Wed, 15 Apr 2015 00:39:28 -0400 (EDT)
Received: from [192.168.1.19] (75-13-92-115.lightspeed.austtx.sbcglobal.net [75.13.92.115]) by mail-sterling.his.com (Postfix) with ESMTPSA id 3D69D3FB0002; Wed, 15 Apr 2015 00:39:28 -0400 (EDT)
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2098\))
X-ASG-Orig-Subj: Mailing list server...
X-Pgp-Agent: GPGMail 2.5b6
From: Brad Knowles <brad@shub-internet.org>
Date: Tue, 14 Apr 2015 23:39:27 -0500
X-Mao-Original-Outgoing-Id: 450765567.78876-257bd74c0a20673454216871da597adc
Message-Id: <DE765F7F-105B-4574-A44F-3880E5B221EE@shub-internet.org>
To: ntpwg@lists.ntp.org
X-Mailer: Apple Mail (2.2098)
X-Barracuda-Connect: smtp-nf-202.his.com[216.194.248.252]
X-Barracuda-Start-Time: 1429072771
X-Barracuda-URL: https://spam.his.com:443/cgi-mod/mark.cgi
Received-SPF: none (his.com: brad@shub-internet.org does not designate permitted sender hosts)
X-Virus-Scanned: by bsmtpd at his.com
X-Barracuda-BRTS-Status: 1
X-Barracuda-Spam-Score: 0.01
X-Barracuda-Spam-Status: No, SCORE=0.01 using global scores of TAG_LEVEL=1000.0 QUARANTINE_LEVEL=1000.0 KILL_LEVEL=7.0 tests=BSF_SC0_MISMATCH_TO, BSF_SC2_SA022a
X-Barracuda-Spam-Report: Code version 3.2, rules version 3.2.3.17936 Rule breakdown below pts rule name              description ---- ---------------------- -------------------------------------------------- 0.00 BSF_SC0_MISMATCH_TO    Envelope rcpt doesn't match header 0.01 BSF_SC2_SA022a         Custom Rule SA022a
X-SA-Exim-Connect-IP: 216.194.251.35
X-SA-Exim-Rcpt-To: ntpwg@lists.ntp.org
X-SA-Exim-Mail-From: brad@shub-internet.org
X-SA-Exim-Version: 4.2
X-SA-Exim-Scanned: Yes (on mail1.ntp.org)
Subject: [ntpwg] Mailing list server...
X-BeenThere: ntpwg@lists.ntp.org
X-Mailman-Version: 2.1.20
Precedence: list
List-Id: IETF Working Group for Network Time Protocol <ntpwg.lists.ntp.org>
List-Unsubscribe: <http://lists.ntp.org/options/ntpwg>, <mailto:ntpwg-request@lists.ntp.org?subject=unsubscribe>
List-Archive: <http://lists.ntp.org/pipermail/ntpwg/>
List-Post: <mailto:ntpwg@lists.ntp.org>
List-Help: <mailto:ntpwg-request@lists.ntp.org?subject=help>
List-Subscribe: <http://lists.ntp.org/listinfo/ntpwg>, <mailto:ntpwg-request@lists.ntp.org?subject=subscribe>
Cc: Brad Knowles <brad@shub-internet.org>
Content-Type: multipart/mixed; boundary="===============3682749974655723363=="
Errors-To: ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org
Sender: "ntpwg" <ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org>

--===============3682749974655723363==
Content-Type: multipart/signed; boundary="Apple-Mail=_4C5DB897-3528-4572-9FD9-A705758ABFE4"; protocol="application/pgp-signature"; micalg=pgp-sha256


--Apple-Mail=_4C5DB897-3528-4572-9FD9-A705758ABFE4
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

Folks,

I want to apologize for the recent problems we=E2=80=99ve had with the =
mail servers for ntp.org and the mailing list server at lists.ntp.org.

We=E2=80=99ve had some systems go unexpectedly south on us, with =
unexpected consequences.  We=E2=80=99re in the process of putting things =
back together, and hopefully we won=E2=80=99t have any more issues with =
the mail system.

If you do notice any problems in the future, please do not hesitate to =
contact me directly, either via e-mail to the address below, or to my =
cell phone at +1-512-964-2949.  Outside of the work I have to do to earn =
a paycheck, and certain personal family issues, these systems and this =
project are my top priority.  If anything happens to them, I want to =
know about it, sooner rather than later.

Thanks!

--
Brad Knowles <brad@shub-internet.org>
LinkedIn Profile: <http://tinyurl.com/y8kpxu>


--Apple-Mail=_4C5DB897-3528-4572-9FD9-A705758ABFE4
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP using GPGMail

-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2.0.27

iQIcBAEBCAAGBQJVLet/AAoJEI8qz2oEN/nw9VsQAI2/Dbj3eSnKi26kmQw3gy4o
SI8uv/m8YhvlasyVXBdEHrUwzyoKU1kJ1ZLEpXolhLx/0LOfTSDAymzYFgwHBN7J
Df3da4rqWX7gvV2BkTTXzHcuF1Qdt+Sub06bjI7o08GptQCOTZ8eVfwiH0p7pN+u
Czqsl+xD40V2SAap8cd03USmBduPSgc4iA3CIlwYHGi81m6IoVihz/Zb0/TPylMW
k8RHau8AjYna91PceqyQQaxKXa9BB2Ft0XnAKES5l/XnSfGzR9vYO/cl+9bCGMlp
ROSSJzGKyiCQTXfrmzR/jWO2iFmQCVODd6HLVU0fyTDgLty6upC5kmUTqaISSnOG
Z6pjezSrazGd0Dn9bK28lK+am/EVnEayoSwhSqcRco3iEFgkBji/KqWfs0vrmofc
rheVBjhzLDYyhfnbtoHzE3pxZ5Ta3xfFuHDvRzQvjzBHD52bMvlfad/XW+guoaUO
2O0gKtqiCxeOI+fuMt75VXDM2V/iv0gRBt7md7oDYs7jNmeQF7dFJ6xFeYuyV319
nZMyvfAVzR/m6sXBgDfe1ep4Eq0skKOF24GwpM0CX1qZ4RGasizfFnP143eO6wP1
KWcMneViOd2NLNiEokvZcyWdjy1NxFIuWo8uoj/D/jEPT0OctknPHELAjlveA56S
FwKKVoN19lTL+HOOFxfb
=I4mu
-----END PGP SIGNATURE-----

--Apple-Mail=_4C5DB897-3528-4572-9FD9-A705758ABFE4--

--===============3682749974655723363==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

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

From ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org  Tue Apr 14 23:12:59 2015
Return-Path: <ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org>
X-Original-To: ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com
Delivered-To: ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A5C5B1B3181 for <ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com>; Tue, 14 Apr 2015 23:12:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level:
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 f-Nz-JdtfW0P for <ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com>; Tue, 14 Apr 2015 23:12:58 -0700 (PDT)
Received: from psp3.ntp.org (psp3.ntp.org [149.20.68.23]) by ietfa.amsl.com (Postfix) with ESMTP id 0BB761B317F for <ntp-archives-ahFae6za@lists.ietf.org>; Tue, 14 Apr 2015 23:12:58 -0700 (PDT)
Received: from psp3.ntp.org (localhost.ntp.org [127.0.0.1]) by psp3.ntp.org (Postfix) with ESMTP id 62CFC39918 for <ntp-archives-ahFae6za@lists.ietf.org>; Tue, 14 Apr 2015 23:12:57 -0700 (PDT)
X-Original-To: ntpwg@lists.ntp.org
Delivered-To: ntpwg@lists.ntp.org
Received: from mail1.ntp.org (mail1.ntp.org [IPv6:2001:4f8:fff7:1::5]) by lists.ntp.org (Postfix) with ESMTP id B43E386D33C for <ntpwg@lists.ntp.org>; Wed, 15 Apr 2015 06:12:53 +0000 (UTC)
Received: from rrzmta1.uni-regensburg.de ([194.94.155.51]) by mail1.ntp.org with esmtps (TLSv1:CAMELLIA256-SHA:256) (Exim 4.77 (FreeBSD)) (envelope-from <Ulrich.Windl@rz.uni-regensburg.de>) id 1YiGZ1-000ICP-UK for ntpwg@lists.ntp.org; Wed, 15 Apr 2015 06:12:53 +0000
Received: from rrzmta1.uni-regensburg.de (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id 944D04F07F for <ntpwg@lists.ntp.org>; Wed, 15 Apr 2015 08:11:26 +0200 (CEST)
Received: from gwsmtp1.uni-regensburg.de (gwsmtp1.uni-regensburg.de [132.199.5.51]) by rrzmta1.uni-regensburg.de (Postfix) with ESMTP id 586A54F06C for <ntpwg@lists.ntp.org>; Wed, 15 Apr 2015 08:11:26 +0200 (CEST)
Received: from uni-regensburg-smtp1-MTA by gwsmtp1.uni-regensburg.de with Novell_GroupWise; Wed, 15 Apr 2015 08:11:26 +0200
Message-Id: <552E1D2C020000A100019D39@gwsmtp1.uni-regensburg.de>
X-Mailer: Novell GroupWise Internet Agent 14.0.1 
Date: Wed, 15 Apr 2015 08:11:24 +0200
From: "Ulrich Windl" <Ulrich.Windl@rz.uni-regensburg.de>
To: <dieter.sibold@ptb.de>,<fweimer@redhat.com>
References: <551D1150.5080500@redhat.com> <OF1F8E2A91.0B970EC7-ONC1257E22.00357A53-C1257E22.00381DAC@ptb.de> <552663D3.7040005@redhat.com> <OF8C2E5A2A.E24A2F5A-ONC1257E23.00500707-C1257E23.0051D4E9@ptb.de> <5527E5B9.3000509@redhat.com>
In-Reply-To: <5527E5B9.3000509@redhat.com>
Mime-Version: 1.0
Content-Disposition: inline
X-SA-Exim-Connect-IP: 194.94.155.51
X-SA-Exim-Rcpt-To: ntpwg@lists.ntp.org
X-SA-Exim-Mail-From: Ulrich.Windl@rz.uni-regensburg.de
X-SA-Exim-Version: 4.2
X-SA-Exim-Scanned: Yes (on mail1.ntp.org)
Subject: [ntpwg] Antw: Re:  Antwort: Re:  Comments on various NTS drafts
X-BeenThere: ntpwg@lists.ntp.org
X-Mailman-Version: 2.1.20
Precedence: list
List-Id: IETF Working Group for Network Time Protocol <ntpwg.lists.ntp.org>
List-Unsubscribe: <http://lists.ntp.org/options/ntpwg>, <mailto:ntpwg-request@lists.ntp.org?subject=unsubscribe>
List-Archive: <http://lists.ntp.org/pipermail/ntpwg/>
List-Post: <mailto:ntpwg@lists.ntp.org>
List-Help: <mailto:ntpwg-request@lists.ntp.org?subject=help>
List-Subscribe: <http://lists.ntp.org/listinfo/ntpwg>, <mailto:ntpwg-request@lists.ntp.org?subject=subscribe>
Cc: ntpwg@lists.ntp.org
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org
Sender: "ntpwg" <ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org>

>>> Florian Weimer <fweimer@redhat.com> schrieb am 10.04.2015 um 17:01 in Nachricht
<5527E5B9.3000509@redhat.com>:
> On 04/10/2015 04:53 PM, dieter.sibold@ptb.de wrote:
> 
>>> You do not periodically refresh asymmetric keys used for the initial
>>> handshake.
>> 
>> No, not the asymmetric keys but for example a random seed value, which 
>> will result in a key refreshment.
> 
> I'm not sure if that's what is meant by key refresh.  Anyway, I think
> periodic refresh is unnecessary with the moderate data rates used for
> time synchronization.

Does it make a difference that the data transferred is mostly known?

Regards,
Ulrich


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

From ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org  Wed Apr 15 04:09:29 2015
Return-Path: <ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org>
X-Original-To: ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com
Delivered-To: ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B95431A6FFB for <ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com>; Wed, 15 Apr 2015 04:09:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level:
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 tNMFrFdHNP_1 for <ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com>; Wed, 15 Apr 2015 04:09:27 -0700 (PDT)
Received: from psp3.ntp.org (psp3.ntp.org [149.20.68.23]) by ietfa.amsl.com (Postfix) with ESMTP id 230501A6FF8 for <ntp-archives-ahFae6za@lists.ietf.org>; Wed, 15 Apr 2015 04:09:27 -0700 (PDT)
Received: from psp3.ntp.org (localhost.ntp.org [127.0.0.1]) by psp3.ntp.org (Postfix) with ESMTP id 1AD0C39917 for <ntp-archives-ahFae6za@lists.ietf.org>; Wed, 15 Apr 2015 04:09:27 -0700 (PDT)
X-Original-To: ntpwg@lists.ntp.org
Delivered-To: ntpwg@lists.ntp.org
Received: from mail1.ntp.org (mail1.ntp.org [IPv6:2001:4f8:fff7:1::5]) by lists.ntp.org (Postfix) with ESMTP id A5A9886D33C for <ntpwg@lists.ntp.org>; Wed, 15 Apr 2015 11:09:24 +0000 (UTC)
Received: from mx1.redhat.com ([209.132.183.28]) by mail1.ntp.org with esmtps (TLSv1:AES256-SHA:256) (Exim 4.77 (FreeBSD)) (envelope-from <fweimer@redhat.com>) id 1YiLBz-0009Ag-TM for ntpwg@lists.ntp.org; Wed, 15 Apr 2015 11:09:24 +0000
Received: from int-mx09.intmail.prod.int.phx2.redhat.com (int-mx09.intmail.prod.int.phx2.redhat.com [10.5.11.22]) by mx1.redhat.com (Postfix) with ESMTPS id AFD1A330488; Wed, 15 Apr 2015 11:07:59 +0000 (UTC)
Received: from oldenburg.str.redhat.com (oldenburg.str.redhat.com [10.33.200.60]) by int-mx09.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4) with ESMTP id t3FB7vmp000874 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 15 Apr 2015 07:07:58 -0400
Message-ID: <552E468D.4090504@redhat.com>
Date: Wed, 15 Apr 2015 13:07:57 +0200
From: Florian Weimer <fweimer@redhat.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.6.0
MIME-Version: 1.0
To: Ulrich Windl <Ulrich.Windl@rz.uni-regensburg.de>, dieter.sibold@ptb.de
References: <551D1150.5080500@redhat.com> <OF1F8E2A91.0B970EC7-ONC1257E22.00357A53-C1257E22.00381DAC@ptb.de> <552663D3.7040005@redhat.com> <OF8C2E5A2A.E24A2F5A-ONC1257E23.00500707-C1257E23.0051D4E9@ptb.de> <5527E5B9.3000509@redhat.com> <552E1D2C020000A100019D39@gwsmtp1.uni-regensburg.de>
In-Reply-To: <552E1D2C020000A100019D39@gwsmtp1.uni-regensburg.de>
X-Scanned-By: MIMEDefang 2.68 on 10.5.11.22
X-SA-Exim-Connect-IP: 209.132.183.28
X-SA-Exim-Rcpt-To: ntpwg@lists.ntp.org
X-SA-Exim-Mail-From: fweimer@redhat.com
X-SA-Exim-Version: 4.2
X-SA-Exim-Scanned: Yes (on mail1.ntp.org)
Subject: Re: [ntpwg] Antw: Re: Antwort: Re: Comments on various NTS drafts
X-BeenThere: ntpwg@lists.ntp.org
X-Mailman-Version: 2.1.20
Precedence: list
List-Id: IETF Working Group for Network Time Protocol <ntpwg.lists.ntp.org>
List-Unsubscribe: <http://lists.ntp.org/options/ntpwg>, <mailto:ntpwg-request@lists.ntp.org?subject=unsubscribe>
List-Archive: <http://lists.ntp.org/pipermail/ntpwg/>
List-Post: <mailto:ntpwg@lists.ntp.org>
List-Help: <mailto:ntpwg-request@lists.ntp.org?subject=help>
List-Subscribe: <http://lists.ntp.org/listinfo/ntpwg>, <mailto:ntpwg-request@lists.ntp.org?subject=subscribe>
Cc: ntpwg@lists.ntp.org
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org
Sender: "ntpwg" <ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org>

On 04/15/2015 08:11 AM, Ulrich Windl wrote:
>>>> Florian Weimer <fweimer@redhat.com> schrieb am 10.04.2015 um 17:01 in Nachricht
> <5527E5B9.3000509@redhat.com>:
>> On 04/10/2015 04:53 PM, dieter.sibold@ptb.de wrote:
>>
>>>> You do not periodically refresh asymmetric keys used for the initial
>>>> handshake.
>>>
>>> No, not the asymmetric keys but for example a random seed value, which 
>>> will result in a key refreshment.
>>
>> I'm not sure if that's what is meant by key refresh.  Anyway, I think
>> periodic refresh is unnecessary with the moderate data rates used for
>> time synchronization.
> 
> Does it make a difference that the data transferred is mostly known?

There is a general belief within the IETF that you absolutely have to
change secrets regularly because every time you use them, you invariably
leak some information.  However, if the cryptographic primitive requires
rekeying for secure operation, it is generally quite broken and should
be replaced.

A good example is RC4.  You can thwart the known attacks by discarding
the first few hundred bytes of the stream, and re-key periodically after
a few dozen megabytes.  But that's a losing proposition: Over time, as
attacks get better, you'll have to discard more and more bytes at the
start (increasing setup costs) and rekey more often (making encryption
more expensive).  The initial discard also needs algorithm parameter
changes which are not negotiated by the protocol, so a new code point
and software updates are needed each time (it's also the reason why
there is no initial discard in TLS).

All this effort is a bit pointless if you can just use AES in counter
mode, or various of the other AES modes.

So in short, rekeying as a means to keep old implementations on life
support, without code changes, does not seem to work in practice, as we
have seen with RC4.

-- 
Florian Weimer / Red Hat Product Security
_______________________________________________
ntpwg mailing list
ntpwg@lists.ntp.org
http://lists.ntp.org/listinfo/ntpwg

From ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org  Wed Apr 15 04:20:25 2015
Return-Path: <ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org>
X-Original-To: ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com
Delivered-To: ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7917D1A87BA for <ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com>; Wed, 15 Apr 2015 04:20:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level:
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 3Lt-P3BqHFO9 for <ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com>; Wed, 15 Apr 2015 04:20:24 -0700 (PDT)
Received: from psp3.ntp.org (psp3.ntp.org [149.20.68.23]) by ietfa.amsl.com (Postfix) with ESMTP id 8474F1B34B2 for <ntp-archives-ahFae6za@lists.ietf.org>; Wed, 15 Apr 2015 04:16:14 -0700 (PDT)
Received: from psp3.ntp.org (localhost.ntp.org [127.0.0.1]) by psp3.ntp.org (Postfix) with ESMTP id 779153991F for <ntp-archives-ahFae6za@lists.ietf.org>; Wed, 15 Apr 2015 04:16:14 -0700 (PDT)
X-Original-To: ntpwg@lists.ntp.org
Delivered-To: ntpwg@lists.ntp.org
Received: from mail1.ntp.org (mail1.ntp.org [IPv6:2001:4f8:fff7:1::5]) by lists.ntp.org (Postfix) with ESMTP id 2BF7486D33C for <ntpwg@lists.ntp.org>; Wed, 15 Apr 2015 11:16:12 +0000 (UTC)
Received: from mx1.redhat.com ([209.132.183.28]) by mail1.ntp.org with esmtps (TLSv1:AES256-SHA:256) (Exim 4.77 (FreeBSD)) (envelope-from <fweimer@redhat.com>) id 1YiLIa-0009Tb-JN for ntpwg@lists.ntp.org; Wed, 15 Apr 2015 11:16:12 +0000
Received: from int-mx14.intmail.prod.int.phx2.redhat.com (int-mx14.intmail.prod.int.phx2.redhat.com [10.5.11.27]) by mx1.redhat.com (8.14.4/8.14.4) with ESMTP id t3FBEm5B014852 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=FAIL); Wed, 15 Apr 2015 07:14:48 -0400
Received: from oldenburg.str.redhat.com (oldenburg.str.redhat.com [10.33.200.60]) by int-mx14.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4) with ESMTP id t3FBElKk025532 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 15 Apr 2015 07:14:48 -0400
Message-ID: <552E4826.7030101@redhat.com>
Date: Wed, 15 Apr 2015 13:14:46 +0200
From: Florian Weimer <fweimer@redhat.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.6.0
MIME-Version: 1.0
To: dieter.sibold@ptb.de
References: <551D1150.5080500@redhat.com> <OF1F8E2A91.0B970EC7-ONC1257E22.00357A53-C1257E22.00381DAC@ptb.de> <552663D3.7040005@redhat.com> <OF4709762A.D10331C0-ONC1257E27.0059C998-C1257E27.005A0FCF@ptb.de>
In-Reply-To: <OF4709762A.D10331C0-ONC1257E27.0059C998-C1257E27.005A0FCF@ptb.de>
X-Scanned-By: MIMEDefang 2.68 on 10.5.11.27
X-SA-Exim-Connect-IP: 209.132.183.28
X-SA-Exim-Rcpt-To: ntpwg@lists.ntp.org
X-SA-Exim-Mail-From: fweimer@redhat.com
X-SA-Exim-Version: 4.2
X-SA-Exim-Scanned: Yes (on mail1.ntp.org)
Subject: Re: [ntpwg] Antwort: Re:  Comments on various NTS drafts
X-BeenThere: ntpwg@lists.ntp.org
X-Mailman-Version: 2.1.20
Precedence: list
List-Id: IETF Working Group for Network Time Protocol <ntpwg.lists.ntp.org>
List-Unsubscribe: <http://lists.ntp.org/options/ntpwg>, <mailto:ntpwg-request@lists.ntp.org?subject=unsubscribe>
List-Archive: <http://lists.ntp.org/pipermail/ntpwg/>
List-Post: <mailto:ntpwg@lists.ntp.org>
List-Help: <mailto:ntpwg-request@lists.ntp.org?subject=help>
List-Subscribe: <http://lists.ntp.org/listinfo/ntpwg>, <mailto:ntpwg-request@lists.ntp.org?subject=subscribe>
Cc: ntpwg@lists.ntp.org
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org
Sender: "ntpwg" <ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org>

On 04/14/2015 06:23 PM, dieter.sibold@ptb.de wrote:

>> I think this is based on a misconception.  DTLS requires a datagram
>> transport, and it has its own fragmentation support, so it should be
>> perfectly possible to run it on top of a layer 2 transport which has
>> sufficient frame size (such as Ethernet).
> 
> Okay, I didn't know this. Do you know if there are implementations 
> available to use DTLS over Ethernet?

According to Matt Caswell, one of the OpenSSL core developers, it should
be possible with OpenSSL and some custom BIO code:

  <http://marc.info/?l=openssl-users&m=142904263719101>

Figuring out the details will still require quite a bit of work, but it
will still be less effort than to reimplement large pieces of DTLS for
the security features you need.

-- 
Florian Weimer / Red Hat Product Security
_______________________________________________
ntpwg mailing list
ntpwg@lists.ntp.org
http://lists.ntp.org/listinfo/ntpwg

From ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org  Wed Apr 15 17:08:02 2015
Return-Path: <ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org>
X-Original-To: ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com
Delivered-To: ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AC5981ACE1A for <ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com>; Wed, 15 Apr 2015 17:08:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.481
X-Spam-Level:
X-Spam-Status: No, score=-1.481 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, MIME_HTML_MOSTLY=0.428, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 q90K1i1R2IiN for <ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com>; Wed, 15 Apr 2015 17:07:59 -0700 (PDT)
Received: from psp3.ntp.org (psp3.ntp.org [149.20.68.23]) by ietfa.amsl.com (Postfix) with ESMTP id BC1761ACE0D for <ntp-archives-ahFae6za@lists.ietf.org>; Wed, 15 Apr 2015 17:07:59 -0700 (PDT)
Received: from psp3.ntp.org (localhost.ntp.org [127.0.0.1]) by psp3.ntp.org (Postfix) with ESMTP id 9452D39926 for <ntp-archives-ahFae6za@lists.ietf.org>; Wed, 15 Apr 2015 17:07:59 -0700 (PDT)
X-Original-To: ntpwg@lists.ntp.org
Delivered-To: ntpwg@lists.ntp.org
Received: from mail1.ntp.org (mail1.ntp.org [IPv6:2001:4f8:fff7:1::5]) by lists.ntp.org (Postfix) with ESMTP id F174A86D33C for <ntpwg@lists.ntp.org>; Wed, 15 Apr 2015 05:28:45 +0000 (UTC)
Received: from szxga02-in.huawei.com ([119.145.14.65]) by mail1.ntp.org with esmtps (TLSv1:RC4-SHA:128) (Exim 4.77 (FreeBSD)) (envelope-from <vikram.choudhary@huawei.com>) id 1YiFsI-000GTI-V4 for ntpwg@lists.ntp.org; Wed, 15 Apr 2015 05:28:45 +0000
Received: from 172.24.2.119 (EHLO SZXEMI402-HUB.china.huawei.com) ([172.24.2.119]) by szxrg02-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id CJU38664; Wed, 15 Apr 2015 13:27:11 +0800 (CST)
Received: from BLREML407-HUB.china.huawei.com (10.20.4.45) by SZXEMI402-HUB.china.huawei.com (10.82.75.34) with Microsoft SMTP Server (TLS) id 14.3.158.1; Wed, 15 Apr 2015 13:27:10 +0800
Received: from BLREML508-MBX.china.huawei.com ([10.20.5.36]) by BLREML407-HUB.china.huawei.com ([10.20.4.45]) with mapi id 14.03.0158.001; Wed, 15 Apr 2015 10:56:59 +0530
From: Vikram Choudhary <vikram.choudhary@huawei.com>
To: "ntpwg@lists.ntp.org" <ntpwg@lists.ntp.org>
Thread-Topic: Idea about modifying existing NTP extension header to remove size restriction due to MAC.
Thread-Index: AdBzfPp+9OiFL4vwThyjiO1EMnznTwDv7l3g
Date: Wed, 15 Apr 2015 05:26:59 +0000
Message-ID: <99F160A7D70E22438C8ECB52BDB54B70C67757@blreml508-mbx>
Accept-Language: zh-CN, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.18.148.88]
MIME-Version: 1.0
X-CFilter-Loop: Reflected
X-SA-Exim-Connect-IP: 119.145.14.65
X-SA-Exim-Rcpt-To: ntpwg@lists.ntp.org
X-SA-Exim-Mail-From: vikram.choudhary@huawei.com
X-SA-Exim-Version: 4.2
X-SA-Exim-Scanned: Yes (on mail1.ntp.org)
X-Mailman-Approved-At: Thu, 16 Apr 2015 00:07:55 +0000
Subject: [ntpwg] Idea about modifying existing NTP extension header to remove size restriction due to MAC.
X-BeenThere: ntpwg@lists.ntp.org
X-Mailman-Version: 2.1.20
Precedence: list
List-Id: IETF Working Group for Network Time Protocol <ntpwg.lists.ntp.org>
List-Unsubscribe: <http://lists.ntp.org/options/ntpwg>, <mailto:ntpwg-request@lists.ntp.org?subject=unsubscribe>
List-Archive: <http://lists.ntp.org/pipermail/ntpwg/>
List-Post: <mailto:ntpwg@lists.ntp.org>
List-Help: <mailto:ntpwg-request@lists.ntp.org?subject=help>
List-Subscribe: <http://lists.ntp.org/listinfo/ntpwg>, <mailto:ntpwg-request@lists.ntp.org?subject=subscribe>
Cc: "Anil Kumar S N \(VRP Network BL\)" <anil.sn@huawei.com>, Kalyankumar Asangi <kalyana@huawei.com>
Content-Type: multipart/mixed; boundary="===============8675945123095188123=="
Errors-To: ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org
Sender: "ntpwg" <ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org>

--===============8675945123095188123==
Content-Language: en-US
Content-Type: multipart/alternative;
	boundary="_000_99F160A7D70E22438C8ECB52BDB54B70C67757blreml508mbx_"

--_000_99F160A7D70E22438C8ECB52BDB54B70C67757blreml508mbx_
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable


Hi All,


I was thinking of redefining the legacy NTP extension header for reducing u=
nwanted padding introduced due to MAC.



How this helps:

=E8 Removes size restriction for the NTP extension field imposed due to MAC=
. (RFC 5905)

=E8 Reduces packet size avoiding unwanted padding.

=E8 Saves bandwidth.



Idea:

Reserve MSB of field type to indicate whether the following TLV is an exten=
sion or not.

       0                   1                   2                   3

      0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1

      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

      |M|        Field Type         |            Length             |

      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

      .                                                             .

      .                            Value                            .

      .                                                             .

      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

      |                       Padding (as needed)                   |

      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

                     Figure: New extension Field Format



        Bit-M : 1 - More extensions to be followed, 0 - No more extensions.



Ensuring backward compatibility:

   Following points/rules will take care of backward compatibility.



a.  NTP packet with no extension/s and MAC.

      This is simple as the packet size will be just equal to NTP header si=
ze. No special processing required.



b.  NTP packet with MAC.

      NTP packet size as defined in RFC 5905 will be considered for MAC pro=
cessing.



   c.  NTP packet with autokey extension/s and with/without MAC.

       Autokey extension's are the only defined NTP extension's so current =
size limitation and processing will remain as defined in RFC 5905 and 5906.

       Note: Autokey extension will be identified as per the defined IANA v=
alues.



   d.  NTP packet with new extension/s with/without autokey extension/s and=
 with/without MAC.

=D8   Autokey extension/s MUST be continuous and SHOULD start after NTP hea=
der (existing implementation, no change).

=D8   First extension following NTP header MUST be at least 7 words.

=D8   First extension following autokey extension MUST be at least 7 words.



   e.  IANA values for the newer extensions should not collide with Autokey=
 IANA values after considering the MSB bit value.



Request you to kindly let me know about your views.



Thanks

Vikram


--_000_99F160A7D70E22438C8ECB52BDB54B70C67757blreml508mbx_
Content-Type: text/html; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Diso-8859-=
1">
<meta name=3D"Generator" content=3D"Microsoft Word 12 (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:SimSun;
	panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:SimSun;
	panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
	{font-family:Consolas;
	panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	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;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
	{mso-style-priority:99;
	mso-style-link:"Plain Text Char";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:10.5pt;
	font-family:Consolas;}
pre
	{mso-style-priority:99;
	mso-style-link:"HTML Preformatted Char";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:10.0pt;
	font-family:"Courier New";}
span.HTMLPreformattedChar
	{mso-style-name:"HTML Preformatted Char";
	mso-style-priority:99;
	mso-style-link:"HTML Preformatted";
	font-family:"Courier New";}
span.PlainTextChar
	{mso-style-name:"Plain Text Char";
	mso-style-priority:99;
	mso-style-link:"Plain Text";
	font-family:Consolas;}
span.EmailStyle21
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.EmailStyle22
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:72.0pt 90.0pt 72.0pt 90.0pt;}
div.WordSection1
	{page:WordSection1;}
/* List Definitions */
@list l0
	{mso-list-id:1632858514;
	mso-list-type:hybrid;
	mso-list-template-ids:-1837362186 -1722496782 67698691 67698693 67698689 6=
7698691 67698693 67698689 67698691 67698693;}
@list l0:level1
	{mso-level-start-at:4;
	mso-level-number-format:bullet;
	mso-level-text:\F0E8;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	margin-left:54.0pt;
	text-indent:-18.0pt;
	font-family:Wingdings;
	mso-fareast-font-family:SimSun;
	mso-bidi-font-family:"Times New Roman";}
@list l0:level2
	{mso-level-tab-stop:72.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l0:level3
	{mso-level-tab-stop:108.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l0:level4
	{mso-level-tab-stop:144.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l0:level5
	{mso-level-tab-stop:180.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l0:level6
	{mso-level-tab-stop:216.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l0:level7
	{mso-level-tab-stop:252.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l0:level8
	{mso-level-tab-stop:288.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l0:level9
	{mso-level-tab-stop:324.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l1
	{mso-list-id:1912150723;
	mso-list-type:hybrid;
	mso-list-template-ids:-1446454398 67698699 67698691 67698693 67698689 6769=
8691 67698693 67698689 67698691 67698693;}
@list l1:level1
	{mso-level-number-format:bullet;
	mso-level-text:\F0D8;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	margin-left:63.8pt;
	text-indent:-18.0pt;
	font-family:Wingdings;}
@list l1:level2
	{mso-level-tab-stop:72.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l1:level3
	{mso-level-tab-stop:108.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l1:level4
	{mso-level-tab-stop:144.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l1:level5
	{mso-level-tab-stop:180.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l1:level6
	{mso-level-tab-stop:216.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l1:level7
	{mso-level-tab-stop:252.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l1:level8
	{mso-level-tab-stop:288.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l1:level9
	{mso-level-tab-stop:324.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l2
	{mso-list-id:1924099067;
	mso-list-type:hybrid;
	mso-list-template-ids:1106695640 67698713 67698713 67698715 67698703 67698=
713 67698715 67698703 67698713 67698715;}
@list l2:level1
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l2:level2
	{mso-level-tab-stop:72.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l2:level3
	{mso-level-tab-stop:108.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l2:level4
	{mso-level-tab-stop:144.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l2:level5
	{mso-level-tab-stop:180.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l2:level6
	{mso-level-tab-stop:216.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l2:level7
	{mso-level-tab-stop:252.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l2:level8
	{mso-level-tab-stop:288.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l2:level9
	{mso-level-tab-stop:324.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
ol
	{margin-bottom:0cm;}
ul
	{margin-bottom:0cm;}
--></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=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal">Hi All,<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">I was thinking of redefining the legacy NTP exten=
sion header for reducing unwanted padding introduced due to MAC.<o:p></o:p>=
</p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText"><b><u>How this helps:<o:p></o:p></u></b></p>
<p class=3D"MsoPlainText" style=3D"margin-left:54.0pt;text-indent:-18.0pt;m=
so-list:l0 level1 lfo2">
<![if !supportLists]><span style=3D"font-family:Wingdings"><span style=3D"m=
so-list:Ignore">=E8<span style=3D"font:7.0pt &quot;Times New Roman&quot;">
</span></span></span><![endif]>Removes size restriction for the NTP extensi=
on field imposed due to MAC. (RFC 5905)<o:p></o:p></p>
<p class=3D"MsoPlainText" style=3D"margin-left:54.0pt;text-indent:-18.0pt;m=
so-list:l0 level1 lfo2">
<![if !supportLists]><span style=3D"font-family:Wingdings"><span style=3D"m=
so-list:Ignore">=E8<span style=3D"font:7.0pt &quot;Times New Roman&quot;">
</span></span></span><![endif]>Reduces packet size avoiding unwanted paddin=
g.<o:p></o:p></p>
<p class=3D"MsoPlainText" style=3D"margin-left:54.0pt;text-indent:-18.0pt;m=
so-list:l0 level1 lfo2">
<![if !supportLists]><span style=3D"font-family:Wingdings"><span style=3D"m=
so-list:Ignore">=E8<span style=3D"font:7.0pt &quot;Times New Roman&quot;">
</span></span></span><![endif]>Saves bandwidth.<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText"><b><u>Idea:</u></b><o:p></o:p></p>
<p class=3D"MsoPlainText">Reserve MSB of field type to indicate whether the=
 following TLV is an extension or not.<o:p></o:p></p>
<pre style=3D"line-height:14.4pt"><span style=3D"color:black">&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp; 0&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 1&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp; 2&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 3<o:p></o:p></span></=
pre>
<pre style=3D"line-height:14.4pt"><span style=3D"color:black">&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp; 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8=
 9 0 1<o:p></o:p></span></pre>
<pre style=3D"line-height:14.4pt"><span style=3D"color:black">&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp; &#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#4=
3;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-=
&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;<o:p></o:p></spa=
n></pre>
<pre style=3D"line-height:14.4pt"><span style=3D"color:black">&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp; |M|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Field Type&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Length&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |<o:p></o:p></span></pre>
<pre style=3D"line-height:14.4pt"><span style=3D"color:black">&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp; &#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#4=
3;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-=
&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;<o:p></o:p></spa=
n></pre>
<pre style=3D"line-height:14.4pt"><span style=3D"color:black">&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp; .&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;.<o:p></o:p></span></pre>
<pre style=3D"line-height:14.4pt"><span style=3D"color:black">&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp; .&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Value&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;.<o:p></o:p></span><=
/pre>
<pre style=3D"line-height:14.4pt"><span style=3D"color:black">&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp; .&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;.<o:p></o:p></span></pre>
<pre style=3D"line-height:14.4pt"><span style=3D"color:black">&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp; &#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#4=
3;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-=
&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;<o:p></o:p></spa=
n></pre>
<pre style=3D"line-height:14.4pt"><span style=3D"color:black">&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp; |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
; Padding (as needed)&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;|<o:p></o:p></s=
pan></pre>
<pre style=3D"line-height:14.4pt"><span style=3D"color:black">&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp; &#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#4=
3;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-=
&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;<o:p></o:p></spa=
n></pre>
<pre style=3D"line-height:14.4pt"><span style=3D"color:black">&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Figure: New extension Field Format<o:p></o=
:p></span></pre>
<pre style=3D"line-height:14.4pt"><span style=3D"color:black"><o:p>&nbsp;</=
o:p></span></pre>
<pre style=3D"line-height:14.4pt"><span style=3D"color:black">&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Bit-M : 1 &#8211; More extensions to be follo=
wed, 0 &#8211; No more extensions. <o:p></o:p></span></pre>
<pre style=3D"line-height:14.4pt"><o:p>&nbsp;</o:p></pre>
<pre style=3D"line-height:14.4pt"><b><u><span style=3D"font-size:10.5pt;fon=
t-family:Consolas">Ensuring backward compatibility:<o:p></o:p></span></u></=
b></pre>
<pre style=3D"line-height:14.4pt"><span style=3D"font-size:10.5pt;font-fami=
ly:Consolas">&nbsp;&nbsp; Following points/rules will take care of backward=
 compatibility.<o:p></o:p></span></pre>
<pre style=3D"line-height:14.4pt"><span style=3D"font-size:10.5pt;font-fami=
ly:Consolas"><o:p>&nbsp;</o:p></span></pre>
<pre style=3D"margin-left:36.0pt;text-indent:-18.0pt;line-height:14.4pt;mso=
-list:l2 level1 lfo4"><![if !supportLists]><span style=3D"font-size:10.5pt;=
font-family:Consolas"><span style=3D"mso-list:Ignore">a.<span style=3D"font=
:7.0pt &quot;Times New Roman&quot;">&nbsp; </span></span></span><![endif]><=
span style=3D"font-size:10.5pt;font-family:Consolas">NTP packet with no ext=
ension/s and MAC.<o:p></o:p></span></pre>
<pre style=3D"line-height:14.4pt"><span style=3D"font-size:10.5pt;font-fami=
ly:Consolas">&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;This is simple as the packet si=
ze will be just equal to NTP header size. No special processing required.<o=
:p></o:p></span></pre>
<pre style=3D"line-height:14.4pt"><span style=3D"font-size:10.5pt;font-fami=
ly:Consolas"><o:p>&nbsp;</o:p></span></pre>
<pre style=3D"margin-left:36.0pt;text-indent:-18.0pt;line-height:14.4pt;mso=
-list:l2 level1 lfo4"><![if !supportLists]><span style=3D"font-size:10.5pt;=
font-family:Consolas"><span style=3D"mso-list:Ignore">b.<span style=3D"font=
:7.0pt &quot;Times New Roman&quot;">&nbsp; </span></span></span><![endif]><=
span style=3D"font-size:10.5pt;font-family:Consolas">NTP packet with MAC.<o=
:p></o:p></span></pre>
<pre style=3D"line-height:14.4pt"><span style=3D"font-size:10.5pt;font-fami=
ly:Consolas">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; NTP packet size as defined in R=
FC 5905 will be considered for MAC processing.<o:p></o:p></span></pre>
<pre style=3D"line-height:14.4pt"><span style=3D"font-size:10.5pt;font-fami=
ly:Consolas">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <o:p></o:p></span></pre>
<pre style=3D"line-height:14.4pt"><span style=3D"font-size:10.5pt;font-fami=
ly:Consolas">&nbsp;&nbsp;&nbsp;c.&nbsp; NTP packet with autokey extension/s=
 and with/without MAC.<o:p></o:p></span></pre>
<pre style=3D"line-height:14.4pt"><span style=3D"font-size:10.5pt;font-fami=
ly:Consolas">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Autokey extension's are t=
he only defined NTP extension's so current size limitation and processing w=
ill remain as defined in RFC 5905 and 5906.<o:p></o:p></span></pre>
<pre style=3D"line-height:14.4pt"><span style=3D"font-size:10.5pt;font-fami=
ly:Consolas">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Note: Autokey extension w=
ill be identified as per the defined IANA values.<o:p></o:p></span></pre>
<pre style=3D"line-height:14.4pt"><span style=3D"font-size:10.5pt;font-fami=
ly:Consolas">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <o:p></o:p></span></pre>
<pre style=3D"line-height:14.4pt"><span style=3D"font-size:10.5pt;font-fami=
ly:Consolas">&nbsp;&nbsp;&nbsp;d.&nbsp; NTP packet with new extension/s wit=
h/without autokey extension/s and with/without MAC.<o:p></o:p></span></pre>
<pre style=3D"margin-left:63.8pt;text-indent:-18.0pt;line-height:14.4pt;mso=
-list:l1 level1 lfo6"><![if !supportLists]><span style=3D"font-size:10.5pt;=
font-family:Wingdings"><span style=3D"mso-list:Ignore">=D8<span style=3D"fo=
nt:7.0pt &quot;Times New Roman&quot;">&nbsp; </span></span></span><![endif]=
><span style=3D"font-size:10.5pt;font-family:Consolas">&nbsp;Autokey extens=
ion/s MUST be continuous and SHOULD start after NTP header (existing implem=
entation, no change).<o:p></o:p></span></pre>
<pre style=3D"margin-left:63.8pt;text-indent:-18.0pt;line-height:14.4pt;mso=
-list:l1 level1 lfo6"><![if !supportLists]><span style=3D"font-size:10.5pt;=
font-family:Wingdings"><span style=3D"mso-list:Ignore">=D8<span style=3D"fo=
nt:7.0pt &quot;Times New Roman&quot;">&nbsp; </span></span></span><![endif]=
><span style=3D"font-size:10.5pt;font-family:Consolas">&nbsp;First extensio=
n following NTP header MUST be at least 7 words.<o:p></o:p></span></pre>
<pre style=3D"margin-left:63.8pt;text-indent:-18.0pt;line-height:14.4pt;mso=
-list:l1 level1 lfo6"><![if !supportLists]><span style=3D"font-size:10.5pt;=
font-family:Wingdings"><span style=3D"mso-list:Ignore">=D8<span style=3D"fo=
nt:7.0pt &quot;Times New Roman&quot;">&nbsp; </span></span></span><![endif]=
><span style=3D"font-size:10.5pt;font-family:Consolas">&nbsp;First extensio=
n following autokey extension MUST be at least 7 words.<o:p></o:p></span></=
pre>
<pre style=3D"line-height:14.4pt"><span style=3D"font-size:10.5pt;font-fami=
ly:Consolas"><o:p>&nbsp;</o:p></span></pre>
<pre style=3D"line-height:14.4pt"><span style=3D"font-size:10.5pt;font-fami=
ly:Consolas"> &nbsp;&nbsp;e.&nbsp; IANA values for the newer extensions sho=
uld not collide with Autokey IANA values after considering the MSB bit valu=
e.<o:p></o:p></span></pre>
<pre style=3D"line-height:14.4pt"><span style=3D"font-size:10.5pt;font-fami=
ly:Consolas"><o:p>&nbsp;</o:p></span></pre>
<pre style=3D"line-height:14.4pt"><span style=3D"font-size:10.5pt;font-fami=
ly:Consolas">Request you to kindly let me know about your views.<o:p></o:p>=
</span></pre>
<pre style=3D"line-height:14.4pt"><span style=3D"font-size:10.5pt;font-fami=
ly:Consolas"><o:p>&nbsp;</o:p></span></pre>
<pre style=3D"line-height:14.4pt"><span style=3D"font-size:10.5pt;font-fami=
ly:Consolas">Thanks<o:p></o:p></span></pre>
<pre style=3D"line-height:14.4pt"><span style=3D"font-size:10.5pt;font-fami=
ly:Consolas">Vikram<o:p></o:p></span></pre>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
</body>
</html>

--_000_99F160A7D70E22438C8ECB52BDB54B70C67757blreml508mbx_--

--===============8675945123095188123==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

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

From ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org  Fri Apr 17 01:26:28 2015
Return-Path: <ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org>
X-Original-To: ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com
Delivered-To: ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C33931B2AE5 for <ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com>; Fri, 17 Apr 2015 01:26:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.791
X-Spam-Level:
X-Spam-Status: No, score=0.791 tagged_above=-999 required=5 tests=[BAYES_50=0.8, HTML_MESSAGE=0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 k59s2VdNMzQa for <ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com>; Fri, 17 Apr 2015 01:26:26 -0700 (PDT)
Received: from psp3.ntp.org (psp3.ntp.org [149.20.68.23]) by ietfa.amsl.com (Postfix) with ESMTP id 559BA1B2AD7 for <ntp-archives-ahFae6za@lists.ietf.org>; Fri, 17 Apr 2015 01:26:20 -0700 (PDT)
Received: from psp3.ntp.org (localhost.ntp.org [127.0.0.1]) by psp3.ntp.org (Postfix) with ESMTP id 21D6F3992C for <ntp-archives-ahFae6za@lists.ietf.org>; Fri, 17 Apr 2015 01:26:20 -0700 (PDT)
X-Original-To: ntpwg@lists.ntp.org
Delivered-To: ntpwg@lists.ntp.org
Received: from mail1.ntp.org (mail1.ntp.org [IPv6:2001:4f8:fff7:1::5]) by lists.ntp.org (Postfix) with ESMTP id 7788286D48C; Fri, 17 Apr 2015 08:26:16 +0000 (UTC)
Received: from mx1.bs.ptb.de ([192.53.103.106]) by mail1.ntp.org with esmtps (TLSv1:AES256-SHA:256) (Exim 4.77 (FreeBSD)) (envelope-from <kristof.teichel@ptb.de>) id 1Yj1bD-000Pit-MJ; Fri, 17 Apr 2015 08:26:16 +0000
Received: from mx1.bs.ptb.de (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id AD778D6AA64; Fri, 17 Apr 2015 10:23:34 +0200 (CEST)
Received: from rose.bs.ptb.de (rose.bs.ptb.de [141.25.85.201]) by mx1.bs.ptb.de (Postfix) with ESMTP id 93948D4D170; Fri, 17 Apr 2015 10:23:34 +0200 (CEST)
In-Reply-To: <552E468D.4090504@redhat.com>
References: <551D1150.5080500@redhat.com>	<OF1F8E2A91.0B970EC7-ONC1257E22.00357A53-C1257E22.00381DAC@ptb.de> <552663D3.7040005@redhat.com>	<OF8C2E5A2A.E24A2F5A-ONC1257E23.00500707-C1257E23.0051D4E9@ptb.de> <5527E5B9.3000509@redhat.com>	<552E1D2C020000A100019D39@gwsmtp1.uni-regensburg.de> <552E468D.4090504@redhat.com>
To: Florian Weimer <fweimer@redhat.com>
MIME-Version: 1.0
X-KeepSent: 31AAE487:B17B4BD0-C1257E2A:002B1230; type=4; name=$KeepSent
X-Mailer: IBM Notes Release 9.0.1FP3 January 13, 2015
Message-ID: <OF31AAE487.B17B4BD0-ONC1257E2A.002B1230-C1257E2A.002E1A51@ptb.de>
From: kristof.teichel@ptb.de
Date: Fri, 17 Apr 2015 10:23:33 +0200
X-MIMETrack: Serialize by Router on ROSE/PTB(Release 9.0.1FP3HF79 | February 9, 2015) at 04/17/2015 10:23:34, Serialize complete at 04/17/2015 10:23:34
X-SA-Exim-Connect-IP: 192.53.103.106
X-SA-Exim-Rcpt-To: ntpwg-bounces+kristof.teichel=ptb.de@lists.ntp.org, ntpwg@lists.ntp.org
X-SA-Exim-Mail-From: kristof.teichel@ptb.de
X-SA-Exim-Version: 4.2
X-SA-Exim-Scanned: Yes (on mail1.ntp.org)
Subject: Re: [ntpwg] Antw: Re: Antwort: Re: Comments on various NTS drafts
X-BeenThere: ntpwg@lists.ntp.org
X-Mailman-Version: 2.1.20
Precedence: list
List-Id: IETF Working Group for Network Time Protocol <ntpwg.lists.ntp.org>
List-Unsubscribe: <http://lists.ntp.org/options/ntpwg>, <mailto:ntpwg-request@lists.ntp.org?subject=unsubscribe>
List-Archive: <http://lists.ntp.org/pipermail/ntpwg/>
List-Post: <mailto:ntpwg@lists.ntp.org>
List-Help: <mailto:ntpwg-request@lists.ntp.org?subject=help>
List-Subscribe: <http://lists.ntp.org/listinfo/ntpwg>, <mailto:ntpwg-request@lists.ntp.org?subject=subscribe>
Cc: ntpwg@lists.ntp.org, ntpwg <ntpwg-bounces+kristof.teichel=ptb.de@lists.ntp.org>
Content-Type: multipart/mixed; boundary="===============6212103135738093370=="
Errors-To: ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org
Sender: "ntpwg" <ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org>

Dies ist eine mehrteilige Nachricht im MIME-Format.
--===============6212103135738093370==
Content-Type: multipart/alternative; boundary="=_alternative 002E1A50C1257E2A_="

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

"ntpwg" <ntpwg-bounces+kristof.teichel=ptb.de@lists.ntp.org> schrieb am 
15.04.2015 13:07:57:

> Von: Florian Weimer <fweimer@redhat.com>
> An: Ulrich Windl <Ulrich.Windl@rz.uni-regensburg.de>, 
dieter.sibold@ptb.de
> Kopie: ntpwg@lists.ntp.org
> Datum: 15.04.2015 13:09
> Betreff: Re: [ntpwg] Antw: Re: Antwort: Re: Comments on various NTS 
drafts
> Gesendet von: "ntpwg" 
<ntpwg-bounces+kristof.teichel=ptb.de@lists.ntp.org>
> 
> On 04/15/2015 08:11 AM, Ulrich Windl wrote:
> >>>> Florian Weimer <fweimer@redhat.com> schrieb am 10.04.2015 um 
> 17:01 in Nachricht
> > <5527E5B9.3000509@redhat.com>:
> >> On 04/10/2015 04:53 PM, dieter.sibold@ptb.de wrote:
> >>
> >>>> You do not periodically refresh asymmetric keys used for the 
initial
> >>>> handshake.
> >>>
> >>> No, not the asymmetric keys but for example a random seed value, 
which 
> >>> will result in a key refreshment.

Yes, the key that we explicitly wish to refresh periodically is the server 
seed, which is used for the generation of MAC keys (which therefore 
implicitly need to be refreshed as well after every seed refresh).

> >>
> >> I'm not sure if that's what is meant by key refresh.  Anyway, I think
> >> periodic refresh is unnecessary with the moderate data rates used for
> >> time synchronization.
> > 
> > Does it make a difference that the data transferred is mostly known?
> 
> There is a general belief within the IETF that you absolutely have to
> change secrets regularly because every time you use them, you invariably
> leak some information.  However, if the cryptographic primitive requires
> rekeying for secure operation, it is generally quite broken and should
> be replaced.

I am not sure how to understand your point. Are you saying it is 
unnecessary, or are you saying it would be detrimental to re-key and must 
be avoided? I have made myself familiar with the arguments for why 
re-keying should be unnecessary from a cryptographic point of view, but I 
still fail to see how it would be hurtful to include a possibility for 
re-keying (as opposed to being unable to re-key even after years of usage 
of a key).

> 
> A good example is RC4.  You can thwart the known attacks by discarding
> the first few hundred bytes of the stream, and re-key periodically after
> a few dozen megabytes. 

Side note: our thoughts were more along the lines of re-keying after a 
given period of time.

> But that's a losing proposition: Over time, as
> attacks get better, you'll have to discard more and more bytes at the
> start (increasing setup costs) and rekey more often (making encryption
> more expensive).  The initial discard also needs algorithm parameter
> changes which are not negotiated by the protocol, so a new code point
> and software updates are needed each time (it's also the reason why
> there is no initial discard in TLS).
> 
> All this effort is a bit pointless if you can just use AES in counter
> mode, or various of the other AES modes.
> 
> So in short, rekeying as a means to keep old implementations on life
> support, without code changes, does not seem to work in practice, as we
> have seen with RC4.
> 
> -- 
> Florian Weimer / Red Hat Product Security
> _______________________________________________
> ntpwg mailing list
> ntpwg@lists.ntp.org
> http://lists.ntp.org/listinfo/ntpwg

Best regards,
Kristof Teichel

--=_alternative 002E1A50C1257E2A_=
Content-Type: text/html; charset="US-ASCII"

<tt><font size=2>&quot;ntpwg&quot; &lt;ntpwg-bounces+kristof.teichel=ptb.de@lists.ntp.org&gt;
schrieb am 15.04.2015 13:07:57:<br>
<br>
&gt; Von: Florian Weimer &lt;fweimer@redhat.com&gt;</font></tt>
<br><tt><font size=2>&gt; An: Ulrich Windl &lt;Ulrich.Windl@rz.uni-regensburg.de&gt;,
dieter.sibold@ptb.de</font></tt>
<br><tt><font size=2>&gt; Kopie: ntpwg@lists.ntp.org</font></tt>
<br><tt><font size=2>&gt; Datum: 15.04.2015 13:09</font></tt>
<br><tt><font size=2>&gt; Betreff: Re: [ntpwg] Antw: Re: Antwort: Re: Comments
on various NTS drafts</font></tt>
<br><tt><font size=2>&gt; Gesendet von: &quot;ntpwg&quot; &lt;ntpwg-bounces+kristof.teichel=ptb.de@lists.ntp.org&gt;</font></tt>
<br><tt><font size=2>&gt; <br>
&gt; On 04/15/2015 08:11 AM, Ulrich Windl wrote:<br>
&gt; &gt;&gt;&gt;&gt; Florian Weimer &lt;fweimer@redhat.com&gt; schrieb
am 10.04.2015 um <br>
&gt; 17:01 in Nachricht<br>
&gt; &gt; &lt;5527E5B9.3000509@redhat.com&gt;:<br>
&gt; &gt;&gt; On 04/10/2015 04:53 PM, dieter.sibold@ptb.de wrote:<br>
&gt; &gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt; You do not periodically refresh asymmetric keys used
for the initial<br>
&gt; &gt;&gt;&gt;&gt; handshake.<br>
&gt; &gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt; No, not the asymmetric keys but for example a random
seed value, which <br>
&gt; &gt;&gt;&gt; will result in a key refreshment.</font></tt>
<br>
<br><tt><font size=2>Yes, the key that we explicitly wish to refresh periodically
is the server seed, which is used for the generation of MAC keys (which
therefore implicitly need to be refreshed as well after every seed refresh).</font></tt>
<br><tt><font size=2><br>
&gt; &gt;&gt;<br>
&gt; &gt;&gt; I'm not sure if that's what is meant by key refresh. &nbsp;Anyway,
I think<br>
&gt; &gt;&gt; periodic refresh is unnecessary with the moderate data rates
used for<br>
&gt; &gt;&gt; time synchronization.<br>
&gt; &gt; <br>
&gt; &gt; Does it make a difference that the data transferred is mostly
known?<br>
&gt; <br>
&gt; There is a general belief within the IETF that you absolutely have
to<br>
&gt; change secrets regularly because every time you use them, you invariably<br>
&gt; leak some information. &nbsp;However, if the cryptographic primitive
requires<br>
&gt; rekeying for secure operation, it is generally quite broken and should<br>
&gt; be replaced.</font></tt>
<br>
<br><tt><font size=2>I am not sure how to understand your point. Are you
saying it is unnecessary, or are you saying it would be detrimental to
re-key and must be avoided? I have made myself familiar with the arguments
for why re-keying should be unnecessary from a cryptographic point of view,
but I still fail to see how it would be hurtful to include a possibility
for re-keying (as opposed to being unable to re-key even after years of
usage of a key).</font></tt>
<br><tt><font size=2><br>
&gt; <br>
&gt; A good example is RC4. &nbsp;You can thwart the known attacks by discarding<br>
&gt; the first few hundred bytes of the stream, and re-key periodically
after<br>
&gt; a few dozen megabytes. &nbsp;</font></tt>
<br>
<br><tt><font size=2>Side note: our thoughts were more along the lines
of re-keying after a given period of time.</font></tt>
<br>
<br><tt><font size=2>&gt; But that's a losing proposition: Over time, as<br>
&gt; attacks get better, you'll have to discard more and more bytes at
the<br>
&gt; start (increasing setup costs) and rekey more often (making encryption<br>
&gt; more expensive). &nbsp;The initial discard also needs algorithm parameter<br>
&gt; changes which are not negotiated by the protocol, so a new code point<br>
&gt; and software updates are needed each time (it's also the reason why<br>
&gt; there is no initial discard in TLS).<br>
&gt; <br>
&gt; All this effort is a bit pointless if you can just use AES in counter<br>
&gt; mode, or various of the other AES modes.<br>
&gt; <br>
&gt; So in short, rekeying as a means to keep old implementations on life<br>
&gt; support, without code changes, does not seem to work in practice,
as we<br>
&gt; have seen with RC4.<br>
&gt; <br>
&gt; -- <br>
&gt; Florian Weimer / Red Hat Product Security<br>
&gt; _______________________________________________<br>
&gt; ntpwg mailing list<br>
&gt; ntpwg@lists.ntp.org<br>
&gt; </font></tt><a href=http://lists.ntp.org/listinfo/ntpwg><tt><font size=2 color=blue>http://lists.ntp.org/listinfo/ntpwg</font></tt></a>
<br>
<br><tt><font size=2>Best regards,</font></tt>
<br><tt><font size=2>Kristof Teichel<br>
</font></tt>
--=_alternative 002E1A50C1257E2A_=--

--===============6212103135738093370==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

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

From ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org  Fri Apr 17 07:04:50 2015
Return-Path: <ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org>
X-Original-To: ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com
Delivered-To: ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 74F591B2D1E for <ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com>; Fri, 17 Apr 2015 07:04:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level:
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 w77-2830J9t1 for <ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com>; Fri, 17 Apr 2015 07:04:49 -0700 (PDT)
Received: from psp3.ntp.org (psp3.ntp.org [149.20.68.23]) by ietfa.amsl.com (Postfix) with ESMTP id E520F1B2D1C for <ntp-archives-ahFae6za@lists.ietf.org>; Fri, 17 Apr 2015 07:04:47 -0700 (PDT)
Received: from psp3.ntp.org (localhost.ntp.org [127.0.0.1]) by psp3.ntp.org (Postfix) with ESMTP id D1CB139930 for <ntp-archives-ahFae6za@lists.ietf.org>; Fri, 17 Apr 2015 07:04:47 -0700 (PDT)
X-Original-To: ntpwg@lists.ntp.org
Delivered-To: ntpwg@lists.ntp.org
Received: from mail1.ntp.org (mail1.ntp.org [IPv6:2001:4f8:fff7:1::5]) by lists.ntp.org (Postfix) with ESMTP id A388286D48C; Fri, 17 Apr 2015 14:04:44 +0000 (UTC)
Received: from mx1.redhat.com ([209.132.183.28]) by mail1.ntp.org with esmtps (TLSv1:AES256-SHA:256) (Exim 4.77 (FreeBSD)) (envelope-from <fweimer@redhat.com>) id 1Yj6sm-000JeH-8q; Fri, 17 Apr 2015 14:04:44 +0000
Received: from int-mx09.intmail.prod.int.phx2.redhat.com (int-mx09.intmail.prod.int.phx2.redhat.com [10.5.11.22]) by mx1.redhat.com (Postfix) with ESMTPS id 6737C8E7BC; Fri, 17 Apr 2015 14:02:05 +0000 (UTC)
Received: from oldenburg.str.redhat.com (oldenburg.str.redhat.com [10.33.200.60]) by int-mx09.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4) with ESMTP id t3HE214A010102 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 17 Apr 2015 10:02:03 -0400
Message-ID: <55311259.8030407@redhat.com>
Date: Fri, 17 Apr 2015 16:02:01 +0200
From: Florian Weimer <fweimer@redhat.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.6.0
MIME-Version: 1.0
To: kristof.teichel@ptb.de
References: <551D1150.5080500@redhat.com>	<OF1F8E2A91.0B970EC7-ONC1257E22.00357A53-C1257E22.00381DAC@ptb.de>	<552663D3.7040005@redhat.com>	<OF8C2E5A2A.E24A2F5A-ONC1257E23.00500707-C1257E23.0051D4E9@ptb.de>	<5527E5B9.3000509@redhat.com>	<552E1D2C020000A100019D39@gwsmtp1.uni-regensburg.de> <552E468D.4090504@redhat.com> <OF31AAE487.B17B4BD0-ONC1257E2A.002B1230-C1257E2A.002E1A51@ptb.de>
In-Reply-To: <OF31AAE487.B17B4BD0-ONC1257E2A.002B1230-C1257E2A.002E1A51@ptb.de>
X-Scanned-By: MIMEDefang 2.68 on 10.5.11.22
X-SA-Exim-Connect-IP: 209.132.183.28
X-SA-Exim-Rcpt-To: ntpwg-bounces+kristof.teichel=ptb.de@lists.ntp.org, ntpwg@lists.ntp.org
X-SA-Exim-Mail-From: fweimer@redhat.com
X-SA-Exim-Version: 4.2
X-SA-Exim-Scanned: Yes (on mail1.ntp.org)
Subject: Re: [ntpwg] Antw: Re: Antwort: Re: Comments on various NTS drafts
X-BeenThere: ntpwg@lists.ntp.org
X-Mailman-Version: 2.1.20
Precedence: list
List-Id: IETF Working Group for Network Time Protocol <ntpwg.lists.ntp.org>
List-Unsubscribe: <http://lists.ntp.org/options/ntpwg>, <mailto:ntpwg-request@lists.ntp.org?subject=unsubscribe>
List-Archive: <http://lists.ntp.org/pipermail/ntpwg/>
List-Post: <mailto:ntpwg@lists.ntp.org>
List-Help: <mailto:ntpwg-request@lists.ntp.org?subject=help>
List-Subscribe: <http://lists.ntp.org/listinfo/ntpwg>, <mailto:ntpwg-request@lists.ntp.org?subject=subscribe>
Cc: ntpwg@lists.ntp.org, ntpwg <ntpwg-bounces+kristof.teichel=ptb.de@lists.ntp.org>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org
Sender: "ntpwg" <ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org>

On 04/17/2015 10:23 AM, kristof.teichel@ptb.de wrote:

>> There is a general belief within the IETF that you absolutely have to
>> change secrets regularly because every time you use them, you invariably
>> leak some information.  However, if the cryptographic primitive requires
>> rekeying for secure operation, it is generally quite broken and should
>> be replaced.
> 
> I am not sure how to understand your point. Are you saying it is 
> unnecessary, or are you saying it would be detrimental to re-key and must 
> be avoided? I have made myself familiar with the arguments for why 
> re-keying should be unnecessary from a cryptographic point of view, but I 
> still fail to see how it would be hurtful to include a possibility for 
> re-keying (as opposed to being unable to re-key even after years of usage 
> of a key).

It drives up complexity considerably.  The client needs to detect that a
rekeying has happened or is to happen soon.  Preferably, this
notification should be itself cryptographically secured, and this is a
bit tricky because you want to get rid of the key.

On the other hand, the same logic is needed to implement server restart
(which potentially discards the secret used for the cookie -> HMAC key
mapping).  But server restart should be a rare event, so this case does
not have to be handled as reliably.

> Side note: our thoughts were more along the lines of re-keying after a 
> given period of time.

The only reason I can see for that is to implement revoking the service
(i.e., client authenticates, but policy changes in some way, and it
would no longer be welcome).

-- 
Florian Weimer / Red Hat Product Security
_______________________________________________
ntpwg mailing list
ntpwg@lists.ntp.org
http://lists.ntp.org/listinfo/ntpwg

From ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org  Mon Apr 20 19:44:04 2015
Return-Path: <ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org>
X-Original-To: ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com
Delivered-To: ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9905D1A8826 for <ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com>; Mon, 20 Apr 2015 19:44:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.909
X-Spam-Level:
X-Spam-Status: No, score=-1.909 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 zeTUTKDaPuKd for <ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com>; Mon, 20 Apr 2015 19:44:02 -0700 (PDT)
Received: from psp3.ntp.org (psp3.ntp.org [149.20.68.23]) by ietfa.amsl.com (Postfix) with ESMTP id 07EEF1A8827 for <ntp-archives-ahFae6za@lists.ietf.org>; Mon, 20 Apr 2015 19:44:02 -0700 (PDT)
Received: from psp3.ntp.org (localhost.ntp.org [127.0.0.1]) by psp3.ntp.org (Postfix) with ESMTP id BB71C39919 for <ntp-archives-ahFae6za@lists.ietf.org>; Mon, 20 Apr 2015 19:44:00 -0700 (PDT)
X-Original-To: ntpwg@lists.ntp.org
Delivered-To: ntpwg@lists.ntp.org
Received: from mail1.ntp.org (mail1.ntp.org [IPv6:2001:4f8:fff7:1::5]) by lists.ntp.org (Postfix) with ESMTP id 7591E86D55F for <ntpwg@lists.ntp.org>; Mon, 20 Apr 2015 04:51:16 +0000 (UTC)
Received: from szxga03-in.huawei.com ([119.145.14.66]) by mail1.ntp.org with esmtps (TLSv1:RC4-SHA:128) (Exim 4.77 (FreeBSD)) (envelope-from <anil.sn@huawei.com>) id 1Yk3fl-000AOJ-R0 for ntpwg@lists.ntp.org; Mon, 20 Apr 2015 04:51:16 +0000
Received: from 172.24.2.119 (EHLO nkgeml410-hub.china.huawei.com) ([172.24.2.119]) by szxrg03-dlp.huawei.com (MOS 4.4.3-GA FastPath queued) with ESMTP id BES74775; Mon, 20 Apr 2015 12:49:31 +0800 (CST)
Received: from NKGEML512-MBX.china.huawei.com ([169.254.7.135]) by nkgeml410-hub.china.huawei.com ([10.98.56.41]) with mapi id 14.03.0158.001; Mon, 20 Apr 2015 12:49:22 +0800
From: "Anil Kumar S N (VRP Network BL)" <anil.sn@huawei.com>
To: "ntpwg@lists.ntp.org" <ntpwg@lists.ntp.org>
Thread-Topic: [NTP Protocol] strengthening  NTP control packets for diagnostic purpose
Thread-Index: AdB4SlgroQbCRORtRlGVD5QLkpitfA==
Date: Mon, 20 Apr 2015 04:49:22 +0000
Message-ID: <327562D94EA7BF428CD805F338C31EF04FB38946@nkgeml512-mbx.china.huawei.com>
Accept-Language: en-US, zh-CN
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.18.212.150]
MIME-Version: 1.0
X-CFilter-Loop: Reflected
X-Mirapoint-Virus-RAPID-Raw: score=unknown(0), refid=str=0001.0A020202.5534855C.0129, ss=1, re=0.000, recu=0.000, reip=0.000, cl=1, cld=1, fgs=0, ip=169.254.7.135, so=2013-05-26 15:14:31, dmn=2013-03-21 17:37:32
X-Mirapoint-Loop-Id: 8209896e8ff229f9da232cc1ba64d137
X-SA-Exim-Connect-IP: 119.145.14.66
X-SA-Exim-Rcpt-To: ntpwg@lists.ntp.org
X-SA-Exim-Mail-From: anil.sn@huawei.com
X-SA-Exim-Version: 4.2
X-SA-Exim-Scanned: Yes (on mail1.ntp.org)
X-Mailman-Approved-At: Tue, 21 Apr 2015 02:43:56 +0000
Subject: [ntpwg] [NTP Protocol] strengthening NTP control packets for diagnostic purpose
X-BeenThere: ntpwg@lists.ntp.org
X-Mailman-Version: 2.1.20
Precedence: list
List-Id: IETF Working Group for Network Time Protocol <ntpwg.lists.ntp.org>
List-Unsubscribe: <http://lists.ntp.org/options/ntpwg>, <mailto:ntpwg-request@lists.ntp.org?subject=unsubscribe>
List-Archive: <http://lists.ntp.org/pipermail/ntpwg/>
List-Post: <mailto:ntpwg@lists.ntp.org>
List-Help: <mailto:ntpwg-request@lists.ntp.org?subject=help>
List-Subscribe: <http://lists.ntp.org/listinfo/ntpwg>, <mailto:ntpwg-request@lists.ntp.org?subject=subscribe>
Cc: "Ankit Kumar Sinha \(A\)" <Ankit.Kumar.Sinha1@huawei.com>, Karen O'Donoghue <odonoghue@isoc.org>, Rajeshmv <rajeshmv@huawei.com>, kasturi chandradeep <kasturi.chandradeep@huawei.com>, Dhruv Dhody <dhruv.dhody@huawei.com>, Chirag shah <chirag.shah@huawei.com>, Kalyankumar Asangi <kalyana@huawei.com>
Content-Type: multipart/mixed; boundary="===============8589322795213437791=="
Errors-To: ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org
Sender: "ntpwg" <ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org>

--===============8589322795213437791==
Content-Language: en-US
Content-Type: multipart/alternative;
	boundary="_000_327562D94EA7BF428CD805F338C31EF04FB38946nkgeml512mbxchi_"

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

Hi Folks,

                Please give your opinion on strengthening of NTP control pa=
ckets for better diagnostic purpose.

Is Yang model and MIB is sufficient ? Will it help to get all the informati=
on ?
Ex: Authorization for management protocol such as MIB/Yang  is limited with=
 respect to service provider, As NTP servers could be managed by other serv=
ice providers.

I feel Mr. Mills was aware of this so he introduced control packets, but I =
feel it's out dated.

There are two options

1.       NTP dynamic runtime diagnostic tools can be implemented using NTP =
extensions using protocol packets

2.       Strengthen NTP control packets with new options to achieve the sam=
e. [Preferred]

Please give your opinion. We are working on this, Your opinion matters.


Thanks & Regards
Anil S N

"Be liberal in what you accept, and conservative in what you send" - Jon Po=
stel



--_000_327562D94EA7BF428CD805F338C31EF04FB38946nkgeml512mbxchi_
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=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 12 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:SimSun;
	panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:SimSun;
	panose-1:2 1 6 0 3 1 1 1 1 1;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	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;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
	{mso-style-priority:34;
	margin-top:0cm;
	margin-right:0cm;
	margin-bottom:0cm;
	margin-left:36.0pt;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
span.EmailStyle18
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:72.0pt 90.0pt 72.0pt 90.0pt;}
div.WordSection1
	{page:WordSection1;}
/* List Definitions */
@list l0
	{mso-list-id:1123815839;
	mso-list-type:hybrid;
	mso-list-template-ids:743079742 -1861029632 67698713 67698715 67698703 676=
98713 67698715 67698703 67698713 67698715;}
@list l0:level1
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	margin-left:54.0pt;
	text-indent:-18.0pt;}
@list l0:level2
	{mso-level-tab-stop:72.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l0:level3
	{mso-level-tab-stop:108.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l0:level4
	{mso-level-tab-stop:144.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l0:level5
	{mso-level-tab-stop:180.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l0:level6
	{mso-level-tab-stop:216.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l0:level7
	{mso-level-tab-stop:252.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l0:level8
	{mso-level-tab-stop:288.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l0:level9
	{mso-level-tab-stop:324.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
ol
	{margin-bottom:0cm;}
ul
	{margin-bottom:0cm;}
--></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=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal">Hi Folks, <o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Please give your opinion on strength=
ening of NTP control packets for better diagnostic purpose. &nbsp;<o:p></o:=
p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal" style=3D"text-indent:36.0pt">Is Yang model and MIB i=
s sufficient ? Will it help to get all the information ?<o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"text-indent:36.0pt">Ex: Authorization for m=
anagement protocol such as MIB/Yang &nbsp;is limited with respect to servic=
e provider, As NTP servers could be managed by other service providers.
<o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"text-indent:36.0pt"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal" style=3D"text-indent:36.0pt">I feel Mr. <span lang=
=3D"EN">Mills was aware of this so he introduced control packets, but I fee=
l it&#8217;s out dated.
</span><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"text-indent:36.0pt"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal" style=3D"text-indent:36.0pt">There are two options<o=
:p></o:p></p>
<p class=3D"MsoListParagraph" style=3D"margin-left:54.0pt;text-indent:-18.0=
pt;mso-list:l0 level1 lfo2">
<![if !supportLists]><span style=3D"mso-list:Ignore">1.<span style=3D"font:=
7.0pt &quot;Times New Roman&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span><![endif]>NTP dynamic runtime diagnostic tools can be impleme=
nted using NTP extensions using protocol packets
<o:p></o:p></p>
<p class=3D"MsoListParagraph" style=3D"margin-left:54.0pt;text-indent:-18.0=
pt;mso-list:l0 level1 lfo2">
<![if !supportLists]><span style=3D"mso-list:Ignore">2.<span style=3D"font:=
7.0pt &quot;Times New Roman&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span><![endif]>Strengthen NTP control packets with new options to =
achieve the same. [Preferred]<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal" style=3D"margin-left:36.0pt">Please give your opinio=
n. We are working on this, Your opinion matters.<o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"margin-left:36.0pt"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Thanks &amp; Regards<o:p></o:p></p>
<p class=3D"MsoNormal">Anil S N<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">&#8220;Be liberal in what you accept, and conservati=
ve in what you send&#8221; - Jon Postel<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>
</div>
</body>
</html>

--_000_327562D94EA7BF428CD805F338C31EF04FB38946nkgeml512mbxchi_--


--===============8589322795213437791==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

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


From ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org  Tue Apr 21 12:43:13 2015
Return-Path: <ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org>
X-Original-To: ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com
Delivered-To: ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BED051B2AE2 for <ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com>; Tue, 21 Apr 2015 12:43:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level:
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 4DWpebjHiyvK for <ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com>; Tue, 21 Apr 2015 12:43:12 -0700 (PDT)
Received: from psp3.ntp.org (psp3.ntp.org [149.20.68.23]) by ietfa.amsl.com (Postfix) with ESMTP id 192A31B2AD8 for <ntp-archives-ahFae6za@lists.ietf.org>; Tue, 21 Apr 2015 12:43:12 -0700 (PDT)
Received: from psp3.ntp.org (localhost.ntp.org [127.0.0.1]) by psp3.ntp.org (Postfix) with ESMTP id E90483991D for <ntp-archives-ahFae6za@lists.ietf.org>; Tue, 21 Apr 2015 12:43:11 -0700 (PDT)
X-Original-To: ntpwg@lists.ntp.org
Delivered-To: ntpwg@lists.ntp.org
Received: from mail1.ntp.org (mail1.ntp.org [IPv6:2001:4f8:fff7:1::5]) by lists.ntp.org (Postfix) with ESMTP id 5128886D55F for <ntpwg@lists.ntp.org>; Tue, 21 Apr 2015 19:43:08 +0000 (UTC)
Received: from mail-am1on0087.outbound.protection.outlook.com ([157.56.112.87] helo=emea01-am1-obe.outbound.protection.outlook.com) by mail1.ntp.org with esmtps (TLSv1:AES256-SHA:256) (Exim 4.77 (FreeBSD)) (envelope-from <denis.reilly@spectracom.orolia.com>) id 1Yke4S-000BcS-6U for ntpwg@lists.ntp.org; Tue, 21 Apr 2015 19:43:08 +0000
Received: from AM3PR06MB1202.eurprd06.prod.outlook.com (25.163.60.28) by AM3PR06MB1202.eurprd06.prod.outlook.com (25.163.60.28) with Microsoft SMTP Server (TLS) id 15.1.136.25; Tue, 21 Apr 2015 19:41:41 +0000
Received: from AM3PR06MB1202.eurprd06.prod.outlook.com ([25.163.60.28]) by AM3PR06MB1202.eurprd06.prod.outlook.com ([25.163.60.28]) with mapi id 15.01.0136.026; Tue, 21 Apr 2015 19:41:41 +0000
From: Denis Reilly <denis.reilly@spectracom.orolia.com>
To: "ntpwg@lists.ntp.org" <ntpwg@lists.ntp.org>
Thread-Topic: Call for Ideas: NTP BCP
Thread-Index: AdB8aqI1PJdi245OQzCeSDg4G1qJNg==
Date: Tue, 21 Apr 2015 19:41:41 +0000
Message-ID: <AM3PR06MB1202E88A2B6E920F20F6BC13D2EF0@AM3PR06MB1202.eurprd06.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
authentication-results: lists.ntp.org; dkim=none (message not signed) header.d=none;
x-originating-ip: [66.193.84.98]
x-microsoft-antispam: UriScan:;BCL:0;PCL:0;RULEID:;SRVR:AM3PR06MB1202;
x-microsoft-antispam-prvs: <AM3PR06MB12024A10A982C7740D34AAE1D2EF0@AM3PR06MB1202.eurprd06.prod.outlook.com>
x-forefront-antispam-report: BMV:1; SFV:NSPM; SFS:(10009020)(6009001)(41584004)(52044002)(86362001)(62966003)(122556002)(74316001)(50986999)(66066001)(92566002)(76576001)(110136001)(54356999)(1720100001)(2501003)(15974865002)(46102003)(40100003)(15975445007)(2656002)(2900100001)(87936001)(19580395003)(2351001)(229853001)(77156002)(19580405001)(102836002)(33656002)(7059030); DIR:OUT; SFP:1101; SCL:1; SRVR:AM3PR06MB1202; H:AM3PR06MB1202.eurprd06.prod.outlook.com; FPR:; SPF:None; MLV:sfv; LANG:en; 
x-exchange-antispam-report-test: UriScan:;
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(601004)(5005006)(5002010); SRVR:AM3PR06MB1202; BCL:0; PCL:0; RULEID:; SRVR:AM3PR06MB1202; 
x-forefront-prvs: 0553CBB77A
MIME-Version: 1.0
X-OriginatorOrg: spectracom.orolia.com
X-MS-Exchange-CrossTenant-originalarrivaltime: 21 Apr 2015 19:41:41.4068 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: a263030c-9c1b-421f-9471-1dec0b29c664
X-MS-Exchange-Transport-CrossTenantHeadersStamped: AM3PR06MB1202
X-SA-Exim-Connect-IP: 157.56.112.87
X-SA-Exim-Rcpt-To: ntpwg@lists.ntp.org
X-SA-Exim-Mail-From: denis.reilly@spectracom.orolia.com
X-SA-Exim-Version: 4.2
X-SA-Exim-Scanned: Yes (on mail1.ntp.org)
Subject: [ntpwg] Call for Ideas: NTP BCP
X-BeenThere: ntpwg@lists.ntp.org
X-Mailman-Version: 2.1.20
Precedence: list
List-Id: IETF Working Group for Network Time Protocol <ntpwg.lists.ntp.org>
List-Unsubscribe: <http://lists.ntp.org/options/ntpwg>, <mailto:ntpwg-request@lists.ntp.org?subject=unsubscribe>
List-Archive: <http://lists.ntp.org/pipermail/ntpwg/>
List-Post: <mailto:ntpwg@lists.ntp.org>
List-Help: <mailto:ntpwg-request@lists.ntp.org?subject=help>
List-Subscribe: <http://lists.ntp.org/listinfo/ntpwg>, <mailto:ntpwg-request@lists.ntp.org?subject=subscribe>
Cc: "stenn@nwtime.org" <stenn@nwtime.org>, "odonoghue@isoc.org" <odonoghue@isoc.org>
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Errors-To: ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org
Sender: "ntpwg" <ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org>

All,

I've started a Wiki page to use to start brainstorming ideas for the NTP BC=
P. I've started it with the brief outline I presented in Dallas, along with=
 some suggestions that came up during the session.

You can access the Wiki here (it's not linked to from anywhere else yet):
http://trac.tools.ietf.org/wg/ntp/trac/wiki/BcpOutline

Feel free to edit it and add ideas as you see fit directly to the Wiki -- I=
'll follow up and try to keep it all coherent. I'm not looking for standard=
s language at this point, I just want to make sure that we think about and =
identify essential topics that need to be in this document. We will get to =
the actual text after kicking around ideas for a few weeks.

I also started a section for more general ideas that came up, but may not f=
it in the scope of the document. I still want to preserve these ideas in ca=
se someone finds a way to make them fit.

If you don't want to edit the Wiki, just post your thoughts here and I will=
 transfer them to the Wiki.

Regards,

--
Denis Reilly=A0=A0=A0 denis.reilly@spectracom.orolia.com

Lead Engineer, Spectracom
www.spectracomcorp.com
Office: (585) 321-5837
Fax:=A0=A0=A0 (585) 321-5219

An Orolia Group Business: www.orolia.com

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

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

From ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org  Tue Apr 21 14:26:08 2015
Return-Path: <ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org>
X-Original-To: ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com
Delivered-To: ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D94D41B2B9E for <ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com>; Tue, 21 Apr 2015 14:26:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level:
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 C1KzerD4WW1p for <ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com>; Tue, 21 Apr 2015 14:26:07 -0700 (PDT)
Received: from psp3.ntp.org (psp3.ntp.org [149.20.68.23]) by ietfa.amsl.com (Postfix) with ESMTP id 6265D1B2B9A for <ntp-archives-ahFae6za@lists.ietf.org>; Tue, 21 Apr 2015 14:26:07 -0700 (PDT)
Received: from psp3.ntp.org (localhost.ntp.org [127.0.0.1]) by psp3.ntp.org (Postfix) with ESMTP id 0E2A73991C for <ntp-archives-ahFae6za@lists.ietf.org>; Tue, 21 Apr 2015 14:26:07 -0700 (PDT)
X-Original-To: ntpwg@lists.ntp.org
Delivered-To: ntpwg@lists.ntp.org
Received: from mail1.ntp.org (mail1.ntp.org [IPv6:2001:4f8:fff7:1::5]) by lists.ntp.org (Postfix) with ESMTP id A5A2B86D55F for <ntpwg@lists.ntp.org>; Tue, 21 Apr 2015 21:15:00 +0000 (UTC)
Received: from albireo.enyo.de ([46.237.207.196]) by mail1.ntp.org with esmtps (TLSv1:AES128-SHA:128) (Exim 4.77 (FreeBSD)) (envelope-from <fw@deneb.enyo.de>) id 1YkfVK-000FWr-Aw for ntpwg@lists.ntp.org; Tue, 21 Apr 2015 21:14:59 +0000
Received: from [172.17.203.2] (helo=deneb.enyo.de) by albireo.enyo.de with esmtps (TLS1.2:DHE_RSA_AES_128_CBC_SHA1:128) id 1YkfU0-0008Kk-6L; Tue, 21 Apr 2015 23:13:28 +0200
Received: from fw by deneb.enyo.de with local (Exim 4.80) (envelope-from <fw@deneb.enyo.de>) id 1YkfTz-0003lp-TG; Tue, 21 Apr 2015 23:13:27 +0200
From: Florian Weimer <fw@deneb.enyo.de>
To: "Anil Kumar S N \(VRP Network BL\)" <anil.sn@huawei.com>
References: <327562D94EA7BF428CD805F338C31EF04FB38946@nkgeml512-mbx.china.huawei.com>
Date: Tue, 21 Apr 2015 23:13:27 +0200
In-Reply-To: <327562D94EA7BF428CD805F338C31EF04FB38946@nkgeml512-mbx.china.huawei.com> (Anil Kumar S. N.'s message of "Mon, 20 Apr 2015 04:49:22 +0000")
Message-ID: <87bnihyyko.fsf@mid.deneb.enyo.de>
MIME-Version: 1.0
X-SA-Exim-Connect-IP: 46.237.207.196
X-SA-Exim-Rcpt-To: ntpwg@lists.ntp.org
X-SA-Exim-Mail-From: fw@deneb.enyo.de
X-SA-Exim-Version: 4.2
X-SA-Exim-Scanned: Yes (on mail1.ntp.org)
X-Mailman-Approved-At: Tue, 21 Apr 2015 21:26:04 +0000
Subject: Re: [ntpwg] [NTP Protocol] strengthening NTP control packets for diagnostic purpose
X-BeenThere: ntpwg@lists.ntp.org
X-Mailman-Version: 2.1.20
Precedence: list
List-Id: IETF Working Group for Network Time Protocol <ntpwg.lists.ntp.org>
List-Unsubscribe: <http://lists.ntp.org/options/ntpwg>, <mailto:ntpwg-request@lists.ntp.org?subject=unsubscribe>
List-Archive: <http://lists.ntp.org/pipermail/ntpwg/>
List-Post: <mailto:ntpwg@lists.ntp.org>
List-Help: <mailto:ntpwg-request@lists.ntp.org?subject=help>
List-Subscribe: <http://lists.ntp.org/listinfo/ntpwg>, <mailto:ntpwg-request@lists.ntp.org?subject=subscribe>
Cc: Karen O'Donoghue <odonoghue@isoc.org>, "ntpwg@lists.ntp.org" <ntpwg@lists.ntp.org>, Rajeshmv <rajeshmv@huawei.com>, kasturi chandradeep <kasturi.chandradeep@huawei.com>, Dhruv Dhody <dhruv.dhody@huawei.com>, Chirag shah <chirag.shah@huawei.com>, Kalyankumar Asangi <kalyana@huawei.com>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org
Sender: "ntpwg" <ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org>

* Anil Kumar S. N.:

> There are two options
>
> 1.       NTP dynamic runtime diagnostic tools can be implemented using NTP extensions using protocol packets
>
> 2.       Strengthen NTP control packets with new options to achieve the same. [Preferred]

I seriously suggest to consider moving diagnostics and other form of
management out of band (say SNMP, CIM or PCP, basically anything else
that does not run over port 123/UDP), so that these interfaces are not
constrained by the NTP technical framework regarding authentication,
authorization, confidentiality, and integrity protection.
_______________________________________________
ntpwg mailing list
ntpwg@lists.ntp.org
http://lists.ntp.org/listinfo/ntpwg

From ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org  Tue Apr 21 21:19:27 2015
Return-Path: <ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org>
X-Original-To: ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com
Delivered-To: ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 49ACE1B3195 for <ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com>; Tue, 21 Apr 2015 21:19:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level:
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 rk3cLiMsELO8 for <ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com>; Tue, 21 Apr 2015 21:19:25 -0700 (PDT)
Received: from psp3.ntp.org (psp3.ntp.org [149.20.68.23]) by ietfa.amsl.com (Postfix) with ESMTP id 531E31B3198 for <ntp-archives-ahFae6za@lists.ietf.org>; Tue, 21 Apr 2015 21:19:25 -0700 (PDT)
Received: from psp3.ntp.org (localhost.ntp.org [127.0.0.1]) by psp3.ntp.org (Postfix) with ESMTP id B986939914 for <ntp-archives-ahFae6za@lists.ietf.org>; Tue, 21 Apr 2015 21:19:24 -0700 (PDT)
X-Original-To: ntpwg@lists.ntp.org
Delivered-To: ntpwg@lists.ntp.org
Received: from mail1.ntp.org (mail1.ntp.org [IPv6:2001:4f8:fff7:1::5]) by lists.ntp.org (Postfix) with ESMTP id E4A9386D55F for <ntpwg@lists.ntp.org>; Wed, 22 Apr 2015 04:19:21 +0000 (UTC)
Received: from [58.251.152.64] (helo=szxga01-in.huawei.com) by mail1.ntp.org with esmtps (TLSv1:RC4-SHA:128) (Exim 4.77 (FreeBSD)) (envelope-from <anil.sn@huawei.com>) id 1Ykm80-00045F-5O for ntpwg@lists.ntp.org; Wed, 22 Apr 2015 04:19:21 +0000
Received: from 172.24.2.119 (EHLO nkgeml409-hub.china.huawei.com) ([172.24.2.119]) by szxrg01-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id CMM28812; Wed, 22 Apr 2015 12:17:30 +0800 (CST)
Received: from NKGEML512-MBX.china.huawei.com ([169.254.7.135]) by nkgeml409-hub.china.huawei.com ([10.98.56.40]) with mapi id 14.03.0158.001; Wed, 22 Apr 2015 12:17:23 +0800
From: "Anil Kumar S N (VRP Network BL)" <anil.sn@huawei.com>
To: Florian Weimer <fw@deneb.enyo.de>
Thread-Topic: [ntpwg] [NTP Protocol] strengthening NTP control packets for diagnostic purpose
Thread-Index: AQHQfHg7s1XuMHWOFEe3sZkoACOK+J1YaqkQ
Date: Wed, 22 Apr 2015 04:17:23 +0000
Message-ID: <327562D94EA7BF428CD805F338C31EF04FB38CD5@nkgeml512-mbx.china.huawei.com>
References: <327562D94EA7BF428CD805F338C31EF04FB38946@nkgeml512-mbx.china.huawei.com> <87bnihyyko.fsf@mid.deneb.enyo.de>
In-Reply-To: <87bnihyyko.fsf@mid.deneb.enyo.de>
Accept-Language: en-US, zh-CN
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.18.212.150]
MIME-Version: 1.0
X-CFilter-Loop: Reflected
X-SA-Exim-Connect-IP: 58.251.152.64
X-SA-Exim-Rcpt-To: ntpwg@lists.ntp.org
X-SA-Exim-Mail-From: anil.sn@huawei.com
X-SA-Exim-Version: 4.2
X-SA-Exim-Scanned: Yes (on mail1.ntp.org)
Subject: Re: [ntpwg] [NTP Protocol] strengthening NTP control packets for diagnostic purpose
X-BeenThere: ntpwg@lists.ntp.org
X-Mailman-Version: 2.1.20
Precedence: list
List-Id: IETF Working Group for Network Time Protocol <ntpwg.lists.ntp.org>
List-Unsubscribe: <http://lists.ntp.org/options/ntpwg>, <mailto:ntpwg-request@lists.ntp.org?subject=unsubscribe>
List-Archive: <http://lists.ntp.org/pipermail/ntpwg/>
List-Post: <mailto:ntpwg@lists.ntp.org>
List-Help: <mailto:ntpwg-request@lists.ntp.org?subject=help>
List-Subscribe: <http://lists.ntp.org/listinfo/ntpwg>, <mailto:ntpwg-request@lists.ntp.org?subject=subscribe>
Cc: Karen O'Donoghue <odonoghue@isoc.org>, "ntpwg@lists.ntp.org" <ntpwg@lists.ntp.org>, Rajeshmv <rajeshmv@huawei.com>, kasturi chandradeep <kasturi.chandradeep@huawei.com>, Dhruv Dhody <dhruv.dhody@huawei.com>, Chirag shah <chirag.shah@huawei.com>, Kalyankumar Asangi <kalyana@huawei.com>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org
Sender: "ntpwg" <ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org>

Hi Weimer,

	You are right, control packets are introduced with the same intention in the mind that only NTP core functionality should be with NTP packets.
	If I am not wrong, NTPq and NTPd process in Linux handle control packets and NTP packets respectively. 

	We just want to standardize and strengthen control packets to the current needs. 
	I want to trigger a discussion in the forum so that we can collect the opinions to come up with better solutions.

Thanks & Regards
Anil S N

"Be liberal in what you accept, and conservative in what you send" - Jon Postel



-----Original Message-----
From: Florian Weimer [mailto:fw@deneb.enyo.de] 
Sent: 22 April 2015 02:43
To: Anil Kumar S N (VRP Network BL)
Cc: ntpwg@lists.ntp.org; Ankit Kumar Sinha (A); Karen O'Donoghue; Rajeshmv; kasturi chandradeep; Dhruv Dhody; Chirag shah; Kalyankumar Asangi
Subject: Re: [ntpwg] [NTP Protocol] strengthening NTP control packets for diagnostic purpose

* Anil Kumar S. N.:

> There are two options
>
> 1.       NTP dynamic runtime diagnostic tools can be implemented using NTP extensions using protocol packets
>
> 2.       Strengthen NTP control packets with new options to achieve the same. [Preferred]

I seriously suggest to consider moving diagnostics and other form of management out of band (say SNMP, CIM or PCP, basically anything else that does not run over port 123/UDP), so that these interfaces are not constrained by the NTP technical framework regarding authentication, authorization, confidentiality, and integrity protection.
_______________________________________________
ntpwg mailing list
ntpwg@lists.ntp.org
http://lists.ntp.org/listinfo/ntpwg

From ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org  Tue Apr 21 23:48:33 2015
Return-Path: <ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org>
X-Original-To: ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com
Delivered-To: ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 554551B31FF for <ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com>; Tue, 21 Apr 2015 23:48:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level:
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 TPSl2xEZaJeE for <ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com>; Tue, 21 Apr 2015 23:48:31 -0700 (PDT)
Received: from psp3.ntp.org (psp3.ntp.org [149.20.68.23]) by ietfa.amsl.com (Postfix) with ESMTP id BC4891B31FD for <ntp-archives-ahFae6za@lists.ietf.org>; Tue, 21 Apr 2015 23:48:31 -0700 (PDT)
Received: from psp3.ntp.org (localhost.ntp.org [127.0.0.1]) by psp3.ntp.org (Postfix) with ESMTP id 1519F39918 for <ntp-archives-ahFae6za@lists.ietf.org>; Tue, 21 Apr 2015 23:48:31 -0700 (PDT)
X-Original-To: ntpwg@lists.ntp.org
Delivered-To: ntpwg@lists.ntp.org
Received: from mail1.ntp.org (mail1.ntp.org [IPv6:2001:4f8:fff7:1::5]) by lists.ntp.org (Postfix) with ESMTP id 8A9D086D55F for <ntpwg@lists.ntp.org>; Wed, 22 Apr 2015 06:48:28 +0000 (UTC)
Received: from rrzmta2.uni-regensburg.de ([194.94.155.52]) by mail1.ntp.org with esmtps (TLSv1:CAMELLIA256-SHA:256) (Exim 4.77 (FreeBSD)) (envelope-from <Ulrich.Windl@rz.uni-regensburg.de>) id 1YkoSJ-0009Z0-GG for ntpwg@lists.ntp.org; Wed, 22 Apr 2015 06:48:28 +0000
Received: from rrzmta2.uni-regensburg.de (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id 0A22C5FC95 for <ntpwg@lists.ntp.org>; Wed, 22 Apr 2015 08:47:02 +0200 (CEST)
Received: from gwsmtp1.uni-regensburg.de (gwsmtp1.uni-regensburg.de [132.199.5.51]) by rrzmta2.uni-regensburg.de (Postfix) with ESMTP id DDF035FC1B for <ntpwg@lists.ntp.org>; Wed, 22 Apr 2015 08:47:01 +0200 (CEST)
Received: from uni-regensburg-smtp1-MTA by gwsmtp1.uni-regensburg.de with Novell_GroupWise; Wed, 22 Apr 2015 08:47:01 +0200
Message-Id: <55376003020000A100019F53@gwsmtp1.uni-regensburg.de>
X-Mailer: Novell GroupWise Internet Agent 14.0.1 
Date: Wed, 22 Apr 2015 08:46:59 +0200
From: "Ulrich Windl" <Ulrich.Windl@rz.uni-regensburg.de>
To: <fw@deneb.enyo.de>,<anil.sn@huawei.com>
References: <327562D94EA7BF428CD805F338C31EF04FB38946@nkgeml512-mbx.china.huawei.com><327562D94EA7BF428CD805F338C31EF04FB38946@nkgeml512-mbx.china.huawei.com> (Anil Kumar S. N.'s message of "Mon, 20 Apr 2015 04:49:22 +0000") <87bnihyyko.fsf@mid.deneb.enyo.de>
In-Reply-To: <87bnihyyko.fsf@mid.deneb.enyo.de>
Mime-Version: 1.0
Content-Disposition: inline
X-SA-Exim-Connect-IP: 194.94.155.52
X-SA-Exim-Rcpt-To: ntpwg@lists.ntp.org
X-SA-Exim-Mail-From: Ulrich.Windl@rz.uni-regensburg.de
X-SA-Exim-Version: 4.2
X-SA-Exim-Scanned: Yes (on mail1.ntp.org)
Subject: [ntpwg] Antw: Re: [NTP Protocol] strengthening NTP control packets for diagnostic purpose
X-BeenThere: ntpwg@lists.ntp.org
X-Mailman-Version: 2.1.20
Precedence: list
List-Id: IETF Working Group for Network Time Protocol <ntpwg.lists.ntp.org>
List-Unsubscribe: <http://lists.ntp.org/options/ntpwg>, <mailto:ntpwg-request@lists.ntp.org?subject=unsubscribe>
List-Archive: <http://lists.ntp.org/pipermail/ntpwg/>
List-Post: <mailto:ntpwg@lists.ntp.org>
List-Help: <mailto:ntpwg-request@lists.ntp.org?subject=help>
List-Subscribe: <http://lists.ntp.org/listinfo/ntpwg>, <mailto:ntpwg-request@lists.ntp.org?subject=subscribe>
Cc: odonoghue@isoc.org, ntpwg@lists.ntp.org, rajeshmv@huawei.com, kasturi.chandradeep@huawei.com, dhruv.dhody@huawei.com, chirag.shah@huawei.com, kalyana@huawei.com
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org
Sender: "ntpwg" <ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org>

>>> Florian Weimer <fw@deneb.enyo.de> schrieb am 21.04.2015 um 23:13 in Nachricht
<87bnihyyko.fsf@mid.deneb.enyo.de>:
> * Anil Kumar S. N.:
> 
>> There are two options
>>
>> 1.       NTP dynamic runtime diagnostic tools can be implemented using NTP 
> extensions using protocol packets
>>
>> 2.       Strengthen NTP control packets with new options to achieve the 
> same. [Preferred]
> 
> I seriously suggest to consider moving diagnostics and other form of
> management out of band (say SNMP, CIM or PCP, basically anything else
> that does not run over port 123/UDP), so that these interfaces are not
> constrained by the NTP technical framework regarding authentication,
> authorization, confidentiality, and integrity protection.

Well, SNMP, CIM and PCP (Performance Co-Pilot?) all may be more standard, but they all have some extra protocol (and library) overhead. And I think confidentiality and integrity are also issues when monitoring or controlling NTP. So I don't see why you want to have it out-band (unless you simply want to get rid of it).

Modeling NTP in SNMP may be an interesting exercise (consuming many hours), but may end up in a moster that only few people want to deal with. I don't like framework monsters feeding each other...

Regards,
Ulrich

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




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

From ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org  Wed Apr 22 00:29:23 2015
Return-Path: <ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org>
X-Original-To: ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com
Delivered-To: ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 87C4C1B32B3 for <ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com>; Wed, 22 Apr 2015 00:29:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.909
X-Spam-Level:
X-Spam-Status: No, score=-1.909 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 HukqUHEZB2ED for <ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com>; Wed, 22 Apr 2015 00:29:22 -0700 (PDT)
Received: from psp3.ntp.org (psp3.ntp.org [149.20.68.23]) by ietfa.amsl.com (Postfix) with ESMTP id 33E351B32BA for <ntp-archives-ahFae6za@lists.ietf.org>; Wed, 22 Apr 2015 00:29:22 -0700 (PDT)
Received: from psp3.ntp.org (localhost.ntp.org [127.0.0.1]) by psp3.ntp.org (Postfix) with ESMTP id 2A2C93991C for <ntp-archives-ahFae6za@lists.ietf.org>; Wed, 22 Apr 2015 00:29:22 -0700 (PDT)
X-Original-To: ntpwg@lists.ntp.org
Delivered-To: ntpwg@lists.ntp.org
Received: from mail1.ntp.org (mail1.ntp.org [IPv6:2001:4f8:fff7:1::5]) by lists.ntp.org (Postfix) with ESMTP id 5A4C286D55F for <ntpwg@lists.ntp.org>; Wed, 22 Apr 2015 07:29:18 +0000 (UTC)
Received: from szxga02-in.huawei.com ([119.145.14.65]) by mail1.ntp.org with esmtps (TLSv1:RC4-SHA:128) (Exim 4.77 (FreeBSD)) (envelope-from <eric.wu@huawei.com>) id 1Ykp5q-000Bis-56 for ntpwg@lists.ntp.org; Wed, 22 Apr 2015 07:29:18 +0000
Received: from 172.24.2.119 (EHLO SZXEMA412-HUB.china.huawei.com) ([172.24.2.119]) by szxrg02-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id CKD37464; Wed, 22 Apr 2015 15:27:38 +0800 (CST)
Received: from SZXEMA508-MBX.china.huawei.com ([169.254.7.38]) by SZXEMA412-HUB.china.huawei.com ([10.82.72.71]) with mapi id 14.03.0158.001; Wed, 22 Apr 2015 15:27:34 +0800
From: "Wunan (Eric)" <eric.wu@huawei.com>
To: "ntpwg@lists.ntp.org" <ntpwg@lists.ntp.org>
Thread-Topic: Solicit comments for draft-wu-ntp-ntp-cfg-00
Thread-Index: AdB8zUWsUJxLvQchQjillo6mEul/oA==
Date: Wed, 22 Apr 2015 07:27:33 +0000
Message-ID: <0F26584357FD124DB93F1535E4B0A6505FBB743F@szxema508-mbx.china.huawei.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.111.87.81]
MIME-Version: 1.0
X-CFilter-Loop: Reflected
X-SA-Exim-Connect-IP: 119.145.14.65
X-SA-Exim-Rcpt-To: ntpwg@lists.ntp.org
X-SA-Exim-Mail-From: eric.wu@huawei.com
X-SA-Exim-Version: 4.2
X-SA-Exim-Scanned: Yes (on mail1.ntp.org)
Subject: [ntpwg] Solicit comments for draft-wu-ntp-ntp-cfg-00
X-BeenThere: ntpwg@lists.ntp.org
X-Mailman-Version: 2.1.20
Precedence: list
List-Id: IETF Working Group for Network Time Protocol <ntpwg.lists.ntp.org>
List-Unsubscribe: <http://lists.ntp.org/options/ntpwg>, <mailto:ntpwg-request@lists.ntp.org?subject=unsubscribe>
List-Archive: <http://lists.ntp.org/pipermail/ntpwg/>
List-Post: <mailto:ntpwg@lists.ntp.org>
List-Help: <mailto:ntpwg-request@lists.ntp.org?subject=help>
List-Subscribe: <http://lists.ntp.org/listinfo/ntpwg>, <mailto:ntpwg-request@lists.ntp.org?subject=subscribe>
Cc: "draft-wu-ntp-ntp-cfg@tools.ietf.org" <draft-wu-ntp-ntp-cfg@tools.ietf.org>
Content-Type: multipart/mixed; boundary="===============6300184779859421616=="
Errors-To: ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org
Sender: "ntpwg" <ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org>

--===============6300184779859421616==
Content-Language: zh-CN
Content-Type: multipart/alternative;
	boundary="_000_0F26584357FD124DB93F1535E4B0A6505FBB743Fszxema508mbxchi_"

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

Hi Guys,

This draft tries to define YANG data model for NTP, which has been presente=
d in Dallas.
Co-authors wish to improve it and move forward if people from NTP-WG think =
this direction is interesting.
To do that, we are appreciated if you guys can comment on it and give some =
suggestion.
More important, we will be pleased if people who are interested can join us=
 to contribute together.

http://tools.ietf.org/html/draft-wu-ntp-ntp-cfg-00

Thanks.

Regards
Eric on behalf of co-authors

--_000_0F26584357FD124DB93F1535E4B0A6505FBB743Fszxema508mbxchi_
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=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 12 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:SimSun;
	panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
	{font-family:SimSun;
	panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:SimSun;
	panose-1:2 1 6 0 3 1 1 1 1 1;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	text-align:justify;
	text-justify:inter-ideograph;
	font-size:10.5pt;
	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;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Courier New";
	color:windowtext;
	font-weight:normal;
	font-style:normal;}
.MsoChpDefault
	{mso-style-type:export-only;}
/* Page Definitions */
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:72.0pt 90.0pt 72.0pt 90.0pt;}
div.WordSection1
	{page:WordSection1;}
--></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=3D"ZH-CN" link=3D"blue" vlink=3D"purple" style=3D"text-justify-t=
rim:punctuation">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-family:&quot;Cour=
ier New&quot;">Hi Guys,<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-family:&quot;Cour=
ier New&quot;"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-family:&quot;Cour=
ier New&quot;">This draft tries to define YANG data model for NTP, which ha=
s been presented in Dallas.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-family:&quot;Cour=
ier New&quot;">Co-authors wish to improve it and move forward if people fro=
m NTP-WG think this direction is interesting.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-family:&quot;Cour=
ier New&quot;">To do that, we are appreciated if you guys can comment on it=
 and give some suggestion.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-family:&quot;Cour=
ier New&quot;">More important, we will be pleased if people who are interes=
ted can join us to contribute together.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-family:&quot;Cour=
ier New&quot;"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><a href=3D"http://tools.ietf.or=
g/html/draft-wu-ntp-ntp-cfg-00">http://tools.ietf.org/html/draft-wu-ntp-ntp=
-cfg-00</a></span><span lang=3D"EN-US" style=3D"font-family:&quot;Courier N=
ew&quot;"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-family:&quot;Cour=
ier New&quot;"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-family:&quot;Cour=
ier New&quot;">Thanks.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-family:&quot;Cour=
ier New&quot;"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-family:&quot;Cour=
ier New&quot;">Regards<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-family:&quot;Cour=
ier New&quot;">Eric on behalf of co-authors<o:p></o:p></span></p>
</div>
</body>
</html>

--_000_0F26584357FD124DB93F1535E4B0A6505FBB743Fszxema508mbxchi_--

--===============6300184779859421616==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

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

From ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org  Wed Apr 22 02:45:56 2015
Return-Path: <ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org>
X-Original-To: ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com
Delivered-To: ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EE5CC1A88D8 for <ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com>; Wed, 22 Apr 2015 02:45:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level:
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 hyB1RhPzgPR2 for <ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com>; Wed, 22 Apr 2015 02:45:54 -0700 (PDT)
Received: from psp3.ntp.org (psp3.ntp.org [149.20.68.23]) by ietfa.amsl.com (Postfix) with ESMTP id 036BD1A1AAA for <ntp-archives-ahFae6za@lists.ietf.org>; Wed, 22 Apr 2015 02:45:54 -0700 (PDT)
Received: from psp3.ntp.org (localhost.ntp.org [127.0.0.1]) by psp3.ntp.org (Postfix) with ESMTP id 777FC39918 for <ntp-archives-ahFae6za@lists.ietf.org>; Wed, 22 Apr 2015 02:45:53 -0700 (PDT)
X-Original-To: ntpwg@lists.ntp.org
Delivered-To: ntpwg@lists.ntp.org
Received: from mail1.ntp.org (mail1.ntp.org [IPv6:2001:4f8:fff7:1::5]) by lists.ntp.org (Postfix) with ESMTP id B57FB86D55F for <ntpwg@lists.ntp.org>; Wed, 22 Apr 2015 09:45:49 +0000 (UTC)
Received: from [58.251.152.64] (helo=szxga01-in.huawei.com) by mail1.ntp.org with esmtps (TLSv1:RC4-SHA:128) (Exim 4.77 (FreeBSD)) (envelope-from <anil.sn@huawei.com>) id 1YkrDx-000Fsz-O9 for ntpwg@lists.ntp.org; Wed, 22 Apr 2015 09:45:49 +0000
Received: from 172.24.2.119 (EHLO nkgeml402-hub.china.huawei.com) ([172.24.2.119]) by szxrg01-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id CMM75083; Wed, 22 Apr 2015 17:43:53 +0800 (CST)
Received: from NKGEML512-MBX.china.huawei.com ([169.254.7.135]) by nkgeml402-hub.china.huawei.com ([10.98.56.33]) with mapi id 14.03.0158.001; Wed, 22 Apr 2015 17:43:46 +0800
From: "Anil Kumar S N (VRP Network BL)" <anil.sn@huawei.com>
To: Ulrich Windl <Ulrich.Windl@rz.uni-regensburg.de>, "fw@deneb.enyo.de" <fw@deneb.enyo.de>
Thread-Topic: Antw: Re: [ntpwg] [NTP Protocol] strengthening NTP control packets for diagnostic purpose
Thread-Index: AQHQfHg7s1XuMHWOFEe3sZkoACOK+J1YETaAgACx9/A=
Date: Wed, 22 Apr 2015 09:43:45 +0000
Message-ID: <327562D94EA7BF428CD805F338C31EF04FB38D5C@nkgeml512-mbx.china.huawei.com>
References: <327562D94EA7BF428CD805F338C31EF04FB38946@nkgeml512-mbx.china.huawei.com><327562D94EA7BF428CD805F338C31EF04FB38946@nkgeml512-mbx.china.huawei.com> (Anil Kumar S. N.'s message of "Mon, 20 Apr 2015 04:49:22 +0000") <87bnihyyko.fsf@mid.deneb.enyo.de> <55376003020000A100019F53@gwsmtp1.uni-regensburg.de>
In-Reply-To: <55376003020000A100019F53@gwsmtp1.uni-regensburg.de>
Accept-Language: en-US, zh-CN
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.18.212.150]
MIME-Version: 1.0
X-CFilter-Loop: Reflected
X-SA-Exim-Connect-IP: 58.251.152.64
X-SA-Exim-Rcpt-To: ntpwg@lists.ntp.org
X-SA-Exim-Mail-From: anil.sn@huawei.com
X-SA-Exim-Version: 4.2
X-SA-Exim-Scanned: Yes (on mail1.ntp.org)
Subject: Re: [ntpwg] Antw: Re: [NTP Protocol] strengthening NTP control packets for diagnostic purpose
X-BeenThere: ntpwg@lists.ntp.org
X-Mailman-Version: 2.1.20
Precedence: list
List-Id: IETF Working Group for Network Time Protocol <ntpwg.lists.ntp.org>
List-Unsubscribe: <http://lists.ntp.org/options/ntpwg>, <mailto:ntpwg-request@lists.ntp.org?subject=unsubscribe>
List-Archive: <http://lists.ntp.org/pipermail/ntpwg/>
List-Post: <mailto:ntpwg@lists.ntp.org>
List-Help: <mailto:ntpwg-request@lists.ntp.org?subject=help>
List-Subscribe: <http://lists.ntp.org/listinfo/ntpwg>, <mailto:ntpwg-request@lists.ntp.org?subject=subscribe>
Cc: "odonoghue@isoc.org" <odonoghue@isoc.org>, "ntpwg@lists.ntp.org" <ntpwg@lists.ntp.org>, Rajeshmv <rajeshmv@huawei.com>, kasturi chandradeep <kasturi.chandradeep@huawei.com>, Dhruv Dhody <dhruv.dhody@huawei.com>, Chirag shah <chirag.shah@huawei.com>, Kalyankumar Asangi <kalyana@huawei.com>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org
Sender: "ntpwg" <ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org>

Hi Windl,

	Please see my comments inline [Anil-1]


Thanks & Regards
Anil S N

"Be liberal in what you accept, and conservative in what you send" - Jon Postel



-----Original Message-----
From: Ulrich Windl [mailto:Ulrich.Windl@rz.uni-regensburg.de] 
Sent: 22 April 2015 12:17
To: fw@deneb.enyo.de; Anil Kumar S N (VRP Network BL)
Cc: Chirag shah; Dhruv Dhody; Kalyankumar Asangi; kasturi chandradeep; Rajeshmv; odonoghue@isoc.org; ntpwg@lists.ntp.org
Subject: Antw: Re: [ntpwg] [NTP Protocol] strengthening NTP control packets for diagnostic purpose

>>> Florian Weimer <fw@deneb.enyo.de> schrieb am 21.04.2015 um 23:13 in 
>>> Nachricht
<87bnihyyko.fsf@mid.deneb.enyo.de>:
> * Anil Kumar S. N.:
> 
>> There are two options
>>
>> 1.       NTP dynamic runtime diagnostic tools can be implemented using NTP 
> extensions using protocol packets
>>
>> 2.       Strengthen NTP control packets with new options to achieve the 
> same. [Preferred]
> 
> I seriously suggest to consider moving diagnostics and other form of 
> management out of band (say SNMP, CIM or PCP, basically anything else 
> that does not run over port 123/UDP), so that these interfaces are not 
> constrained by the NTP technical framework regarding authentication, 
> authorization, confidentiality, and integrity protection.

Well, SNMP, CIM and PCP (Performance Co-Pilot?) all may be more standard, but they all have some extra protocol (and library) overhead. And I think confidentiality and integrity are also issues when monitoring or controlling NTP. So I don't see why you want to have it out-band (unless you simply want to get rid of it).

Modeling NTP in SNMP may be an interesting exercise (consuming many hours), but may end up in a moster that only few people want to deal with. I don't like framework monsters feeding each other...
Regards,
Ulrich


[Anil-1] : I think current IETF standards for managing NTP are NTP MIB (SNMP based) and Yang model. These are the protocols who's reach is confined to a service provider due to authentication issues. Many operators have defined their own private MIB to access information and configure NTP. Confidentiality is not required for NTP but integrity of the NTP content yes it is required, As of now its optional we can think of making it mandatory for control packets.  

Usually cases are like in service provider network they will have a NTP client connected to a different NTP server which belongs to different service provider; from which all other devices in that service provider network will get their time synchronized. If the server is faulty, diagnostic purpose we need to query behavior of the server at that particular time. Only with control packets we will be able to get the information of the NTP server which belongs to different service provider

NTP control packets exist for NTPv3, do you want to get rid of it :)  Think about it, there were very good reasons for introducing it.
I can see Linux exhaustively exploits NTP query functionality, One very good utility is People have written scripts to perform NTP trace. 
Let's take what's good in current design of control packets and address the shortcomings.



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




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

From ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org  Wed Apr 22 04:10:28 2015
Return-Path: <ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org>
X-Original-To: ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com
Delivered-To: ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 43B0B1B345F for <ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com>; Wed, 22 Apr 2015 04:10:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level:
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 wMHOlhdFPEVB for <ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com>; Wed, 22 Apr 2015 04:10:19 -0700 (PDT)
Received: from psp3.ntp.org (psp3.ntp.org [149.20.68.23]) by ietfa.amsl.com (Postfix) with ESMTP id AE6831B345D for <ntp-archives-ahFae6za@lists.ietf.org>; Wed, 22 Apr 2015 04:10:19 -0700 (PDT)
Received: from psp3.ntp.org (localhost.ntp.org [127.0.0.1]) by psp3.ntp.org (Postfix) with ESMTP id 68B4839918 for <ntp-archives-ahFae6za@lists.ietf.org>; Wed, 22 Apr 2015 04:10:19 -0700 (PDT)
X-Original-To: ntpwg@lists.ntp.org
Delivered-To: ntpwg@lists.ntp.org
Received: from mail1.ntp.org (mail1.ntp.org [IPv6:2001:4f8:fff7:1::5]) by lists.ntp.org (Postfix) with ESMTP id D367E86D55F for <ntpwg@lists.ntp.org>; Wed, 22 Apr 2015 11:10:16 +0000 (UTC)
Received: from rrzmta1.uni-regensburg.de ([194.94.155.51]) by mail1.ntp.org with esmtps (TLSv1:CAMELLIA256-SHA:256) (Exim 4.77 (FreeBSD)) (envelope-from <Ulrich.Windl@rz.uni-regensburg.de>) id 1YksXf-000MVM-SP for ntpwg@lists.ntp.org; Wed, 22 Apr 2015 11:10:16 +0000
Received: from rrzmta1.uni-regensburg.de (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id 9C2324EA4F for <ntpwg@lists.ntp.org>; Wed, 22 Apr 2015 13:08:50 +0200 (CEST)
Received: from gwsmtp1.uni-regensburg.de (gwsmtp1.uni-regensburg.de [132.199.5.51]) by rrzmta1.uni-regensburg.de (Postfix) with ESMTP id 8752F4556C for <ntpwg@lists.ntp.org>; Wed, 22 Apr 2015 13:08:49 +0200 (CEST)
Received: from uni-regensburg-smtp1-MTA by gwsmtp1.uni-regensburg.de with Novell_GroupWise; Wed, 22 Apr 2015 13:08:49 +0200
Message-Id: <55379D5F020000A100019F64@gwsmtp1.uni-regensburg.de>
X-Mailer: Novell GroupWise Internet Agent 14.0.1 
Date: Wed, 22 Apr 2015 13:08:47 +0200
From: "Ulrich Windl" <Ulrich.Windl@rz.uni-regensburg.de>
To: <fw@deneb.enyo.de>,<anil.sn@huawei.com>
References: <327562D94EA7BF428CD805F338C31EF04FB38946@nkgeml512-mbx.china.huawei.com><327562D94EA7BF428CD805F338C31EF04FB38946@nkgeml512-mbx.china.huawei.com> (Anil Kumar S. N.'s message of "Mon, 20 Apr 2015 04:49:22 +0000") <87bnihyyko.fsf@mid.deneb.enyo.de> <55376003020000A100019F53@gwsmtp1.uni-regensburg.de> <327562D94EA7BF428CD805F338C31EF04FB38D5C@nkgeml512-mbx.china.huawei.com>
In-Reply-To: <327562D94EA7BF428CD805F338C31EF04FB38D5C@nkgeml512-mbx.china.huawei.com>
Mime-Version: 1.0
Content-Disposition: inline
X-SA-Exim-Connect-IP: 194.94.155.51
X-SA-Exim-Rcpt-To: ntpwg@lists.ntp.org
X-SA-Exim-Mail-From: Ulrich.Windl@rz.uni-regensburg.de
X-SA-Exim-Version: 4.2
X-SA-Exim-Scanned: Yes (on mail1.ntp.org)
Subject: Re: [ntpwg] Antw: Re: [NTP Protocol] strengthening NTP control packets for diagnostic purpose
X-BeenThere: ntpwg@lists.ntp.org
X-Mailman-Version: 2.1.20
Precedence: list
List-Id: IETF Working Group for Network Time Protocol <ntpwg.lists.ntp.org>
List-Unsubscribe: <http://lists.ntp.org/options/ntpwg>, <mailto:ntpwg-request@lists.ntp.org?subject=unsubscribe>
List-Archive: <http://lists.ntp.org/pipermail/ntpwg/>
List-Post: <mailto:ntpwg@lists.ntp.org>
List-Help: <mailto:ntpwg-request@lists.ntp.org?subject=help>
List-Subscribe: <http://lists.ntp.org/listinfo/ntpwg>, <mailto:ntpwg-request@lists.ntp.org?subject=subscribe>
Cc: odonoghue@isoc.org, ntpwg@lists.ntp.org, rajeshmv@huawei.com, kasturi.chandradeep@huawei.com, dhruv.dhody@huawei.com, chirag.shah@huawei.com, kalyana@huawei.com
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org
Sender: "ntpwg" <ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org>

Hello!

I mostly agee except "(...)Confidentiality is not required for NTP(...)": Assume some configuration data is not publicly available. If someone who is allowed to access that configuration data over the net with proper authentication, these data will appear on the net (without confidentiality). You don't make them public, but you may disclose it these days...

That's what I thought.

Regards,
Ulrich


>>> "Anil Kumar S N (VRP Network BL)" <anil.sn@huawei.com> schrieb am 22.04.2015 um
11:43 in Nachricht
<327562D94EA7BF428CD805F338C31EF04FB38D5C@nkgeml512-mbx.china.huawei.com>:
> Hi Windl,
> 
> 	Please see my comments inline [Anil-1]
> 
> 
> Thanks & Regards
> Anil S N
> 
> "Be liberal in what you accept, and conservative in what you send" - Jon 
> Postel
> 
> 
> 
> -----Original Message-----
> From: Ulrich Windl [mailto:Ulrich.Windl@rz.uni-regensburg.de] 
> Sent: 22 April 2015 12:17
> To: fw@deneb.enyo.de; Anil Kumar S N (VRP Network BL)
> Cc: Chirag shah; Dhruv Dhody; Kalyankumar Asangi; kasturi chandradeep; 
> Rajeshmv; odonoghue@isoc.org; ntpwg@lists.ntp.org 
> Subject: Antw: Re: [ntpwg] [NTP Protocol] strengthening NTP control packets 
> for diagnostic purpose
> 
>>>> Florian Weimer <fw@deneb.enyo.de> schrieb am 21.04.2015 um 23:13 in 
>>>> Nachricht
> <87bnihyyko.fsf@mid.deneb.enyo.de>:
>> * Anil Kumar S. N.:
>> 
>>> There are two options
>>>
>>> 1.       NTP dynamic runtime diagnostic tools can be implemented using NTP 
>> extensions using protocol packets
>>>
>>> 2.       Strengthen NTP control packets with new options to achieve the 
>> same. [Preferred]
>> 
>> I seriously suggest to consider moving diagnostics and other form of 
>> management out of band (say SNMP, CIM or PCP, basically anything else 
>> that does not run over port 123/UDP), so that these interfaces are not 
>> constrained by the NTP technical framework regarding authentication, 
>> authorization, confidentiality, and integrity protection.
> 
> Well, SNMP, CIM and PCP (Performance Co-Pilot?) all may be more standard, but 
> they all have some extra protocol (and library) overhead. And I think 
> confidentiality and integrity are also issues when monitoring or controlling 
> NTP. So I don't see why you want to have it out-band (unless you simply want 
> to get rid of it).
> 
> Modeling NTP in SNMP may be an interesting exercise (consuming many hours), 
> but may end up in a moster that only few people want to deal with. I don't 
> like framework monsters feeding each other...
> Regards,
> Ulrich
> 
> 
> [Anil-1] : I think current IETF standards for managing NTP are NTP MIB (SNMP 
> based) and Yang model. These are the protocols who's reach is confined to a 
> service provider due to authentication issues. Many operators have defined 
> their own private MIB to access information and configure NTP. 
> Confidentiality is not required for NTP but integrity of the NTP content yes 
> it is required, As of now its optional we can think of making it mandatory 
> for control packets.  
> 
> Usually cases are like in service provider network they will have a NTP 
> client connected to a different NTP server which belongs to different service 
> provider; from which all other devices in that service provider network will 
> get their time synchronized. If the server is faulty, diagnostic purpose we 
> need to query behavior of the server at that particular time. Only with 
> control packets we will be able to get the information of the NTP server 
> which belongs to different service provider
> 
> NTP control packets exist for NTPv3, do you want to get rid of it :)  Think 
> about it, there were very good reasons for introducing it.
> I can see Linux exhaustively exploits NTP query functionality, One very good 
> utility is People have written scripts to perform NTP trace. 
> Let's take what's good in current design of control packets and address the 
> shortcomings.
> 
> 
> 
>> _______________________________________________
>> ntpwg mailing list
>> ntpwg@lists.ntp.org 
>> http://lists.ntp.org/listinfo/ntpwg 



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

From ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org  Wed Apr 22 04:59:13 2015
Return-Path: <ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org>
X-Original-To: ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com
Delivered-To: ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 656571B34F6 for <ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com>; Wed, 22 Apr 2015 04:59:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level:
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 SUU2wFwoV472 for <ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com>; Wed, 22 Apr 2015 04:59:11 -0700 (PDT)
Received: from psp3.ntp.org (psp3.ntp.org [149.20.68.23]) by ietfa.amsl.com (Postfix) with ESMTP id 9E2A51B34F4 for <ntp-archives-ahFae6za@lists.ietf.org>; Wed, 22 Apr 2015 04:59:11 -0700 (PDT)
Received: from psp3.ntp.org (localhost.ntp.org [127.0.0.1]) by psp3.ntp.org (Postfix) with ESMTP id 5C1D939919 for <ntp-archives-ahFae6za@lists.ietf.org>; Wed, 22 Apr 2015 04:59:11 -0700 (PDT)
X-Original-To: ntpwg@lists.ntp.org
Delivered-To: ntpwg@lists.ntp.org
Received: from mail1.ntp.org (mail1.ntp.org [IPv6:2001:4f8:fff7:1::5]) by lists.ntp.org (Postfix) with ESMTP id 5DB9C86D55F for <ntpwg@lists.ntp.org>; Wed, 22 Apr 2015 11:59:08 +0000 (UTC)
Received: from albireo.enyo.de ([46.237.207.196]) by mail1.ntp.org with esmtps (TLSv1:AES128-SHA:128) (Exim 4.77 (FreeBSD)) (envelope-from <fw@deneb.enyo.de>) id 1YktIx-000O5z-04 for ntpwg@lists.ntp.org; Wed, 22 Apr 2015 11:59:08 +0000
Received: from [172.17.203.2] (helo=deneb.enyo.de) by albireo.enyo.de with esmtps (TLS1.2:DHE_RSA_AES_128_CBC_SHA1:128) id 1YktHd-0003Rp-77; Wed, 22 Apr 2015 13:57:37 +0200
Received: from fw by deneb.enyo.de with local (Exim 4.80) (envelope-from <fw@deneb.enyo.de>) id 1YktHc-0006Kl-VQ; Wed, 22 Apr 2015 13:57:36 +0200
From: Florian Weimer <fw@deneb.enyo.de>
To: "Ulrich Windl" <Ulrich.Windl@rz.uni-regensburg.de>
References: <327562D94EA7BF428CD805F338C31EF04FB38946@nkgeml512-mbx.china.huawei.com> <327562D94EA7BF428CD805F338C31EF04FB38946@nkgeml512-mbx.china.huawei.com> <87bnihyyko.fsf@mid.deneb.enyo.de> <55376003020000A100019F53@gwsmtp1.uni-regensburg.de> <327562D94EA7BF428CD805F338C31EF04FB38D5C@nkgeml512-mbx.china.huawei.com> <55379D5F020000A100019F64@gwsmtp1.uni-regensburg.de>
Date: Wed, 22 Apr 2015 13:57:36 +0200
In-Reply-To: <55379D5F020000A100019F64@gwsmtp1.uni-regensburg.de> (Ulrich Windl's message of "Wed, 22 Apr 2015 13:08:47 +0200")
Message-ID: <877ft474un.fsf@mid.deneb.enyo.de>
MIME-Version: 1.0
X-SA-Exim-Connect-IP: 46.237.207.196
X-SA-Exim-Rcpt-To: ntpwg@lists.ntp.org
X-SA-Exim-Mail-From: fw@deneb.enyo.de
X-SA-Exim-Version: 4.2
X-SA-Exim-Scanned: Yes (on mail1.ntp.org)
Subject: Re: [ntpwg] Antw: Re: [NTP Protocol] strengthening NTP control packets for diagnostic purpose
X-BeenThere: ntpwg@lists.ntp.org
X-Mailman-Version: 2.1.20
Precedence: list
List-Id: IETF Working Group for Network Time Protocol <ntpwg.lists.ntp.org>
List-Unsubscribe: <http://lists.ntp.org/options/ntpwg>, <mailto:ntpwg-request@lists.ntp.org?subject=unsubscribe>
List-Archive: <http://lists.ntp.org/pipermail/ntpwg/>
List-Post: <mailto:ntpwg@lists.ntp.org>
List-Help: <mailto:ntpwg-request@lists.ntp.org?subject=help>
List-Subscribe: <http://lists.ntp.org/listinfo/ntpwg>, <mailto:ntpwg-request@lists.ntp.org?subject=subscribe>
Cc: odonoghue@isoc.org, rajeshmv@huawei.com, ntpwg@lists.ntp.org, kasturi.chandradeep@huawei.com, dhruv.dhody@huawei.com, chirag.shah@huawei.com, kalyana@huawei.com
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org
Sender: "ntpwg" <ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org>

* Ulrich Windl:

> I mostly agee except "(...)Confidentiality is not required for
> NTP(...)": Assume some configuration data is not publicly
> available. If someone who is allowed to access that configuration
> data over the net with proper authentication, these data will appear
> on the net (without confidentiality). You don't make them public,
> but you may disclose it these days...

It's also needed when the monitoring discloses information about
clients in some way (which would be pretty reasonable for load
monitoring, I assume).
_______________________________________________
ntpwg mailing list
ntpwg@lists.ntp.org
http://lists.ntp.org/listinfo/ntpwg

From ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org  Wed Apr 22 05:10:45 2015
Return-Path: <ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org>
X-Original-To: ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com
Delivered-To: ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 110F61B34F0 for <ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com>; Wed, 22 Apr 2015 05:10:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level:
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 9UnETYMBqqTc for <ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com>; Wed, 22 Apr 2015 05:10:42 -0700 (PDT)
Received: from psp3.ntp.org (psp3.ntp.org [149.20.68.23]) by ietfa.amsl.com (Postfix) with ESMTP id D5D761AC402 for <ntp-archives-ahFae6za@lists.ietf.org>; Wed, 22 Apr 2015 05:10:42 -0700 (PDT)
Received: from psp3.ntp.org (localhost.ntp.org [127.0.0.1]) by psp3.ntp.org (Postfix) with ESMTP id C25E83991A for <ntp-archives-ahFae6za@lists.ietf.org>; Wed, 22 Apr 2015 05:10:42 -0700 (PDT)
X-Original-To: ntpwg@lists.ntp.org
Delivered-To: ntpwg@lists.ntp.org
Received: from mail1.ntp.org (mail1.ntp.org [IPv6:2001:4f8:fff7:1::5]) by lists.ntp.org (Postfix) with ESMTP id B019086D55F for <ntpwg@lists.ntp.org>; Wed, 22 Apr 2015 12:10:39 +0000 (UTC)
Received: from szxga03-in.huawei.com ([119.145.14.66]) by mail1.ntp.org with esmtps (TLSv1:RC4-SHA:128) (Exim 4.77 (FreeBSD)) (envelope-from <anil.sn@huawei.com>) id 1YktU7-000OTa-GN for ntpwg@lists.ntp.org; Wed, 22 Apr 2015 12:10:39 +0000
Received: from 172.24.2.119 (EHLO nkgeml407-hub.china.huawei.com) ([172.24.2.119]) by szxrg03-dlp.huawei.com (MOS 4.4.3-GA FastPath queued) with ESMTP id BEW27891; Wed, 22 Apr 2015 20:08:42 +0800 (CST)
Received: from NKGEML512-MBX.china.huawei.com ([169.254.7.135]) by nkgeml407-hub.china.huawei.com ([10.98.56.38]) with mapi id 14.03.0158.001; Wed, 22 Apr 2015 20:08:34 +0800
From: "Anil Kumar S N (VRP Network BL)" <anil.sn@huawei.com>
To: Ulrich Windl <Ulrich.Windl@rz.uni-regensburg.de>, "fw@deneb.enyo.de" <fw@deneb.enyo.de>
Thread-Topic: Antw: Re: [ntpwg] [NTP Protocol] strengthening NTP control packets for diagnostic purpose
Thread-Index: AQHQfHg7s1XuMHWOFEe3sZkoACOK+J1YETaAgACx9/D//5cugIAAlinA
Date: Wed, 22 Apr 2015 12:08:33 +0000
Message-ID: <327562D94EA7BF428CD805F338C31EF04FB38E0F@nkgeml512-mbx.china.huawei.com>
References: <327562D94EA7BF428CD805F338C31EF04FB38946@nkgeml512-mbx.china.huawei.com><327562D94EA7BF428CD805F338C31EF04FB38946@nkgeml512-mbx.china.huawei.com> (Anil Kumar S. N.'s message of "Mon, 20 Apr 2015 04:49:22 +0000") <87bnihyyko.fsf@mid.deneb.enyo.de> <55376003020000A100019F53@gwsmtp1.uni-regensburg.de> <327562D94EA7BF428CD805F338C31EF04FB38D5C@nkgeml512-mbx.china.huawei.com> <55379D5F020000A100019F64@gwsmtp1.uni-regensburg.de>
In-Reply-To: <55379D5F020000A100019F64@gwsmtp1.uni-regensburg.de>
Accept-Language: en-US, zh-CN
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.18.212.150]
MIME-Version: 1.0
X-CFilter-Loop: Reflected
X-Mirapoint-Virus-RAPID-Raw: score=unknown(0), refid=str=0001.0A020202.55378F4A.035F, ss=1, re=0.000, recu=0.000, reip=0.000, cl=1, cld=1, fgs=0, ip=169.254.7.135, so=2013-05-26 15:14:31, dmn=2013-03-21 17:37:32
X-Mirapoint-Loop-Id: 91dd3f6b2cb7bad9bd661ff998b0d79d
X-SA-Exim-Connect-IP: 119.145.14.66
X-SA-Exim-Rcpt-To: ntpwg@lists.ntp.org
X-SA-Exim-Mail-From: anil.sn@huawei.com
X-SA-Exim-Version: 4.2
X-SA-Exim-Scanned: Yes (on mail1.ntp.org)
Subject: Re: [ntpwg] Antw: Re: [NTP Protocol] strengthening NTP control packets for diagnostic purpose
X-BeenThere: ntpwg@lists.ntp.org
X-Mailman-Version: 2.1.20
Precedence: list
List-Id: IETF Working Group for Network Time Protocol <ntpwg.lists.ntp.org>
List-Unsubscribe: <http://lists.ntp.org/options/ntpwg>, <mailto:ntpwg-request@lists.ntp.org?subject=unsubscribe>
List-Archive: <http://lists.ntp.org/pipermail/ntpwg/>
List-Post: <mailto:ntpwg@lists.ntp.org>
List-Help: <mailto:ntpwg-request@lists.ntp.org?subject=help>
List-Subscribe: <http://lists.ntp.org/listinfo/ntpwg>, <mailto:ntpwg-request@lists.ntp.org?subject=subscribe>
Cc: "odonoghue@isoc.org" <odonoghue@isoc.org>, "ntpwg@lists.ntp.org" <ntpwg@lists.ntp.org>, Rajeshmv <rajeshmv@huawei.com>, kasturi chandradeep <kasturi.chandradeep@huawei.com>, Dhruv Dhody <dhruv.dhody@huawei.com>, Chirag shah <chirag.shah@huawei.com>, Kalyankumar Asangi <kalyana@huawei.com>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org
Sender: "ntpwg" <ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org>

Hi,

	In NTP you are talking about Authentication key and password ?, Anyways that should not be in the scope of control packets.	
	What else you are expecting to be kept confidential ? Do you have anything specific in mind?

Thanks & Regards
Anil S N

"Be liberal in what you accept, and conservative in what you send" - Jon Postel



-----Original Message-----
From: Ulrich Windl [mailto:Ulrich.Windl@rz.uni-regensburg.de] 
Sent: 22 April 2015 19:09
To: fw@deneb.enyo.de; Anil Kumar S N (VRP Network BL)
Cc: Chirag shah; Dhruv Dhody; Kalyankumar Asangi; kasturi chandradeep; Rajeshmv; odonoghue@isoc.org; ntpwg@lists.ntp.org
Subject: RE: Antw: Re: [ntpwg] [NTP Protocol] strengthening NTP control packets for diagnostic purpose

Hello!

I mostly agee except "(...)Confidentiality is not required for NTP(...)": Assume some configuration data is not publicly available. If someone who is allowed to access that configuration data over the net with proper authentication, these data will appear on the net (without confidentiality). You don't make them public, but you may disclose it these days...

That's what I thought.

Regards,
Ulrich


>>> "Anil Kumar S N (VRP Network BL)" <anil.sn@huawei.com> schrieb am 
>>> 22.04.2015 um
11:43 in Nachricht
<327562D94EA7BF428CD805F338C31EF04FB38D5C@nkgeml512-mbx.china.huawei.com>:
> Hi Windl,
> 
> 	Please see my comments inline [Anil-1]
> 
> 
> Thanks & Regards
> Anil S N
> 
> "Be liberal in what you accept, and conservative in what you send" - 
> Jon Postel
> 
> 
> 
> -----Original Message-----
> From: Ulrich Windl [mailto:Ulrich.Windl@rz.uni-regensburg.de]
> Sent: 22 April 2015 12:17
> To: fw@deneb.enyo.de; Anil Kumar S N (VRP Network BL)
> Cc: Chirag shah; Dhruv Dhody; Kalyankumar Asangi; kasturi chandradeep; 
> Rajeshmv; odonoghue@isoc.org; ntpwg@lists.ntp.org
> Subject: Antw: Re: [ntpwg] [NTP Protocol] strengthening NTP control 
> packets for diagnostic purpose
> 
>>>> Florian Weimer <fw@deneb.enyo.de> schrieb am 21.04.2015 um 23:13 in 
>>>> Nachricht
> <87bnihyyko.fsf@mid.deneb.enyo.de>:
>> * Anil Kumar S. N.:
>> 
>>> There are two options
>>>
>>> 1.       NTP dynamic runtime diagnostic tools can be implemented using NTP 
>> extensions using protocol packets
>>>
>>> 2.       Strengthen NTP control packets with new options to achieve the 
>> same. [Preferred]
>> 
>> I seriously suggest to consider moving diagnostics and other form of 
>> management out of band (say SNMP, CIM or PCP, basically anything else 
>> that does not run over port 123/UDP), so that these interfaces are 
>> not constrained by the NTP technical framework regarding 
>> authentication, authorization, confidentiality, and integrity protection.
> 
> Well, SNMP, CIM and PCP (Performance Co-Pilot?) all may be more 
> standard, but they all have some extra protocol (and library) 
> overhead. And I think confidentiality and integrity are also issues 
> when monitoring or controlling NTP. So I don't see why you want to 
> have it out-band (unless you simply want to get rid of it).
> 
> Modeling NTP in SNMP may be an interesting exercise (consuming many 
> hours), but may end up in a moster that only few people want to deal 
> with. I don't like framework monsters feeding each other...
> Regards,
> Ulrich
> 
> 
> [Anil-1] : I think current IETF standards for managing NTP are NTP MIB 
> (SNMP
> based) and Yang model. These are the protocols who's reach is confined 
> to a service provider due to authentication issues. Many operators 
> have defined their own private MIB to access information and configure NTP.
> Confidentiality is not required for NTP but integrity of the NTP 
> content yes it is required, As of now its optional we can think of 
> making it mandatory for control packets.
> 
> Usually cases are like in service provider network they will have a 
> NTP client connected to a different NTP server which belongs to 
> different service provider; from which all other devices in that 
> service provider network will get their time synchronized. If the 
> server is faulty, diagnostic purpose we need to query behavior of the 
> server at that particular time. Only with control packets we will be 
> able to get the information of the NTP server which belongs to 
> different service provider
> 
> NTP control packets exist for NTPv3, do you want to get rid of it :)  
> Think about it, there were very good reasons for introducing it.
> I can see Linux exhaustively exploits NTP query functionality, One 
> very good utility is People have written scripts to perform NTP trace.
> Let's take what's good in current design of control packets and 
> address the shortcomings.
> 
> 
> 
>> _______________________________________________
>> ntpwg mailing list
>> ntpwg@lists.ntp.org
>> http://lists.ntp.org/listinfo/ntpwg



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

From ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org  Wed Apr 22 18:50:01 2015
Return-Path: <ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org>
X-Original-To: ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com
Delivered-To: ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CB40F1B2D29 for <ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com>; Wed, 22 Apr 2015 18:50:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.481
X-Spam-Level:
X-Spam-Status: No, score=-1.481 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, MIME_HTML_MOSTLY=0.428, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 G1BFbazsB1y4 for <ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com>; Wed, 22 Apr 2015 18:49:57 -0700 (PDT)
Received: from psp3.ntp.org (psp3.ntp.org [149.20.68.23]) by ietfa.amsl.com (Postfix) with ESMTP id 533521B2D31 for <ntp-archives-ahFae6za@lists.ietf.org>; Wed, 22 Apr 2015 18:49:57 -0700 (PDT)
Received: from psp3.ntp.org (localhost.ntp.org [127.0.0.1]) by psp3.ntp.org (Postfix) with ESMTP id 3372839919 for <ntp-archives-ahFae6za@lists.ietf.org>; Wed, 22 Apr 2015 18:49:57 -0700 (PDT)
X-Original-To: ntpwg@lists.ntp.org
Delivered-To: ntpwg@lists.ntp.org
Received: from mail1.ntp.org (mail1.ntp.org [IPv6:2001:4f8:fff7:1::5]) by lists.ntp.org (Postfix) with ESMTP id 0DE8E86D55F for <ntpwg@lists.ntp.org>; Wed, 22 Apr 2015 14:04:33 +0000 (UTC)
Received: from [58.251.152.64] (helo=szxga01-in.huawei.com) by mail1.ntp.org with esmtps (TLSv1:RC4-SHA:128) (Exim 4.77 (FreeBSD)) (envelope-from <anil.sn@huawei.com>) id 1YkvGI-0001zi-EU for ntpwg@lists.ntp.org; Wed, 22 Apr 2015 14:04:33 +0000
Received: from 172.24.2.119 (EHLO nkgeml408-hub.china.huawei.com) ([172.24.2.119]) by szxrg01-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id CMM99265; Wed, 22 Apr 2015 22:02:30 +0800 (CST)
Received: from NKGEML512-MBX.china.huawei.com ([169.254.7.135]) by nkgeml408-hub.china.huawei.com ([10.98.56.39]) with mapi id 14.03.0158.001; Wed, 22 Apr 2015 22:02:22 +0800
From: "Anil Kumar S N (VRP Network BL)" <anil.sn@huawei.com>
To: Greg Dowd <Greg.Dowd@microsemi.com>
Thread-Topic: [ntpwg] Antw: Re: [NTP Protocol] strengthening NTP control packets for diagnostic purpose
Thread-Index: AQHQfQR1eYXjID+rmEKoMjEgTSdCw51ZDxOw
Date: Wed, 22 Apr 2015 14:02:21 +0000
Message-ID: <327562D94EA7BF428CD805F338C31EF04FB38E63@nkgeml512-mbx.china.huawei.com>
References: <327562D94EA7BF428CD805F338C31EF04FB38946@nkgeml512-mbx.china.huawei.com><327562D94EA7BF428CD805F338C31EF04FB38946@nkgeml512-mbx.china.huawei.com> (Anil Kumar S. N.'s message of "Mon, 20 Apr 2015 04:49:22 +0000") <87bnihyyko.fsf@mid.deneb.enyo.de> <55376003020000A100019F53@gwsmtp1.uni-regensburg.de> <327562D94EA7BF428CD805F338C31EF04FB38D5C@nkgeml512-mbx.china.huawei.com> <55379D5F020000A100019F64@gwsmtp1.uni-regensburg.de>, <327562D94EA7BF428CD805F338C31EF04FB38E0F@nkgeml512-mbx.china.huawei.com> <8D2BF679AAC7C346848A489074F9F8BF3DF2EA6E@sjsrvexchmbx2.microsemi.net>
In-Reply-To: <8D2BF679AAC7C346848A489074F9F8BF3DF2EA6E@sjsrvexchmbx2.microsemi.net>
Accept-Language: en-US, zh-CN
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.18.212.150]
MIME-Version: 1.0
X-CFilter-Loop: Reflected
X-SA-Exim-Connect-IP: 58.251.152.64
X-SA-Exim-Rcpt-To: ntpwg@lists.ntp.org
X-SA-Exim-Mail-From: anil.sn@huawei.com
X-SA-Exim-Version: 4.2
X-SA-Exim-Scanned: Yes (on mail1.ntp.org)
X-Mailman-Approved-At: Thu, 23 Apr 2015 01:49:53 +0000
Subject: Re: [ntpwg] Antw: Re: [NTP Protocol] strengthening NTP control packets for diagnostic purpose
X-BeenThere: ntpwg@lists.ntp.org
X-Mailman-Version: 2.1.20
Precedence: list
List-Id: IETF Working Group for Network Time Protocol <ntpwg.lists.ntp.org>
List-Unsubscribe: <http://lists.ntp.org/options/ntpwg>, <mailto:ntpwg-request@lists.ntp.org?subject=unsubscribe>
List-Archive: <http://lists.ntp.org/pipermail/ntpwg/>
List-Post: <mailto:ntpwg@lists.ntp.org>
List-Help: <mailto:ntpwg-request@lists.ntp.org?subject=help>
List-Subscribe: <http://lists.ntp.org/listinfo/ntpwg>, <mailto:ntpwg-request@lists.ntp.org?subject=subscribe>
Cc: "odonoghue@isoc.org" <odonoghue@isoc.org>, "ntpwg@lists.ntp.org" <ntpwg@lists.ntp.org>, kasturi chandradeep <kasturi.chandradeep@huawei.com>, Rajeshmv <rajeshmv@huawei.com>, Dhruv Dhody <dhruv.dhody@huawei.com>, Chirag shah <chirag.shah@huawei.com>, Kalyankumar Asangi <kalyana@huawei.com>
Content-Type: multipart/mixed; boundary="===============5666670701745279356=="
Errors-To: ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org
Sender: "ntpwg" <ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org>

--===============5666670701745279356==
Content-Language: en-US
Content-Type: multipart/alternative;
	boundary="_000_327562D94EA7BF428CD805F338C31EF04FB38E63nkgeml512mbxchi_"

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

Hi Dowd,

                Do you expect White List in control packets, I feel anythin=
g confidential should not be part of NTP control packets.
                For Sensitive data such as Authentication Password and Whit=
e/Black List  Configuration or access should be done using Management proto=
col which support confidentiality (Owned and controlled by service provider=
 for their devices)

Thanks & Regards
Anil S N

"Be liberal in what you accept, and conservative in what you send" - Jon Po=
stel


From: Greg Dowd [mailto:Greg.Dowd@microsemi.com]
Sent: 22 April 2015 19:28
To: Anil Kumar S N (VRP Network BL)
Cc: fw@deneb.enyo.de; Ulrich Windl; Kalyankumar Asangi; Dhruv Dhody; kastur=
i chandradeep; ntpwg@lists.ntp.org; Rajeshmv; Chirag shah; odonoghue@isoc.o=
rg
Subject: Re: [ntpwg] Antw: Re: [NTP Protocol] strengthening NTP control pac=
kets for diagnostic purpose


I could see the white list restrict entries as confidential for example.
On Apr 22, 2015 5:10 AM, "Anil Kumar S N (VRP Network BL)" <anil.sn@huawei.=
com<mailto:anil.sn@huawei.com>> wrote:
Hi,

        In NTP you are talking about Authentication key and password ?, Any=
ways that should not be in the scope of control packets.
        What else you are expecting to be kept confidential ? Do you have a=
nything specific in mind?

Thanks & Regards
Anil S N

"Be liberal in what you accept, and conservative in what you send" - Jon Po=
stel



-----Original Message-----
From: Ulrich Windl [mailto:Ulrich.Windl@rz.uni-regensburg.de]
Sent: 22 April 2015 19:09
To: fw@deneb.enyo.de<mailto:fw@deneb.enyo.de>; Anil Kumar S N (VRP Network =
BL)
Cc: Chirag shah; Dhruv Dhody; Kalyankumar Asangi; kasturi chandradeep; Raje=
shmv; odonoghue@isoc.org<mailto:odonoghue@isoc.org>; ntpwg@lists.ntp.org<ma=
ilto:ntpwg@lists.ntp.org>
Subject: RE: Antw: Re: [ntpwg] [NTP Protocol] strengthening NTP control pac=
kets for diagnostic purpose

Hello!

I mostly agee except "(...)Confidentiality is not required for NTP(...)": A=
ssume some configuration data is not publicly available. If someone who is =
allowed to access that configuration data over the net with proper authenti=
cation, these data will appear on the net (without confidentiality). You do=
n't make them public, but you may disclose it these days...

That's what I thought.

Regards,
Ulrich


>>> "Anil Kumar S N (VRP Network BL)" <anil.sn@huawei.com<mailto:anil.sn@hu=
awei.com>> schrieb am
>>> 22.04.2015 um
11:43 in Nachricht
<327562D94EA7BF428CD805F338C31EF04FB38D5C@nkgeml512-mbx.china.huawei.com<ma=
ilto:327562D94EA7BF428CD805F338C31EF04FB38D5C@nkgeml512-mbx.china.huawei.co=
m>>:
> Hi Windl,
>
>        Please see my comments inline [Anil-1]
>
>
> Thanks & Regards
> Anil S N
>
> "Be liberal in what you accept, and conservative in what you send" -
> Jon Postel
>
>
>
> -----Original Message-----
> From: Ulrich Windl [mailto:Ulrich.Windl@rz.uni-regensburg.de]
> Sent: 22 April 2015 12:17
> To: fw@deneb.enyo.de<mailto:fw@deneb.enyo.de>; Anil Kumar S N (VRP Networ=
k BL)
> Cc: Chirag shah; Dhruv Dhody; Kalyankumar Asangi; kasturi chandradeep;
> Rajeshmv; odonoghue@isoc.org<mailto:odonoghue@isoc.org>; ntpwg@lists.ntp.=
org<mailto:ntpwg@lists.ntp.org>
> Subject: Antw: Re: [ntpwg] [NTP Protocol] strengthening NTP control
> packets for diagnostic purpose
>
>>>> Florian Weimer <fw@deneb.enyo.de<mailto:fw@deneb.enyo.de>> schrieb am =
21.04.2015 um 23:13 in
>>>> Nachricht
> <87bnihyyko.fsf@mid.deneb.enyo.de<mailto:87bnihyyko.fsf@mid.deneb.enyo.de=
>>:
>> * Anil Kumar S. N.:
>>
>>> There are two options
>>>
>>> 1.       NTP dynamic runtime diagnostic tools can be implemented using =
NTP
>> extensions using protocol packets
>>>
>>> 2.       Strengthen NTP control packets with new options to achieve the
>> same. [Preferred]
>>
>> I seriously suggest to consider moving diagnostics and other form of
>> management out of band (say SNMP, CIM or PCP, basically anything else
>> that does not run over port 123/UDP), so that these interfaces are
>> not constrained by the NTP technical framework regarding
>> authentication, authorization, confidentiality, and integrity protection=
.
>
> Well, SNMP, CIM and PCP (Performance Co-Pilot?) all may be more
> standard, but they all have some extra protocol (and library)
> overhead. And I think confidentiality and integrity are also issues
> when monitoring or controlling NTP. So I don't see why you want to
> have it out-band (unless you simply want to get rid of it).
>
> Modeling NTP in SNMP may be an interesting exercise (consuming many
> hours), but may end up in a moster that only few people want to deal
> with. I don't like framework monsters feeding each other...
> Regards,
> Ulrich
>
>
> [Anil-1] : I think current IETF standards for managing NTP are NTP MIB
> (SNMP
> based) and Yang model. These are the protocols who's reach is confined
> to a service provider due to authentication issues. Many operators
> have defined their own private MIB to access information and configure NT=
P.
> Confidentiality is not required for NTP but integrity of the NTP
> content yes it is required, As of now its optional we can think of
> making it mandatory for control packets.
>
> Usually cases are like in service provider network they will have a
> NTP client connected to a different NTP server which belongs to
> different service provider; from which all other devices in that
> service provider network will get their time synchronized. If the
> server is faulty, diagnostic purpose we need to query behavior of the
> server at that particular time. Only with control packets we will be
> able to get the information of the NTP server which belongs to
> different service provider
>
> NTP control packets exist for NTPv3, do you want to get rid of it :)
> Think about it, there were very good reasons for introducing it.
> I can see Linux exhaustively exploits NTP query functionality, One
> very good utility is People have written scripts to perform NTP trace.
> Let's take what's good in current design of control packets and
> address the shortcomings.
>
>
>
>> _______________________________________________
>> ntpwg mailing list
>> ntpwg@lists.ntp.org<mailto:ntpwg@lists.ntp.org>
>> http://lists.ntp.org/listinfo/ntpwg



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

--_000_327562D94EA7BF428CD805F338C31EF04FB38E63nkgeml512mbxchi_
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=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 12 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:SimSun;
	panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
	{font-family:SimSun;
	panose-1:2 1 6 0 3 1 1 1 1 1;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","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;}
p
	{mso-style-priority:99;
	mso-margin-top-alt:auto;
	margin-right:0cm;
	mso-margin-bottom-alt:auto;
	margin-left:0cm;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
	{mso-style-priority:99;
	mso-style-link:"Balloon Text Char";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:8.0pt;
	font-family:"Tahoma","sans-serif";}
p.emailquote, li.emailquote, div.emailquote
	{mso-style-name:emailquote;
	mso-margin-top-alt:auto;
	margin-right:0cm;
	mso-margin-bottom-alt:auto;
	margin-left:1.0pt;
	border:none;
	padding:0cm;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
span.BalloonTextChar
	{mso-style-name:"Balloon Text Char";
	mso-style-priority:99;
	mso-style-link:"Balloon Text";
	font-family:"Tahoma","sans-serif";}
span.EmailStyle21
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:72.0pt 90.0pt 72.0pt 90.0pt;}
div.WordSection1
	{page:WordSection1;}
--></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=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">Hi Dowd,<o:p></o:p></span=
></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Do you ex=
pect White List in control packets, I feel anything confidential should not=
 be part of NTP control packets.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; For Sensi=
tive data such as Authentication Password and White/Black List &nbsp;Config=
uration or access should be done using Management protocol which
 support confidentiality (Owned and controlled by service provider for thei=
r devices)<o:p></o:p></span></p>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">Thanks &amp; Regards<o:p>=
</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">Anil S N<o:p></o:p></span=
></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">&#8220;Be liberal in what=
 you accept, and conservative in what you send&#8221; - Jon Postel<o:p></o:=
p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
</div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm =
0cm 0cm">
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span style=3D"font-s=
ize:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> Greg Dow=
d [mailto:Greg.Dowd@microsemi.com]
<br>
<b>Sent:</b> 22 April 2015 19:28<br>
<b>To:</b> Anil Kumar S N (VRP Network BL)<br>
<b>Cc:</b> fw@deneb.enyo.de; Ulrich Windl; Kalyankumar Asangi; Dhruv Dhody;=
 kasturi chandradeep; ntpwg@lists.ntp.org; Rajeshmv; Chirag shah; odonoghue=
@isoc.org<br>
<b>Subject:</b> Re: [ntpwg] Antw: Re: [NTP Protocol] strengthening NTP cont=
rol packets for diagnostic purpose<o:p></o:p></span></p>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<div>
<p>I could see the white list restrict entries as confidential for example.=
<o:p></o:p></p>
<div>
<p class=3D"MsoNormal">On Apr 22, 2015 5:10 AM, &quot;Anil Kumar S N (VRP N=
etwork BL)&quot; &lt;<a href=3D"mailto:anil.sn@huawei.com">anil.sn@huawei.c=
om</a>&gt; wrote:<o:p></o:p></p>
</div>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt">Hi,<br>
<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; In NTP you are talking about Aut=
hentication key and password ?, Anyways that should not be in the scope of =
control packets.&nbsp;&nbsp;&nbsp;&nbsp;
<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; What else you are expecting to b=
e kept confidential ? Do you have anything specific in mind?<br>
<br>
Thanks &amp; Regards<br>
Anil S N<br>
<br>
&quot;Be liberal in what you accept, and conservative in what you send&quot=
; - Jon Postel<br>
<br>
<br>
<br>
-----Original Message-----<br>
From: Ulrich Windl [<a href=3D"mailto:Ulrich.Windl@rz.uni-regensburg.de">ma=
ilto:Ulrich.Windl@rz.uni-regensburg.de</a>]
<br>
Sent: 22 April 2015 19:09<br>
To: <a href=3D"mailto:fw@deneb.enyo.de">fw@deneb.enyo.de</a>; Anil Kumar S =
N (VRP Network BL)<br>
Cc: Chirag shah; Dhruv Dhody; Kalyankumar Asangi; kasturi chandradeep; Raje=
shmv; <a href=3D"mailto:odonoghue@isoc.org">
odonoghue@isoc.org</a>; <a href=3D"mailto:ntpwg@lists.ntp.org">ntpwg@lists.=
ntp.org</a><br>
Subject: RE: Antw: Re: [ntpwg] [NTP Protocol] strengthening NTP control pac=
kets for diagnostic purpose<br>
<br>
Hello!<br>
<br>
I mostly agee except &quot;(...)Confidentiality is not required for NTP(...=
)&quot;: Assume some configuration data is not publicly available. If someo=
ne who is allowed to access that configuration data over the net with prope=
r authentication, these data will appear on
 the net (without confidentiality). You don't make them public, but you may=
 disclose it these days...<br>
<br>
That's what I thought.<br>
<br>
Regards,<br>
Ulrich<br>
<br>
<br>
&gt;&gt;&gt; &quot;Anil Kumar S N (VRP Network BL)&quot; &lt;<a href=3D"mai=
lto:anil.sn@huawei.com">anil.sn@huawei.com</a>&gt; schrieb am
<br>
&gt;&gt;&gt; 22.04.2015 um<br>
11:43 in Nachricht<br>
&lt;<a href=3D"mailto:327562D94EA7BF428CD805F338C31EF04FB38D5C@nkgeml512-mb=
x.china.huawei.com">327562D94EA7BF428CD805F338C31EF04FB38D5C@nkgeml512-mbx.=
china.huawei.com</a>&gt;:<br>
&gt; Hi Windl,<br>
&gt; <br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Please see my comments inlin=
e [Anil-1]<br>
&gt; <br>
&gt; <br>
&gt; Thanks &amp; Regards<br>
&gt; Anil S N<br>
&gt; <br>
&gt; &quot;Be liberal in what you accept, and conservative in what you send=
&quot; - <br>
&gt; Jon Postel<br>
&gt; <br>
&gt; <br>
&gt; <br>
&gt; -----Original Message-----<br>
&gt; From: Ulrich Windl [<a href=3D"mailto:Ulrich.Windl@rz.uni-regensburg.d=
e">mailto:Ulrich.Windl@rz.uni-regensburg.de</a>]<br>
&gt; Sent: 22 April 2015 12:17<br>
&gt; To: <a href=3D"mailto:fw@deneb.enyo.de">fw@deneb.enyo.de</a>; Anil Kum=
ar S N (VRP Network BL)<br>
&gt; Cc: Chirag shah; Dhruv Dhody; Kalyankumar Asangi; kasturi chandradeep;=
 <br>
&gt; Rajeshmv; <a href=3D"mailto:odonoghue@isoc.org">odonoghue@isoc.org</a>=
; <a href=3D"mailto:ntpwg@lists.ntp.org">
ntpwg@lists.ntp.org</a><br>
&gt; Subject: Antw: Re: [ntpwg] [NTP Protocol] strengthening NTP control <b=
r>
&gt; packets for diagnostic purpose<br>
&gt; <br>
&gt;&gt;&gt;&gt; Florian Weimer &lt;<a href=3D"mailto:fw@deneb.enyo.de">fw@=
deneb.enyo.de</a>&gt; schrieb am 21.04.2015 um 23:13 in
<br>
&gt;&gt;&gt;&gt; Nachricht<br>
&gt; &lt;<a href=3D"mailto:87bnihyyko.fsf@mid.deneb.enyo.de">87bnihyyko.fsf=
@mid.deneb.enyo.de</a>&gt;:<br>
&gt;&gt; * Anil Kumar S. N.:<br>
&gt;&gt; <br>
&gt;&gt;&gt; There are two options<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; 1.&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; NTP dynamic runtime dia=
gnostic tools can be implemented using NTP <br>
&gt;&gt; extensions using protocol packets<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; 2.&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Strengthen NTP control =
packets with new options to achieve the <br>
&gt;&gt; same. [Preferred]<br>
&gt;&gt; <br>
&gt;&gt; I seriously suggest to consider moving diagnostics and other form =
of <br>
&gt;&gt; management out of band (say SNMP, CIM or PCP, basically anything e=
lse <br>
&gt;&gt; that does not run over port 123/UDP), so that these interfaces are=
 <br>
&gt;&gt; not constrained by the NTP technical framework regarding <br>
&gt;&gt; authentication, authorization, confidentiality, and integrity prot=
ection.<br>
&gt; <br>
&gt; Well, SNMP, CIM and PCP (Performance Co-Pilot?) all may be more <br>
&gt; standard, but they all have some extra protocol (and library) <br>
&gt; overhead. And I think confidentiality and integrity are also issues <b=
r>
&gt; when monitoring or controlling NTP. So I don't see why you want to <br=
>
&gt; have it out-band (unless you simply want to get rid of it).<br>
&gt; <br>
&gt; Modeling NTP in SNMP may be an interesting exercise (consuming many <b=
r>
&gt; hours), but may end up in a moster that only few people want to deal <=
br>
&gt; with. I don't like framework monsters feeding each other...<br>
&gt; Regards,<br>
&gt; Ulrich<br>
&gt; <br>
&gt; <br>
&gt; [Anil-1] : I think current IETF standards for managing NTP are NTP MIB=
 <br>
&gt; (SNMP<br>
&gt; based) and Yang model. These are the protocols who's reach is confined=
 <br>
&gt; to a service provider due to authentication issues. Many operators <br=
>
&gt; have defined their own private MIB to access information and configure=
 NTP.<br>
&gt; Confidentiality is not required for NTP but integrity of the NTP <br>
&gt; content yes it is required, As of now its optional we can think of <br=
>
&gt; making it mandatory for control packets.<br>
&gt; <br>
&gt; Usually cases are like in service provider network they will have a <b=
r>
&gt; NTP client connected to a different NTP server which belongs to <br>
&gt; different service provider; from which all other devices in that <br>
&gt; service provider network will get their time synchronized. If the <br>
&gt; server is faulty, diagnostic purpose we need to query behavior of the =
<br>
&gt; server at that particular time. Only with control packets we will be <=
br>
&gt; able to get the information of the NTP server which belongs to <br>
&gt; different service provider<br>
&gt; <br>
&gt; NTP control packets exist for NTPv3, do you want to get rid of it :)&n=
bsp; <br>
&gt; Think about it, there were very good reasons for introducing it.<br>
&gt; I can see Linux exhaustively exploits NTP query functionality, One <br=
>
&gt; very good utility is People have written scripts to perform NTP trace.=
<br>
&gt; Let's take what's good in current design of control packets and <br>
&gt; address the shortcomings.<br>
&gt; <br>
&gt; <br>
&gt; <br>
&gt;&gt; _______________________________________________<br>
&gt;&gt; ntpwg mailing list<br>
&gt;&gt; <a href=3D"mailto:ntpwg@lists.ntp.org">ntpwg@lists.ntp.org</a><br>
&gt;&gt; <a href=3D"http://lists.ntp.org/listinfo/ntpwg">http://lists.ntp.o=
rg/listinfo/ntpwg</a><br>
<br>
<br>
<br>
_______________________________________________<br>
ntpwg mailing list<br>
<a href=3D"mailto:ntpwg@lists.ntp.org">ntpwg@lists.ntp.org</a><br>
<a href=3D"http://lists.ntp.org/listinfo/ntpwg">http://lists.ntp.org/listin=
fo/ntpwg</a><o:p></o:p></span></p>
</div>
</div>
</body>
</html>

--_000_327562D94EA7BF428CD805F338C31EF04FB38E63nkgeml512mbxchi_--

--===============5666670701745279356==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

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

From ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org  Thu Apr 23 20:26:16 2015
Return-Path: <ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org>
X-Original-To: ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com
Delivered-To: ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4A3671B2B8E for <ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com>; Thu, 23 Apr 2015 20:26:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.51
X-Spam-Level:
X-Spam-Status: No, score=-0.51 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 V4y2HKoPKgmP for <ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com>; Thu, 23 Apr 2015 20:26:14 -0700 (PDT)
Received: from psp3.ntp.org (psp3.ntp.org [149.20.68.23]) by ietfa.amsl.com (Postfix) with ESMTP id 5A48D1B2B88 for <ntp-archives-ahFae6za@lists.ietf.org>; Thu, 23 Apr 2015 20:25:55 -0700 (PDT)
Received: from psp3.ntp.org (localhost.ntp.org [127.0.0.1]) by psp3.ntp.org (Postfix) with ESMTP id 87AE539924 for <ntp-archives-ahFae6za@lists.ietf.org>; Thu, 23 Apr 2015 20:25:54 -0700 (PDT)
X-Original-To: ntpwg@lists.ntp.org
Delivered-To: ntpwg@lists.ntp.org
Received: from mail1.ntp.org (mail1.ntp.org [IPv6:2001:4f8:fff7:1::5]) by lists.ntp.org (Postfix) with ESMTP id 7BA4D86D55F for <ntpwg@lists.ntp.org>; Fri, 24 Apr 2015 03:25:51 +0000 (UTC)
Received: from chessie.everett.org ([66.220.13.234]) by mail1.ntp.org with esmtp (Exim 4.77 (FreeBSD)) (envelope-from <mayer@ntp.org>) id 1YlUFH-00098x-VJ for ntpwg@lists.ntp.org; Fri, 24 Apr 2015 03:25:50 +0000
Received: from localhost (localhost [127.0.0.1]) by chessie.everett.org (Postfix) with SMTP id 9E28AB835 for <ntpwg@lists.ntp.org>; Fri, 24 Apr 2015 03:21:54 +0000 (UTC)
Received: from [10.10.10.102] (static-108-1-141-212.bstnma.east.verizon.net [108.1.141.212]) by chessie.everett.org (Postfix) with ESMTPSA id DF5FCB814; Fri, 24 Apr 2015 03:21:47 +0000 (UTC)
Message-ID: <5539B703.5050308@ntp.org>
Date: Thu, 23 Apr 2015 23:22:43 -0400
From: Danny Mayer <mayer@ntp.org>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.6.0
MIME-Version: 1.0
To: "Anil Kumar S N (VRP Network BL)" <anil.sn@huawei.com>,  "ntpwg@lists.ntp.org" <ntpwg@lists.ntp.org>
References: <327562D94EA7BF428CD805F338C31EF04FB38946@nkgeml512-mbx.china.huawei.com>
In-Reply-To: <327562D94EA7BF428CD805F338C31EF04FB38946@nkgeml512-mbx.china.huawei.com>
X-DSPAM-Result: Innocent
X-DSPAM-Processed: Fri Apr 24 03:21:54 2015
X-DSPAM-Confidence: 1.0000
X-DSPAM-Probability: 0.0023
X-DSPAM-Signature: 6384,5539b6d2473991540177441
X-SA-Exim-Connect-IP: 66.220.13.234
X-SA-Exim-Rcpt-To: ntpwg@lists.ntp.org
X-SA-Exim-Mail-From: mayer@ntp.org
X-SA-Exim-Version: 4.2
X-SA-Exim-Scanned: Yes (on mail1.ntp.org)
Subject: Re: [ntpwg] [NTP Protocol] strengthening NTP control packets for diagnostic purpose
X-BeenThere: ntpwg@lists.ntp.org
X-Mailman-Version: 2.1.20
Precedence: list
List-Id: IETF Working Group for Network Time Protocol <ntpwg.lists.ntp.org>
List-Unsubscribe: <http://lists.ntp.org/options/ntpwg>, <mailto:ntpwg-request@lists.ntp.org?subject=unsubscribe>
List-Archive: <http://lists.ntp.org/pipermail/ntpwg/>
List-Post: <mailto:ntpwg@lists.ntp.org>
List-Help: <mailto:ntpwg-request@lists.ntp.org?subject=help>
List-Subscribe: <http://lists.ntp.org/listinfo/ntpwg>, <mailto:ntpwg-request@lists.ntp.org?subject=subscribe>
Cc: Karen O'Donoghue <odonoghue@isoc.org>, Rajeshmv <rajeshmv@huawei.com>, kasturi chandradeep <kasturi.chandradeep@huawei.com>, Dhruv Dhody <dhruv.dhody@huawei.com>, Chirag shah <chirag.shah@huawei.com>, Kalyankumar Asangi <kalyana@huawei.com>
Content-Type: text/plain; charset="windows-1252"
Content-Transfer-Encoding: quoted-printable
Errors-To: ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org
Sender: "ntpwg" <ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org>

On 4/20/2015 12:49 AM, Anil Kumar S N (VRP Network BL) wrote:
> Hi Folks,
>                 Please give your opinion on strengthening of NTP control
> packets for better diagnostic purpose.  =

>

I am not sure I understand what you mean by that. Can you explain what
you want to accomplish first before we try to decide what you need?

> Is Yang model and MIB is sufficient ? Will it help to get all the
> information ?
> =


I have no idea what the Yang model is and what it does for you. Maybe
you can explain in a few words?

> Ex: Authorization for management protocol such as MIB/Yang  is limited
> with respect to service provider, As NTP servers could be managed by
> other service providers.
> =


This is even less clear. If you don't manage an NTP server you should
not be able to control it and sometimes not even know any details about
it. I'm not sure what this has to do with MIB/Yang.

> I feel Mr. Mills was aware of this so he introduced control packets, but
> I feel it=92s out dated.
> =


You really should ask him if you want to know. We can't go by feelings.

> There are two options
> =

> 1.       NTP dynamic runtime diagnostic tools can be implemented using
> NTP extensions using protocol packets
> =


What would these runtime diagnostiv tools do and why do you think you
should use NTP extension fields for this? There are other ways of
managing servers without using the NTP protocol. Have you considered that?

> 2.       Strengthen NTP control packets with new options to achieve the
> same. [Preferred]
>  =


What are you thinking of? What is meant by strengthen? What are these
new options and what would they accomplish?

> Please give your opinion. We are working on this, Your opinion matters.
>

What exactly are you working on? It's hard to make suggestions or give
advice without knowing the goals.

> Thanks & Regards
> =

> Anil S N
> =


I've been reading the responses to this thread and I'm no wiser as to
what you are trying to do. Can we get the ultimate goals detailed before
we discussed how to get there?

Danny

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

From ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org  Mon Apr 27 00:11:15 2015
Return-Path: <ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org>
X-Original-To: ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com
Delivered-To: ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 72C1A1A8953 for <ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com>; Mon, 27 Apr 2015 00:11:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.011
X-Spam-Level:
X-Spam-Status: No, score=-0.011 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 ejMN_43IjORb for <ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com>; Mon, 27 Apr 2015 00:11:13 -0700 (PDT)
Received: from psp3.ntp.org (psp3.ntp.org [149.20.68.23]) by ietfa.amsl.com (Postfix) with ESMTP id ACBEA1A893C for <ntp-archives-ahFae6za@lists.ietf.org>; Mon, 27 Apr 2015 00:11:13 -0700 (PDT)
Received: from psp3.ntp.org (localhost.ntp.org [127.0.0.1]) by psp3.ntp.org (Postfix) with ESMTP id 09A8439950 for <ntp-archives-ahFae6za@lists.ietf.org>; Mon, 27 Apr 2015 00:11:13 -0700 (PDT)
X-Original-To: ntpwg@lists.ntp.org
Delivered-To: ntpwg@lists.ntp.org
Received: from mail1.ntp.org (mail1.ntp.org [IPv6:2001:4f8:fff7:1::5]) by lists.ntp.org (Postfix) with ESMTP id 880C486D48C for <ntpwg@lists.ntp.org>; Mon, 27 Apr 2015 07:11:09 +0000 (UTC)
Received: from szxga02-in.huawei.com ([119.145.14.65]) by mail1.ntp.org with esmtps (TLSv1:RC4-SHA:128) (Exim 4.77 (FreeBSD)) (envelope-from <anil.sn@huawei.com>) id 1Ymd9a-000MCt-CJ; Mon, 27 Apr 2015 07:08:38 +0000
Received: from 172.24.2.119 (EHLO nkgeml408-hub.china.huawei.com) ([172.24.2.119]) by szxrg02-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id CKL89044; Mon, 27 Apr 2015 15:05:54 +0800 (CST)
Received: from NKGEML512-MBX.china.huawei.com ([169.254.7.135]) by nkgeml408-hub.china.huawei.com ([10.98.56.39]) with mapi id 14.03.0158.001; Mon, 27 Apr 2015 15:05:47 +0800
From: "Anil Kumar S N (VRP Network BL)" <anil.sn@huawei.com>
To: Danny Mayer <mayer@ntp.org>, "ntpwg@lists.ntp.org" <ntpwg@lists.ntp.org>
Thread-Topic: [ntpwg] [NTP Protocol] strengthening NTP control packets for diagnostic purpose
Thread-Index: AQHQfj5jFMhUQReBTEGn1GGloV8Ngp1gdC6Q
Date: Mon, 27 Apr 2015 07:05:47 +0000
Message-ID: <327562D94EA7BF428CD805F338C31EF04FB393E0@nkgeml512-mbx.china.huawei.com>
References: <327562D94EA7BF428CD805F338C31EF04FB38946@nkgeml512-mbx.china.huawei.com> <5539B703.5050308@ntp.org>
In-Reply-To: <5539B703.5050308@ntp.org>
Accept-Language: en-US, zh-CN
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.18.212.150]
MIME-Version: 1.0
X-CFilter-Loop: Reflected
X-SA-Exim-Connect-IP: 119.145.14.65
X-SA-Exim-Rcpt-To: ntpwg@lists.ntp.org, mayer@ntp.org
X-SA-Exim-Mail-From: anil.sn@huawei.com
X-SA-Exim-Version: 4.2
X-SA-Exim-Scanned: Yes (on mail1.ntp.org)
Subject: Re: [ntpwg] [NTP Protocol] strengthening NTP control packets for diagnostic purpose
X-BeenThere: ntpwg@lists.ntp.org
X-Mailman-Version: 2.1.20
Precedence: list
List-Id: IETF Working Group for Network Time Protocol <ntpwg.lists.ntp.org>
List-Unsubscribe: <http://lists.ntp.org/options/ntpwg>, <mailto:ntpwg-request@lists.ntp.org?subject=unsubscribe>
List-Archive: <http://lists.ntp.org/pipermail/ntpwg/>
List-Post: <mailto:ntpwg@lists.ntp.org>
List-Help: <mailto:ntpwg-request@lists.ntp.org?subject=help>
List-Subscribe: <http://lists.ntp.org/listinfo/ntpwg>, <mailto:ntpwg-request@lists.ntp.org?subject=subscribe>
Cc: Karen O'Donoghue <odonoghue@isoc.org>, Rajeshmv <rajeshmv@huawei.com>, kasturi chandradeep <kasturi.chandradeep@huawei.com>, Dhruv Dhody <dhruv.dhody@huawei.com>, Chirag shah <chirag.shah@huawei.com>, Kalyankumar Asangi <kalyana@huawei.com>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org
Sender: "ntpwg" <ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org>

Hi Danny, 

	Was out of station, Will respond to this mail soon with details.

Thanks & Regards
Anil S N

"Be liberal in what you accept, and conservative in what you send" - Jon Postel



-----Original Message-----
From: ntpwg [mailto:ntpwg-bounces+anilkumarsn=huawei.com@lists.ntp.org] On Behalf Of Danny Mayer
Sent: 24 April 2015 11:23
To: Anil Kumar S N (VRP Network BL); ntpwg@lists.ntp.org
Cc: Karen O'Donoghue; Rajeshmv; kasturi chandradeep; Dhruv Dhody; Chirag shah; Kalyankumar Asangi
Subject: Re: [ntpwg] [NTP Protocol] strengthening NTP control packets for diagnostic purpose

On 4/20/2015 12:49 AM, Anil Kumar S N (VRP Network BL) wrote:
> Hi Folks,
>                 Please give your opinion on strengthening of NTP 
> control packets for better diagnostic purpose.
>

I am not sure I understand what you mean by that. Can you explain what
you want to accomplish first before we try to decide what you need?

> Is Yang model and MIB is sufficient ? Will it help to get all the
> information ?
> 

I have no idea what the Yang model is and what it does for you. Maybe
you can explain in a few words?

> Ex: Authorization for management protocol such as MIB/Yang  is limited
> with respect to service provider, As NTP servers could be managed by
> other service providers.
> 

This is even less clear. If you don't manage an NTP server you should
not be able to control it and sometimes not even know any details about
it. I'm not sure what this has to do with MIB/Yang.

> I feel Mr. Mills was aware of this so he introduced control packets, but
> I feel it's out dated.
> 

You really should ask him if you want to know. We can't go by feelings.

> There are two options
> 
> 1.       NTP dynamic runtime diagnostic tools can be implemented using
> NTP extensions using protocol packets
> 

What would these runtime diagnostiv tools do and why do you think you
should use NTP extension fields for this? There are other ways of
managing servers without using the NTP protocol. Have you considered that?

> 2.       Strengthen NTP control packets with new options to achieve the
> same. [Preferred]
>  

What are you thinking of? What is meant by strengthen? What are these
new options and what would they accomplish?

> Please give your opinion. We are working on this, Your opinion matters.
>

What exactly are you working on? It's hard to make suggestions or give
advice without knowing the goals.

> Thanks & Regards
> 
> Anil S N
> 

I've been reading the responses to this thread and I'm no wiser as to
what you are trying to do. Can we get the ultimate goals detailed before
we discussed how to get there?

Danny

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