transportprotocols:07may2020

Attendees: tuexen@, rscheff@, thj@, rrs@

Discussion

  • tuexen discussed how to mitigate blackhole detection problems
    • tuexen@ has a review to ensure we don't do blackhole detection once we are at the minimum value D24308; committed
    • Discussion on what should trigger blackhole detection – full size? Or, even smaller messages which are above our min MTU? For at least IPv6, min MTU makes sense.
    • Otherwise, tuexen@'s plan remains unchanged.
    • BBR and RACK needs some modifcation
  • Discussion of D24237: rscheff@ changed both the in-order and out-of-order data path so we call sorwakeup_locked() [when necessary] after the SACK blocks are updated. rrs@ provided feedback.
  • D23364: CWR with new data. This is a problem which impacts compatibility with other OSs.
  • D23371: tuexen@ will look into this.
  • D23373: tuexen@ will look into this.
  • D24657: Waiting for testing.

Next meeting: 21 May @ 1400 UTC

  • transportprotocols/07may2020.txt
  • Last modified: 2020/05/07 15:02
  • by MichaelTuexen