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

"Joel M. Halpern" <jmh@joelhalpern.com> Thu, 26 March 2020 18:46 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 2986E3A079D for <ietfarch-rfc-interest-archive@ietfa.amsl.com>; Thu, 26 Mar 2020 11:46:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.451
X-Spam-Level:
X-Spam-Status: No, score=-2.451 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.249, MAILING_LIST_MULTI=-1, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (1024-bit key) reason="fail (body has been altered)" header.d=joelhalpern.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 efNxiAK-0dDn for <ietfarch-rfc-interest-archive@ietfa.amsl.com>; Thu, 26 Mar 2020 11:46:03 -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 41D9C3A0028 for <rfc-interest-archive-SieQuei0be@ietf.org>; Thu, 26 Mar 2020 11:46:03 -0700 (PDT)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id 71D5FF40713; Thu, 26 Mar 2020 11:45:51 -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 60055F40713 for <rfc-interest@rfc-editor.org>; Thu, 26 Mar 2020 11:45:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at rfc-editor.org
Authentication-Results: rfcpa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=joelhalpern.com
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 WLDCG1mKcnHK for <rfc-interest@rfc-editor.org>; Thu, 26 Mar 2020 11:45:48 -0700 (PDT)
Received: from mailb2.tigertech.net (mailb2.tigertech.net [208.80.4.154]) by rfc-editor.org (Postfix) with ESMTPS id 84A97F40712 for <rfc-interest@rfc-editor.org>; Thu, 26 Mar 2020 11:45:48 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mailb2.tigertech.net (Postfix) with ESMTP id 48pDTM6j3jz1p0fL; Thu, 26 Mar 2020 11:45:59 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=joelhalpern.com; s=2.tigertech; t=1585248359; bh=9TqanqJuFDjawZOjyivnH6ehBKegq+ggx/WBta51xBQ=; h=From:Subject:To:Cc:References:Date:In-Reply-To:From; b=iCCrH6tvfbrpHf/Fhh07tZ+EPJXdXUG70urZEuzvXm1n4EMxwdoBNoG7nulW8TuHl au7ZQmePDKPBZSypEY8YaQd7o9cswKf41daSQqs6394190aQdo4O0PHo6Eq46L7/7o IF3Q8+PyfD8+3erdqh/m18/saRDnVQbL+BNHCccU=
X-Virus-Scanned: Debian amavisd-new at b2.tigertech.net
Received: from [192.168.128.43] (209-255-163-147.ip.mcleodusa.net [209.255.163.147]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mailb2.tigertech.net (Postfix) with ESMTPSA id 48pDTM2wLfz1p0cf; Thu, 26 Mar 2020 11:45:59 -0700 (PDT)
From: "Joel M. Halpern" <jmh@joelhalpern.com>
To: Joe Touch <touch@strayalpha.com>
References: <30855.1585242882@localhost> <59F42CB0-6980-42B3-9A7E-24F601EF8A8D@strayalpha.com>
Message-ID: <5023ce7d-2cc1-9163-b3c0-bc8c66ec6d7f@joelhalpern.com>
Date: Thu, 26 Mar 2020 14:45:58 -0400
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:68.0) Gecko/20100101 Thunderbird/68.6.0
MIME-Version: 1.0
In-Reply-To: <59F42CB0-6980-42B3-9A7E-24F601EF8A8D@strayalpha.com>
Content-Language: en-US
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-Transfer-Encoding: base64
Content-Type: text/plain; charset="utf-8"; Format="flowed"
Errors-To: rfc-interest-bounces@rfc-editor.org
Sender: "rfc-interest" <rfc-interest-bounces@rfc-editor.org>

(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