Script updating archive at 2022-04-25T20:00:13Z. [ci skip]

archive.json

@@ -1,6 +1,6 @@
 {
   "magic": "E!vIA5L86J2I",
-  "timestamp": "2022-04-12T15:10:51.407314+00:00",
+  "timestamp": "2022-04-25T20:00:10.780789+00:00",
   "repo": "quicwg/load-balancers",
   "labels": [
     {
@@ -3000,9 +3000,17 @@
       "labels": [],
       "body": "There are cases where an offload might send Retry on the second initial but not the first:\r\n- it turns on between the two packets\r\n- it is in a stochastic mode where it doesn't always send Retry\r\n\r\nThere is one failure mode and one degraded performance issue:\r\n1) If the server sends HRR, if the client's response triggers Retry it is likely to blackhole the connection.\r\n2) Under certain conditions, dropping the client's second Initial packet will cause either a client or server PTO. (Specifically, there will be no penalty if the client's 2nd flight has a datagram that (a) does not contain an initial, and (b) contains a HS ACK.)\r\n\r\nWe ought to write this down in the draft. For #1, it might be good practice for servers to send CONNECTION_CLOSE instead of HRR under two conditions:\r\n1) There is no Retry token in the Initial, and\r\n2) Other recent initials contained Retry tokens.",
       "createdAt": "2022-03-30T16:31:37Z",
-      "updatedAt": "2022-03-30T16:31:37Z",
+      "updatedAt": "2022-04-12T16:42:32Z",
       "closedAt": null,
-      "comments": []
+      "comments": [
+        {
+          "author": "martinduke",
+          "authorAssociation": "CONTRIBUTOR",
+          "body": "The amplification limit is a problem here. If the client's second flight is one packet, including an Initial, which keeps getting dropped, and the server is at its amplification limit, there is no way for the connection to progress.",
+          "createdAt": "2022-04-12T16:42:32Z",
+          "updatedAt": "2022-04-12T16:42:32Z"
+        }
+      ]
     },
     {
       "number": 166,
@@ -8798,13 +8806,13 @@
       "labels": [],
       "body": "Fix #166 in accordance with the 2nd crypto review",
       "createdAt": "2022-04-05T20:50:14Z",
-      "updatedAt": "2022-04-07T19:53:24Z",
+      "updatedAt": "2022-04-25T19:59:32Z",
       "baseRepository": "quicwg/load-balancers",
       "baseRefName": "main",
-      "baseRefOid": "493d0fd8a6264e5a6d11105815a370d670589296",
+      "baseRefOid": "cf4c59ea1d54b6023a36458192ff0ce058cdbfc6",
       "headRepository": "quicwg/load-balancers",
       "headRefName": "fix-index",
-      "headRefOid": "38ad3477d6691750d9fcebae09584f58471453b4",
+      "headRefOid": "0a204922150cf07e83d6257d3084859bb0ea6df6",
       "closedAt": null,
       "mergedAt": null,
       "mergedBy": null,
@@ -8852,6 +8860,34 @@
           ]
         }
       ]
+    },
+    {
+      "number": 170,
+      "id": "PR_kwDODoD6yc42HxoK",
+      "title": "Handle Second Initial correctly",
+      "url": "https://github.com/quicwg/load-balancers/pull/170",
+      "state": "OPEN",
+      "author": "martinduke",
+      "authorAssociation": "CONTRIBUTOR",
+      "assignees": [
+        "nibanks"
+      ],
+      "labels": [],
+      "body": "Fix #165",
+      "createdAt": "2022-04-12T18:06:40Z",
+      "updatedAt": "2022-04-12T18:06:40Z",
+      "baseRepository": "quicwg/load-balancers",
+      "baseRefName": "main",
+      "baseRefOid": "cf4c59ea1d54b6023a36458192ff0ce058cdbfc6",
+      "headRepository": "quicwg/load-balancers",
+      "headRefName": "late-retyr",
+      "headRefOid": "f18171bd1d14aa9a30f5d808fc3480672847eae9",
+      "closedAt": null,
+      "mergedAt": null,
+      "mergedBy": null,
+      "mergeCommit": null,
+      "comments": [],
+      "reviews": []
     }
   ]
 }