[Sidrops] rpki rp frequency

Randy Bush <randy@psg.com> Sat, 11 April 2020 20:04 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 94FBC3A18B4 for <sidrops@ietfa.amsl.com>; Sat, 11 Apr 2020 13:04:33 -0700 (PDT)
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 QsnSJpN4Hl2T for <sidrops@ietfa.amsl.com>; Sat, 11 Apr 2020 13:04:32 -0700 (PDT)
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 2DC373A18B2 for <sidrops@ietf.org>; Sat, 11 Apr 2020 13:04:32 -0700 (PDT)
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 1jNMMg-0004Gd-9L for sidrops@ietf.org; Sat, 11 Apr 2020 20:04:30 +0000
Date: Sat, 11 Apr 2020 13:04:29 -0700
Message-ID: <m2d08d3i2a.wl-randy@psg.com>
From: Randy Bush <randy@psg.com>
To: SIDR Operations WG <sidrops@ietf.org>
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/19DAnBg-FirMjizpbqrG7zoVSIU>
Subject: [Sidrops] rpki rp frequency
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: Sat, 11 Apr 2020 20:04:34 -0000

how often do RPs fetch?  how often to routers fetch from RPs?

an experiment announces 147.28.241.0/24 constantly from 47065

a CA has a ROA for { 147.28.241.0/24 47065 } from 12:00 to 04:00 UCT and
for some other, non-announcing i.e. incorrect, AS from 04:00 to 12:00.

it's 19:50 UTC, and a seattle router shows

    r0.sea#sh ip bg rpki table | i ^147.28.241
    147.28.241.0/24      24      47065      0       147.28.0.30/323

i.e. it sees the ROA for the announcing prefix

but the received bgp route to 147.28.241.0/24 is does not reach that
router maybe because transits dropped as invalid?  2914 is the upstream
for that router.

but rv shows

    route-views>show ip bgp 147.28.241.0/24
    BGP routing table entry for 147.28.241.0/24, version 523202351
    Paths: (12 available, best #12, table default)
      Not advertised to any peer
      Refresh Epoch 2
      3303 47065
	217.192.89.50 from 217.192.89.50 (138.187.128.158)
	  Origin IGP, localpref 100, valid, external
	  Community: 3303:1004 3303:1006 3303:1030 3303:3051 47065:332
	  path 7F57D930ED10 RPKI State valid
	  rx pathid: 0, tx pathid: 0

and more.  but with no paths through 2914.

how do we diagnose such things?

randy