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

Joe Touch <touch@strayalpha.com> Mon, 26 August 2019 04:45 UTC

Return-Path: <touch@strayalpha.com>
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 E89B4120824 for <architecture-discuss@ietfa.amsl.com>; Sun, 25 Aug 2019 21:45:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.219
X-Spam-Level:
X-Spam-Status: No, score=-1.219 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_NEUTRAL=0.779] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=strayalpha.com
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 5qxGyLpJE6ab for <architecture-discuss@ietfa.amsl.com>; Sun, 25 Aug 2019 21:45:08 -0700 (PDT)
Received: from server217-3.web-hosting.com (server217-3.web-hosting.com [198.54.115.226]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8AAC31200A4 for <architecture-discuss@iab.org>; Sun, 25 Aug 2019 21:45:08 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=strayalpha.com; s=default; h=To:References:Message-Id:Cc:Date:In-Reply-To: From:Subject:Mime-Version:Content-Type:Sender:Reply-To: Content-Transfer-Encoding:Content-ID:Content-Description:Resent-Date: Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Id: List-Help:List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=GcvAO7PXnPVLVtiFhI31gKGBw4NzNDkThjUY87JGYxw=; b=QU6iwjJfjN9ntc4iAvkOfU5xQ x72RLSn6xk/pit3MNaYUT54f3kNCT3Km5KMoLenzzMbsekkBSX8Jy8lbH8EwofDtKOKJOaasjL6tr j04qPYyMdmAHZ+JaXo/dsfGOFBtzBOGtZ3EipGW6CeC5HDU9blS0X0sLTXmgtWmaIAzVAc/zEVBNQ FZ9aTCqCU2sWhdpkzMPbv0pJYkIW2wZZBd4Gfiv9uKVPa4M97vRAuUssf0OXjCzOFjf1S/bAOo0Pa gmYzt4eldgEQNkH8zdgpOBoCL9Py0/O7oQ/NC6TvstToj/Y9m6BY76oun9QqenmAyF1Fqj/T1NVUV /GNJm/YMg==;
Received: from cpe-172-250-225-198.socal.res.rr.com ([172.250.225.198]:59530 helo=[192.168.1.10]) by server217.web-hosting.com with esmtpsa (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.92) (envelope-from <touch@strayalpha.com>) id 1i26sJ-000M1v-2k; Mon, 26 Aug 2019 00:45:07 -0400
Content-Type: multipart/alternative; boundary="Apple-Mail=_9F707663-0E0F-4B35-A7D2-B046631385C4"
Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\))
From: Joe Touch <touch@strayalpha.com>
In-Reply-To: <01b1dcd9-1acf-784e-1b71-f6e497a2f472@si6networks.com>
Date: Sun, 25 Aug 2019 21:45:02 -0700
Cc: Christian Huitema <huitema@huitema.net>, architecture-discuss@iab.org
Message-Id: <F9D68FFD-9B60-4CAF-A9F6-039B2C957FD2@strayalpha.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> <eb2bc35f-ea95-69b9-5163-baded0c47478@si6networks.com> <19058eaf-47e9-7cac-bf34-cfef646a9bd6@huitema.net> <01b1dcd9-1acf-784e-1b71-f6e497a2f472@si6networks.com>
To: Fernando Gont <fgont@si6networks.com>
X-Mailer: Apple Mail (2.3445.9.1)
X-OutGoing-Spam-Status: No, score=-1.0
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - server217.web-hosting.com
X-AntiAbuse: Original Domain - iab.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - strayalpha.com
X-Get-Message-Sender-Via: server217.web-hosting.com: authenticated_id: touch@strayalpha.com
X-Authenticated-Sender: server217.web-hosting.com: touch@strayalpha.com
X-Source:
X-Source-Args:
X-Source-Dir:
X-From-Rewrite: unmodified, already matched
Archived-At: <https://mailarchive.ietf.org/arch/msg/architecture-discuss/-KOAP1MNALczbTE-s3twM9ko9Cg>
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: Mon, 26 Aug 2019 04:45:10 -0000


> If IP is Internet, and QUIC is transport, what do you call the UDP that
> stis in between?


Therein lies the error.

QUIC alone is not a transport.

It’s not complete enough to be transport by itself. It doesn’t provide the socket (as in RFC793’s idea of a socket) demuxing.

IMO, QUIC + UDP is a transport layer. A layer that provides a more complex service than UDP alone.

So yes, UDP is a transport layer - when operating by itself. But when paired with QUIC, it is the pair that are the transport.

UDP affords the ability to design new transports on top of a basic muxing service. Those new transports CAN be inside user space, but that’s not the point necessarily - they can easily also be implemented inside an OS.

(and IMO, UDP options help extend that muxing service without necessarily completing all the features we call a transport, so that’s consistent here too).

Joe