OSPF Traffic Engineering capability TLVs
draft-vasseur-mpls-ospf-te-cap-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | JP Vasseur , Peter Psenak | ||
| Last updated | 2002-10-28 | ||
| 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
This draft proposes OSPF traffic engineering capability TLVs. Two capability TLVs are defined in the current draft: the Path Computation Server Discovery (PCSD) TLV that allows a router to announce its Path Computation Server capability to other LSRs within an OSPF area or a routing domain and the Mesh-group TLV used by an LSR to indicate its desire to participate to a mesh of Traffic Engineering Label Switched Path (this mesh of TE LSPs is identified by a mesh-group number). They are both used in the context of MPLS Traffic Engineering. Additional OSPF TE capability TLVs may be added in further revision of this draft. Those OSPF TE capability TLVs will be carried within the OSPF router information LSA (opaque type of 4, opaque ID of 0) defined in [18].
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)