Re: [Rfced-future] Consensus check: Issue 22 – new stream for RFC Editor

Brian E Carpenter <brian.e.carpenter@gmail.com> Tue, 22 June 2021 22:01 UTC

Return-Path: <brian.e.carpenter@gmail.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 4A4493A1BD4 for <rfced-future@ietfa.amsl.com>; Tue, 22 Jun 2021 15:01:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.437
X-Spam-Level:
X-Spam-Status: No, score=-2.437 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.338, RCVD_IN_DNSWL_NONE=-0.0001, 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=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 xAb0Rjpx0OA9 for <rfced-future@ietfa.amsl.com>; Tue, 22 Jun 2021 15:01:28 -0700 (PDT)
Received: from mail-pg1-x531.google.com (mail-pg1-x531.google.com [IPv6:2607:f8b0:4864:20::531]) (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 EC0B93A1BD2 for <rfced-future@iab.org>; Tue, 22 Jun 2021 15:01:27 -0700 (PDT)
Received: by mail-pg1-x531.google.com with SMTP id v7so18223461pgl.2 for <rfced-future@iab.org>; Tue, 22 Jun 2021 15:01:27 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-language:content-transfer-encoding; bh=Byfwu+722Yo/eqzJjJuKadsR7quoQ1flxKtKFZqOrFE=; b=jEBXU+qU8/DV8Yq6H28AYNWD3uVgZ7c1TWZao/RU/U5Q7/DDZFkyG/M1zNUmwhAeWn aBBrWMjjZS8uK3fZVdroRcF4+K5aUrI5dqBM8ng9pCquZs65TZzthVrrbntHxpUvK4Ps +QH3Ym+u4pGFaEjPJct0GSsIcz1G8G18xoYMZLUBn83TCDRSCWlQOpf/w/gXtJSKzQB0 jKm5H8KKnR16KvtoUiwrIygG9np1uATIjFnBOgcW5ex3q8iHgF32ZAQZXV1xMEDOWn8p TEytZ7QdSWpEz1q0F/WqzeOgCXw7/Tli99LcP2VTAC0i1B7+yzPsEHbxgcD+TXPE3uA8 vv8Q==
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-language :content-transfer-encoding; bh=Byfwu+722Yo/eqzJjJuKadsR7quoQ1flxKtKFZqOrFE=; b=HCkXfsugPQsT9Vr3/EGBj6fpBrejHmS51PSNAUPh73IubGfA1qCugR4PRVJUKgmAKK NYZYsokGe4YJTtBsPnkRFpcsev3d3M62ZmURkxr5ccvCOqQAgoJTbMvhpc/wuPS03ZKW dXsUmN3EkN6B/m202sJMoNVhDlUq/B/2ZaQTE1vAAy1g5ZSwUYHRXwSxYoJISKHlqsVm sPwtWY0h3eF9d7eZQSlX/erXsf0tsWm/NecEj1Abn3qCE4wA5IABLyFhnA7k07IGkRAV ealb2jUk7+dZuLVWCkieM7ba5qIJuLEKitvpRcLiO6nnCO91aK82NjlA1H8Sq99lWNK2 Y/Ew==
X-Gm-Message-State: AOAM530zMU7XuKB1gAra9LdJE+uCBwUNaPtigVBg1L2fJJrRX/WKZ/DB 5akyyJWSIWUKch99Z9rN01GST+8ptxMwvg==
X-Google-Smtp-Source: ABdhPJyow7oHCvRgeGx63MwWoVUpkSyhk5Kl0B+eL38qAiu17m2mR1sj6AwBHc2GmRAHcAKZ/sZPJw==
X-Received: by 2002:a63:f20:: with SMTP id e32mr703884pgl.235.1624399286532; Tue, 22 Jun 2021 15:01:26 -0700 (PDT)
Received: from ?IPv6:2406:e003:100d:901:80b2:5c79:2266:e431? ([2406:e003:100d:901:80b2:5c79:2266:e431]) by smtp.gmail.com with ESMTPSA id w2sm3169362pjq.5.2021.06.22.15.01.24 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Tue, 22 Jun 2021 15:01:26 -0700 (PDT)
To: Martin Thomson <mt@lowentropy.net>, 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>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Message-ID: <47618d03-3136-a4db-cd5b-66a1e89216ac@gmail.com>
Date: Wed, 23 Jun 2021 10:01:22 +1200
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.10.0
MIME-Version: 1.0
In-Reply-To: <7bda1df1-307b-4370-ad94-71af09af12c4@www.fastmail.com>
Content-Type: text/plain; charset="utf-8"
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfced-future/RgZGwFwZQYhOiaQ1eqvBX0ZKdLw>
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 22:01:29 -0000

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.

   Brian C.