IETF Network Slice Topology YANG Data Model
draft-liu-teas-transport-network-slice-yang-07
Document | Type |
This is an older version of an Internet-Draft whose latest revision state is "Active".
Expired & archived
|
|
---|---|---|---|
Authors | Xufeng Liu , Jeff Tantsura , Igor Bryskin , Luis M. Contreras , Qin Wu , Sergio Belotti , Reza Rokui , Aihua Guo , Italo Busi | ||
Last updated | 2024-01-08 (Latest revision 2023-07-07) | ||
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
An IETF network slice may use a customized topology to describe intended resource reservation for connectivities between slice endpoints. Customized topologies enable customers to request shared resources among connections activated on demand and to customize the service paths in a network slice with an extensive level of control. This document describes a YANG data model for managing and controlling customized topologies for IETF network slices defined in RFC YYYY. [RFC EDITOR NOTE: Please replace RFC YYYY with the RFC number of draft-ietf-teas-ietf-network-slices once it has been published.
Authors
Xufeng Liu
Jeff Tantsura
Igor Bryskin
Luis M. Contreras
Qin Wu
Sergio Belotti
Reza Rokui
Aihua Guo
Italo Busi
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)