RFC 4678
Server/Application State Protocol v1, September 2006
- File formats:
- Status:
- INFORMATIONAL
- Author:
- A. Bivens
- Stream:
- INDEPENDENT
Cite this RFC: TXT | XML | BibTeX
DOI: https://doi.org/10.17487/RFC4678
Discuss this RFC: Send questions or comments to the mailing list rfc-ise@rfc-editor.org
Other actions: View Errata | Submit Errata | Find IPR Disclosures from the IETF | View History of RFC 4678
Abstract
Entities responsible for distributing work across a group of systems traditionally do not know a great deal about the ability of the applications on those systems to complete the work in a satisfactory fashion. Workload management systems traditionally know a great deal about the health of applications, but have little control over the rate in which these applications receive work. The Server/Application State Protocol (SASP) provides a mechanism for load balancers and workload management systems to communicate better ways of distributing the existing workload to the group members. This memo provides information for the Internet community.
For the definition of Status, see RFC 2026.
For the definition of Stream, see RFC 8729.