Project

General

Profile

Feature #3091

idea: reduce confusion by renaming aud2G and aud3G to gsm and umts?

Added by neels 7 months ago. Updated 3 months ago.

Status:
Resolved
Priority:
Low
Assignee:
Target version:
-
Start date:
03/21/2018
Due date:
% Done:

100%


Description

Looking at https://gerrit.osmocom.org/7391 it is clear that any newcomer would assume that the 2G RAN lacks milenage support.
It is hard to grasp that the aud3g tokens are actually happily available for a GERAN network.

  subscriber (imsi|msisdn|id) IDENT update aud2g (comp128v1|comp128v2|comp128v3|xor) ki KI
  subscriber (imsi|msisdn|id) IDENT update aud3g milenage k K (op|opc) OP_C [ind-bitlen] [<0-28>]

We want to a) aggressively document the fact that "aud3g" is also used on 2G and maybe also
b) despite the effort, go for renaming of the vty commands and possibly the internal data structures, using "gsm" and "umts" instead of "2G" and "3G".

I'm not sure if renaming would really make it clear, because it seems usually UMTS is used synonymous to 3G despite it being available on 2G.
What's the opinion on this?

Definitely we need a): aggressively document that we support full milenage on 2G and how it works.

History

#1 Updated by neels 7 months ago

  • Description updated (diff)

#2 Updated by laforge 4 months ago

  • Priority changed from Normal to Low

#3 Updated by laforge 4 months ago

I think the most important part is to properly explain it in the user manual. Is that the case?

#4 Updated by neels 4 months ago

#5 Updated by neels 4 months ago

  • % Done changed from 0 to 50

#6 Updated by neels 4 months ago

  • % Done changed from 50 to 90

The HLR VTY doc already say "aud3g Set UMTS authentication data (3G, and 2G with UMTS AKA)"

#7 Updated by neels 4 months ago

  • Assignee set to neels

#8 Updated by neels 3 months ago

  • Status changed from New to Resolved
  • % Done changed from 90 to 100

above patch was merged

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 48.8 MB)