I2RS MPLS LSPs Use Case
draft-li-i2rs-mpls-lsps-use-case-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Li Xin , Rongbo Zhang , Ke Li , Shanzhi Chen | ||
| Last updated | 2015-05-18 (Latest revision 2014-11-14) | ||
| 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
The Label-switched paths (LSPs) play fundument role in MPLS domain. Traditionally Label-switched paths (LSPs) are established by the network operator via CLI, SNMP or NETCONF for a variety of purposes, such as to create network-based IP virtual private networks or to route traffic along specified paths through the network. Interface to the Routing System's (I2RS) Programmatic interfaces provides an alternate way to create and maintain the LSPs.This document describes requirement and use case for which I2RS can be used for LSPs management.
Authors
Li Xin
Rongbo Zhang
Ke Li
Shanzhi Chen
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)