Re: [Iasa20] draft-ietf-iasa2-rfc2418bis-01.txt

John C Klensin <john-ietf@jck.com> Sat, 20 October 2018 21:27 UTC

Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AA31F130E0C; Sat, 20 Oct 2018 14:27:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001] 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 NSUFETXE_rfR; Sat, 20 Oct 2018 14:27:27 -0700 (PDT)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9AFA1130DF9; Sat, 20 Oct 2018 14:27:27 -0700 (PDT)
Received: from [198.252.137.10] (helo=PSB) by bsa2.jck.com with esmtp (Exim 4.82 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1gDymL-000H1t-PS; Sat, 20 Oct 2018 17:27:25 -0400
Date: Sat, 20 Oct 2018 17:27:18 -0400
From: John C Klensin <john-ietf@jck.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
cc: ietf@ietf.org, sob@sobco.com, rsalz@akamai.com, iasa20@ietf.org
Subject: Re: [Iasa20] draft-ietf-iasa2-rfc2418bis-01.txt
Message-ID: <1C77C07809EFB402E3E10907@PSB>
In-Reply-To: <8906b727-f9c3-e7e1-164b-f7b88e48e74b@gmail.com>
References: <4915CD062D28D607D3D4AD44@PSB> <8906b727-f9c3-e7e1-164b-f7b88e48e74b@gmail.com>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-SA-Exim-Connect-IP: 198.252.137.10
X-SA-Exim-Mail-From: john-ietf@jck.com
X-SA-Exim-Scanned: No (on bsa2.jck.com); SAEximRunCond expanded to false
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/XSWHz5uGx5_IsYOWJPCYRGoFkzw>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 20 Oct 2018 21:27:29 -0000


--On Sunday, October 21, 2018 10:07 +1300 Brian E Carpenter
<brian.e.carpenter@gmail.com> wrote:

> fwiw I agree. There is no reference to IASA in 2418, for
> obvious reasons.
> 
> From a practical point of view, any terminology issue could
> be handled
> as an erratum with disposition "wait for update".

That, IMO, would be an even better solution than creating an
updating document that says "any time earlier documents say
'IETF Executive Director' replace it with..." and similar things
and then hunting down the relevant documents and marking them as
updated.  

Depending on how compulsive the WG and relevant AD are feeling,
I think either would work.  But we really have better ways to
spend our time than replacing a process document to change a
title... or at least I hope we do.  

Frankly, the only good reason I can see for generating all of
these IASA2 documents just to change terminology is to create
enough noise that the community doesn't notice and pay attention
to changes that actually might be controversial.   I trust and
assume that is not the intent of anyone involved.

    john