Re: [rfc-i] Clusters in the RFC Editor Queue

RFC Editor <rfc-editor@rfc-editor.org> Wed, 08 July 2020 17:56 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 440A33A0403; Wed, 8 Jul 2020 10:56:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.9
X-Spam-Level:
X-Spam-Status: No, score=-2.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MAILING_LIST_MULTI=-1, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 Ra2mybFlvz0n; Wed, 8 Jul 2020 10:56:29 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1EAB83A040F; Wed, 8 Jul 2020 10:56:29 -0700 (PDT)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id 00568F40742; Wed, 8 Jul 2020 10:56:01 -0700 (PDT)
X-Original-To: rfc-interest@rfc-editor.org
Delivered-To: rfc-interest@rfc-editor.org
Received: by rfc-editor.org (Postfix, from userid 6000) id E6CDDF4073E; Wed, 8 Jul 2020 10:55:59 -0700 (PDT)
Date: Wed, 8 Jul 2020 10:55:59 -0700
From: RFC Editor <rfc-editor@rfc-editor.org>
To: S Moonesamy <sm+ietf@elandsys.com>
Message-ID: <20200708175559.GC8863@rfc-editor.org>
References: <6.2.5.6.2.20200629105013.10434f88@elandnews.com>
MIME-Version: 1.0
Content-Disposition: inline
In-Reply-To: <6.2.5.6.2.20200629105013.10434f88@elandnews.com>
User-Agent: Mutt/1.10.1 (2018-07-13)
Subject: Re: [rfc-i] Clusters in the RFC Editor Queue
X-BeenThere: rfc-interest@rfc-editor.org
X-Mailman-Version: 2.1.29
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>
Cc: rfc-interest@rfc-editor.org, rse@rfc-editor.org, RFC Editor <rfc-editor@rfc-editor.org>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: rfc-interest-bounces@rfc-editor.org
Sender: "rfc-interest" <rfc-interest-bounces@rfc-editor.org>

Hi SM,

Apologies for the delayed reply.  Thank you for letting us know. This
redirect is now in place: 
https://www.rfc-editor.org/cluster_def.html
resolves to
https://www.rfc-editor.org/about/clusters/

(This should've been one of the many redirects that were put in place
after the website transition in 2015.)

RFC Editor/sg


On Mon, Jun 29, 2020 at 11:00:10AM -0700, S Moonesamy wrote:
> Hello,
> 
> I was reading RFC 7322 and I came across this:
> 
>   * Connected to www.rfc-editor.org (2001:1900:3001:11::31) port 80 (#0)
>   > HEAD /cluster_def.html HTTP/1.1
>   > Host: www.rfc-editor.org
>   > User-Agent: [removed]
>   > Accept: */*
>   >
>   * Mark bundle as not supporting multiuse
>   < HTTP/1.1 404 Not Found
>   HTTP/1.1 404 Not Found
> 
> Section 4.8.6.1 of the RFC states that: "The use of URIs in references is
> acceptable, as long as the URI is the most stable (i.e., unlikely to change
> and expected to be continuously available) and direct reference possible."
> Is that accurate?
> 
> Regards,
> S. Moonesamy
_______________________________________________
rfc-interest mailing list
rfc-interest@rfc-editor.org
https://www.rfc-editor.org/mailman/listinfo/rfc-interest