Guidance to Avoid Carrying RPKI Validation States in BGP Path Attributes
draft-ietf-sidrops-avoid-rpki-state-in-bgp-12

Approval announcement
Draft of message to be sent after approval:

Announcement

From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Cc: The IESG <iesg@ietf.org>, draft-ietf-sidrops-avoid-rpki-state-in-bgp@ietf.org, ggx@gigix.net, mohamed.boucadair@orange.com, rfc-editor@rfc-editor.org, sidrops-chairs@ietf.org, sidrops@ietf.org
Subject: Protocol Action: 'Guidance to Avoid Carrying RPKI Validation States in BGP Path Attributes' to Best Current Practice (draft-ietf-sidrops-avoid-rpki-state-in-bgp-11.txt)

The IESG has approved the following document:
- 'Guidance to Avoid Carrying RPKI Validation States in BGP Path
   Attributes'
  (draft-ietf-sidrops-avoid-rpki-state-in-bgp-11.txt) as Best Current Practice

This document is the product of the SIDR Operations Working Group.

The IESG contact persons are Mahesh Jethanandani and Mohamed Boucadair.

A URL of this Internet-Draft is:
https://datatracker.ietf.org/doc/draft-ietf-sidrops-avoid-rpki-state-in-bgp/

Ballot Text

Technical Summary

   This document provides guidance to avoid carrying Resource Public Key
   Infrastructure (RPKI) derived validation states in Border Gateway
   Protocol (BGP) Path Attributes whose change triggers a BGP UPDATE
   being sent across external BGP (EBGP) sessions.  Annotating routes
   with BGP Path Attributes carried across EBGP sessions signaling
   validation states may cause needless flooding of BGP UPDATE messages
   through the global Internet routing system, for example when Route
   Origin Authorizations (ROAs) are issued, or are revoked, or when
   RPKI-To-Router sessions are terminated.

   Operators should ensure RPKI-derived validation states are not
   signaled in BGP Path Attributes whose change triggers a BGP UPDATE
   being sent across EBGP sessions.  Specifically, operators should not
   associate Prefix Origin Validation state with BGP routes using any
   form of BGP Communities carried across EBGP session.

Working Group Summary & Document Quality

    Working Group Last Call has shown a broad support for this
    document. 
    Refer to https://datatracker.ietf.org/doc/draft-ietf-sidrops-avoid-rpki-state-in-bgp/shepherdwriteup/
    for more details.
   
Personnel

   The Document Shepherd for this document is Luigi Iannone.
   The Responsible Area Director is Mohamed Boucadair.

RFC Editor Note