Re: [Sidrops] rpki rp frequency

Randy Bush <randy@psg.com> Mon, 13 April 2020 17:31 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 F41C53A1000 for <sidrops@ietfa.amsl.com>; Mon, 13 Apr 2020 10:31:00 -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 Op_jUH2kjWiH for <sidrops@ietfa.amsl.com>; Mon, 13 Apr 2020 10:30:59 -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 D16763A0FFE for <sidrops@ietf.org>; Mon, 13 Apr 2020 10:30:59 -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 1jO2vA-0001fz-B0; Mon, 13 Apr 2020 17:30:56 +0000
Date: Mon, 13 Apr 2020 10:30:55 -0700
Message-ID: <m27dyj1eeo.wl-randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Jared Mauch <jared@puck.nether.net>
Cc: SIDR Operations WG <sidrops@ietf.org>, Di Ma <madi@rpstir.net>
In-Reply-To: <AAEAD739-8F96-418B-8F76-64A1FDD167ED@puck.nether.net>
References: <m2d08d3i2a.wl-randy@psg.com> <20B9DFE3-73E5-48D6-B8F0-7F401EBA9E19@rpstir.net> <m2v9m41rp8.wl-randy@psg.com> <AF8CA9B7-5266-4172-B023-F77E612A0E9F@rpstir.net> <m28siz1nda.wl-randy@psg.com> <AAEAD739-8F96-418B-8F76-64A1FDD167ED@puck.nether.net>
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/1mQuOaaI9OVzIT-ctvfGobmwDkI>
Subject: Re: [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: Mon, 13 Apr 2020 17:31:01 -0000

>>>>> As often as necessary that the RP can synchronize with a repository.
>>>> how often is 'necessary?'  in units of time, please.
>>> I think It is the ISP who defines what is necessary.
>> what is reasonable for the good of routing in the internet?  i suggest
>> an hour.
>> before notify, we tolerated dns propagation of a day, and it was very
>> painful.  that seems primitive and silly now.
> Most of the IRRs are mirroring at an interval of 5 minutes or so these
> days, or that was one of the last things I asked to be changed at 2914
> before I left to ensure regular sync.
> I think 300s is reasonable, but 3600 (60 min) is likely the high limit.

there are the questions of how frequently a CA publishes, how often an
RP pulls, and how often routers pull from their RP(s).

for CA publishing, a few seconds seems easily achieved with reasonable
software.

for RPs pulling, 600s may be optimistic in the short term given
  o the load it will put on publication services
  o and one notorious repo which is against spec
but it should be achievable in a while.  an hour would be the longest
acceptable in my mind today.

for the router(s) pulling from the RP(s), 300-3600s is a wide window.
but remember, the rpki-rtr protocol does have the equivalent of dns
notify, where the cache tells the router that it has some nice tasty
new data.  you're welcome :)

i imagine that few here are old enough to remember when curtis only
updated the backbone (there was only one) routing peering once a week
on wednesday.

if we want the internet to rely on this stuff, it's time to get into the
21st century.

randy