IETF Logo Mail Archive

Re: rfc791 coming up to 40 years ... what to do (remember, celebrate, ...?)

Phillip Hallam-Baker <phill@hallambaker.com> Wed, 24 March 2021 21:24 UTC

Return-Path: <hallam@gmail.com>
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 581B23A0BCC for <ietf@ietfa.amsl.com>; Wed, 24 Mar 2021 14:24:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.399
X-Spam-Level:
X-Spam-Status: No, score=-1.399 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FORGED_FROMDOMAIN=0.249, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.25, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, 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 wmYmNpAEFupj for <ietf@ietfa.amsl.com>; Wed, 24 Mar 2021 14:24:40 -0700 (PDT)
Received: from mail-yb1-f170.google.com (mail-yb1-f170.google.com [209.85.219.170]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 83BDE3A0BC7 for <ietf@ietf.org>; Wed, 24 Mar 2021 14:24:40 -0700 (PDT)
Received: by mail-yb1-f170.google.com with SMTP id j2so67208ybj.8 for <ietf@ietf.org>; Wed, 24 Mar 2021 14:24:40 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=yVBx5DrtpTbNnXogmdxvZkf2q60BrTTQXirP6mMHQNU=; b=ojg+iYMrWt9Ymf2yZ4do5vUdN5Gun+BTOrvNSe4KsNwMn9slR+rGBLm9lgn7S2M0lp FH1ZDuCMwBxsoJg/zCF8gtwEMmA+bgGjscWvZgGhCeRLthV+dBKPlcREhpt2fpEvD0nx igJUr7PogqCb7JGYyZvgFkTtAMiNq15K3BylelGVNzWf5lh62qYw851hXPkQ3zf0w1e9 Ezop+Bd3YUcPNIWOJqOWkLIXO63sf7BoH9XRw9ylSppqFEmjSmzP72Di6S7qa7D61WgH rg/Lg1j+r1cSqHBpBuLlI0SQbTkEjLloSjUC/VRSxSbT56KSlZZQ43wmFCyUnsN1Kmf4 lUBg==
X-Gm-Message-State: AOAM531hAAjERRR+i1RZK1T/OvsxH1MXQDZoungcjSiwvLpqXLw0VKQq YXRWN9AGSSHOkUYdeNKulaZUMdRSTfMcBdEJVAQ=
X-Google-Smtp-Source: ABdhPJzcu3k16+cEACUWhnkcZBHZlXekPeY8qjFaYSyW3+rnx6+TO+Wa2qMQkWksIw4ZzLzG8HS87YRlRuD7uVTOyc0=
X-Received: by 2002:a25:bf88:: with SMTP id l8mr7709136ybk.213.1616621079711; Wed, 24 Mar 2021 14:24:39 -0700 (PDT)
MIME-Version: 1.0
References: <4c4460b9-5074-a320-6ebb-8b537f4c22a2@network-heretics.com> <A5F380FA-FB87-46CB-9D77-1FDB4453E8BD@strayalpha.com> <CAC8QAcfLqmf8Hq22fr6SQQxGj7i9p4n0i=WG1fUBX9hnHwT55Q@mail.gmail.com>
In-Reply-To: <CAC8QAcfLqmf8Hq22fr6SQQxGj7i9p4n0i=WG1fUBX9hnHwT55Q@mail.gmail.com>
From: Phillip Hallam-Baker <phill@hallambaker.com>
Date: Wed, 24 Mar 2021 17:24:30 -0400
Message-ID: <CAMm+LwjunKat1rp9QgkmZEKrp0zUAzPDL8Mp35f6saX5dyzu7g@mail.gmail.com>
Subject: Re: rfc791 coming up to 40 years ... what to do (remember, celebrate, ...?)
To: sarikaya@ieee.org
Cc: Joe Touch <touch@strayalpha.com>, Keith Moore <moore@network-heretics.com>, IETF <ietf@ietf.org>
Content-Type: multipart/alternative; boundary="00000000000031551005be4eedfa"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/oocMZq21nJo5MzsIenlZ04MIotc>
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: Wed, 24 Mar 2021 21:24:45 -0000

On Wed, Mar 24, 2021 at 10:46 AM Behcet Sarikaya <sarikaya2012@gmail.com>
wrote:

>
>
> On Tue, Mar 23, 2021 at 4:19 PM Joe Touch <touch@strayalpha.com> wrote:
>
>>
>>
>> > On Mar 23, 2021, at 2:05 PM, Keith Moore <moore@network-heretics.com>
>> wrote:
>> >
>> >> On 3/23/21 3:57 PM, Spencer Dawkins at IETF wrote:
>> >>
>> >> I'd like to see some observance like this. Another related day that
>> might serve was the TCP/IP Flag Day, when Arpanet stopped carrying NCP, on
>> January 1, 1983.
>> >
>> > Maybe the public Internet can start filtering advertisements for IPv4
>> prefixes on the 40th anniversary of that date?
>>
>> That’s one way to make sure the Internet doesn’t make it to 41.
>>
>>
> +1
>
> Also let's celebrate as Toerless suggests on January 1, 2023 as TCP/IP
> Flag Day.
> My guess is by then QUIC will be ready to take over TCP, so after that
> day, TCP/IP no more but long live QUIC/IP
>

That won't ever happen because the mistake in TCP/IP was to imagine that
transport is a kernel level concern.

Transport started moving to the application stack when SSL happened. And
QUIC is only the logical endpoint. But contrary to expectations here, the
logic that there can only be one TCP does not apply to QUIC. Once you move
Transport up to application, it is going to be game on and QUIC is going to
be the first of many.

And this is a good thing. TCP responds poorly to HTTP needs because it is
optimized for file transfer. QUIC is optimized for Web browsing. QUIC is
not optimized for every Internet application because not everything is Web
browsing and not every Internet application is a Web browser. That wasn't
the goal in 1992 and it certainly isn't the goal now that Web browsers are
entering middle age with a rather nasty case of 'spread'.

v2.23.0 | Report a Bug | By Email