NECP the Network Element Control Protocol
draft-cerpa-wrec-necp-01
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Hooman Beheshti , Chuck Neerdaels , Alberto Cerpa , Dr. Peter B. Danzig , Raj Jalan , Anawat Chankhunthod , Jeremy Elson , Ted Schroeder , Gary Tomlinson | ||
| Last updated | 1999-12-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
This document describes 'NECP', a lightweight protocol for signalling 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 transparent 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 network transparent proxies, and cut-through of flows that can not be served by the farm.
Authors
Hooman Beheshti
Chuck Neerdaels
Alberto Cerpa
Dr. Peter B. Danzig
Raj Jalan
Anawat Chankhunthod
Jeremy Elson
Ted Schroeder
Gary Tomlinson
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)