LISP Traffic Engineering Use-Cases
draft-farinacci-lisp-te-12
Document | Type |
Replaced Internet-Draft
(lisp WG)
Expired & archived
|
|
---|---|---|---|
Authors | Dino Farinacci , Michael Kowal , Parantap Lahiri | ||
Last updated | 2017-04-28 (Latest revision 2017-02-28) | ||
Replaced by | draft-ietf-lisp-te | ||
RFC stream | Internet Engineering Task Force (IETF) | ||
Intended RFC status | (None) | ||
Formats | |||
Yang Validation | ☯ 0 errors, 0 warnings | ||
Additional resources | Mailing list discussion | ||
Stream | WG state | Adopted by a WG | |
Document shepherd | (None) | ||
IESG | IESG state | Replaced by draft-ietf-lisp-te | |
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.)