Aggregate Server Access Protocol
RFC 5352, “Aggregate Server Access Protocol”, is an Experimental document published in September 2008 by R. Stewart, Q. Xie, M. Stillman, M. Tuexen. The canonical text is published by the RFC Editor.
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.
What “Experimental” means
Describes a specification that is part of a research or development effort, published so the community can gain experience with it.
The canonical text of RFC 5352 is hosted at rfc-editor.org. Available in TXT,HTML.
- RFC 5351 An Overview of Reliable Server Pooling Protocols
- RFC 5353 Endpoint Handlespace Redundancy Protocol
- RFC 5350 IANA Considerations for the IPv4 and IPv6 Router Alert Options
- RFC 5354 Aggregate Server Access Protocol and Endpoint Handlespace Redundancy Protocol Parameters
- RFC 5349 Elliptic Curve Cryptography Support for Public Key Cryptography for Initial Authentication in Kerberos
- RFC 5355 Threats Introduced by Reliable Server Pooling and Requirements for Security in Response to Threats
- RFC 5348 TCP Friendly Rate Control : Protocol Specification
- RFC 5356 Reliable Server Pooling Policies