diff --git a/archive.json b/archive.json
index 9be3ad0..34b1101 100644
--- a/archive.json
+++ b/archive.json
@@ -1,6 +1,6 @@
 {
   "magic": "E!vIA5L86J2I",
-  "timestamp": "2024-03-26T00:18:10.268907+00:00",
+  "timestamp": "2024-03-28T00:18:45.176516+00:00",
   "repo": "tfpauly/draft-happy-eyeballs-v3",
   "labels": [
     {
@@ -713,7 +713,7 @@
       "labels": [],
       "body": "(copying from an email I sent to the authors)\r\n\r\nWith PREF64 being available, some networks might only provide PREF64 and do not use DNS64, as the latter has a number of disadvantages, such as breaking DNSSEC and not working if the host has custom DNS\r\nservers configured.\r\n\r\nSo do you think it's worth adding some text saying that some Ipv6-only\r\nor, more likely, IPv6-mostly networks might only deploy PREF64 w/o DNS64?\r\n\r\nSee https://www.ietf.org/archive/id/draft-link-v6ops-6mops-00.html#name-dns-vs-dns64",
       "createdAt": "2024-03-18T23:01:03Z",
-      "updatedAt": "2024-03-25T18:23:43Z",
+      "updatedAt": "2024-03-26T00:43:12Z",
       "closedAt": null,
       "comments": [
         {
@@ -736,6 +736,13 @@
           "body": "Jen was trying to be able to remove DNS64 in general, since it breaks DNSSEC, etc, etc",
           "createdAt": "2024-03-25T18:23:43Z",
           "updatedAt": "2024-03-25T18:23:43Z"
+        },
+        {
+          "author": "DavidSchinazi",
+          "authorAssociation": "COLLABORATOR",
+          "body": "I see. Maybe we split up the PREF64 and DNS64 algorithms completely then, with the PREF64 algorithm preferred over the DNS64 one",
+          "createdAt": "2024-03-26T00:43:10Z",
+          "updatedAt": "2024-03-26T00:43:10Z"
         }
       ]
     },