Re: [Lsvr] Comments on LSVR with RR peering

Randy Bush <randy@psg.com> Wed, 05 December 2018 20:58 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 53219130F55 for <lsvr@ietfa.amsl.com>; Wed, 5 Dec 2018 12:58:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.901
X-Spam-Level:
X-Spam-Status: No, score=-6.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-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 cPt8pfoqnhMR for <lsvr@ietfa.amsl.com>; Wed, 5 Dec 2018 12:58:53 -0800 (PST)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:8006::18]) (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 AD68A130F80 for <lsvr@ietf.org>; Wed, 5 Dec 2018 12:58:53 -0800 (PST)
Received: from localhost ([127.0.0.1] helo=ryuu.rg.net) by ran.psg.com with esmtp (Exim 4.90_1) (envelope-from <randy@psg.com>) id 1gUeFv-0002P7-N8; Wed, 05 Dec 2018 20:58:52 +0000
Date: Wed, 05 Dec 2018 12:58:51 -0800
Message-ID: <m2o99zlmgk.wl-randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Eric Rosen <erosen@juniper.net>
Cc: "lsvr@ietf.org" <lsvr@ietf.org>
In-Reply-To: <378f54f4-8b92-3859-519b-3539f49b42d6@juniper.net>
References: <2384fdea-b8f9-ea6d-5287-83f39908fcb0@juniper.net> <m2lg54naid.wl-randy@psg.com> <378f54f4-8b92-3859-519b-3539f49b42d6@juniper.net>
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="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/lsvr/_2-MK40kvGgzu-XpVDXH1sUaejQ>
Subject: Re: [Lsvr] Comments on LSVR with RR peering
X-BeenThere: lsvr@ietf.org
X-Mailman-Version: 2.1.29
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: Wed, 05 Dec 2018 20:58:56 -0000

i think i see the disconnect

>>> RR--1--A--1--B--1--C--1--D--1--E
>>>                |                 |
>>>                |-----5-----F--1--|
>>>
>>> The letters represent routers (RR being the Route Reflector), and the
>>> numbers are link metrics.

B, C, D, E, and F may not be clients of RR.  2.2 says you can use
loopbacks.  this does not imply that you can multi-hop peer a la ibgp.
hence, 2.3 does not allow multi-hop.

or i am still confused.

randy