LISP Traffic Engineering Use-Cases
draft-farinacci-lisp-te-02
Document | Type |
This is an older version of an Internet-Draft whose latest revision state is "Replaced".
Expired & archived
|
|
---|---|---|---|
Authors | Dino Farinacci , Parantap Lahiri , Michael Kowal | ||
Last updated | 2013-07-11 (Latest revision 2013-01-07) | ||
Replaced by | draft-ietf-lisp-te, draft-ietf-lisp-te | ||
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 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
Parantap Lahiri
Michael Kowal
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)