On 8/23/22 6:46 PM, Brian E Carpenter wrote:
Robert,
I raised another version of this as [rt5.ietf.org #7260] two months ago.
Thanks for the pointer.
I don't think there's any choice about it. This needs to be fixed,
since keeping records of meetings is a fundamental obligation
(section 8 of RFC2026). As far as I know, there are now precisely
zero supported browsers that handle the ftp: schema. So even where
the ftp: URLs still point to content, you can't fetch it in any
convenient way.
Does the transformation ftp://ftp.ietf.org/<resource>
to https://www.ietf.org/ietf-ftp/<resource> work globally?
Yes.
I'm asking the secretariat to look into a manual transformation for the
older proceedings.
RjS
Regards
Brian Carpenter
On 24-Aug-22 02:11, Robert Sparks wrote:
Fwiw, the content itself is not lost - just the ftp access mechanism.
Per the document for how to find things (section 3.26 of RFC9141), this
content can be found at places like
https://www.ietf.org/ietf-ftp/ietf-online-proceedings/95dec/directorsmessage.txt.
It would be reasonable, in my opinion, to ask for a project that updated
the links in old proceedings.
That said - this particular breakage was not caused by turning off the
ftp service for the ftp service is not yet shut down. Rather it was
likely broken in an earlier file organization effort.
RjS
On 8/22/22 11:34 PM, Mike StJohns wrote:
https://www.ietf.org/proceedings/34/
I was trying to remember the hotel we were at for the first IETF in
Dallas. Similar to current events, the Trinity river was out of its
banks and was within an inch or so of level from flooding the
electrical pad for the hotel. I thought perhaps the old proceedings
might have some details. Imagine my surprise when none of the links
worked.
I haven’t looked at other old proceedings, but my guess is that they
may be in no better shape.
Mike
Sent from my iPad
.
