Re: -- basics not working?

Brian E Carpenter <> Fri, 15 October 2021 20:02 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 59F273A0A4A for <>; Fri, 15 Oct 2021 13:02:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Status: No, score=-2.099 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, NICE_REPLY_A=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (2048-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id staSePNH_VB2 for <>; Fri, 15 Oct 2021 13:02:35 -0700 (PDT)
Received: from ( [IPv6:2607:f8b0:4864:20::52c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 7CD6E3A0A39 for <>; Fri, 15 Oct 2021 13:02:35 -0700 (PDT)
Received: by with SMTP id 66so9528494pgc.9 for <>; Fri, 15 Oct 2021 13:02:35 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20210112; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-language:content-transfer-encoding; bh=b28HOGC9+afqhAI54UwyThD3R/HAXqa+/0ZxAEHJud4=; b=hrLP+5PRF2qd9FC/V0RH0aWTBVUiJ5FoE6xmr1zUq9mfo/zxrC8+H44Z37d1qro0qG MwLalvqR+UNBLOlpD3BdxCbBDzYdVVUx2olg9qD/PXVZcGbeiewNP/wUhG1hSxfAuy3K 1N8+PAWzpZD6Mv0ahe+ZQonOf4c9aZlLC//2RsTxjoFD6TngvcaRGG+YS+9TQjIHL3wO ieBh0QYTrrvziQQzMKBHOdQvfzu5sJChZy0coN1CN0I9lRQTT3T+k+9mOYXCVM1Mxy5f 1qWfG/VhDcW0zWDXycOdnXacSPUXxzddSpYDHuRNxt0zIvT4K5n6Z8QVL4XtLE3cxR1y 3LpA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20210112; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=b28HOGC9+afqhAI54UwyThD3R/HAXqa+/0ZxAEHJud4=; b=AofqWNX6uz+RQyiyw+TviPqQQrAqApfiqcX4OlewGzcIkLNwQ3hTkDZOshYCC726xl ZJzryzKxnsON9x6ooK+6MyUgEIzULFeyCAcGEPMJFD75x8/FHYHeMEW5G6uUmGEJJXPB rJP4EMMMk628+lfCsN9sLM05mpGrs4kDtumloCv31lUoUkNbG/9GRtbYn4hKte0aD0bZ jEYSyPlcM4dHrYECCaOuKRzsshZ6SjCBHmtjKXi0THX/CUkfzyYAG17BU227sped81Yy LSfFQNTbGNPiyN6BOS6J+9dWc14ARmeOSsCmhWQ18i1Gyqx6M6F1JrCqFZ64Co18lEQP x2Lw==
X-Gm-Message-State: AOAM532n4EBfxiam4jyan0XiupHNYBV1OUseIIv5CnsT06NTUS83sQtH nxgh6d7K9wtA268CPyXQx/2Xk0BqXac=
X-Google-Smtp-Source: ABdhPJwU8LkNnDHe5/fjm+jMszF8G+jRb5ofuH6U4WTmYwT+NWv4VuSTSu3ebw1SStTMhF+ZTG/Kcw==
X-Received: by 2002:a05:6a00:1248:b0:44c:84cd:f795 with SMTP id u8-20020a056a00124800b0044c84cdf795mr13361458pfi.79.1634328154458; Fri, 15 Oct 2021 13:02:34 -0700 (PDT)
Received: from ?IPv6:2406:e003:102d:e801:db7:d041:a2d:ce65? ([2406:e003:102d:e801:db7:d041:a2d:ce65]) by with ESMTPSA id kk18sm5927293pjb.8.2021. (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Fri, 15 Oct 2021 13:02:33 -0700 (PDT)
Subject: Re: -- basics not working?
To: Havard Eidnes <>,
References: <>
From: Brian E Carpenter <>
Message-ID: <>
Date: Sat, 16 Oct 2021 09:02:29 +1300
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.10.0
MIME-Version: 1.0
In-Reply-To: <>
Content-Type: text/plain; charset="utf-8"
Content-Language: en-US
Content-Transfer-Encoding: quoted-printable
Archived-At: <>
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF-Discussion <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Fri, 15 Oct 2021 20:02:41 -0000

Hi Havard,

I guess you missed this:

It seems the IETF 111 deadline was missed, but I'm sure Robert will update us on progress.

   Brian Carpenter

On 16-Oct-21 08:46, Havard Eidnes wrote:
> Hi,
> is it just me who finds the basic functionality of
> 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
> which redirects to
> which is once again a "404 Not Found" page.
> The same goes for the "RFCs" link, which goes to
> which redirects to
> 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,
> 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