Hi Pascal, Some additional info. Both formats exist for the PLMN Id. One is called "little-endian" MNC encoding in Wireshark's code.
[0] MCC digit 2, MCC digit 1 [1] MNC digit 3, MCC digit 3 [2] MNC digit 2, MNC digit 1 While the one I wrote in my original email is the "big-endian" MNC encoding. [0] MCC digit 2, MCC digit 1 [1] MNC digit 1, MCC digit 3 [2] MNC digit 3, MNC digit 2 It is not clear to me which one to adopt for the initial part of ECGI or NR CGI identifiers in a generic header field. In our application we use the latter. Looking at Wireshark code I see the "big-endian" MNC encoding being used to dissect the PLMN-Id of ECGI and NCGI fields in E1AP, S1AP, X2AP protocols. On the other side, GTPv2 uses "little-endian" MNC encoding. To avoid confusion I could also store MCC and MNC as separate fields... Any idea? Mauro ___________________________________________________________________________ Sent via: Wireshark-dev mailing list <wireshark-dev@wireshark.org> Archives: https://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe
