Detect a packet-size black-hole pattern in synthetic traces
Small requests succeed while larger uploads stall without an application response.
- Focused work estimate
- 3h + prerequisites
- Priority in the scenario
- High
- Engineering practice
- Transport analysis
Estimated field mix
- Networking100%
Field percentages are editorial estimates of the ticket's engineering focus. They total 100%; they are not measured time, proficiency scores, or ownership evidence.
Review it, then add it to your workspace.
The board opens an editable draft; nothing is saved until you confirm it. Sign-in and workspace permissions apply, and Demo boards remain ephemeral.
Project context
A fictional desktop sync client works on one office network but intermittently fails on another. Application retries hide whether DNS, IPv6, or transport limits are responsible.
Setup prerequisites
- Author synthetic packet traces and local IPv4/IPv6 endpoint doubles; use no third-party scanning or captured personal traffic.
Preceding work
Complete these dependencies, or supply their agreed outputs before taking this ticket.
Acceptance criteria
- Identify the declared retransmission and size pattern.
- Distinguish a hypothesis from confirmed cause.
- Suggest one bounded local verification step.
Implementation constraints
- Do not infer path MTU from an arbitrary single failed request.
Verification to include
- Analyze a synthetic size-dependent failure.
- Keep a generic timeout trace inconclusive.
Deliverables
- Packet-size diagnostic rule.
Rollout and recovery
Use advisory findings only; require the verification step before configuration changes.
Value of the work
For the engineer: Practice layered network diagnosis and reproducible troubleshooting.
For the team: Produce precise support diagnostics that distinguish application defects from connectivity conditions.
Evidence boundaries
Outcome Evidence: Tests, patches, and runbooks are requested deliverables. They become Outcome Evidence only through a qualified Mission and immutable Evidence IDs.
Ownership Evidence: Independent adaptation must be observed under a declared verification policy and cite immutable Evidence IDs. Completing a planning ticket establishes no Ownership Evidence.