10 Jun 2004 21:55
I-D ACTION:draft-ietf-rserpool-asap-09.txt
<Internet-Drafts <at> ietf.org>
2004-06-10 19:55:23 GMT
2004-06-10 19:55:23 GMT
A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Reliable Server Pooling Working Group of the IETF. Title : Aggregate Server Access Protocol (ASAP) Author(s) : R. Stewart, et al. Filename : draft-ietf-rserpool-asap-09.txt Pages : 43 Date : 2004-6-10 Aggregate Server Access Protocol (ASAP) in conjunction with the Endpoint Name Resolution Protocol (ENRP) [6] provides a high availability data transfer mechanism over IP networks. ASAP uses a name-based addressing model which 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) RFC2960 [4]. Each transport protocol to be used by Pool Elements (PE) and Pool Users (PU) MUST have an accompanying transports mapping document. Note that ASAP messages passed between PE's and ENRP servers MUST use SCTP. The high availability server pooling is gained by combining two protocols, namely ASAP and ENRP, in which ASAP provides the user interface for name to address translation, load sharing management,(Continue reading)
RSS Feed