Terminology and Models for Control of Traffic Engineered Networks with Client-Server Relationship
draft-dios-ccamp-control-models-customer-provider-01
Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
---|---|---|---|
Authors | Oscar Gonzalez de Dios , Julien Meuric , Daniele Ceccarelli | ||
Last updated | 2015-01-22 (Latest revision 2014-07-21) | ||
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
Different kinds of relationships can be established among interconnected Traffic Engineered Networks. In particular, this document focuses on the case where there is a client-server relation between the network domains. The domain interconnection is a policy and administrative boundary. This informational document collects current terminology and provides a taxonomy for the posible control plane based operation models. Each control model defines, on the one hand, the level of information that the domain acting as client receives by control plane means from the domain acting as server and, on the other hand, the control model will determine what can be requested from the client domain to the server domain.
Authors
Oscar Gonzalez de Dios
Julien Meuric
Daniele Ceccarelli
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)