Aggregate Server Access Protocol (ASAP) and Endpoint Handlespace Redundancy Protocol (ENRP) Parameters

Tuexen, Michael; Stewart, Randall; Stillman, Maureen; Xie, Qiaobing

doi:10.17487/rfc5354

Cited by 5 publications

(8 citation statements)

References 5 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…For a detailed overview of the documents that describe the current Reliable Server Pooling (RSerPool) framework, please refer to [RFC3237], [RFC5351], [RFC5352], [RFC5353], [RFC5354], [RFC5355], and [RFC5356]. A more informal introduction can be found at [RSerPoolPage] as well as in [Dre2006], [LCN2005], and [IJHIT2008].…”

Section: The Reliable Server Pooling (Rserpool) Frameworkmentioning

confidence: 99%

Reliable Server Pooling MIB Module Definition

Dreibholz¹,

Mulik²

2009

View full text Add to dashboard Cite

Section: The Reliable Server Pooling (Rserpool) Frameworkmentioning

confidence: 99%

Reliable Server Pooling MIB Module Definition

Dreibholz¹,

Mulik²

2009

View full text Add to dashboard Cite

“…Messages sent and received between a PE/PU and an ENRP server are part of ASAP and are defined in [RFC5352]. A common format, that is defined in [RFC5354], is used for all ENRP and ASAP messages.…”

Section: Enrp Message Definitionsmentioning

confidence: 99%

Endpoint Handlespace Redundancy Protocol (ENRP)

Tuexen¹,

Silverton²,

Stewart³

et al. 2008

Self Cite

View full text Add to dashboard Cite

show abstract

“…For fields with a length bigger than 4 bytes, a number in a pair of parentheses may follow the field name to indicate the length of the field in number of bytes. The basic message format and all parameter formats can be found in [RFC5354]. Note also that *all* ASAP messages exchanged between an ENRP server and a PE MUST use SCTP as transport, while ASAP messages exchanged between an ENRP server and a PU MUST use either SCTP or TCP as transport.…”

Section: Message Definitionsmentioning

confidence: 99%

“…This section details the individual messages used by ASAP. These messages are composed of a standard message format found in Section 4 of [RFC5354]. The parameter descriptions can be found in [RFC5354].…”

Section: Asap Messagesmentioning

confidence: 99%

Aggregate Server Access Protocol (ASAP)

Tuexen¹,

Stewart²,

Stillman³

et al. 2008

Self Cite

View full text Add to dashboard Cite

Aggregate Server Access Protocol (ASAP) Status of This MemoThis memo defines an Experimental Protocol for the Internet community. It does not specify an Internet standard of any kind. Discussion and suggestions for improvement are requested. Distribution of this memo is unlimited. AbstractAggregate 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.

show abstract

Aggregate Server Access Protocol (ASAP) and Endpoint Handlespace Redundancy Protocol (ENRP) Parameters

Cited by 5 publications

References 5 publications

Reliable Server Pooling MIB Module Definition

Reliable Server Pooling MIB Module Definition

Endpoint Handlespace Redundancy Protocol (ENRP)

Aggregate Server Access Protocol (ASAP)

Contact Info

Product

Resources

About