IETF Logo Mail Archive

Re: [Lsvr] Comments on LSVR with RR peering

Randy Bush <randy@psg.com> Tue, 04 December 2018 23:21 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 BE5C912E7C1 for <lsvr@ietfa.amsl.com>; Tue, 4 Dec 2018 15:21:49 -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 7KsWs8cCYjRL for <lsvr@ietfa.amsl.com>; Tue, 4 Dec 2018 15:21:48 -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 8A861127332 for <lsvr@ietf.org>; Tue, 4 Dec 2018 15:21:48 -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 1gUK0g-0000da-NX; Tue, 04 Dec 2018 23:21:46 +0000
Date: Tue, 04 Dec 2018 15:21:46 -0800
Message-ID: <m2lg54naid.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: <2384fdea-b8f9-ea6d-5287-83f39908fcb0@juniper.net>
References: <2384fdea-b8f9-ea6d-5287-83f39908fcb0@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/m7kC24RPXJA8evCiHDy9_QsO1bw>
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: Tue, 04 Dec 2018 23:21:50 -0000

apologies, but i am easily confused.

> 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.
> 
> Suppose BC goes down, and consider the following sequence of events:
> 
> 1. B tells RR (via path B-A-RR) that BC is down.

are you doing some sort of multi-hop or underlay?  if not, then A told
RR that B told her that B-C was down.

> 2. RR tells A (via path RR-A) that BC is down.

did A not know B-C was down already?

randy

v2.23.0 | Report a Bug | By Email