Updating References to the IETF FTP Service
draft-danyliw-replace-ftp-pointers-06

[Ballot comment]
Section 3.4

  The MIB in Section 3 of [RFC2954] is updated as follows:

Can we really update a MIB without changing its LAST-UPDATED stanza?
(Likewise for the other similar MIB updates.)
Maybe we should just say we update the text and not say anything about
the fact that it appears in a MIB...

Section 3.11

  OLD:

  [9] Ogier, R., Message in IETF email archive for MANET,
  ftp://ftp.ietf.org/ietf-mail-archive/manet/2002-03.mail, March 2002.

  NEW:

  [9] Ogier, R., Message in IETF email archive for MANET,
  https://www.ietf.org/ietf-ftp/ietf-mail-archive/manet/2002-02.mail,
  March 2002.

Looks like a copy/paste issue about 2002-03 vs 2002-02.

RFC 5428

  The MIB in Section 5 of [RFC5428] is updated as follows:

I think the MIB is in Section 6, not 5.

NITS

Section 3.12

  OLD:

  [LEACH] Leach, P., email to IETF Kerberos working group mailing list,
  5 May 2003, ftp://ftp.ietf.org/ietf-mail- archive/krb-
  wg/2003-05.mail.

The formatting and line break don't seem to have been preserved from the
original.

Section 3.16

  OLD:

  [DAI] Dai, W., "An attack against SSH2 protocol", Email to the SECSH
  Working Group ietf-ssh@netbsd.org ftp:// ftp.ietf.org/ietf-mail-
  archive/secsh/2002- 02.mail, Feb 2002.

(ditto)

Section 4

  more secure way.  For example, HTTPS provides an encrypted channel
  that includes protections such as verifying the server's identity per
  the certificate verification behavior of the client, and integrity
  and confidentiality commensurate with the negotiated TLS protocol
  version and ciphersuite.

s/commensurate/protection commensurate/

To address the 3 comments received during the IETF Last Call:

- Russ H about "IAB" rather than "IAB stream editor"

- Brian C about updated RFC 2026 as well

- Tom P about using RFC 8792 for the updated URL.

(Via drafts-lastcall@iana.org): IESG/Authors/WG Chairs:

The IANA Functions Operator has reviewed draft-danyliw-replace-ftp-pointers-03, which is currently in Last Call, and has the following comments:

We understand that this document doesn't require any registry actions.

While it's often helpful for a document's IANA Considerations section to remain in place upon publication even if there are no actions, if the authors strongly prefer to remove it, we do not object.

If this assessment is not accurate, please respond as soon as possible.

Thank you,

Sabrina Tanamal
Lead IANA Services Specialist

The following Last Call announcement was sent out (ends 2021-09-27):

From: The IESG
To: IETF-Announce
CC: draft-danyliw-replace-ftp-pointers@ietf.org, evyncke@cisco.com
Reply-To: last-call@ietf.org
Sender:
Subject: Last Call:  (Updating References to the IETF FTP Service) to Proposed Standard


The IESG has received a request from an individual submitter to consider the
following document: - 'Updating References to the IETF FTP Service'
  as Proposed Standard

The IESG plans to make a decision in the next few weeks, and solicits final
comments on this action. Please send substantive comments to the
last-call@ietf.org mailing lists by 2021-09-27. Exceptionally, comments may
be sent to iesg@ietf.org instead. In either case, please retain the beginning
of the Subject line to allow automated sorting.

Abstract


  The IETF FTP service running at ftp.ietf.org, ops.ietf.org and
  ietf.org will be retired.  A number of published RFCs in the IETF and
  IAB streams include URIs that reference this FTP service.  To ensure
  that the materials referenced using the IETF FTP service can still be
  found, this document updates the FTP-based references in these
  affected documents with HTTPS URIs.




The file can be obtained via
https://datatracker.ietf.org/doc/draft-danyliw-replace-ftp-pointers/



No IPR declarations have been submitted directly on this I-D.