Re: [Lsvr] Comments on LSVR with RR peering

Stewart Bryant <stewart.bryant@gmail.com> Thu, 06 December 2018 10:20 UTC

Return-Path: <stewart.bryant@gmail.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 85427130E1A for <lsvr@ietfa.amsl.com>; Thu, 6 Dec 2018 02:20:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 cmyD-rTprx75 for <lsvr@ietfa.amsl.com>; Thu, 6 Dec 2018 02:20:03 -0800 (PST)
Received: from mail-wm1-x32b.google.com (mail-wm1-x32b.google.com [IPv6:2a00:1450:4864:20::32b]) (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 73C49129BBF for <lsvr@ietf.org>; Thu, 6 Dec 2018 02:20:03 -0800 (PST)
Received: by mail-wm1-x32b.google.com with SMTP id y139so380863wmc.5 for <lsvr@ietf.org>; Thu, 06 Dec 2018 02:20:03 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-transfer-encoding:content-language; bh=yzataEkpoAl163ePxigEvDLY9AKO0EJUKRGcqBsXV6U=; b=g4eh2B06M/1FU343w9xJXfSF6VrwpDNojLpVwbeiH4Bs6s9uJoMIXo94XDiEke2mJv JfKr2hnXNwbja/EJveK5gbNko5ncYWnl/QIo8pPoaBOHN9Wfc5oIVqCWfpsE3x5Hmug8 ag6j+gIvaWZoK7NcZjpIcz9XEqEgaqaiadCU5IMXbxOydOVFidUWUlYriV/W4DgkwuWP puWj9L9GGi1SdzCEUq417tdsfWy25CcIWlYdtEmGkOM8r6JH2nVoUEhEpgtnaEpprK/3 /76hhz8Xd9G7gm6N6+JkGuDi08o4OzPY7GuQ5dXzB+AWY37GpkTKuY0v8MsUJy5C3UFD UkCg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding :content-language; bh=yzataEkpoAl163ePxigEvDLY9AKO0EJUKRGcqBsXV6U=; b=Lm6JttErRGTcdtifGTdwj9EjbH7+uXr8lSQV5ClS7tr1W7+Iu0Y74ScEYpgX9zY+yG 7KMp+ZtQpvRoKIp+TYywAdmdrptZuebx7CPRtzhIvBvrxTJ3exFn3ybP1uFWnVOJQa3l D4jfJO9ielWlZOhElkXiCG9OfHnC9m4K54IKiFi9zFupIgbS9Z/qKRxV/5LQiNr73glH o/05IkvgMAFShmy4V6widEPtpxVp8v+xOWkuKw++uJXJSVthg4PvCGQDcUrGa+nyEUEE n+fIihmLghWDUGiM8a/AFpIGugYG+zPgCpxxdqLNWfPw+q1jq9bgqhW9axsPIg6MMRQp Uynw==
X-Gm-Message-State: AA+aEWbAfMirL+j1/cRMiJHvPfGZ9kq+dl0ITVAuCZhVlH1Tyz5bVVRu nFc8jFjmDAekA5GYAW5WBhdIFlP/
X-Google-Smtp-Source: AFSGD/VnSkQeX10hiIPLyb51MrgCHFJGcqm9bjXa90khoTvirFQUHITvcJQ0ba69e+U57qYscxN8Kg==
X-Received: by 2002:a1c:18c:: with SMTP id 134mr18516902wmb.88.1544091601616; Thu, 06 Dec 2018 02:20:01 -0800 (PST)
Received: from [192.168.2.198] (host213-123-124-182.in-addr.btopenworld.com. [213.123.124.182]) by smtp.gmail.com with ESMTPSA id t4sm31145160wrm.6.2018.12.06.02.20.00 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 06 Dec 2018 02:20:00 -0800 (PST)
To: Randy Bush <randy@psg.com>, Eric Rosen <erosen@juniper.net>
Cc: "lsvr@ietf.org" <lsvr@ietf.org>
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> <m2lg53liix.wl-randy@psg.com>
From: Stewart Bryant <stewart.bryant@gmail.com>
Message-ID: <c55f0dbb-8816-173c-ea35-dc0b07cbda97@gmail.com>
Date: Thu, 06 Dec 2018 10:19:59 +0000
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.9.1
MIME-Version: 1.0
In-Reply-To: <m2lg53liix.wl-randy@psg.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Content-Language: en-GB
Archived-At: <https://mailarchive.ietf.org/arch/msg/lsvr/C49GA3WCCZCovtT3nLfJArun_eY>
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: Thu, 06 Dec 2018 10:20:05 -0000


On 05/12/2018 22:23, Randy Bush wrote:
>> 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

Presumably in needs to be "directly connected via an alternate physical 
network."

- Stewart



>
> _______________________________________________
> Lsvr mailing list
> Lsvr@ietf.org
> https://www.ietf.org/mailman/listinfo/lsvr