RFC 8207: BGPsec Operational Considerations

In plain English — editorial summary, not part of the RFC

Deployment of the BGPsec architecture and protocols has many operational considerations. This document attempts to collect and present the most critical and universal. Operational practices are expected to evolve as BGPsec is formalized and initially deployed.

Document record

Document ID

RFC8207

Published

September 2017

Authors

R. Bush

Status

BEST CURRENT PRACTICE

Stream

IETF

Area

rtg

Pages

10

Also known as

BCP211

• Read the full RFC text →
• Plain text version
• IETF Datatracker history
• DOI: 10.17487/RFC8207

Topics

• BGP
• RPKI
• Routing
• Security

Related documents

Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.

• RFC 6382Unique Origin Autonomous System Numbers (ASNs) per Node for Globally Anycasted ServicesCurrent

  October 2011

• RFC 7353Security Requirements for BGP Path ValidationCurrent

  August 2014

• RFC 8893Resource Public Key Infrastructure (RPKI) Origin Validation for BGP ExportCurrent

  September 2020

• RFC 7182Integrity Check Value and Timestamp TLV Definitions for Mobile Ad Hoc Networks (MANETs)Current

  April 2014

• RFC 7128Resource Public Key Infrastructure (RPKI) Router Implementation ReportCurrent

  February 2014

• RFC 6622Integrity Check Value and Timestamp TLV Definitions for Mobile Ad Hoc Networks (MANETs)Obsoleted

  May 2012

• RFC 6483Validation of Route Origination Using the Resource Certificate Public Key Infrastructure (PKI) and Route Origin Authorizations (ROAs)Current

  February 2012

• RFC 6482A Profile for Route Origin Authorizations (ROAs)Obsoleted

  February 2012

Also filed under

• BEST CURRENT PRACTICE
• 2017
• IETF stream
• rtg area
• BCP 211