Project

General

Profile

Actions

Feature #2001

closed

Implement RKM on the M3UA client side

Added by laforge about 7 years ago. Updated almost 7 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Target version:
-
Start date:
04/10/2017
Due date:
% Done:

100%

Spec Reference:

Description

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.

Actions #1

Updated by laforge almost 7 years ago

  • Status changed from New to Closed
  • % Done changed from 30 to 100

long merged to master.

Actions

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 48.8 MB)