RFC 7705: Autonomous System Migration Mechanisms and Their Effects on the BGP AS_PATH Attribute
In plain English — editorial summary, not part of the RFC
This document discusses some existing commonly used BGP mechanisms for Autonomous System Number (ASN) migration that are not formally part of the BGP4 protocol specification. It is necessary to document these de facto standards to ensure that they are properly supported in future BGP protocol work.
Document record
- Document ID
- RFC7705
- Published
- November 2015
- Authors
- W. George; S. Amante
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rtg
- Pages
- 16
- Also known as
- —
- Updates:
- RFC 4271
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 8538Notification Message Support for BGP Graceful RestartCurrent
March 2019
- RFC 9072Extended Optional Parameters Length for BGP OPEN MessageCurrent
July 2021
- RFC 5575Dissemination of Flow Specification RulesObsoleted
August 2009
- RFC 5492Capabilities Advertisement with BGP-4Updated
February 2009
- RFC 7854BGP Monitoring Protocol (BMP)Updated
June 2016
- RFC 9736The BGP Monitoring Protocol (BMP) Peer Up Message NamespaceCurrent
March 2025
- RFC 9972Advanced BGP Monitoring Protocol (BMP) Statistics TypesCurrent
May 2026
- RFC 7674Clarification of the Flowspec Redirect Extended CommunityObsoleted
October 2015
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?