Re: [Int-area] New Version Notification for draft-li-int-aggregation-00.txt

Toerless Eckert <tte@cs.fau.de> Fri, 25 February 2022 16:37 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 1F4EB3A0D40 for <int-area@ietfa.amsl.com>; Fri, 25 Feb 2022 08:37:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.649
X-Spam-Level:
X-Spam-Status: No, score=-6.649 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.25, RCVD_IN_DNSWL_HI=-5, 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 8_vxs1ziig3Q for <int-area@ietfa.amsl.com>; Fri, 25 Feb 2022 08:37:47 -0800 (PST)
Received: from faui40.informatik.uni-erlangen.de (faui40.informatik.uni-erlangen.de [131.188.34.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 393E83A091C for <int-area@ietf.org>; Fri, 25 Feb 2022 08:37:46 -0800 (PST)
Received: from faui48e.informatik.uni-erlangen.de (faui48e.informatik.uni-erlangen.de [IPv6:2001:638:a000:4134::ffff:51]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by faui40.informatik.uni-erlangen.de (Postfix) with ESMTPS id ED627549E97; Fri, 25 Feb 2022 17:37:40 +0100 (CET)
Received: by faui48e.informatik.uni-erlangen.de (Postfix, from userid 10463) id D55DA4EA768; Fri, 25 Feb 2022 17:37:40 +0100 (CET)
Date: Fri, 25 Feb 2022 17:37:40 +0100
From: Toerless Eckert <tte@cs.fau.de>
To: "touch@strayalpha.com" <touch@strayalpha.com>
Cc: Tony Li <tony.li@tony.li>, int-area@ietf.org
Message-ID: <YhkF1OW5x43qI0FN@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>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <0486FE87-601F-480F-9B93-4BC9777421F9@strayalpha.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/int-area/M426_aFMG8OHLqJFzon75SJ5W-0>
Subject: Re: [Int-area] 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: Fri, 25 Feb 2022 16:37:54 -0000

I primarily thought that the document wasn't improving by making statements
about routing and addressing in general given how it does specifically seem
to want to improve the situation for the Internet Architecture, so non-Internet
Architecture considerations would be derailments ?!

Aka: Avoid for the document to have to deal with the type of generic discussion
like what you're opening up in your email (which of course is a fun discussion).

For example:

Is LISP really part of the Internet Architecture ? I thought (unfortunately)
not. E.g.: i don't think i can become an Internet transit ISP without participating
in the "native" BGP routing. "Hey, i don't want these gigantic BGP Internet
routing tables, and my customers don't need it. I just want do do LISP".

If we didn't have the need for the global Internet BGP routing table,
but had a requirement that every Internet ISP had to use LISP, would
there be a need for Tony to write this document ? 

Cheers
    Toerless

On Fri, Feb 25, 2022 at 07:40:25AM -0800, touch@strayalpha.com wrote:
> 
> > On Feb 25, 2022, at 12:02 AM, Toerless Eckert <tte@cs.fau.de> wrote:
> > 
> >> Abstract
> >> 
> >>    Routing and addressing are inexorably tied, and the scalability of
> > 
> >     ^
> > Nit:
> >    prepend "In the Internet architecture"
> > 
> > E.g.: If we would have a better architecture, including LISP, we would
> > arguably have a less than inexorable tie... i think.
> 
> 
> There are only so many ways to determine paths, e.g.:
> - by the structure of the address itself
> - by flooding, at least until you cache a path
> - by knowing what flooding would have accomplished, e.g., by ‘global knowledge’ of the network topology
> 
> We use all three in the Internet (longest prefix, ARP/LISP, and RIP/OSPF, respectively).
> 
> “Better” is relative; structure is more efficient and scalable but harder to manage, flooding is least efficient and scalable but requires no management, and global knowledge is a bit of a balance between the two.
> 
> Or is there some other “better” you’re imagining?
> 
> Joe