diff --git a/177a45d2ae3c8df71a744fc145ed442fa53914a5 b/177a45d2ae3c8df71a744fc145ed442fa53914a5
index 7fcab02f..e6888baa 100644
--- a/177a45d2ae3c8df71a744fc145ed442fa53914a5
+++ b/177a45d2ae3c8df71a744fc145ed442fa53914a5
@@ -1,5 +1,22 @@
 {
   "comments": [
+    {
+      "unresolved": true,
+      "key": {
+        "uuid": "f00a2814_36ab91c0",
+        "filename": "docs/put_key-tutorial.rst",
+        "patchSetId": 2
+      },
+      "lineNbr": 80,
+      "author": {
+        "id": 1000028
+      },
+      "writtenOn": "2026-03-17T12:06:38Z",
+      "side": 1,
+      "message": "We need to check back if this really works. Does the isdp_aid really point to the ISD we set up in the securityDomain PE?\n\nIn the experiments I have done so far, the select to the ISD-P by the isdp_aid is successful. When I try get_data key_information I get an empty list back. I always thought that was due to the fact that I had no secure channel yet. But apparently the key_information does not require a secure channel.\n\nWhen I look at the profile package. I see that the securityDomain PE specifies an \u0027instanceAID\u0027 field. When I select the AID in that field everything starts to look normal and I can even establish the SCP03 secure channel.\n\nThis is a bit confusing. I thought the securityDomain PE and the ISD-P were the same thing. I think this is something we should clarify and write down in this tutorial.",
+      "revId": "177a45d2ae3c8df71a744fc145ed442fa53914a5",
+      "serverId": "035e6965-6537-41bd-912c-053f3cf69326"
+    },
     {
       "unresolved": true,
       "key": {