Requirements for Reliable Server Pooling
Metadata
- Publisher
- IETF
- Doc Type
- Informational
- Pages
- 10
- Abstract
- This document defines a basic set of requirements for reliable server pooling. This memo provides information for the Internet community.
- Publication Date
- 2002-01-01
- Status Note
- Informational
- DOI
10.17487/RFC3237- Link
- https://doi.org/10.17487/RFC3237
- Author(s)
- Michael TüxenQiaobing XieRandall R. StewartMelinda ShoreLyndon OngJohn A. LoughneyMaureen Stillman
- Keyword(s)
- RSerPool, Application
Latest version of IETF RFC 3237
Document Versions — IETF RFC 3237
-
▶ IETF RFC 3237 (2002-01-01)THIS DOC [ACTIVE] [LATEST VERSION]
Bibliographic Reference(s)
- IETF RFC 793 [Superseded*]
- IETF RFC 959 [Active*]
- IETF RFC 2026 [Active*]
- IETF RFC 2608 [Active*]
- IETF RFC 2719 [Active*]
- IETF RFC 2914 [Active*]
- IETF RFC 2960 [Superseded*]
Source Data (JSON)
Full registry record with provenance metadata. Open directly: /api/doc/RFC3237.json
Reference Tree
Explore all references and references to this document, as a navigable tree.
Open Reference TreeReference this Doc
Plain text (ISO 690 compliant)
Preview:
IETF RFC 3237, Requirements for Reliable Server Pooling. Available at https://doi.org/10.17487/RFC3237
Snippet:
IETF RFC 3237, Requirements for Reliable Server Pooling. Available at https://doi.org/10.17487/RFC3237
HTML (ISO 690 compliant)
Preview:
IETF RFC 3237, Requirements for Reliable Server Pooling. Available at https://doi.org/10.17487/RFC3237
Snippet:
<span class="citation"><cite>IETF RFC 3237</cite>, Requirements for Reliable Server Pooling. Available at <a href="https://doi.org/10.17487/RFC3237" target="_blank" rel="noopener">https://doi.org/10.17487/RFC3237</a></span>
SMPTE's HTML Pub
Preview:
IETF RFC 3237, Requirements for Reliable Server Pooling
doi: 10.17487/RFC3237
url: https://doi.org/10.17487/RFC3237
doi: 10.17487/RFC3237
url: https://doi.org/10.17487/RFC3237
Snippet:
<li> <cite id="bib-rfc3237">IETF RFC 3237</cite>, Requirements for Reliable Server Pooling <span class="doi">10.17487/RFC3237</span> </li>
Referenced By
- IETF RFC 5351 [Active*]
- IETF RFC 5352 [Active*]
- IETF RFC 5353 [Active*]