draft-ietf-rserpool-asap-17.txt   draft-ietf-rserpool-asap-18.txt 
Network Working Group R. Stewart Network Working Group R. Stewart
Internet-Draft Cisco Systems, Inc. Internet-Draft Cisco Systems, Inc.
Intended status: Experimental Q. Xie Intended status: Experimental Q. Xie
Expires: March 25, 2008 Motorola, Inc. Expires: May 22, 2008 Motorola, Inc.
M. Stillman M. Stillman
Nokia Nokia
M. Tuexen M. Tuexen
Muenster Univ. of Applied Sciences Muenster Univ. of Applied Sciences
September 22, 2007 November 19, 2007
Aggregate Server Access Protocol (ASAP) Aggregate Server Access Protocol (ASAP)
draft-ietf-rserpool-asap-17.txt draft-ietf-rserpool-asap-18.txt
Status of this Memo Status of this Memo
By submitting this Internet-Draft, each author represents that any By submitting this Internet-Draft, each author represents that any
applicable patent or other IPR claims of which he or she is aware applicable patent or other IPR claims of which he or she is aware
have been or will be disclosed, and any of which he or she becomes have been or will be disclosed, and any of which he or she becomes
aware will be disclosed, in accordance with Section 6 of BCP 79. aware will be disclosed, in accordance with Section 6 of BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF), its areas, and its working groups. Note that
skipping to change at page 1, line 39 skipping to change at page 1, line 39
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt. http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html. http://www.ietf.org/shadow.html.
This Internet-Draft will expire on March 25, 2008. This Internet-Draft will expire on May 22, 2008.
Copyright Notice Copyright Notice
Copyright (C) The IETF Trust (2007). Copyright (C) The IETF Trust (2007).
Abstract Abstract
Aggregate Server Access Protocol (ASAP) in conjunction with the Aggregate Server Access Protocol (ASAP) in conjunction with the
Endpoint Handlespace Redundancy Protocol (ENRP) [9] provides a high Endpoint Handlespace Redundancy Protocol (ENRP)
availability data transfer mechanism over IP networks. ASAP uses a [I-D.ietf-rserpool-enrp] provides a high availability data transfer
handle-based addressing model which isolates a logical communication mechanism over IP networks. ASAP uses a handle-based addressing
endpoint from its IP address(es), thus effectively eliminating the model which isolates a logical communication endpoint from its IP
binding between the communication endpoint and its physical IP address(es), thus effectively eliminating the binding between the
address(es) which normally constitutes a single point of failure. 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 In addition, ASAP defines each logical communication destination as a
pool, providing full transparent support for server-pooling and load pool, providing full transparent support for server-pooling and load
sharing. It also allows dynamic system scalability - members of a sharing. It also allows dynamic system scalability - members of a
server pool can be added or removed at any time without interrupting server pool can be added or removed at any time without interrupting
the service. the service.
ASAP is designed to take full advantage of the network level ASAP is designed to take full advantage of the network level
redundancy provided by the Stream Transmission Control Protocol redundancy provided by the Stream Transmission Control Protocol
(SCTP) RFC2960 [3]. Each transport protocol, other than SCTP, MUST (SCTP) [RFC4960]. Each transport protocol, other than SCTP, MUST
have an accompanying transport mapping document. It should be noted have an accompanying transport mapping document. It should be noted
that ASAP messages passed between PE's and ENRP servers MUST use the that ASAP messages passed between PE's and ENRP servers MUST use the
SCTP transport protocol. SCTP transport protocol.
The high availability server pooling is gained by combining two The high availability server pooling is gained by combining two
protocols, namely ASAP and ENRP, in which ASAP provides the user protocols, namely ASAP and ENRP, in which ASAP provides the user
interface for pool handle to address translation, load sharing interface for pool handle to address translation, load sharing
management, and fault management while ENRP defines the high management, and fault management while ENRP defines the high
availability pool handle translation service. availability pool handle translation service.
skipping to change at page 3, line 32 skipping to change at page 3, line 32
2.2.7. ASAP_ENDPOINT_KEEP_ALIVE message . . . . . . . . . . . 14 2.2.7. ASAP_ENDPOINT_KEEP_ALIVE message . . . . . . . . . . . 14
2.2.8. ASAP_ENDPOINT_KEEP_ALIVE_ACK message . . . . . . . . . 15 2.2.8. ASAP_ENDPOINT_KEEP_ALIVE_ACK message . . . . . . . . . 15
2.2.9. ASAP_ENDPOINT_UNREACHABLE message . . . . . . . . . . 15 2.2.9. ASAP_ENDPOINT_UNREACHABLE message . . . . . . . . . . 15
2.2.10. ASAP_SERVER_ANNOUNCE message . . . . . . . . . . . . . 16 2.2.10. ASAP_SERVER_ANNOUNCE message . . . . . . . . . . . . . 16
2.2.11. ASAP_COOKIE message . . . . . . . . . . . . . . . . . 16 2.2.11. ASAP_COOKIE message . . . . . . . . . . . . . . . . . 16
2.2.12. ASAP_COOKIE_ECHO message . . . . . . . . . . . . . . . 17 2.2.12. ASAP_COOKIE_ECHO message . . . . . . . . . . . . . . . 17
2.2.13. ASAP_BUSINESS_CARD message . . . . . . . . . . . . . . 17 2.2.13. ASAP_BUSINESS_CARD message . . . . . . . . . . . . . . 17
2.2.14. ASAP_ERROR message . . . . . . . . . . . . . . . . . . 18 2.2.14. ASAP_ERROR message . . . . . . . . . . . . . . . . . . 18
3. Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . 19 3. Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . 19
3.1. Registration . . . . . . . . . . . . . . . . . . . . . . . 19 3.1. Registration . . . . . . . . . . . . . . . . . . . . . . . 19
3.2. Deregistration . . . . . . . . . . . . . . . . . . . . . . 21 3.2. Deregistration . . . . . . . . . . . . . . . . . . . . . . 22
3.3. Handle resolution . . . . . . . . . . . . . . . . . . . . 22 3.3. Handle resolution . . . . . . . . . . . . . . . . . . . . 23
3.4. Endpoint keep alive . . . . . . . . . . . . . . . . . . . 23 3.4. Endpoint keep alive . . . . . . . . . . . . . . . . . . . 25
3.5. Reporting unreachable endpoints . . . . . . . . . . . . . 24 3.5. Unreachable endpoints . . . . . . . . . . . . . . . . . . 26
3.6. ENRP server hunt procedures . . . . . . . . . . . . . . . 24 3.6. ENRP server hunt procedures . . . . . . . . . . . . . . . 27
3.7. Handling ASAP Endpoint to ENRP Server Communication 3.7. Handling ASAP Endpoint to ENRP Server Communication
Failures . . . . . . . . . . . . . . . . . . . . . . . . . 26 Failures . . . . . . . . . . . . . . . . . . . . . . . . . 29
3.7.1. SCTP Send Failure . . . . . . . . . . . . . . . . . . 26 3.7.1. SCTP Send Failure . . . . . . . . . . . . . . . . . . 29
3.7.2. T1-ENRPrequest Timer Expiration . . . . . . . . . . . 26 3.7.2. T1-ENRPrequest Timer Expiration . . . . . . . . . . . 29
3.7.3. Registration Failure . . . . . . . . . . . . . . . . . 27 3.7.3. Registration Failure . . . . . . . . . . . . . . . . . 30
3.8. Cookie handling procedures . . . . . . . . . . . . . . . . 27 3.8. Cookie handling procedures . . . . . . . . . . . . . . . . 30
3.9. Business Card handling procedures . . . . . . . . . . . . 27 3.9. Business Card handling procedures . . . . . . . . . . . . 30
4. The ASAP Interfaces . . . . . . . . . . . . . . . . . . . . . 29 4. Roles of Endpoints . . . . . . . . . . . . . . . . . . . . . . 32
4.1. Registration.Request Primitive . . . . . . . . . . . . . . 29 5. SCTP considerations . . . . . . . . . . . . . . . . . . . . . 33
4.2. Deregistration.Request Primitive . . . . . . . . . . . . . 29 6. The ASAP Interfaces . . . . . . . . . . . . . . . . . . . . . 34
4.3. CachePopulateRequest Primitive . . . . . . . . . . . . . . 30 6.1. Registration.Request Primitive . . . . . . . . . . . . . . 34
4.4. CachePurgeRequest Primitive . . . . . . . . . . . . . . . 30 6.2. Deregistration.Request Primitive . . . . . . . . . . . . . 34
4.5. DataSendRequest Primitive . . . . . . . . . . . . . . . . 30 6.3. CachePopulateRequest Primitive . . . . . . . . . . . . . . 35
4.5.1. Sending to a Pool Handle . . . . . . . . . . . . . . . 31 6.4. CachePurgeRequest Primitive . . . . . . . . . . . . . . . 35
4.5.2. Pool Element Selection . . . . . . . . . . . . . . . . 32 6.5. DataSendRequest Primitive . . . . . . . . . . . . . . . . 35
4.5.3. Sending to a Pool Element Handle . . . . . . . . . . . 33 6.5.1. Sending to a Pool Handle . . . . . . . . . . . . . . . 36
4.5.4. Send by Transport Address . . . . . . . . . . . . . . 34 6.5.2. Pool Element Selection . . . . . . . . . . . . . . . . 37
4.5.5. Message Delivery Options . . . . . . . . . . . . . . . 34 6.5.3. Sending to a Pool Element Handle . . . . . . . . . . . 38
4.6. Data.Received Notification . . . . . . . . . . . . . . . . 35 6.5.4. Send by Transport Address . . . . . . . . . . . . . . 39
4.7. Error.Report Notification . . . . . . . . . . . . . . . . 36 6.5.5. Message Delivery Options . . . . . . . . . . . . . . . 39
4.8. Examples . . . . . . . . . . . . . . . . . . . . . . . . . 36 6.6. Data.Received Notification . . . . . . . . . . . . . . . . 40
4.8.1. Send to a New Pool . . . . . . . . . . . . . . . . . . 36 6.7. Error.Report Notification . . . . . . . . . . . . . . . . 41
4.8.2. Send to a Cached Pool Handle . . . . . . . . . . . . . 38 6.8. Examples . . . . . . . . . . . . . . . . . . . . . . . . . 41
4.9. PE send failure . . . . . . . . . . . . . . . . . . . . . 38 6.8.1. Send to a New Pool . . . . . . . . . . . . . . . . . . 41
4.9.1. Translation.Request Primitive . . . . . . . . . . . . 38 6.8.2. Send to a Cached Pool Handle . . . . . . . . . . . . . 43
4.9.2. Transport.Failure Primitive . . . . . . . . . . . . . 39 6.9. PE send failure . . . . . . . . . . . . . . . . . . . . . 43
5. Timers, Variables, and Thresholds . . . . . . . . . . . . . . 40 6.9.1. Translation.Request Primitive . . . . . . . . . . . . 43
5.1. Timers . . . . . . . . . . . . . . . . . . . . . . . . . . 40 6.9.2. Transport.Failure Primitive . . . . . . . . . . . . . 44
5.2. Variables . . . . . . . . . . . . . . . . . . . . . . . . 40 7. Timers, Variables, and Thresholds . . . . . . . . . . . . . . 45
5.3. Thresholds . . . . . . . . . . . . . . . . . . . . . . . . 40 7.1. Timers . . . . . . . . . . . . . . . . . . . . . . . . . . 45
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 42 7.2. Variables . . . . . . . . . . . . . . . . . . . . . . . . 45
6.1. A New Table for ASAP Message Types . . . . . . . . . . . . 42 7.3. Thresholds . . . . . . . . . . . . . . . . . . . . . . . . 45
7. Security Considerations . . . . . . . . . . . . . . . . . . . 43 8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 47
7.1. Summary of Rserpool Security Threats . . . . . . . . . . . 43 8.1. A New Table for ASAP Message Types . . . . . . . . . . . . 47
7.2. Implementing Security Mechanisms . . . . . . . . . . . . . 44 8.2. Multicast addresses . . . . . . . . . . . . . . . . . . . 47
7.3. Chain of trust . . . . . . . . . . . . . . . . . . . . . . 45 9. Security Considerations . . . . . . . . . . . . . . . . . . . 48
8. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 47 9.1. Summary of Rserpool Security Threats . . . . . . . . . . . 48
9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 48 9.2. Implementing Security Mechanisms . . . . . . . . . . . . . 49
9.1. Normative References . . . . . . . . . . . . . . . . . . . 48 9.3. Chain of trust . . . . . . . . . . . . . . . . . . . . . . 50
9.2. Informative References . . . . . . . . . . . . . . . . . . 49 10. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 52
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 50 11. References . . . . . . . . . . . . . . . . . . . . . . . . . . 53
Intellectual Property and Copyright Statements . . . . . . . . . . 51 11.1. Normative References . . . . . . . . . . . . . . . . . . . 53
11.2. Informative References . . . . . . . . . . . . . . . . . . 54
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 55
Intellectual Property and Copyright Statements . . . . . . . . . . 56
1. Introduction 1. Introduction
The Aggregate Server Access Protocol (ASAP) when used in conjunction The Aggregate Server Access Protocol (ASAP) when used in conjunction
with Endpoint Name Resolution Protocol [9] provides a high with Endpoint Name Resolution Protocol [I-D.ietf-rserpool-enrp]
availability data transfer mechanism over IP networks. ASAP uses a provides a high availability data transfer mechanism over IP
handle-based addressing model which isolates a logical communication networks. ASAP uses a handle-based addressing model which isolates a
endpoint from its IP address(es), thus effectively eliminating the logical communication endpoint from its IP address(es), thus
binding between the communication endpoint and its physical IP effectively eliminating the binding between the communication
address(es) which normally constitutes a single point of failure. endpoint and its physical IP address(es) which normally constitutes a
single point of failure.
When multiple receiver instances exist under the same handle (a.k.a, When multiple receiver instances exist under the same handle (a.k.a,
a server pool),an ASAP endpoint will select one Pool Element (PE), a server pool),an ASAP endpoint will select one Pool Element (PE),
based on the current load sharing policy indicated by the server based on the current load sharing policy indicated by the server
pool, and deliver its message to the selected PE. pool, and deliver its message to the selected PE.
While delivering the message, ASAP can be used to monitor the While delivering the message, ASAP can be used to monitor the
reachability of the selected PE. If it is found unreachable, before reachability of the selected PE. If it is found unreachable, before
notifying the message sender (an ASAP user) of the failure, ASAP can notifying the message sender (an ASAP user) of the failure, ASAP can
automatically select another PE (if one exists) under that pool and automatically select another PE (if one exists) under that pool and
attempt to deliver the message to that PE. In other words, ASAP is attempt to deliver the message to that PE. In other words, ASAP is
capable of transparent fail-over amongst PE instances within a server capable of transparent fail-over amongst PE instances within a server
pool. pool.
ASAP depends on ENRP which provides a high availability pool handle ASAP depends on ENRP which provides a high availability pool handle
space. ASAP is responsible for the abstraction of the underlying space. ASAP is responsible for the abstraction of the underlying
transport technologies, load distribution management, fault transport technologies, load distribution management, fault
management, as well as presentation to the upper layer (aka an ASAP management, as well as presentation to the upper layer (aka an ASAP
user) via a unified primitive interface. user) via a unified primitive interface.
When SCTP RFC2960 [3] is used as the transport layer protocol, ASAP When SCTP [RFC4960] is used as the transport layer protocol, ASAP can
can seamlessly incorporate the link-layer redundancy provided by seamlessly incorporate the link-layer redundancy provided by SCTP.
SCTP.
This document defines the ASAP portion of the high availability This document defines the ASAP portion of the high availability
server pool. server pool.
1.1. Definitions 1.1. Definitions
This document uses the following terms: This document uses the following terms:
ASAP user: Either a PE or PU that uses ASAP. ASAP user: Either a PE or PU that uses ASAP.
skipping to change at page 6, line 48 skipping to change at page 6, line 48
Transport address: A Transport Address is traditionally defined by Transport address: A Transport Address is traditionally defined by
Network Layer address, Transport Layer protocol and Transport Network Layer address, Transport Layer protocol and Transport
Layer port number. In the case of SCTP running over IP, a Layer port number. In the case of SCTP running over IP, a
transport address is defined by the combination of an IP address transport address is defined by the combination of an IP address
and an SCTP port number (where SCTP is the Transport protocol). and an SCTP port number (where SCTP is the Transport protocol).
1.2. Organization of this document 1.2. Organization of this document
Section 2 details the ASAP message formats. In Section 3 we provide Section 2 details the ASAP message formats. In Section 3 we provide
detailed ASAP procedures for for the ASAP implementer. In Section 4 detailed ASAP procedures for for the ASAP implementer. In Section 6
we give details of the ASAP interface, focusing on the communication we give details of the ASAP interface, focusing on the communication
primitives between ASAP the applications above ASAP and ASAP itself, primitives between ASAP the applications above ASAP and ASAP itself,
and the communications primitives between ASAP and SCTP (or other and the communications primitives between ASAP and SCTP (or other
transport layers). Also included in this discussion are relevant transport layers). Also included in this discussion are relevant
timers and configurable parameters as appropriate. Section 5 timers and configurable parameters as appropriate. Section 7
provides threshold and protocol variables. provides threshold and protocol variables.
Variables, timers and constants are used in the text when necessary.
A complete list can be found in Section 7
1.3. Scope of ASAP 1.3. Scope of ASAP
The requirements for high availability and scalability do not imply The requirements for high availability and scalability do not imply
requirements on shared state and data. ASAP does not provide requirements on shared state and data. ASAP does not provide
transaction failover. If a host or application fails during the transaction failover. If a host or application fails during the
processing of a transaction, this transaction may be lost. Some processing of a transaction, this transaction may be lost. Some
services MAY provide a way to handle the failure, but this is not services MAY provide a way to handle the failure, but this is not
guaranteed. ASAP MAY provide hooks to assist an application in guaranteed. ASAP MAY provide hooks to assist an application in
building a mechanism to share state but ASAP in itself does NOT share building a mechanism to share state but ASAP in itself does NOT share
any state. any state.
skipping to change at page 7, line 35 skipping to change at page 7, line 38
Suppose a PU in North America wishes to contact a server pool in Suppose a PU in North America wishes to contact a server pool in
Japan instead of North America. The PU would use DNS to get the list Japan instead of North America. The PU would use DNS to get the list
of IP addresses of the Japanese server pool, that is, the ENRP client of IP addresses of the Japanese server pool, that is, the ENRP client
channel in Japan. From there the PU would query the Home ENRP server channel in Japan. From there the PU would query the Home ENRP server
it established and then directly contact the PE(s) of interest. it established and then directly contact the PE(s) of interest.
1.4. Conventions 1.4. Conventions
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in RFC2119 [1]. document are to be interpreted as described in [RFC2119].
2. Message Definitions 2. Message Definitions
All messages as well as their fields described below shall be in All messages as well as their fields described below shall be in
Network Byte Order during transmission. For fields with a length Network Byte Order during transmission. For fields with a length
bigger than 4 bytes, a number in a pair of parentheses may follow the 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. field name to indicate the length of the field in number of bytes.
2.1. ASAP Parameter Formats 2.1. ASAP Parameter Formats
The basic message format and all parameter formats can be found in The basic message format and all parameter formats can be found in
ENRP-ASAP [8]. Note also that ALL ASAP messages exchanged between an [I-D.ietf-rserpool-common-param]. Note also that ALL ASAP messages
ENRP server and a PE MUST use SCTP as transport, while ASAP messages exchanged between an ENRP server and a PE MUST use SCTP as transport,
exchanged between an ENRP server and a PU MUST use either SCTP or TCP while ASAP messages exchanged between an ENRP server and a PU MUST
as transport. PE to PU data traffic MAY use any transport protocol use either SCTP or TCP as transport. PE to PU data traffic MAY use
specified by the PE during registration. any transport protocol specified by the PE during registration.
2.2. ASAP Messages 2.2. ASAP Messages
This section details the individual messages used by ASAP. These This section details the individual messages used by ASAP. These
messages are composed of a standard message format found in Section 4 messages are composed of a standard message format found in Section 4
of ENRP-ASAP [8]. The parameter descriptions can be found in Section of [I-D.ietf-rserpool-common-param]. The parameter descriptions can
3 of ENRP-ASAP [8]. be found in [I-D.ietf-rserpool-common-param].
The following ASAP message types are defined in this section: The following ASAP message types are defined in this section:
Type Message Name Type Message Name
----- ------------------------- ----- -------------------------
0x00 - (reserved by IETF) 0x00 - (reserved by IETF)
0x01 - ASAP_REGISTRATION 0x01 - ASAP_REGISTRATION
0x02 - ASAP_DEREGISTRATION 0x02 - ASAP_DEREGISTRATION
0x03 - ASAP_REGISTRATION_RESPONSE 0x03 - ASAP_REGISTRATION_RESPONSE
0x04 - ASAP_DEREGISTRATION_RESPONSE 0x04 - ASAP_DEREGISTRATION_RESPONSE
skipping to change at page 9, line 31 skipping to change at page 9, line 31
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type = 0x01 |0|0|0|0|0|0|0|0| Message Length | | Type = 0x01 |0|0|0|0|0|0|0|0| Message Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
: Pool Handle Parameter : : Pool Handle Parameter :
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
: Pool Element Parameter : : Pool Element Parameter :
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Pool Handle Parameter: Pool Handle Parameter:
See [8] section 3.7 See [I-D.ietf-rserpool-common-param]
Pool Element Parameter: Pool Element Parameter:
See [8] section 3.8 See [I-D.ietf-rserpool-common-param]
2.2.2. ASAP_DEREGISTRATION message 2.2.2. ASAP_DEREGISTRATION message
The ASAP_DEREGISTRATION message is sent by a PE to its Home ENRP The ASAP_DEREGISTRATION message is sent by a PE to its Home ENRP
Server to remove itself from a pool to which it registered. Server to remove itself from a pool to which it registered.
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type = 0x02 |0|0|0|0|0|0|0|0| Message Length | | Type = 0x02 |0|0|0|0|0|0|0|0| Message Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
: Pool Handle Parameter : : Pool Handle Parameter :
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
: PE Identifier Parameter : : PE Identifier Parameter :
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+++ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+++
Pool Handle Parameter: Pool Handle Parameter:
See [8] section 3.7 See [I-D.ietf-rserpool-common-param]
PE Identifier Parameter: PE Identifier Parameter:
See [8] section 3.12 See [I-D.ietf-rserpool-common-param]
The PE sending the ASAP_DEREGISTRATION MUST fill in the pool handle The PE sending the ASAP_DEREGISTRATION MUST fill in the pool handle
and the PE identifier parameter in order to allow the ENRP server to and the PE identifier parameter in order to allow the ENRP server to
verify the identity of the endpoint. Note that deregistration is NOT verify the identity of the endpoint. Note that deregistration is NOT
allowed by proxy, in other words a PE may only deregister itself. allowed by proxy, in other words a PE may only deregister itself.
2.2.3. ASAP_REGISTRATION_RESPONSE message 2.2.3. ASAP_REGISTRATION_RESPONSE message
The ASAP_REGISTRATION_RESPONSE message is sent in response by the The ASAP_REGISTRATION_RESPONSE message is sent in response by the
Home ENRP Server to the PE that sent a ASAP_REGISTRATION message. Home ENRP Server to the PE that sent a ASAP_REGISTRATION message.
skipping to change at page 10, line 41 skipping to change at page 10, line 41
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
R (Reject) Flag: R (Reject) Flag:
When set to '1', this flag indicates that the ENRP server sending When set to '1', this flag indicates that the ENRP server sending
this message has rejected the registration. Otherwise when this flag this message has rejected the registration. Otherwise when this flag
is set to '0', this indicates the registration has been granted. is set to '0', this indicates the registration has been granted.
Pool Handle Parameter: Pool Handle Parameter:
See [8] section 3.7. See [I-D.ietf-rserpool-common-param]
PE Identifier Parameter: PE Identifier Parameter:
See [8] section 3.12 See [I-D.ietf-rserpool-common-param]
Operational Error Parameter (optional): Operational Error Parameter (optional):
See [8] section 3.10 See [I-D.ietf-rserpool-common-param]
This parameter is included if an error or some atypical events This parameter is included if an error or some atypical events
occurred during the registration process. When the R flag is set to occurred during the registration process. When the R flag is set to
'1', this parameter, if present, indicates the cause of the '1', this parameter, if present, indicates the cause of the
rejection. When the R flag is set to '0', this parameter, if rejection. When the R flag is set to '0', this parameter, if
present, serves as a warning to the registering PE, informing it that present, serves as a warning to the registering PE, informing it that
some of its registration values may have been modified by the ENRP some of its registration values may have been modified by the ENRP
server. If the registration was successful and there is no warning, server. If the registration was successful and there is no warning,
this parameter is not included. this parameter is not included.
skipping to change at page 11, line 31 skipping to change at page 11, line 31
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
: Pool Handle Parameter : : Pool Handle Parameter :
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
: PE Identifier Parameter : : PE Identifier Parameter :
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
: Operational Error (optional) : : Operational Error (optional) :
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Pool Handle Parameter: Pool Handle Parameter:
See [8] section 3.7. See [I-D.ietf-rserpool-common-param]
PE Identifier Parameter: PE Identifier Parameter:
See [8] section 3.12. See [I-D.ietf-rserpool-common-param]
Operational Error: Operational Error:
See [8] section 3.10. See [I-D.ietf-rserpool-common-param]
This parameter is included if an error or some atypical events This parameter is included if an error or some atypical events
occurred during the deregistration process. If the deregistration occurred during the deregistration process. If the deregistration
was successful this parameter is not included. was successful this parameter is not included.
2.2.5. ASAP_HANDLE_RESOLUTION message 2.2.5. ASAP_HANDLE_RESOLUTION message
The ASAP_HANDLE_RESOLUTION message is sent by either a PE or PU to The ASAP_HANDLE_RESOLUTION message is sent by either a PE or PU to
its Home ENRP Server to resolve a pool handle into a list of pool its Home ENRP Server to resolve a pool handle into a list of pool
elements that are members of the pool indicated by the pool handle. elements that are members of the pool indicated by the pool handle.
skipping to change at page 12, line 16 skipping to change at page 12, line 16
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type = 0x05 |0|0|0|0|0|0|0|S| Message Length | | Type = 0x05 |0|0|0|0|0|0|0|S| Message Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
: Pool Handle Parameter : : Pool Handle Parameter :
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
The 'S' bit: The 'S' bit:
The 'S' bit, if set to '1', requests the Home ENRP server to send The 'S' bit, if set to '1', requests the Home ENRP server to send
updates to this Pool dynamically when the Pool changes. Dynamic updates to this Pool dynamically when the Pool changes for the
updates to the pool will consist of additional lifetime of the SCTP association. Dynamic updates to the pool will
ASAP_HANDLE_RESOLUTION_RESPONSE messages, without the user needing to consist of additional ASAP_HANDLE_RESOLUTION_RESPONSE messages,
send in a ASAP_HANDLE_RESOLUTION. without the user needing to send in a ASAP_HANDLE_RESOLUTION.
If the 'S' bit is set to '0' no dynamic updates are requested. If the 'S' bit is set to '0' no dynamic updates are requested.
Note that if a new Home ENRP server is adopted any 'dynamic update Note that if a new Home ENRP server is adopted any 'dynamic update
request' will need to be resent to the new Home ENPR server if the request' will need to be resent to the new Home ENPR server if the
endpoint would like to continue to recieve updates. In other words, endpoint would like to continue to receive updates. In other words,
the ENRP servers do NOT share state regarding which of its PU's are the ENRP servers do NOT share state regarding which of its PU's are
requesting automatic update of state. Thus upon change of Home ENRP requesting automatic update of state. Thus upon change of Home ENRP
Server the PU will need to resend a ASAP_HANDLE_RESOLUTION message Server the PU will need to resend a ASAP_HANDLE_RESOLUTION message
with the 'S' bit set to 1. Note also, that the 'S' bit will only with the 'S' bit set to 1. Note also, that the 'S' bit will only
cause dynamic update of a Pool when the Pool exists. If a negative cause dynamic update of a Pool when the Pool exists. If a negative
response is returned, no further updates to the Pool (when it is response is returned, no further updates to the Pool (when it is
created) will occur. created) will occur.
Pool Handle parameter: Pool Handle parameter:
See [8] section 3.7. See [I-D.ietf-rserpool-common-param]
2.2.6. ASAP_HANDLE_RESOLUTION_RESPONSE message 2.2.6. ASAP_HANDLE_RESOLUTION_RESPONSE message
The ASAP_HANDLE_RESOLUTION_RESPONSE message is sent in response by The ASAP_HANDLE_RESOLUTION_RESPONSE message is sent in response by
the Home ENRP server of the PU or PE that sent a the Home ENRP server of the PU or PE that sent a
ASAP_HANDLEE_RESOLUTION message or periodically upon Pool changes if ASAP_HANDLEE_RESOLUTION message or periodically upon Pool changes if
the PU as requested Dynamic updates. the PU as requested Dynamic updates.
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
skipping to change at page 13, line 34 skipping to change at page 13, line 34
A bit: A bit:
This bit is set to '1' if the ENRP server accepts the request to send This bit is set to '1' if the ENRP server accepts the request to send
automatic updates (i.e. the S bit was set on the request). If this automatic updates (i.e. the S bit was set on the request). If this
bit is set to '0' either the ENRP server does NOT support automatic bit is set to '0' either the ENRP server does NOT support automatic
update, it has resource issues and cannot supply this feature or the update, it has resource issues and cannot supply this feature or the
user did not request it. user did not request it.
Pool Handle parameter: Pool Handle parameter:
See [8] section 3.7. See [I-D.ietf-rserpool-common-param]
Overall PE Selection Policy (optional): Overall PE Selection Policy (optional):
See [8] section 3.6. See [I-D.ietf-rserpool-common-param]
This parameter can be present when the response is positive. If This parameter can be present when the response is positive. If
present, it indicates the overall pool member selection policy of the present, it indicates the overall pool member selection policy of the
pool. If not present, a round robin overall pool member selection pool. If not present, a round robin overall pool member selection
policy is assumed. This parameter is not present when the response policy is assumed. This parameter is not present when the response
is negative. is negative.
Note, any load policy parameter within a Pool Element Parameter (if Note, any load policy parameter within a Pool Element Parameter (if
present) MUST be ignored, and MUST NOT be used to determine the present) MUST be ignored, and MUST NOT be used to determine the
overall pool member selection policy. overall pool member selection policy.
Pool Element Parameters (optional): Pool Element Parameters (optional):
See [8] section 3.10. See [I-D.ietf-rserpool-common-param]
When the response is positive, an array of PE parameters are When the response is positive, an array of PE parameters are
included, indicating the current information about the PEs in the included, indicating the current information about the PEs in the
named pool. At least one PE parameter MUST be present. When the named pool. At least one PE parameter MUST be present. When the
response is negative, no PE parameters are included. response is negative, no PE parameters are included.
Operational Error (optional): Operational Error (optional):
See [8] section 3.10. See [I-D.ietf-rserpool-common-param]
The presence of this parameter indicates that the response is The presence of this parameter indicates that the response is
negative (the handle resolution request was rejected by the ENRP negative (the handle resolution request was rejected by the ENRP
server). The cause code in this parameter (if present) will indicate server). The cause code in this parameter (if present) will indicate
the reason the handle resolution request was rejected (e.g., the the reason the handle resolution request was rejected (e.g., the
requested pool handle was not found). The absence of this parmaeter requested pool handle was not found). The absence of this parmaeter
indicates that the response is positive. indicates that the response is positive.
2.2.7. ASAP_ENDPOINT_KEEP_ALIVE message 2.2.7. ASAP_ENDPOINT_KEEP_ALIVE message
skipping to change at page 14, line 49 skipping to change at page 14, line 48
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
H (Home ENRP server) flag H (Home ENRP server) flag
When set to '1', indicate that the ENRP server that sends this When set to '1', indicate that the ENRP server that sends this
message want to be the home ENRP server of the receiver of this message want to be the home ENRP server of the receiver of this
message. message.
Server Identifier: 32 bit (unsigned integer) Server Identifier: 32 bit (unsigned integer)
This is the ID of the ENRP server, as discussed in Section 3.2.1 of This is the ID of the ENRP server, as discussed in
ENRP [9]. [I-D.ietf-rserpool-enrp].
Pool Handle parameter: Pool Handle parameter:
See [8] section 3.7. See [I-D.ietf-rserpool-common-param] .
2.2.8. ASAP_ENDPOINT_KEEP_ALIVE_ACK message 2.2.8. ASAP_ENDPOINT_KEEP_ALIVE_ACK message
The ASAP_ENDPOINT_KEEP_ALIVE_ACK message is sent by a PE in response The ASAP_ENDPOINT_KEEP_ALIVE_ACK message is sent by a PE in response
to an ASAP_ENDPOINT_KEEP_ALIVE message sent by an ENRP Server. to an ASAP_ENDPOINT_KEEP_ALIVE message sent by an ENRP Server.
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type = 0x08 |0|0|0|0|0|0|0|0| Message Length | | Type = 0x08 |0|0|0|0|0|0|0|0| Message Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
: Pool Handle Parameter : : Pool Handle Parameter :
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
: PE Identifier Parameter : : PE Identifier Parameter :
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Pool Handle parameter: Pool Handle parameter:
See [8] section 3.7. See [I-D.ietf-rserpool-common-param].
PE Identifier parameter: PE Identifier parameter:
See [8] section 3.12. See [I-D.ietf-rserpool-common-param].
2.2.9. ASAP_ENDPOINT_UNREACHABLE message 2.2.9. ASAP_ENDPOINT_UNREACHABLE message
The ASAP_ENDPOINT_UNREACHABLE message is sent by either a PE or PU to The ASAP_ENDPOINT_UNREACHABLE message is sent by either a PE or PU to
its Home ENRP Server to report an unreachable PE. its Home ENRP Server to report an unreachable PE.
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type = 0x09 |0|0|0|0|0|0|0|0| Message Length | | Type = 0x09 |0|0|0|0|0|0|0|0| Message Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
: Pool Handle Parameter : : Pool Handle Parameter :
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
: PE Identifier Parameter : : PE Identifier Parameter :
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Pool Handle parameter: Pool Handle parameter:
See [8] section 3.7. See [I-D.ietf-rserpool-common-param].
PE Identifier parameter: PE Identifier parameter:
See [8] section 3.12. See [I-D.ietf-rserpool-common-param].
2.2.10. ASAP_SERVER_ANNOUNCE message 2.2.10. ASAP_SERVER_ANNOUNCE message
The ASAP_SERVER_ANNOUNCE message is sent by an ENRP Server such that The ASAP_SERVER_ANNOUNCE message is sent by an ENRP Server such that
PUs and PEs know the transport information necessary to connect to PUs and PEs know the transport information necessary to connect to
the ENRP server. the ENRP server.
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
skipping to change at page 16, line 31 skipping to change at page 16, line 31
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
: : : :
: ..... : : ..... :
: : : :
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
: Transport param #n : : Transport param #n :
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Server Identifier: 32 bit (unsigned integer) Server Identifier: 32 bit (unsigned integer)
This is the ID of the ENRP server, as discussed in Section 3.2.1 in This is the ID of the ENRP server, as discussed in
ENRP [9]. [I-D.ietf-rserpool-enrp].
Transport parameters (optional): Transport parameters (optional):
See [8] seections 3.3 and 3.4 for the SCTP and TCP Transport See [I-D.ietf-rserpool-common-param] for the SCTP and TCP Transport
parameters respectively. parameters.
Only SCTP and TCP Transport parameters are allowed for use within the Only SCTP and TCP Transport parameters are allowed for use within the
SERVER_ANNOUNCE message. SERVER_ANNOUNCE message.
2.2.11. ASAP_COOKIE message 2.2.11. ASAP_COOKIE message
The ASAP_COOKIE message is sent by a PE to a PU allowing the PE to The ASAP_COOKIE message is sent by a PE to a PU allowing the PE to
convey information it wishes to share using a control channel. convey information it wishes to share using a control channel.
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type = 0x0b |0|0|0|0|0|0|0|0| Message Length | | Type = 0x0b |0|0|0|0|0|0|0|0| Message Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
: Cookie Parameter : : Cookie Parameter :
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Cookie Parameter : Cookie Parameter :
See [8] section 3.11. See [I-D.ietf-rserpool-common-param].
2.2.12. ASAP_COOKIE_ECHO message 2.2.12. ASAP_COOKIE_ECHO message
The ASAP_COOKIE_ECHO message is sent by a PU to a new PE when it The ASAP_COOKIE_ECHO message is sent by a PU to a new PE when it
detects a failure with the current PE to aid in failover. The Cookie detects a failure with the current PE to aid in failover. The Cookie
Parameter sent by the PE is the latest one received from the failed Parameter sent by the PE is the latest one received from the failed
PE. PE.
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type = 0x0c |0|0|0|0|0|0|0|0| Message Length | | Type = 0x0c |0|0|0|0|0|0|0|0| Message Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
: Cookie Parameter : : Cookie Parameter :
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Cookie Parameter: Cookie Parameter:
See [8] section 3.11. See [I-D.ietf-rserpool-common-param].
2.2.13. ASAP_BUSINESS_CARD message 2.2.13. ASAP_BUSINESS_CARD message
The ASAP_BUSINESS_CARD message is sent by a PU to a PE or from a PE The ASAP_BUSINESS_CARD message is sent by a PU to a PE or from a PE
to a PU using a control channel to convey the pool handle and a to a PU using a control channel to convey the pool handle and a
preferred failover ordering. preferred failover ordering.
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
skipping to change at page 18, line 5 skipping to change at page 18, line 5
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
: Pool Element Parameter-1 : : Pool Element Parameter-1 :
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
: .. : : .. :
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
: Pool Element Parameter-N : : Pool Element Parameter-N :
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Pool Handle parameter: Pool Handle parameter:
See [8] section 3.7. See [I-D.ietf-rserpool-common-param].
Pool Element parameters: Pool Element parameters:
See [8] section 3.8. See [I-D.ietf-rserpool-common-param].
2.2.14. ASAP_ERROR message 2.2.14. ASAP_ERROR message
The ASAP_ERROR message is sent in response by an ASAP endpoint The ASAP_ERROR message is sent in response by an ASAP endpoint
receiving an unknown message or an unknown parameter to the sending receiving an unknown message or an unknown parameter to the sending
ASAP endpoint to report the problem or issue. ASAP endpoint to report the problem or issue.
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type = 0x0e |0|0|0|0|0|0|0|0| Message Length | | Type = 0x0e |0|0|0|0|0|0|0|0| Message Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
: Operational Error Parameter : : Operational Error Parameter :
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Operation Error parameter: Operation Error parameter:
See [8] section 3.10 See [I-D.ietf-rserpool-common-param].
When an ASAP endpoint receives an ASAP message with an unknown When an ASAP endpoint receives an ASAP message with an unknown
message type or a message of known type that contains an unknown message type or a message of known type that contains an unknown
parameter, it SHOULD handle the unknown message or the unknown parameter, it SHOULD handle the unknown message or the unknown
parameter according to the unrecognized message and parameter parameter according to the unrecognized message and parameter
handling rules defined in Section 3. handling rules defined in Section 3.
According to the rules, if an error report to the message sender is According to the rules, if an error report to the message sender is
needed, the ASAP endpoint that discovered the error SHOULD send back needed, the ASAP endpoint that discovered the error SHOULD send back
an ASAP_ERROR message which includes an Operation Error parameter an ASAP_ERROR message which includes an Operation Error parameter
with the proper cause code, cause length, and case specific with the proper cause code, cause length, and case specific
information. information.
3. Procedures 3. Procedures
This section will focus on the methods and procedures used by an This section will focus on the methods and procedures used by an
internal ASAP endpoint. Appropriate timers and recovery actions for internal ASAP endpoint. Appropriate timers and recovery actions for
failure detection and management are also discussed. Also please failure detection and management are also discussed. Also please
note that ASAP messages, sent between a PE and PU are identified by note that ASAP messages, sent between a PE and PU are identified by
an SCTP Payload Protocol Identifier (PPID) (or equivilant mapped an SCTP Payload Protocol Identifier (PPID).
function if using TCP).
3.1. Registration 3.1. Registration
When a PE wishes to initiate or join a server pool it MUST use the When a PE wishes to initiate or join a server pool it MUST use the
procedures outlined in this section for registration. Often, the procedures outlined in this section for registration. Often, the
registration will be triggered by a user request primitive (discussed registration will be triggered by a user request primitive (discussed
in Section 4.1). The PE MUST register using an SCTP association in Section 6.1). The PE MUST register using an SCTP association
established between itself and the Home ENRP server. If the PE has established between itself and the Home ENRP server. If the PE has
not established its Home ENRP server, it MUST follow the procedures not established its Home ENRP server, it MUST follow the procedures
specified in Section 3.6. specified in Section 3.6.
Once the PE's ASAP endpoint has established its Home ENRP server the Once the PE's ASAP endpoint has established its Home ENRP server the
following procedures MUST be followed to register: following procedures MUST be followed to register:
R1) The PE's SCTP endpoint used to communicate with the Home ENRP R1) The PE's SCTP endpoint used to communicate with the Home ENRP
server MUST be bound to all IP addresses that will be used by the server MUST be bound to all IP addresses that will be used by the
PE (irregardless of what transport protocol will be used to PE (irregardless of what transport protocol will be used to
service user requests to the PE). service user requests to the PE).
R2) The PE's ASAP endpoint MUST formulate an ASAP_REGISTRATION R2) The PE's ASAP endpoint MUST formulate an ASAP_REGISTRATION
message as defined in Section 2.2.1. In formulating the message, message as defined in Section 2.2.1. In formulating the message,
the PE MUST: the PE MUST:
R2.1) Fill in the Pool Handle Parameter to specify which server R2.1) Fill in the Pool Handle Parameter to specify which server
pool the ASAP endpoint wishes to join. pool the ASAP endpoint wishes to join.
R2.2) Fill in the PE identifier using a good quality randomly R2.2) Fill in the PE identifier using a good quality randomly
generated number (RFC4086 [11] provides some information on generated number ([RFC4086] provides some information on
randomness guidelines). randomness guidelines).
R2.3) Fill in the Registration Life time parameter with the R2.3) Fill in the Registration Life time parameter with the
number of seconds that this registration is valid for. Note a number of seconds that this registration is valid for. Note a
PE that wishes to continue service MUST re-register after the PE that wishes to continue service MUST re-register before the
registration expires. registration expires.
R2.4) Fill in a User Transport Parameter to specify the type of R2.4) Fill in a User Transport Parameter to specify the type of
transport and the data/control channel usage the PE is willing transport and the data/control channel usage the PE is willing
to support. Note, in joining an existing server pool, the PE to support. Note, in joining an existing server pool, the PE
MUST follow the overall transport type and overall data/control MUST follow the overall transport type and overall data/control
channel usage of the pool. Otherwise, the registration may be channel usage of the pool. Otherwise, the registration may be
rejected by the ENRP server. rejected by the ENRP server.
R2.5) Fill in the preferred Pool Member Selection Policy R2.5) Fill in the preferred Pool Member Selection Policy
skipping to change at page 21, line 5 skipping to change at page 20, line 50
Note that an implementation SHOULD keep a record of the number of Note that an implementation SHOULD keep a record of the number of
registration (and reregistration) attempts it makes in a local registration (and reregistration) attempts it makes in a local
variable that gets set to zero before the initial registration variable that gets set to zero before the initial registration
attempt to the Home ENRP server or after a successful re- attempt to the Home ENRP server or after a successful re-
registration.If repeated registration time-outs or failures occurs registration.If repeated registration time-outs or failures occurs
and the local count exceeds the Threshold 'MAX-REG-ATTEMPT' the and the local count exceeds the Threshold 'MAX-REG-ATTEMPT' the
implementation SHOULD report the error to its upper layer and stop implementation SHOULD report the error to its upper layer and stop
attempting registration. attempting registration.
The ENRP server handles the ASAP_REGISTRATION message according to
the following rules:
1. If the named pool does not exist in the handlespace, the ENRP
server MUST creates a new pool with that handle in the
handlespace and add the PE to the pool as its first PE;
When a new pool is created, the overall member selection policy
of the pool MUST be set to the policy type indicated by the first
PE, the overall pool transport type MUST be set to the transport
type indicated by the PE, and the overall pool data/control
channel configuration MUST be set to what is indicated in the
Transport Use field of the User Transport parameter by the
registering PE.
2. If the named pool already exists in the handlespace, but the
requesting PE is not currently a member of the pool, the ENRP
server will add the PE as a new member to the pool;
However, before adding the PE to the pool, the server MUST check
if the policy type, transport type, and transport usage indicated
by the registering PE is consistent with those of the pool. If
different, the ENRP server MUST reject the registration.
3. If the named pool already exists in the handlespace AND the
requesting PE is already a member of the pool, the ENRP server
SHOULD consider this as a re-registration case. The ENRP server
MUST perform the same tests on policy, transport type, transport
use, as described above. If the re-registration is accepted
after the test, the ENRP Server SHOULD replace the attributes of
the existing PE with the information carried in the received
ASAP_REGISTRATION message.
4. After accepting the registration, the ENRP server MUST assign
itself the owner of this PE. If this is a re-registration, the
ENRP server MUST take over ownership of this PE regardless of
whether the PE was previously owned by this server or by another
server. The ENRP server MUST also record the SCTP transport
address from which it received the ASAP_REGISTRATION in the ASAP
Transport parameter TLV inside the PE parameter of this PE.
5. The ENRP server may reject the registration due to other reasons
such as invalid values, lack of resource, authentication failure,
etc.
In all above cases, the ENRP server MUST reply to the requesting PE
with an ASAP_REGISTRATION_RESPONSE message. If the registration is
accepted, the ENRP server MUST set the 'R' flag in the
ASAP_REGISTRATION_RESPONSE to '0'. If the registration is rejected,
the ENRP server MUST indicate the rejection by setting the 'R' flag
in the ASAP_REGISTRATION_RESPONSE to '1'.
If the registration is rejected, the ENRP server SHOULD include the
proper error cause(s) in the ASAP_REGISTRATION_RESPONSE message.
If the registration is granted (either a new registration or a re-
registration case), the ENRP server MUST assign itself to be the home
ENRP server of the PE, i.e., to "own" the PE.
Implementation note: for better performance, the ENRP server may
find it both efficient and convenient to internally maintain two
separate PE lists or tables - one is for the PEs that are "owned"
by the ENRP server and the other for all the PEs owned by its
peer(s).
Moreover, if the registration is granted, the ENRP server MUST take
the handlespace update action to inform its peers about the change
just made. If the registration is denied, no message will be sent to
its peers.
3.2. Deregistration 3.2. Deregistration
In the event a PE wishes to deregister from its server pool (normally In the event a PE wishes to deregister from its server pool (normally
via an upper layer requests see Section 4.2), it SHOULD use the via an upper layer requests see Section 6.2), it SHOULD use the
following procedure. It should be noted that an alternate method of following procedure. It should be noted that an alternate method of
deregistration is to NOT re-register and to allow the registration deregistration is to NOT re-register and to allow the registration
life of the PE to expire. In this case a life of the PE to expire. In this case a
ASAP_DEREGISTRATION_RESPONSE message is sent to the PE's ASAP ASAP_DEREGISTRATION_RESPONSE message is sent to the PE's ASAP
endpoint to indicate the removal of the PE from the pool it endpoint to indicate the removal of the PE from the pool it
registered. registered.
When deregistering the PE SHOULD use the SCTP association that was When deregistering the PE SHOULD use the SCTP association that was
used for registration with its Home ENRP server. To deregister, the used for registration with its Home ENRP server. To deregister, the
PE's ASAP endpoint MUST take the following actions: PE's ASAP endpoint MUST take the following actions:
D1) Fill in the Pool Handle parameter of the ASAP_DEREGISTRATION D1) Fill in the Pool Handle parameter of the ASAP_DEREGISTRATION
message ( Section 2.2.2) using the same Pool Handle parameter sent message ( Section 2.2.2) using the same Pool Handle parameter sent
during registration. during registration.
D2) Fill in the PE Identifier parameter of the ASAP_DEREGISTRATION D2) Fill in the PE Identifier parameter of the ASAP_DEREGISTRATION
message. The identifier MUST be the same as used during message. The identifier MUST be the same as used during
registration. The use of the same Pool Handle and Pool Identifier registration. The use of the same Pool Handle and Pool Identifier
parameters used in registration allows the identity of the PE ASAP parameters used in registration allows the identity of the PE ASAP
endpoint be verified before deregisteration can occur. endpoint be verified before deregistration can occur.
D3) Send the ASAP_DEREGISTRATION message to the Home ENRP server D3) Send the ASAP_DEREGISTRATION message to the Home ENRP server
using the PE's SCTP association. using the PE's SCTP association.
D4) Start a T3-Deregistration timer. D4) Start a T3-Deregistration timer.
If the T3-Deregistration timer expires before receiving either a If the T3-Deregistration timer expires before receiving either a
ASAP_REGISTRATION_RESPONSE message, or a SEND.FAILURE notification ASAP_REGISTRATION_RESPONSE message, or a SEND.FAILURE notification
from the PE's SCTP endpint, the PE's ASAP endpoint shall start the from the PE's SCTP endpint, the PE's ASAP endpoint shall start the
ENRP Server Hunt procedure (see Section 3.6) in an attempt to get ENRP Server Hunt procedure (see Section 3.6) in an attempt to get
skipping to change at page 22, line 5 skipping to change at page 23, line 23
procedure. procedure.
At the reception of the ASAP_DEREGISTRATION_RESPONSE, the PE's ASAP At the reception of the ASAP_DEREGISTRATION_RESPONSE, the PE's ASAP
endpoint MUST stop the T3-deregistration timer. endpoint MUST stop the T3-deregistration timer.
It should be noted that after a successful deregistration the PE MAY It should be noted that after a successful deregistration the PE MAY
still receive requests for some period of time. The PE MAY wish to still receive requests for some period of time. The PE MAY wish to
remain active and service these requests or to exit and ignore these remain active and service these requests or to exit and ignore these
requests. requests.
Upon receiving the message, the ENRP server SHALL remove the PE from
its handlespace. Moreover, if the PE is the last one of the named
pool, the ENRP server will remove the pool from the handlespace as
well.
If the ENRP server fails to find any record of the PE in its
handlespace, it SHOULD consider the de-registration granted and
completed, and send an ASAP_DEREGISTRATION_RESPONSE message to the
PE.
The ENRP server may reject the de-registration request for various
reasons, such as invalid parameters, authentication failure, etc.
In response, the ENRP server MUST send an
ASAP_DEREGISTRATION_RESPONSE message to the PE. If the de-
registration is rejected, the ENRP server MUST indicate the rejection
by including the proper Operational Error parameter.
It should be noted that de-registration does not stop the PE from
sending or receiving application messages.
Once the de-registration request is granted AND the PE removed from
its local copy of the handlespace, the ENRP server MUST take the
handlespace update action to inform its peers about the change just
made. Otherwise, the ENRP server MUST NOT inform its peers.
3.3. Handle resolution 3.3. Handle resolution
At any time a PE or PU may wish to resolve a handle. This usually At any time a PE or PU may wish to resolve a handle. This usually
will occur when a ASAP Endpoint sends to a Pool handle ( will occur when a ASAP Endpoint sends to a Pool handle (
Section 4.5.1) to its home ENRP server or requests a cache population Section 6.5.1) to its home ENRP server or requests a cache population
(Section 4.3). It may also occur for other reasons (e.g. the (Section 6.3). It may also occur for other reasons (e.g. the
internal ASAP PE wishes to know its peers for sending a message to internal ASAP PE wishes to know its peers for sending a message to
all of them). When an ASAP Endpoint (PE or PU) wishes to resolve a all of them). When an ASAP Endpoint (PE or PU) wishes to resolve a
pool handle to a list of accesible transport addresses of the member pool handle to a list of accesible transport addresses of the member
PEs of the pool, it MUST take the following actions: PEs of the pool, it MUST take the following actions:
NR1) Fill in an ASAP_HANDLE_RESOLUTION message ( Section 2.2.5) with NR1) Fill in an ASAP_HANDLE_RESOLUTION message ( Section 2.2.5) with
the Pool Handle to be resolved. the Pool Handle to be resolved.
NR2) If the endpoint does not have a Home ENRP server start the ENRP NR2) If the endpoint does not have a Home ENRP server start the ENRP
Server Hunt procedures specified in Section 3.6 to obtain one. Server Hunt procedures specified in Section 3.6 to obtain one.
skipping to change at page 23, line 5 skipping to change at page 24, line 45
ASAP endpoint MUST stop its T1-ENRPrequest timer. After stopping the ASAP endpoint MUST stop its T1-ENRPrequest timer. After stopping the
T1-ENRPrequest timer the ASAP endpoint SHOULD process the message as T1-ENRPrequest timer the ASAP endpoint SHOULD process the message as
appropriate (e.g. populate a local cache, give the response to the appropriate (e.g. populate a local cache, give the response to the
ASAP user, and/or use the response to send the ASAP users message). ASAP user, and/or use the response to send the ASAP users message).
Note that some ASAP endpoints MAY use a cache to minimize the number Note that some ASAP endpoints MAY use a cache to minimize the number
of handle resolutions sent. If a cache is used, it SHOULD: of handle resolutions sent. If a cache is used, it SHOULD:
C1) Be consulted before sending a handle resolution. C1) Be consulted before sending a handle resolution.
C2) Have a stale timeout timer associated with the cache. If the C2) Have a stale timeout timer associated with each cache entry. If
cache is determined to be stale upon a cache hit, a handle the cache entry is determined to be stale upon a cache hit, a
resolution message SHOULD be sent so the cache can be updated. handle resolution message SHOULD be sent so the cache can be
updated.
C3) In the case of a stale cache the implementation may in parallel C3) In the case of a stale cache entry the implementation may in
update the cache and answer the request or it may block the user parallel update the cache and answer the request or it may block
and wait for an updated cache before proceeding with the users the user and wait for an updated cache before proceeding with the
request. users request.
C4) If the cache is NOT stale, the endpoint SHOULD NOT send a handle C4) If the cache entry is NOT stale, the endpoint SHOULD NOT send a
resolution request but instead SHOULD use the entry from the handle resolution request but instead SHOULD use the entry from
cache. the cache.
It should be noted that the impact of using a cache depends on the
policy and the requirements of the application. For some
applications cache-usage can increase the performance of the system,
for some it can decrease it.
An ENRP server SHOULD be prepared to receive ASAP_HANDLE_RESOLUTION
requests from PUs either over an SCTP association on the well-know
SCTP port, or over a TCP connection on the well-know TCP port.
Upon reception of the ASAP_HANDLE_RESOLUTION message, the ENRP server
MUST first look up the pool handle in its handlespace. If the pool
exits, the home ENRP server MUST compose and send back an
ASAP_HANDLE_RESOLUTION_RESPONSE message to the requesting PU.
In the response message, the ENRP server SHOULD list all the PEs
currently registered in this pool, in a list of PE parameters. The
ENRP server MUST also include a pool member selection policy
parameter to indicate the overall member selection policy for the
pool, if the current pool member selection policy is not round-robin.
If the named pool does not exist in the handlespace, the ENRP server
MUST reject the handle resolution request by responding with an
ASAP_HANDLE_RESOLUTION_RESPONSE message carrying a Unknown Poor
Handle error.
3.4. Endpoint keep alive 3.4. Endpoint keep alive
The ASAP_ENDPOINT_KEEP_ALIVE message is sent by an ENRP server to a The ASAP_ENDPOINT_KEEP_ALIVE message is sent by an ENRP server to a
PE in order to verify it is reachable. If the transport level heart PE in order to verify it is reachable. If the transport level heart
beat mechanism is insufficient, this message can be used in a heart beat mechanism is insufficient, this message can be used in a heart
beat mechanism for the ASAP level whose goal is determining the beat mechanism for the ASAP level whose goal is determining the
health status of the ASAP level in a timely fashion. (The transport health status of the ASAP level in a timely fashion. (The transport
level heart beat mechanism may be insufficient due to either the time level heart beat mechanism may be insufficient due to either the time
outs or the heart beat interval being set too long, or, that the outs or the heart beat interval being set too long, or, that the
skipping to change at page 24, line 21 skipping to change at page 26, line 36
KA2.3) Send the ASAP_ENDPOINT_KEEP_ALIVE_ACK message via the KA2.3) Send the ASAP_ENDPOINT_KEEP_ALIVE_ACK message via the
appropriate SCTP association for the ENRP server which sent the appropriate SCTP association for the ENRP server which sent the
ASAP_ENDPOINT_KEEP_ALIVE message. ASAP_ENDPOINT_KEEP_ALIVE message.
KA2.4) If the 'H' flag in the received ASAP_ENDPOINT_KEEP_ALIVE KA2.4) If the 'H' flag in the received ASAP_ENDPOINT_KEEP_ALIVE
message is set, and the Server Identifier in the message is NOT message is set, and the Server Identifier in the message is NOT
the identity of your Home ENRP server (or it is not set e.g you the identity of your Home ENRP server (or it is not set e.g you
have a no Home ENRP server) adopt the sender of the have a no Home ENRP server) adopt the sender of the
ASAP_ENDPOINT_KEEP_ALIVE message as the new home ENRP server. ASAP_ENDPOINT_KEEP_ALIVE message as the new home ENRP server.
3.5. Reporting unreachable endpoints 3.5. Unreachable endpoints
Occasionally, an ASAP endpoint may realize a PE is unreachable. This Occasionally, an ASAP endpoint may realize a PE is unreachable. This
may occur by a specific SCTP error realized by the ASAP endpoint or may occur by a specific SCTP error realized by the ASAP endpoint or
via an ASAP user report via the Transport.Failure Primitive via an ASAP user report via the Transport.Failure Primitive
(Section 4.9.2). In either case, the ASAP endpoint SHOULD report the (Section 6.9.2). In either case, the ASAP endpoint SHOULD report the
unavailability of the PE by sending an ASAP_ENDPOINT_UNREACHABLE unavailability of the PE by sending an ASAP_ENDPOINT_UNREACHABLE
message to its Home ENRP server. Before sending the message to any ENRP server. Before sending the
ASAP_ENDPOINT_UNREACHABLE message, the ASAP Endpoint should fill in ASAP_ENDPOINT_UNREACHABLE message, the ASAP Endpoint should fill in
the Pool Handle parameter and PE identifier parameter of the the Pool Handle parameter and PE identifier parameter of the
unreachable endpoint. If the sender is a PE, the message MUST be unreachable endpoint. If the sender is a PE, the message MUST be
sent via SCTP. It should be noted that an ASAP endpoint MUST report sent via SCTP. It should be noted that an ASAP endpoint MUST report
no more than once each time it encounters such an event. no more than once each time it encounters such an event.
Additionally, when processing a Transport.Failure Primitive Additionally, when processing a Transport.Failure Primitive
(Section 4.9.2) the ASAP endpoint MUST NOT send an (Section 6.9.2) the ASAP endpoint MUST NOT send an
ASAP_ENDPOINT_UNREACHABLE message unless the user has made a previous ASAP_ENDPOINT_UNREACHABLE message unless the user has made a previous
request to send data to the PE specified by the primitive. request to send data to the PE specified by the primitive.
Upon the reception of an ASAP_ENDPOINT_UNREACHABLE message, a server
MUST immediately send a point-to-point ASAP_ENDPOINT_KEEP_ALIVE
message to the PE in question (the 'H' flag in the message SHOULD be
set to '0' in this case). If this ASAP_ENDPOINT_KEEP_ALIVE fails
(e.g., it results in an SCTP SEND.FAILURE notification), the ENRP
server MUST consider the PE as truly unreachable and MUST remove the
PE from its handlespace.
If the ASAP_ENDPOINT_KEEP_ALIVE message is transmitted successfully
to the PE, the ENRP server MUST retain the PE in its handlespace.
Moreover, the server SHOULD keep a counter to record how many
ASAP_ENDPOINT_UNREACHABLE messages it has received reporting
reachability problem relating to this PE. If the counter exceeds the
protocol threshold MAX-BAD-PE-REPORT, the ENRP server SHOULD remove
the PE from its handlespace.
Optionally, an ENRP server may also periodically send point-to-point
ASAP_ENDPOINT_KEEP_ALIVE (with 'H' flag set to '0') messages to each
of the PEs owned by the ENRP server in order to check their
reachability status. If the send of ASAP_ENDPOINT_KEEP_ALIVE to a PE
fails, the ENRP server MUST consider the PE as unreachable and MUST
remove the PE from its handlespace . Note, if an ENRP server owns a
large number of PEs, the implementation should pay attention not to
flood the network with bursts of ASAP_ENDPOINT_KEEP_ALIVE messages.
Instead, the implementation MUST distribute the
ASAP_ENDPOINT_KEEP_ALIVE message traffic over a time period.
3.6. ENRP server hunt procedures 3.6. ENRP server hunt procedures
Each PU and PE manages a list of transport addresses of ENRP servers Each PU and PE manages a list of transport addresses of ENRP servers
it knows about. it knows about.
If multicast capabilities are used within the operational scope an If multicast capabilities are used within the operational scope an
ENRP server MUST send periodically every T6-Serverannounce an ENRP server MUST send periodically every (N+1)*T6-Serverannounce an
ASAP_SERVER_ANNOUNCE message (Section 2.2.10) which includes all the ASAP_SERVER_ANNOUNCE message (Section 2.2.10) which includes all the
transport addresses available for ASAP communication on the multicast transport addresses available for ASAP communication on the multicast
ENRP client channel. ENRP client channel where N is the number of ENRP servers the server
has found via receiving ASAP_SERVER_ANNOUNCE messages. This should
result in a message rate of approximately 1 ASAP_SERVER_ANNOUNCE per
T6-Serverannounce.
If an ASAP_SERVER_ANNOUNCE message is received by a PU or PE, it If an ASAP_SERVER_ANNOUNCE message is received by a PU or PE, it
SHOULD insert all new included transport addresses into its list of SHOULD insert all new included transport addresses into its list of
ENRP server addresses and start a T7-ENRPoutdate timer for each ENRP server addresses and start a T7-ENRPoutdate timer for each
address. For all already known included transport addresses, the T7- address. For all already known included transport addresses, the T7-
ENRPoutdate timer MUST be restarted for each address. If no ENRPoutdate timer MUST be restarted for each address. If no
transport parameters are included in the ASAP_SERVER_ANNOUNCE transport parameters are included in the ASAP_SERVER_ANNOUNCE
message, the SCTP transport protocol is assumed to be used and the message, the SCTP transport protocol is assumed to be used and the
source IP address and the IANA registered ASAP port number is used source IP address and the IANA registered ASAP port number is used
for communication with the ENRP server. If a T7-ENRPoutdate timer for communication with the ENRP server. If a T7-ENRPoutdate timer
skipping to change at page 26, line 27 skipping to change at page 29, line 27
or PU tries to communicate with an ENRP server: or PU tries to communicate with an ENRP server:
A) SCTP send failure A) SCTP send failure
B) T1-ENRPrequest timer expiration B) T1-ENRPrequest timer expiration
C) Registration failure C) Registration failure
3.7.1. SCTP Send Failure 3.7.1. SCTP Send Failure
This communication failure indicates that the SCTP layer was uanble This communication failure indicates that the SCTP layer was unable
to deliver a message sent to an ENRP server. In other words, the to deliver a message sent to an ENRP server. In other words, the
ENRP server is unreachable. ENRP server is unreachable.
In such a case, the ASAP endpoint should not re-send the In such a case, the ASAP endpoint should not re-send the
undeliverable message. Instead, it should discard the message and undeliverable message. Instead, it should discard the message and
start the ENRP server hunt procedure as described in Section 3.6 . start the ENRP server hunt procedure as described in Section 3.6 .
After finding a new Home ENRP server, the ASAP endpoint should After finding a new Home ENRP server, the ASAP endpoint should
reconstruct and retransmit the request. reconstruct and retransmit the request.
Note that an ASAP endpoint MAY also choose to NOT discard the Note that an ASAP endpoint MAY also choose to NOT discard the
skipping to change at page 27, line 22 skipping to change at page 30, line 22
3.8. Cookie handling procedures 3.8. Cookie handling procedures
Whenever a PE wants, and a control channel exists, it can send an Whenever a PE wants, and a control channel exists, it can send an
ASAP_COOKIE message to a PU via the control channel. The PU's ASAP ASAP_COOKIE message to a PU via the control channel. The PU's ASAP
endpoint stores the Cookie parameter and discards an older cookie if endpoint stores the Cookie parameter and discards an older cookie if
it is previously stored. it is previously stored.
Note: a control channel is a communication channel between a PU and Note: a control channel is a communication channel between a PU and
PE that does not end in data passed to the user. This is PE that does not end in data passed to the user. This is
accomplished with SCTP by using a PPID to seperate the ASAP messages accomplished with SCTP by using a PPID to separate the ASAP messages
(Cookie and Business Card) from normal data messages. (Cookie and Business Card) from normal data messages.
If the PU's ASAP endpoint detects a failure and initiates a failover If the PU's ASAP endpoint detects a failure and initiates a failover
to a different PE, it SHOULD send the lastest received cookie to a different PE, it SHOULD send the lastest received cookie
parameter in an ASAP_COOKIE_ECHO message to the new PE. Upper layers parameter in an ASAP_COOKIE_ECHO message to the new PE as the first
may be involved in the failover procedure. message on the control channel. Upper layers may be involved in the
failover procedure.
The cookie handling procedure can be used for state sharing. The cookie handling procedure can be used for state sharing.
Therefore a cookie should be signed by the sending PE ASAP endpoint Therefore a cookie should be signed by the sending PE ASAP endpoint
and the cookie should be verified by the receiving PE's ASAP and the cookie should be verified by the receiving PE's ASAP
endpoint. The details of the verification procedure are out of scope endpoint. The details of the verification procedure are out of scope
for this document. It is only important that the PU always stores for this document. It is only important that the PU always stores
the last received Cookie Parameter and sends that back unmodified in the last received Cookie Parameter and sends that back unmodified in
case of a PE failure. case of a PE failure.
3.9. Business Card handling procedures 3.9. Business Card handling procedures
skipping to change at page 28, line 8 skipping to change at page 31, line 9
communication as been established between a PE and PU, a new communication as been established between a PE and PU, a new
ASAP_BUSINESS_CARD message may be sent at any time by either entity ASAP_BUSINESS_CARD message may be sent at any time by either entity
to update its failover order. to update its failover order.
The ASAP_BUSINESS_CARD message serves two purposes. First it lists The ASAP_BUSINESS_CARD message serves two purposes. First it lists
the pool handle. For a PU which is part of a PU/PE combination which the pool handle. For a PU which is part of a PU/PE combination which
is contacting a PE this is essential so that the PE learns the pool is contacting a PE this is essential so that the PE learns the pool
handle of the PU/PE combination requesting service. Secondly the handle of the PU/PE combination requesting service. Secondly the
ASAP_BUSINESS_CARD message tells the receiving entity a failover ASAP_BUSINESS_CARD message tells the receiving entity a failover
order that is recommended to follow. This should facilitate order that is recommended to follow. This should facilitate
rendezvous between entities that have been working togehter as well rendezvous between entities that have been working together as well
to control the load redistribution upon the failure of any PE. to control the load redistribution upon the failure of any PE.
Upon receipt of an ASAP_BUSINESS_CARD message (see Section 2.2.13) Upon receipt of an ASAP_BUSINESS_CARD message (see Section 2.2.13)
the receiving ASAP endpoint SHOULD: the receiving ASAP endpoint SHOULD:
BC1) Unpack the message and if no entry exists in the translation BC1) Unpack the message and if no entry exists in the translation
cache of the receiving ASAP endpoint for the pool handle listed cache of the receiving ASAP endpoint for the pool handle listed
within the ASAP_BUSINESS_CARD message perform a within the ASAP_BUSINESS_CARD message perform a
ASAP_HANDLE_RESOLUTION for that pool handle. If the translation ASAP_HANDLE_RESOLUTION for that pool handle. If the translation
cache does hold an entry for the pool handle, then it may be cache does hold an entry for the pool handle, then it may be
necessary to update the peer endpoint. necessary to update the peer endpoint.
BC2) Unpack the message and populate a preferred list for failover BC2) Unpack the message and populate a preferred list for failover
order. If the peers PE should fail this preferred list will be order. If the peers PE should fail this preferred list will be
used guide the ASAP endpoint in the selection of an alternate PE. used guide the ASAP endpoint in the selection of an alternate PE.
4. The ASAP Interfaces 4. Roles of Endpoints
A PU MUST implement the handling of ASAP_HANDLE_RESOLUTION, and
ASAP_HANDLE_RESOLUTION_RESPONSE messages. Furthermore it MUST
support the handling of ASAP_ERROR messages. It MAY implement the
handling of ASAP_COOKIE, ASAP_COOKIE_ECHO, and ASAP_BUSINESS_CARD
messages. It MAY also implement the handling of ASAP_SERVER_ANNOUNCE
messages.
A PE MUST implement the handling of ASAP_REGISTRATION,
ASAP_DEREGISTRATION ASAP_REGISTRATION_RESPONSE, and
ASAP_DEREGISTRATION_RESPONSE messages. Furthermore it MUST support
the handling of ASAP_ENDPOINT_KEEP_ALIVE,
ASAP_ENDPOINT_KEEP_ALIVE_ACK, ASAP_ENDPOINT_UNREACHABLE, and
ASAP_ERROR messages. It SHOULD support the handling of ASAP_COOKIE,
ASAP_COOKIE_ECHO, and ASAP_BUSINESS_CARD messages. Furthermore it
MAY support the handling of ASAP_SERVER_ANNOUNCE messages.
An ENRP server MUST implement the handling of ASAP_REGISTRATION,
ASAP_DEREGISTRATION ASAP_REGISTRATION_RESPONSE, and
ASAP_DEREGISTRATION_RESPONSE messages. Furthermore it MUST support
the handling of ASAP_ENDPOINT_KEEP_ALIVE,
ASAP_ENDPOINT_KEEP_ALIVE_ACK, ASAP_ENDPOINT_UNREACHABLE, and
ASAP_ERROR messages. Furthermore it MAY support the handling of
ASAP_SERVER_ANNOUNCE messages.
If a node acts as a PU and a PE, it MUST fullfil both roles.
5. SCTP considerations
Each ASAP message is considered as an SCTP user message. The PPID
registered for ASAP SHOULD be used. The SCTP port used at the ENRP
server might be preconfigured or announced in the
ASAP_SERVER_ANNOUNCE message or the well known ASAP port.
ASAP messages beloning to the control channel MUST be sent using the
PPID registered for ASAP. Messages belonging to the data channel
MUST NOT use the PPID registered for ASAP.
6. The ASAP Interfaces
This chapter will focus primarily on the primitives and notifications This chapter will focus primarily on the primitives and notifications
that form the interface between the ASAP-user and ASAP and that that form the interface between the ASAP-user and ASAP and that
between ASAP and its lower layer transport protocol (e.g., SCTP). between ASAP and its lower layer transport protocol (e.g., SCTP).
Note, the following primitive and notification descriptions are shown Note, the following primitive and notification descriptions are shown
for illustrative purposes. We believe that including these for illustrative purposes. We believe that including these
descriptions in this document is important to the understanding of descriptions in this document is important to the understanding of
the operation of many aspects of ASAP. But an ASAP implementation is the operation of many aspects of ASAP. But an ASAP implementation is
not required to use the exact syntax described in this section. not required to use the exact syntax described in this section.
An ASAP User passes primitives to the ASAP sub-layer to request An ASAP User passes primitives to the ASAP sub-layer to request
certain actions. Upon the completion of those actions or upon the certain actions. Upon the completion of those actions or upon the
detection of certain events, the ASAP layer will notify the ASAP detection of certain events, the ASAP layer will notify the ASAP
user. user.
4.1. Registration.Request Primitive 6.1. Registration.Request Primitive
Format: registration.request(poolHandle, Format: registration.request(poolHandle,
User Transport parameter(s)) User Transport parameter(s))
The poolHandle parameter contains a NULL terminated ASCII string of The poolHandle parameter contains a NULL terminated ASCII string of
fixed length. The optional User Transport parameter(s) indicate fixed length. The optional User Transport parameter(s) indicate
specific transport parameters and types to register with. If this specific transport parameters and types to register with. If this
optional parameter is left off, then the SCTP endpoint used to optional parameter is left off, then the SCTP endpoint used to
communicate with the ENRP server is used as the default User communicate with the ENRP server is used as the default User
Transport parameter. Note that any IP address contained within a Transport parameter. Note that any IP address contained within a
User Transport parameter MUST be a bound IP address in the SCTP User Transport parameter MUST be a bound IP address in the SCTP
endpoint used to communicate with the ENRP server. endpoint used to communicate with the ENRP server.
The ASAP user invokes this primitive to add itself to the The ASAP user invokes this primitive to add itself to the
handlespace, thus becoming a Pool Element of a pool. The ASAP user handlespace, thus becoming a Pool Element of a pool. The ASAP user
must register itself with the ENRP server by using this primitive must register itself with the ENRP server by using this primitive
before other ASAP users using the handlespace can send message(s) to before other ASAP users using the handlespace can send message(s) to
this ASAP user by Pool Handle or by PE handle (see Section 4.5.1 and this ASAP user by Pool Handle or by PE handle (see Section 6.5.1 and
Section 4.5.3). Section 6.5.3).
In response to the registration primitive, the ASAP endpoint will In response to the registration primitive, the ASAP endpoint will
send an ASAP_REGISTRATION message to the home ENRP server (See send an ASAP_REGISTRATION message to the home ENRP server (See
Section 2.2.1 and Section 3.1), and start a T2-registration timer. Section 2.2.1 and Section 3.1), and start a T2-registration timer.
4.2. Deregistration.Request Primitive 6.2. Deregistration.Request Primitive
Format: deregistration.request(poolHandle) Format: deregistration.request(poolHandle)
The ASAP PE invokes this primitive to remove itself from the Server The ASAP PE invokes this primitive to remove itself from the Server
Pool. This should be used as a part of the graceful shutdown process Pool. This should be used as a part of the graceful shutdown process
by the application. by the application.
A ASAP_DEREGISTRATION message will be sent by ASAP endpoint to the A ASAP_DEREGISTRATION message will be sent by ASAP endpoint to the
home ENRP server (see Section 2.2.2 and Section 3.2). home ENRP server (see Section 2.2.2 and Section 3.2).
4.3. CachePopulateRequest Primitive 6.3. CachePopulateRequest Primitive
Format: cache_populate_request([Pool-Handle | Format: cache_populate_request([Pool-Handle |
Pool-Element-Handle]) Pool-Element-Handle])
If the address type is a Pool handle and a local handle translation If the address type is a Pool handle and a local handle translation
cache exists, the ASAP endpoint should initiate a mapping information cache exists, the ASAP endpoint should initiate a mapping information
query by sending an ASAP_HANDLE_RESOLUTION message on the Pool handle query by sending an ASAP_HANDLE_RESOLUTION message on the Pool handle
and update it local cache when the response comes back from the ENRP and update it local cache when the response comes back from the ENRP
server. server.
If a Pool-Element-Handle is passed then the Pool Handle is unpacked If a Pool-Element-Handle is passed then the Pool Handle is unpacked
from the Pool-Element-Handle and the ASAP_HANDLE_RESOLUTION message from the Pool-Element-Handle and the ASAP_HANDLE_RESOLUTION message
is sent to the ENRP server for resolution. When the response message is sent to the ENRP server for resolution. When the response message
returns from the ENRP server the local cache is updated. returns from the ENRP server the local cache is updated.
Note that if the ASAP service does NOT support a local cache this Note that if the ASAP service does NOT support a local cache this
primitive performs NO action. primitive performs NO action.
4.4. CachePurgeRequest Primitive 6.4. CachePurgeRequest Primitive
Format: cache_purge_request([Pool-Handle | Pool-Element-Handle]) Format: cache_purge_request([Pool-Handle | Pool-Element-Handle])
If the user passes a Pool handle and local handle translation cache If the user passes a Pool handle and local handle translation cache
exists, the ASAP endpoint should remove the mapping information on exists, the ASAP endpoint should remove the mapping information on
the Pool handle from its local cache. If the user passes a Pool- the Pool handle from its local cache. If the user passes a Pool-
Element-Handle then the Pool handle within is used for the Element-Handle then the Pool handle within is used for the
cache_purge_request. cache_purge_request.
Note that if the ASAP service does NOT support a local cache this Note that if the ASAP service does NOT support a local cache this
primitive performs NO action. primitive performs NO action.
4.5. DataSendRequest Primitive 6.5. DataSendRequest Primitive
Format: data_send_request(destinationAddress, typeOfAddress, Format: data_send_request(destinationAddress, typeOfAddress,
message, sizeOfMessage, Options); message, sizeOfMessage, Options);
This primitive requests ASAP to send a message to some specified Pool This primitive requests ASAP to send a message to some specified Pool
or Pool Element within the current Operational scope. or Pool Element within the current Operational scope.
Depending on the address type used for the send request, the senders Depending on the address type used for the send request, the senders
ASAP endpoint may perform address translation and Pool Element ASAP endpoint may perform address translation and Pool Element
selection before sending the message out. This also MAY dictate the selection before sending the message out. This also MAY dictate the
creation of a local transport endpoint in order to meet the required creation of a local transport endpoint in order to meet the required
transport type. transport type.
The data_send_request primitive can take different forms of address The data_send_request primitive can take different forms of address
types as described in the following sections. types as described in the following sections.
4.5.1. Sending to a Pool Handle 6.5.1. Sending to a Pool Handle
In this case the destinationAddress and typeOfAddress together In this case the destinationAddress and typeOfAddress together
indicates a pool handle. indicates a pool handle.
This is the simplest form of send_data_request primitive. By This is the simplest form of send_data_request primitive. By
default, this directs ASAP to send the message to one of the Pool default, this directs ASAP to send the message to one of the Pool
Elements in the specified pool. Elements in the specified pool.
Before sending the message out to the pool, the senders ASAP endpoint Before sending the message out to the pool, the senders ASAP endpoint
MUST first perform a pool handle to address translation. It may also MUST first perform a pool handle to address translation. It may also
skipping to change at page 31, line 42 skipping to change at page 36, line 42
Once the necessary mapping information arrives from the ENRP server, Once the necessary mapping information arrives from the ENRP server,
the senders ASAP will: the senders ASAP will:
A) map the pool handle into a list of transport addresses of the A) map the pool handle into a list of transport addresses of the
destination PE(s), destination PE(s),
B) if multiple PEs exist in the pool, ASAP will choose one of them B) if multiple PEs exist in the pool, ASAP will choose one of them
and transmit the message to it. In that case, the choice of the and transmit the message to it. In that case, the choice of the
PE is made by ASAP endpoint of the sender based on the server PE is made by ASAP endpoint of the sender based on the server
pooling policy as discussed in Section 4.5.2 pooling policy as discussed in Section 6.5.2
C) Optionally create any transport endpoint that may be needed to C) Optionally create any transport endpoint that may be needed to
communicate with the PE selected. communicate with the PE selected.
D) if no transport association or connection exists towards the D) if no transport association or connection exists towards the
destination PE, ASAP will establish any needed transport state, destination PE, ASAP will establish any needed transport state,
E) send out the queued message(s) to the appropriate transport E) send out the queued message(s) to the appropriate transport
connection using the appropriate send mechanism (e.g. for SCTP the connection using the appropriate send mechanism (e.g. for SCTP the
SEND primitive in RFC2960 [3] would be used), and, SEND primitive in [RFC4960] would be used), and,
F) if the local cache is implemented, append/update the local cache F) if the local cache is implemented, append/update the local cache
with the mapping information received in the ENRP server's with the mapping information received in the ENRP server's
response. Also, record the local transport information (e.g. the response. Also, record the local transport information (e.g. the
SCTP association id) if any new transport state was created. SCTP association id) if any new transport state was created.
For more on the ENRP server request procedures see ENRP [9]. For more on the ENRP server request procedures see
[I-D.ietf-rserpool-enrp].
Optionally, the ASAP endpoint of the sender may return a Pool Element Optionally, the ASAP endpoint of the sender may return a Pool Element
handle of the selected PE to the application after sending the handle of the selected PE to the application after sending the
message. This PE handle can then be used for future transmissions to message. This PE handle can then be used for future transmissions to
that same PE (see Section 4.5.3). that same PE (see Section 6.5.3).
Section 3.7 defines the fail-over procedures for cases where the Section 3.7 defines the fail-over procedures for cases where the
selected PE is found unreachable. selected PE is found unreachable.
4.5.2. Pool Element Selection 6.5.2. Pool Element Selection
Each time an ASAP user sends a message to a pool that contains more Each time an ASAP user sends a message to a pool that contains more
than one PE, the senders ASAP endpoint must select one of the PEs in than one PE, the senders ASAP endpoint must select one of the PEs in
the pool as the receiver of the current message. The selection is the pool as the receiver of the current message. The selection is
done according to the current server pooling policy of the pool to done according to the current server pooling policy of the pool to
which the message is sent. which the message is sent.
Note, no selection is needed if the ASAP_SEND_TOALL option is set Note, no selection is needed if the ASAP_SEND_TOALL option is set
(see Section 4.5.5). (see Section 6.5.5).
Together with the server pooling policy, each PE can also specify a Together with the server pooling policy, each PE can also specify a
Policy Value for itself at the registration time. The meaning of the Policy Value for itself at the registration time. The meaning of the
policy value depends on the current server pooling policy of the policy value depends on the current server pooling policy of the
group. A PE can also change its policy value whenever it desires, by group. A PE can also change its policy value whenever it desires, by
re-registering itself with the handlespace with a new policy value. re-registering itself with the handlespace with a new policy value.
Re-registration shall be done by simply sending another Re-registration shall be done by simply sending another
ASAP_REGISTRATION to its home ENRP server (See Section 2.2.1). ASAP_REGISTRATION to its home ENRP server (See Section 2.2.1).
One basic policy is defined in this document, others can be found in One basic policy is defined in this document, others can be found in
[7] [I-D.ietf-rserpool-policies]
4.5.2.1. Round Robin Policy 6.5.2.1. Round Robin Policy
When an ASAP endpoint sends messages by Pool Handle and Round-Robin When an ASAP endpoint sends messages by Pool Handle and Round-Robin
is the current policy of that Pool, the ASAP endpoint of the sender is the current policy of that Pool, the ASAP endpoint of the sender
will select the receiver for each outbound message by round-Robining will select the receiver for each outbound message by round-Robining
through all the registered PEs in that Pool, in an attempt to achieve through all the registered PEs in that Pool, in an attempt to achieve
an even distribution of outbound messages. Note that in a large an even distribution of outbound messages. Note that in a large
server pool, the ENRP server MAY not send back all PEs to the ASAP server pool, the ENRP server MAY not send back all PEs to the ASAP
client. In this case the client or PU will be performing a round client. In this case the client or PU will be performing a round
robin policy on a subset of the entire Pool. robin policy on a subset of the entire Pool.
4.5.3. Sending to a Pool Element Handle 6.5.3. Sending to a Pool Element Handle
In this case the destinationAddress and typeOfAddress together In this case the destinationAddress and typeOfAddress together
indicate an ASAP Pool Element handle. indicate an ASAP Pool Element handle.
This requests the ASAP endpoint to deliver the message to the PE This requests the ASAP endpoint to deliver the message to the PE
identified by the Pool Element handle. identified by the Pool Element handle.
The Pool Element handle should contain the Pool Handle and a The Pool Element handle should contain the Pool Handle and a
destination transport address of the destination PE or the Pool destination transport address of the destination PE or the Pool
Handle and the transport type. Other implementation dependent Handle and the transport type. Other implementation dependent
skipping to change at page 33, line 47 skipping to change at page 38, line 48
i) ask the home ENRP server for handle resolution on pool handle i) ask the home ENRP server for handle resolution on pool handle
by sending an ASAP_HANDLE_RESOLUTION message (see by sending an ASAP_HANDLE_RESOLUTION message (see
Section 2.2.5), and Section 2.2.5), and
ii) use the response to update the local cache. ii) use the response to update the local cache.
If the pool handle is in the cache, the endpoint will only If the pool handle is in the cache, the endpoint will only
update the pool handle if the cache is stale. A stale cache is update the pool handle if the cache is stale. A stale cache is
indicated by it being older than the protocol parameter indicated by it being older than the protocol parameter
'stale.cache.value' (see Section 5.2). 'stale.cache.value' (see Section 7.2).
Section 3.5 and Section 4.9 defines the fail-over procedures for Section 3.5 and Section 6.9 defines the fail-over procedures for
cases where the PE pointed to by the Pool Element handle is found cases where the PE pointed to by the Pool Element handle is found
unreachable. unreachable.
Optionally, the ASAP endpoint may return the actual Pool Element Optionally, the ASAP endpoint may return the actual Pool Element
handle to which the message was sent (this may be different from the handle to which the message was sent (this may be different from the
Pool Element handle specified when the primitive is invoked, due to Pool Element handle specified when the primitive is invoked, due to
the possibility of automatic fail-over). the possibility of automatic fail-over).
4.5.4. Send by Transport Address 6.5.4. Send by Transport Address
In this case the destinationAddress and typeOfAddress together In this case the destinationAddress and typeOfAddress together
indicate a transport address and transport type. indicate a transport address and transport type.
This directs the senders ASAP endpoint to send the message out to the This directs the senders ASAP endpoint to send the message out to the
specified transport address. specified transport address.
No endpoint fail-over is support when this form of send request is No endpoint fail-over is support when this form of send request is
used. This form of send request effectively by-passes the ASAP used. This form of send request effectively by-passes the ASAP
endpoint. endpoint.
4.5.5. Message Delivery Options 6.5.5. Message Delivery Options
The Options parameter passed in the various forms of the above The Options parameter passed in the various forms of the above
data_send_request primitive gives directions to the senders ASAP data_send_request primitive gives directions to the senders ASAP
endpoint on special handling of the message delivery. endpoint on special handling of the message delivery.
The value of the Options parameter is generated by bit-wise "OR"ing The value of the Options parameter is generated by bit-wise "OR"ing
of the following pre-defined constants: of the following pre-defined constants:
ASAP_USE_DEFAULT: 0x0000 Use default setting. ASAP_USE_DEFAULT: 0x0000 Use default setting.
skipping to change at page 35, line 31 skipping to change at page 40, line 31
ASAP_SEND_TO_SELF: 0x0010 This option only applies in combination ASAP_SEND_TO_SELF: 0x0010 This option only applies in combination
with ASAP_SEND_TO_ALL option. It permits the senders ASAP with ASAP_SEND_TO_ALL option. It permits the senders ASAP
endpoint also deliver a copy of the message to itself if the endpoint also deliver a copy of the message to itself if the
sender is a PE of the pool (i.e., loop-back). sender is a PE of the pool (i.e., loop-back).
ASAP_SCTP_UNORDER: 0x1000 This option requests the transport layer ASAP_SCTP_UNORDER: 0x1000 This option requests the transport layer
to send the current message using un-ordered delivery (note the to send the current message using un-ordered delivery (note the
underlying transport must support un-ordered delivery for this underlying transport must support un-ordered delivery for this
option to be effective). option to be effective).
4.6. Data.Received Notification 6.6. Data.Received Notification
Format: data.received(messageReceived, sizeOfMessage, Format: data.received(messageReceived, sizeOfMessage,
senderAddress, typeOfAddress) senderAddress, typeOfAddress)
When a new user message is received, the ASAP endpoint of the When a new user message is received, the ASAP endpoint of the
receiver uses this notification to pass the message to its upper receiver uses this notification to pass the message to its upper
layer. layer.
Along with the message being passed, the ASAP endpoint of the Along with the message being passed, the ASAP endpoint of the
receiver should also indicate to its upper layer the message senders receiver should also indicate to its upper layer the message senders
skipping to change at page 36, line 10 skipping to change at page 41, line 10
receiver's ASAP endpoint, a reverse mapping from the senders IP receiver's ASAP endpoint, a reverse mapping from the senders IP
address to the pool handle should be performed and if the mapping address to the pool handle should be performed and if the mapping
is successful, the senders ASAP Pool Element handle should be is successful, the senders ASAP Pool Element handle should be
constructed and passed in the senderAddress field. constructed and passed in the senderAddress field.
B) If there is no local cache or the reverse mapping is not B) If there is no local cache or the reverse mapping is not
successful, the SCTP association id or other transport specific successful, the SCTP association id or other transport specific
identification (if SCTP is not being used) should be passed in the identification (if SCTP is not being used) should be passed in the
senderAddress field. senderAddress field.
4.7. Error.Report Notification 6.7. Error.Report Notification
Format: error.report(destinationAddress, typeOfAddress, Format: error.report(destinationAddress, typeOfAddress,
failedMessage, sizeOfMessage) failedMessage, sizeOfMessage)
An error.report should be generated to notify the ASAP user about An error.report should be generated to notify the ASAP user about
failed message delivery as well as other abnormalities. failed message delivery as well as other abnormalities.
The destinationAddress and typeOfAddress together indicates to whom The destinationAddress and typeOfAddress together indicates to whom
the message was originally sent. The address type can be either a the message was originally sent. The address type can be either a
ASAP Pool Element handle, association id, or a transport address. ASAP Pool Element handle, association id, or a transport address.
The original message (or the first portion of it if the message is The original message (or the first portion of it if the message is
too big) and its size should be passed in the failedMessage and too big) and its size should be passed in the failedMessage and
sizeOfMessage fields, respectively. sizeOfMessage fields, respectively.
4.8. Examples 6.8. Examples
These examples assume an underlying SCTP transport between the PE and These examples assume an underlying SCTP transport between the PE and
PU. Other transports are possible but SCTP is utilized in the PU. Other transports are possible but SCTP is utilized in the
examples for illustrative purposes. Note that all communication examples for illustrative purposes. Note that all communication
between PU and ENRP server and PE and ENRP servers would be using between PU and ENRP server and PE and ENRP servers would be using
SCTP. SCTP.
4.8.1. Send to a New Pool 6.8.1. Send to a New Pool
This example shows the event sequence when a Pool User sends the This example shows the event sequence when a Pool User sends the
message "hello" to a pool which is not in the local translation cache message "hello" to a pool which is not in the local translation cache
(assuming local caching is supported). (assuming local caching is supported).
ENRP Server PU new-handle:PEx ENRP Server PU new-handle:PEx
| | | | | |
| +---+ | | +---+ |
| | 1 | | | | 1 | |
skipping to change at page 38, line 5 skipping to change at page 43, line 5
information about pool "new-handle". information about pool "new-handle".
5) ASAP at PU cancels the T1-ENRPrequest timer and populate its local 5) ASAP at PU cancels the T1-ENRPrequest timer and populate its local
cache with information on pool "new-handle". cache with information on pool "new-handle".
6) Based on the server pooling policy of pool "new-handle", ASAP at 6) Based on the server pooling policy of pool "new-handle", ASAP at
PU selects the destination PE (PEx), sets up, if necessary, an PU selects the destination PE (PEx), sets up, if necessary, an
SCTP association towards PEx (explicitly or implicitly), and send SCTP association towards PEx (explicitly or implicitly), and send
out the queued "hello1" user message. out the queued "hello1" user message.
4.8.2. Send to a Cached Pool Handle 6.8.2. Send to a Cached Pool Handle
This shows the event sequence when the ASAP user PU sends another This shows the event sequence when the ASAP user PU sends another
message to the pool "new-handle" after what happened in message to the pool "new-handle" after what happened in
Section 4.8.1. Section 6.8.1.
ENRP Server PU new-handle:PEx ENRP Server PU new-handle:PEx
| | | | | |
| +---+ | | +---+ |
| | 1 | | | | 1 | |
| +---+ 2. "hello2" | | +---+ 2. "hello2" |
| |---------------->| | |---------------->|
| | | | | |
skipping to change at page 38, line 31 skipping to change at page 43, line 31
pdata_send_request("new-handle", handle-type, "hello2", 6, 0); pdata_send_request("new-handle", handle-type, "hello2", 6, 0);
The ASAP endpoint, in response, looks up the pool "new-handle" in The ASAP endpoint, in response, looks up the pool "new-handle" in
its local cache and find the mapping information. its local cache and find the mapping information.
2) Based on the server pooling policy of "new-handle", ASAP at PU 2) Based on the server pooling policy of "new-handle", ASAP at PU
selects the PE (assume EPx is selected again), and sends out selects the PE (assume EPx is selected again), and sends out
"hello2" message (assume the SCTP association is already set up). "hello2" message (assume the SCTP association is already set up).
4.9. PE send failure 6.9. PE send failure
When the ASAP endpoint in a PE or PU attempts to send a message to a When the ASAP endpoint in a PE or PU attempts to send a message to a
PE and fails the failed sender will report the event as described in PE and fails the failed sender will report the event as described in
Section 3.5 . Section 3.5 .
Additional primitive are also defined in this section to support Additional primitive are also defined in this section to support
those user applications that do not wish to use ASAP as the actual those user applications that do not wish to use ASAP as the actual
transport. transport.
4.9.1. Translation.Request Primitive 6.9.1. Translation.Request Primitive
Format: translation.request(Pool-Handle) Format: translation.request(Pool-Handle)
If the address type is a Pool handle and a local handle translation If the address type is a Pool handle and a local handle translation
cache exists, the ASAP endpoint should look within its translation cache exists, the ASAP endpoint should look within its translation
cache and return the current known transport types, ports and cache and return the current known transport types, ports and
addresses to the caller. addresses to the caller.
If the Pool handle does not exist in the local handle cache or no If the Pool handle does not exist in the local handle cache or no
handle cache exists, the ASAP endpoint will send an handle cache exists, the ASAP endpoint will send an
ASAP_HANDLE_RESOLUTION request using the Pool handle. Upon ASAP_HANDLE_RESOLUTION request using the Pool handle. Upon
completion of the handle resolution, the ASAP endpoint should completion of the handle resolution, the ASAP endpoint should
populate the local handle cache (if a local handle cache is populate the local handle cache (if a local handle cache is
supported) and return the transport types, ports and addresses to the supported) and return the transport types, ports and addresses to the
caller. caller.
4.9.2. Transport.Failure Primitive 6.9.2. Transport.Failure Primitive
Format: transport.failure(Pool-Handle, Transport-address) Format: transport.failure(Pool-Handle, Transport-address)
If an external user encounters a failure in sending to a PE and is If an external user encounters a failure in sending to a PE and is
NOT using ASAP it can use this primitive to report the failure to the NOT using ASAP it can use this primitive to report the failure to the
ASAP endpoint. ASAP will send an ASAP_ENDPOINT_UNREACHABLE to the ASAP endpoint. ASAP will send an ASAP_ENDPOINT_UNREACHABLE to the
"home" ENRP server in response to this primitive. Note ASAP SHOULD "home" ENRP server in response to this primitive. Note ASAP SHOULD
NOT send a ASAP_ENDPOINT_UNREACHABLE UNLESS the user has actually NOT send a ASAP_ENDPOINT_UNREACHABLE UNLESS the user has actually
made a previous request to send data to the PE. made a previous request to send data to the PE.
5. Timers, Variables, and Thresholds 7. Timers, Variables, and Thresholds
The following is a summary of the timers, variables, and pre-set The following is a summary of the timers, variables, and pre-set
protocol constants used in ASAP. protocol constants used in ASAP.
5.1. Timers 7.1. Timers
T1-ENRPrequest - A timer started when a request is sent by ASAP to T1-ENRPrequest - A timer started when a request is sent by ASAP to
the ENRP server (providing application information is queued). the ENRP server (providing application information is queued).
Normally set to 15 seconds. Normally set to 15 seconds.
T2-registration - A timer started when sending an ASAP_REGISTRATION T2-registration - A timer started when sending an ASAP_REGISTRATION
request to the home ENRP server, normally set to 30 seconds. request to the home ENRP server, normally set to 30 seconds.
T3-deregistration - A timer started when sending a deregistration T3-deregistration - A timer started when sending a deregistration
request to the home ENRP server, normally set to 30 seconds. request to the home ENRP server, normally set to 30 seconds.
skipping to change at page 40, line 38 skipping to change at page 45, line 38
T5-Serverhunt - This timer is used during the ENRP server hunt T5-Serverhunt - This timer is used during the ENRP server hunt
procedure and is normally set to 10 seconds. procedure and is normally set to 10 seconds.
T6-Serverannounce - This timer gives the time between the sending of T6-Serverannounce - This timer gives the time between the sending of
consecutive ASAP_SERVER_ANNOUNCE messages. It is normally set to consecutive ASAP_SERVER_ANNOUNCE messages. It is normally set to
1 second. 1 second.
T7-ENRPoutdate - This timer gives the time a server announcement is T7-ENRPoutdate - This timer gives the time a server announcement is
valid. It is normally set to 5 seconds. valid. It is normally set to 5 seconds.
5.2. Variables 7.2. Variables
stale_cache_value - A threshold variable that indicates how long a stale_cache_value - A threshold variable that indicates how long a
cache entry is valid for. cache entry is valid for.
5.3. Thresholds 7.3. Thresholds
MAX-REG-ATTEMPT - The maximum number of registration attempts to be MAX-REG-ATTEMPT - The maximum number of registration attempts to be
made before a server hunt is issued. The default value of this is made before a server hunt is issued. The default value of this is
set to 2. set to 2.
MAX-REQUEST-RETRANSMIT - The maximum number of attempts to be made MAX-REQUEST-RETRANSMIT - The maximum number of attempts to be made
when requesting information from the local ENRP server before a when requesting information from the local ENRP server before a
server hunt is issued. The default value for this is 2. server hunt is issued. The default value for this is 2.
RETRAN-MAX - This value represents the maximum time between RETRAN-MAX - This value represents the maximum time between
registration attmempts and puts a ceiling on how far the registration attmempts and puts a ceiling on how far the
registration timer will back-off. The default value for this is registration timer will back-off. The default value for this is
normally set to 60 seconds. normally set to 60 seconds.
6. IANA Considerations 8. IANA Considerations
[NOTE to RFC-Editor: [NOTE to RFC-Editor:
"RFCXXXX" is to be replaced by the RFC number you assign this "RFCXXXX" is to be replaced by the RFC number you assign this
document. document.
] ]
This document (RFCXXX) is the reference for all registrations This document (RFCXXX) is the reference for all registrations
described in this section. All registrations need to be listed on an described in this section. All registrations need to be listed on an
RSerPool specific page. RSerPool specific page.
6.1. A New Table for ASAP Message Types 8.1. A New Table for ASAP Message Types
ASAP Message Types have to be maintained by IANA. Fourteen initial ASAP Message Types have to be maintained by IANA. Fourteen initial
values should be assigned by IANA as described in Figure 1. This values should be assigned by IANA as described in Figure 1. This
requires a new table "ASAP Message Types": requires a new table "ASAP Message Types":
Type Message Name Reference Type Message Name Reference
----- ------------------------- --------- ----- ------------------------- ---------
0x00 (reserved by IETF) RFCXXXX 0x00 (reserved by IETF) RFCXXXX
0x01 ASAP_REGISTRATION RFCXXXX 0x01 ASAP_REGISTRATION RFCXXXX
0x02 ASAP_DEREGISTRATION RFCXXXX 0x02 ASAP_DEREGISTRATION RFCXXXX
skipping to change at page 42, line 45 skipping to change at page 47, line 45
0x09 ASAP_ENDPOINT_UNREACHABLE RFCXXXX 0x09 ASAP_ENDPOINT_UNREACHABLE RFCXXXX
0x0a ASAP_SERVER_ANNOUNCE RFCXXXX 0x0a ASAP_SERVER_ANNOUNCE RFCXXXX
0x0b ASAP_COOKIE RFCXXXX 0x0b ASAP_COOKIE RFCXXXX
0x0c ASAP_COOKIE_ECHO RFCXXXX 0x0c ASAP_COOKIE_ECHO RFCXXXX
0x0d ASAP_BUSINESS_CARD RFCXXXX 0x0d ASAP_BUSINESS_CARD RFCXXXX
0x0e ASAP_ERROR RFCXXXX 0x0e ASAP_ERROR RFCXXXX
0x0b-0xff (reserved by IETF) RFCXXXX 0x0b-0xff (reserved by IETF) RFCXXXX
For registering at IANA an ASAP Message Type in this table a request For registering at IANA an ASAP Message Type in this table a request
has to be made to assign such a number. This number must be unique. has to be made to assign such a number. This number must be unique.
The "Specification Required" policy of RFC2434 [2] MUST be applied. The "Specification Required" policy of [RFC2434] MUST be applied.
7. Security Considerations 8.2. Multicast addresses
IANA needs to assign an IPv4 and an IPv6 mulitcast address.
9. Security Considerations
We present a summary of the of the threats to the Rserpool We present a summary of the of the threats to the Rserpool
architecture and describe security requirements in response to architecture and describe security requirements in response to
mitigate the threats. Next we present the security mechanisms, based mitigate the threats. Next we present the security mechanisms, based
on TLS, that are implementation requirements in response to the on TLS, that are implementation requirements in response to the
threats. Finally, we present a chain of trust argument that examines threats. Finally, we present a chain of trust argument that examines
critical data paths in Rserpool and shows how these paths are critical data paths in Rserpool and shows how these paths are
protected by the TLS implementation. protected by the TLS implementation.
7.1. Summary of Rserpool Security Threats 9.1. Summary of Rserpool Security Threats
Threats Introduced by Rserpool and Requirements for Security in Threats Introduced by Rserpool and Requirements for Security in
Response to Threats [10] describes the threats to the Rserpool Response to Threats [I-D.ietf-rserpool-threats] describes the threats
architecture in detail lists the security requirements in response to to the Rserpool architecture in detail lists the security
each threat. From the threats described in this document, the requirements in response to each threat. From the threats described
security services required for the Rserpool protocol are enumerated in this document, the security services required for the Rserpool
below. protocol are enumerated below.
Threat 1) PE registration/deregistration flooding or spoofing Threat 1) PE registration/deregistration flooding or spoofing
----------- -----------
Security mechanism in response: ENRP server authenticates the PE Security mechanism in response: ENRP server authenticates the PE
Threat 2) PE registers with a malicious ENRP server Threat 2) PE registers with a malicious ENRP server
----------- -----------
Security mechanism in response: PE authenticates the ENRP server Security mechanism in response: PE authenticates the ENRP server
Threat 1 and 2 taken together results in mutual authentication of the Threat 1 and 2 taken together results in mutual authentication of the
skipping to change at page 44, line 34 skipping to change at page 49, line 34
To summarize the threats 1-7 require security mechanisms which To summarize the threats 1-7 require security mechanisms which
support authentication, integrity, data confidentiality, protection support authentication, integrity, data confidentiality, protection
from replay attacks. from replay attacks.
For Rserpool we need to authenticate the following: For Rserpool we need to authenticate the following:
PU <---- ENRP Server (PU authenticates the ENRP server) PU <---- ENRP Server (PU authenticates the ENRP server)
PE <----> ENRP Server (mutual authentication) PE <----> ENRP Server (mutual authentication)
ENRP server <-----> ENRP Server (mutual authentication) ENRP server <-----> ENRP Server (mutual authentication)
7.2. Implementing Security Mechanisms 9.2. Implementing Security Mechanisms
We do not define any new security mechanisms specifically for We do not define any new security mechanisms specifically for
responding to threats 1-7. Rather we use an existing IETF security responding to threats 1-7. Rather we use an existing IETF security
protocol, specifically [4], to provide the security services protocol, specifically [RFC3237], to provide the security services
required. TLS supports all these requirements and MUST be required. TLS supports all these requirements and MUST be
implemented. The TLS_RSA_WITH_AES_128_CBC_SHA ciphersuite MUST be implemented. The TLS_RSA_WITH_AES_128_CBC_SHA ciphersuite MUST be
supported at a minimum by implementors of TLS for Rserpool. For supported at a minimum by implementors of TLS for Rserpool. For
purposes of backwards compatibility, ENRP SHOULD support purposes of backwards compatibility, ENRP SHOULD support
TLS_RSA_WITH_3DES_EDE_CBC_SHA. Implementers MAY also support any TLS_RSA_WITH_3DES_EDE_CBC_SHA. Implementers MAY also support any
other IETF approved ciphersuites. other IETF approved ciphersuites.
ENRP servers, PEs, PUs MUST implement TLS. ENRP servers and PEs must ENRP servers, PEs, PUs MUST implement TLS. ENRP servers and PEs must
support mutual authentication. ENRP servers must support mutual support mutual authentication. ENRP servers must support mutual
authentication among themselves. PUs MUST authenticate ENRP servers. authentication among themselves. PUs MUST authenticate ENRP servers.
skipping to change at page 45, line 12 skipping to change at page 50, line 12
ENRP servers and PEs SHOULD possess a site certificate whose subject ENRP servers and PEs SHOULD possess a site certificate whose subject
corresponds to their canonical hostname. PUs MAY have certificates corresponds to their canonical hostname. PUs MAY have certificates
of their own for mutual authentication with TLS, but no provisions of their own for mutual authentication with TLS, but no provisions
are set forth in this document for their use. All Rserpool elements are set forth in this document for their use. All Rserpool elements
that support TLS MUST have a mechanism for validating certificates that support TLS MUST have a mechanism for validating certificates
received during TLS negotiation; this entails possession of one or received during TLS negotiation; this entails possession of one or
more root certificates issued by certificate authorities (preferably more root certificates issued by certificate authorities (preferably
well-known distributors of site certificates comparable to those that well-known distributors of site certificates comparable to those that
issue root certificates for web browsers). issue root certificates for web browsers).
Implementations MUST support TLS with SCTP as described in [5] or TLS Implementations MUST support TLS with SCTP as described in [RFC3436]
over TCP as described in [6]. When using TLS/SCTP we must ensure or TLS over TCP as described in [RFC4346]. When using TLS/SCTP we
that RSerPool does not use any features of SCTP that are not must ensure that RSerPool does not use any features of SCTP that are
available to an TLS/SCTP user. This is not a difficult technical not available to an TLS/SCTP user. This is not a difficult technical
problem, but simply a requirement. When describing an API of the problem, but simply a requirement. When describing an API of the
RSerPool lower layer we have also to take into account the RSerPool lower layer we have also to take into account the
differences between TLS and SCTP. differences between TLS and SCTP.
Threat 8 requires the ASAP protocol to limit the number of Threat 8 requires the ASAP protocol to limit the number of
ASAP_ENDPOINT_UNREACHABLE messages (see Section 3.5 in this document) ASAP_ENDPOINT_UNREACHABLE messages (see Section 3.5 in this document)
to the ENRP server. to the ENRP server.
Threat 9 requires the ENRP protocol to limit the number of Threat 9 requires the ENRP protocol to limit the number of
ASAP_ENDPOINT_KEEP_ALIVE messages from the ENRP server to the PE (see ASAP_ENDPOINT_KEEP_ALIVE messages from the ENRP server to the PE (see
[9]). [I-D.ietf-rserpool-enrp]).
7.3. Chain of trust 9.3. Chain of trust
Security is mandatory to implement in Rserpool and is based on TLS Security is mandatory to implement in Rserpool and is based on TLS
implementation in all three architecture components that comprise implementation in all three architecture components that comprise
Rserpool -- namely PU, PE and ENRP server. We define an ENRP server Rserpool -- namely PU, PE and ENRP server. We define an ENRP server
that uses TLS for all communication and authenticates ENRP peers and that uses TLS for all communication and authenticates ENRP peers and
PE registrants to be a secured ENRP server. PE registrants to be a secured ENRP server.
Here is a description of all possible data paths and a description of Here is a description of all possible data paths and a description of
the security. the security.
skipping to change at page 47, line 5 skipping to change at page 52, line 5
Summary: Summary:
Rserpool architecture components can communicate with each other to Rserpool architecture components can communicate with each other to
establish a chain of trust. Secured PE and ENRP servers reject any establish a chain of trust. Secured PE and ENRP servers reject any
communications with unsecured ENRP or PE servers. communications with unsecured ENRP or PE servers.
If the above is enforced, then a chain of trust is established for If the above is enforced, then a chain of trust is established for
the Rserpool user. the Rserpool user.
8. Acknowledgments 10. Acknowledgments
The authors wish to thank John Loughney, Lyndon Ong, Walter Johnson, The authors wish to thank John Loughney, Lyndon Ong, Walter Johnson,
Thomas Dreibholz, and many others for their invaluable comments and Thomas Dreibholz, and many others for their invaluable comments and
feedback. feedback.
9. References 11. References
9.1. Normative References 11.1. Normative References
[1] Bradner, S., "Key words for use in RFCs to Indicate Requirement [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Levels", BCP 14, RFC 2119, March 1997. Requirement Levels", BCP 14, RFC 2119, March 1997.
[2] Narten, T. and H. Alvestrand, "Guidelines for Writing an IANA [RFC2434] Narten, T. and H. Alvestrand, "Guidelines for Writing an
Considerations Section in RFCs", BCP 26, RFC 2434, IANA Considerations Section in RFCs", BCP 26, RFC 2434,
October 1998. October 1998.
[3] Stewart, R., Xie, Q., Morneault, K., Sharp, C., Schwarzbauer, [RFC3237] Tuexen, M., Xie, Q., Stewart, R., Shore, M., Ong, L.,
H., Taylor, T., Rytina, I., Kalla, M., Zhang, L., and V. Loughney, J., and M. Stillman, "Requirements for Reliable
Paxson, "Stream Control Transmission Protocol", RFC 2960, Server Pooling", RFC 3237, January 2002.
October 2000.
[4] Tuexen, M., Xie, Q., Stewart, R., Shore, M., Ong, L., Loughney,
J., and M. Stillman, "Requirements for Reliable Server
Pooling", RFC 3237, January 2002.
[5] Jungmaier, A., Rescorla, E., and M. Tuexen, "Transport Layer [RFC3436] Jungmaier, A., Rescorla, E., and M. Tuexen, "Transport
Security over Stream Control Transmission Protocol", RFC 3436, Layer Security over Stream Control Transmission Protocol",
December 2002. RFC 3436, December 2002.
[6] Dierks, T. and E. Rescorla, "The Transport Layer Security (TLS) [RFC4346] Dierks, T. and E. Rescorla, "The Transport Layer Security
Protocol Version 1.1", RFC 4346, April 2006. (TLS) Protocol Version 1.1", RFC 4346, April 2006.
[7] Tuexen, M. and T. Dreibholz, "Reliable Server Pooling [RFC4960] Stewart, R., "Stream Control Transmission Protocol",
Policies", draft-ietf-rserpool-policies-05 (work in progress), RFC 4960, September 2007.
July 2007.
[8] Stewart, R., "Aggregate Server Access Protocol (ASAP) and [I-D.ietf-rserpool-policies]
Endpoint Handlespace Redundancy Protocol (ENRP) Parameters", Tuexen, M. and T. Dreibholz, "Reliable Server Pooling
draft-ietf-rserpool-common-param-12 (work in progress), Policies", draft-ietf-rserpool-policies-07 (work in
July 2007. progress), November 2007.
[9] Stewart, R., "Endpoint Handlespace Redundancy Protocol (ENRP)", [I-D.ietf-rserpool-common-param]
draft-ietf-rserpool-enrp-16 (work in progress), July 2007. Stewart, R., Xie, Q., Stillman, M., and M. Tuexen,
"Aggregate Server Access Protocol (ASAP) and Endpoint
Handlespace Redundancy Protocol (ENRP) Parameters",
draft-ietf-rserpool-common-param-14 (work in progress),
November 2007.
[10] Gopal, R., Guttman, E., Holdrege, M., Sengodan, S., and M. [I-D.ietf-rserpool-enrp]
Stillman, "Threats Introduced by Rserpool and Requirements for Xie, Q., Stewart, R., Stillman, M., Tuexen, M., and A.
Security in response to Threats", Silverton, "Endpoint Handlespace Redundancy Protocol
draft-ietf-rserpool-threats-08 (work in progress), (ENRP)", draft-ietf-rserpool-enrp-17 (work in progress),
September 2007. September 2007.
9.2. Informative References [I-D.ietf-rserpool-threats]
Stillman, M., Gopal, R., Guttman, E., Holdrege, M., and S.
Sengodan, "Threats Introduced by RSerPool and Requirements
for Security in Response to Threats",
draft-ietf-rserpool-threats-09 (work in progress),
October 2007.
[11] Eastlake, D., Schiller, J., and S. Crocker, "Randomness 11.2. Informative References
[RFC4086] Eastlake, D., Schiller, J., and S. Crocker, "Randomness
Requirements for Security", BCP 106, RFC 4086, June 2005. Requirements for Security", BCP 106, RFC 4086, June 2005.
Authors' Addresses Authors' Addresses
Randall R. Stewart Randall R. Stewart
Cisco Systems, Inc. Cisco Systems, Inc.
4875 Forest Drive 4875 Forest Drive
Suite 200 Suite 200
Columbia, SC 29206 Columbia, SC 29206
USA USA
 End of changes. 128 change blocks. 
231 lines changed or deleted 438 lines changed or added

This html diff was produced by rfcdiff 1.34. The latest version is available from http://tools.ietf.org/tools/rfcdiff/