Attendees: bz@, rscheff@, tuexen@
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. Still ongoing. rrs@ reviewed. Discussion continues.
- Can the TCP_STATS framework be turned on and sample no connections? Yes. thj@ will do.
- D18892: PRR, rrs@ will review.
- D18985: Upcoming: Rescue retransmission
- D21117: Upcoming: Reduce counter space
- D8253: rscheff@ will look into it.
- D10894: possibly use hystart++ instead. rrs@ will look into this later this year.
- D26518: Bundle stack and CC data separately. tuexen@ approved it.
- D26446: Fix sending of segments. tuexen@ approved.
- D26714: DSCP for iSCSI initiator. @rscheff still working on it.
- D26409: Setting VLAN priority per socket. rrs@ needs to review.
- bz@ is asking current status of MPTCP. tuexen@ will contact grenville.
Next meeting: 22 October @ 1400 UTC