Actions
Bug #5145
closedDon't require a NTFY(AS-INACTIVE) after ASP-UP procedure
Start date:
05/10/2021
Due date:
% Done:
100%
Spec Reference:
Description
When we're in the ASP role, the current behavior is as follows:
- perform the ASP-UP procedure (outbound)
- wait for incoming NTFY
- if that arrives before T_NOTIFY times out: proceed with outbound ASP-ACTIVE procedure
- if T_NOTIFY times out: attempt RKM routing key registration
While this is in-line with the various ladder diagrams in RFC4666, that same RFC states the SG should send the NTFY. It doesn't say must.
We currently encouter a presumed Ericsson peer that doesn't send said NOTIFY.
So we should tolerate such a scenario, and attempt the ASP-ACTIVE procedure
As RKM is apparently a relatively rarely implemented M3UA feature, it's probably best to make the behavior on T_NOTIFY timeout configurable, so the user can choose whether to- attempt a blind ASP-ACTIVE, or
- attempt RKM registration
Actions