Re: [Gendispatch] Possible topic: WG adoption of drafts

Fernando Gont <fgont@si6networks.com> Fri, 22 May 2020 09:56 UTC

Return-Path: <fgont@si6networks.com>
X-Original-To: gendispatch@ietfa.amsl.com
Delivered-To: gendispatch@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 795233A09F2 for <gendispatch@ietfa.amsl.com>; Fri, 22 May 2020 02:56:31 -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, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, 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 dDixQg9Sh9Dx for <gendispatch@ietfa.amsl.com>; Fri, 22 May 2020 02:56:30 -0700 (PDT)
Received: from fgont.go6lab.si (fgont.go6lab.si [91.239.96.14]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CFC6E3A09F6 for <gendispatch@ietf.org>; Fri, 22 May 2020 02:56:29 -0700 (PDT)
Received: from [IPv6:2800:810:464:11f:f597:cad2:df35:f6c5] (unknown [IPv6:2800:810:464:11f:f597:cad2:df35:f6c5]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by fgont.go6lab.si (Postfix) with ESMTPSA id 580F228380C; Fri, 22 May 2020 09:56:27 +0000 (UTC)
To: Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>
Cc: gendispatch@ietf.org
References: <c4bb2691-0c2e-8017-49fc-742d50e9b50f@si6networks.com> <CAKKJt-ds1bVarDo9dHYPerBbKqtmXg=JG7Qw2rZd0LBjP=W17g@mail.gmail.com>
From: Fernando Gont <fgont@si6networks.com>
Message-ID: <093c8506-4903-770d-45a8-1f2be879f510@si6networks.com>
Date: Fri, 22 May 2020 06:56:05 -0300
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.9.1
MIME-Version: 1.0
In-Reply-To: <CAKKJt-ds1bVarDo9dHYPerBbKqtmXg=JG7Qw2rZd0LBjP=W17g@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: en-US
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/gendispatch/qmMnIsZS6Hgt4usu_rf9dOOkjuI>
Subject: Re: [Gendispatch] Possible topic: WG adoption of drafts
X-BeenThere: gendispatch@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: General Area Dispatch <gendispatch.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gendispatch>, <mailto:gendispatch-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gendispatch/>
List-Post: <mailto:gendispatch@ietf.org>
List-Help: <mailto:gendispatch-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gendispatch>, <mailto:gendispatch-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 22 May 2020 09:56:32 -0000

Hi, Spencer,

On 18/5/20 09:19, Spencer Dawkins at IETF wrote:
[....]
>     the procedures in RFC2026.
> 
> 
> I agree that working group draft adoption is a widespread practice. As 
> an individual participant, I certainly treat this as an important step 
> for drafts I am working on.
> 
> I agree that at least documenting the practice would be helpful to new 
> participants.
> 
> I don't know if it's universal across all working groups. That's 
> probably a question that should also be asked on the wgchairs mailing list.
> 
> I don't know if this step is necessary for all drafts in working groups 
> that use this practice - that's trying to guess the edge cases.

Having a uniform practice among all wgs would be a good idea -- for many 
reasons.



> As I almost always do, I'd phrase guidance on this topic as 
> recommendations - we really do trust working group chairs to make bigger 
> decisions about working group consensus for the benefit of their working 
> groups. So a RECOMMENDED BCP, or even an Informational draft, seems more 
> useful than a REQUIRED BCP, with all the edge cases we usually trip over 
> when we write such text.
> 
> And my understanding is that we can appeal almost anything using the 
> procedures in RFC 2026, if that's what you're referring to. 

I guess you can. But how would you e.g. Appeal a non-decision?


Thanks,
-- 
Fernando Gont
SI6 Networks
e-mail: fgont@si6networks.com
PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492