Bicone Source Address Validation
draft-qin-savnet-bicone-sav-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Lancheng Qin , Dan Li , Li Chen , Libin Liu | ||
| Last updated | 2026-07-02 (Latest revision 2025-12-29) | ||
| Replaces | draft-li-sidrops-bicone-sav | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
Source address validation (SAV) aims to avoid improper blocking of legitimate traffic while maintaining directionality. Existing SAV mechanisms commonly rely on ingress allowlist filters on interfaces facing customer or lateral peer Autonomous Systems (ASes), which can result in improper blocking when the allowlist is incomplete. This document analyzes this issue and describes an alternative ingress SAV approach based on a blocklist of prefixes exclusively associated with the provider cone. Network operators may select either approach based on their operational context.
Authors
Lancheng Qin
Dan Li
Li Chen
Libin Liu
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)