Re: Status of this memo

Donald Eastlake <d3e3e3@gmail.com> Tue, 27 April 2021 19:39 UTC

Return-Path: <d3e3e3@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 C584F3A1D98 for <ietf@ietfa.amsl.com>; Tue, 27 Apr 2021 12:39:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.848
X-Spam-Level:
X-Spam-Status: No, score=-1.848 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_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=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 MU_bUWC7-znm for <ietf@ietfa.amsl.com>; Tue, 27 Apr 2021 12:39:22 -0700 (PDT)
Received: from mail-io1-xd29.google.com (mail-io1-xd29.google.com [IPv6:2607:f8b0:4864:20::d29]) (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 273D13A1D93 for <ietf@ietf.org>; Tue, 27 Apr 2021 12:39:22 -0700 (PDT)
Received: by mail-io1-xd29.google.com with SMTP id e186so7726484iof.7 for <ietf@ietf.org>; Tue, 27 Apr 2021 12:39:22 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc:content-transfer-encoding; bh=VPS41lWKhlYhrxHKnG8MpvRjGWtfRoTivbd6+M8uFmI=; b=GfAP0+zytMNSx085zMyHgS7LmrhShDcql27GUT0EwSOtIGR7mN1I974+6q3iKrnwjc FVw38sAlRUnCXl3/RLKPYSepHQtAUPUNNVsHS4K4JWqnJ4Y9M1WTbZeGo4n2/zrB2wxv vMeKlTnd4OcFT50vbAE083CwG/gpMjQIiHYaJu9afG+JG4OuF58lWXt+aVkQPPmDbJSS pbgivSchgcfIxNCSYszNRoXLnpFAMjoq3NbQpClcXgpJHcsTMIBncCNDJeJTxt2g3dxU D0Zo84/CIbGkYWpWrSSGeY5+tzvh3XIFmliCjiDtU7yoRbL3R4zsps19Oz2Uje0TWhre v48Q==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=VPS41lWKhlYhrxHKnG8MpvRjGWtfRoTivbd6+M8uFmI=; b=tP9gbVbsArsPviKRA65cVPMq6P1cbSAaAf3grBco8vgaQ7DSWk5WNdJu4iUHHWvzHF DDSyHwYBlV5rpC6EtqbIUTitfIxsrRV1lu1XL8qYDIupbE7m1D/d+vfwDl9pN4qU3OPC +4/KU46Y4RvfCuPxxJhLMW87As1P7c9Dxd/NHxAe5d93KSjCWvkln8DRZ1sP0Fme1rSd gVCTOKSp4au5+FeVMuO+KSemjSrBKZ+KxT3HZ+zrIcBP+9PRAwbpxpLSVZWYUoyafrVa i3ItYZurErcbLMpLhWKRD//sdmoknADKnfn7zcLac8HhHmJ7LfwJhBmkBPuuhYkd+dc1 AiSQ==
X-Gm-Message-State: AOAM530+a/ol3PcOjv9GWdbqlIxitpgrljJ22swOV/OrZx+zT8IrujOS Am8CVX+OP6gbbPcJUlcEXqSS0BmxclmFw9TLXCThZGvChvoZow==
X-Google-Smtp-Source: ABdhPJxQ3zOUCtmtDr+RtW49RPb7eiwCxtCL+rTNS/9WIuIFXwhBrT6UPpcYgirAC6msOEMdyC79EcVdt7ad+xiZWS0=
X-Received: by 2002:a02:c017:: with SMTP id y23mr23862622jai.48.1619552360048; Tue, 27 Apr 2021 12:39:20 -0700 (PDT)
MIME-Version: 1.0
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>
In-Reply-To: <2c48c55c-fd37-6ced-e025-707eb145a27b@nokia.com>
From: Donald Eastlake <d3e3e3@gmail.com>
Date: Tue, 27 Apr 2021 15:39:08 -0400
Message-ID: <CAF4+nEEXZacC+AEjFqabQAE8A2e9s=065zaSgEUybn+r-L6E+w@mail.gmail.com>
Subject: Re: Status of this memo
To: Martin Vigoureux <martin.vigoureux@nokia.com>
Cc: ietf@ietf.org
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/XC2QLRZ3yBYiu6eJL0bZKB7_Xs0>
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 19:39:27 -0000

Hi Martin,

On Tue, Apr 27, 2021 at 12:07 PM Martin Vigoureux
<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?

I can give you my opinion, which may be different from Andy's:

When a draft is adopted, it means it is the Chair's judgement that
there is WG consensus that it is a reasonable point from which to
start. (Note: "a" reasonable point, not necessarily the only one.)
There can easily be one or more technical items in the draft that, at
the time of adoption, are clearly against WG consensus. (In which case
I think the best practice is to post a -00 with the minimum changes to
make it a WG draft and then post a -01 with those technical items
changed to WG consensus.)

The entire draft is not determined to be WG consensus until the Chair
says so, most commonly at the end of a WG Last Call.

Thanks,
Donald
===============================
 Donald E. Eastlake 3rd   +1-508-333-2270 (cell)
 2386 Panoramic Circle, Apopka, FL 32703 USA
 d3e3e3@gmail.com

> -m
>
> > Cheers,
> > Andy
> >
> >
> > On Tue, Apr 27, 2021 at 10:27 AM Keith Moore <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