aboutsummaryrefslogtreecommitdiffstats
path: root/osmoappdesc.py
diff options
context:
space:
mode:
authorNeels Hofmeyr <neels@hofmeyr.de>2019-12-12 01:31:04 +0100
committerNeels Hofmeyr <neels@hofmeyr.de>2019-12-12 02:10:06 +0100
commit63b246453be19d06035f73c616406a20b0f899d3 (patch)
tree836620133be8ce7edcce8037cb548e80a30ec1ad /osmoappdesc.py
parentabbdbfbbaba26c3c3e6ce9f2971f29c693f8c3b9 (diff)
gsup: indicate CN-Domain in SendAuthInfo Requests
In order for osmo-hlr to be able to 100% guarantee distinct INDs for CS and PS, set CN-Domain = CS in all SendAuthInfo Requests. In Milenage auth, it is highly desirable that osmo-hlr guarantees use of distinct INDs for CS and PS domains. If an MSC and SGSN attached at the same time use the same IND bucket to generate Milenage SQN, that collision would rapidly waste SQNs and load osmo-hlr with requesting new auth tuples on each CS/PS Complete-Layer3. So far, osmo-msc did not indicate the CN domain in the GSUP SendAuthInfo Request, which was neither required nor evaluated. The CN-Domain is only sent for the UpdateLocation Request that usually follows later. Related: OS#4318 Change-Id: I22f44068268e62801cadbf6542efaf153423cd65
Diffstat (limited to 'osmoappdesc.py')
0 files changed, 0 insertions, 0 deletions