Re: Status of this memo
John C Klensin <john-ietf@jck.com> Tue, 27 April 2021 19:43 UTC
Return-Path: <john-ietf@jck.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 12D4D3A1DCA for <ietf@ietfa.amsl.com>; Tue, 27 Apr 2021 12:43:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level:
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_NONE=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 XFvavRn8fGaU for <ietf@ietfa.amsl.com>; Tue, 27 Apr 2021 12:43:47 -0700 (PDT)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5A2653A1DC9 for <ietf@ietf.org>; Tue, 27 Apr 2021 12:43:47 -0700 (PDT)
Received: from [198.252.137.10] (helo=PSB) by bsa2.jck.com with esmtp (Exim 4.82 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1lbTcW-000DUV-J0; Tue, 27 Apr 2021 15:43:44 -0400
Date: Tue, 27 Apr 2021 15:43:38 -0400
From: John C Klensin <john-ietf@jck.com>
To: "Andrew G. Malis" <agmalis@gmail.com>, Martin Vigoureux <martin.vigoureux@nokia.com>
cc: IETF Discussion <ietf@ietf.org>
Subject: Re: Status of this memo
Message-ID: <C422B69434A3E9B97DC5E628@PSB>
In-Reply-To: <CAA=duU1zuZ0ae_fK9vQkkRxFffgitLpATxwNcpfeftepBpY4=w@mail.gmail.com>
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>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-SA-Exim-Connect-IP: 198.252.137.10
X-SA-Exim-Mail-From: john-ietf@jck.com
X-SA-Exim-Scanned: No (on bsa2.jck.com); SAEximRunCond expanded to false
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/XJmvzu2axvTorX0fctfNAPW2cDA>
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:43:49 -0000
--On Tuesday, April 27, 2021 14:08 -0400 "Andrew G. Malis" <agmalis@gmail.com> 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. >... Andrew, I'd dispute even that. Identification as a WG draft definitely means that the draft represents some sort of WG consensus that the draft is something the WG intends to discuss and use as a basis for further development. It does not imply WG agreement with the details or ideas expressed in the draft (if, indeed, details are present) although, at some stages of development, it might. I think that position is consistent with RFC 7221, noting that it says "might be a blank sheet...". > 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. Sure, but let's be very clear about what that consensus is about or what it means. This is the same distinction I hope the IESG intended to make when they issued as statement that any document published in the IETF Steam -- including Informational or Experimental ones -- needed IETF consensus. Consensus that information is good to publish or that an experiment is worth documenting and performing does not constitute (and, IMO, should not require) IETF agreement with the ideas being expressed or even that the experimental spec would be worth standardizing if the experiment is later judged as having succeeded. >... > 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. >... Right. But, again, the WG may have made no decisions more specific than "this draft, in its current state, is a good starting point for future discussion". And that would be true even if an editor included strawman (or some other straw person or object) positions intended to stimulate discussion rather than being expected to reflect WG consensus. >... best, john
- Status of this memo Brian E Carpenter
- Re: Status of this memo Phillip Hallam-Baker
- Re: Status of this memo Lars Eggert
- Re: Status of this memo Vittorio Bertola
- Re: Status of this memo Lars Eggert
- Re: Status of this memo Donald Eastlake
- Re: Status of this memo Carsten Bormann
- Re: Status of this memo Andrew G. Malis
- Re: Status of this memo Keith Moore
- Re: Status of this memo Carsten Bormann
- Re: Status of this memo Keith Moore
- Re: Status of this memo Lars Eggert
- Re: Status of this memo Lloyd W
- Re: Status of this memo Keith Moore
- Re: Status of this memo Lars Eggert
- Re: Status of this memo Scott Brim
- Re: Status of this memo Vittorio Bertola
- Re: Status of this memo Keith Moore
- Re: Status of this memo Scott Bradner
- Re: Status of this memo Phillip Hallam-Baker
- Re: Status of this memo Keith Moore
- Re: Status of this memo Keith Moore
- Re: Status of this memo Charles Eckel (eckelcu)
- Re: Status of this memo Salz, Rich
- Re: Status of this memo Keith Moore
- Re: Status of this memo Andrew G. Malis
- Re: Status of this memo Phillip Hallam-Baker
- Re: Status of this memo Keith Moore
- Re: Status of this memo Joel M. Halpern
- Re: Status of this memo Keith Moore
- Re: Status of this memo Martin Vigoureux
- Re: Status of this memo Carsten Bormann
- Re: Status of this memo Phillip Hallam-Baker
- Re: Status of this memo Keith Moore
- Re: Status of this memo Bob Hinden
- Re: Status of this memo Phillip Hallam-Baker
- Re: Status of this memo Andrew G. Malis
- Re: Status of this memo Donald Eastlake
- Re: Status of this memo Keith Moore
- Re: Status of this memo Donald Eastlake
- Re: Status of this memo Keith Moore
- Re: Status of this memo Donald Eastlake
- Re: Status of this memo Donald Eastlake
- Re: Status of this memo Keith Moore
- RE: Status of this memo Michael McBride
- Re: Status of this memo Keith Moore
- Re: Status of this memo Carsten Bormann
- Re: Status of this memo Keith Moore
- Re: Status of this memo Donald Eastlake
- Re: Status of this memo Donald Eastlake
- Re: Status of this memo Donald Eastlake
- Re: Status of this memo John C Klensin
- Re: Status of this memo Martin Vigoureux
- Re: Status of this memo Phillip Hallam-Baker
- Re: Status of this memo John C Klensin
- Re: Status of this memo Michael StJohns
- Re: Status of this memo Martin Vigoureux
- Re: Status of this memo Benjamin Kaduk
- Re: Status of this memo Randy Presuhn
- Re: Status of this memo Keith Moore
- Re: Status of this memo Phillip Hallam-Baker
- Re: Status of this memo Benjamin Kaduk
- Re: Status of this memo Joel M. Halpern
- Re: Status of this memo John C Klensin
- Re: Status of this memo ned+ietf
- Re: Status of this memo Keith Moore
- Re: Status of this memo Keith Moore
- Re: Status of this memo Joel M. Halpern
- Re: Status of this memo [NOTE WELL] Brian E Carpenter
- Re: Status of this memo Keith Moore
- Re: Status of this memo [WG consensus] Brian E Carpenter
- Re: Status of this memo [name remixing] Brian E Carpenter
- Re: Status of this memo Scott Bradner
- Re: Status of this memo Joel M. Halpern
- Re: Status of this memo [name remixing] Christian Huitema
- Re: Status of this memo Michael StJohns
- Re: Status of this memo Keith Moore
- Re: Status of this memo ned+ietf
- Re: Status of this memo Joel M. Halpern
- Re: Status of this memo [NOTE WELL] Phillip Hallam-Baker
- Re: Status of this memo [WG consensus] Theodore Ts'o
- Re: Status of this memo Benjamin Kaduk
- Re: Status of this memo John C Klensin
- Re: Status of this memo Lloyd W
- Re: Status of this memo John C Klensin
- Re: Status of this memo Murray S. Kucherawy
- Re: Status of this memo Simon Josefsson
- Re: Status of this memo Lloyd W
- Re: Status of this memo Keith Moore
- Re: Status of this memo Keith Moore
- Re: Status of this memo Keith Moore
- Re: Status of this memo Salz, Rich
- RE: Status of this memo Gorman, Pierce
- Re: Status of this memo Nick Hilliard
- Re: Status of this memo tom petch
- Re: Status of this memo Warren Kumari
- Re: Status of this memo Brian E Carpenter
- Re: Status of this memo S Moonesamy