Re: Status of this memo [WG consensus]

Brian E Carpenter <brian.e.carpenter@gmail.com> Tue, 27 April 2021 23:17 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 E69E03A23A5 for <ietf@ietfa.amsl.com>; Tue, 27 Apr 2021 16:17:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level:
X-Spam-Status: No, score=-2.099 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, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, 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 4OGsvNZPSRfm for <ietf@ietfa.amsl.com>; Tue, 27 Apr 2021 16:17:17 -0700 (PDT)
Received: from mail-pj1-x102e.google.com (mail-pj1-x102e.google.com [IPv6:2607:f8b0:4864:20::102e]) (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 676523A24C3 for <ietf@ietf.org>; Tue, 27 Apr 2021 16:16:20 -0700 (PDT)
Received: by mail-pj1-x102e.google.com with SMTP id j6-20020a17090adc86b02900cbfe6f2c96so8088288pjv.1 for <ietf@ietf.org>; Tue, 27 Apr 2021 16:16:20 -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=+/JNsQcbNZL5xectj70ZP+NZbZMClUryTldxG5Bhjac=; b=u1kv+aOQGfcfgORakp4rZ3duBQf8E/8/aDSKDEEhEg+/KbuE0Of4vrMD2qmUlueB6s e67XBYIPunuJrjT5jg3WF/VNKsZ535pBn+yKnMbyVngHya2nZbODNe9Mqj75RZp1/NoL 3yPN/5M2ltn1Bj/VYdQh/6wy/EgmgheAvmBeJp0AY0O5M2J9WQCR1lL8kFpY9N7pnIZC M1SpPLG17XLx+9/pGdHnQqqRu7qzIQOCEKF3jpMcidcGowsRHEXUsAOCtctBk+ABofZ8 0dThqcsgbhtrZYUdG35WoJ7bv6FS7qiQUk/CNvlJcaUHhmXI8yloo7OCfANovmaGjzux fp+A==
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=+/JNsQcbNZL5xectj70ZP+NZbZMClUryTldxG5Bhjac=; b=I15UQxNTthW5blpy0CEr6aZkBB44ipaRB3Qc0IzCtVzQUTabTAy/sd6vKK6CAuMwKZ FJnsIJLM4Yb7Of8vUITTuS8uV8QifpbhfprYOPBYZuHONmg3ZF6NCjdIxYAk13Pg/D2e mphUaEJwun5dCFulDFYSk7UlHPIvlYLnXckjoHOOTjNA57rnBpgUi5mp0X5K2qWvfNNt R9UzLRFvcf/LTS3vq2cH8T+vSWC/6mjTghWk9xO+IwlyocHaWVuq3ZQe1rrJBHXUu324 ckvFGkXrBuCDJ3YWfz7YOHDBbuSlvFhc2d9+AoKZ+TrmYdFBLZuYh5ZVA5kPXnd9Tnkb XkMg==
X-Gm-Message-State: AOAM531xhWId4sKsxggnNyqvSb/5CW/n5kCYyVzEt6fuUc0xkY+M22Df Q9+TU7msjjWrgiW/NHO9ZYf+v7vvemqkUw==
X-Google-Smtp-Source: ABdhPJyHaWYCMvo3YZy/KqZaMc+2U/2uOamPxUJe2p69IGw4Z5L0p5K8Jl/ZXxVWJs4hjx3iGqu6yQ==
X-Received: by 2002:a17:902:a705:b029:ec:bd14:7825 with SMTP id w5-20020a170902a705b02900ecbd147825mr27117123plq.83.1619565379214; Tue, 27 Apr 2021 16:16:19 -0700 (PDT)
Received: from [130.216.38.176] (sc-cs-567-laptop.uoa.auckland.ac.nz. [130.216.38.176]) by smtp.gmail.com with ESMTPSA id q3sm654404pgb.80.2021.04.27.16.16.17 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Tue, 27 Apr 2021 16:16:18 -0700 (PDT)
Subject: Re: Status of this memo [WG consensus]
To: "Andrew G. Malis" <agmalis@gmail.com>, Martin Vigoureux <martin.vigoureux@nokia.com>
Cc: IETF Discussion <ietf@ietf.org>
References: <376f83f0-89a3-cd0e-1792-c8434bd8a5d2@gmail.com> <9ACE59FA-30B6-475A-AF6B-4B874E4A2788@eggert.org> <1804294246.5904.1619512137931@appsuite-gw2.open-xchange.com> <D653D3B2-7666-409A-B856-2A4B1BA958CA@eggert.org> <3DBB64B1-40B8-4BC3-B66C-7F9B7F395874@akamai.com> <b5210c71-9500-3dba-05d2-4ae1c6ad16e9@network-heretics.com> <CAA=duU1VJs2vCE=uCF=fXO7FNedn9yPAaZWTgcaAiHTexA8uWA@mail.gmail.com> <2c48c55c-fd37-6ced-e025-707eb145a27b@nokia.com> <CAA=duU1zuZ0ae_fK9vQkkRxFffgitLpATxwNcpfeftepBpY4=w@mail.gmail.com>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Message-ID: <363d636a-38cf-d62c-202a-f92cc4153dc1@gmail.com>
Date: Wed, 28 Apr 2021 11:16:14 +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: <CAA=duU1zuZ0ae_fK9vQkkRxFffgitLpATxwNcpfeftepBpY4=w@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"
Content-Language: en-US
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/JtjdMR8iZ5ShCegisGBLlhvjuG4>
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: Tue, 27 Apr 2021 23:17:22 -0000

On 28-Apr-21 06:08, Andrew G. Malis wrote:
> Martin,
> 
> A draft reflects WG consensus when it has the name draft-ietf-wg-.... (that's the definition of that name). Before then, it's just a proposal from one or more individuals.

Actually, no. It only reflects consensus to work on the topic with draft in question as a basis. It does not imply that the WG will reach rough consensus on the draft. It is not uncommon for adopted drafts to fade away, fail to reach WG Last Call, or fail to reach WG consensus after WG Last Call. As Martin says downthread, it's only when the draft is sent off to the AD that we can be sure that the WG chairs have called consensus.

   Brian

> 
> It's the document editor and WG chair's jobs to make sure that WG drafts do in fact reflect WG status. If a WG participant disagrees with the editor and the chair that the draft reflects WG consensus, they can appeal to an AD or the IESG as a whole.
> 
> This is from RFC 2418:
> 
> 6.3. Document Editor
> 
>    Most IETF working groups focus their efforts on a document, or set of
>    documents, that capture the results of the group's work.  A working
>    group generally designates a person or persons to serve as the Editor
>    for a particular document.  The Document Editor is responsible for
>    ensuring that the contents of the document accurately reflect the
>    decisions that have been made by the working group.
> 
>    As a general practice, the Working Group Chair and Document Editor
>    positions are filled by different individuals to help ensure that the
>    resulting documents accurately reflect the consensus of the working
>    group and that all processes are followed.
> 
> Cheers,
> Andy
> 
> 
> On Tue, Apr 27, 2021 at 12:07 PM Martin Vigoureux <martin.vigoureux@nokia.com <mailto:martin.vigoureux@nokia.com>> wrote:
> 
>     Andy,
> 
>     quick question, if I may:
> 
>     Le 2021-04-27 à 17:06, Andrew G. Malis a écrit :
>     > Keith,
>     >
>     > I disagree. WGs have charters, which result in RFCs. During that
>     > process, they have consensus-based working drafts that are refined to
>     > meet their charter goals. That's an "adopted" draft. But it doesn't have
>     > to be based on a single individual draft, a working draft can be the
>     > result of merging earlier individual drafts, or can even originate as a
>     > WG draft without a preceding individual draft or drafts. But yes,
>     > working drafts do reflect WG consensus, and they have formal standing as
>     > such.
>     At which point in time to do they reflect WG consensus, according to you?
>     As examples to illustrate my ask: From day 1 or only at "Publication
>     Requested" time, or some other time, if any specific one?
> 
>     -m
> 
> 
>     >
>     > Cheers,
>     > Andy
>     >
>     >
>     > On Tue, Apr 27, 2021 at 10:27 AM Keith Moore <moore@network-heretics.com <mailto:moore@network-heretics.com>
>     > <mailto:moore@network-heretics.com <mailto:moore@network-heretics.com>>> wrote:
>     >
>     >     On 4/27/21 10:17 AM, Salz, Rich wrote:
>     >
>     >>>         There was also a suggestion to add something to the boilerplate text of individual I-Ds along the lines of "anyone can submit an I-D; they have no formal standing until they are adopted by a group in the IETF or IRTF". Would that provide additional clarification?
>     >>     Oh yes, PLEASE!
>     >
>     >     concur.   Except get rid of the "adopted" bit, because even assuming
>     >     that "adoption" of a draft by a WG is useful, it doesn't imply any
>     >     kind of broad support from the organization.   Just say that the
>     >     existence of a draft does not mean it has any formal standing with
>     >     IETF or any other organization.   Documents with formal standing in
>     >     IETF are published as RFCs.
>     >
>     >     Keith
>     >
>     >
>