Opened 7 weeks ago

#29 new defect

classic bottleneck detection can misidentify L4S queues as RFC 3168 queues

Reported by: pete@… Owned by: draft-ietf-tsvwg-l4s-arch@…
Priority: major Milestone:
Component: l4s-arch Version:
Severity: - Keywords:
Cc:

Description

There are several cases we've noticed where classic bottleneck detection will misidentify an L4S queue as an RFC 3168 queue:

  • paths with about 2ms or more of jitter
  • low capacity paths (tested 5 Mbps)
  • asymmetric links with bi-directional traffic

Although misidentifying an L4S queue as an RFC 3168 queue is safe in and of itself, it leads to performance issues, which increases the likelihood of bottleneck detection being disabled.

Test results around jitter and low capacity links are here:

https://github.com/heistp/sce-l4s-ect1#false-positives

An explanation of the results with asymmetric links and bi-directional traffic, along with links to test results is here:

https://mailarchive.ietf.org/arch/msg/tsvwg/-gx8R1jcwiCsX1_5cdnvl3kKlOs/

Change History (0)

Note: See TracTickets for help on using tickets.