Hi Havard, I guess you missed this: https://mailarchive.ietf.org/arch/msg/ietf/0n-6EXEmkTp3Uv_vj-5Vnm3o0bo It seems the IETF 111 deadline was missed, but I'm sure Robert will update us on progress. Regards Brian Carpenter On 16-Oct-21 08:46, Havard Eidnes wrote: > Hi, > > is it just me who finds the basic functionality of > https://tools.ietf.org/ has declined significantly over about the > last half year or so? > > My use of the web site is fairly basic: > > - look up RFCs by number (I'm sufficiently environmentally > damaged to remember some of them by number) > - look up internet drafts based on partial draft name > - look up the RFC Index (for when the environment damage > mentioned above doesn't work...) > - look up the Internet Drafts index > > I used to be able to enter the RFC number (just the number, not > having to prefix it with "rfc") in the "Doc fetch:" box. This > stopped working a few months ago, instead I now get a "404 Not > Found" page. On a previous exchange when I said that this > stopped working, I was told "you need to prefix with 'rfc'". Of > course that also doesn't work anymore, if I try to fetch rfc1034, > I also get a "404 Not Found" page. > > The "hover text" for the "Doc fetch:" box says "Enter document > number or name, rfc, bcp, draft-..., etc., and hit return". I > think that's what I'm doing, and ... it's not working for looking > up Internet Drafts either, with or without the version number > (which should not be necessary). If I paste in > "draft-ietf-dnsop-svcb-https" and I get back the same "404 Not > Found" web page. Of course just searching for "svcb" is met with > the same fate, even though there's some probability that there > aren't all that many drafts with that string in the draft name. > > The "Documents" link just above the "Doc fetch:" box leads to > > https://tools.ietf.org/html/ > which redirects to > https://datatracker.ietf.org/doc/html/ > > which is once again a "404 Not Found" page. > > The same goes for the "RFCs" link, which goes to > > https://tools.ietf.org/rfc/index > which redirects to > https://www.rfc-editor.org/rfc/index > > which results in an "Object not found", another way to emit the > 404 "No such web page" error. > > Yes, I have tried to report this to webmaster@xxxxxxxxxxxxxx, > listed as the contact at the end of the page, but my latest query > has now gone unanswered for a couple of days. > > How did we get here? Are the toolsmiths so busy doing other > fancy stuff that the basics are allowed to languish on their own, > unattended by the wayside? > > Isn't this supposed to work? > > Obviously, it's not, and I don't think it looks good. > > Regards, > > - Håvard >
