Re: [Sidrops] rpki rp frequency

Jared Mauch <jared@puck.nether.net> Mon, 13 April 2020 14:25 UTC

Return-Path: <jared@puck.nether.net>
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 45AE73A16BD for <sidrops@ietfa.amsl.com>; Mon, 13 Apr 2020 07:25:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.92
X-Spam-Level:
X-Spam-Status: No, score=-1.92 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, URIBL_BLOCKED=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 RFare2H4tMPj for <sidrops@ietfa.amsl.com>; Mon, 13 Apr 2020 07:25:48 -0700 (PDT)
Received: from puck.nether.net (puck.nether.net [204.42.254.5]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3DA483A16B9 for <sidrops@ietf.org>; Mon, 13 Apr 2020 07:25:48 -0700 (PDT)
Received: from [10.0.0.129] (c-68-49-104-93.hsd1.mi.comcast.net [68.49.104.93]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by puck.nether.net (Postfix) with ESMTPSA id 6F07954014E; Mon, 13 Apr 2020 10:25:46 -0400 (EDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.80.23.2.2\))
From: Jared Mauch <jared@puck.nether.net>
In-Reply-To: <m28siz1nda.wl-randy@psg.com>
Date: Mon, 13 Apr 2020 10:25:45 -0400
Cc: Di Ma <madi@rpstir.net>, SIDR Operations WG <sidrops@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <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>
To: Randy Bush <randy@psg.com>
X-Mailer: Apple Mail (2.3608.80.23.2.2)
Archived-At: <https://mailarchive.ietf.org/arch/msg/sidrops/VBkxO85f0cjs4x0scOSkh9YfJmo>
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 14:25:49 -0000


> On Apr 13, 2020, at 10:17 AM, Randy Bush <randy@psg.com> wrote:
> 
>>>> 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.

- Jared