Attention is currently required from: neels.
laforge has posted comments on this change. ( https://gerrit.osmocom.org/c/osmo-hnbgw/+/32987 )
Change subject: use new osmo_sccp_instance_next_conn_id()
......................................................................
Patch Set 1: Code-Review+1
--
To view, visit https://gerrit.osmocom.org/c/osmo-hnbgw/+/32987
To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings
Gerrit-Project: osmo-hnbgw
Gerrit-Branch: master
Gerrit-Change-Id: I0fc6e486ce5d68b06d0bc9869292f082ec7a67f0
Gerrit-Change-Number: 32987
Gerrit-PatchSet: 1
Gerrit-Owner: neels <nhofmeyr(a)sysmocom.de>
Gerrit-Reviewer: Jenkins Builder
Gerrit-Reviewer: laforge <laforge(a)osmocom.org>
Gerrit-Attention: neels <nhofmeyr(a)sysmocom.de>
Gerrit-Comment-Date: Thu, 25 May 2023 08:21:08 +0000
Gerrit-HasComments: No
Gerrit-Has-Labels: Yes
Gerrit-MessageType: comment
Attention is currently required from: neels, pespin.
laforge has posted comments on this change. ( https://gerrit.osmocom.org/c/osmo-hnbgw/+/32915 )
Change subject: immediately SCCP RLSD on HNB re-register
......................................................................
Patch Set 3:
(1 comment)
File src/osmo-hnbgw/context_map_sccp.c:
https://gerrit.osmocom.org/c/osmo-hnbgw/+/32915/comment/b6b75d10_d7051683
PS1, Line 362: tx_sccp_df1(fi, ranap_msg);
: tx_sccp_rlsd(fi);
> ok. i'm still a bit unclear, is this about only tx_sccp_rlsd() or also the other one?
Any function that implies transmitting a certain packet is named wrong.
> in my POV both functions already have the best names -- they both transmit actual SCCP packets on the wire,
they do not, which is why they are mis-nomers.
> by asking the SCCP user sap. So may I ask reviewers to just tell me which function(s) to rename to exactly what and I can do that.
The point is that you are *not* requesting the SCCP stack/provider to transmit a certain packet. You are requesting the SCCP stack to terminate a connection. Depending on the internal state of the SCCP stack, and the protocol specification, this *may* trigger a RLSD packet. So unless you reviewed the SCCP state meachines of Q.714 in the last detail, and can prove that no matter what, there will always be a RLSD, the name is wrong.
When I wrote the original comment, I stated "I personally don't know the SCCP CO state machines sufficiently off my head". I now did, and it confirms my point all along,
A cursory glance of e.g. scoc_fsm_conn_pend_out() shows that SCOC_E_SCU_N_DISC_REQ in this case does not trigger the generation of a RLSD message. Or if you check scoc_fsm_conn_pend_in(), then a SCOC_E_SCU_N_DISC_REQ triggers a SUA CORE packet (which is a CREF in SCCP), and not a RLSD.
The SCCP user has no way to send individual protocol messages. This is what protocol stacks are all about. If we wanted the user to implement all the nitty gritty details of SCCP internally, then the user could transmit low-level SCCP packets itself. But it doesn't. It's just a user of the SCCP SAP ("API"), and that API has high-level primitives and not low-level commands to trigger transmission of certain packets.
Just like you call close() on a TCP socket. That's what you care about. You don't care about (nor know) if the TCP stack does this with a FIN packet, RST packet or in whatever other magic way.
> In every case that would happen in a separate patch. If there's no opposition, I'm going to click on 'Resolved' here, from the perspective of review on the changes of *this* patch.
agreed.
--
To view, visit https://gerrit.osmocom.org/c/osmo-hnbgw/+/32915
To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings
Gerrit-Project: osmo-hnbgw
Gerrit-Branch: master
Gerrit-Change-Id: I4e78617ad39bb73fe92097c8a1a8069da6a7f6a1
Gerrit-Change-Number: 32915
Gerrit-PatchSet: 3
Gerrit-Owner: neels <nhofmeyr(a)sysmocom.de>
Gerrit-Reviewer: Jenkins Builder
Gerrit-Reviewer: neels <nhofmeyr(a)sysmocom.de>
Gerrit-Reviewer: pespin <pespin(a)sysmocom.de>
Gerrit-CC: laforge <laforge(a)osmocom.org>
Gerrit-Attention: neels <nhofmeyr(a)sysmocom.de>
Gerrit-Attention: pespin <pespin(a)sysmocom.de>
Gerrit-Comment-Date: Thu, 25 May 2023 08:19:17 +0000
Gerrit-HasComments: Yes
Gerrit-Has-Labels: No
Comment-In-Reply-To: neels <nhofmeyr(a)sysmocom.de>
Comment-In-Reply-To: laforge <laforge(a)osmocom.org>
Comment-In-Reply-To: pespin <pespin(a)sysmocom.de>
Gerrit-MessageType: comment
Attention is currently required from: merlinchlosta, dexter.
laforge has posted comments on this change. ( https://gerrit.osmocom.org/c/pysim/+/32688 )
Change subject: docs: add SUPI/SUCI usage example
......................................................................
Patch Set 3:
(5 comments)
Patchset:
PS1:
> thanks for submitting it. […]
Done
File docs/suci-tutorial.rst:
https://gerrit.osmocom.org/c/pysim/+/32688/comment/396b6a96_48cf5968
PS1, Line 6: . pySIM
> probably makes sense to mention the two different fundamental ways of SUCI calculation (on card / on […]
Done
https://gerrit.osmocom.org/c/pysim/+/32688/comment/2555e4e5_b0a5edfe
PS1, Line 33: If you bought
: the SIM card from your network
> maybe make it more explicit that this only works with a programmable card where you as the pySim use […]
Done
https://gerrit.osmocom.org/c/pysim/+/32688/comment/cd05fbb9_49cb477f
PS1, Line 103: file is **invalid**:
> does the file contain invalid data, or do you mean it is invalidated (other term for deactivated)?
Done
https://gerrit.osmocom.org/c/pysim/+/32688/comment/f75efe47_7c6e78be
PS1, Line 168: sysmocom ISIM does
> best to always say "sysmoISIM-SJA2" as other products in the future may also be a "sysmocom ISIM" bu […]
Done
--
To view, visit https://gerrit.osmocom.org/c/pysim/+/32688
To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings
Gerrit-Project: pysim
Gerrit-Branch: master
Gerrit-Change-Id: I2908ea9df7e78c596554731085902e2ab7278328
Gerrit-Change-Number: 32688
Gerrit-PatchSet: 3
Gerrit-Owner: merlinchlosta <merlin.chlosta(a)rub.de>
Gerrit-Reviewer: Jenkins Builder
Gerrit-Reviewer: dexter <pmaier(a)sysmocom.de>
Gerrit-CC: laforge <laforge(a)osmocom.org>
Gerrit-Attention: merlinchlosta <merlin.chlosta(a)rub.de>
Gerrit-Attention: dexter <pmaier(a)sysmocom.de>
Gerrit-Comment-Date: Thu, 25 May 2023 08:08:29 +0000
Gerrit-HasComments: Yes
Gerrit-Has-Labels: No
Comment-In-Reply-To: laforge <laforge(a)osmocom.org>
Comment-In-Reply-To: merlinchlosta <merlin.chlosta(a)rub.de>
Gerrit-MessageType: comment
Attention is currently required from: dexter.
Hello Jenkins Builder, fixeria, dexter,
I'd like you to reexamine a change. Please visit
https://gerrit.osmocom.org/c/pysim/+/32992
to look at the new patch set (#3).
Change subject: ts_31_102: Add DF.SAIP support
......................................................................
ts_31_102: Add DF.SAIP support
DF.SAIP (SIMalliance Interoperable Profile) is not part of 31.102,
but something from the eSIM/eUICC universe of TCA (formerly known as
SIMalliance). However, as 3GPP does not specify how/where the card
stores the information required for SUCI calculation, the
TCA/SIMalliance standard is the only standard there is. Some CardOS
start to use this standard even for non-eSIM/eUICC use cases.
Change-Id: Iffb65af335dfdbd7791fca9a0a6ad4b79814a57c
---
M pySim/ts_31_102.py
1 file changed, 29 insertions(+), 0 deletions(-)
git pull ssh://gerrit.osmocom.org:29418/pysim refs/changes/92/32992/3
--
To view, visit https://gerrit.osmocom.org/c/pysim/+/32992
To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings
Gerrit-Project: pysim
Gerrit-Branch: master
Gerrit-Change-Id: Iffb65af335dfdbd7791fca9a0a6ad4b79814a57c
Gerrit-Change-Number: 32992
Gerrit-PatchSet: 3
Gerrit-Owner: laforge <laforge(a)osmocom.org>
Gerrit-Reviewer: Jenkins Builder
Gerrit-Reviewer: dexter <pmaier(a)sysmocom.de>
Gerrit-Reviewer: fixeria <vyanitskiy(a)sysmocom.de>
Gerrit-Attention: dexter <pmaier(a)sysmocom.de>
Gerrit-MessageType: newpatchset
Attention is currently required from: merlinchlosta, dexter.
laforge has uploaded a new patch set (#2) to the change originally created by merlinchlosta. ( https://gerrit.osmocom.org/c/pysim/+/32688 )
Change subject: docs: add SUPI/SUCI usage example
......................................................................
docs: add SUPI/SUCI usage example
Change-Id: I2908ea9df7e78c596554731085902e2ab7278328
---
M docs/conf.py
M docs/shell.rst
A docs/suci-tutorial.rst
3 files changed, 212 insertions(+), 2 deletions(-)
git pull ssh://gerrit.osmocom.org:29418/pysim refs/changes/88/32688/2
--
To view, visit https://gerrit.osmocom.org/c/pysim/+/32688
To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings
Gerrit-Project: pysim
Gerrit-Branch: master
Gerrit-Change-Id: I2908ea9df7e78c596554731085902e2ab7278328
Gerrit-Change-Number: 32688
Gerrit-PatchSet: 2
Gerrit-Owner: merlinchlosta <merlin.chlosta(a)rub.de>
Gerrit-Reviewer: Jenkins Builder
Gerrit-Reviewer: dexter <pmaier(a)sysmocom.de>
Gerrit-CC: laforge <laforge(a)osmocom.org>
Gerrit-Attention: merlinchlosta <merlin.chlosta(a)rub.de>
Gerrit-Attention: dexter <pmaier(a)sysmocom.de>
Gerrit-MessageType: newpatchset