LISP Extensions for Segment Routing
draft-brockners-lisp-sr-01
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Frank Brockners , Shwetha Bhandari , Fabio Maino , Darrel Lewis | ||
| Last updated | 2014-08-17 (Latest revision 2014-02-13) | ||
| 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
Segment Routing (SR) combines source routing and tunneling to steer traffic through the transit network. The Locator/ID Separation Protocol (LISP) separates IP addresses into Endpoint Identifiers (EIDs) and Routing Locators (RLOCs) and also leverages tunneling mechanisms. Mapping between EIDs and RLOCs is facilitated by the LISP mapping system. Combining LISP and SR enables the LISP mapping system to provide SR information to encapsulating routers so that traffic can be steered in the transit network or the list of segments a particular packet traverses is recorded in the packet header. This document describes extensions required to the Locator/ID Separation Protocol (LISP) to enable a LISP mapping system to communicate list of segment identifiers or the request to record the list of segments a particular packet traverses to the encapsulating router.
Authors
Frank Brockners
Shwetha Bhandari
Fabio Maino
Darrel Lewis
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)