Re: [rfc-i] draft-kuehlewind-update-tag/

Toerless Eckert <tte@cs.fau.de> Thu, 26 March 2020 18:56 UTC

Return-Path: <rfc-interest-bounces@rfc-editor.org>
X-Original-To: ietfarch-rfc-interest-archive@ietfa.amsl.com
Delivered-To: ietfarch-rfc-interest-archive@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id ACDBD3A094D for <ietfarch-rfc-interest-archive@ietfa.amsl.com>; Thu, 26 Mar 2020 11:56:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.651
X-Spam-Level:
X-Spam-Status: No, score=-2.651 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.249, MAILING_LIST_MULTI=-1, 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 UvpotlqhmHNq for <ietfarch-rfc-interest-archive@ietfa.amsl.com>; Thu, 26 Mar 2020 11:56:52 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 115873A080F for <rfc-interest-archive-SieQuei0be@ietf.org>; Thu, 26 Mar 2020 11:56:52 -0700 (PDT)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id 457BBF40713; Thu, 26 Mar 2020 11:56:40 -0700 (PDT)
X-Original-To: rfc-interest@rfc-editor.org
Delivered-To: rfc-interest@rfc-editor.org
Received: from localhost (localhost [127.0.0.1]) by rfc-editor.org (Postfix) with ESMTP id 5B325F40713 for <rfc-interest@rfc-editor.org>; Thu, 26 Mar 2020 11:56:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at rfc-editor.org
Received: from rfc-editor.org ([127.0.0.1]) by localhost (rfcpa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id b8QBt5M1rE4X for <rfc-interest@rfc-editor.org>; Thu, 26 Mar 2020 11:56:36 -0700 (PDT)
Received: from faui40.informatik.uni-erlangen.de (faui40.informatik.uni-erlangen.de [131.188.34.40]) by rfc-editor.org (Postfix) with ESMTPS id 2238BF40712 for <rfc-interest@rfc-editor.org>; Thu, 26 Mar 2020 11:56:35 -0700 (PDT)
Received: from faui48f.informatik.uni-erlangen.de (faui48f.informatik.uni-erlangen.de [IPv6:2001:638:a000:4134::ffff:52]) by faui40.informatik.uni-erlangen.de (Postfix) with ESMTP id 8C8B654804A; Thu, 26 Mar 2020 19:56:41 +0100 (CET)
Received: by faui48f.informatik.uni-erlangen.de (Postfix, from userid 10463) id 8676D440040; Thu, 26 Mar 2020 19:56:41 +0100 (CET)
Date: Thu, 26 Mar 2020 19:56:41 +0100
From: Toerless Eckert <tte@cs.fau.de>
To: "Joel M. Halpern" <jmh@joelhalpern.com>
Message-ID: <20200326185641.GZ30574@faui48f.informatik.uni-erlangen.de>
References: <30855.1585242882@localhost> <59F42CB0-6980-42B3-9A7E-24F601EF8A8D@strayalpha.com> <5023ce7d-2cc1-9163-b3c0-bc8c66ec6d7f@joelhalpern.com>
MIME-Version: 1.0
Content-Disposition: inline
In-Reply-To: <5023ce7d-2cc1-9163-b3c0-bc8c66ec6d7f@joelhalpern.com>
User-Agent: Mutt/1.10.1 (2018-07-13)
Subject: Re: [rfc-i] draft-kuehlewind-update-tag/
X-BeenThere: rfc-interest@rfc-editor.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "A list for discussion of the RFC series and RFC Editor functions." <rfc-interest.rfc-editor.org>
List-Unsubscribe: <https://www.rfc-editor.org/mailman/options/rfc-interest>, <mailto:rfc-interest-request@rfc-editor.org?subject=unsubscribe>
List-Archive: <http://www.rfc-editor.org/pipermail/rfc-interest/>
List-Post: <mailto:rfc-interest@rfc-editor.org>
List-Help: <mailto:rfc-interest-request@rfc-editor.org?subject=help>
List-Subscribe: <https://www.rfc-editor.org/mailman/listinfo/rfc-interest>, <mailto:rfc-interest-request@rfc-editor.org?subject=subscribe>
Cc: "rfc-interest@rfc-editor.org" <rfc-interest@rfc-editor.org>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: rfc-interest-bounces@rfc-editor.org
Sender: "rfc-interest" <rfc-interest-bounces@rfc-editor.org>

I would appreciate if we would first or at least also work on guidance
for what needs to go into an "update to RFCXXXX" section for new
documents. Once we are clear about at the things that should be
said (how prir doc is changed, what impact on interop thia
results in, ..), it will be a lot easier to figure out if there are simple
classifications that could go into metadata. Then its yet a third
step whether we should try to expand/proliferate on our rather
old metadata approach or go with newer approaches like what Mcr
suggested.

Cheeers
    toerless

On Thu, Mar 26, 2020 at 02:45:58PM -0400, Joel M. Halpern wrote:
> (Resend.)
> 
> Joe, we all know that the formal words we use do not have the same meaning
> that they do in English.  Our standards are not, effectively, "requests for
> comment".  They are standards.
> We also know by observation that other people have understood "Updates" in
> ways that are different from how you understand it.  Claiming that the
> meaning as used for metadata on RFCs is "obvious to any English speaker" is
> contradicted by the observable facts.
> 
> Yours,
> Joel
> 
> On 3/26/2020 1:25 PM, Joe Touch wrote:
> > 
> > 
> > > On Mar 26, 2020, at 10:14 AM, Michael Richardson <mcr+ietf@sandelman.ca> wrote:
> > > 
> > > > ???Updates??? means just that - it affects the base document in a way that
> > > > MIGHT be hazardous to ignore. That means you need to read the doc to
> > > > find out why, to what extent, and how that affects what you want to
> > > > do.
> > > 
> > > I wonder if you can recognize that this might not be the only way it has been
> > > used in the past.  Maybe those uses were in error, but you've picked a
> > > particular definition that wasn't always applied.
> > 
> > I do. Adding terms doesn???t make that more clear or useful. Updates means changes of any nature that do not replace the prior RFC in its entirety.
> > 
> > If that isn???t obvious to any English speaker, then these nuanced other terms that subdivide that category further definitely will not help.
> > 
> > Joe
> > 
> _______________________________________________
> rfc-interest mailing list
> rfc-interest@rfc-editor.org
> https://www.rfc-editor.org/mailman/listinfo/rfc-interest

-- 
---
tte@cs.fau.de
_______________________________________________
rfc-interest mailing list
rfc-interest@rfc-editor.org
https://www.rfc-editor.org/mailman/listinfo/rfc-interest