Re: The end of the Internet as we now it

Toerless Eckert <tte@cs.fau.de> Thu, 15 October 2020 09:47 UTC

Return-Path: <eckert@i4.informatik.uni-erlangen.de>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5AD913A13B2 for <ietf@ietfa.amsl.com>; Thu, 15 Oct 2020 02:47:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.87
X-Spam-Level:
X-Spam-Status: No, score=-0.87 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.249, SPF_HELO_NONE=0.001, SPF_NEUTRAL=0.779, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kD9vqgvQDfIo for <ietf@ietfa.amsl.com>; Thu, 15 Oct 2020 02:47:18 -0700 (PDT)
Received: from faui40.informatik.uni-erlangen.de (faui40.informatik.uni-erlangen.de [IPv6:2001:638:a000:4134::ffff:40]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4DE9B3A13AF for <ietf@ietf.org>; Thu, 15 Oct 2020 02:47:17 -0700 (PDT)
Received: from faui48f.informatik.uni-erlangen.de (faui48f.informatik.uni-erlangen.de [IPv6:2001:638:a000:4134::ffff:52]) by faui40.informatik.uni-erlangen.de (Postfix) with ESMTP id 9F269548610; Thu, 15 Oct 2020 11:47:11 +0200 (CEST)
Received: by faui48f.informatik.uni-erlangen.de (Postfix, from userid 10463) id 98006440059; Thu, 15 Oct 2020 11:47:11 +0200 (CEST)
Date: Thu, 15 Oct 2020 11:47:11 +0200
From: Toerless Eckert <tte@cs.fau.de>
To: Mark Nottingham <mnot@mnot.net>
Cc: Christian Huitema <huitema@huitema.net>, Jared Mauch <jared@puck.nether.net>, IETF <ietf@ietf.org>
Subject: Re: The end of the Internet as we now it
Message-ID: <20201015094711.GA18517@faui48f.informatik.uni-erlangen.de>
References: <1245BFD6-1178-40D2-A475-838687A26A6F@puck.nether.net> <6626EED3-1CC1-4B40-879C-C68425A41B78@gmail.com> <8119d23c-5db5-060e-34e9-895d50c6eb4b@huitema.net> <8686EA57-4A60-4B56-98E1-503344C86627@mnot.net> <648fcb28-688e-0a37-cac6-9eb6821002ce@huitema.net> <B3F3D160-C295-49DE-BC50-E91635CCE15C@mnot.net>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <B3F3D160-C295-49DE-BC50-E91635CCE15C@mnot.net>
User-Agent: Mutt/1.10.1 (2018-07-13)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/ZzrVygnSXsEeeyUvoK4RcCqXSN4>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 15 Oct 2020 09:47:20 -0000

Christian: Its most likely Marks fault. Since rfc8890 he is responsible for
the list of end users for the Internet and must have forgotten to add you.

Mark: Expecting Christian to understand rfc7230 headers before he
can read it is recursive logic.

Christian: wget -d https://tools.ietf.org/html/rfc7230

paste relevant output if that does not work.

I think what Mark was suggesting is:

openssl s_client -crlf -connect tools.ietf.org:443
GET /html/rfc7230 HTTP/1.1
User-Agent: Not Christian Huitema
Host: tools.ietf.org

(don't forget empty line at the end)

Cheers
    Toerless

On Thu, Oct 15, 2020 at 05:18:49PM +1100, Mark Nottingham wrote:
> Send:
> 
> GET /html/rfc7230 HTTP/1.1
> Host: tools.ietf.org
> Is-Christian: ?0
> 
> Cheers,
> 
> 
> > On 15 Oct 2020, at 5:17 pm, Christian Huitema <huitema@huitema.net> wrote:
> > 
> > I think there must be some side effect from my setup. What is really
> > weird is that it fails from 2 different computers.
> > 
> > I know the RFC can be accessed elsewhere. In fact, the IETF datatracker
> > works. It is just an issue for me with the tool server. But it is really
> > weird.
> > 
> > On 10/14/2020 11:10 PM, Mark Nottingham wrote:
> >> Christian,
> >> 
> >> The relevant HTTP RFCs are also available at <https://httpwg.org/specs/> -- and of course <https://rfc-editor.org/>.
> >> 
> >> Cheers,
> >> 
> >> 
> >>> On 15 Oct 2020, at 5:01 pm, Christian Huitema <huitema@huitema.net> wrote:
> >>> 
> >>> Keeps not working for me. Tried getting RFC1984, same result. Tried from my IPhone and that's forbidden too. I wonder whether I was put on some kind of no-rfc list.
> >>> 
> >>> On 10/14/2020 10:37 PM, Fred Baker wrote:
> >>>> Works for me...
> >>>> 
> >>>> Sent from my iPad
> >>>> 
> >>>>> On Oct 14, 2020, at 10:08 PM, Jared Mauch <jared@puck.nether.net> wrote:
> >>>>> 
> >>>>> ??? Seems to work for me. 
> >>>>> 
> >>>>> Sent from my iCar
> >>>>> 
> >>>>>> On Oct 15, 2020, at 12:20 AM, Christian Huitema <huitema@huitema.net> wrote:
> >>>>>> 
> >>>>>> ???
> >>>>>> Trying to access RFC 7230 as https://tools.ietf.org/html/rfc7230, I get:
> >>>>>> 
> >>>>>> Forbidden
> >>>>>> 
> >>>>>> You don't have permission to access /html/rfc7230 on this server.
> >>>>>> 
> >>>>>> Additionally, a 403 Forbidden error was encountered while trying to use an ErrorDocument to handle the request.
> >>>>>> Apache/2.2.22 (Debian) Server at tools.ietf.org Port 443
> >>>>>> 
> >>>>>> 
> >>>>>> So, the Internet is no for everybody anymore...
> >>>>>> 
> >>>>>> -- Christian Huitema
> >> --
> >> Mark Nottingham   https://www.mnot.net/
> >> 
> 
> --
> Mark Nottingham   https://www.mnot.net/

-- 
---
tte@cs.fau.de