Re: [Iasa20] I-D Action: draft-ietf-iasa2-consolidated-upd-04.txt

John C Klensin <john-ietf@jck.com> Fri, 18 January 2019 19:54 UTC

Return-Path: <john-ietf@jck.com>
X-Original-To: iasa20@ietfa.amsl.com
Delivered-To: iasa20@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DDC4F13136D for <iasa20@ietfa.amsl.com>; Fri, 18 Jan 2019 11:54:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, 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 g1bgTITO6BJP for <iasa20@ietfa.amsl.com>; Fri, 18 Jan 2019 11:53:59 -0800 (PST)
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 BCB20131366 for <iasa20@ietf.org>; Fri, 18 Jan 2019 11:53:58 -0800 (PST)
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 1gkaDF-000AEl-34; Fri, 18 Jan 2019 14:53:57 -0500
Date: Fri, 18 Jan 2019 14:53:50 -0500
From: John C Klensin <john-ietf@jck.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
cc: iasa20@ietf.org
Message-ID: <73F411A8D83C47CB78AA7B75@PSB>
In-Reply-To: <b57d02fc-a138-2cc7-b0c7-568224444a93@gmail.com>
References: <154776119259.10469.9076218329658422383@ietfa.amsl.com> <50FC4101-FAA3-48FB-910B-88286225140C@cable.comcast.com> <3A2DA89A-9D0F-4F26-8346-BE1EE5E15831@gmail.com> <b57d02fc-a138-2cc7-b0c7-568224444a93@gmail.com>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
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/iasa20/R80w0z7UHGlbglT7ISI2lQbTVU4>
Subject: Re: [Iasa20] I-D Action: draft-ietf-iasa2-consolidated-upd-04.txt
X-BeenThere: iasa20@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: =?iso-8859-1?q?Discussions_relating_to_reorganising_the_IETF_administrative_structures_in_the_so_called_=93IASA_2=2E0=94_project=2E?= <iasa20.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/iasa20>, <mailto:iasa20-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/iasa20/>
List-Post: <mailto:iasa20@ietf.org>
List-Help: <mailto:iasa20-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/iasa20>, <mailto:iasa20-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 18 Jan 2019 19:54:02 -0000

Speaking as the relevant editor...

(1) I'm fairly agnostic about this and am happy to title the
document however the WG prefers.

(2) I personally tend to agree with Brian, _unless_, there are
reasonable odds that we will conclude in a year or three that
some properties of the IASA 2.0 approach, including this
terminology, is not working for us and needs to be changed
above.  In that case, "version 2" or something equivalent in the
title would probably be desirable.

(3) My concerns about whether the I-D says the right things for
the long term go well beyond the title.  Those who care are
encouraged to read the note at the end of the change log, think
about it, and comment as appropriate.

    john


--On Saturday, January 19, 2019 08:40 +1300 Brian E Carpenter
<brian.e.carpenter@gmail.com> wrote:

> On 2019-01-19 08:10, Bob Hinden wrote:
>> Jason,
>> 
>>> On Jan 18, 2019, at 6:43 AM, Livingood, Jason
>>> <Jason_Livingood@comcast.com> wrote:
>>> 
>>> A participant offlist suggested: 
>>> The title "Consolidated IASA2-Related Document Updates"
>>> seems a bit unsuitable for long-term relevance. How about
>>> "Consolidated Updates of IETF Administrative Terminology" or
>>> something like that?
>>> 
>>> Seems like a good suggestion, and I believe the editor
>>> agrees. Please speak up if you have any concerns with this.
>> 
>> I agree.  Might be good to get IASA 2.0 into the title.  How
>> about something like:
>> 
>>   Consolidated IASA 2.0 Updates of IETF Administrative
>>   Terminology
> 
> Well (speaking as the offlist participant concerned) I
> disagree. Looking at this in 5 or 10 years' time, IMHO nobody
> will find the term "IASA 2.0" helpful or interesting.
> 
>      Brian
> 
>> 
>> Bob
>> 
>> 
>>> 
>>> Thanks
>>> Jason 
>>> 
>>> 
>>> 
>>> 
>>> On 1/17/19, 4:40 PMഀ਀㸀㸀㸀 , "iasa20 on behalf
ഀ਀㸀㸀㸀 of internet-drafts@iഀ਀㸀㸀㸀 etf.org"
<iasa20-bouഀ਀㸀㸀㸀 nces@ietf.org on
behഀ਀㸀㸀㸀 alf of
internet-drafഀ਀㸀㸀㸀 ts@ietf.org> wrote:
´€à¨€ã¸€ã¸€ã¸€â€€>>
>>
>>    A Newഀ਀㸀㸀㸀  Internet-Draft is
aഀ਀㸀㸀㸀 vailable from the onഀ਀㸀㸀㸀 -line
Internet-Draftഀ਀㸀㸀㸀 s directories.
>>  ഀ਀㸀㸀㸀   This draft is a woഀ਀㸀㸀㸀 rk
item of the IETF ഀ਀㸀㸀㸀 Administrative
Suppoഀ਀㸀㸀㸀 rt Activity 2 WG of ഀ਀㸀㸀㸀 the
IETF.
>>
>>   ഀ਀㸀㸀㸀          Title      ഀ਀㸀㸀㸀 
: Consolidated ഀ਀㸀㸀㸀 IASA2-Related
Documeഀ਀㸀㸀㸀 nt Updates
>>      ഀ਀㸀㸀㸀       Author        ഀ਀㸀㸀㸀 
: John C Klensin
ഀ਀㸀㸀㸀 >>    	Filename     ഀ਀㸀㸀㸀    :
draft-ietf-iasaഀ਀㸀㸀㸀 2-consolidated-upd-0ഀ਀㸀㸀㸀 4.txt
>>    	Pages ഀ਀㸀㸀㸀           : 9
>>   ഀ਀㸀㸀㸀  	Date            :
ഀ਀㸀㸀㸀 2019-01-17
>>
>>  ഀ਀㸀㸀㸀   Abstract:
>>     ഀ਀㸀㸀㸀   In 2018, the IETF
ഀ਀㸀㸀㸀 began the transitionഀ਀㸀㸀㸀  to a
new administraഀ਀㸀㸀㸀 tive
>>       strucഀ਀㸀㸀㸀 ture and updated
itsഀ਀㸀㸀㸀  IETF Administrativeഀ਀㸀㸀㸀 
Support Activity (Iഀ਀㸀㸀㸀 ASA)
>>       to a ഀ਀㸀㸀㸀 new "IASA 2.0"
strucഀ਀㸀㸀㸀 ture.  In addition tഀ਀㸀㸀㸀 o
more substantive
ഀ਀㸀㸀㸀 >>       changes thaഀ਀㸀㸀㸀 t are
described in oഀ਀㸀㸀㸀 ther documents, the
ഀ਀㸀㸀㸀 transition to the
>ഀ਀㸀㸀㸀 >       2018 IETF
Adഀ਀㸀㸀㸀 ministrative Supportഀ਀㸀㸀㸀 
structure changes sഀ਀㸀㸀㸀 everal position
>> ഀ਀㸀㸀㸀       titles and
orgഀ਀㸀㸀㸀 anizational relationഀ਀㸀㸀㸀 ships
that are referഀ਀㸀㸀㸀 enced
>>       elseഀ਀㸀㸀㸀 where.  Rather than
ഀ਀㸀㸀㸀 reissue those refereഀ਀㸀㸀㸀 ncing
documents
>> ഀ਀㸀㸀㸀       individually, ഀ਀㸀㸀㸀 this
specification pഀ਀㸀㸀㸀 rovides updates to
tഀ਀㸀㸀㸀 hem and
>>       deഀ਀㸀㸀㸀 precates some
now-obഀ਀㸀㸀㸀 solete documents to
ഀ਀㸀㸀㸀 ensure that there isഀ਀㸀㸀㸀  no
>>       confusഀ਀㸀㸀㸀 ion due to these
chaഀ਀㸀㸀㸀 nges.
>>
>>
>>   ഀ਀㸀㸀㸀  The IETF datatrackeഀ਀㸀㸀㸀 r
status page for thഀ਀㸀㸀㸀 is draft is:
>>
ഀ਀㸀㸀㸀 https://datatracker.ഀ਀㸀㸀㸀 ietf.org/doc/draft-iഀ਀㸀㸀㸀 etf-iasa2-consolidatഀ਀㸀㸀㸀 ed-upd/
>>
>>    Tഀ਀㸀㸀㸀 here are also
htmlizഀ਀㸀㸀㸀 ed versions availablഀ਀㸀㸀㸀 e
at:
>>
https:/ഀ਀㸀㸀㸀 /tools.ietf.org/htmlഀ਀㸀㸀㸀 /draft-ietf-iasa2-coഀ਀㸀㸀㸀 nsolidated-upd-04
>ഀ਀㸀㸀㸀 >
https://datatraഀ਀㸀㸀㸀 cker.ietf.org/doc/htഀ਀㸀㸀㸀 ml/draft-ietf-iasa2-ഀ਀㸀㸀㸀 consolidated-upd-04
´€à¨€ã¸€ã¸€ã¸€â€€>>
>>    A diff frഀ਀㸀㸀㸀 om the previous
versഀ਀㸀㸀㸀 ion is available at:ഀ਀㸀㸀㸀 
>>
https://www.ഀ਀㸀㸀㸀 ietf.org/rfcdiff?urlഀ਀㸀㸀㸀 2=draft-ietf-iasa2-cഀ਀㸀㸀㸀 onsolidated-upd-04
ഀ਀㸀㸀㸀 >>
>>
>>    Pleaseഀ਀㸀㸀㸀  note that it may
taഀ਀㸀㸀㸀 ke a couple of minutഀ਀㸀㸀㸀 es
from the time of ഀ਀㸀㸀㸀 submission
>>    unഀ਀㸀㸀㸀 til the htmlized
verഀ਀㸀㸀㸀 sion and diff are
avഀ਀㸀㸀㸀 ailable at tools.ietഀ਀㸀㸀㸀 f.org.
>>
>>    Inഀ਀㸀㸀㸀 ternet-Drafts are
alഀ਀㸀㸀㸀 so available by anonഀ਀㸀㸀㸀 ymous
FTP at:
>>   ഀ਀㸀㸀㸀 
ftp://ftp.ietf.org/ഀ਀㸀㸀㸀 internet-drafts/
>>ഀ਀㸀㸀㸀 
>>
____________ഀ਀㸀㸀㸀 ____________________ഀ਀㸀㸀㸀 _______________
>> ഀ਀㸀㸀㸀    iasa20 mailing liഀ਀㸀㸀㸀 st
>>    iasa20@ietഀ਀㸀㸀㸀 f.org
>>
https:/ഀ਀㸀㸀㸀 /www.ietf.org/mailmaഀ਀㸀㸀㸀 n/listinfo/iasa20
>ഀ਀㸀㸀㸀 >
>>
>>
__________ഀ਀㸀㸀㸀 ____________________ഀ਀㸀㸀㸀 _________________
>ഀ਀㸀㸀㸀 > iasa20 mailing lisഀ਀㸀㸀㸀 t
>> iasa20@ietf.orഀ਀㸀㸀㸀 g
>>
https://www.ieഀ਀㸀㸀㸀 tf.org/mailman/listiഀ਀㸀㸀㸀 nfo/iasa20
> 
>
__ഀ਀㸀㸀㸀 ____________________ഀ਀㸀㸀㸀 ____________________ഀ਀㸀㸀㸀 _____
> iasa20 mailഀ਀㸀㸀㸀 ing list
> iasa20@iഀ਀㸀㸀㸀 etf.org
>
https://wഀ਀㸀㸀㸀 ww.ietf.org/mailman/ഀ਀㸀㸀㸀 listinfo/iasa20
> 
´€à¨€ã¸€ã¸€ã¸€â€€
_________________ഀ਀㸀㸀㸀 ____________________ഀ਀㸀㸀㸀 __________
iasa20 mഀ਀㸀㸀㸀 ailing list
iasa20@ഀ਀㸀㸀㸀 ietf.org
https://wwഀ਀㸀㸀㸀 w.ietf.org/mailman/lഀ਀㸀㸀㸀 istinfo/iasa20
ഀ਀ഀ਀ഀ਀ഀ਀