Re: [Ntp] Summary notes from IETF 102

Denis Reilly <denis.reilly@spectracom.orolia.com> Thu, 16 August 2018 19:40 UTC

Return-Path: <denis.reilly@spectracom.orolia.com>
X-Original-To: ntp@ietfa.amsl.com
Delivered-To: ntp@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 32A6F130DE2 for <ntp@ietfa.amsl.com>; Thu, 16 Aug 2018 12:40:46 -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, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_DKIMWL_WL_MED=-0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=oroliagroup.onmicrosoft.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 Y-UEjL0mxM45 for <ntp@ietfa.amsl.com>; Thu, 16 Aug 2018 12:40:42 -0700 (PDT)
Received: from EUR02-AM5-obe.outbound.protection.outlook.com (mail-eopbgr00069.outbound.protection.outlook.com [40.107.0.69]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5153B12785F for <ntp@ietf.org>; Thu, 16 Aug 2018 12:40:42 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=OROLIAGROUP.onmicrosoft.com; s=selector1-spectracom-orolia-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=/QGRW5+JdDK0ivEsEw8NlZYq7uwAKKe9PEWtARd0Ynk=; b=sVB18BGhOSRKm5WLMdAcZbZZM3CyuTwmSDXWChy1560iHTPuvu4+S1+sg2PyguH+DCs/nnItr6bOIP3mAzoz5w0jSStBs/GIb1cpLuoGiX/cnPLBBUHXEeua5ZUP2aW5tHayhku0Y6dpqxXUGSHk9zXuWOy16OedtxGHRDWHRY8=
Received: from AM0PR0602MB3730.eurprd06.prod.outlook.com (52.133.40.31) by AM0PR0602MB3620.eurprd06.prod.outlook.com (52.133.49.159) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1059.20; Thu, 16 Aug 2018 19:40:37 +0000
Received: from AM0PR0602MB3730.eurprd06.prod.outlook.com ([fe80::a14a:50e5:a2e8:b547]) by AM0PR0602MB3730.eurprd06.prod.outlook.com ([fe80::a14a:50e5:a2e8:b547%3]) with mapi id 15.20.1038.025; Thu, 16 Aug 2018 19:40:37 +0000
From: Denis Reilly <denis.reilly@spectracom.orolia.com>
To: Karen O'Donoghue <odonoghue@isoc.org>, "ntp@ietf.org" <ntp@ietf.org>
Thread-Topic: Summary notes from IETF 102
Thread-Index: AQHUNNJhfRJGzFk0LECaa/jJpYDBwaTCxnow
Date: Thu, 16 Aug 2018 19:40:37 +0000
Message-ID: <AM0PR0602MB373012E45B6DCDAC1BF7FC16D23E0@AM0PR0602MB3730.eurprd06.prod.outlook.com>
References: <32433918-AA3B-4587-9A26-1C3451BB6632@isoc.org>
In-Reply-To: <32433918-AA3B-4587-9A26-1C3451BB6632@isoc.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: spf=none (sender IP is ) smtp.mailfrom=denis.reilly@spectracom.orolia.com;
x-originating-ip: [66.193.84.98]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; AM0PR0602MB3620; 6:y3Cstf0RoYt4Lw/cNJooWN+fWycf0fG4SDcyhNyxewr+Qwq0jDMzq4UXSZuIZqjpynS+pIFNSThKswlul/EFTboBYB3+R46DXlWEq5Bq+cQKgmyDqk5KaNL4+UJTXURaj62iyCsm5JWGW7rIsL9KUQgSq0Atd6MbQZAunyU+4idgsq2W+wBlQDcDsx+Jv87ktbMQ9L6mzDcQzw4ulpXoZKMdmGiLD2zKVJdsxUbxv/ziCNZE2yEh5ajSjhbBtBVcewmpC2ZCYPlSsCoijjEjjIQz3YG6Fkz1SbHhAx5HMyPj3d05oGCHmf3i3393CFsqZICS5GXBovLygTzIIYITSwc0vA4P2DAkXT/OGFxxmn2FDK6ye25jWN5SN4hfv7Qe78RXRTXl63o2yXvKNmeSPAuk6dgWutuCKFqVsqfyWWP8vNrinarjCtaZ0WNLf15odEsK1NdHth4IFfYt/jfjgA==; 5:a1ZYudH9uS4/JcHYQTKX8KfCHu/X/DMFAQPPvPHl5Py7+yWkAw4DOD3UAIxxjp6E7jn5e9GdtNw6FcWoXH6OVjobsecnOMps8aISNyooZE+l/pN9d54sIEHCnpnmK67DHW9v4Lgu3zZZEo9vkuErxCwoOW9ZXHeA45B7fwhzZwg=; 7:eVLVZVx6Ji9npr1THtBgILNAyaDhBsNypHk38DgRKQALQrsdFRyQLG1TvE5/u4Cx4zHCMcsMjvU1dQAE5ssyPRXfnZ5lErSqZHV9R2lfR0W/Qx51m3Aih7uCAVZAKz73ioqbDkwHcj1gR3oWGn/yL5dFqSgSxJjdxVah/2ol2D5hNpbVKAulmByGHInFBQr90LgvHyROaFTgsyIUP83O5bbIYzQADCrXvTTCT+7Xz6bafx2xt0OnjrG+khqBu1na
x-ms-exchange-antispam-srfa-diagnostics: SOS;
x-ms-office365-filtering-correlation-id: 476f7239-cb29-4272-66f4-08d603b02453
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(7020095)(4652040)(8989137)(4534165)(4627221)(201703031133081)(201702281549075)(8990107)(5600074)(711020)(2017052603328)(7153060)(7193020); SRVR:AM0PR0602MB3620;
x-ms-traffictypediagnostic: AM0PR0602MB3620:
x-microsoft-antispam-prvs: <AM0PR0602MB3620EDFC6B690E790E1BCAFAD23E0@AM0PR0602MB3620.eurprd06.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(28532068793085)(120809045254105)(100405760836317)(21748063052155);
x-ms-exchange-senderadcheck: 1
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(8211001083)(6040522)(2401047)(5005006)(8121501046)(93006095)(93001095)(3002001)(10201501046)(3231311)(944501410)(52105095)(149027)(150027)(6041310)(20161123564045)(20161123560045)(20161123558120)(20161123562045)(201703131423095)(201702281528075)(20161123555045)(201703061421075)(201703061406153)(201708071742011)(7699016); SRVR:AM0PR0602MB3620; BCL:0; PCL:0; RULEID:; SRVR:AM0PR0602MB3620;
x-forefront-prvs: 07665BE9D1
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(39850400004)(396003)(366004)(136003)(376002)(346002)(60444003)(189003)(199004)(2906002)(33656002)(19609705001)(81166006)(81156014)(8676002)(790700001)(6116002)(3846002)(86362001)(606006)(106356001)(105586002)(5660300001)(97736004)(7696005)(8936002)(966005)(68736007)(478600001)(6246003)(76176011)(110136005)(99286004)(14454004)(316002)(2900100001)(6436002)(2501003)(55016002)(236005)(9686003)(54896002)(6306002)(74316002)(7736002)(53936002)(229853002)(25786009)(66066001)(5250100002)(256004)(102836004)(476003)(26005)(53546011)(6506007)(14444005)(11346002)(44832011)(486006)(186003)(446003); DIR:OUT; SFP:1101; SCL:1; SRVR:AM0PR0602MB3620; H:AM0PR0602MB3730.eurprd06.prod.outlook.com; FPR:; SPF:None; PTR:InfoNoRecords; MX:3; A:1;
received-spf: None (protection.outlook.com: spectracom.orolia.com does not designate permitted sender hosts)
x-microsoft-antispam-message-info: nkxmAxCwvDPaGZygSlg9CkWSM3vWyHA4fWjKqRHYkiYyHzs6PzQZu+ZKrw1CLPQifqOo5R1TKvANUVfnxqDQEsAoRWoxOAf3DcBUuhiVREAN2F4ZMyT1FXWFvq7m7DjEuyNGnwI43XJTN51FLK+LG0infFaGeMIWrD/8YTMUBvqRGT//TPRG6N+u38jffZc2+SkleYHYh1kEMdI6Bvz8IxitE1PJ4egg9fbPO6l06Qy8wKavNXyHST5rUNMZ7a0k4Y5fBMit8BTvM5PTWg5wmbA4X13J59CdGiCNJoLQp8DXXn7X8Z8jjkCEpTefThXBsCWh7jDgiOmwJhHJtBSOseV2pNiZoAfZXemXSN0jITM=
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: multipart/alternative; boundary="_000_AM0PR0602MB373012E45B6DCDAC1BF7FC16D23E0AM0PR0602MB3730_"
MIME-Version: 1.0
X-OriginatorOrg: spectracom.orolia.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 476f7239-cb29-4272-66f4-08d603b02453
X-MS-Exchange-CrossTenant-originalarrivaltime: 16 Aug 2018 19:40:37.7136 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: a263030c-9c1b-421f-9471-1dec0b29c664
X-MS-Exchange-Transport-CrossTenantHeadersStamped: AM0PR0602MB3620
Archived-At: <https://mailarchive.ietf.org/arch/msg/ntp/rOUAigc02haHHCu_Fvvod7GejiI>
Subject: Re: [Ntp] Summary notes from IETF 102
X-BeenThere: ntp@ietf.org
X-Mailman-Version: 2.1.27
Precedence: list
List-Id: <ntp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ntp>, <mailto:ntp-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ntp/>
List-Post: <mailto:ntp@ietf.org>
List-Help: <mailto:ntp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ntp>, <mailto:ntp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 16 Aug 2018 19:40:46 -0000

Hello, Karen! Thanks for keeping track of all this.

In regards to the NTP BCP, I finally did submit the updates we made in response to the INTDIR review to datatracker, on 31 July.
So, we consider that done, and we can start working with Suresh on the next steps.

Best Regards,

- Denis

--
Denis Reilly  |  Lead Engineer  |  denis.reilly@spectracom.orolia.com<mailto:denis.reilly@spectracom.orolia.com>  (585)321-5837<tel:(585)%20321-5837>

From: ntp <ntp-bounces@ietf.org> On Behalf Of Karen O'Donoghue
Sent: Wednesday, August 15, 2018 3:59 PM
To: ntp@ietf.org; tictoc@ietf.org
Subject: [Ntp] Summary notes from IETF 102

Folks,

Below is my summary of the next steps for each document from our IETF 102 meeting...
I produced it for my own sanity, but I thought it might be helpful to some of you…

Also, please remember that the minutes (thank you Tal and Dieter!) have been posted by Dieter.
https://datatracker.ietf.org/meeting/102/materials/minutes-102-ntp-01
Please get any final corrections to us by 30 Sept.

Regards,
Karen

*********************
IETF 102 Summary…

TICTOC
------

1588v2 YANG module
https://datatracker.ietf.org/doc/html/draft-ietf-tictoc-1588v2-yang
Status:  Submitted to IESG for Publication -
Next Steps:  Chairs to followup with AD and authors to ensure progression

Enterprise Profile for the PTP With Mixed Multicast and Unicast Messages
https://tools.ietf.org/html/draft-ietf-tictoc-ptp-enterprise-profile
Status:  WGLC closed successfully with some minor edits required.
Next Steps: Document update expected within two weeks. Once the update is completed, the document will be ready for the IESG.

Synchronizing Internet Clocks
https://datatracker.ietf.org/doc/html/draft-alavarez-hamelin-tictoc-sic
Status:  No consensus to adopt document at this time. Author needs to work to identify a broader community or set of collaborators interested in this work.

NTP
---

NTP MAC
https://datatracker.ietf.org/doc/html/draft-ietf-ntp-mac
Status:  Submitted to IESG for Publication
Next Steps:  Chairs to follow up with AD on status of IESG review

NTP Data Minimization
https://datatracker.ietf.org/doc/html/draft-ietf-ntp-data-minimization
Status: Document has been updated.
Next Steps: Issue WGLC

Guidelines for Defining Packet Timestamps
https://datatracker.ietf.org/doc/html/draft-ietf-ntp-packet-timestamps
Status: Document updated
Next Steps: Ask mailing list about addition of another recommended timestamp format. Pending resolution of that issue, document is ready for WGLC.

Network Time Protocol Best Current Practices
https://datatracker.ietf.org/doc/html/draft-ietf-ntp-bcp
Status: Submitted to IESG for publication.
Next Steps: Authors to update based on INTDIR review. Chairs to followup with AD.

Control Messages Protocol for Use with NTPv4
https://datatracker.ietf.org/doc/html/draft-ietf-ntp-mode-6-cmds
Status: Document updated based on WGLC
Next Steps: Measure consensus on publishing as informational versus historic. Answer the question: what implementations beyond the reference implementation implement this?

A YANG Data Model for NTP
https://datatracker.ietf.org/doc/html/draft-ietf-ntp-yang-data-model
Status: Document is updated and ready.
Next Steps: Chairs ask for a YANG expert review.

Interleaved Modes
https://datatracker.ietf.org/doc/html/draft-ietf-ntp-interleaved-modes
Status: Document has been updated.
Next Steps: Further review/discussion. When will it be ready for a WGLC?

NTS for NTP
https://datatracker.ietf.org/doc/html/draft-ietf-ntp-using-nts-for-ntp
https://datatracker.ietf.org/doc/html/draft-dansarie-nts-00
Status: Base document updated from hackathon lessons. dansarie document provides some updates.
Next Steps: Marcus to do pull requests for changes suggested by his team. Possible WGLC after those pull requests are implemented.

A Secure Selection and Filtering Mechanism for the NTPv4
https://datatracker.ietf.org/doc/html/draft-schiff-ntp-chronos
Status: Individual submission
Next Steps: Further development by author and any interested parties.

REFID Updates
https://datatracker.ietf.org/doc/html/draft-ietf-ntp-refid-updates
Status: Been around for awhile and not changing much. General support/understanding for Not You and IPv6 IDs. Concerns with leap smear ID.
Next Steps: Suggestion to split the document into two. Take question to the mailing list.

NTP Correction Field
https://datatracker.ietf.org/doc/html/draft-mlichvar-ntp-correction-field
Status: Document updated
Next Steps: Further review/discussion by working group.

7822bis (Network Time Protocol Version 4 Extension Fields0
https://datatracker.ietf.org/doc/html/draft-ietf-ntp-extension-fields
Status: Document updated.
Next Steps: Chairs to issue a WG Call for Adoption

Additional Extension Field Proposals
https://datatracker.ietf.org/doc/draft-stenn-ntp-extended-information/
https://datatracker.ietf.org/doc/draft-stenn-ntp-i-do/
https://datatracker.ietf.org/doc/draft-stenn-ntp-mac-last-ef/
https://datatracker.ietf.org/doc/draft-stenn-ntp-suggest-refid/
Status: Documents exist
Next Steps: Harlan to update to ensure compliance with RFC 7822. Any that can be published under the current extension field construct can be considered for WG adoption. Those that cannot will need to be deferred until there is consensus on any update to extension fields.