Signaling SAVNET Capability Using IGP
draft-cheng-lsr-adv-savnet-capbility-01
| Document | Type | This is an older version of an Internet-Draft whose latest revision state is "Active". Expired & archived | |
|---|---|---|---|
| Authors | Weiqiang Cheng , Changwang Lin , Shengnan Yue | ||
| Last updated | 2025-08-19 (Latest revision 2025-02-15) | ||
| RFC stream | (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
Existing intra-domain SAV solutions (e.g., BCP38 [RFC2827] and BCP84 [RFC3704]) have problems of high operational overhead or inaccurate validation (see [I-D.ietf-savnet-intra-domain-problem-statement]). To address these problems and guide the design of new intra-domain SAV solutions,[I-D.ietf-savnet-intra-domain-architecture] proposes the architecture of intra-domain SAVNET and introduces the use of SAV-specific information in intra-domain networks. This document defines a mechanism to signal the SAVNET capablity and the source prefix using IGP and BGP-LS.
Authors
Weiqiang Cheng
Changwang Lin
Shengnan Yue
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)