Using Operator-defined TLVs for Agile Service Deployment
draft-chunduri-ospf-operator-defined-tlvs-02

Document Type Expired Internet-Draft (individual)
Last updated 2016-07-21 (latest revision 2016-01-06)
Replaces draft-chunduri-ospf-self-defined-sub-tlvs
Stream (None)
Intended RFC status (None)
Formats
Expired & archived
pdf htmlized (tools) htmlized bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Expired
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at
https://www.ietf.org/archive/id/draft-chunduri-ospf-operator-defined-tlvs-02.txt

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 (uma.chunduri@ericsson.com)
Xiaohu Xu (xuxiaohu@huawei.com)
Luis Contreras (luismiguel.contrerasmurillo@telefonica.com)
Mohamed Boucadair (mohamed.boucadair@orange.com)
Luay Jalil (luay.jalil@verizon.com)

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