Skip to main content

A YANG Data Model for requesting path computation
draft-ietf-teas-yang-path-computation-18

Document Type Expired Internet-Draft (teas WG)
Expired & archived
Authors Italo Busi , Sergio Belotti , Oscar Gonzalez de Dios , Anurag Sharma , Daniele Ceccarelli
Last updated 2022-11-07 (Latest revision 2022-03-22)
Replaces draft-busibel-teas-yang-path-computation
RFC stream Internet Engineering Task Force (IETF)
Intended RFC status (None)
Formats
Yang Validation 7 errors, 1 warnings
Reviews
Stream WG state WG Document
Revised I-D Needed - Issue raised by WGLC
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. This document defines a YANG data model which contains Remote Procedure Calls (RPCs) to request path computation. This model complements the solution, defined in RFC YYYY, to configure a TE tunnel path in "compute-only" mode. [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
Daniele Ceccarelli

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)