Using Operator-defined TLVs for Agile Service Deployment
draft-chunduri-ospf-operator-defined-tlvs-01
| Document | Type |
This is an older version of an Internet-Draft whose latest revision state is "Expired".
Expired & archived
|
|
|---|---|---|---|
| Authors | Uma Chunduri , Xiaohu Xu , Luis M. Contreras , Mohamed Boucadair , Luay Jalil | ||
| Last updated | 2016-01-03 (Latest revision 2015-07-02) | ||
| Replaces | draft-chunduri-ospf-self-defined-sub-tlvs | ||
| RFC stream | (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
This document proposes a TLV within the body of the OSPF Router Information (RI) Opaque LSA, called Operator-defined Sub-TLV Container TLV. Here the term OSPF means both OSPFv2 and OSPFv3.This attribute is meant to accommodate policy-based and deployment- specific use cases.
Authors
Uma Chunduri
Xiaohu Xu
Luis M. Contreras
Mohamed Boucadair
Luay Jalil
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)