[roll] Roll fuchsia [netstack3] Introduce SACK based loss recovery

Introduce the bulk of SACK based loss recovery. We're still not
initiating it, since processing SACKs is behind the SACK_PERMITTED
constant.

We're still missing RTO handling that needs special care if currently in
loss recovery, and the RFC 6675 section 6 text around managing the RTO
timer.

Original-Bug: 42078221
Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/1238730
Original-Revision: 4d5d0b740565426e3174e102a89aca4de243b122
GitOrigin-RevId: c1f0f0f82d495c4c3854c72f3b5b98b9959880d4
Change-Id: I4294084fad2406e3f5d2ba6f9d1e2bcbcdba6140
1 file changed
tree: 2f2a59fb70a79ee6c8b77d76ab9fb454a5f5ba0e
  1. ctf/
  2. git-hooks/
  3. infra/
  4. third_party/
  5. cts
  6. firmware
  7. flower
  8. jiri.lock
  9. MILESTONE
  10. minimal
  11. prebuilts
  12. README.md
  13. stem
  14. test_durations
  15. toolchain
README.md

Integration

This repository contains Fuchsia's Global Integration manifest files.

Making changes

All changes should be made to the internal version of this repository. Our infrastructure automatically updates this version when the internal one changes.

Currently all changes must be made by a Google employee. Non-Google employees wishing to make a change can ask for assistance in one of the communication channels documented at get involved.

Obtaining the source

First install Jiri.

Next run:

$ jiri init
$ jiri import minimal https://fuchsia.googlesource.com/integration
$ jiri update

Third party

Third party projects should have their own subdirectory in ./third_party.