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

Chris Morrow <morrowc@ops-netman.net> Fri, 23 August 2019 20:41 UTC

Return-Path: <morrowc@ops-netman.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 49A4512023E for <architecture-discuss@ietfa.amsl.com>; Fri, 23 Aug 2019 13:41:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.099
X-Spam-Level:
X-Spam-Status: No, score=-1.099 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_ALL=0.8, 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 Doqw2YmHkDvn for <architecture-discuss@ietfa.amsl.com>; Fri, 23 Aug 2019 13:41:45 -0700 (PDT)
Received: from relay.kvm02.ops-netman.net (relay.kvm02.ops-netman.net [IPv6:2606:700:e:550:5c82:28ff:fe25:4960]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 075E3120128 for <architecture-discuss@iab.org>; Fri, 23 Aug 2019 13:41:44 -0700 (PDT)
Received: from mail.ops-netman.net (mailserver.ops-netman.net [199.168.90.119]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by relay.kvm02.ops-netman.net (Postfix) with ESMTPS id C7A8A3FDAA; Fri, 23 Aug 2019 20:41:43 +0000 (UTC)
Received: from mailserver.ops-netman.net.ops-netman.net (localhost [127.0.0.1]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.ops-netman.net (Postfix) with ESMTPSA id 6DA853C2; Fri, 23 Aug 2019 20:41:43 +0000 (UTC)
Date: Fri, 23 Aug 2019 20:41:43 +0000
Message-ID: <87ftlrvcl4.wl-morrowc@ops-netman.net>
From: Chris Morrow <morrowc@ops-netman.net>
To: Ted Hardie <ted.ietf@gmail.com>
Cc: Chris Morrow <morrowc@ops-netman.net>, Fernando Gont <fgont@si6networks.com>, architecture-discuss@iab.org
In-Reply-To: <CA+9kkMDWk3kmYOZ8Zz+BjUZG0+sshQJjR9pYt-NgL8umqpMtWQ@mail.gmail.com>
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>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/24.5 Mule/6.0 (HANACHIRUSATO)
Organization: Operations Network Management, Ltd.
MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue")
Content-Type: text/plain; charset="US-ASCII"
Archived-At: <https://mailarchive.ietf.org/arch/msg/architecture-discuss/7hzwJ0HD8NZr4Nau8wCnwiO-BZ4>
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: Fri, 23 Aug 2019 20:41:46 -0000

On Fri, 23 Aug 2019 20:28:43 +0000,
Ted Hardie <ted.ietf@gmail.com> wrote:
> 
> [1  <text/plain; UTF-8 (7bit)>]
> Howdy,
> 
> On Fri, Aug 23, 2019 at 11:48 AM Chris Morrow <morrowc@ops-netman.net>
> wrote:
> 
> >
> > I had figured quic was really an admission that: "Adding a new tcp/udp
> > like protocol was much harder to swallow for the internet than just
> > re-using an existing thing (UDP)."
> >
> > quic COULD have just as easily been done over tcp, esp, ah, icmp ...
> > all of those come with some baggage though, which UDP didn't have.
> > (admittedly udp has it's own baggage)
> >
> 
> Changing TCP behavior on most systems requires modifying the kernel.

sure, and permitting <new protocol number> though/around/over/etc all
the various 'firewall' things (not to mention that security NAT
device) is also .. fun.

> Having something built so that it could be modified in user space really
> was important.  UDP is just a demux for QUIC and that's a success because
> it enabled all of the other functionality to go up into the user space.
>

agree, just saying that there are lots of reasons why: "picked udp, not X".
but that really ... as fernando said any other number would have also worked...

except that UDP has pretty universal access end-to-end without
molestation AND it's not something kernels generally do much with
except: "here ya go socket listener!"

> Just my perspective,

thanks! (I also have a perspective! which I hope gets better with new
glasses) :)

-chris