IETF Logo Mail Archive

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)

Suresh Krishnan <Suresh@kaloom.com> Wed, 19 February 2020 22:25 UTC

Return-Path: <Suresh@kaloom.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 ABC5C120857; Wed, 19 Feb 2020 14:25:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=kaloom.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 B8zyCCNlxDj8; Wed, 19 Feb 2020 14:25:32 -0800 (PST)
Received: from CAN01-TO1-obe.outbound.protection.outlook.com (mail-eopbgr670116.outbound.protection.outlook.com [40.107.67.116]) (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 DCB471208F8; Wed, 19 Feb 2020 14:25:31 -0800 (PST)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=hzM3aA6X50ujyFza4OusEU8plLhiUfTAw3fdNoIq1CFYQa1I1WkBSIbuJFpaOO6+FF07fYWQ2GDBeYnxUGJ7bvuzjQ84UVBck89TDj98bjxrSxFc+6m8a+X+yLSiqBPmuyJbajQktQs/oJ/Nh+QjQPb7eptnr21T9Y3dlVT0Y2r4Mb3r261uzUtdO9oaAOAOudbYwsAriOknOCzy8ikxi7Er37B6qVcEljgOFYG/2s59TsdR+Rx/bMc9BHNKfx/Ox3ujrUQDDEgjbzm0JG3ighWoT3gXPxY9LGo4IkgstwoFsrsu7SXobQN/3Y6cWxXz2ja+HbZD7j2PyqHv2gpV6w==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=L+oFfGvSbwtJ/10ffQuiTrO9aX+x6oehmmpLmSDH9fE=; b=DKbyQCgq5/Tf9F2Y9LzvVtZuoDIfUMmLkOT3KyjqWLTEBQPrm6sLIbqJp3kTbQ17x/9JeLeq92gFu0pHy+wYG7dRAxeO99HPJ7HcNp4vwx564RsWEtWUm+SjDvA4cRkXbFMYN7e63wY/M6+g37yctiAoxZw7ihQld6Uc2hSV0izx6ujNAYc57Qf6OhGbcaesWhpRqD2QP+qkTqi/w/LC4T8eIqqfCwrpKCM6FhrwS2VREnxZtp/n9IIOBu/0B/HpJn1uh5KEDKgpv2GsQkAISW0zB8FRs/TFeC8WaLIooVnHXodOUc8B0/Z0k3nfoz8CYHC8BztIa/NlU0KDC2Ij/Q==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=kaloom.com; dmarc=pass action=none header.from=kaloom.com; dkim=pass header.d=kaloom.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kaloom.com; s=selector2; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=L+oFfGvSbwtJ/10ffQuiTrO9aX+x6oehmmpLmSDH9fE=; b=KNEOUT6sAvcorukeZTTfdCGH8C1v2EuCsD/q7H3boxzWXSoDiWAhXfYq0QQmaBclBe2WamEsGOyr/gHDgSq8/uplQRzMGTA8vWZgeZpgIDM/c9gDDw4LCMz6tZx4sRfA665OKmghcoiqnRCxq/hIwqT1UOIt92Vq8uHxZJbiYQg=
Received: from YTXPR0101MB1615.CANPRD01.PROD.OUTLOOK.COM (52.132.33.14) by YTXPR0101MB1568.CANPRD01.PROD.OUTLOOK.COM (52.132.37.139) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2729.25; Wed, 19 Feb 2020 22:25:29 +0000
Received: from YTXPR0101MB1615.CANPRD01.PROD.OUTLOOK.COM ([fe80::90ee:fc62:858:74c7]) by YTXPR0101MB1615.CANPRD01.PROD.OUTLOOK.COM ([fe80::90ee:fc62:858:74c7%6]) with mapi id 15.20.2729.032; Wed, 19 Feb 2020 22:25:29 +0000
From: Suresh Krishnan <Suresh@kaloom.com>
To: "Franke, Daniel" <dafranke@akamai.com>
CC: Hal Murray <hmurray@megapathdsl.net>, "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: AQHV50R5ymzgo+YhZkGGE+N0d1sKOKgi08MAgABEr4A=
Date: Wed, 19 Feb 2020 22:25:29 +0000
Message-ID: <5DB7AC6E-2F1E-4735-8CF7-21DD349F1214@kaloom.com>
References: <20200219084813.E4C6840605C@ip-64-139-1-69.sjc.megapath.net> <F9A58B4B-25A7-4652-8963-6849DE359C5A@kaloom.com> <1582136379878.71291@akamai.com>
In-Reply-To: <1582136379878.71291@akamai.com>
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=Suresh@kaloom.com;
x-originating-ip: [45.19.110.76]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: a4115874-4fd7-46e8-f2eb-08d7b58aa04e
x-ms-traffictypediagnostic: YTXPR0101MB1568:
x-microsoft-antispam-prvs: <YTXPR0101MB15682F62DB50F6575EC2C7D2B4100@YTXPR0101MB1568.CANPRD01.PROD.OUTLOOK.COM>
x-ms-oob-tlc-oobclassifiers: OLM:8882;
x-forefront-prvs: 0318501FAE
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(346002)(366004)(396003)(136003)(376002)(39850400004)(199004)(189003)(6486002)(71200400001)(66946007)(4326008)(508600001)(6506007)(66556008)(64756008)(6512007)(66476007)(76116006)(91956017)(4744005)(66446008)(316002)(5660300002)(8676002)(81156014)(86362001)(81166006)(33656002)(2616005)(53546011)(8936002)(2906002)(54906003)(6916009)(186003)(36756003)(26005); DIR:OUT; SFP:1102; SCL:1; SRVR:YTXPR0101MB1568; H:YTXPR0101MB1615.CANPRD01.PROD.OUTLOOK.COM; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:1; MX:1;
received-spf: None (protection.outlook.com: kaloom.com does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: I+p1TqQ9nJ3pu75QlQo0Zk4ZFz/8MNGaK2l573RnQ2HA/zF9M62sIR6g2fgnpNCSLlLbFuNF6IX4qDGRe4WyOht5MEkLLV8d4JgBVQIYWEhrIVJUoDTO6LjFJoYDqkI+YRBVS8+Ce+N35gkCI5O7f9eDO61bXBjRWhXS3DXTYvxWazc3B4vlaVIf9lMIbn/6dbGJXjqe+dxC5Ww0VjidpLd8sftQ/rkaGYH2v6fG5feI0gFQEWgpS6A0fCL4GqIHYfKBhfJvjuZlGn30SQzUuFSjO0Q36YCCGXzHba8AT22KhOcPCgveMvoJGDUrb849MykTvYbd1KCtbEwqD0hu1ANzhF0NS1ieHx1wtZzggFHV1xQfrFCvD4aQFSsny7cEh3i0vzmy4UVDThWbxxFyZVLiFj010qIlT/CA3mN7gcoDII9t+KdxYY/ks5EkvUK5
x-ms-exchange-antispam-messagedata: eJ4HCxYLZp1WLIrPNucILavOCkcXIRu5I62eetuM3goVdrG3af+GojIoUhKcQXy4DXIZQ9pK49BHUEM7gRfWdIb2yOhuJgx6F3sGdxseoz/A/yNAphkV3OHWofr3EfKFuj8UchyXkMBV5svCEEO0uA==
x-ms-exchange-transport-forked: True
Content-Type: multipart/alternative; boundary="_000_5DB7AC6E2F1E47358CF721DD349F1214kaloomcom_"
MIME-Version: 1.0
X-OriginatorOrg: kaloom.com
X-MS-Exchange-CrossTenant-Network-Message-Id: a4115874-4fd7-46e8-f2eb-08d7b58aa04e
X-MS-Exchange-CrossTenant-originalarrivaltime: 19 Feb 2020 22:25:29.4509 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 47d58e26-f796-48e8-ac40-1c365c204513
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: mGAfOrlkbfoAzO6ZeWeK3nZ8BvA0ycneci62LgcGO9mvA4COYhKbZ7Yi6EpRzjexHR8z0XaJmOnqFNAQHs+7UA==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: YTXPR0101MB1568
Archived-At: <https://mailarchive.ietf.org/arch/msg/ntp/3ZcH1dECjMmLzOw8HGWxwkWzC5A>
X-Mailman-Approved-At: Thu, 20 Feb 2020 08:36:01 -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 22:25:36 -0000

Hi Daniel,

On Feb 19, 2020, at 1:19 PM, Franke, Daniel <dafranke@akamai.com<mailto:dafranke@akamai.com>> wrote:

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.


Ah. Thanks for clarifying. That makes sense. I don’t have any issues with this either. As Ben Kaduk said downthread, you can stuff in the currently used values as “requested values” into the draft after the last call completes. I will work with IANA to get these values assigned (I don’t foresee an issue)

Regards
Suresh

v2.23.0 | Report a Bug | By Email