IETF Logo Mail Archive

Re: [Ntp] Publication has been requested for draft-ietf-ntp-using-nts-for-ntp-20

Miroslav Lichvar <mlichvar@redhat.com> Wed, 13 November 2019 16:07 UTC

Return-Path: <mlichvar@redhat.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 B0A571208DE for <ntp@ietfa.amsl.com>; Wed, 13 Nov 2019 08:07:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.299
X-Spam-Level:
X-Spam-Status: No, score=-4.299 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_MED=-2.3, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=redhat.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 Kam_cAnw-ObO for <ntp@ietfa.amsl.com>; Wed, 13 Nov 2019 08:07:16 -0800 (PST)
Received: from us-smtp-1.mimecast.com (us-smtp-delivery-1.mimecast.com [205.139.110.120]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DF326120862 for <ntp@ietf.org>; Wed, 13 Nov 2019 08:07:15 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1573661234; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=EM4ZPEd5A8ZtKX2QyWen0+hpw1B7DyPLgG1YZtTokF4=; b=NcoFs8nQUx2VuoPp6sKbnzraJuZsULiMPr1bMtAB+F80bXkB47VMPGx6URA/xVOf/pgKWK l+ENZ7degEfbYOrHCZKqYsZffx80EMKo1ctbBTQ1QFap5gza90N57OGMapMkxSTcIAdZdg JwtT5/zURuyKYGwW+wJgxD2JI7hF0vE=
Received: from mimecast-mx01.redhat.com (mimecast-mx01.redhat.com [209.132.183.4]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-70-ewjr2mXEPiqTvUJJZiOVzw-1; Wed, 13 Nov 2019 11:07:13 -0500
Received: from smtp.corp.redhat.com (int-mx06.intmail.prod.int.phx2.redhat.com [10.5.11.16]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx01.redhat.com (Postfix) with ESMTPS id 39C6C8FB8E6 for <ntp@ietf.org>; Wed, 13 Nov 2019 16:07:12 +0000 (UTC)
Received: from localhost (holly.tpb.lab.eng.brq.redhat.com [10.43.134.11]) by smtp.corp.redhat.com (Postfix) with ESMTPS id A5C751726D for <ntp@ietf.org>; Wed, 13 Nov 2019 16:07:11 +0000 (UTC)
Date: Wed, 13 Nov 2019 17:07:10 +0100
From: Miroslav Lichvar <mlichvar@redhat.com>
To: ntp@ietf.org
Message-ID: <20191113160710.GD2634@localhost>
References: <157313897534.2133.12635995715081872821.idtracker@ietfa.amsl.com> <20191113114825.GA1287494@ot.lublin.se>
MIME-Version: 1.0
In-Reply-To: <20191113114825.GA1287494@ot.lublin.se>
User-Agent: Mutt/1.12.1 (2019-06-15)
X-Scanned-By: MIMEDefang 2.79 on 10.5.11.16
X-MC-Unique: ewjr2mXEPiqTvUJJZiOVzw-1
X-Mimecast-Spam-Score: 0
Content-Type: text/plain; charset="WINDOWS-1252"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
Archived-At: <https://mailarchive.ietf.org/arch/msg/ntp/9yxRUBQOUa-f5aCRtrB-yJlCKk0>
Subject: Re: [Ntp] Publication has been requested for draft-ietf-ntp-using-nts-for-ntp-20
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, 13 Nov 2019 16:07:18 -0000

On Wed, Nov 13, 2019 at 12:48:25PM +0100, Daniel Lublin wrote:
> Karen O'Donoghue via Datatracker <noreply@ietf.org>, 2019-11-07 07:02:55 (-0800):
> > Karen O&#39;Donoghue has requested publication of draft-ietf-ntp-using-nts-for-ntp-20 as Proposed Standard on behalf of the NTP working group.
> > 
> > Please verify the document's state at https://datatracker.ietf.org/doc/draft-ietf-ntp-using-nts-for-ntp/
> 
> As was mentioned on the list in July, section "1.2. Protocol Overview" is
> outdated. It says, wrongly:
> 
>    with a list of one or more IP addresses to NTP servers for which the cookies

Is it wrong to interpret a FQDN as a list of addresses?

> but should say:
> 
>    with an address to the NTP server for which the cookies

Or maybe "with an address or name"?

> Or something similar, in singular!
> 
> For reference, see "4.1.7. NTPv4 Server Negotiation":
> 
>    Its body consists of an ASCII-encoded [ANSI.X3-4.1986] string. The
>    contents of the string SHALL be either an IPv4 address in dotted decimal
>    notation, an IPv6 address, or a fully qualified domain name (FQDN).

-- 
Miroslav Lichvar

v2.23.0 | Report a Bug | By Email