Re: [Ntp] NTP Extensions (was Re: Last Call: <draft-ietf-ntp-using-nts-for-ntp-22.txt> (Network Time Security for the Network Time Protocol) to Proposed Standard)
"Franke, Daniel" <dafranke@akamai.com> Wed, 19 February 2020 18:19 UTC
Return-Path: <dafranke@akamai.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 3F18712082C; Wed, 19 Feb 2020 10:19:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, HTTPS_HTTP_MISMATCH=0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=akamai.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 Xym5TbfSKSFV; Wed, 19 Feb 2020 10:19:42 -0800 (PST)
Received: from mx0a-00190b01.pphosted.com (mx0a-00190b01.pphosted.com [IPv6:2620:100:9001:583::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BC2DB120810; Wed, 19 Feb 2020 10:19:42 -0800 (PST)
Received: from pps.filterd (m0122333.ppops.net [127.0.0.1]) by mx0a-00190b01.pphosted.com (8.16.0.42/8.16.0.42) with SMTP id 01JIIWJr028264; Wed, 19 Feb 2020 18:19:42 GMT
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=akamai.com; h=from : to : cc : subject : date : message-id : references : in-reply-to : content-type : mime-version; s=jan2016.eng; bh=6wD7Scx/LBAKFc6QoqPP7MKF1S+91LAi3yVXNa+vbKo=; b=b2liOqKLi/TVoHbgp85N7JL2n9AefPJyqkRj0DoUFbMIZNDxoAugefgMi17G4psfEAOf qXsocVl1caDJyK9rswu2dlDiwqh9Cjw5rufBe/HnDjEMNUV3KNmVD9b9MOMLgZ0vMzsW Y8GxxqzLzL3OaCGDCac4Ku1UqwKQuP//b7jlK1aRpIZhswx6u1mPNaqygV1HmtVZtK+s c3I7IvLeQbWAh+POreFtHrzSdew4SBknUg9su4xzuyVlXrLv3LiA+GFlZQffR+jQI/BI haoh6Yn0fht85rGC8M5BK6II251cNTQCNhq19/pG98aEF5UCHhoZ+dckkCB/zLJ0UlGU qQ==
Received: from prod-mail-ppoint7 (prod-mail-ppoint7.akamai.com [96.6.114.121] (may be forged)) by mx0a-00190b01.pphosted.com with ESMTP id 2y68sfa0v5-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Wed, 19 Feb 2020 18:19:42 +0000
Received: from pps.filterd (prod-mail-ppoint7.akamai.com [127.0.0.1]) by prod-mail-ppoint7.akamai.com (8.16.0.27/8.16.0.27) with SMTP id 01JIH9lA004722; Wed, 19 Feb 2020 13:19:41 -0500
Received: from email.msg.corp.akamai.com ([172.27.165.116]) by prod-mail-ppoint7.akamai.com with ESMTP id 2y6p65jm4c-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=NOT); Wed, 19 Feb 2020 13:19:41 -0500
Received: from USTX2EX-DAG3MB3.msg.corp.akamai.com (172.27.165.127) by USTX2EX-DAG3MB2.msg.corp.akamai.com (172.27.165.126) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Wed, 19 Feb 2020 10:19:40 -0800
Received: from USTX2EX-DAG3MB3.msg.corp.akamai.com ([172.27.165.127]) by USTX2EX-DAG3MB3.msg.corp.akamai.com ([172.27.165.127]) with mapi id 15.00.1473.005; Wed, 19 Feb 2020 12:19:40 -0600
From: "Franke, Daniel" <dafranke@akamai.com>
To: Suresh Krishnan <Suresh@kaloom.com>, Hal Murray <hmurray@megapathdsl.net>
CC: "last-call@ietf.org" <last-call@ietf.org>, "ntp@ietf.org" <ntp@ietf.org>, Karen O'Donoghue <odonoghue@isoc.org>, "draft-ietf-ntp-using-nts-for-ntp@ietf.org" <draft-ietf-ntp-using-nts-for-ntp@ietf.org>
Thread-Topic: NTP Extensions (was Re: [Ntp] Last Call: <draft-ietf-ntp-using-nts-for-ntp-22.txt> (Network Time Security for the Network Time Protocol) to Proposed Standard)
Thread-Index: AQHV50TLfPiqz/8HEEi2uR9iXRMXf6gi0pXn
Date: Wed, 19 Feb 2020 18:19:40 +0000
Message-ID: <1582136379878.71291@akamai.com>
References: <20200219084813.E4C6840605C@ip-64-139-1-69.sjc.megapath.net>, <F9A58B4B-25A7-4652-8963-6849DE359C5A@kaloom.com>
In-Reply-To: <F9A58B4B-25A7-4652-8963-6849DE359C5A@kaloom.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [172.28.13.81]
Content-Type: multipart/alternative; boundary="_000_158213637987871291akamaicom_"
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:, , definitions=2020-02-19_05:, , signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 suspectscore=0 malwarescore=0 phishscore=0 bulkscore=0 spamscore=0 mlxscore=0 mlxlogscore=999 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-2002050000 definitions=main-2002190140
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:6.0.138, 18.0.572 definitions=2020-02-19_05:2020-02-19, 2020-02-19 signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 suspectscore=0 impostorscore=0 spamscore=0 clxscore=1011 phishscore=0 lowpriorityscore=0 adultscore=0 bulkscore=0 mlxlogscore=999 malwarescore=0 mlxscore=0 priorityscore=1501 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.12.0-2001150001 definitions=main-2002190140
Archived-At: <https://mailarchive.ietf.org/arch/msg/ntp/Rv2-0wvIErVBii20Y0s3m6Bx33g>
X-Mailman-Approved-At: Wed, 19 Feb 2020 10:24:20 -0800
Subject: Re: [Ntp] NTP Extensions (was Re: Last Call: <draft-ietf-ntp-using-nts-for-ntp-22.txt> (Network Time Security for the Network Time Protocol) to Proposed Standard)
X-BeenThere: ntp@ietf.org
X-Mailman-Version: 2.1.29
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: Wed, 19 Feb 2020 18:22:54 -0000
Suresh, Hal may not have been clear. The four extension fields we're discussing are the four defined by the NTS draft. Due to the registry's unfortunate lack of any P&E range, Hal and other implementers have picked four codes that they've been squatting on for their draft implementations. Desiring to avoid a flag day when the draft becomes final, they'd like IANA to turn these four codes into official allocations rather than having IANA arbitrarily assign something else. Speaking as an author of the draft I have no objection to this. ________________________________ From: Suresh Krishnan <Suresh@kaloom.com> Sent: Wednesday, February 19, 2020 11:48 To: Hal Murray Cc: Daniel Lublin; last-call@ietf.org; ntp@ietf.org; Karen O'Donoghue; draft-ietf-ntp-using-nts-for-ntp@ietf.org; ntp-chairs@ietf.org; IETF-Announce Subject: NTP Extensions (was Re: [Ntp] Last Call: <draft-ietf-ntp-using-nts-for-ntp-22.txt> (Network Time Security for the Network Time Protocol) to Proposed Standard) Hi Hal, (Changed subject to match your question below) On Feb 19, 2020, at 3:48 AM, Hal Murray <hmurray@megapathdsl.net<mailto:hmurray@megapathdsl.net>> wrote: daniel@lublin.se<mailto:daniel@lublin.se> said: I'm not entirely convinced of keeping a list of implementations in an RFC. But since the information is there, let's at least have it corrected and updated upon publishing. I thought it was a temporary section and would be deleted by the final editing pass when the TBDs were filled in. Traditionally, RFCs required running code, normally at least 2 independent implementations that can talk to each other. That section is useful while debugging and collects the data for the reviewers. ------- Speaking of TBDs... How do we contact the czar who assigns numbers for NTP extensions? We've all been testing with 4 values. It will be a pain if they change and I don't know of any reason not to make the values we are using official. If you are talking about NTP extension field types [0], they do require IETF review for allocation (i.e. no czar). Writing up a draft with your usage and sending it over to the ntp wg for consideration would be the best way forward. [0] https://www.iana.org/assignments/ntp-parameters/ntp-parameters.xhtml#ntp-parameters-3<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.iana.org_assignments_ntp-2Dparameters_ntp-2Dparameters.xhtml-23ntp-2Dparameters-2D3&d=DwMFAg&c=96ZbZZcaMF4w0F4jpN6LZg&r=NlX0r6ynsvJy6t1-UbBqZbYxmdFYzvmLMmHofVndJ5k&m=4kCauNy5drgPVUEUsh2dWTBaaNAbwXU3tn1IZ2PbYI8&s=Ilafc9XVtUXj0DZFzrrma2AVM9yP4qsJLTGybPb_FaE&e=> Regards Suresh
- [Ntp] Last Call: <draft-ietf-ntp-using-nts-for-nt… The IESG
- Re: [Ntp] Last Call: <draft-ietf-ntp-using-nts-fo… Russ Housley
- Re: [Ntp] Last Call: <draft-ietf-ntp-using-nts-fo… Marcus Dansarie
- Re: [Ntp] Last Call: <draft-ietf-ntp-using-nts-fo… Patrik Fältström
- Re: [Ntp] Last Call: <draft-ietf-ntp-using-nts-fo… Daniel Lublin
- Re: [Ntp] [Last-Call] Last Call: <draft-ietf-ntp-… Russ Housley
- Re: [Ntp] Last Call: <draft-ietf-ntp-using-nts-fo… Harlan Stenn
- Re: [Ntp] Last Call: <draft-ietf-ntp-using-nts-fo… Hal Murray
- Re: [Ntp] Last Call: <draft-ietf-ntp-using-nts-fo… Harlan Stenn
- Re: [Ntp] Last Call: <draft-ietf-ntp-using-nts-fo… Miroslav Lichvar
- Re: [Ntp] Last Call: <draft-ietf-ntp-using-nts-fo… Hal Murray
- [Ntp] Antw: [EXT] Re: Last Call: <draft-ietf-ntp-… Ulrich Windl
- Re: [Ntp] [Last-Call] Last Call: <draft-ietf-ntp-… Paul Wouters
- Re: [Ntp] [Last-Call] Last Call: <draft-ietf-ntp-… Watson Ladd
- Re: [Ntp] [Last-Call] Last Call: <draft-ietf-ntp-… Salz, Rich
- Re: [Ntp] [Last-Call] Last Call: <draft-ietf-ntp-… Karen O'Donoghue
- Re: [Ntp] NTP Extensions (was Re: Last Call: <dra… Franke, Daniel
- Re: [Ntp] [Last-Call] NTP Extensions (was Re: Las… Benjamin Kaduk
- Re: [Ntp] NTP Extensions (was Re: Last Call: <dra… Harlan Stenn
- Re: [Ntp] NTP Extensions (was Re: Last Call: <dra… Watson Ladd
- Re: [Ntp] NTP Extensions (was Re: Last Call: <dra… Harlan Stenn
- Re: [Ntp] NTP Extensions (was Re: Last Call: <dra… Watson Ladd
- Re: [Ntp] NTP Extensions (was Re: Last Call: <dra… Harlan Stenn
- Re: [Ntp] NTP Extensions (was Re: Last Call: <dra… Daniel Franke
- Re: [Ntp] NTP Extensions (was Re: Last Call: <dra… Karen O'Donoghue
- Re: [Ntp] NTP Extensions (was Re: Last Call: <dra… Watson Ladd
- Re: [Ntp] NTP Extensions (was Re: Last Call: <dra… Harlan Stenn
- Re: [Ntp] NTP Extensions (was Re: Last Call: <dra… Harlan Stenn
- Re: [Ntp] NTP Extensions (was Re: Last Call: <dra… Daniel Franke
- Re: [Ntp] NTP Extensions (was Re: Last Call: <dra… Karen O'Donoghue
- Re: [Ntp] [Last-Call] Last Call: <draft-ietf-ntp-… Karen O'Donoghue
- Re: [Ntp] NTP Extensions (was Re: Last Call: <dra… Suresh Krishnan
- Re: [Ntp] Last Call: <draft-ietf-ntp-using-nts-fo… Steven Sommars
- Re: [Ntp] Last Call: <draft-ietf-ntp-using-nts-fo… Watson Ladd
- Re: [Ntp] Last Call: <draft-ietf-ntp-using-nts-fo… Miroslav Lichvar
- [Ntp] Antw: [EXT] Re: Last Call: <draft-ietf-ntp-… Ulrich Windl