IETF Logo Mail Archive

Re: [Sidrops] [routing-wg] misconceptions about ROV

Randy Bush <randy@psg.com> Wed, 23 February 2022 00:25 UTC

Return-Path: <randy@psg.com>
X-Original-To: sidrops@ietfa.amsl.com
Delivered-To: sidrops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BA1AB3A0A30 for <sidrops@ietfa.amsl.com>; Tue, 22 Feb 2022 16:25:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, 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 hynXYb33yo5O for <sidrops@ietfa.amsl.com>; Tue, 22 Feb 2022 16:25:24 -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 95A3F3A0A2A for <sidrops@ietf.org>; Tue, 22 Feb 2022 16:25:24 -0800 (PST)
Received: from localhost ([127.0.0.1] helo=ryuu.rg.net) by ran.psg.com with esmtp (Exim 4.93) (envelope-from <randy@psg.com>) id 1nMfSz-000Ha8-4a; Wed, 23 Feb 2022 00:25:13 +0000
Date: Tue, 22 Feb 2022 16:25:12 -0800
Message-ID: <m2k0dmmntj.wl-randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Tim Bruijnzeels <tim@nlnetlabs.nl>
Cc: Geoff Huston <gih@apnic.net>, "sidrops@ietf.org" <sidrops@ietf.org>
In-Reply-To: <E16290C1-77ED-4CB1-8712-F6163304ED45@nlnetlabs.nl>
References: <m2h78roqbp.wl-randy@psg.com> <7FBC2063-2404-4BF9-836E-210629C4BA63@juicybun.cn> <m28ru3ofyq.wl-randy@psg.com> <3C18BA8C-FA34-4D24-96E4-F85644089513@nlnetlabs.nl> <015C9C28-4230-40D8-A9F2-7420B726C00F@juicybun.cn> <DF148DA2-C94D-42BF-A37F-668D9B37860B@nlnetlabs.nl> <YhS/WR3czIP3jNLF@snel> <ABE3FA29-6C9D-492B-A72A-68C20176E76D@nlnetlabs.nl> <949277FD-27AF-40E8-B557-AA58C62BFEA7@apnic.net> <E16290C1-77ED-4CB1-8712-F6163304ED45@nlnetlabs.nl>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/26.3 Mule/6.0 (HANACHIRUSATO)
MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue")
Content-Type: text/plain; charset=US-ASCII
Archived-At: <https://mailarchive.ietf.org/arch/msg/sidrops/-KoAzN0XsFS3WBUX4jCEkjGlAIM>
Subject: Re: [Sidrops] [routing-wg] misconceptions about ROV
X-BeenThere: sidrops@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: A list for the SIDR Operations WG <sidrops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sidrops>, <mailto:sidrops-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/sidrops/>
List-Post: <mailto:sidrops@ietf.org>
List-Help: <mailto:sidrops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sidrops>, <mailto:sidrops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 23 Feb 2022 00:25:27 -0000

> BGPSec path validation procedure results in one of two states: 'Valid'
> and 'Not Valid'. (section 5.1 of 8205).
> 
> A BGPSec path as a whole can only be 'Valid' if all signatures are
> present, and they are all valid.
> 
> The absence of any signature, whether it's because the update left a
> capable island, or an adversary removed signatures, results in 'Not
> Valid'.

almost.  there is also NotSigned aka BGP4.

as it leaves an island, it becomes Unsigned.  it can not become signed
at any further hop.

> Rejecting 'Not Valid' is therefore only safe on known islands.
> 
> Outside of these islands all paths are BGPSec 'Not Valid'.

not exactly, they are Unsigned

randy

v2.8.7 | Report a Bug | By Email