ALTO extensions for handling Service Functions
draft-lcsr-alto-service-functions-02
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Luis M. Contreras , Sabine Randriamasy , Xufeng Liu | ||
| Last updated | 2023-09-14 (Latest revision 2023-03-13) | ||
| RFC stream | (None) | ||
| Intended RFC status | (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 proposes the usage of ALTO (and its extensions) to provide information about service functions to clients (e.g., external systems) that could consume such information for decisions requiring network information (service composition, traffic steering to service chains, etc).
Authors
Luis M. Contreras
Sabine Randriamasy
Xufeng Liu
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)