Multi-domain Service Function Chaining with ALTO
draft-lachos-multi-domain-sfc-alto-00
| Document | Type |
This is an older version of an Internet-Draft whose latest revision state is "Replaced".
Expired & archived
|
|
|---|---|---|---|
| Authors | Danny Alex Lachos Perez , Qiao Xiang , Christian Esteve Rothenberg , Y. Richard Yang | ||
| Last updated | 2019-01-03 (Latest revision 2018-07-02) | ||
| Replaced by | draft-lachos-sfc-multi-domain-alto | ||
| 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
Currently, Service Function Chaining (SFC) that span domains with different technology, administration or ownership are being defined by the SFC WG. This document focuses on how the Application Layer Traffic Optimization (ALTO) protocol can be used to advertise and discover abstract topology, resource and service information from different domains, and then compute inter-domain service function paths. Another important concern of this draft is to initiate a discussion (ALTO, SFC as well as other WGs) regarding if, how, and under what conditions ALTO can be useful to improve the multi-domain SFC process.
Authors
Danny Alex Lachos Perez
Qiao Xiang
Christian Esteve Rothenberg
Y. Richard Yang
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)