Implement RKM on the M3UA client side
The server already supports RKM (whcih has been validated using m3ua-testtool), but the ASP side is not implemented yet. We need some kind of xUA layer manager FSM for the client which will attempt to register a routing key for the locally-configured point code.
This way we can avoid the SG matching the client based on IP address and port information (which is of course quite old-fashioned and inflexible).
I have some work for this in the
laforge/sigtran-rkm branch, needs testing and completing.