Use Cases for an Interface to LDP Protocol
draft-chen-i2rs-mpls-ldp-usecases-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Xia Chen , Zhenbin Li | ||
| Last updated | 2014-04-23 (Latest revision 2013-10-20) | ||
| 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 Distribution Protocol (LDP) [RFC5036] is a protocol defined for distributing labels in MPLS domain. Traditionally LDP protocol may be managed via CLI, SNMP or NETCONF. Interface to the Routing System's (I2RS) Programmatic interfaces, as defined in [I-D.ward-i2rs-framework], provides an alternate way to control the configuration and diagnose the operation of the LDP protocol. This document describes requirement and use cases for which I2RS can be used for LDP protocol.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)