RFC 7607: Codification of AS 0 Processing
In plain English — editorial summary, not part of the RFC
This document updates RFC 4271 and proscribes the use of Autonomous System (AS) 0 in the Border Gateway Protocol (BGP) OPEN, AS_PATH, AS4_PATH, AGGREGATOR, and AS4_AGGREGATOR attributes in the BGP UPDATE message.
Document record
- Document ID
- RFC7607
- Published
- August 2015
- Authors
- W. Kumari; R. Bush; H. Schiller; K. Patel
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rtg
- Pages
- 5
- Also known as
- —
- Updates:
- RFC 4271
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 7353Security Requirements for BGP Path ValidationCurrent
August 2014
- RFC 7606Revised Error Handling for BGP UPDATE MessagesCurrent
August 2015
- RFC 7611BGP ACCEPT_OWN Community AttributeCurrent
August 2015
- RFC 7674Clarification of the Flowspec Redirect Extended CommunityObsoleted
October 2015
- RFC 7705Autonomous System Migration Mechanisms and Their Effects on the BGP AS_PATH AttributeCurrent
November 2015
- RFC 7752North-Bound Distribution of Link-State and Traffic Engineering (TE) Information Using BGPObsoleted
March 2016
- RFC 7899Multicast VPN State DampingCurrent
June 2016
- RFC 7938Use of BGP for Routing in Large-Scale Data CentersCurrent
August 2016
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?