IETF Logo Mail Archive

Re: TLS access Re: Call for Community Feedback: Retiring IETF FTP Service

ned+ietf@mauve.mrochek.com Thu, 19 November 2020 20:11 UTC

Return-Path: <ned+ietf@mauve.mrochek.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 989C03A1128 for <ietf@ietfa.amsl.com>; Thu, 19 Nov 2020 12:11:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 Ar65MRsmsf0v for <ietf@ietfa.amsl.com>; Thu, 19 Nov 2020 12:11:22 -0800 (PST)
Received: from mauve.mrochek.com (mauve.mrochek.com [98.153.82.211]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9B2563A1120 for <ietf@ietf.org>; Thu, 19 Nov 2020 12:11:22 -0800 (PST)
Received: from dkim-sign.mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01RS71724VIO00COC9@mauve.mrochek.com> for ietf@ietf.org; Thu, 19 Nov 2020 12:06:19 -0800 (PST)
MIME-version: 1.0
Content-transfer-encoding: 7bit
Content-type: TEXT/PLAIN; CHARSET="US-ASCII"
Received: from mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01RS4XGHZZF4005PTU@mauve.mrochek.com> (original mail from NED@mauve.mrochek.com) for ietf@ietf.org; Thu, 19 Nov 2020 12:06:15 -0800 (PST)
From: ned+ietf@mauve.mrochek.com
Cc: Roman Danyliw <rdd@cert.org>, "ietf@ietf.org" <ietf@ietf.org>
Message-id: <01RS71703R2O005PTU@mauve.mrochek.com>
Date: Thu, 19 Nov 2020 11:58:22 -0800
Subject: Re: TLS access Re: Call for Community Feedback: Retiring IETF FTP Service
In-reply-to: "Your message dated Thu, 19 Nov 2020 19:40:18 +0000" <1049FA76-DCB8-4735-8947-6D5CC0144C9F@akamai.com>
References: <af6ab231024c478bbd28bbec0f9c69c9@cert.org> <0D41F3FD-BA1F-4716-A165-4FE7529431A9@vigilsec.com> <D26DCBB6-3997-4A73-BB46-867B4FD79BD2@eggert.org> <27b80ed2-76fb-aee7-f22d-de56019e9aa9@nostrum.com> <a8bdd67a-13ea-4433-aa38-9cfd48ea28da@network-heretics.com> <0e875497-9986-a0d9-8354-3eac26b7f882@nostrum.com> <a02e15f2-34fb-4124-7ba0-c0ee0070b39f@network-heretics.com> <6a29096e-c76e-9bde-388c-bf411b235346@nostrum.com> <6ff3c8a8-57c9-a278-51ce-ce24fd2dfc0e@network-heretics.com> <01RS3W7DNPHA005PTU@mauve.mrochek.com> <7057e29825514008a06b749cb5c476f6@cert.org> <01RS3Y1AZ65A0085YQ@mauve.mrochek.com> <365930470c214fbd982da633c69b3b67@cert.org> <5172d442-6bb0-0e11-81fb-3da6e828166e@network-heretics.com> <c7afe761c0264c1daa533cec1895f1af@cert.org> <2088e835-86ef-1896-d307-fc4433ec3b65@network-heretics.com> <37e993ad382c423b90e11b4ca06a307e@cert.org> <f8e0951c-d655-31e4-63bc-357b1085b358@network-heretics.com> <5FB667B1.8000702@btconnect.com> <ee4a65123d7a4011be9b04b3408d1bea@cert.org> <1049FA76-DCB8-4735-8947-6D5CC0144C9F@akamai.com>
To: "Salz, Rich" <rsalz=40akamai.com@dmarc.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/Wz8WJjUpnfYSSwiOOBDwtaauLtk>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 19 Nov 2020 20:11:24 -0000

> >  FWIW, datatracker.ietf and www.ietf are the canonical repositories for the
> > I-Ds and RFCs in the IETF.

> Separate question: we were told for the newcomers slides to use
> rfc-editor.org for official RFC references.  How do we resolve that difference
> of views?

FWIW, I think that's a good choice for someone not participating in the IETF,
but a suboptimal one for someone who is, or will be.

The nice thing about datatracker.ietf.org is how easy it is to get to related
resources - stuff IETFers need to see, but non-IETFers generally do not.

I do find it odd that DuckDuckGo seems to prefer tools.ietf.org (fine, I
guess), and datatracker.ietf.org (?) and even internetsociety.org (??) to
rfc-editor.org, but it's not like we have any control over that.

				Ned

v2.23.0 | Report a Bug | By Email