From b4467ddcfaa2e78e5704f820cd8bd036edb8c7b4 Mon Sep 17 00:00:00 2001
From: Gerrit User 1000028 <1000028@035e6965-6537-41bd-912c-053f3cf69326>
Date: Thu, 19 Mar 2026 16:33:15 +0000
Subject: [PATCH] Update patch set 3

Patch Set 3:

(2 comments)

Patch-set: 3
---
 177a45d2ae3c8df71a744fc145ed442fa53914a5 | 36 ++++++++++++++++++++++++
 1 file changed, 36 insertions(+)

diff --git a/177a45d2ae3c8df71a744fc145ed442fa53914a5 b/177a45d2ae3c8df71a744fc145ed442fa53914a5
index e6888baa..78b990f5 100644
--- a/177a45d2ae3c8df71a744fc145ed442fa53914a5
+++ b/177a45d2ae3c8df71a744fc145ed442fa53914a5
@@ -17,6 +17,24 @@
       "revId": "177a45d2ae3c8df71a744fc145ed442fa53914a5",
       "serverId": "035e6965-6537-41bd-912c-053f3cf69326"
     },
+    {
+      "unresolved": false,
+      "key": {
+        "uuid": "4cf5210a_e1df87dc",
+        "filename": "docs/put_key-tutorial.rst",
+        "patchSetId": 2
+      },
+      "lineNbr": 80,
+      "author": {
+        "id": 1000028
+      },
+      "writtenOn": "2026-03-19T16:33:15Z",
+      "side": 1,
+      "message": "I have now reworked this. When I get https://euicc-manual.osmocom.org/docs/lpa/applet-id/ correctly then the purpose of the ISD-P is to be some kind of secure container of the profile. When it also is the \"on-card representative of the SM-DP+\", then the eSIM profile owner (MNO) probably has no influence here at all. This also may explain why it has no keys provisioned. As far as I understand now the ISD-P is not interesting at all in the scope of this tutorial. What we are interested in is the securityDomain that is specified in the eSIM profile.",
+      "parentUuid": "f00a2814_36ab91c0",
+      "revId": "177a45d2ae3c8df71a744fc145ed442fa53914a5",
+      "serverId": "035e6965-6537-41bd-912c-053f3cf69326"
+    },
     {
       "unresolved": true,
       "key": {
@@ -51,6 +69,24 @@
       "revId": "177a45d2ae3c8df71a744fc145ed442fa53914a5",
       "serverId": "035e6965-6537-41bd-912c-053f3cf69326"
     },
+    {
+      "unresolved": false,
+      "key": {
+        "uuid": "3eab4fe4_cf6a6d15",
+        "filename": "docs/put_key-tutorial.rst",
+        "patchSetId": 2
+      },
+      "lineNbr": 462,
+      "author": {
+        "id": 1000028
+      },
+      "writtenOn": "2026-03-19T16:33:15Z",
+      "side": 1,
+      "message": "I have checked this back. Remote Application Management over HTTP – Public Release v1.1.2, section 3.3.2 clearly says that the second key is a DEK key. So this is correct.",
+      "parentUuid": "e399c246_e2140b13",
+      "revId": "177a45d2ae3c8df71a744fc145ed442fa53914a5",
+      "serverId": "035e6965-6537-41bd-912c-053f3cf69326"
+    },
     {
       "unresolved": true,
       "key": {