IETF Logo Mail Archive

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

Peter Saint-Andre <stpeter@mozilla.com> Fri, 25 June 2021 20:08 UTC

Return-Path: <stpeter@mozilla.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 B422D3A0CDD for <rfced-future@ietfa.amsl.com>; Fri, 25 Jun 2021 13:08: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, NICE_REPLY_A=-0.338, 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 (1024-bit key) header.d=mozilla.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 sugn-A9j-Jpx for <rfced-future@ietfa.amsl.com>; Fri, 25 Jun 2021 13:08:28 -0700 (PDT)
Received: from mail-il1-x130.google.com (mail-il1-x130.google.com [IPv6:2607:f8b0:4864:20::130]) (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 384113A0CDC for <rfced-future@iab.org>; Fri, 25 Jun 2021 13:08:28 -0700 (PDT)
Received: by mail-il1-x130.google.com with SMTP id g3so1897320ilj.7 for <rfced-future@iab.org>; Fri, 25 Jun 2021 13:08:28 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mozilla.com; s=google; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-language:content-transfer-encoding; bh=GY4YNMRn5qvSI1vE6RGNBRUeqoo6fhSsbJiym05L5vo=; b=aMllQVzW1eSB3J41jSc2fDmaxLX5wqb1nDPKeZTQz81FyEn/AWb6rNPRIyqGG6qp90 I+32P2xBndv0AgawCLXIlwfK2sfZsogGtsZw0ThtA7SLhbmKMMV94USOV+eBOaQpSUCO 3EOzmKbTqIkbuFlN9QVibGqxOsr/6PGzu6rDg=
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=GY4YNMRn5qvSI1vE6RGNBRUeqoo6fhSsbJiym05L5vo=; b=mIPnlUSgPPCDrXdRS8FyRDcgMZ+W+wdxJA7lnS8VM9nqC6euvF/REAIem010BMz9DM M9ZxxEGl9mqLL9ghpiHlfcAm7S8ippc1OWCtvSyvLcM8qKD7RsU8d+odKPTLKAhfEfZD ac3pWB6TfcH9CEy4mB+ZpNe5WVkog3PQzoW4VIJC3Mx5lQhU/AUO4HyDhWpM1aTR2C+3 p2DLzxFVK0XBQz37QTTGXEmILO3Y5cqlqJDovx2MC2oKYUE86swRw9R9TlH7ValU/ozq OwtTKQScrm8XoI2H2fVbYIWzBHGyf0TY6TLOQ+IJcDjjT88S0hXwWV1FAocMFHji62VN YYag==
X-Gm-Message-State: AOAM5322C+P88RrOELLtpJFxJDtlERhp4odtV1e9KnWIamIp8hksh7PC Akjjty8LeZMaKoB+lp5MbhlSO7EDGc+WpQ==
X-Google-Smtp-Source: ABdhPJz0P5TRJnNm/FSBiWmZb8qc5BrNJEWexMXZYjq07XsQYKDxkeIIG3x1RIalvZ9ncCFM5GkulQ==
X-Received: by 2002:a05:6e02:1288:: with SMTP id y8mr8461784ilq.86.1624651706848; Fri, 25 Jun 2021 13:08:26 -0700 (PDT)
Received: from dragon.local (c-73-78-113-156.hsd1.co.comcast.net. [73.78.113.156]) by smtp.gmail.com with ESMTPSA id n5sm1807361ilo.78.2021.06.25.13.08.25 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Fri, 25 Jun 2021 13:08: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: Peter Saint-Andre <stpeter@mozilla.com>
Message-ID: <9eeb8fdb-73d2-5ee4-6021-7aa39e8a9333@mozilla.com>
Date: Fri, 25 Jun 2021 14:08:24 -0600
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:78.0) Gecko/20100101 Thunderbird/78.11.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/YIDyj9EFlSAnfP4pCFRMp4CBr5c>
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: Fri, 25 Jun 2021 20:08:30 -0000

On 6/22/21 3:30 PM, 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.

That seems sensible.

Naturally, an existing stream could shut itself down, too, but I suppose
that could happen via the RSWG. Let's say the IRTF decides to close up
shop - the act of closing the IRTF stream could be done through an RFC
in the Editorial Stream.

Peter

v2.23.0 | Report a Bug | By Email