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

Brian E Carpenter <brian.e.carpenter@gmail.com> Tue, 22 June 2021 21:59 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 C8A7B3A1BC2 for <rfced-future@ietfa.amsl.com>; Tue, 22 Jun 2021 14:59:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.435
X-Spam-Level:
X-Spam-Status: No, score=-2.435 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_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=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 FKVU4rftBuhc for <rfced-future@ietfa.amsl.com>; Tue, 22 Jun 2021 14:59:21 -0700 (PDT)
Received: from mail-pl1-x62d.google.com (mail-pl1-x62d.google.com [IPv6:2607:f8b0:4864:20::62d]) (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 982543A1BC0 for <rfced-future@iab.org>; Tue, 22 Jun 2021 14:59:21 -0700 (PDT)
Received: by mail-pl1-x62d.google.com with SMTP id f10so35938plg.0 for <rfced-future@iab.org>; Tue, 22 Jun 2021 14:59:21 -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=stQZF9RRnGOoXycMGyEEiHwVZCoILz6B3EnRFN34cdE=; b=qaQli51vQEsaX61B39z8MlLpfO87Ic98ycEHyI7fAGfoXSIbm2etkZxBlHkVlalWZK 73Kv6QK9VdZwKnFa3rikn4lqm5YmGDRpflGSgLQ0SPfTNPK3Bh7KlApYftd0QT5rT0MU O3fGpcz7Ln9wF5gVnRB7noeY3jP9gspd+yMvyoXV4+ZMhyYybMn9Fpo2xNZpz8MQpw/K w53NW+6Si/Mori+4FfU0xQ0szvWysB3r+jvHZre/RYVtWyGJsAWGxV83iILBguVcWNaG +BO1UhXqZHivOeShS+Wp2tT2vTLu1UzbnUq9pDY4T0HP2pWSJor0bL5Ev6LzMoHKfFre cuDw==
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=stQZF9RRnGOoXycMGyEEiHwVZCoILz6B3EnRFN34cdE=; b=tLLFAnOciG38k32I1/IsV9LTAG2UDFxQdrdfJA2PD5jdbUcNqWIp+TCeSBF8L4cJMB 9BScis4/dmeqf0C8xSD9YbmScqfgMsfS+2nfFIktofkef8ZO0OyQXrNo04K2L/C6eYGg xMbN+9DSDNXIyPKSNhBq9lk972Y6flOcLz49x/rUJ8l3yzgJH0F5Ifw9LLt3IyRSeDjE ODIQPWx1I5yGxH/buxRyRQvGOwRt0gmaTruz2/atLMa4Ru/UInGt2Fz/ov2iWLqzxDeW q2KP5x/PmwrMF9FZWLhvf7ysgLBdqQbGRyRVG64U9Xy4yjWm52KSf2358BIXKp8NgLXG sfew==
X-Gm-Message-State: AOAM531ceDsW3uMqADe9QvsvC6gqV8EXQ3Xdr50dhUkHoxi3UZegaksz KwBegzE9uPiw4Cw8DKcgKXwactin4QM9TA==
X-Google-Smtp-Source: ABdhPJzE/ayVD9iPBgbyY4N0llxYFRyLPOY6MQEENUQHUUCnFvrM0FsHjdS2YUcxteljqY8kheORvw==
X-Received: by 2002:a17:902:8b8a:b029:108:7849:dae0 with SMTP id ay10-20020a1709028b8ab02901087849dae0mr24060552plb.36.1624399160348; Tue, 22 Jun 2021 14:59:20 -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 v1sm3100585pjg.19.2021.06.22.14.59.18 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Tue, 22 Jun 2021 14:59:19 -0700 (PDT)
To: adrian@olddog.co.uk, 'Eliot Lear' <lear@lear.ch>, rfced-future@iab.org
References: <7ef10df2-cb21-a95b-b977-286b6d8a8405@lear.ch> <0a8101d76788$0e1af5a0$2a50e0e0$@olddog.co.uk>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Message-ID: <b0339360-3867-2b5b-944a-81231075c569@gmail.com>
Date: Wed, 23 Jun 2021 09:59:16 +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: <0a8101d76788$0e1af5a0$2a50e0e0$@olddog.co.uk>
Content-Type: text/plain; charset="utf-8"
Content-Language: en-US
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfced-future/UfHwbZ4nNwpcNKgYxoMr0be8xuY>
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 21:59:26 -0000

On 23-Jun-21 05:00, Adrian Farrel wrote:
> I don't have a problem with this idea, but I also think it is massively 
missing the point.
> 
> The RFC Series is not owned by the IAB. Formerly it was owned by the RSE 

Well, it all depends on what you mean by "owned". The IETF has a BCP that 
says:

"The IAB must approve the appointment of an organization to
 act as RFC Editor and the general policy followed by the RFC Editor."

so that is going to need changing in the not too distant future.

The copyright in the RFC Series is currently owned by the IETF Trust (to over-simplify things in a way that an IPR lawyer would hate).

> and it will become owned by the RSWG&RSAB.

Not really. They will "own" the policy-formation bit.
 
> Thus, decisions about creating new streams (as many as are wanted) will 
be made by the RSWG&RSAB. So I don't think we need to document it, or if we do, let's do it in a more general way such as...
> 
> "The RSWG with approval of the RSAB may create additional streams as necessary."
> 
> Of course, a slightly tricky question is on which stream *this* document will get published.

Exactly why IMHO we need to create the editorial stream and fix the IAB charter, simultaneously with publishing the new model in the editorial scheme.

   Brian


> 
> Adrian
> 
> -----Original Message-----
> From: Rfced-future <rfced-future-bounces@iab.org> On Behalf Of Eliot Lear
> Sent: 22 June 2021 15:52
> To: rfced-future@iab.org
> Subject: [Rfced-future] Consensus check: Issue 22 – new stream for RFC Editor
> 
> In yesterday's meeting there was general consensus that there should be 

> a new stream, and that the RSE/A should manage it.  The general argument 
> was that there should be no supervisory check performed by the IAB after 
> the RSAB has approved a document.
> 
> Please send any concerns by 6 July.
> 
> Eliot
> 
> 
>