Re: [Iasa20] draft-ietf-iasa2-consolidated-upd-06

John C Klensin <john-ietf@jck.com> Fri, 08 March 2019 16:39 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 DD5F812DDA3 for <iasa20@ietfa.amsl.com>; Fri, 8 Mar 2019 08:39:11 -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, 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 6QfuTYl5Ydke for <iasa20@ietfa.amsl.com>; Fri, 8 Mar 2019 08:39:10 -0800 (PST)
Received: from bsa2.jck.com (ns.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 AF799130F12 for <iasa20@ietf.org>; Fri, 8 Mar 2019 08:39:10 -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 1h2IWY-000DRP-Ud; Fri, 08 Mar 2019 11:39:06 -0500
Date: Fri, 08 Mar 2019 11:39:00 -0500
From: John C Klensin <john-ietf@jck.com>
To: Alissa Cooper <alissa@cooperw.in>
cc: Brian E Carpenter <brian.e.carpenter@gmail.com>, iasa20@ietf.org
Message-ID: <264AA91C7A94F3E572712DD1@PSB>
In-Reply-To: <79791048-1315-48D5-AE10-FC643ED38AA2@cooperw.in>
References: <A7B72177ABB2B2F0BEE7763B@PSB> <567462F2-46E3-445E-BDA3-493DA7AD31CC@cooperw.in> <4faec579-e4dd-f138-4c96-f26d9945c307@gmail.com> <3AC01BB5-613D-474C-B8AE-A85D8F264A83@cooperw.in> <CD6FB2CD65EAEA39265FFD0F@PSB> <610B71DF-46AC-4662-9F5B-70C58A2D872C@cooperw.in> <6175C7F84A4F40FDAE2A1CCB@PSB> <79791048-1315-48D5-AE10-FC643ED38AA2@cooperw.in>
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/iasa20/NaNjZVpxUxIjvK1VSlXnAk5s18g>
Subject: Re: [Iasa20] draft-ietf-iasa2-consolidated-upd-06
X-BeenThere: iasa20@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Discussions relating to reorganising the IETF administrative structures in the so called “IASA 2.0” project. <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, 08 Mar 2019 16:39:12 -0000


--On Friday, March 8, 2019 11:08 -0500 Alissa Cooper
<alissa@cooperw.in> wrote:

> Hi John,
> 
>> On Mar 8, 2019, at 9:53 AM, John C Klensin
>> <john-ietf@jck.com> wrote:
>> 
>> 
>> 
>> --On Friday, March 8, 2019 06:30 -0500 Alissa Cooper
>> <alissa@cooperw.in> wrote:
>> 
>>> Hi John,
>>> ...
>>>> However, I, and I assume most WG participants, am much more
>>>> interested in getting this work finished than in arguing so,
>>>> if you are putting on your Responsible AD hat and telling me
>>>> to change this, I will certainly do so.
>>> 
>>> Yes, I am.
>>> 
>>> Thanks,
>>> Alissa
>> 
>> I will try to find the time to make the changes and get a new
>> version up over the weekend.  For the record, I believe that a
>> single AD making a decision like this without offering
>> evidence of either WG or IETF consensus to be an abuse of
>> power and hope it does not set a precedent but, as suggested
>> above, as far as this document is concerned, I just want to
>> move on.
> 
> The point of AD evaluation is to catch things like this. But
> if the WG chairs would like to issue a consensus call about
> whether this WG should do something outside its charter, I can
> wait to request the issuance of the IETF last call until that
> is done.
> 
> The evaluation of IETF consensus will occur after IETF last
> call has completed.

Alissa,

I don't want to drag this out and hope the WG Chairs and
Participants don't either.  However, to clarify my comment in
the light of your comment above, I think it is entirely
reasonable for you to call out your concern as part of AD review
and let the WG figure out what to do about that.  At the same
time, as a document editor who is just trying to follow WG
directions, I've got text that was put in at the direction of WG
participants confirmed by one of the co-chairs, that has been in
several consecutive I-Ds without, IIR, anyone in the WG
suggesting it be removed or restructured and certainly without
the co-chairs telling me to change it.  From that perspective, I
would have expected your comment/preference to trigger a WG
discussion and either different instructions to me from the WG
or a WG decision to push back.   In that context, the "abuse of
power" comment comes from your unilaterally telling me to change
text which I've assumed up to this point represents at least
rough WG consensus.

Separately, I think making decisions based on readings of a WG
charter that prevent a WG from addressing an issue discovered as
part of its work when that appears to be consistent with good
sense and the general intend of charter rules is a bad idea for
the IETF and that the precedents for it are, at best, mixed and
inconsistent.   But let's save that for another day.

best,
   john