IETF Logo Mail Archive

Re: Call for Community Feedback: Retiring IETF FTP Service

Kathleen Moriarty <kathleen.moriarty.ietf@gmail.com> Thu, 03 December 2020 16:45 UTC

Return-Path: <kathleen.moriarty.ietf@gmail.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 90A003A03F3 for <ietf@ietfa.amsl.com>; Thu, 3 Dec 2020 08:45:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level:
X-Spam-Status: No, score=-2.097 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, HTML_MESSAGE=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 yNz6baEg0T6X for <ietf@ietfa.amsl.com>; Thu, 3 Dec 2020 08:45:01 -0800 (PST)
Received: from mail-vs1-xe29.google.com (mail-vs1-xe29.google.com [IPv6:2607:f8b0:4864:20::e29]) (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 96BAD3A03F1 for <ietf@ietf.org>; Thu, 3 Dec 2020 08:45:01 -0800 (PST)
Received: by mail-vs1-xe29.google.com with SMTP id q5so1619904vsg.0 for <ietf@ietf.org>; Thu, 03 Dec 2020 08:45:01 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=RgBa2ZO0H9ZSqdkUqOm6ITK2jF8F05l+YBuhnI/WIEQ=; b=aEr/12dsg+ygSjCiwQFgTN34RZWq1aXGGJjfHlSeWa9n35uDET2HiYPIXo/vnG7sB8 1lNve+Rghsyh3A8UwIgRxSvaV0vAmy1+nRX1KhcM1VuNzOrTjaq3NOwBqWlMiaLPTo/u ZvfwgLGui1KT0dSxdgCLaM+fafsd53FG/CiJVLrDhMkRbZvmIR0vh31+QvzJp0KiE+K3 1YMiR+rUANJ70TtoQ/jxabwItFlRVCNi9SNcJvRRf/E6qDPNxDiyMl0vpHXFUhLA9K7T gGNAv352wnfCZqRWvu0POa9i1Jp3p8lxUdjr96W3Giun7NuNRE5CEAFmwDx76e4UuuUt 7QSA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=RgBa2ZO0H9ZSqdkUqOm6ITK2jF8F05l+YBuhnI/WIEQ=; b=rlz2vHzKsU9z4mroCYugBH6+3sOmwLxj6oRHqnZhc2ZIULYc43Ab4YWgaASfF7Tw0b NJz4Yi+5yNLXJZmKdPQDXTfuRtI7h7v/ToKZzXVpRH6scLkCpCZVeZwrxmIq2XUwU1rz 6CSpdgLDId8+DKsZ7NvlDGVhwdptQHiIhFXIqxXZ24neuFB4iZkqCI5Tne3mde0GbaDm H4FQ3CK+FqRe9gahfcMTuHXvrH22gc4YVQMb3qRBhlgQIvDVXrZru8G4Zad84j9dd8Io O0lw/tLPLOKyXRm8ZHg7h2X1ruQw45KpsIACuhD+bhErYHo/Dp5+4xS7oLQqkbUdGH+J PGQA==
X-Gm-Message-State: AOAM531Dr8VlimitAM7Fj15Cc8baC1HIOwv5ipfi5+aHSyPyPMsgg4n4 9PMNZbPSsFSidff6nh4uL5g4U4YKLUF5ovi0mqCnwTPk
X-Google-Smtp-Source: ABdhPJwcXk81l8QZvrgAElXb58I7RO439WQAHriMP2cwCkiSYNnkV3BryMRIJ0PlIpvp8gfqIRGAOu+q55mm+Oh1VIc=
X-Received: by 2002:a67:d39b:: with SMTP id b27mr3196171vsj.22.1607013900418; Thu, 03 Dec 2020 08:45:00 -0800 (PST)
MIME-Version: 1.0
References: <af6ab231024c478bbd28bbec0f9c69c9@cert.org> <0D41F3FD-BA1F-4716-A165-4FE7529431A9@vigilsec.com> <138B3221-5A32-4DB0-AA1C-1D8D09D93B89@cert.org>
In-Reply-To: <138B3221-5A32-4DB0-AA1C-1D8D09D93B89@cert.org>
From: Kathleen Moriarty <kathleen.moriarty.ietf@gmail.com>
Date: Thu, 03 Dec 2020 11:44:23 -0500
Message-ID: <CAHbuEH6t=AUtNGa_Xdq7ATeZ5qH1Ug3BdrcBSCUcFUiU+dm5Rg@mail.gmail.com>
Subject: Re: Call for Community Feedback: Retiring IETF FTP Service
To: "ietf@ietf.org" <ietf@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000af040a05b59214c2"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/X0tg_lTmoPN50GS0hjDOEt-hcz8>
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, 03 Dec 2020 16:45:04 -0000

+1. It is time to move on and adapt.  I agree with Russ on the increased
security offered from HTTPS and the practicality points from both Russ and
Chris.

Best regards,
Kathleen

On Fri, Nov 20, 2020 at 11:39 AM Chris Inacio <inacio@cert.org> wrote:

> +1.
>
> FTP was great in its day.  I also really liked gopher.  Maybe more than
> the current web.  But let’s be real - that’s just not practical at this
> point, IMHO.  The Internet (at large) has moved on, possible even enabled
> by IETF, we should keep to that reality.
>
> Chris
>
>
> > On Nov 16, 2020, at 5:43 AM, Russ Housley <housley@vigilsec.com> wrote:
> >
> > I support turning off the FTP service at ietf.org. The FTP daemon
> places frustrating constraints on the file system structure.  HTTPS offers
> much greater security, and it does not impose constraints on the file
> system structure.
> >
> > Russ
> >
> >> On Nov 9, 2020, at 9:23 PM, Roman Danyliw <rdd@cert.org> wrote:
> >>
> >> Hi!
> >>
> >> The Internet Engineering Steering Group (IESG) is seeking community
> input on retiring the IETF FTP service (ftp://ftp.ietf.org,
> ftp://ops.ietf.org, ftp://ietf.org).  A review of this service has found
> that FTP appears to serve a very small community and HTTP has become the
> access mechanism of choice.  Given this shift in community usage, reducing
> the operational complexity of the overall IETF infrastructure seems to
> outweigh the very limited community served with FTP.
> >>
> >> In reviewing the additional impacts of such a service retirement, the
> dependencies on FTP have been assessed.  Additionally, it has been
> confirmed that all information currently reachable through FTP will
> continue to be available through other services (HTTP, RSYNC, IMAP).
> >>
> >> In consultation with the Tools team (Robert, Glen, Henrik, Russ, and
> Alexey), Communications team (Greg), affected SDO liaisons, IAB Chair, and
> LLC ED, a proposed retirement plan was developed and is available at:
> >>
> >> https://www.ietf.org/media/documents/Retiring_IETF_FTP_Service.pdf
> >>
> >> The IESG appreciates any input from the community on this proposal and
> will consider all input received by December 4, 2020 (to account for the
> upcoming IETF 109 and holidays).
> >>
> >> Regards,
> >> Roman
> >> (as the IESG Tools Liaison)
> >>
> >
>
>

-- 

Best regards,
Kathleen

v2.23.0 | Report a Bug | By Email