diff --git a/67e1fef97dafa2b140a974b7cbbb668eff66aa6c b/67e1fef97dafa2b140a974b7cbbb668eff66aa6c
index 893de61..abe1f38 100644
--- a/67e1fef97dafa2b140a974b7cbbb668eff66aa6c
+++ b/67e1fef97dafa2b140a974b7cbbb668eff66aa6c
@@ -34,6 +34,24 @@
       "parentUuid": "cd48c380_8cedbf65",
       "revId": "67e1fef97dafa2b140a974b7cbbb668eff66aa6c",
       "serverId": "035e6965-6537-41bd-912c-053f3cf69326"
+    },
+    {
+      "unresolved": true,
+      "key": {
+        "uuid": "fcee2076_2e91b009",
+        "filename": "/COMMIT_MSG",
+        "patchSetId": 2
+      },
+      "lineNbr": 9,
+      "author": {
+        "id": 1000074
+      },
+      "writtenOn": "2024-02-15T17:31:51Z",
+      "side": 1,
+      "message": "Ah I think I previously confused IPv4/Ipv6 *outer* support with *inner* support here, sorry.\n\n\u003eAnd a GTP can only listen to one single address at the same time, either IPv4 or IPv6.\n\nSo this means, If one wants to implement a GSN node which can be accessed both through IPv4 and IPv6 in UDP/GTP-U (*outer*, not *inner*), then 2 gtp tun devices need to be created right? One for IPv4 and one for IPv6.\n\nEg. When sending a GTPv2C CreateSessionReq, the GSN node can specify both an IPv4 and an IPv6 address where it can be reached (in FQDN IE). Similar stuff in the CreateSessionResp back.\nSimilar stuff in GTpv1C with \"GSN Address\" IEs.",
+      "parentUuid": "c66d4f48_89ff8d1b",
+      "revId": "67e1fef97dafa2b140a974b7cbbb668eff66aa6c",
+      "serverId": "035e6965-6537-41bd-912c-053f3cf69326"
     }
   ]
 }
\ No newline at end of file