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)

Karen O'Donoghue <> Thu, 20 February 2020 08:55 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 1180E120864 for <>; Thu, 20 Feb 2020 00:55:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.001
X-Spam-Status: No, score=-2.001 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (1024-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id ffy5av3x9KOi for <>; Thu, 20 Feb 2020 00:55:56 -0800 (PST)
Received: from ( []) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 0A2F01201E4 for <>; Thu, 20 Feb 2020 00:55:56 -0800 (PST)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901;; cv=none; b=KS6NQuya5kW4KdPDPfhbb5L9zQUlaMwgI0KN7IkiFiORAaQw1ue597wiRbecCpKSnzNKIggFBJ5pcQndb23t1+Fw/RuGAZ3vnaQMpOu8UOagden1X/aIS5da6ZoWZ1LVHoWv6RqhW2GikOQGkVZiTmCmkOlYfEKunU/049yAP80ZNj2D5vA7Om38Ea4uYBDbLS5qgJzQL3Ydc5VEs4DNiWvfvQKjdF18Mli80jmc7YUe3JM5SoK1rNp8AQKt1UvGYiM68tOIowJWsdjg7Ac9ImPkbc4x7CrBah9IZ5ITH/OBwdNOhkoOtuDXlvTpT2j0OOtD96/2MtnTGsOXfkWYsw==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed;; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=mQhOJR5CyvGKTO5l2KMCGgl7bzE09Mp9XoxjlZqbmmM=; b=jrA74SBXkpCrydLGW+w+bNqdKvAUEp0ssfEh9cwn48u76GsU/t5byw4AFkAmQdVqVQdBL988iWvN4Ef1Db6LE7YsgDl5EwqqOum8kK7TgmiNPxoGLn64EusM5UUdQ0eY4d6+RTpf2jGp1iiygAD4ZkG4YBfMQ45uf78JEQ9pZL6q2wEhSd4+CZO4LpWMklx6NZg3cygupKEg1q+kjnN3yO13KoGYk4rGjpg1neHidfUZmdzXr9m+PPXWVyKUWfpbIeQHy1XJC048C4nXp7ayRgFI2lTbew+c4mEo23lpIV6yt/zNZ+oLFE4uUTlk1SN1Yu8JFh6JlOW9x9mFSFxvuA==
ARC-Authentication-Results: i=1; 1; spf=pass; dmarc=pass action=none; dkim=pass; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=selector2; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=mQhOJR5CyvGKTO5l2KMCGgl7bzE09Mp9XoxjlZqbmmM=; b=oTlTB7FDYpzd52WMNqwhDi9KwBSZW9rRv53kFVVr8v4T64ua6yjndRwSClQEekzOYSVTZJJh2o9KRZN+0JNZQtIhA8mlxEetJAiOVYonWFrZrMz4Il+yJa+umfwdOUp1ZdBy9g/Y5mTl+JfdQf/5y8daLmLPVotQ6AuzKNwgxG8=
Received: from (2603:10b6:3:3b::23) by (2603:10b6:4:3d::30) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2750.17; Thu, 20 Feb 2020 08:55:53 +0000
Received: from ([fe80::e8ad:b2bc:a48b:7b8]) by ([fe80::e8ad:b2bc:a48b:7b8%11]) with mapi id 15.20.2729.033; Thu, 20 Feb 2020 08:55:53 +0000
From: Karen O'Donoghue <>
To: Daniel Franke <>
CC: NTP WG <>, Harlan Stenn <>, Watson Ladd <>
Thread-Topic: [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)
Thread-Index: AQHV52xHFA31IVQBTESYPmdjcmambKgjENKA//+0YgCAAL6fAP//8J+A
Date: Thu, 20 Feb 2020 08:55:53 +0000
Message-ID: <>
References: <> <> <> <> <> <> <>
In-Reply-To: <>
Accept-Language: en-US
Content-Language: en-US
authentication-results: spf=none (sender IP is );
x-originating-ip: []
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 9325507e-abbe-4cee-32da-08d7b5e2b13e
x-ms-traffictypediagnostic: DM5PR06MB3227:
x-microsoft-antispam-prvs: <>
x-ms-oob-tlc-oobclassifiers: OLM:10000;
x-forefront-prvs: 031996B7EF
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(39850400004)(346002)(136003)(376002)(396003)(366004)(199004)(189003)(6512007)(316002)(26005)(8936002)(5660300002)(2906002)(71200400001)(6916009)(478600001)(81166006)(4326008)(8676002)(81156014)(54906003)(2616005)(86362001)(6506007)(53546011)(15650500001)(66446008)(36756003)(66946007)(33656002)(6486002)(66476007)(64756008)(66556008)(91956017)(186003)(76116006); DIR:OUT; SFP:1101; SCL:1; SRVR:DM5PR06MB3227;; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:1; MX:1;
received-spf: None ( does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: qghJMrV6SF/eXTLXNbkf2dAP0WMWkhHGzieK/MTFE4eME9Op4ovWiZOk+Rnvpx7ExoyTIrnLMvRt8C6ZicXuD5FgrnS7pm+lVd6ylDAQMgxSXwxEJOoNbhvbFzK/lUQiEp1OaWtk2Oj7uzqJcy397RPZ1Z7GnT7ib7ANw40z1gQARENNBp+kWGw/BnhaFWLG6RSjocbXwnRtBcgUh/tNfx22kRdfBZyGo6dCFL7RfGFqSBESqashD4pxNA3tRHjcGunUJNizGdpGa1UH7MBUvMsTGf63pJqXc9fAVwDcyYlz/33Q0moUDfrKhn+5p+4z+AEvKjvsoNEWS34rWxLwwkZdJitrhzDmUSIFu2m4RLIOV3S3a3Z8tYZQ7MnxzhKWO4b9HZDJ8xeDupyMe6UnpbG/oQWRXRQ8RoXtiveuuyDP/aRJ+mqZxsH3BTnvA2wz
x-ms-exchange-antispam-messagedata: 4MUhdym7A9VDsrDwyVID9Vvvx5ncQjMSZQORd2hM0bpMhwh+WxnWylUijScNTGT5FyZkGTn9uRbxnED2PqKVcD06TFRv/JaHBnI1idBQPDVLR18oRhO+j2C3dZPhMXDYOXLNR/zLvFp0V8IVLxbDZg==
x-ms-exchange-transport-forked: True
Content-Type: text/plain; charset="utf-8"
Content-ID: <>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: 9325507e-abbe-4cee-32da-08d7b5e2b13e
X-MS-Exchange-CrossTenant-originalarrivaltime: 20 Feb 2020 08:55:53.5694 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 89f84dfb-7285-4810-bc4d-8b9b5794554f
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: p11o0Kfojczq28sTZZQRty+GY54n1PjrrSsI1sP+/OBVQ+BdloKBP2hD5PRALePAxf5qrXNTyB0mJRviknoNYA==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DM5PR06MB3227
Archived-At: <>
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-Mailman-Version: 2.1.29
Precedence: list
List-Id: <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Thu, 20 Feb 2020 08:55:58 -0000

On 2/19/20, 11:51 PM, "Daniel Franke" <> wrote:

    On Wed, Feb 19, 2020 at 5:28 PM Karen O'Donoghue <> wrote:
    > We can do two things:
    > 1) Quickly come to consensus with the implementers, authors, and working group on an update to the IANA considerations text that we can add between IETF Last Call and the IESG vote.
    > 2) Do nothing and let the IANA folks do what they will... (do you really want this to happen?!?)
    It seems to me we already have consensus. Everyone who's spoken up
    prefers that we ask IANA to register the numbers we've been squatting
    on. Some have added that if the numbers get changed, then they can
    live with that. I've already asked Hal Murray to submit a PR adding
    the requested numbers to the draft, but I'll take it from whomever
    submits one first.

<kfo> I have seen a lot of discussion and possibly consensus, but I haven't seen concrete text that articulates that consensus. The document is now a working group document, and given the amount of discussion around this topic, I would like to see the text agreed to before it is incorporated into the document. As you say it shouldn't be that hard, so someone please propose some text on the list, we'll discuss, determine consensus, and then you can incorporate it. 
    This makes the argument over whether EF type codes have any structure
    irrelevant because the codes we've been squatting already conform to
    the structure that Harlan asserts exists. But the argument is also out
    of order in general, because it's already been settled. Last year or
    so Harlan sought adoption of a draft laying out this structure. That
    draft is now a dead document because the response to the call for
    adoption was overwhelming and unanimous in opposition to it.
<kfo> You are correct that the Extension Field draft did not get adopted last year. However, there was a great deal more in that draft than just instructions or possible structuring for the assignment of the code points for EFs. This is still a topic that we could potentially resolve with a much more narrowly scoped document - if we chose to do so. Or we could move it to the potential future ntpv5 effort.