IETF Logo Mail Archive

Re: [Sidrops] [WGLC] draft-ietf-sidrops-roa-considerations-01 - Ends 10/March/2022

Randy Bush <randy@psg.com> Thu, 10 March 2022 11:41 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 37D403A0C02 for <sidrops@ietfa.amsl.com>; Thu, 10 Mar 2022 03:41:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.91
X-Spam-Level:
X-Spam-Status: No, score=-6.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01] 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 30Ns04afCyaH for <sidrops@ietfa.amsl.com>; Thu, 10 Mar 2022 03:41:22 -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 03D813A0B8F for <sidrops@ietf.org>; Thu, 10 Mar 2022 03:41:21 -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 1nSHAS-0003jp-Fg; Thu, 10 Mar 2022 11:41:16 +0000
Date: Thu, 10 Mar 2022 03:41:15 -0800
Message-ID: <m2v8wm8278.wl-randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Ties de Kock <tdekock@ripe.net>
Cc: Tim Bruijnzeels <tim@nlnetlabs.nl>, "sidrops@ietf.org" <sidrops@ietf.org>
In-Reply-To: <D46FDA88-15E2-4EC6-BE07-0A1A93038B64@ripe.net>
References: <BYAPR18MB26961DE9F15501CCA12ECCF1C13D9@BYAPR18MB2696.namprd18.prod.outlook.com> <851649A5-9075-4956-8B57-E51F612DF6BD@nlnetlabs.nl> <m235jqa2fk.wl-randy@psg.com> <D46FDA88-15E2-4EC6-BE07-0A1A93038B64@ripe.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/j36lU7Pa9FWuzdx-wh34IKU98cc>
Subject: Re: [Sidrops] [WGLC] draft-ietf-sidrops-roa-considerations-01 - Ends 10/March/2022
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: Thu, 10 Mar 2022 11:41:23 -0000

maybe i just don't get it.

the CA, in some thought of saving bandwidth or something, packs data
up into AS-based blobs which the RPs are then supposed to unpack and
reconcile.  where's the win that is worth all that work?

and i do not see the RPKI data as having epochs, times when it is
stable.  times when there is a complete snapshot of the data.  data
are being added and removed asynchronously in the distributed tree
cross the net topology.  like bgp, it does not converge to a stable
point; it is constantly in motion.

randy

v2.23.0 | Report a Bug | By Email