Re: Status of this memo
Michael StJohns <mstjohns@comcast.net> Tue, 27 April 2021 23:43 UTC
Return-Path: <mstjohns@comcast.net>
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 D06813A25BA for <ietf@ietfa.amsl.com>; Tue, 27 Apr 2021 16:43:52 -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_BLOCKED=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=comcast.net
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 9Wj58mT2A0Pu for <ietf@ietfa.amsl.com>; Tue, 27 Apr 2021 16:43:50 -0700 (PDT)
Received: from resqmta-ch2-09v.sys.comcast.net (resqmta-ch2-09v.sys.comcast.net [IPv6:2001:558:fe21:29:69:252:207:41]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7B6403A25B7 for <ietf@ietf.org>; Tue, 27 Apr 2021 16:43:50 -0700 (PDT)
Received: from resomta-ch2-13v.sys.comcast.net ([69.252.207.109]) by resqmta-ch2-09v.sys.comcast.net with ESMTP id bWfPlwX5UkWizbXMql29kc; Tue, 27 Apr 2021 23:43:48 +0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=20190202a; t=1619567028; bh=wK5zNF3zIwdDdd6IVqmkyTZdM8RRerppkeV7TIJTYNY=; h=Received:Received:Subject:To:From:Message-ID:Date:MIME-Version: Content-Type; b=3Nqypg0Y34WInSnf35fKydTuU1GJYllQ5ZQoQtiRIvu0qvC4v6JJJmHE76oljOY70 BCL1eABBnBJ56baus5ylEjAQhWeD8YmctQX1zX8HzKpY0OUNn9TbxcoPEoqAZtJTLd pPITeuCldJcPY/81aX9oH0cI5TEuH+LkliX6k7B09ZwIGhlXCEADZCyYBDO/tQTvKc El3VUe44QZII1GwJlomaKOwME/rIHdiFlqziDfk9P380gPKVluUNFfGKK0KOIlcZcJ v1q+LFta82L+2Pt3uG5ueqncughlg7PWhLabgwGtyTr7wdCkt14q0UsIw9WeiR2sDa iDkenXb9cH8qA==
Received: from [192.168.1.23] ([72.83.11.195]) by resomta-ch2-13v.sys.comcast.net with ESMTPSA id bXMglSgJ2Ca1tbXMhlWUxU; Tue, 27 Apr 2021 23:43:46 +0000
X-Xfinity-VAAS: gggruggvucftvghtrhhoucdtuddrgeduledrvddvuddgvdefucetufdoteggodetrfdotffvucfrrhhofhhilhgvmecuvehomhgtrghsthdqtfgvshhipdfqfgfvpdfpqffurfetoffkrfenuceurghilhhouhhtmecufedtudenucenucfjughrpefuvfhfhffkffgfgggjtgfgsehtkeertddtfeejnecuhfhrohhmpefoihgthhgrvghlucfuthflohhhnhhsuceomhhsthhjohhhnhhssegtohhmtggrshhtrdhnvghtqeenucggtffrrghtthgvrhhnpeefieevjeehueduvdfhveelgfelffegheejiefhhfevtdekkeelfeehhfejledtgeenucfkphepjedvrdekfedruddurdduleehnecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehhvghloheplgduledvrdduieekrddurddvfegnpdhinhgvthepjedvrdekfedruddurdduleehpdhmrghilhhfrhhomhepmhhsthhjohhhnhhssegtohhmtggrshhtrdhnvghtpdhrtghpthhtohepihgvthhfsehivghtfhdrohhrgh
X-Xfinity-VMeta: sc=0.00;st=legit
Subject: Re: Status of this memo
To: ietf@ietf.org
References: <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> <CAF4+nEEz4x3HtUhWQ0ONYCpyHy27E4u7_chVEuHi3rDr+sc39A@mail.gmail.com> <b3762d56-bff2-6f71-caa2-69d34e81b9dc@network-heretics.com> <20210427215415.GK79563@kduck.mit.edu> <aafedd93-0f90-aaa4-966e-8fef9573149e@network-heretics.com> <20210427222219.GN79563@kduck.mit.edu> <b5741e60-fd4c-ca3d-3973-ae1652bb42e9@network-heretics.com> <a6b57eef-1a1e-2416-a98d-dfeda824dcf0@joelhalpern.com>
From: Michael StJohns <mstjohns@comcast.net>
Message-ID: <2dc0326b-766e-1076-eee2-b225e30f7f67@comcast.net>
Date: Tue, 27 Apr 2021 19:43:38 -0400
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.9.1
MIME-Version: 1.0
In-Reply-To: <a6b57eef-1a1e-2416-a98d-dfeda824dcf0@joelhalpern.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/bXN1Kzt5sOQdVmmLXg0781fNf_w>
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:43:53 -0000
On 4/27/2021 7:12 PM, Joel M. Halpern wrote: > Once the WG adopts the document, the WG owns it, and the document pen > holder (original author or otherwise) is expected to work according to > the direciton of the WG. Hi Joel - I'm lacking a reference for that specific claim in the various documents that describe the process of getting a document published as an RFC. Could you provide one please? E.g. where does it say that the WG owns it? For that matter, where does it say that a WG needs to formally adopt a document to work on it? I would say instead that the WG may - when faced with a recalcitrant author/editor a) replace them, b) decline to advance the document. In my experience (a) has been difficult to achieve simply because you may not be able to find anyone else who cares enough to do the grunt work of taking the slings and arrows of the WG and turning it into a publishable document. So the person who holds the pen, also tends to have a bit more say over the content of the document - that's just the reality of things. Later, Mike
- 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