LISP Traffic Engineering Use-Cases
draft-ietf-lisp-te-00
| Document | Type |
This is an older version of an Internet-Draft whose latest revision state is "Active".
Expired & archived
|
|
|---|---|---|---|
| Authors | Dino Farinacci , Michael Kowal , Parantap Lahiri | ||
| Last updated | 2017-10-30 (Latest revision 2017-04-28) | ||
| Replaces | draft-farinacci-lisp-te | ||
| RFC stream | Internet Engineering Task Force (IETF) | ||
| Formats | |||
| Additional resources | Mailing list discussion | ||
| Stream | WG state | WG Document | |
| Document shepherd | (None) | ||
| IESG | IESG state | Expired | |
| Consensus boilerplate | Unknown | ||
| 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 describes how LISP reencapsulating tunnels can be used for Traffic Engineering purposes. The mechanisms described in this document require no LISP protocol changes but do introduce a new locator (RLOC) encoding. The Traffic Engineering features provided by these LISP mechanisms can span intra-domain, inter-domain, or combination of both.
Authors
Dino Farinacci
Michael Kowal
Parantap Lahiri
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)