dexter has submitted this change. ( https://gerrit.osmocom.org/c/onomondo-eim/+/43654?usp=email )

(

2 is the latest approved patch-set. No files were changed between the latest approved patch-set and the submitted one. )Change subject: esipa_asn1_handler: fix typos ......................................................................

esipa_asn1_handler: fix typos

Related: SYS#8100 Change-Id: I14416250cdb523f5c1a20d3a3e3dbe5cc6c53bcd --- M src/esipa_asn1_handler.erl 1 file changed, 3 insertions(+), 3 deletions(-)

Approvals: Jenkins Builder: Verified laforge: Looks good to me, approved

diff --git a/src/esipa_asn1_handler.erl b/src/esipa_asn1_handler.erl index 2fe7603..9cb264a 100644 --- a/src/esipa_asn1_handler.erl +++ b/src/esipa_asn1_handler.erl @@ -21,7 +21,7 @@ % initiateAuthenticationRequest. However the field is only missing in case the IPA capability minimizeEsipaBytes is % used. This is an optional feature that this eIM does not support, so we can expect euiccInfo1 to be always present.

- % TODO: Popluate smdpAddress from Activation Code if missing: smdpAddress is declared as anan optional field in + % TODO: Popluate smdpAddress from Activation Code if missing: smdpAddress is declared as an optional field in % InitiateAuthenticationRequestEsipa. If the field is missing, we can retrieve it from the Activation Code that is % stored in the download Order (see also SGP.32, section 3.2.3.2, step 8).

@@ -229,8 +229,8 @@ % Sub-procedure Profile Installation (see also GSMA SGP.22, section 3.1.3.3). The eIM uses the % result data contained in this message to conclude the download and to make the download results % available to the REST API user. However, in rare cases it is possible that a - % ProfileInstallationResult is received way too late as part of the Notification Delivery to - % Notification Receivers (see also GSMA SGP.32, section 3.7) procedure. By then the context in the + % ProfileInstallationResult is received way too late as part of the notification delivery to + % notification receivers (see also GSMA SGP.32, section 3.7) procedure. By then the context in the % eIM may be long gone. The eIM will be unable to match the ProfileInstallationResult to any % context but it will foward it to the SMDP+ anyway. case mnesia_db_work:bind(Pid, TransactionId) of