Attention is currently required from: laforge, pespin.
osmith has posted comments on this change. ( https://gerrit.osmocom.org/c/osmo-ttcn3-hacks/+/37412?usp=email )
Change subject: deps/Makefile: Use osmocom fork of titan.TestPorts.SIPmsg
......................................................................
Patch Set 2: Code-Review+2
(1 comment)
File deps/Makefile:
https://gerrit.osmocom.org/c/osmo-ttcn3-hacks/+/37412/comment/74119302_0498…
PS1, Line 132: titan.TestPorts.SIPmsg_commit= osmocom/master
> I suggest using a specific commit here, like in the other lines. […]
Done
--
To view, visit https://gerrit.osmocom.org/c/osmo-ttcn3-hacks/+/37412?usp=email
To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings
Gerrit-Project: osmo-ttcn3-hacks
Gerrit-Branch: master
Gerrit-Change-Id: If9bffd57204ee1ea56cbf0cb0109c422fb2c460f
Gerrit-Change-Number: 37412
Gerrit-PatchSet: 2
Gerrit-Owner: pespin <pespin(a)sysmocom.de>
Gerrit-Reviewer: Jenkins Builder
Gerrit-Reviewer: laforge <laforge(a)osmocom.org>
Gerrit-Reviewer: osmith <osmith(a)sysmocom.de>
Gerrit-Attention: laforge <laforge(a)osmocom.org>
Gerrit-Attention: pespin <pespin(a)sysmocom.de>
Gerrit-Comment-Date: Mon, 08 Jul 2024 08:32:27 +0000
Gerrit-HasComments: Yes
Gerrit-Has-Labels: Yes
Comment-In-Reply-To: osmith <osmith(a)sysmocom.de>
Gerrit-MessageType: comment
Attention is currently required from: laforge, pespin.
Hello Jenkins Builder, laforge, osmith,
I'd like you to reexamine a change. Please visit
https://gerrit.osmocom.org/c/osmo-ttcn3-hacks/+/37412?usp=email
to look at the new patch set (#2).
The following approvals got outdated and were removed:
Code-Review+1 by laforge, Verified+1 by Jenkins Builder
Change subject: deps/Makefile: Use osmocom fork of titan.TestPorts.SIPmsg
......................................................................
deps/Makefile: Use osmocom fork of titan.TestPorts.SIPmsg
This will allow us using IPv6 in IPmsg_PT until [1] is mergedi upstream.
[1] https://gitlab.eclipse.org/eclipse/titan/titan.TestPorts.SIPmsg/-/merge_req…
Related: SYS#6982
Change-Id: If9bffd57204ee1ea56cbf0cb0109c422fb2c460f
---
M deps/Makefile
1 file changed, 18 insertions(+), 4 deletions(-)
git pull ssh://gerrit.osmocom.org:29418/osmo-ttcn3-hacks refs/changes/12/37412/2
--
To view, visit https://gerrit.osmocom.org/c/osmo-ttcn3-hacks/+/37412?usp=email
To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings
Gerrit-Project: osmo-ttcn3-hacks
Gerrit-Branch: master
Gerrit-Change-Id: If9bffd57204ee1ea56cbf0cb0109c422fb2c460f
Gerrit-Change-Number: 37412
Gerrit-PatchSet: 2
Gerrit-Owner: pespin <pespin(a)sysmocom.de>
Gerrit-Reviewer: Jenkins Builder
Gerrit-Reviewer: laforge <laforge(a)osmocom.org>
Gerrit-Reviewer: osmith <osmith(a)sysmocom.de>
Gerrit-Attention: laforge <laforge(a)osmocom.org>
Gerrit-Attention: pespin <pespin(a)sysmocom.de>
Gerrit-MessageType: newpatchset
Attention is currently required from: pespin.
osmith has posted comments on this change. ( https://gerrit.osmocom.org/c/osmo-ttcn3-hacks/+/37412?usp=email )
Change subject: deps/Makefile: Use osmocom fork of titan.TestPorts.SIPmsg
......................................................................
Patch Set 1:
(1 comment)
File deps/Makefile:
https://gerrit.osmocom.org/c/osmo-ttcn3-hacks/+/37412/comment/5389001e_2da5…
PS1, Line 132: titan.TestPorts.SIPmsg_commit= osmocom/master
I suggest using a specific commit here, like in the other lines. Otherwise it's not clear which commit is used at which time, which makes reproducing errors and bisect harder.
--
To view, visit https://gerrit.osmocom.org/c/osmo-ttcn3-hacks/+/37412?usp=email
To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings
Gerrit-Project: osmo-ttcn3-hacks
Gerrit-Branch: master
Gerrit-Change-Id: If9bffd57204ee1ea56cbf0cb0109c422fb2c460f
Gerrit-Change-Number: 37412
Gerrit-PatchSet: 1
Gerrit-Owner: pespin <pespin(a)sysmocom.de>
Gerrit-Reviewer: Jenkins Builder
Gerrit-Reviewer: laforge <laforge(a)osmocom.org>
Gerrit-Reviewer: osmith <osmith(a)sysmocom.de>
Gerrit-Attention: pespin <pespin(a)sysmocom.de>
Gerrit-Comment-Date: Mon, 08 Jul 2024 08:22:22 +0000
Gerrit-HasComments: Yes
Gerrit-Has-Labels: No
Gerrit-MessageType: comment
Attention is currently required from: laforge.
neels has posted comments on this change. ( https://gerrit.osmocom.org/c/osmo-iuh/+/37393?usp=email )
Change subject: support RAB Assignment in cn_ranap_rx_*_msg_co()
......................................................................
Patch Set 2:
(1 comment)
Commit Message:
https://gerrit.osmocom.org/c/osmo-iuh/+/37393/comment/49ee9033_44a78c0a
PS2, Line 20: Procedure", but doesn't
> I always assumed that the "outcome" is for the "intermediate" responses and the final response would […]
My humble conclusion is to just accept all the variants that an implementation could sensibly choose. There are no adverse effects AFAICT.
Details:
If an implementation were separating the outcomes by success/failure, each would have to be a separate RANAP PDU entirely:
Below listings show how the [[un]successful]outcome is indicated once in the "top" of the RANAP PDU, and the RAB Assignment lists of actual detailed responses is deeper within that single PDU:
```
typedef struct RANAP_RANAP_PDU {
RANAP_RANAP_PDU_PR present;
union RANAP_RANAP_PDU_u {
RANAP_InitiatingMessage_t initiatingMessage;
RANAP_SuccessfulOutcome_t successfulOutcome;
RANAP_UnsuccessfulOutcome_t unsuccessfulOutcome;
RANAP_Outcome_t outcome;
/*
* This type is extensible,
* possible extensions are below.
*/
} choice;
/* Context for parsing across buffer boundaries */
asn_struct_ctx_t _asn_ctx;
} RANAP_RANAP_PDU_t;
typedef struct RANAP_SuccessfulOutcome {
RANAP_ProcedureCode_t procedureCode; --> "RAB Assignment"
RANAP_Criticality_t criticality;
ANY_t value; --> decoded to struct ranap_message
/* Context for parsing across buffer boundaries */
asn_struct_ctx_t _asn_ctx;
} RANAP_SuccessfulOutcome_t;
typedef struct ranap_message_s {
uint8_t procedureCode; --> "RAB Assignment"
uint8_t criticality;
uint8_t direction; --> initiating/*outcome copied from RANAP_PDU
union {
...
RANAP_RAB_AssignmentRequestIEs_t raB_AssignmentRequestIEs;
RANAP_RAB_AssignmentResponseIEs_t raB_AssignmentResponseIEs;
...
}
}
typedef struct RANAP_RAB_AssignmentResponseIEs_s {
uint16_t presenceMask;
RANAP_RAB_SetupOrModifiedList_t raB_SetupOrModifiedList; ///< Optional field
RANAP_RAB_ReleasedList_t raB_ReleasedList; ///< Optional field
RANAP_RAB_QueuedList_t raB_QueuedList; ///< Optional field
RANAP_RAB_FailedList_t raB_FailedList; ///< Optional field
RANAP_RAB_ReleaseFailedList_t raB_ReleaseFailedList; ///< Optional field
RANAP_CriticalityDiagnostics_t criticalityDiagnostics; ///< Optional field
} RANAP_RAB_AssignmentResponseIEs_t;
```
A clear wording on which kind of outcome should be used doesn't seem to exist for Class 3, we only have this for Class 1:
3GPP TS 25.413 3.1:
"[Class 1 EP...]
Successful and Unsuccessful:
- One signalling message reports both successful and unsuccessful outcome for the different included requests.
The response message used is the one defined for successful outcome.
"
An implementation could assume the same for Class 3. Or they could return "outcome" for mixed outcomes. Or they could make it unsuccessful if >=1 items have failed... Each interpretation makes sense from different points of view.
--
To view, visit https://gerrit.osmocom.org/c/osmo-iuh/+/37393?usp=email
To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings
Gerrit-Project: osmo-iuh
Gerrit-Branch: master
Gerrit-Change-Id: Ifec566a98cb6141d27b9e5e33d5a78f8b1530658
Gerrit-Change-Number: 37393
Gerrit-PatchSet: 2
Gerrit-Owner: neels <nhofmeyr(a)sysmocom.de>
Gerrit-Reviewer: Jenkins Builder
Gerrit-Reviewer: laforge <laforge(a)osmocom.org>
Gerrit-Attention: laforge <laforge(a)osmocom.org>
Gerrit-Comment-Date: Sat, 06 Jul 2024 14:55:07 +0000
Gerrit-HasComments: Yes
Gerrit-Has-Labels: No
Comment-In-Reply-To: laforge <laforge(a)osmocom.org>
Gerrit-MessageType: comment
Attention is currently required from: neels.
laforge has posted comments on this change. ( https://gerrit.osmocom.org/c/osmo-iuh/+/37393?usp=email )
Change subject: support RAB Assignment in cn_ranap_rx_*_msg_co()
......................................................................
Patch Set 2: Code-Review+1
(1 comment)
Commit Message:
https://gerrit.osmocom.org/c/osmo-iuh/+/37393/comment/aa9aba01_b34723a3
PS2, Line 20: Procedure", but doesn't
I always assumed that the "outcome" is for the "intermediate" responses and the final response would then be a "successfulOutcome" or an "unsuccessfulOutcome".
So basically any rab assignment request would always see exactly one of either "successful" or "unsuccessful" outcome, plus 0..N "outcome". This is just my gut feeling of how I understand those type of 3GPP specs - I cannot give you a spec refrerence for it.
--
To view, visit https://gerrit.osmocom.org/c/osmo-iuh/+/37393?usp=email
To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings
Gerrit-Project: osmo-iuh
Gerrit-Branch: master
Gerrit-Change-Id: Ifec566a98cb6141d27b9e5e33d5a78f8b1530658
Gerrit-Change-Number: 37393
Gerrit-PatchSet: 2
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: Sat, 06 Jul 2024 11:00:08 +0000
Gerrit-HasComments: Yes
Gerrit-Has-Labels: Yes
Gerrit-MessageType: comment