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

Brian E Carpenter <brian.e.carpenter@gmail.com> Wed, 17 April 2019 20:38 UTC

Return-Path: <brian.e.carpenter@gmail.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 0BB441203D6 for <ietf@ietfa.amsl.com>; Wed, 17 Apr 2019 13:38:47 -0700 (PDT)
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 hP02wqbzUQqu for <ietf@ietfa.amsl.com>; Wed, 17 Apr 2019 13:38:45 -0700 (PDT)
Received: from mail-pf1-x42c.google.com (mail-pf1-x42c.google.com [IPv6:2607:f8b0:4864:20::42c]) (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 5590C1203D4 for <ietf@ietf.org>; Wed, 17 Apr 2019 13:38:45 -0700 (PDT)
Received: by mail-pf1-x42c.google.com with SMTP id 9so12608334pfj.13 for <ietf@ietf.org>; Wed, 17 Apr 2019 13:38:45 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-language:content-transfer-encoding; bh=eemwPTfSy0UOEGNH4ec12345KmRGBKRQAQJIo/bmenw=; b=jfuAL9zTeVbfQZNzuXnE8lm0FTJqcrNo8TFX6ONHBGPL7yX8G1kLzM5DbO5vH2hdK0 o3vKbhKB8kHWIDtQX4rTmVa3yE4OD4URHjsaaCzE2D2reA3Bxvl5KHuTSJLdGThNQQhp FamQi6DIgRb/YckIHG4OIvgUFilXIMFEsXxhl7qZ9X0zQOyL17+MfDLQvY96PFmh5/yL sT0+CoWRBSu97V3wO9x/ri97QHGwKYI33lNZpbgPJRA4cp+pe5UbJTB7U9CaIKJXaQbE /jkFnOZP+0WVq8M4I/nJJSAYgH8FpCInsKCEv83UQR9W83THP/NThl5jvK/DtR5KfqY+ SdJA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=eemwPTfSy0UOEGNH4ec12345KmRGBKRQAQJIo/bmenw=; b=ip+KEs1DRb+dK3Fiicebe1JDamj2/kJWmVDtP98ghn/LYcgMcbbjFsamQR54T+/B+D UOhcU1akcv7rMdUoUJ52M/gV6EhV5vPlScVOX2H0MRtY9awZunJq6eTZ0cxGbXLMh3PE cLCX2WU4f7bEG2Oskv8zWa9apMvVZU+IbHMhHl3eLRj8+0rPB+vEnqeLufNPu+qGYvhP 8XIDizftYcPDobYN6g8Y4g40DxbK9f4THQNm++2Hyue+dZvT94HTQziGaswMm6NTvjDl e3Yzieu5YP9ZcE8O34Gkj2l6Yyr0KqCHhWYsXnemovzid39Tbha5SFgNL8Ht3pAxMWjb FZaA==
X-Gm-Message-State: APjAAAVxf00SVL3KyxAeg3/RF1lkzsicoWhf7FyzusPc4HfyxagpFe5v 2HsZNu75jd+7sVN75M2O9/62BBBE
X-Google-Smtp-Source: APXvYqxKGgnnRJ7PEOOK66MEVqxUkiEAmTMd/1aKJ+BN1dBbovaYY3YR1gslrc1gx0L3HPl2qAiLQg==
X-Received: by 2002:a62:1a06:: with SMTP id a6mr91824105pfa.18.1555533523936; Wed, 17 Apr 2019 13:38:43 -0700 (PDT)
Received: from [192.168.178.30] ([118.148.72.205]) by smtp.gmail.com with ESMTPSA id l1sm64147571pgp.9.2019.04.17.13.38.42 for <ietf@ietf.org> (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 17 Apr 2019 13:38:43 -0700 (PDT)
Subject: Re: AD Sponsorship of draft-moonesamy-recall-rev
To: ietf@ietf.org
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> <C11980900F520E0EFCC83CEB@PSB>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Message-ID: <98e75e64-f381-7788-aea2-31218eeaebfc@gmail.com>
Date: Thu, 18 Apr 2019 08:38:44 +1200
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.6.1
MIME-Version: 1.0
In-Reply-To: <C11980900F520E0EFCC83CEB@PSB>
Content-Type: text/plain; charset="utf-8"
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/hpR8Bykggpd8KbAexsWe-F6J9fY>
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 20:38:47 -0000

It would certainly be ironic if a proposal to alleviate some
of the disadvantages of remote participation couldn't be be
discussed by remote participants in multiple time zones.

With all due respect, etc. etc., I've always understood that
discussion by email was intended to alleviate exactly that
problem, and this list *is* the IETF plenary. So exactly who
has been disenfranchised from this discussion who would be
enfranchised by a physical or virtual BOF?

Regards
   Brian

On 18-Apr-19 06:56, John C Klensin wrote:
> 
> 
> --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
> 
> 
> 
>