Subject: [Rserpool] Suggested change to ENDPOINT_KEEP_ALIVE

From: Johnson Walter-CWJ002 <[email-masked]>
Date: Mon, 25 Apr 2005 14:45:25 -0500

ASAP draft - Section 3.4 - States "KA2.4) Adopt the sender of the ASAP_ENDPOINT_KEEP_ALIVE message as the new home ENRP server"

Wouldn't it be better to add a flag to the ASAP_ENDPOINT_KEEP_ALIVE message that indicates when the receiving PE should adopt the sending ENRP server as its new home ENRP server? 

In the case of a takeover, the flag would be set to indicate to adopt the ENRP server as its new home. But in the case of an ASAP_ENDPOINT_KEEP_ALIVE message for heartbeat or checking reachability status due to a PU sending an ASAP_ENDPOINT_UNREACHABLE message to its home ENRP server this behavior of adopting the sending ENRP server may not be wanted so the flag would not be set. 

For example in the current draft, if the PE is alive, the PU can affect the PE to adopt a new home server and since PE is assumed to be more trusted in the architecture this is not necessarily good. Also if the PE is really alive, no updates to the handlespace are required so no additional messaging and workload on all of the ENRP servers will occur as in the original case. If the PE is not alive, the same signaling load within the architecture will occur as in original case.

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