Re: AD Sponsorship of draft-moonesamy-recall-rev

John C Klensin <john-ietf@jck.com> Wed, 17 April 2019 18:57 UTC

Return-Path: <john-ietf@jck.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 356C81204AE; Wed, 17 Apr 2019 11:57:00 -0700 (PDT)
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 FanffimWTOMo; Wed, 17 Apr 2019 11:56:57 -0700 (PDT)
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 6E08012049D; Wed, 17 Apr 2019 11:56:56 -0700 (PDT)
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 1hGpjl-000HDV-Jk; Wed, 17 Apr 2019 14:56:49 -0400
Date: Wed, 17 Apr 2019 14:56:43 -0400
From: John C Klensin <john-ietf@jck.com>
To: Aaron Falk <aafalk@akamai.com>, Adrian Farrel <adrian@olddog.co.uk>
cc: Alissa Cooper <alissa@cooperw.in>, S Moonesamy <sm+ietf@elandsys.com>, IESG <iesg@ietf.org>, ietf@ietf.org
Subject: Re: AD Sponsorship of draft-moonesamy-recall-rev
Message-ID: <C11980900F520E0EFCC83CEB@PSB>
In-Reply-To: <BB40F115-46E8-4EF3-ABDE-15ABB33B4ACA@akamai.com>
References: <6.2.5.6.2.20190405085139.0d5c39b0@elandnews.com> <54510B49-175B-4CE6-9319-1F9A4803940E@cooperw.in> <033d01d4f52f$c6f2dca0$54d895e0$@olddog.co.uk> <BB40F115-46E8-4EF3-ABDE-15ABB33B4ACA@akamai.com>
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/ietf/Tf_Nqpe2Uqjapfgy3zBdiyY2jvU>
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: Wed, 17 Apr 2019 18:57:05 -0000


--On Wednesday, April 17, 2019 13:22 -0400 Aaron Falk
<aafalk@akamai.com> wrote:

> On 17 Apr 2019, at 11:10, Adrian Farrel wrote:
> 
>> Can I suggest:
>> ...
>> - A virtual/interim BoF be held in (say) four weeks from now.
> 
> What a cool and (now that you've stated it) obvious idea!
> Has it been done before?

Let me take Adrian's suggestion a step further: since the
primary issue the draft is trying to address is associated with
remote participants, perhaps we could schedule two or three
virtual BOF sessions to make participation from different
timezones convenient?

In addition...

--On Wednesday, April 17, 2019 10:46 -0400 Alissa Cooper
<alissa@cooperw.in> wrote:

> I discussed this with the IESG and our recommendation is for
> you to submit a BOF proposal if you'd like to pursue this
> further. We think these kinds of changes to the IETF's
> governance structure need the more in-depth problem statement
> discussion and broader review that a chartering process and
> working group would provide.

With the disclaimer that, while I'm somewhat implicated in the
document, I've turned over the decision-making to SM, part of
the intent was to keep the draft very narrowly focused rather
than opening up the range of possible changes to the IETF's
governance structures that the above seems to imply and that
would almost certainly require another iteration on the POISED/
POISSON work that built the foundation of those processes.  I
persuaded him to include the change to allow IESG/ IAB members
to initiate recalls because that had come up years ago but there
seemed to be insufficient energy at the time to carry it
forward.  If the conclusion from the IESG's informal discussion
is that including that change broadens the scope from making an
adjustment to increase the ability of mostly-remote participants
to ensure fair treatment to changes requiring broader review,
then I would recommend removing that change and narrowing the
focus of the document.   

Conversely, if the IESG has concluded that a more general review
of procedures is needed (nearly 20 years after what I think was
the last such review in POISSON), then let's try to solicit
proposals for such a WG and its scope and figure out whether
that actually needs a BOF.

best,
   john