Re: [rfc-i] Moving my Unknown RFCs to Historic
Brian E Carpenter <brian.e.carpenter@gmail.com> Fri, 21 January 2022 23:02 UTC
Return-Path: <rfc-interest-bounces@rfc-editor.org>
X-Original-To: ietfarch-rfc-interest-archive@ietfa.amsl.com
Delivered-To: ietfarch-rfc-interest-archive@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7B7783A15CB; Fri, 21 Jan 2022 15:02:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.911
X-Spam-Level:
X-Spam-Status: No, score=-2.911 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, FREEMAIL_FORGED_FROMDOMAIN=0.25, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.25, MAILING_LIST_MULTI=-1, NICE_REPLY_A=-0.714, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (2048-bit key) reason="fail (message has been altered)" 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 GbwSH2K2a3cv; Fri, 21 Jan 2022 15:02:16 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1900:3001:11::31]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 986403A15D8; Fri, 21 Jan 2022 15:02:04 -0800 (PST)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id 4A77E10D72; Fri, 21 Jan 2022 15:02:03 -0800 (PST)
X-Original-To: rfc-interest@rfc-editor.org
Delivered-To: rfc-interest@rfc-editor.org
Received: from localhost (localhost [127.0.0.1]) by rfc-editor.org (Postfix) with ESMTP id 57D7110D72 for <rfc-interest@rfc-editor.org>; Fri, 21 Jan 2022 15:02:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at rfc-editor.org
Authentication-Results: rfcpa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from rfc-editor.org ([127.0.0.1]) by localhost (rfcpa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id D1J3HLosSQ6N for <rfc-interest@rfc-editor.org>; Fri, 21 Jan 2022 15:02:00 -0800 (PST)
Received: from mail-pj1-x102c.google.com (mail-pj1-x102c.google.com [IPv6:2607:f8b0:4864:20::102c]) by rfc-editor.org (Postfix) with ESMTPS id AA2C910D62 for <rfc-interest@rfc-editor.org>; Fri, 21 Jan 2022 15:02:00 -0800 (PST)
Received: by mail-pj1-x102c.google.com with SMTP id n16-20020a17090a091000b001b46196d572so10272554pjn.5 for <rfc-interest@rfc-editor.org>; Fri, 21 Jan 2022 15:02:00 -0800 (PST)
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=ejyOwrbYoCgZvFswfwKDau/Q1q6pABJrPNvdO1UTq3c=; b=fUU4L3yBDAGIcYr7kpj8iGFwiykjzrgWkC+WCW9JLoTdcKiuUSf4UufKYJ/mjhKYpS JHJT8X8wMvGp8qrRnhZv9gJ+0vYmWSjthInn7bveFPyJG2JGipFMCpjlYDJ/rUMelJQJ KupMS4XKJe3puh9tDOv4v2RyPe1UMoMp64Ut9/bhSbBhcFQ0KaaFrAwpZHYXROaOka2X 5B6bQT9bpH7U39+opYMtl/OkHS28bMzNlHJ3F52P9TkGWWNgn7nGeKNmg7FKnL0LxzO5 rrXN5rlCflMjjpLh8Tf2Ue3kh13Hv/mlrfdQACQPbEOJof+MEIKe348SUCH3YqHCNsCy pN/w==
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=ejyOwrbYoCgZvFswfwKDau/Q1q6pABJrPNvdO1UTq3c=; b=pimFkICSnlHTYqDfwVQFLux9nKV3K2OKrw+IfdG52lW87IDEGdsREpbIJvt95waYBE FAsl9eLXahVJ9jwVnLxm5X8VYLgcUqApOpVxWq9Yrr5or6ri38bDUIpQ0+9vfhfzQpTh HpQ7dP11iI3Z8I21tAgPdXiyzaorvQPZT/UzdRf7go3Tm9OAmhmbfD7+lFOfHjAp50rw 7Ae3FtzbElYYwYxSGIz0WACiFCgZOGw66oVvbvRpnveOVt+Cq6Y9li3WbGSHvlYtwgVi kKlqAeTn3dt9JJPhO1xELG1hLcIppqTcr6Ew6UtmUZMTw3HXfvgdpt6kjxgyH5q/tZYv xJHA==
X-Gm-Message-State: AOAM531kq+WAyPiNq5mbUvap+gs5aX/+wlLOpwgQLvjkj2bKog+DLvE6 s53Ga+irMzKoHPs7n9PUMXrYOPpcn1wguw==
X-Google-Smtp-Source: ABdhPJwDp3/Wy782+LVRpHQZw1i7vXCyPeF+WPMGzryyoYNE9nYOkLU8gZGWniup5rih7UYmOCrgrQ==
X-Received: by 2002:a17:90a:bb0e:: with SMTP id u14mr2804151pjr.149.1642806119933; Fri, 21 Jan 2022 15:01:59 -0800 (PST)
Received: from ?IPv6:2406:e003:1071:1701:80b2:5c79:2266:e431? ([2406:e003:1071:1701:80b2:5c79:2266:e431]) by smtp.gmail.com with ESMTPSA id g19sm8079725pfv.11.2022.01.21.15.01.57 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Fri, 21 Jan 2022 15:01:59 -0800 (PST)
To: "Andrew G. Malis" <agmalis@gmail.com>
Cc: RFC Interest <rfc-interest@rfc-editor.org>
References: <CAA=duU0FeO+wo3nMWa_car14ncujP7n7xW_onoc2ja6=ok2XfQ@mail.gmail.com> <7c77860d-7c79-37ab-e39f-032ad4f6b70c@gmail.com> <CAA=duU02kOZdnyFxDXUjqAVxk4J=60Tn7mu1iyRbxufog4oGNA@mail.gmail.com>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Message-ID: <dab5ae99-defe-c61a-ba7c-83ce4c8f071a@gmail.com>
Date: Sat, 22 Jan 2022 12:01:54 +1300
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: <CAA=duU02kOZdnyFxDXUjqAVxk4J=60Tn7mu1iyRbxufog4oGNA@mail.gmail.com>
Content-Language: en-US
Subject: Re: [rfc-i] Moving my Unknown RFCs to Historic
X-BeenThere: rfc-interest@rfc-editor.org
X-Mailman-Version: 2.1.34
Precedence: list
List-Id: "A list for discussion of the RFC series and RFC Editor functions." <rfc-interest.rfc-editor.org>
List-Unsubscribe: <https://www.rfc-editor.org/mailman/options/rfc-interest>, <mailto:rfc-interest-request@rfc-editor.org?subject=unsubscribe>
List-Archive: <http://www.rfc-editor.org/pipermail/rfc-interest/>
List-Post: <mailto:rfc-interest@rfc-editor.org>
List-Help: <mailto:rfc-interest-request@rfc-editor.org?subject=help>
List-Subscribe: <https://www.rfc-editor.org/mailman/listinfo/rfc-interest>, <mailto:rfc-interest-request@rfc-editor.org?subject=subscribe>
Content-Transfer-Encoding: base64
Content-Type: text/plain; charset="utf-8"; Format="flowed"
Errors-To: rfc-interest-bounces@rfc-editor.org
Sender: rfc-interest <rfc-interest-bounces@rfc-editor.org>
Hi Andy,
They would presumably offer advice, but policy formulation would come from the RSWG.
Regards
Brian
On 22-Jan-22 10:44, Andrew G. Malis wrote:
> Brian,
>
> If the current proposal is adopted, then it looks like this would be the RSCE's responsibility?
>
> Cheers,
> Andy
>
>
> On Fri, Jan 21, 2022 at 3:18 PM Brian E Carpenter <brian.e.carpenter@gmail.com <mailto:brian.e.carpenter@gmail.com>> wrote:
>
> Abdy,
>
> On 22-Jan-22 03:54, Andrew G. Malis wrote:
> > All this talk about RFC 911 got me to check my old RFCs. I have six pre-IETF ARPANET-related RFCs that are currently Unknown and should be Historic, 802, 851, 852, 878, 979, and 1005. What would people suggest the best way to get this done? Should we wait until we have a new RFC Editor in place?
>
> My suggestion is to wait until we have the new RFC Editor *model* in place, at which point the venue for this discussion will become clear.
>
> To avoid being told that I am being obscure:
> https://www.ietf.org/archive/id/draft-iab-rfcefdp-rfced-model-10.html <https://www.ietf.org/archive/id/draft-iab-rfcefdp-rfced-model-10.html>
>
> Brian
>
_______________________________________________
rfc-interest mailing list
rfc-interest@rfc-editor.org
https://www.rfc-editor.org/mailman/listinfo/rfc-interest
- [rfc-i] Moving my Unknown RFCs to Historic Andrew G. Malis
- Re: [rfc-i] Moving my Unknown RFCs to Historic Brian E Carpenter
- Re: [rfc-i] Moving my Unknown RFCs to Historic Andrew G. Malis
- Re: [rfc-i] Moving my Unknown RFCs to Historic Brian E Carpenter