Re: [Gendispatch] Thoughts on draft-carpenter-gendispatch-draft-adoption

Brian E Carpenter <brian.e.carpenter@gmail.com> Wed, 22 July 2020 01:51 UTC

Return-Path: <brian.e.carpenter@gmail.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 933E53A082A; Tue, 21 Jul 2020 18:51:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.1
X-Spam-Level:
X-Spam-Status: No, score=-2.1 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, NICE_REPLY_A=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-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 WxKp-ags2Plf; Tue, 21 Jul 2020 18:51:41 -0700 (PDT)
Received: from mail-pl1-x62b.google.com (mail-pl1-x62b.google.com [IPv6:2607:f8b0:4864:20::62b]) (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 763DE3A0827; Tue, 21 Jul 2020 18:51:41 -0700 (PDT)
Received: by mail-pl1-x62b.google.com with SMTP id m16so191099pls.5; Tue, 21 Jul 2020 18:51:41 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=htQk6haEJdbDstnIG9azvqrxxNKnwZt0twUby2Hsa0o=; b=AMP/UzDJj0PA6/auoSE50qKM+3EN/eDv4SABzaM8q82oJ19MeSqCUKcQZREmpGWnHO jC8DPLMyDLxGr8Y/pQDQv4ANZu3Rm1p3dWZjpiqz/L9VkeR/jaSdEI3sWfXdTbc20l+W Su+YL+ECOAlo0+FZz+dK02ZeDj49Ol+5OQr3xp5cNW12Ybs5fRhAcc43qpNJ1bk3BLlL hk8pdVpAU2zZ+pLYPWeusF6baqKqBxGIQYYctqAhAzGGRQ5BTv9pQS5KOUwbtzR3BnHQ gF9qj38mGDqkLVnc6FXecIwhfrEvb2OTIO6HUh0/BdjtpuSngVgm1NIwAmHVhpnFKE7s hiog==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=htQk6haEJdbDstnIG9azvqrxxNKnwZt0twUby2Hsa0o=; b=RTzz1DDVKaFg0uO71o/pK1IPpIkzspe/oQDkSoL41rn7iLKlgKfthRFKf6HJ5nZDR3 iMV6fOCINit5dH8dOxsPy5xgYaXbg3HKVvHW/LTBqAxjDgtdUReNfiYmIiaI0RQRUReT Qgm384W/mBuT3TA/ob43lKJgYCimoKqBg2fIyWDjcXgGW7Ebt4kRXyyFac572rB4Ijli B35ACfJJF/ztp+rhyG5CTLJ2BwCifoJZMbLv9Mc7o9NPg7BG9Dc0FghXUgkF8Fx72LkE W4TEWrJfDhdMgVNEeMGtp+UfODeM4ELEtQUZFMSUg1iwZ2Et/ZwyQB0ZuzzyiVVsOxkY xSIQ==
X-Gm-Message-State: AOAM530BjhiSO0rHB8SGLXsF7mjoMCvrszXB5le73qE2Lh7AWykNM8Dj sP8lk/4oKCSmlihAv7JA0wGgc1wu
X-Google-Smtp-Source: ABdhPJwVYjdgM0KDegCdrSl92ZRZ3xQkt14EASeEZaB4lQZzUNnDk3Neom8X3Qj8NyU7PFFUuBx0TA==
X-Received: by 2002:a17:902:44c:: with SMTP id 70mr23458161ple.97.1595382700590; Tue, 21 Jul 2020 18:51:40 -0700 (PDT)
Received: from [192.168.178.20] ([151.210.139.192]) by smtp.gmail.com with ESMTPSA id d16sm21696175pfo.156.2020.07.21.18.51.38 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Tue, 21 Jul 2020 18:51:40 -0700 (PDT)
To: adrian@olddog.co.uk, gendispatch@ietf.org
Cc: draft-carpenter-gendispatch-draft-adoption@ietf.org
References: <031601d65fb0$f6aa0a30$e3fe1e90$@olddog.co.uk>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Message-ID: <2c566e75-901d-2289-9b20-21ada18eae30@gmail.com>
Date: Wed, 22 Jul 2020 13:51:37 +1200
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.9.1
MIME-Version: 1.0
In-Reply-To: <031601d65fb0$f6aa0a30$e3fe1e90$@olddog.co.uk>
Content-Type: text/plain; charset="utf-8"
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/gendispatch/9-6XPCxk8m3MhOsFotfusbuEEcU>
Subject: Re: [Gendispatch] Thoughts on draft-carpenter-gendispatch-draft-adoption
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: Wed, 22 Jul 2020 01:51:43 -0000

fwiw, this co-author partly agrees with you. I think it's fair to say
that a formally designated design team would be expected to produce
a WG draft but I think the text you quote goes too far.

Just to quote the relevant bit of RFC2418 (a.k.a. BCP25):
"Design teams may range from an informal chat
 between people in a hallway to a formal set of expert volunteers that
 the WG chair or AD appoints to attack a controversial problem.  The
 output of a design team is always subject to approval, rejection or
 modification by the WG as a whole."

So we need to tune the text you quoted to be compatible with that.

Regards
   Brian

On 22-Jul-20 10:47, Adrian Farrel wrote:
> Hi,
> 
> In this draft you have (section 3)...
> 
>    A WG that decides to create a design team to solve a
>    problem has implicitely agreed to adopt the result.  To not adopt the
>    result is to say that the results of the WG mandated design team does
>    not deserve first class agenda time.  Such a design team would have
>    been created, for instance, when a WG can not decide between two
>    competing individual drafts and decides to merge them.
> 
> s/implicitely/implicitly/
> s/can not/cannot/
> 
> But I strongly disagree with this statement. I think that the DT is (very)
> often chartered to come up with a draft for the WG to consider adopting. If,
> however, as is somewhat common, the DT goes a little wild and produces a
> document that the DT likes but the WG finds unacceptable, then the document
> should not be adopted. 
> 
> While it is true that the WG can rewrite all of the document once adopted,
> it must be understood that there is a certain stickiness to fundamental
> ideas that are contained in adopted documents (the details may be changed,
> but the main thrust is much harder to change).
> 
> I would go as far as to say that sometimes there is an expectation that the
> output of a DT will be presented to a WG as a done decision that the WG must
> accept because "the WG chartered the DT". But a DT is "just a group of
> people working together on a draft," and the fact that the WG chartered a DT
> merely means that the WG helped form the group of people.
> 
> The sentence about the "first class agenda time" also seems wrong. Yes, the
> output of the DT deserves agenda time, but if the use of that time reveals
> that the result is not up to scratch, that is good use of time and the draft
> should not be adopted.
> 
> Thanks,
> Adrian
> 
>