Skip to main content

I2RS Use Cases for Control of Forwarding Path by Central Control Network Element (CCNE)
draft-ji-i2rs-usecases-ccne-service-02

Document Type Expired Internet-Draft (individual)
Expired & archived
Authors Xiaofeng Ji, Shunwan Zhuang , Tieying Huang, Susan Hares
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

As networks expand bridging access, Data Center, and WAN, more networks have a central control point for the network elements in one administrative domain. This document defines that network device as central control network element (CCNE). The CCNE can be RR Router, PCE Server, or a federation of RR Router and PCE Server, or other devices. This document describes use cases where the CCNE can utilize both these the traditional functions and the programmatic Interface to Routing System (I2RS) to communicate with devices in the network. The I2RS use cases described in this document encompass: Control IP Network by RR Router, Control MPLS TE Network by PCE Server. The goal of this document is to increase the community's understanding of how CCNE extensions fit within the overall I2RS architecture. It is intended to provide a basis for the solutions draft describing the set of interfaces for the CCNE device.

Authors

Xiaofeng Ji
Shunwan Zhuang
Tieying Huang
Susan Hares

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)