[Ntp] Antw: [EXT] Re: "Extensions" vs. "Extension Fields"

Ulrich Windl <Ulrich.Windl@rz.uni-regensburg.de> Tue, 29 September 2020 10:06 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 05A393A0AC3 for <ntp@ietfa.amsl.com>; Tue, 29 Sep 2020 03:06:16 -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 wCRMXHgXQQZR for <ntp@ietfa.amsl.com>; Tue, 29 Sep 2020 03:06:12 -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 A8FF13A0ABE for <ntp@ietf.org>; Tue, 29 Sep 2020 03:06:11 -0700 (PDT)
Received: from mx2.uni-regensburg.de (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id 63FF36000056 for <ntp@ietf.org>; Tue, 29 Sep 2020 12:06:06 +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 8200E600004D for <ntp@ietf.org>; Tue, 29 Sep 2020 12:06:03 +0200 (CEST)
Received: from uni-regensburg-smtp1-MTA by gwsmtp.uni-regensburg.de with Novell_GroupWise; Tue, 29 Sep 2020 12:06:04 +0200
Message-Id: <5F73070A020000A10003B9E1@gwsmtp.uni-regensburg.de>
X-Mailer: Novell GroupWise Internet Agent 18.2.1
Date: Tue, 29 Sep 2020 12:06:02 +0200
From: Ulrich Windl <Ulrich.Windl@rz.uni-regensburg.de>
To: Daniel Franke <dfoxfranke@gmail.com>, Tal Mizrahi <tal.mizrahi.phd@gmail.com>, doug.arnold@meinberg-usa.com, Danny Mayer <mayer@ntp.org>, mills@udel.edu
Cc: "ntp@ietf.org" <ntp@ietf.org>
References: <CAJm83bARMjKX5KzWSsS1d3hqSR52g9JveGv-Lw36cYcX_PCfCQ@mail.gmail.com> <CAJm83bBtMcE2MwPVR0zms0pAaFEE12u+sXWx3c1pRid08iwUPQ@mail.gmail.com> <CAJm83bDLv=woxReko979JHsL6Ck0ng5cQcbZcOZntbLHO63C7g@mail.gmail.com> <4F54FAF2-21B6-4032-BC94-18E12EC84F5A@meinberg-usa.com>
In-Reply-To: <4F54FAF2-21B6-4032-BC94-18E12EC84F5A@meinberg-usa.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/5wgUX1MiSjE1kRpfZAE4uNNtIWg>
Subject: [Ntp] Antw: [EXT] Re: "Extensions" vs. "Extension Fields"
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: Tue, 29 Sep 2020 10:06:16 -0000

>>> Doug Arnold <doug.arnold@meinberg-usa.com> schrieb am 18.09.2020 um 00:01
in
Nachricht <4F54FAF2-21B6-4032-BC94-18E12EC84F5A@meinberg-usa.com>:
> Making a distinction between extensions and extension fields might make it 
> clearer to the reader.

What if you used "extension field syntax" instead of "extension field(s)"?
IMHO it would be even more clear. Sorry for the late response; I had been away
from E_Mail for two weeks....

> 
> Doug
> 
> On 9/17/20, 11:23 AM, "ntp on behalf of Daniel Franke"
<ntp-bounces@ietf.org 
> on behalf of dfoxfranke@gmail.com> wrote:
> 
>     And furthermore my addresses for Jim, Jack, and William seem to be
>     bouncing. Oh well, hoping they're still subscribed to this list.
> 
>     On Thu, Sep 17, 2020 at 11:20 AM Daniel Franke <dfoxfranke@gmail.com> 
> wrote:
>     >
>     > The email expansions I used to address the RFC 5905 / 7822 authors
>     > don't seem to be working. Resending with those authors' addresses
>     > given directly.
>     >
>     > On Thu, Sep 17, 2020 at 11:12 AM Daniel Franke <dfoxfranke@gmail.com>

> wrote:
>     > >
>     > > Dave, Jim, Jack, William, Tal, Danny:
>     > >
>     > > draft-ietf-ntp-using-nts-for-ntp has been reviewed by the RFC
editor
>     > > and is now in AUTH48. I want an opinion from the six of you before
I
>     > > respond to one of the proposed edits.
>     > >
>     > > The RFC editor has proposed to change several uses of "NTS
Extensions"
>     > > to "NTS Extension Fields". However, my usage of one vs. the other
was
>     > > deliberate. When I refer to "extension fields", I am speaking
purely
>     > > syntactically, i.e., discussing the bits on the wire. When I refer
to
>     > > "extensions", I'm referring to the whole semiotic package: not only
to
>     > > syntax of the fields but also to the protocol semantics and
business
>     > > logic that accompany them.
>     > >
>     > > What I want to know from you six, as the authors of RFC 5905 and
7822,
>     > > is not so much whether you think it's a good idea to make this
>     > > distinction, but whether you *already had this distinction in mind*
at
>     > > the time you wrote those documents. If any of you tell me that
you've
>     > > been thinking in those terms all along, then I'll take that as
>     > > vindication and reply to the RFC editor accordingly. If none of you
>     > > do, then I'll accept the edit and use "extension fields"
everywhere,
>     > > because my intent here was to follow existing terminology and not
to
>     > > coin anything new.
> 
>     _______________________________________________
>     ntp mailing list
>     ntp@ietf.org 
>     https://www.ietf.org/mailman/listinfo/ntp 
> 
> _______________________________________________
> ntp mailing list
> ntp@ietf.org 
> https://www.ietf.org/mailman/listinfo/ntp