Re: [Iasa20] draft-ietf-iasa2-rfc2418bis-01.txt
Alissa Cooper <alissa@cooperw.in> Mon, 22 October 2018 09:43 UTC
Return-Path: <alissa@cooperw.in>
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 053CC130E12; Mon, 22 Oct 2018 02:43:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level:
X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=cooperw.in header.b=lJ7QozrG; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=RvxkaEuk
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 Qa73X83D5uke; Mon, 22 Oct 2018 02:43:36 -0700 (PDT)
Received: from out3-smtp.messagingengine.com (out3-smtp.messagingengine.com [66.111.4.27]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0FC80130E13; Mon, 22 Oct 2018 02:43:34 -0700 (PDT)
Received: from compute7.internal (compute7.nyi.internal [10.202.2.47]) by mailout.nyi.internal (Postfix) with ESMTP id 6B9A922115; Mon, 22 Oct 2018 05:43:33 -0400 (EDT)
Received: from mailfrontend1 ([10.202.2.162]) by compute7.internal (MEProxy); Mon, 22 Oct 2018 05:43:33 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cooperw.in; h= content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; s=fm1; bh=i Z4xXlbr2a0DViVDif7SOodf8fDV+mPCF2BhidnlvTg=; b=lJ7QozrGeVard1HiU k7R/2ldIKgxIb5miUnifw+u2VeWglObA7GDVkDQiAsD7nPzlropEDZOpbq+OyGge nBV1AyK/GgOXO/849amCsYlY0/uJGRt0jwn5YfuHBiVjjr2Pytcw4tiTzIn6Z4aV QniKN4d8aZ0kz/SyGtPg7P8BWx6l34quEDHveSnteWHstXYhlNBdUaMpgQcW1Moy F+7N/IaLOQy59W6wW/6OapaX5dS8S+HHq4U3ahBrSz2zILgxRIUR8AUkWZ5kSWQX 7Xba9EFYBGK6Wqsrm3966hC/VH5VQ5kaKq8nHdnUZwfqttC9Gsok8cK526BkMQrG cSRFw==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm1; bh=iZ4xXlbr2a0DViVDif7SOodf8fDV+mPCF2Bhidnlv Tg=; b=RvxkaEukJAbPRKlrvH0DOR0b6I4pGPCvhuF9Yd6RB4WRBFTByCSL7tfFi uP6b1ADNqecLBXiddIuTj1Dqo1WKjfOMXKn93N/k2Ky64grECEh7PEYFC+o+5LTY Xmj+sVY/tXr3WRRtqCoyh1VzvCE7veBdShYkLSEABi82HshvJz7lEHF2jdUIXOWD NJkQHAMyElsvnX90PHrf3PeRqQVPIa3w5oRTIK5ZVEeuFiD0aaIeaf6Rxs+85p0d yj022o2507U4OJ5LNi24f2RZ7zdjrPT0UeRuFlKfNeIUC65VMdgLF2vDuMT/eG+i oE/+atEkwPThK5mH5UntwFX9gO+VQ==
X-ME-Sender: <xms:xJvNW2Z8RrKW9l6pOiHsrKbNS2cLJE3gJxA96jIgELhLhi88kQZ5cQ>
X-ME-Proxy: <xmx:xJvNW2xz84jRTjIY2jCSyBFU2H8zHTFSVAl8e3mhpoNdux7y4PUivQ> <xmx:xJvNWzt_2souwKhnzb_gVnBaILYTsR-20H8u94AARgm99yuPksjJGA> <xmx:xJvNWztmcUYDVpVE_-_wZCNzfASFMbmQbgJ-u23yMnk8I3rI29l9tQ> <xmx:xJvNW5l95GJ52ZnMLoUL3RWSephtUPQ2EPXQng64WYATJ4aYrl_Y_Q> <xmx:xJvNW5vH_ldaUZ7M1X6eZNn5cCh3ESBPQnHz4M7xbhFIvQdkVhLbAA> <xmx:xZvNW_TEAxOUTQL2nJBgKjDIfvtZbWFOMzkhJopgEcSfDMnCJ8lCmw>
Received: from [10.43.177.37] (mobile-166-171-59-92.mycingular.net [166.171.59.92]) by mail.messagingengine.com (Postfix) with ESMTPA id EE864E4899; Mon, 22 Oct 2018 05:43:31 -0400 (EDT)
Content-Type: multipart/alternative; boundary="Apple-Mail-5275FE2E-1F1C-4933-A007-8F536030AB89"
Mime-Version: 1.0 (1.0)
Subject: Re: [Iasa20] draft-ietf-iasa2-rfc2418bis-01.txt
From: Alissa Cooper <alissa@cooperw.in>
X-Mailer: iPhone Mail (16A366)
In-Reply-To: <1C77C07809EFB402E3E10907@PSB>
Date: Mon, 22 Oct 2018 05:43:30 -0400
Cc: Brian E Carpenter <brian.e.carpenter@gmail.com>, rsalz@akamai.com, iasa20@ietf.org, ietf@ietf.org, sob@sobco.com
Content-Transfer-Encoding: 7bit
Message-Id: <F955E5C3-6236-4F98-B531-EE39C4280A3F@cooperw.in>
References: <4915CD062D28D607D3D4AD44@PSB> <8906b727-f9c3-e7e1-164b-f7b88e48e74b@gmail.com> <1C77C07809EFB402E3E10907@PSB>
To: John C Klensin <john-ietf@jck.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/WNnvydRCXv5pfvXMpBQOf91lBEw>
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: Mon, 22 Oct 2018 09:43:39 -0000
I think 2418 can be covered under the “others can be grouped into one or a small number of documents that update several other RFCs at once” category at https://github.com/IASA2/Miscellaneous/blob/master/Document%20Work%20List.md. There are a bunch of other docs on that list for which that isn’t the right answer though. Alissa > On Oct 20, 2018, at 5:27 PM, John C Klensin <john-ietf@jck.com> wrote: > > > > --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 > > > > _______________________________________________ > iasa20 mailing list > iasa20@ietf.org > https://www.ietf.org/mailman/listinfo/iasa20
- Re: draft-ietf-iasa2-rfc2418bis-01.txt John C Klensin
- Re: [Iasa20] draft-ietf-iasa2-rfc2418bis-01.txt Brian E Carpenter
- Re: [Iasa20] draft-ietf-iasa2-rfc2418bis-01.txt John C Klensin
- Re: [Iasa20] draft-ietf-iasa2-rfc2418bis-01.txt Scott O. Bradner
- Re: [Iasa20] draft-ietf-iasa2-rfc2418bis-01.txt Bob Hinden
- Re: [Iasa20] draft-ietf-iasa2-rfc2418bis-01.txt John C Klensin
- Re: [Iasa20] draft-ietf-iasa2-rfc2418bis-01.txt Scott Bradner
- Re: [Iasa20] draft-ietf-iasa2-rfc2418bis-01.txt Scott Bradner
- Re: [Iasa20] draft-ietf-iasa2-rfc2418bis-01.txt Alissa Cooper
- Re: [Iasa20] draft-ietf-iasa2-rfc2418bis-01.txt Peter Saint-Andre
- Re: [Iasa20] draft-ietf-iasa2-rfc2418bis-01.txt Livingood, Jason
- Re: [Iasa20] draft-ietf-iasa2-rfc2418bis-01.txt Livingood, Jason
- Re: [Iasa20] draft-ietf-iasa2-rfc2418bis-01.txt Livingood, Jason
- Re: [Iasa20] draft-ietf-iasa2-rfc2418bis-01.txt John C Klensin
- Re: [Iasa20] draft-ietf-iasa2-rfc2418bis-01.txt Joseph Lorenzo Hall
- Re: [Iasa20] draft-ietf-iasa2-rfc2418bis-01.txt John C Klensin
- fundamental brokenness of iasa2 updates (was Re: … Scott Bradner
- Re: fundamental brokenness of iasa2 updates (was … Scott Bradner
- Re: [Iasa20] fundamental brokenness of iasa2 upda… Alissa Cooper
- Re: [Iasa20] fundamental brokenness of iasa2 upda… Scott Bradner
- Re: [Iasa20] fundamental brokenness of iasa2 upda… Joel M. Halpern
- Re: [Iasa20] fundamental brokenness of iasa2 upda… Scott O. Bradner
- Re: [Iasa20] fundamental brokenness of iasa2 upda… Livingood, Jason
- Re: fundamental brokenness of iasa2 updates (was … Bob Hinden