[Sidrops] Last Call: <draft-ietf-sidrops-rov-no-rr-03.txt> (RPKI-Based Policy Without Route Refresh) to Internet Standard

The IESG <iesg-secretary@ietf.org> Tue, 12 July 2022 16:30 UTC

MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Auto-Submitted: auto-generated
Precedence: bulk
CC: draft-ietf-sidrops-rov-no-rr@ietf.org, morrowc@ops-netman.net, sidrops-chairs@ietf.org, sidrops@ietf.org, warren@kumari.net
Reply-To: last-call@ietf.org
Sender: iesg-secretary@ietf.org
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
Message-ID: <165764343269.5095.10696633702959718883@ietfa.amsl.com>
Date: Tue, 12 Jul 2022 09:30:32 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/sidrops/a9qUiI76JntQZkFC_CRFroWic4E>
Subject: [Sidrops] Last Call: <draft-ietf-sidrops-rov-no-rr-03.txt> (RPKI-Based Policy Without Route Refresh) to Internet Standard

The IESG has received a request from the SIDR Operations WG (sidrops) to
consider the following document: - 'RPKI-Based Policy Without Route Refresh'
  <draft-ietf-sidrops-rov-no-rr-03.txt> as Internet Standard

The IESG plans to make a decision in the next few weeks, and solicits final
comments on this action. Please send substantive comments to the
last-call@ietf.org mailing lists by 2022-08-02. Exceptionally, comments may
be sent to iesg@ietf.org instead. In either case, please retain the beginning
of the Subject line to allow automated sorting.

Abstract


   A BGP Speaker performing RPKI-based policy should not issue Route
   Refresh to its neighbors because it has received new RPKI data.  This
   document updates RFC8481 by describing how to avoid doing so by
   either keeping a full Adj-RIB-In or saving paths dropped due to ROV
   so they may be reevaluated with respect to new RPKI data.





The file can be obtained via
https://datatracker.ietf.org/doc/draft-ietf-sidrops-rov-no-rr/



No IPR declarations have been submitted directly on this I-D.


The document contains these normative downward references.
See RFC 3967 for additional information: 
    rfc7313: Enhanced Route Refresh Capability for BGP-4 (Proposed Standard - Internet Engineering Task Force (IETF))
    rfc4271: A Border Gateway Protocol 4 (BGP-4) (Draft Standard - Internet Engineering Task Force (IETF))

[Sidrops] Last Call: <draft-ietf-sidrops-rov-no-r… The IESG