Attendees: tuexen@, rscheff@, thj@, jtl@
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.
- Availability of Black Box logging tools: jtl@ will ask olivier@ to upstream.
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.
- To avoid a bug on older Linux kernels which occurs when the remote peer reneges on receive window size, rscheff proposes that we round up the receive window. With large window scales, rounding the receive window (which scaling requires) looks like we are reneging on receive window.
- tuexen@ reports on a bug in RACK which involves sending OOB messages. We discussed this and determined we could deprecate OOB support in RACK.
- rscheff@ will examine D19000 further. It has proven difficult to debug.
- D23364: CWR with new data. This is a problem which impacts compatibility with other OSs.
- tuexen@ will run the meeting for the next 3 months, except when he is unavailable.
Next meeting: 7 May @ 1400 UTC