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

"Livingood, Jason" <Jason_Livingood@comcast.com> Mon, 22 October 2018 14:25 UTC

Return-Path: <Jason_Livingood@comcast.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 5B25612EB11; Mon, 22 Oct 2018 07:25:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0
X-Spam-Level:
X-Spam-Status: No, score=0 tagged_above=-999 required=5 tests=[HTML_MESSAGE=0.001, SPF_PASS=-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 4_W0n0kQ6nLm; Mon, 22 Oct 2018 07:25:36 -0700 (PDT)
Received: from copdcmhout01.cable.comcast.com (copdcmhout01.cable.comcast.com [162.150.44.71]) (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 25AD8130DC9; Mon, 22 Oct 2018 07:25:14 -0700 (PDT)
X-AuditID: a2962c47-d4dff70000003e3c-30-5bcdddb6a317
Received: from copdcexc39.cable.comcast.com (copdcmhoutvip.cable.comcast.com [96.114.156.147]) (using TLS with cipher AES256-SHA256 (256/256 bits)) (Client did not present a certificate) by copdcmhout01.cable.comcast.com (SMTP Gateway) with SMTP id 07.F3.15932.6BDDDCB5; Mon, 22 Oct 2018 08:24:54 -0600 (MDT)
Received: from COPDCEXC37.cable.comcast.com (147.191.125.136) by copdcexc39.cable.comcast.com (147.191.125.138) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1466.3; Mon, 22 Oct 2018 10:25:05 -0400
Received: from COPDCEXC37.cable.comcast.com ([fe80::3aea:a7ff:fe36:8a94]) by COPDCEXC37.cable.comcast.com ([fe80::3aea:a7ff:fe36:8a94%15]) with mapi id 15.01.1466.009; Mon, 22 Oct 2018 10:25:05 -0400
From: "Livingood, Jason" <Jason_Livingood@comcast.com>
To: Alissa Cooper <alissa@cooperw.in>, John C Klensin <john-ietf@jck.com>
CC: "rsalz@akamai.com" <rsalz@akamai.com>, "iasa20@ietf.org" <iasa20@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
Subject: Re: [Iasa20] draft-ietf-iasa2-rfc2418bis-01.txt
Thread-Topic: [Iasa20] draft-ietf-iasa2-rfc2418bis-01.txt
Thread-Index: AQHUaLIWWpnqiALk7Em/K8gy6dO0QqUo45cAgAAFbgCAAmAFAIAAC54A
Date: Mon, 22 Oct 2018 14:25:05 +0000
Message-ID: <AE51678E-BFBF-48D1-995D-C6BCF8C4EF99@cable.comcast.com>
References: <4915CD062D28D607D3D4AD44@PSB> <8906b727-f9c3-e7e1-164b-f7b88e48e74b@gmail.com> <1C77C07809EFB402E3E10907@PSB> <F955E5C3-6236-4F98-B531-EE39C4280A3F@cooperw.in>
In-Reply-To: <F955E5C3-6236-4F98-B531-EE39C4280A3F@cooperw.in>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/10.10.3.181015
x-originating-ip: [96.114.156.7]
Content-Type: multipart/alternative; boundary="_000_AE51678EBFBF48D1995DC6BCF8C4EF99cablecomcastcom_"
MIME-Version: 1.0
X-CFilter-Loop: Forward
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFlrAKsWRmVeSWpSXmKPExsWSUDRnsu62u2ejDSavEbSYfuYvo8WS6RuZ LJ5tnM9i0XrpD5vF/y2dLA6sHpOPLGD2+PLkJZPHkiU/mTwur3zNHMASFW5TlFpcmpSbWaJQ nFpUlpmcaquUnFisZMelgAGASnNSE4tTHZNLMvPzivUx1NjowwyzSwjPeLv9NlvBsybGitu9 Wg2MC+u7GDk5JARMJJZ3zWHpYuTiEBLYxSRx+u5sVpCEkEALk0Trel+IxGlGiQd3JjKDJNgE zCTuLrwCZosIeEr86N4I1M3BwSxQKLFzmiZIWFjAQmLvl8VsIGERAUuJ25vUIardJFZeOsME YrMIqEpMufqWEcTmFXCReHvpATPEqk2MEu9/PgK7gVPATuL91XNgDYwCYhLfT60Bs5kFxCVu PZnPBPGAgMSSPeeZIWxRiZeP/4H1igroS+yecJwRIq4g0TNhOjNEb7rE8oWfmSEWC0qcnPmE BaJGXOLwkR2sExjFZyFZMQtJyywkLbPAPtaUWL9LH6JEUWJK90N2CFtDonXOXHaIEiuJ4218 yEoWMHKsYuQ1NDPSMzQ10DMx0TM33MQITDeLpum472D8cD72EKMAB6MSD6/hgbPRQqyJZcWV uYcYJTiYlUR4Vy4BCvGmJFZWpRblxxeV5qQWH2KU5mBREucNNzgVLSSQnliSmp2aWpBaBJNl 4uCUamB0utzz5/ieKym+DzXlZjc1lmScs11uY1WY+nrKh/YPllobZ/zYZjp98zO3HJu02e8O 7XlwgctF4aDch49u0as7ZkT6BL4863i8P052p8/SO89/Z3mV9M+Wnq9yqLIiKTnf+FXssSe/ p8v1HLsftU1/1RLNKUtvaW9iCDKKnj6l0Y5hT39MxSMPJZbijERDLeai4kQALTjAAjMDAAA=
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/il8TxbzA7Cv-LHSfA1atCOEjo0o>
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 14:25:38 -0000

Thanks, Alissa, we’ll take a look and assess this.

Jason

From: ietf <ietf-bounces@ietf.org> on behalf of Alissa Cooper <alissa@cooperw.in>
Date: Monday, October 22, 2018 at 5:44 AM
To: John C Klensin <john-ietf@jck.com>
Cc: "rsalz@akamai.com" <rsalz@akamai.com>, "iasa20@ietf.org" <iasa20@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
Subject: Re: [Iasa20] draft-ietf-iasa2-rfc2418bis-01.txt

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<mailto:john-ietf@jck.com>> wrote:



--On Sunday, October 21, 2018 10:07 +1300 Brian E Carpenter
<brian.e.carpenter@gmail.com<mailto: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<mailto:iasa20@ietf.org>
https://www.ietf.org/mailman/listinfo/iasa20