RFC 6382: Unique Origin Autonomous System Numbers (ASNs) per Node for Globally Anycasted Services
In plain English — editorial summary, not part of the RFC
This document makes recommendations regarding the use of unique origin autonomous system numbers (ASNs) per node for globally anycasted critical infrastructure services in order to provide routing system discriminators for a given anycasted prefix. Network management and monitoring techniques, or other operational mechanisms, may employ this new discriminator in whatever manner best accommodates their operating environment. This memo documents an Internet Best Current Practice.
Document record
- Document ID
- RFC6382
- Published
- October 2011
- Authors
- D. McPherson; R. Donnelly; F. Scalzo
- Status
- BEST CURRENT PRACTICE
- Stream
- IETF
- Area
- ops
- Pages
- 10
- Also known as
- BCP169
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 8207BGPsec Operational ConsiderationsCurrent
September 2017
- RFC 8893Resource Public Key Infrastructure (RPKI) Origin Validation for BGP ExportCurrent
September 2020
- RFC 7353Security Requirements for BGP Path ValidationCurrent
August 2014
- RFC 6198Requirements for the Graceful Shutdown of BGP SessionsCurrent
April 2011
- RFC 8481Clarifications to BGP Origin Validation Based on Resource Public Key Infrastructure (RPKI)Updated
September 2018
- RFC 8482Providing Minimal-Sized Responses to DNS Queries That Have QTYPE=ANYCurrent
January 2019
- RFC 8509A Root Key Trust Anchor Sentinel for DNSSECCurrent
December 2018
- RFC 8767Serving Stale Data to Improve DNS ResiliencyCurrent
March 2020
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?