Re: [Rfced-future] New Version Notification for draft-iab-rfcefdp-rfced-model-03.txt

Brian E Carpenter <brian.e.carpenter@gmail.com> Thu, 23 September 2021 02:42 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 0E7753A1854 for <rfced-future@ietfa.amsl.com>; Wed, 22 Sep 2021 19:42:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.1
X-Spam-Level:
X-Spam-Status: No, score=-2.1 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, 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 QpjLRcq4_0xA for <rfced-future@ietfa.amsl.com>; Wed, 22 Sep 2021 19:42:46 -0700 (PDT)
Received: from mail-pf1-x429.google.com (mail-pf1-x429.google.com [IPv6:2607:f8b0:4864:20::429]) (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 455D53A1853 for <rfced-future@iab.org>; Wed, 22 Sep 2021 19:42:46 -0700 (PDT)
Received: by mail-pf1-x429.google.com with SMTP id n23so1552020pfv.4 for <rfced-future@iab.org>; Wed, 22 Sep 2021 19:42:46 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=qqLqbAiWWS/BM+dEVCYVoiln3CkLHxrOGEKVv5DZbz0=; b=L/8JMT2srjYbj4uCBlrfmkQdV3ZpEx1B8JnX1g/+msg//3pWkz5yajwD9n8TZ/X4QR uD4Vulk4GgAnFcVj6qMyRN7YiIREFHWt/CB8XpOzR8VbeC6RgoHsSp8ET838BEvDGUFD K3nr0YgJm0K6SdI++2TVhnuRzU41NmQMftFvzr4w0ukBadKxwuUB+CKjq+LK6ZhJs7GP WiTvi+b8/rEjWB7vvUJXcefaaKjIehr9yRlBPKl3ZkbRC6VbZuL4AZefCPZAU7j/jfIv /8ZvznGNIu7Pf7bfyitYcP8ijDNU0jsILgF8PoU5tNtZ2tFApbEzchLeLQllX23Ek5PI 7ESw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=qqLqbAiWWS/BM+dEVCYVoiln3CkLHxrOGEKVv5DZbz0=; b=Nxo6GOMp4/Ya4aTuKrMzXhSevn2/mVY1BhQRinL2GlANY3v2y7+aVJY26NNu/1xCvV 1t3/xuieDSQYybcPT1XjDSfHHlXWJits+kMhKJtlVC8MJI1rjOFM3SwV51SyO9ADEXz/ c4PJxSh8jG0Tjvs6Fh+R52RCFSnOA+QnBfG7HnLAALEpGVGk5CCxahguLdA4bgrvGM+E tYDwo+bpuzjA3UWeFvT2ri7XohTVknY7L8o72DT6s4rZiaLFoHWtiD2TivdM2fvuRPQZ 7ia+Ay3fK5QjELyHeG0vKvnkRNg89aI0yXvZlXLmrXu7n9AzUzjOMPX1g2PY1nyV8rMo wkbQ==
X-Gm-Message-State: AOAM5319h8U6yf7LmqsCu66VX5pTQgrc2h2x2O9vieeCrrtdYskNNUdN 05Kv9U1vmXMJYK829rLMkUGdXPasbDz7tg==
X-Google-Smtp-Source: ABdhPJw7DfdO46TkT5MqPhFF4LvbWX/L7BVCCT1l83jcVnZlpZg2lR4PDAmUwgc+xGbllAthnDCkLQ==
X-Received: by 2002:a63:4c0e:: with SMTP id z14mr1964764pga.427.1632364965420; Wed, 22 Sep 2021 19:42:45 -0700 (PDT)
Received: from ?IPv6:2406:e003:11aa:d701:80b2:5c79:2266:e431? ([2406:e003:11aa:d701:80b2:5c79:2266:e431]) by smtp.gmail.com with ESMTPSA id t20sm3669317pfe.50.2021.09.22.19.42.43 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Wed, 22 Sep 2021 19:42:44 -0700 (PDT)
To: Colin Perkins <csp@csperkins.org>, Peter Saint-Andre <stpeter@mozilla.com>
Cc: rfced-future@iab.org
References: <163225690759.25175.2693552847212281935@ietfa.amsl.com> <e1a319c5-6069-db17-2e96-ff0a68dc2391@stpeter.im> <CA70A07B-D7F6-4BDF-B057-B47C8060160E@csperkins.org> <be648c37-3953-bd1f-a3a2-4af524d3e364@mozilla.com> <00649D0D-F9F6-42A2-BB65-BB1E8652F44D@csperkins.org>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Message-ID: <c2a2e2f7-9563-e03a-5796-d053193418c3@gmail.com>
Date: Thu, 23 Sep 2021 14:42:39 +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: <00649D0D-F9F6-42A2-BB65-BB1E8652F44D@csperkins.org>
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/64dGMgMSIePoDX2Hf_InOCdIpJ8>
Subject: Re: [Rfced-future] New Version Notification for draft-iab-rfcefdp-rfced-model-03.txt
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: Thu, 23 Sep 2021 02:42:48 -0000

I've read the thread but my comment is only on Colin's original post:

On 23-Sep-21 07:48, Colin Perkins wrote:
>> On 22 Sep 2021, at 20:44, Peter Saint-Andre <stpeter@mozilla.com> wrote:
>> On 9/22/21 1:31 PM, Colin Perkins wrote:
>>> Hi,
>>>
>>> A nit, perhaps, that’s been present since the -02 version but 
that I forgot to mention.
>>>
>>> Section 6 says: "Documents pubished in the Editorial Stream shall have a status of Informational.  The Editorial Stream is not authorized to publish RFCs that are Standards Track or Best Current Practice, since such 
RFCs are reserved to the IETF Stream [RFC8729].” This does not mention Experimental RFCs. Should it? We’ve had "process experiments" in the past… 
>>
>> The concern was that the Editorial Stream not publish RFCs that could be
>> construed as standards. One could imagine that we *might* want to do
>> experiments in the Editorial Stream, but some squinting is involved.
>> Thus personally I'd be fine with mentioning Experimental as well
>> (although, again, that was not the concern).
> 
> 
> Sure – I understand the concern.
> 
> I’d lean towards cannot publish Experimental RFCs on the Editorial Stream, as process experiments seem to be stretching the definition of experimental, but don’t have a strong opinion. I do think we should make a decision though.

We only have one RFC Series, so I don't think the idea of an experiment makes any sense. Suppose somebody proposed an experimental category of RFC's called "Whizzbang" and we published an Experimental RFC describing the 
Whizzbang category. Any Whizzbangs that we published would become permanently archived RFCs with their own DOIs and until the end of civilisation, 
they'd be there, clearly labelled "Whizzbang". If we terminated the "experiment" after 2 years, and even if we concluded that the Whizzbangs should have been called Damp Squibs, they would be Whizzbangs for ever.

So, experiments on an archival series really aren't reversible. Consider that we have 30+ RFCs in the "FYI" category. (See RFC1150 and RFC6360.)

Therefore, I think there is no value in labelling an editorial stream RFC 
"Experimental". Whatever it does has permanent effects.

(This is a very different case from RFC8989, which is an experimental process document, with time-limited effects.)

   Brian