Requirements of Interior Gateway Protocol (IGP) for Central Control
draft-li-rtgwg-igp-cc-reqs-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Zhenbin Li , Huaimo Chen | ||
| Last updated | 2015-01-05 (Latest revision 2014-07-04) | ||
| 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
Interior Gateway Protocol(IGP) such as IS-IS or OSPF is a fundamental building block for traditional routing system which is based on distributed computation model. Routing in networks based on centralized computation model such as Software Defined Network(SDN) may require special IGP extension to facilitate its operation in multi-domain, multi-region, or multi-layer networks. This document introduces an architecture of deploying IGP for central-controlled network, but it does not aim to provide a detailed description of all the architectural components. It also specifies a set of functional requirements which can be fulfilled by IGP with proper extension for the central-controlled network.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)