RFC 3237: Requirements for Reliable Server Pooling
In plain English — editorial summary, not part of the RFC
This document defines a basic set of requirements for reliable server pooling. This memo provides information for the Internet community.
Document record
- Document ID
- RFC3237
- Published
- January 2002
- Authors
- M. Tuexen; Q. Xie; R. Stewart; M. Shore; L. Ong; J. Loughney; M. Stillman
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- tsv
- Pages
- 10
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 3242RObust Header Compression (ROHC): A Link-Layer Assisted Profile for IP/UDP/RTPObsoleted
April 2002
- RFC 2887The Reliable Multicast Design Space for Bulk Data TransferCurrent
August 2000
- RFC 2771An Abstract API for Multicast Address AllocationCurrent
February 2000
- RFC 2203RPCSEC_GSS Protocol SpecificationUpdated
September 1997
- RFC 5351An Overview of Reliable Server Pooling ProtocolsCurrent
September 2008
- RFC 5352Aggregate Server Access Protocol (ASAP)Current
September 2008
- RFC 5353Endpoint Handlespace Redundancy Protocol (ENRP)Current
September 2008
- RFC 5354Aggregate Server Access Protocol (ASAP) and Endpoint Handlespace Redundancy Protocol (ENRP) ParametersCurrent
September 2008
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?