Re: [Lsvr] Comments on LSVR with RR peering

Randy Bush <randy@psg.com> Wed, 05 December 2018 22:23 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 6263B130E03 for <lsvr@ietfa.amsl.com>; Wed, 5 Dec 2018 14:23: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 djE-rND2GWJ0 for <lsvr@ietfa.amsl.com>; Wed, 5 Dec 2018 14:23: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 CAA7A130DC4 for <lsvr@ietf.org>; Wed, 5 Dec 2018 14:23: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 1gUfaA-0002lv-OL; Wed, 05 Dec 2018 22:23:50 +0000
Date: Wed, 05 Dec 2018 14:23:50 -0800
Message-ID: <m2lg53liix.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: <5a1b19d9-de7a-3c0c-c7fe-0df559956d12@juniper.net>
References: <2384fdea-b8f9-ea6d-5287-83f39908fcb0@juniper.net> <m2lg54naid.wl-randy@psg.com> <378f54f4-8b92-3859-519b-3539f49b42d6@juniper.net> <m2o99zlmgk.wl-randy@psg.com> <5a1b19d9-de7a-3c0c-c7fe-0df559956d12@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/fiQ9tJ-EaGH44u54ph6Zhdgp2lk>
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 22:23:55 -0000

> Perhaps the authors can clarify what they meant by "BGP speakers peer 
> solely with one or more ... controllers".
> 
> On 12/5/2018 3:58 PM, Randy Bush wrote:
>> 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
> 

perhaps they thought "directly" in the section title of 2.2 would give
us a clue

     2.2. BGP Peering Between Directly Connected Network Nodes

followed by
  
    2.3.  BGP Peering in Route-Reflector or Controller Topology

       In this model, BGP speakers peer solely with one or more Route
       Reflectors [RFC4456] or controllers.  As in the previous model,
       direct connection discovery and liveliness detection for those
       connections are done outside the BGP protocol.   

so would you have them clarify 2.3 with something such as

    as with non-spf bgp route reflection, clients are directly connected
    to the reflector(s)

randy