RFC 8206: BGPsec Considerations for Autonomous System (AS) Migration
In plain English — editorial summary, not part of the RFC
This document discusses considerations and methods for supporting and securing a common method for Autonomous System (AS) migration within the BGPsec protocol.
Document record
- Document ID
- RFC8206
- Published
- September 2017
- Authors
- W. George; S. Murphy
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rtg
- Pages
- 16
- Also known as
- —
- Updates:
- RFC 8205
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 7705Autonomous System Migration Mechanisms and Their Effects on the BGP AS_PATH AttributeCurrent
November 2015
- RFC 7132Threat Model for BGP Path SecurityCurrent
February 2014
- RFC 8181A Publication Protocol for the Resource Public Key Infrastructure (RPKI)Current
July 2017
- RFC 8416Simplified Local Internet Number Resource Management with the RPKI (SLURM)Current
August 2018
- RFC 7607Codification of AS 0 ProcessingCurrent
August 2015
- RFC 7353Security Requirements for BGP Path ValidationCurrent
August 2014
- RFC 6916Algorithm Agility Procedure for the Resource Public Key Infrastructure (RPKI)Current
April 2013
- RFC 6811BGP Prefix Origin ValidationUpdated
January 2013
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?