LISP Map Server Reliable Transport
draft-ietf-lisp-map-server-reliable-transport-01
Document | Type |
This is an older version of an Internet-Draft whose latest revision state is "Active".
Expired & archived
|
|
---|---|---|---|
Authors | Darrel Lewis , Balaji Venkatachalapathy , Marc Portoles-Comeras , Isidor Kouvelas , Chris Cassar | ||
Last updated | 2023-07-25 (Latest revision 2023-01-10) | ||
Replaces | draft-kouvelas-lisp-map-server-reliable-transport | ||
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
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
Darrel Lewis
Balaji Venkatachalapathy
Marc Portoles-Comeras
Isidor Kouvelas
Chris Cassar
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)