)]}'
{
  "commit": "85e8667f3db9d6748ad8fe4609ee6a227cb10034",
  "tree": "f0cd03507628649334bb128712dce40c5b2d9901",
  "parents": [
    "17ca6b0e1a45d3ae966632ba71f7a9485980e269"
  ],
  "author": {
    "name": "fayang",
    "email": "fayang@google.com",
    "time": "Thu Jun 17 05:29:32 2021 -0700"
  },
  "committer": {
    "name": "Copybara-Service",
    "email": "copybara-worker@google.com",
    "time": "Thu Jun 17 05:30:10 2021 -0700"
  },
  "message": "Do not send PATH_CHALLENGE or PATH_RESPONSE when 1-RTT write key is not available. This does not have functional because:\n1) Client does not initiated path validation until handshake confirmed.\n2) Server does not allow peer address change during handshake (no reverse path validation until handshake complete).\n3) Server can only receive PATH_CHALLENGE in ENCRYPTION_ZERO_RTT and ENCRYPTION_FORWARD_SECURE, while server must have 1-RTT write key. Client can only receive PATH_CHALLENGE in ENCRYPTION_FORWARD_SECURE, while client must have 1-RTT write key.\n\nThis is needed since we are going to allow address change during the handshake.\n\nPiperOrigin-RevId: 379936797\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "ce99e65f306ec72a58eed4203a50182374b885d5",
      "old_mode": 33188,
      "old_path": "quic/core/quic_connection.cc",
      "new_id": "d5252421f4404bf35e5ae837599f968c33211ec2",
      "new_mode": 33188,
      "new_path": "quic/core/quic_connection.cc"
    }
  ]
}