LISP Reliable Transport
draft-kouvelas-lisp-reliable-transport-02
| Document | Type |
Replaced Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Christian Cassar , Isidor Kouvelas , Darrel Lewis | ||
| Last updated | 2015-09-28 (Latest revision 2015-03-27) | ||
| Replaced by | draft-kouvelas-lisp-map-server-reliable-transport | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Replaced by draft-kouvelas-lisp-map-server-reliable-transport | |
| 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
The communication between LISP ETRs and Map-Servers is based on unreliable UDP message exchange coupled with periodic message transmission in order to maintain soft state. The drawback of periodic messaging is the constant load imposed on both the ETR and the Map-Server. New use cases for LISP have increased the amount of state that needs to be communicated with requirements that are not satisfied by the current mechanism. This document introduces the use of a reliable transport for ETR to Map-Server communication in order to eliminate the periodic messaging overhead, while providing reliability, flow-control and endpoint liveness detection.
Authors
Christian Cassar
Isidor Kouvelas
Darrel Lewis
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)