Deprecated AS_SET: Why the IETF changed the rules of BGP aggregation.
For over three decades, BGP’s AS_SET path segment has been a legal, if problematic, feature of Internet routing. In May 2025, the IETF formally ended that era. RFC 9774 doesn’t merely discourage AS_SET: it prohibits it entirely.
This post unpacks what AS_SET is, why it was created, what went wrong, and what network operators need to do now that the IETF has made its deprecation a binding standard requirement.
Background: What is the AS_PATH attribute?
Every BGP UPDATE message carries an AS_PATHattribute – a record of the Autonomous Systems a route advertisement has traversed on its way from origin to destination. It serves two critical functions: loop prevention (a router seeing its own AS in the path discards the route) and policy (operators use AS_PATH to make routing decisions based on where traffic comes from or how it’s being forwarded.
The AS_PATH is composed of path segments, each of which is one of four types:
| Type | Description | Status |
|---|---|---|
| AS_SEQUENCE | An ordered list of ASes the route has passed through. The most common and well-understood type. | Valid |
| AS_SET | An unordered set of ASes created during route aggregation. Now deprecated. | Deprecated |
| AS_CONFED_SEQUENCE | Ordered list of Member AS Numbers within a Continue reading |
