[Ntp] Antw: [EXT] Fwd: New Version Notification for draft‑gruessing‑ntp‑ntpv5‑requirements‑03.txt

Ulrich Windl <Ulrich.Windl@rz.uni-regensburg.de> Mon, 11 October 2021 07:19 UTC

Return-Path: <Ulrich.Windl@rz.uni-regensburg.de>
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 52AA73A045B for <ntp@ietfa.amsl.com>; Mon, 11 Oct 2021 00:19:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 Q9NGUkji6fCa for <ntp@ietfa.amsl.com>; Mon, 11 Oct 2021 00:18:53 -0700 (PDT)
Received: from mx2.uni-regensburg.de (mx2.uni-regensburg.de [IPv6:2001:638:a05:137:165:0:3:bdf8]) (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 891973A044D for <ntp@ietf.org>; Mon, 11 Oct 2021 00:18:51 -0700 (PDT)
Received: from mx2.uni-regensburg.de (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id 1701B6000052 for <ntp@ietf.org>; Mon, 11 Oct 2021 09:18:46 +0200 (CEST)
Received: from gwsmtp.uni-regensburg.de (gwsmtp1.uni-regensburg.de [132.199.5.51]) by mx2.uni-regensburg.de (Postfix) with ESMTP id B783A600004D for <ntp@ietf.org>; Mon, 11 Oct 2021 09:18:44 +0200 (CEST)
Received: from uni-regensburg-smtp1-MTA by gwsmtp.uni-regensburg.de with Novell_GroupWise; Mon, 11 Oct 2021 09:18:44 +0200
Message-Id: <6163E552020000A10004462F@gwsmtp.uni-regensburg.de>
X-Mailer: Novell GroupWise Internet Agent 18.3.1
Date: Mon, 11 Oct 2021 09:18:42 +0200
From: Ulrich Windl <Ulrich.Windl@rz.uni-regensburg.de>
To: james.ietf@gmail.com, "ntp@ietf.org" <ntp@ietf.org>
References: <163386015957.12424.6997038478834885480@ietfa.amsl.com> <CAO+dDx=6baLhf9LwSMvR1F0ieuLO6NXmExYLDvcCF2tgchHs8w@mail.gmail.com>
In-Reply-To: <CAO+dDx=6baLhf9LwSMvR1F0ieuLO6NXmExYLDvcCF2tgchHs8w@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 8bit
Content-Disposition: inline
Archived-At: <https://mailarchive.ietf.org/arch/msg/ntp/iZ_UOwpz39hya584zROskeuMqHU>
Subject: [Ntp] Antw: [EXT] Fwd: New Version Notification for draft‑gruessing‑ntp‑ntpv5‑requirements‑03.txt
X-BeenThere: ntp@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Network Time Protocol <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: Mon, 11 Oct 2021 07:19:03 -0000

Hi!

I wonder: Should "gruessing" be "guessing" actually?

Regards,
Ulrich

>>> James <james.ietf@gmail.com> schrieb am 10.10.2021 um 20:01 in Nachricht
<CAO+dDx=6baLhf9LwSMvR1F0ieuLO6NXmExYLDvcCF2tgchHs8w@mail.gmail.com>:
> Despite saying I was going to hold off making a new version, I've made
> some changes to prevent expiration ahead of IETF 112, including an
> initial threat model and other minor changes.
> The working group's feedback as always would be appreciated.
> 
> ‑ J
> 
> ‑‑‑‑‑‑‑‑‑‑ Forwarded message ‑‑‑‑‑‑‑‑‑
> From: <internet‑drafts@ietf.org>
> Date: Sun, 10 Oct 2021 at 10:02
> Subject: New Version Notification for
> draft‑gruessing‑ntp‑ntpv5‑requirements‑03.txt
> To: James Gruessing <james.ietf@gmail.com>
> 
> 
> 
> A new version of I‑D, draft‑gruessing‑ntp‑ntpv5‑requirements‑03.txt
> has been successfully submitted by James Gruessing and posted to the
> IETF repository.
> 
> Name:           draft‑gruessing‑ntp‑ntpv5‑requirements
> Revision:       03
> Title:          NTPv5 use cases and requirements
> Document date:  2021‑10‑10
> Group:          Individual Submission
> Pages:          8
> URL:
>
https://www.ietf.org/archive/id/draft‑gruessing‑ntp‑ntpv5‑requirements‑03.txt

> Status:
> https://datatracker.ietf.org/doc/draft‑gruessing‑ntp‑ntpv5‑requirements/ 
> Htmlized:
> https://datatracker.ietf.org/doc/html/draft‑gruessing‑ntp‑ntpv5‑requirements

> Diff:
> https://www.ietf.org/rfcdiff?url2=draft‑gruessing‑ntp‑ntpv5‑requirements‑03

> 
> Abstract:
>    This document describes the use cases, requirements, and
>    considerations that should be factored in the design of a successor
>    protocol to supersede version 4 of the NTP protocol [RFC5905]
>    presently referred to as NTP version 5 ("NTPv5").  This document is
>    non‑exhaustive and does not in its current version represent working
>    group consensus.
> 
> 
> 
> 
> The IETF Secretariat
> 
> _______________________________________________
> ntp mailing list
> ntp@ietf.org 
> https://www.ietf.org/mailman/listinfo/ntp