Re: [Sidrops] I-D Action: draft-ietf-sidrops-rov-no-rr-01.txt

Randy Bush <randy@psg.com> Wed, 11 May 2022 17:39 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 1C9AFC157B5A for <sidrops@ietfa.amsl.com>; Wed, 11 May 2022 10:39:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Db9lqss2PUqh for <sidrops@ietfa.amsl.com>; Wed, 11 May 2022 10:39:45 -0700 (PDT)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:8006::18]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8EE79C14F726 for <sidrops@ietf.org>; Wed, 11 May 2022 10:39:45 -0700 (PDT)
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 1noqJH-000OQi-HD; Wed, 11 May 2022 17:39:39 +0000
Date: Wed, 11 May 2022 10:39:38 -0700
Message-ID: <m2zgjoj7dx.wl-randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Ties de Kock <tdekock@ripe.net>
Cc: sidrops@ietf.org
In-Reply-To: <B2602263-BBC1-4ED0-BD35-F9E5A90B74EF@ripe.net>
References: <165187444339.21170.13445821749382495729@ietfa.amsl.com> <m2fslmnwqd.wl-randy@psg.com> <B2602263-BBC1-4ED0-BD35-F9E5A90B74EF@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/IyFJLDnv3_RTUE6clJazHUCo8-4>
Subject: Re: [Sidrops] I-D Action: draft-ietf-sidrops-rov-no-rr-01.txt
X-BeenThere: sidrops@ietf.org
X-Mailman-Version: 2.1.34
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: Wed, 11 May 2022 17:39:50 -0000

>>   If new RPKI data arrive which invalidate the best path, and the
>>   router did not keep all alternatives, then it MUST issue a route
>>   refresh so those alternatives may be evaluated for best path.
> 
> Just to make sure this is the intended behaviour: When new RPKI data
> arrives that transitions a 'better' route that was invalid to unknown
> or valid, the router will stick to the old preferred route.

i don't think the above was talking about that.  the paragraph above
that in the draft says

   When RPKI data cause one or more paths to be dropped due to ROV,
   those paths MUST NOT be evaluated for best path, but MUST be saved
   (either separately or marked) so they may be reevaluated with respect
   to new RPKI data.

> It only switches when the best path is invalidated.

no.  it'll switch if a ROA comes in which validates a previously
invalidated path, and that path competes successfully with the current
best path.

> Can we simulate or estimate the impact of the specification in section
> 4?

could be a fun measurement project.  but the IMC 2022 dreadline is now,
and we're kinda focused on that.  gladly collaborate with someone on
this new measurement starting in a week+.

randy