[Int-area] tunneling and recursion (was: Re: New Version Notification for draft-li-int-aggregation-00.txt)

Toerless Eckert <tte@cs.fau.de> Mon, 28 February 2022 17:54 UTC

Return-Path: <eckert@i4.informatik.uni-erlangen.de>
X-Original-To: int-area@ietfa.amsl.com
Delivered-To: int-area@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A38723A12C8 for <int-area@ietfa.amsl.com>; Mon, 28 Feb 2022 09:54:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.881
X-Spam-Level:
X-Spam-Status: No, score=-5.881 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.248, RCVD_IN_DNSWL_HI=-5, SPF_HELO_NONE=0.001, SPF_NEUTRAL=0.779, T_SCC_BODY_TEXT_LINE=-0.01, 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 Bd4VqEdG3YF2 for <int-area@ietfa.amsl.com>; Mon, 28 Feb 2022 09:54:16 -0800 (PST)
Received: from faui40.informatik.uni-erlangen.de (faui40.informatik.uni-erlangen.de [IPv6:2001:638:a000:4134::ffff:40]) (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 1EB4E3A12AF for <int-area@ietf.org>; Mon, 28 Feb 2022 09:54:15 -0800 (PST)
Received: from faui48e.informatik.uni-erlangen.de (faui48e.informatik.uni-erlangen.de [131.188.34.51]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits)) (No client certificate requested) by faui40.informatik.uni-erlangen.de (Postfix) with ESMTPS id 8F8D9549C11; Mon, 28 Feb 2022 18:54:10 +0100 (CET)
Received: by faui48e.informatik.uni-erlangen.de (Postfix, from userid 10463) id 849CC4EA7B1; Mon, 28 Feb 2022 18:54:10 +0100 (CET)
Date: Mon, 28 Feb 2022 18:54:10 +0100
From: Toerless Eckert <tte@cs.fau.de>
To: "touch@strayalpha.com" <touch@strayalpha.com>
Cc: Dino Farinacci <farinacci@gmail.com>, int-area@ietf.org
Message-ID: <Yh0MQkNKsdQcSm21@faui48e.informatik.uni-erlangen.de>
References: <164367925561.21687.13323438769934745511@ietfa.amsl.com> <A5236BE8-2499-4E45-8B06-C131C4324611@tony.li> <YhiNEDhMoo2HRVPz@faui48e.informatik.uni-erlangen.de> <0486FE87-601F-480F-9B93-4BC9777421F9@strayalpha.com> <YhkF1OW5x43qI0FN@faui48e.informatik.uni-erlangen.de> <4D049831-0A06-440F-9E37-E04F470050B8@gmail.com> <75401375-5137-4D15-B3BE-2E3C4981BCE5@strayalpha.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <75401375-5137-4D15-B3BE-2E3C4981BCE5@strayalpha.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/int-area/vDUsoQ6mk0D0cVR3AzVw_YPXZ7o>
Subject: [Int-area] tunneling and recursion (was: Re: New Version Notification for draft-li-int-aggregation-00.txt)
X-BeenThere: int-area@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF Internet Area WG Mailing List <int-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/int-area>, <mailto:int-area-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/int-area/>
List-Post: <mailto:int-area@ietf.org>
List-Help: <mailto:int-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/int-area>, <mailto:int-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 28 Feb 2022 17:54:21 -0000

On Fri, Feb 25, 2022 at 08:19:42PM -0800, touch@strayalpha.com wrote:
> I disagree; a tunnel (done correctly) is isomorphic to a link. There’s no difference between tunnels and what we already rely on as “L2”.

I guess wrt. routing we (Internet Routing Architecture) started out with
alot of simplifying assumptions about the properties of links. Primarily them
being full-mesh-mp2mp or p2p. And then MPLS gave us arbitrary mesh mp2p LSPs,
 and then MANET came with arbitrary partial-connectivity meshes. I don't this
we ever formalized any of this so that we could really confidently use 
link or tunnels and be clear about what options the reader will assume.

> The flaw is the OSI model assuming layer levels are absolute (they’re relative) from all viewpoints (again, relative). There’s a strong equivalence between a link, a tunnel, and a router (which, in essence, emulates shared link). And, interestingly, forwarding can also be described as recursive tunneling.

I thought you just look whats on the wire and you know
the level. If its a frame it's L2, if it's a packet, it's L3. If it's
anything more complicated, it's a tunnel (sorry, couldn't resist ;-))

Is there any IETF RFC that is actually any better than OSI in this respect ?

And yes. I wish there was better material about recursion as the core
fundamental of building networks. Especially because so far we mostly
have re-invented the wheel for every instance of recursion (frame,
packets, tunnel headers..).

Cheers
    Toerless