A YANG Data Model for requesting path computation
draft-ietf-teas-yang-path-computation-21
| Document | Type |
This is an older version of an Internet-Draft whose latest revision state is "Active".
Expired & archived
|
|
|---|---|---|---|
| Authors | Italo Busi , Sergio Belotti , Oscar Gonzalez de Dios , Anurag Sharma , Yan Shi | ||
| Last updated | 2024-01-08 (Latest revision 2023-07-07) | ||
| Replaces | draft-busibel-teas-yang-path-computation | ||
| RFC stream | Internet Engineering Task Force (IETF) | ||
| Formats | |||
| Reviews | |||
| Additional resources | Mailing list discussion | ||
| Stream | WG state | WG Document | |
| Associated WG milestone |
|
||
| Document shepherd | Vishnu Pavan Beeram | ||
| IESG | IESG state | Expired | |
| Consensus boilerplate | Unknown | ||
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | vishnupavan@gmail.com |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
There are scenarios, typically in a hierarchical Software-Defined Networking (SDN) context, where the topology information provided by a Traffic Engineering (TE) network provider may be insufficient for its client to perform multi-domain path computation. In these cases the client would need to request the TE network provider to compute some intra-domain paths to be used by the client to choose the optimal multi-domain paths. This document provides a mechanism to request path computation by augmenting the Remote Procedure Calls (RPCs) defined in RFC YYYY. [RFC EDITOR NOTE: Please replace RFC YYYY with the RFC number of draft-ietf-teas-yang-te once it has been published. Moreover, this document describes some use cases where the path computation request, via YANG-based protocols (e.g., NETCONF or RESTCONF), can be needed.
Authors
Italo Busi
Sergio Belotti
Oscar Gonzalez de Dios
Anurag Sharma
Yan Shi
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)