Hi Tom! Thanks for reviewing the document. More inline ... > -----Original Message----- > From: tom petch <daedulus@xxxxxxxxxxxxx> > Sent: Monday, September 6, 2021 4:26 AM > To: last-call@xxxxxxxx > Cc: draft-danyliw-replace-ftp-pointers@xxxxxxxx > Subject: Re: Last Call: <draft-danyliw-replace-ftp-pointers-03.txt> (Updating > References to the IETF FTP Service) to Proposed Standard > > On 30/08/2021 15:22, The IESG wrote: > > > > The IESG has received a request from an individual submitter to > > consider the following document: - 'Updating References to the IETF FTP > Service' > > <draft-danyliw-replace-ftp-pointers-03.txt> 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@xxxxxxxx mailing lists by 2021-09-27. Exceptionally, > > comments may be sent to iesg@xxxxxxxx instead. In either case, please > > retain the beginning of the Subject line to allow automated sorting. > > If I cut and paste the https: URI intoa browser, some fail. This is to be expected > as some have been folded over two lines to meet the requirements of > publication as an RFC. > > This is not a new problem. Indeed, there is a technical solution in the shape of > RFC8792 which prescribes the use of backslash to denote where such folding > has occurred. This technique is not as widely known as it might be - I have seen > comments on directorate lists on the lines of 'What is this?' - but it does offer a > solution. I leave it up to the author as to whether or not this approach would > be an improvement here. Good point. In the general case, I would have said the text definitely should rely on the convention in RFC8792. However, looking at these different cases of wrapped URLs, it's less clear to me how to handle it with the inline or OLD/NEW style URL references. My thinking is to defer to whatever the RFC Editor suggests is the right approach. I've also made a few edits to ensure they don't break across lines. Roman > Tom Petch > > > > 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. > > > > > > > > > > > > _______________________________________________ > > IETF-Announce mailing list > > IETF-Announce@xxxxxxxx > > https://www.ietf.org/mailman/listinfo/ietf-announce > > . > > -- last-call mailing list last-call@xxxxxxxx https://www.ietf.org/mailman/listinfo/last-call
