Re: [Sidrops] what to do when the CRL is hosed?

Randy Bush <randy@psg.com> Thu, 02 April 2020 21:32 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 EFD973A1A36 for <sidrops@ietfa.amsl.com>; Thu, 2 Apr 2020 14:32:09 -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 BK-j_Xfy4Mbn for <sidrops@ietfa.amsl.com>; Thu, 2 Apr 2020 14:32:08 -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 AE24B3A1A34 for <sidrops@ietf.org>; Thu, 2 Apr 2020 14:32:08 -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 1jK7RW-0000zr-70; Thu, 02 Apr 2020 21:32:06 +0000
Date: Thu, 02 Apr 2020 14:32:05 -0700
Message-ID: <m2y2rdo9pm.wl-randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Jay Borkenhagen <jayb@braeburn.org>
Cc: SIDR Operations WG <sidrops@ietf.org>
In-Reply-To: <24198.20355.168888.506246@oz.mt.att.com>
References: <20200224151532.GD19221@vurt.meerval.net> <20200224211531.GB60925@vurt.meerval.net> <20200225090338.10464b1a@glaurung.nlnetlabs.nl> <9cc3a6a5-f9c8-23df-588e-48dee5db62d4@verizon.net> <3B7006DE-5366-47E7-9CD6-AF392F9ED0CC@nlnetlabs.nl> <6602d1a7-ecbf-73a0-21d8-1254fb2aff97@verizon.net> <20200226173935.GE72144@vurt.meerval.net> <2db8d19a-6f91-d2fc-36c3-65742ba77e6c@ripe.net> <8B09B96B-432C-4190-9DE0-DC2004AAFCC2@nlnetlabs.nl> <CC64461D-4F34-4367-AD9D-D42B2A476363@ripe.net> <75140927-0b8b-07ab-ad2e-952e32256df1@verizon.net> <24198.20355.168888.506246@oz.mt.att.com>
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/xIYkJKePpJD6BV2kuracFwiuW0U>
Subject: Re: [Sidrops] what to do when the CRL is hosed?
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, 02 Apr 2020 21:32:10 -0000

credit where due department:

> As a network operator, yes, I expect to have the flexibility of
> configuring my network using local policy.  But in the context of the
> RPKI, we need to reach a point where all RFC-compliant RPs will
> generate identical sets of VRPs when presented with the same input.
> There will be reasons why I may prefer to operate one RP over another,
> but the VRPs that a particular RP generates should never be one of
> them.
> 
> No network operators want to specify any 'local policy' on their RP
> instances to control under which conditions an RPKI object would be
> accepted.  Some network operators in this WG have voiced strong
> opinions about how such acceptance should be decided, but that's not
> because they want the ability to exert local policy there.  Such
> opinions are all toward the goal we share of all implementations
> reliably creating a correct/consistent VRP set.

you have been testing RP compliance to this for a good number of years,
and having quiet chats with RP implementors.  this has really helped and
is much appreciated.

randy