ONF/T-API Services vs. IETF/YANG Models and Interfaces
draft-bryskin-teas-yang-ietf-vs-onf-00
| Document | Type |
This is an older version of an Internet-Draft whose latest revision state is "Expired".
Expired & archived
|
|
|---|---|---|---|
| Authors | Igor Bryskin , Xufeng Liu , Vishnu Pavan Beeram , Tarek Saad | ||
| Last updated | 2017-09-14 (Latest revision 2017-03-13) | ||
| 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
This document compares IETF YANG TE (Traffic Engineering) data model and ONF/T-API model.
Authors
Igor Bryskin
Xufeng Liu
Vishnu Pavan Beeram
Tarek Saad
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)