Re: [Rfced-future] Consensus check: Issue 22 – new stream for RFC Editor
Michael StJohns <msj@nthpermutation.com> Tue, 22 June 2021 23:31 UTC
Return-Path: <msj@nthpermutation.com>
X-Original-To: rfced-future@ietfa.amsl.com
Delivered-To: rfced-future@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 71BD93A1F42 for <rfced-future@ietfa.amsl.com>; Tue, 22 Jun 2021 16:31:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.235
X-Spam-Level:
X-Spam-Status: No, score=-2.235 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, NICE_REPLY_A=-0.338, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=nthpermutation-com.20150623.gappssmtp.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 sHZfegbW_UUm for <rfced-future@ietfa.amsl.com>; Tue, 22 Jun 2021 16:31:13 -0700 (PDT)
Received: from mail-qv1-xf2c.google.com (mail-qv1-xf2c.google.com [IPv6:2607:f8b0:4864:20::f2c]) (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 503D83A1F3F for <rfced-future@iab.org>; Tue, 22 Jun 2021 16:31:13 -0700 (PDT)
Received: by mail-qv1-xf2c.google.com with SMTP id r19so495951qvw.5 for <rfced-future@iab.org>; Tue, 22 Jun 2021 16:31:13 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nthpermutation-com.20150623.gappssmtp.com; s=20150623; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-transfer-encoding:content-language; bh=h88HqV72KH5Wxu0k8METr0J9qdoEYFiba9mtzrn61Fk=; b=RQRFYxBBuuohh0ZY8AZSnwbJodE191q27pdZLuSb/Mw6CndOrL7jwtz5oA2C/wubGo ruuY288nv6bTQOdLjEsdzmla8UajgM156KVdtBJ1O+BNmcDxGKz0xt4fr83pelxmT/PU PasLdRjL1rFLy2Wdw8xrRfV2d9FWpaIa6srTbhwA/UYSI/rxQLNQFybztcb4mSVn2qs1 nktC5/Ye8i+0LloGWCIOYhRBbz7TRzPaAw+dyq4gLQJxFS4CWELC5H8gChI3kvFUa8v5 zKfvBiZJsFF3lxeGbNVrYczonKRjkho/jz29deXP9iONTEfV9Pc3nQtq58YXFi2Tnz/c awIQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding :content-language; bh=h88HqV72KH5Wxu0k8METr0J9qdoEYFiba9mtzrn61Fk=; b=e+ju840Jk+A/5AzSSHRgT5bNNJi5U9EuXTkG9YwAIYHB53eYOqu8M/0Rz+vMYsdoOt 1NEgSonDvzHGNphBk5avfxu3Ga/oTmPLANdfas0vJI1Brzcl9K8Bmy0iiLP4jSM6yygT Z0oGXnm/PhkkBaMRyRpKRvoCGkNn+9phsikvGStASIwB1rrFwDD8P3Ataud/v1RBDYdO P9Qk5fQtWwqZbBt7WrAdleRNY/ridsaVEsgEMb8z62MsUp6EG1C6XRmQ1C+k52WXaFmj o7c6Bvh0ucGM7KnWjTz1W3xD1NW5zr5YFTT+GtKkbJ+e4XN/uP+Rr3ctpI/4MiFcFPfY 7Glw==
X-Gm-Message-State: AOAM5304wsmFUi1VvhrJ4skcRSSH5KHGpqmq/epgziShyX+pXesiObxM p2vf/7TfmHUqpbUxwmFHAuTt5+8ZBgH28DoI
X-Google-Smtp-Source: ABdhPJwaj7in5KywdNrvYagc00A1tjgc7HI4JZkA+GzpV3R6aoTVQiozTTurg0Q4tc3jXiSxDJ6RBQ==
X-Received: by 2002:a05:6214:242f:: with SMTP id gy15mr271942qvb.9.1624404671094; Tue, 22 Jun 2021 16:31:11 -0700 (PDT)
Received: from [192.168.1.23] (pool-108-51-200-187.washdc.fios.verizon.net. [108.51.200.187]) by smtp.gmail.com with ESMTPSA id k139sm14376970qke.96.2021.06.22.16.31.09 for <rfced-future@iab.org> (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Tue, 22 Jun 2021 16:31:10 -0700 (PDT)
To: rfced-future@iab.org
References: <7ef10df2-cb21-a95b-b977-286b6d8a8405@lear.ch> <0a8101d76788$0e1af5a0$2a50e0e0$@olddog.co.uk> <fdb50b3a-a0e1-1421-4a4f-733002cfccda@lear.ch> <0ace01d767a5$39001350$ab0039f0$@olddog.co.uk> <7bda1df1-307b-4370-ad94-71af09af12c4@www.fastmail.com> <47618d03-3136-a4db-cd5b-66a1e89216ac@gmail.com>
From: Michael StJohns <msj@nthpermutation.com>
Message-ID: <492d7b65-33b9-e749-3297-85fe6779531c@nthpermutation.com>
Date: Tue, 22 Jun 2021 19:31:09 -0400
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.11.0
MIME-Version: 1.0
In-Reply-To: <47618d03-3136-a4db-cd5b-66a1e89216ac@gmail.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/rfced-future/KBJKoIBZQvUSpe9nwhJiPuqgHqA>
Subject: Re: [Rfced-future] Consensus check: Issue 22 – new stream for RFC Editor
X-BeenThere: rfced-future@iab.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: RFC Editor Future Development Program <rfced-future.iab.org>
List-Unsubscribe: <https://www.iab.org/mailman/options/rfced-future>, <mailto:rfced-future-request@iab.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rfced-future/>
List-Post: <mailto:rfced-future@iab.org>
List-Help: <mailto:rfced-future-request@iab.org?subject=help>
List-Subscribe: <https://www.iab.org/mailman/listinfo/rfced-future>, <mailto:rfced-future-request@iab.org?subject=subscribe>
X-List-Received-Date: Tue, 22 Jun 2021 23:31:16 -0000
On 6/22/2021 6:01 PM, Brian E Carpenter wrote: > On 23-Jun-21 09:30, Martin Thomson wrote: >> On Wed, Jun 23, 2021, at 06:28, Adrian Farrel wrote: >>> I think a stream exists because an organisation has requested to >>> publish within the RFC Series. >>> The owner of the Series surely decides whether to allow publication and >>> whether a new stream is appropriate. >>> >>> I'm also interested in how a stream is shut down. Who makes that decision? >> My simple answer to both of these is: the RSWG proposes a change to the structure (add a stream, remove a stream) and the RSAB approves it. I think that both warrant publishing an RFC that documents the addition. > Fully agreed, except that as just noted, I believe that creating the editorial stream, publishing the new model, and fixing the IAB charter must be done as a piece of synchronized swimming. Nah. The last can be done by something like" "This document supersedes and replaces any previous grant or assumption of authority to the IAB claimed in the IAB charter (ref...) or other documents as applies to the selection and oversight of the RFC Editor and the RFC series". Add "Updates: " to the tag line to refer back to the IAB charter. No reason to require anything more than that I would expect. For the stream: "This document mandates the creation of the Editorial stream to be managed by the RSA/E and for the publication of documents created through the auspices of the RSWG and the RSAB." Maybe one or both additional statements: "Stream is limited to documents that affect the operation, publication and sustainment of the RFC Series" and "The RSWG and RSAB shall issue additional documents as necessary to refine the processes for acceptance and publication of documents on the Editorial stream and the implementation of related changes to the operation of the RFC publication process." Mike > > Brian C. > >
- [Rfced-future] Consensus check: Issue 22 – new st… Eliot Lear
- Re: [Rfced-future] Consensus check: Issue 22 – ne… Adrian Farrel
- Re: [Rfced-future] Consensus check: Issue 22 – ne… Eliot Lear
- Re: [Rfced-future] Consensus check: Issue 22 – ne… Adrian Farrel
- Re: [Rfced-future] Consensus check: Issue 22 – ne… Martin Thomson
- Re: [Rfced-future] Consensus check: Issue 22 – ne… Brian E Carpenter
- Re: [Rfced-future] Consensus check: Issue 22 – ne… Brian E Carpenter
- Re: [Rfced-future] Consensus check: Issue 22 – ne… Michael StJohns
- Re: [Rfced-future] Consensus check: Issue 22 – ne… Jay Daley
- Re: [Rfced-future] Consensus check: Issue 22 – ne… Brian E Carpenter
- Re: [Rfced-future] Consensus check: Issue 22 – ne… Joel M. Halpern
- Re: [Rfced-future] Consensus check: Issue 22 – ne… Jay Daley
- Re: [Rfced-future] Consensus check: Issue 22 – ne… Martin Thomson
- Re: [Rfced-future] Consensus check: Issue 22 – ne… Eliot Lear
- Re: [Rfced-future] Consensus check: Issue 22 – ne… Jay Daley
- Re: [Rfced-future] Consensus check: Issue 22 – ne… Joel Halpern Direct
- Re: [Rfced-future] Consensus check: Issue 22 – ne… Adrian Farrel
- Re: [Rfced-future] Consensus check: Issue 22 – ne… Eliot Lear
- Re: [Rfced-future] Consensus check: Issue 22 – ne… Eliot Lear
- Re: [Rfced-future] Consensus check: Issue 22 – ne… Michael StJohns
- [Rfced-future] BCP or not [was: Consensus check: … Brian E Carpenter
- Re: [Rfced-future] Consensus check: Issue 22 – ne… Brian E Carpenter
- Re: [Rfced-future] Consensus check: Issue 22 – ne… Jay Daley
- Re: [Rfced-future] Consensus check: Issue 22 – ne… Brian E Carpenter
- Re: [Rfced-future] Consensus check: Issue 22 – ne… Lars Eggert
- Re: [Rfced-future] Consensus check: Issue 22 – ne… Martin J. Dürst
- Re: [Rfced-future] Consensus check: Issue 22 – ne… Brian E Carpenter
- Re: [Rfced-future] Consensus check: Issue 22 – ne… Mirja Kuehlewind
- Re: [Rfced-future] Consensus check: Issue 22 – ne… Joel M. Halpern
- Re: [Rfced-future] Consensus check: Issue 22 – ne… Mirja Kuehlewind
- Re: [Rfced-future] Consensus check: Issue 22 – ne… Eliot Lear
- Re: [Rfced-future] Consensus check: Issue 22 – ne… Christian Huitema
- Re: [Rfced-future] Consensus check: Issue 22 – ne… Joel M. Halpern
- Re: [Rfced-future] Consensus check: Issue 22 – ne… Michael StJohns
- Re: [Rfced-future] Consensus check: Issue 22 – ne… Bob Hinden
- Re: [Rfced-future] Consensus check: Issue 22 – ne… Peter Saint-Andre
- Re: [Rfced-future] Consensus check: Issue 22 – ne… Peter Saint-Andre
- Re: [Rfced-future] Consensus check: Issue 22 – ne… Peter Saint-Andre
- Re: [Rfced-future] Consensus check: Issue 22 – ne… Peter Saint-Andre
- Re: [Rfced-future] Consensus check: Issue 22 – ne… Joel M. Halpern
- Re: [Rfced-future] Consensus check: Issue 22 – ne… Peter Saint-Andre
- Re: [Rfced-future] Consensus check: Issue 22 – ne… Brian E Carpenter
- Re: [Rfced-future] Consensus check: Issue 22 – ne… Brian E Carpenter
- Re: [Rfced-future] Consensus check: Issue 22 – ne… Joel Halpern Direct
- Re: [Rfced-future] Consensus check: Issue 22 – ne… Brian E Carpenter
- [Rfced-future] RSAB membership (was Re: Consensus… Eliot Lear
- Re: [Rfced-future] RSAB membership (was Re: Conse… Brian E Carpenter