Re: [arch-d] FYI: closure of the IAB Stack Evolution program

John Leslie <john@jlc.net> Sun, 25 August 2019 19:41 UTC

Return-Path: <john@jlc.net>
X-Original-To: architecture-discuss@ietfa.amsl.com
Delivered-To: architecture-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 64D841200F7 for <architecture-discuss@ietfa.amsl.com>; Sun, 25 Aug 2019 12:41:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham 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 42qbHqL1HFA3 for <architecture-discuss@ietfa.amsl.com>; Sun, 25 Aug 2019 12:41:36 -0700 (PDT)
Received: from mailhost.jlc.net (mailhost.jlc.net [199.201.159.4]) by ietfa.amsl.com (Postfix) with ESMTP id 4470E12004D for <architecture-discuss@iab.org>; Sun, 25 Aug 2019 12:41:36 -0700 (PDT)
Received: by mailhost.jlc.net (Postfix, from userid 104) id B4957908893; Sun, 25 Aug 2019 15:41:35 -0400 (EDT)
Date: Sun, 25 Aug 2019 15:41:35 -0400
From: John Leslie <john@jlc.net>
To: Christian Huitema <huitema@huitema.net>
Cc: Fernando Gont <fgont@si6networks.com>, architecture-discuss@iab.org
Message-ID: <20190825194135.GB78819@verdi>
References: <B5A0F4E0-D437-4DF9-9918-C35627A8CADC@trammell.ch> <d5009253-4884-9f1f-66e7-1159e85524b9@si6networks.com> <770822F2-688F-44EA-A6A1-7E7EDBFAA989@trammell.ch> <cece8133-6b69-a677-52fc-a7fb4c7d5136@si6networks.com> <64E3A59C-8709-41E0-B74F-C036E4481AE4@apple.com> <f3645e11-d823-4308-3f51-6f2da5e33180@si6networks.com> <87imqnvhui.wl-morrowc@ops-netman.net> <CA+9kkMDWk3kmYOZ8Zz+BjUZG0+sshQJjR9pYt-NgL8umqpMtWQ@mail.gmail.com> <eb2bc35f-ea95-69b9-5163-baded0c47478@si6networks.com> <19058eaf-47e9-7cac-bf34-cfef646a9bd6@huitema.net>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <19058eaf-47e9-7cac-bf34-cfef646a9bd6@huitema.net>
User-Agent: Mutt/1.6.1 (2016-04-27)
Archived-At: <https://mailarchive.ietf.org/arch/msg/architecture-discuss/CF5PLX9MyTEYwlC7Z9dJKatuqQg>
Subject: Re: [arch-d] FYI: closure of the IAB Stack Evolution program
X-BeenThere: architecture-discuss@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: open discussion forum for long/wide-range architectural issues <architecture-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/architecture-discuss>, <mailto:architecture-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/architecture-discuss/>
List-Post: <mailto:architecture-discuss@ietf.org>
List-Help: <mailto:architecture-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/architecture-discuss>, <mailto:architecture-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 25 Aug 2019 19:41:37 -0000

Christian Huitema <huitema@huitema.net> wrote:
> 
> I think we are getting caught in disputes over vocabulary. Two things
> are true at the same time:
> 
> 1) We cannot send packets in which the IP protocol or IPv6 payload type
> is set to a different value than TCP or UDP and expect them to reach
> destinations across the Internet.

   We certainly _can_ send different payload types.

   We _can_ design protocols which check whether those payload types are
received.

   There are other approaches which _today_ seem much more practical.

> 2) QUIC, BitTorrent and SCTP demonstrate that you can run a protocol on
> top of UDP that has all the characteristics of a classic transport
> protocol, including error recovery and congestion control. ( QUIC can
> perform mux/demux by itself, using the "connection ID" field, but most
> deployments refrain from using multiple layers of multiplexing.)

   Absolutely true!

> Using UDP causes 8 bytes of overhead per packet, which is unfortunate.

   True. We chose the wrong size limits 25 years ago. Next time I hope
we'll know better. (25 years ago, 8 bytes of overhead was significant
by itself.)

> You may call that a middle-box tax if you want. But as long as you are
> willing to pay that tax, you can of course deploy new transmission
> control protocols over the Internet. Most people will call them
> transport protocols.

   Actually, what we call them _does_ make a real difference. I'd be happy
to call them "transport protocols"...

--
John Leslie <john@jlc.net>