RFC 5352: Aggregate Server Access Protocol (ASAP)

Aggregate Server Access Protocol (ASAP; RFC 5352), in conjunction with the Endpoint Handlespace Redundancy Protocol (ENRP; RFC 5353), provides a…

Read RFC 5352 on the RFC Editor

Outgoing relationships (15 related RFCs)

Normative reference — RFC 2119: Key words for use in RFCs to Indicate Requirement Levels
Normative reference — RFC 5226: Guidelines for Writing an IANA Considerations Section in RFCs
Normative reference — RFC 5246: The Transport Layer Security (TLS) Protocol Version 1.2
Normative reference — RFC 2460: Internet Protocol, Version 6 (IPv6) Specification
Normative reference — RFC 791: Internet Protocol
Normative reference — RFC 4960: Stream Control Transmission Protocol
Normative reference — RFC 3490: Internationalizing Domain Names in Applications (IDNA)
Normative reference — RFC 4511: Lightweight Directory Access Protocol (LDAP): The Protocol
Normative reference — RFC 3436: Transport Layer Security over Stream Control Transmission Protocol
Normative reference — RFC 5353: Endpoint Handlespace Redundancy Protocol (ENRP)
Normative reference — RFC 5354: Aggregate Server Access Protocol (ASAP) and Endpoint Handlespace Redundancy Protocol (ENRP) Parameters
Normative reference — RFC 5355: Threats Introduced by Reliable Server Pooling (RSerPool) and Requirements for Security in Response to Threats
Normative reference — RFC 3237: Requirements for Reliable Server Pooling
Normative reference — RFC 5356: Reliable Server Pooling Policies
Informative reference — RFC 4086: Randomness Requirements for Security

Incoming relationships (3 related RFCs)

Normatively referenced by — RFC 5353: Endpoint Handlespace Redundancy Protocol (ENRP)
Normatively referenced by — RFC 5356: Reliable Server Pooling Policies
Informatively referenced by — RFC 6404: Session PEERing for Multimedia INTerconnect (SPEERMINT) Security Threats and Suggested Countermeasures