API Resources
Theme

Choose how MSRBot.io looks on this device.

Auto (match system) Light mode Dark mode

Preference is stored in this browser only.

IETF RFC 5352
[ACTIVE]

Aggregate Server Access Protocol (ASAP)

Metadata

Publisher
IETF
Doc Type
Experimental
Pages
53
Abstract
Aggregate Server Access Protocol (ASAP; RFC 5352), in conjunction with the Endpoint Handlespace Redundancy Protocol (ENRP; RFC 5353), provides a high-availability data transfer mechanism over IP networks. ASAP uses a handle-based addressing model that isolates a logical communication endpoint from its IP address(es), thus effectively eliminating the binding between the communication endpoint and its physical IP address(es), which normally constitutes a single point of failure. In addition, ASAP defines each logical communication destination as a pool, providing full transparent support for server pooling and load sharing. It also allows dynamic system scalability -- members of a server pool can be added or removed at any time without interrupting the service. ASAP is designed to take full advantage of the network level redundancy provided by the Stream Transmission Control Protocol (SCTP; RFC 4960). Each transport protocol, other than SCTP, MUST have an accompanying transport mapping document. It should be noted that ASAP messages passed between Pool Elements (PEs) and ENRP servers MUST use the SCTP transport protocol. The high-availability server pooling is gained by combining two protocols, namely ASAP and ENRP, in which ASAP provides the user interface for Pool Handle to address translation, load sharing management, and fault management, while ENRP defines the high- availability Pool Handle translation service. This memo defines an Experimental Protocol for the Internet community.
Publication Date
2008-09-01
Status Note
Experimental
DOI
10.17487/RFC5352
Link
https://doi.org/10.17487/RFC5352
Author(s)
Randall R. Stewart
Qiaobing Xie
Maureen Stillman
Michael Tüxen
Keyword(s)
RSerPool
Latest version of IETF RFC 5352

Document Versions — IETF RFC 5352

  • ▶ IETF RFC 5352 (2008-09-01)
    THIS DOC [ACTIVE] [LATEST VERSION]

Normative Reference(s)

Bibliographic Reference(s)

Source Data (JSON)

Full registry record with provenance metadata. Open directly: /api/doc/RFC5352.json

Reference Tree

Explore all references and references to this document, as a navigable tree.

Open Reference Tree
Reference this Doc

Plain text (ISO 690 compliant)

Preview:
IETF RFC 5352, Aggregate Server Access Protocol (ASAP). Available at https://doi.org/10.17487/RFC5352
Snippet:
IETF RFC 5352, Aggregate Server Access Protocol (ASAP). Available at https://doi.org/10.17487/RFC5352

HTML (ISO 690 compliant)

Preview:
IETF RFC 5352, Aggregate Server Access Protocol (ASAP). Available at https://doi.org/10.17487/RFC5352
Snippet:
<span class="citation"><cite>IETF RFC 5352</cite>, Aggregate Server Access Protocol (ASAP). Available at <a href="https://doi.org/10.17487/RFC5352" target="_blank" rel="noopener">https://doi.org/10.17487/RFC5352</a></span>

SMPTE Icon SMPTE's HTML Pub

Preview:
IETF RFC 5352, Aggregate Server Access Protocol (ASAP)
doi: 10.17487/RFC5352
url: https://doi.org/10.17487/RFC5352
Snippet:
<li>
<cite id="bib-rfc5352">IETF RFC 5352</cite>, Aggregate Server Access Protocol (ASAP)
<span class="doi">10.17487/RFC5352</span>
</li>

Referenced By