Re: [Lsvr] Kicking off the LSVR (Link State Vector Routing) charter discussion

Randy Bush <randy@psg.com> Thu, 25 January 2018 20:15 UTC

Return-Path: <randy@psg.com>
X-Original-To: lsvr@ietfa.amsl.com
Delivered-To: lsvr@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CE2D612EA62 for <lsvr@ietfa.amsl.com>; Thu, 25 Jan 2018 12:15:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.911
X-Spam-Level:
X-Spam-Status: No, score=-6.911 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 XqQVIMUlrcpX for <lsvr@ietfa.amsl.com>; Thu, 25 Jan 2018 12:15:36 -0800 (PST)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:8006::18]) (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 337D512EA98 for <lsvr@ietf.org>; Thu, 25 Jan 2018 12:15:36 -0800 (PST)
Received: from localhost ([127.0.0.1] helo=ryuu.rg.net) by ran.psg.com with esmtp (Exim 4.86_2) (envelope-from <randy@psg.com>) id 1eenvp-0006ig-0N; Thu, 25 Jan 2018 20:15:33 +0000
Date: Thu, 25 Jan 2018 12:15:32 -0800
Message-ID: <m28tcllmor.wl-randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Tony Li <tony1athome@gmail.com>
Cc: "Jakob Heitz (jheitz)" <jheitz@cisco.com>, "lsvr@ietf.org" <lsvr@ietf.org>
In-Reply-To: <4DD58182-10E6-480F-A787-DE03DE089355@gmail.com>
References: <AM5PR0701MB2836FFBB9A9F6C3D7C3C7122E0110@AM5PR0701MB2836.eurprd07.prod.outlook.com> <f590456ccee0498eadbb5fa4e4e048cc@XCH-ALN-014.cisco.com> <m2shatlqsd.wl-randy@psg.com> <e7462ad1b5044442a40a505a8d8602c3@XCH-ALN-014.cisco.com> <m2k1w5loyu.wl-randy@psg.com> <4DD58182-10E6-480F-A787-DE03DE089355@gmail.com>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/25.3 Mule/6.0 (HANACHIRUSATO)
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/lsvr/1wGe2xkRglZIu8n9-l7y453XJEU>
Subject: Re: [Lsvr] Kicking off the LSVR (Link State Vector Routing) charter discussion
X-BeenThere: lsvr@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Link State Vector Routing <lsvr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/lsvr>, <mailto:lsvr-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/lsvr/>
List-Post: <mailto:lsvr@ietf.org>
List-Help: <mailto:lsvr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/lsvr>, <mailto:lsvr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 25 Jan 2018 20:15:38 -0000

>>>>> Should  LSVR introduce a grouping in the way that OSPF has areas and 
>>>>> ISIS has levels?
>>>> to what purpose?
>>> For scalability.
>> i thought that is why we were using bgp.
> That addresses the scalability of update propagation, but the SPF
> operation is still O(n log n) on the size of the area database. If
> there is no abstraction, this will balloon.

does bgp not already provide [too] many mechanisms for scoping
propagation?

>>> The OSPF "areas" concept looks quite easy: just use regular VGP
>>> routes between "areas".  The only difference is that an OSPF ABR
>>> straddles the area boundaries, whereas an AS boundary is between 2
>>> ASBRs in BGP.
>>> The ISIS concept of levels could get interesting if duplicated in
>>> BGP SPF.  It joins level 1 domains with level 2 links.
>> i am sure we can figure out how to complicate it.
> It actually would be more complicated to not respect the abstractions
> that the base protocol is expecting.

given that the base protocol is bgp, we could list the abstractions it
provides for limiting scope except this margin is too small.

randy