Alberto Cerpa, Jeremy Elson, Hooman Beheshti, Anawat Cankhunthod, Peter Danzig, Raj Jana, Chuck Neerdaels, Ted Schroeder, Gary Tomlinson
This document describes 'NECP', a lightweight protocol for signaling between servers and the network elements that forward traffic to them. It is intended for use in a wide variety of server applications, including for origin servers, proxies, and interception proxies. The network element may also be a range of devices, including so-called L4 or content-aware switches and load-balancing routers. NECP provides methods for network elements to learn about servers' capabilities, availability, and hints as to which flows can and can not be serviced. This allows network elements to perform load balancing across a farm of servers, redirection to interception proxies, and cut-through of flows that can not be served by the farm.
Alberto Cerpa, Jeremy Elson, Hooman Beheshti, Anawat Cankhunthod, Peter Danzig, Raj Jana, Chuck Neerdaels, Ted Schroeder, Gary Tomlinson, "NECP: Network Element Control Protocol," Internet-Draft, pp. 1--38, Internet Engineering Task Force (IETF), March, 2000.
@TechReport{Cerpa00a, author = "Alberto Cerpa and Jeremy Elson and Hooman Beheshti and Anawat Cankhunthod and Peter Danzig and Raj Jana and Chuck Neerdaels and Ted Schroeder and Gary Tomlinson", title = "{NECP}: Network Element Control Protocol", institution = "Internet Engineering Task Force (IETF)", number = "Internet-Draft", year = "2000", pages = "1--38", month = mar, URL = "http://www.andes.ucmerced.edu/papers/Cerpa00a.pdf", cited = "10", }