Re: [Lsvr] Comments on LSVR with RR peering

Eric Rosen <erosen@juniper.net> Wed, 05 December 2018 14:42 UTC

Return-Path: <erosen@juniper.net>
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 F2BD212785F for <lsvr@ietfa.amsl.com>; Wed, 5 Dec 2018 06:42:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.161
X-Spam-Level:
X-Spam-Status: No, score=-4.161 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-1.46, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=juniper.net
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 61UYS4fKQZUG for <lsvr@ietfa.amsl.com>; Wed, 5 Dec 2018 06:42:25 -0800 (PST)
Received: from mx0a-00273201.pphosted.com (mx0a-00273201.pphosted.com [208.84.65.16]) (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 CADE8124BF6 for <lsvr@ietf.org>; Wed, 5 Dec 2018 06:42:25 -0800 (PST)
Received: from pps.filterd (m0108159.ppops.net [127.0.0.1]) by mx0a-00273201.pphosted.com (8.16.0.27/8.16.0.27) with SMTP id wB5EbOmc011180; Wed, 5 Dec 2018 06:42:25 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=juniper.net; h=from : to : cc : subject : date : message-id : references : in-reply-to : content-type : content-id : content-transfer-encoding : mime-version; s=PPS1017; bh=V/c5YgLyg84i2C8rhIMZZ9e8WevoCF21IOVAMxw0AOE=; b=X11qmTioB9nRKSydRuraRNpRh7R2DyL+YfPmJwlC2Xi4x/qu6Z/KJmtLR0xCLcAoX5p4 sXzu7EGeHqHNv6pFd3Ku3404BNOQnZCsah7bGvq/IkpW3GV7Dv/g/wdt2jLgmo37RqhH pzw0qC03zg6Ui5woykIIlCyYPT7q09V8bMi0qW8PxY+7kDfuf84ehPtbmDByAikZFXUe U04Y3F/QrUVleA2PinSc2O1JPeuawn+AmUbryUyLL8izxoy5g8WcaQ4SDtxLSd8qFIfM IkeWmBFu0kCxPOKzYMYhw1cfNuERcjdoHoVJq9OXxuz2JqpetPU0YuxWAxx4NEvadfAW CA==
Received: from nam02-sn1-obe.outbound.protection.outlook.com (mail-sn1nam02lp2058.outbound.protection.outlook.com [104.47.36.58]) by mx0a-00273201.pphosted.com with ESMTP id 2p6gkf00dw-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=NOT); Wed, 05 Dec 2018 06:42:24 -0800
Received: from DM5PR0501MB3864.namprd05.prod.outlook.com (10.167.108.27) by DM5PR0501MB3829.namprd05.prod.outlook.com (10.167.108.15) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1404.7; Wed, 5 Dec 2018 14:42:22 +0000
Received: from DM5PR0501MB3864.namprd05.prod.outlook.com ([fe80::5543:1507:165b:1903]) by DM5PR0501MB3864.namprd05.prod.outlook.com ([fe80::5543:1507:165b:1903%2]) with mapi id 15.20.1425.006; Wed, 5 Dec 2018 14:42:22 +0000
From: Eric Rosen <erosen@juniper.net>
To: EXT - randy <randy@psg.com>
CC: "lsvr@ietf.org" <lsvr@ietf.org>
Thread-Topic: [Lsvr] Comments on LSVR with RR peering
Thread-Index: AQHUi9wKWk8mpUn4x068f8Q4VXKv3qVvOIcAgAEBMgA=
Date: Wed, 05 Dec 2018 14:42:22 +0000
Message-ID: <378f54f4-8b92-3859-519b-3539f49b42d6@juniper.net>
References: <2384fdea-b8f9-ea6d-5287-83f39908fcb0@juniper.net> <m2lg54naid.wl-randy@psg.com>
In-Reply-To: <m2lg54naid.wl-randy@psg.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-clientproxiedby: BN6PR17CA0010.namprd17.prod.outlook.com (2603:10b6:404:65::20) To DM5PR0501MB3864.namprd05.prod.outlook.com (2603:10b6:4:7b::27)
x-ms-exchange-messagesentrepresentingtype: 1
x-originating-ip: [66.129.241.13]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; DM5PR0501MB3829; 6:pSmAnqHG57olAWU4/yTVWiH9objVs0OBZaIcnfhcNaXY+FT/5CMTC/xv52YvAf/U/3IUYhIJYCQCCx6p/aiYPGbNsl6pdxIIzKgOBRfSvErQFCg5b+JiSgSuPqnkb75MmqxMl8+v5n4RrPtRabO561A2xgOkaBBrIpIHV47n1svonEYpZon2NN114QRZjmJHExMTKfbq7UXJikZEHhKrwsmoASbDv4ygtTPKTQj48OeQojhVLLV3cB0Vry/68YO5+9oM1vbqy4KElrZBv2WdJR82O8+XsH713XI7C0VzwGvgr4DPSvoVyNhFpwb0A4jMkObMTJySHHJLlCQwEb07kcr4VbWznKfALenyOEcV/35DVO8oeu6fO7xa0dc2jjcfGUPp6ca1a9obF9JcxyT7Gumugr/v9c3d8uM3iFxkNoKFWJ2dJqtfZMU1L90erZ0tBDppGeVpTJIXDdM2N8fsEA==; 5:E+fjB51cQglwgKZ8t+nvXMYjISplpb91nE45FHXR6HnNwd7y5jhJ4CNoj+B2R0zxA+Nh2DZIJF3q7gXNta92/ig6MW3UV/JCD2vbMigOaVx7WaJ1KKqu3v7gMP9h4pXiPXQQaLMxPQyFxXHNgovjmYszvetDkjNZQjFhl+BOB/Q=; 7:ssFuEif/dS0n2hYxCeLbc0+JDzsB+dzZShPL6RJg369NzTXRVjjUbSHrHz/jh9i73JWOW47Czkbf828kYxttuLXFrFS0Cc8kaZfx6/Ar083aVmfu3ZX1KTxEtR6Fh9+vJ18rPy+Vnvz6v8ZX5dDCxg==
x-ms-office365-filtering-correlation-id: c30a9ce8-1d30-46f6-5243-08d65abfdd6f
x-ms-office365-filtering-ht: Tenant
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390098)(7020095)(4652040)(8989299)(5600074)(711020)(4618075)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(2017052603328)(7153060)(7193020); SRVR:DM5PR0501MB3829;
x-ms-traffictypediagnostic: DM5PR0501MB3829:
x-ld-processed: bea78b3c-4cdb-4130-854a-1d193232e5f4,ExtAddr
x-microsoft-antispam-prvs: <DM5PR0501MB3829E121E113E3A7F542A790D4A80@DM5PR0501MB3829.namprd05.prod.outlook.com>
x-ms-exchange-senderadcheck: 1
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(8211001083)(6040522)(2401047)(8121501046)(5005006)(10201501046)(3002001)(93006095)(93001095)(3231455)(999002)(944501520)(52105112)(6055026)(148016)(149066)(150057)(6041310)(201703131423095)(201702281528075)(20161123555045)(201703061421075)(201703061406153)(20161123558120)(20161123562045)(20161123560045)(20161123564045)(201708071742011)(7699051)(76991095); SRVR:DM5PR0501MB3829; BCL:0; PCL:0; RULEID:; SRVR:DM5PR0501MB3829;
x-forefront-prvs: 08770259B4
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(136003)(396003)(366004)(346002)(39860400002)(376002)(199004)(189003)(3846002)(66066001)(6246003)(305945005)(7736002)(68736007)(4326008)(53936002)(5660300001)(106356001)(105586002)(6512007)(6436002)(31686004)(6916009)(36756003)(6486002)(229853002)(25786009)(2906002)(6116002)(14454004)(53546011)(478600001)(8676002)(11346002)(486006)(446003)(2616005)(81156014)(476003)(256004)(97736004)(76176011)(8936002)(102836004)(81166006)(6506007)(386003)(186003)(26005)(99286004)(52116002)(71190400001)(31696002)(71200400001)(86362001)(316002); DIR:OUT; SFP:1102; SCL:1; SRVR:DM5PR0501MB3829; H:DM5PR0501MB3864.namprd05.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:1; MX:1;
received-spf: None (protection.outlook.com: juniper.net does not designate permitted sender hosts)
x-microsoft-antispam-message-info: 3efxh6SQD8i8hBA7oHaK57l+EE2fxRxkAALQrkatYHjcbeZKnKesQLadX4OoW3ZarQKuN6e6KsUYAwxkEDHatoazDO5TrJjPeOgORbEWeE3OR9lMQG1yyySJ84yNPEeUjfEs/q7dZSFK/cgCOvvcNShC3QvuIMf5yFKwySa3lYyhYMPDnFeTU119MyhgTNpDk49qaO6h4M4T/oa759aTfn8ourrm+U5usgReXZLRxFzbNBbDkBLkMprBZ1IHJwnC99/nowyXktmHDib3xLama03TtadSWq2cDZkyV1rleVhsV7ZdVYtjXV4GE4W1uf5uZn2ppx/uis+Nk09b4xqzwTmgv8PLOq8zYfBmbyA8Egs=
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: text/plain; charset="utf-8"
Content-ID: <6A558B2B65E53145B649494B66BA0B65@namprd05.prod.outlook.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-OriginatorOrg: juniper.net
X-MS-Exchange-CrossTenant-Network-Message-Id: c30a9ce8-1d30-46f6-5243-08d65abfdd6f
X-MS-Exchange-CrossTenant-originalarrivaltime: 05 Dec 2018 14:42:22.3319 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: bea78b3c-4cdb-4130-854a-1d193232e5f4
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DM5PR0501MB3829
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:, , definitions=2018-12-05_05:, , signatures=0
X-Proofpoint-Spam-Details: rule=outbound_spam_notspam policy=outbound_spam score=0 priorityscore=1501 malwarescore=0 suspectscore=0 phishscore=0 bulkscore=0 spamscore=0 clxscore=1011 lowpriorityscore=0 mlxscore=0 impostorscore=0 mlxlogscore=698 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1810050000 definitions=main-1812050131
Archived-At: <https://mailarchive.ietf.org/arch/msg/lsvr/i5HjBi-_Be9ktGKfjt7HIcLYZus>
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 14:42:28 -0000

This example is based on Section 2.3 of lsvr-bgp-spf-03 ("BGP Peering in 
Route-Reflector or Controller Topology"), which states:

    "In this model, BGP speakers peer solely with one or more Route 
Reflectors [RFC4456] or controllers."

Thus when BC goes down, B cannot tell A of this fact, it can only tell 
the Route Reflector, and A can only learn of this fact from the Route 
Reflector.

Perhaps I took the statement in Section 2.3 too literally? ;-)

On 12/4/2018 6:21 PM, Randy Bush wrote:
> 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