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

Bob Hinden <bob.hinden@gmail.com> Wed, 30 January 2019 02:47 UTC

Return-Path: <bob.hinden@gmail.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 8C0461310FF for <iasa20@ietfa.amsl.com>; Tue, 29 Jan 2019 18:47:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 oE3XHjl5WOrh for <iasa20@ietfa.amsl.com>; Tue, 29 Jan 2019 18:47:06 -0800 (PST)
Received: from mail-wm1-x32e.google.com (mail-wm1-x32e.google.com [IPv6:2a00:1450:4864:20::32e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9C4D61310FE for <iasa20@ietf.org>; Tue, 29 Jan 2019 18:47:05 -0800 (PST)
Received: by mail-wm1-x32e.google.com with SMTP id d15so20036383wmb.3 for <iasa20@ietf.org>; Tue, 29 Jan 2019 18:47:05 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=h1fKOF3b7G6LslF2zDVwkl3hVT67K7rgwUWx9gabGf8=; b=Wqs38gKb8uxJi4d9kj9tzdMwEB3suleH3gEwzhOWG1foLN7sma0gCfACDaQZxPWhSd ENGpAkWTu5U3tT42PTyMFHGagwOvG2i1LnL6Gz6TDH5sgUw2JeebNDvSIaonmlhcdJVK 2kvHA5ZFm7Wc4Pc9FXq1AlNjdiPBMNDORcLQ1+voAWe6jMvJDpzhnibiFl2pykk2hyBZ VCKqh0nsauuW3C5cRAhZ5nmakQG9bVMAPWSGFeaGO2pjBunFQLXrwiUDglqhQiAWIunj J9SB2ySajDja/tIr4em7jLfRw81d9Bbk6EDJuOo4Y7Q8RK6pTddib9nJJ8jHpfBjYr41 4G/A==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=h1fKOF3b7G6LslF2zDVwkl3hVT67K7rgwUWx9gabGf8=; b=TZuGFrApzpw5hSju5ArpEuVcJrk22H58YFQ7zlYJNt8Dc+ao5WCgPtqs0aTBggY9nW 3pxfMKpYNtKlxn3KBJ1p/90kHu3KjyQ/TaSsaZ3Rmn2MfOBN1kq0Z65vjkPp8OU1C386 DJdhP6EIf4jddQ7q65cSHaBPvEwSpCyvuOpTIjEsr6NmwQUfWXjv7X7wFgJPRFvDlQbI tBWxr1E2Vt83w0a69hBNwzYT1B9s5WliNtDuPK5dtnKP1nSXeA314VRfNq3WLUVEDVa0 wkd0WkOn1T11b4jwwSKBCOdUjeOfitfDCkWihNFpWViymghekWo3naAyFY8M1LG5n1uM B7kQ==
X-Gm-Message-State: AJcUukfmthBm7GwfPtLnJuH3l4mIxIY4luptaMN7NWDaLCnt/M8Z2Yb7 wUtUg/fgGXHn0tABUNNSEyk=
X-Google-Smtp-Source: ALg8bN7j826ZDYLyLAiM+rbcFPF+5Ezvz+lEuGFD86Y3CYy2UxjF0vlwMzYBTHCwIAOnDjStO9oW8g==
X-Received: by 2002:a1c:9183:: with SMTP id t125mr22807314wmd.79.1548816423955; Tue, 29 Jan 2019 18:47:03 -0800 (PST)
Received: from ?IPv6:2601:647:4d01:f3a:e862:d8ab:ef2d:5b89? ([2601:647:4d01:f3a:e862:d8ab:ef2d:5b89]) by smtp.gmail.com with ESMTPSA id w125sm1691781wmb.45.2019.01.29.18.47.01 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 29 Jan 2019 18:47:02 -0800 (PST)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 12.2 \(3445.102.3\))
From: Bob Hinden <bob.hinden@gmail.com>
In-Reply-To: <C06063D0-98F6-4D49-97B3-4FF7BA873E4A@cable.comcast.com>
Date: Tue, 29 Jan 2019 18:46:58 -0800
Cc: Bob Hinden <bob.hinden@gmail.com>, Brian Carpenter <brian.e.carpenter@gmail.com>, "iasa20@ietf.org" <iasa20@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <3526D195-85CB-460C-8720-0346CC0BE4EB@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> <EF086EB9-0B78-4216-B8BC-160AB84C9936@gmail.com> <40aaf229-6957-81ac-62e2-983cdcc65ff9@gmail.com> <C06063D0-98F6-4D49-97B3-4FF7BA873E4A@cable.comcast.com>
To: Jason Livingood <Jason_Livingood@comcast.com>
X-Mailer: Apple Mail (2.3445.102.3)
Archived-At: <https://mailarchive.ietf.org/arch/msg/iasa20/yVINNe8nD2YhWM2ao00qw_yiwm4>
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: Wed, 30 Jan 2019 02:47:08 -0000

I have a slight preference for the second one.

Bob


> On Jan 29, 2019, at 12:26 PM, Livingood, Jason <Jason_Livingood@comcast.com> wrote:
> 
> Bob & Brian - Are you guys good with a title like " Consolidated Updates of IETF Administrative Terminology" or do you prefer "Consolidated IASA 2.0 Updates of IETF Administrative Terminology" or something else? It wasn't clear to me where we ended up.
> 
> Thanks
> Jason
> 
> On 1/20/19, 5:38 PM, "iasa20 on behalf of Brian E Carpenter" <iasa20-bounces@ietf.org on behalf of brian.e.carpenter@gmail.com> wrote:
> 
>    On 2019-01-19 14:40, Bob Hinden wrote:
>> Brian,
>> 
>>> On Jan 18, 2019, at 11:40 AM, 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.
>> 
>> My thinking is that this document is consolidating updates for many of the the IASA 2.0 changes, that’s why I think the title should make that clear.
> 
>    Well, this is a matter of taste I guess. Not really a big deal for me.
>> 
>> When we do IASA 3.0, we will need a similar IASA 3.0 document :-)
> 
>    We will. I hope it is a long time in the future.!
> 
>    Regards
>        Brian
>> 
>> Bob
>> 
>> 
>>> 
>>>    Brian
>>> 
>>>> 
>>>> Bob
>>>> 
>>>> 
>>>>> 
>>>>> Thanks
>>>>> Jason 
>>>>> 
>>>>> 
>>>>> 
>>>>> 
>>>>> On 1/17/19, 4:40 PM, "iasa20 on behalf of internet-drafts@ietf.org" <iasa20-bounces@ietf.org on behalf of internet-drafts@ietf.org> wrote:
>>>>> 
>>>>> 
>>>>>  A New Internet-Draft is available from the on-line Internet-Drafts directories.
>>>>>  This draft is a work item of the IETF Administrative Support Activity 2 WG of the IETF.
>>>>> 
>>>>>          Title           : Consolidated IASA2-Related Document Updates
>>>>>          Author          : John C Klensin
>>>>>  	Filename        : draft-ietf-iasa2-consolidated-upd-04.txt
>>>>>  	Pages           : 9
>>>>>  	Date            : 2019-01-17
>>>>> 
>>>>>  Abstract:
>>>>>     In 2018, the IETF began the transition to a new administrative
>>>>>     structure and updated its IETF Administrative Support Activity (IASA)
>>>>>     to a new "IASA 2.0" structure.  In addition to more substantive
>>>>>     changes that are described in other documents, the transition to the
>>>>>     2018 IETF Administrative Support structure changes several position
>>>>>     titles and organizational relationships that are referenced
>>>>>     elsewhere.  Rather than reissue those referencing documents
>>>>>     individually, this specification provides updates to them and
>>>>>     deprecates some now-obsolete documents to ensure that there is no
>>>>>     confusion due to these changes.
>>>>> 
>>>>> 
>>>>>  The IETF datatracker status page for this draft is:
>>>>>  https://datatracker.ietf.org/doc/draft-ietf-iasa2-consolidated-upd/
>>>>> 
>>>>>  There are also htmlized versions available at:
>>>>>  https://tools.ietf.org/html/draft-ietf-iasa2-consolidated-upd-04
>>>>>  https://datatracker.ietf.org/doc/html/draft-ietf-iasa2-consolidated-upd-04
>>>>> 
>>>>>  A diff from the previous version is available at:
>>>>>  https://www.ietf.org/rfcdiff?url2=draft-ietf-iasa2-consolidated-upd-04
>>>>> 
>>>>> 
>>>>>  Please note that it may take a couple of minutes from the time of submission
>>>>>  until the htmlized version and diff are available at tools.ietf.org.
>>>>> 
>>>>>  Internet-Drafts are also available by anonymous FTP at:
>>>>>  ftp://ftp.ietf.org/internet-drafts/
>>>>> 
>>>>>  _______________________________________________
>>>>>  iasa20 mailing list
>>>>>  iasa20@ietf.org
>>>>>  https://www.ietf.org/mailman/listinfo/iasa20
>>>>> 
>>>>> 
>>>>> _______________________________________________
>>>>> iasa20 mailing list
>>>>> iasa20@ietf.org
>>>>> https://www.ietf.org/mailman/listinfo/iasa20
>>>> 
>>>> _______________________________________________
>>>> iasa20 mailing list
>>>> iasa20@ietf.org
>>>> https://www.ietf.org/mailman/listinfo/iasa20
>>>> 
>>> 
>>> _______________________________________________
>>> iasa20 mailing list
>>> iasa20@ietf.org
>>> https://www.ietf.org/mailman/listinfo/iasa20
>> 
>> 
> 
>    _______________________________________________
>    iasa20 mailing list
>    iasa20@ietf.org
>    https://www.ietf.org/mailman/listinfo/iasa20
> 
>