I-D Action:draft-ietf-rserpool-asap-17.txt

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-17.txt
	Pages           : 51
	Date            : 2007-09-22

Aggregate Server Access Protocol (ASAP) in conjunction with the
Endpoint Handlespace Redundancy Protocol (ENRP) [9] provides a high
availability data transfer mechanism over IP networks.  ASAP uses a
handle-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 [3].  Each transport protocol, other than SCTP, MUST
have an accompanying transport mapping document.  It should be noted
that ASAP messages passed between PE's 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.Table of Contents

1.  Introduction . . . . . . . . . . . . . . . . . . . . . . . . .  5
  1.1.  Definitions  . . . . . . . . . . . . . . . . . . . . . . .  5
  1.2.  Organization of this document  . . . . . . . . . . . . . .  6
  1.3.  Scope of ASAP  . . . . . . . . . . . . . . . . . . . . . .  7

 1.3.1.  Extent of the Handlespace  . . . . . . . . . . . . . .  7
  1.4.  Conventions  . . . . . . . . . . . . . . . . . . . . . . .  7
2.  Message Definitions  . . . . . . . . . . . . . . . . . . . . .  8
  2.1.  ASAP Parameter Formats . . . . . . . . . . . . . . . . . .  8
  2.2.  ASAP Messages  . . . . . . . . . . . . . . . . . . . . . .  8

 2.2.1.  ASAP_REGISTRATION message  . . . . . . . . . . . . . .  9

 2.2.2.  ASAP_DEREGISTRATION message  . . . . . . . . . . . . .  9

 2.2.3.  ASAP_REGISTRATION_RESPONSE message . . . . . . . . . . 10

 2.2.4.  ASAP_DEREGISTRATION_RESPONSE message . . . . . . . . . 11

 2.2.5.  ASAP_HANDLE_RESOLUTION message . . . . . . . . . . . . 11

 2.2.6.  ASAP_HANDLE_RESOLUTION_RESPONSE message  . . . . . . . 12

 2.2.7.  ASAP_ENDPOINT_KEEP_ALIVE message . . . . . . . . . . . 14

 2.2.8.  ASAP_ENDPOINT_KEEP_ALIVE_ACK message . . . . . . . . . 15

 2.2.9.  ASAP_ENDPOINT_UNREACHABLE message  . . . . . . . . . . 15

 2.2.10. ASAP_SERVER_ANNOUNCE message . . . . . . . . . . . . . 16

 2.2.11. ASAP_COOKIE message  . . . . . . . . . . . . . . . . . 16

 2.2.12. ASAP_COOKIE_ECHO message . . . . . . . . . . . . . . . 17

 2.2.13. ASAP_BUSINESS_CARD message . . . . . . . . . . . . . . 17

 2.2.14. ASAP_ERROR message . . . . . . . . . . . . . . . . . . 18
3.  Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . 19
  3.1.  Registration . . . . . . . . . . . . . . . . . . . . . . . 19
  3.2.  Deregistration . . . . . . . . . . . . . . . . . . . . . . 21
  3.3.  Handle resolution  . . . . . . . . . . . . . . . . . . . . 22
  3.4.  Endpoint keep alive  . . . . . . . . . . . . . . . . . . . 23
  3.5.  Reporting unreachable endpoints  . . . . . . . . . . . . . 24
  3.6.  ENRP server hunt procedures  . . . . . . . . . . . . . . . 24
  3.7.  Handling ASAP Endpoint to ENRP Server Communication


  Failures . . . . . . . . . . . . . . . . . . . . . . . . . 26

 3.7.1.  SCTP Send Failure  . . . . . . . . . . . . . . . . . . 26

 3.7.2.  T1-ENRPrequest Timer Expiration  . . . . . . . . . . . 26

 3.7.3.  Registration Failure . . . . . . . . . . . . . . . . . 27
  3.8.  Cookie handling procedures . . . . . . . . . . . . . . . . 27
  3.9.  Business Card handling procedures  . . . . . . . . . . . . 27
4.  The ASAP Interfaces  . . . . . . . . . . . . . . . . . . . . . 29
  4.1.  Registration.Request Primitive . . . . . . . . . . . . . . 29
  4.2.  Deregistration.Request Primitive . . . . . . . . . . . . . 29
  4.3.  CachePopulateRequest Primitive . . . . . . . . . . . . . . 30
  4.4.  CachePurgeRequest Primitive  . . . . . . . . . . . . . . . 30
  4.5.  DataSendRequest Primitive  . . . . . . . . . . . . . . . . 30

 4.5.1.  Sending to a Pool Handle . . . . . . . . . . . . . . . 31

 4.5.2.  Pool Element Selection . . . . . . . . . . . . . . . . 32

 4.5.3.  Sending to a Pool Element Handle . . . . . . . . . . . 33

 4.5.4.  Send by Transport Address  . . . . . . . . . . . . . . 34

 4.5.5.  Message Delivery Options . . . . . . . . . . . . . . . 34
  4.6.  Data.Received Notification . . . . . . . . . . . . . . . . 35
  4.7.  Error.Report Notification  . . . . . . . . . . . . . . . . 36
  4.8.  Examples . . . . . . . . . . . . . . . . . . . . . . . . . 36

 4.8.1.  Send to a New Pool . . . . . . . . . . . . . . . . . . 36

 4.8.2.  Send to a Cached Pool Handle . . . . . . . . . . . . . 38
  4.9.  PE send failure  . . . . . . . . . . . . . . . . . . . . . 38

 4.9.1.  Translation.Request Primitive  . . . . . . . . . . . . 38

 4.9.2.  Transport.Failure Primitive  . . . . . . . . . . . . . 39
5.  Timers, Variables, and Thresholds  . . . . . . . . . . . . . . 40
  5.1.  Timers . . . . . . . . . . . . . . . . . . . . . . . . . . 40
  5.2.  Variables  . . . . . . . . . . . . . . . . . . . . . . . . 40
  5.3.  Thresholds . . . . . . . . . . . . . . . . . . . . . . . . 40
6.  IANA Considerations  . . . . . . . . . . . . . . . . . . . . . 42
  6.1.  A New Table for ASAP Message Types . . . . . . . . . . . . 42
7.  Security Considerations  . . . . . . . . . . . . . . . . . . . 43
  7.1.  Summary of Rserpool Security Threats . . . . . . . . . . . 43
  7.2.  Implementing Security Mechanisms . . . . . . . . . . . . . 44
  7.3.  Chain of trust . . . . . . . . . . . . . . . . . . . . . . 45
8.  Acknowledgments  . . . . . . . . . . . . . . . . . . . . . . . 47
9.  References . . . . . . . . . . . . . . . . . . . . . . . . . . 48
  9.1.  Normative References . . . . . . . . . . . . . . . . . . . 48
  9.2.  Informative References . . . . . . . . . . . . . . . . . . 49
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 50
Intellectual Property and Copyright Statements . . . . . . . . . . 51

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-rserpool-asap-17.txt

To remove yourself from the I-D Announcement list, send a message to
[email protected] with the word unsubscribe in the body of 
the message.
You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce
to change your subscription settings.

Internet-Drafts are also available by anonymous FTP. Login with the 
username "anonymous" and a password of your e-mail address. After 
logging in, type "cd internet-drafts" and then
	"get draft-ietf-rserpool-asap-17.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt

Internet-Drafts can also be obtained by e-mail.

Send a message to:
	[email protected].
In the body type:
	"FILE /internet-drafts/draft-ietf-rserpool-asap-17.txt".

NOTE:   The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.

Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

_______________________________________________
rserpool mailing list
[email protected]
https://www1.ietf.org/mailman/listinfo/rserpool