BGP SR Policy Extensions for template
draft-zhang-idr-sr-policy-template-01
| Document | Type |
This is an older version of an Internet-Draft whose latest revision state is "Expired".
Expired & archived
|
|
|---|---|---|---|
| Authors | KaZhang , Zhibo Hu, Jie Dong | ||
| Last updated | 2022-11-07 (Latest revision 2022-04-27) | ||
| 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
Segment Routing(SR) Policies can be advertised using BGP. An SR Policy may has lots of constraints, and as the application and features evolve, the SR Policy may need have more and more attribute constraints. To avoid modifying BGP when constraints are added to an SR Policy, we can define a template. The identifier and content of the template are defined by the receiver of the SR Policy. The advertiser of an SR policy only needs to know the ID of the template. When advertising SR policy, the advertiser carries the template ID in the tunnel encapsulation information of the SR policy. After receiving the SR Policy information, the receiver obtains the corresponding template and content according to the template ID, thereby obtaining abundant constraint configuration information.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)