Re: [Ntp] Comments on draft-langer-ntp-nts-for-ptp

Miroslav Lichvar <> Mon, 08 March 2021 16:00 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 780C03A2CCE for <>; Mon, 8 Mar 2021 08:00:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.367
X-Spam-Status: No, score=-2.367 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.248, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (1024-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id ZotQECH0iVsC for <>; Mon, 8 Mar 2021 08:00:10 -0800 (PST)
Received: from ( []) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id E90883A2CCD for <>; Mon, 8 Mar 2021 08:00:09 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=mimecast20190719; t=1615219209; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=j3i3cQm7zUsGg34E3O19wMZOJiNjgB4vRIWlqgzjdeA=; b=PHZDhhi5p4PLOE4k4m0YEbTCStKtSFP+wSP3QTRvSHWMHCtBdSqJPso8qFJSwOvwCu+3pE OdKwouH2+qb+yr77Te8zAY2Pq8MGRv6XW5uKOnvtA3IKCtbhnPER9aNtt5ki6uA35YV8iH QirsUyBcmKZkyPXbtqt1RyPhroTNTFE=
Received: from ( []) (Using TLS) by with ESMTP id us-mta-89-5ytXxa5OMb-AGoHzpomP1w-1; Mon, 08 Mar 2021 11:00:06 -0500
X-MC-Unique: 5ytXxa5OMb-AGoHzpomP1w-1
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 4FF5619057A0; Mon, 8 Mar 2021 16:00:05 +0000 (UTC)
Received: from localhost ( []) by (Postfix) with ESMTPS id 77F315D6D7; Mon, 8 Mar 2021 16:00:03 +0000 (UTC)
Date: Mon, 8 Mar 2021 17:00:01 +0100
From: Miroslav Lichvar <>
To: Heiko Gerstung <>
Cc: Watson Ladd <>, NTP WG <>, "Langer, Martin" <>
Message-ID: <YEZKAbw2xc2yvDis@localhost>
References: <> <> <> <YEYHHhIrYv4ZhTkl@localhost> <> <YEYhUyx1r6aAO1Xi@localhost> <>
MIME-Version: 1.0
In-Reply-To: <>
X-Scanned-By: MIMEDefang 2.79 on
Authentication-Results:; auth=pass smtp.auth=CUSA124A263
X-Mimecast-Spam-Score: 0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Archived-At: <>
Subject: Re: [Ntp] Comments on draft-langer-ntp-nts-for-ptp
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Mon, 08 Mar 2021 16:00:12 -0000

On Mon, Mar 08, 2021 at 02:31:04PM +0100, Heiko Gerstung wrote:
> >    If you don't have any client-specific state on the server (and
> >    hardcode the address in the cookie), how do you prevent replay
> >    attacks, e.g. canceling a previous request, or changing the message
> >    rate to a previous value, or requesting unicast transmissions for
> >    clients that no longer exist to cause a DoS attack on the server?
> Not sure what you mean with "hardcode the address in the cookie", 

That the client's address is included in the cookie to prevent
replaying from other addresses.

> but in order to change the message rate or cancel a unicast transmission, an NTS4PTP client would have to present a valid cookie. Replay attacks could be prevented by adding an expiration field into the cookie after which a GM will not accept it anymore. 

I don't see how could that work.

How would the server know when will be the cookie used? Even if it had
only one cookie, it could be used at any time, e.g. to cancel the
grant when it is shutting down. If it was started soon again, that
cookie which authenticated the cancelation request would still be

Miroslav Lichvar