RESEARCH / PROTOCOLS, SYSTEMS & SECURITY

Research.

Packet traces, protocols, enumeration, fuzzing, and the craft of writing a result someone else can reproduce.

BOUNDARIES FIRST

These are educational notes, not reports from a professional engagement. No employer, customer, private system or nonpublic finding is described.

01 / PACKET FLOW

A packet analysis path from capture context through protocol layers. SCHEMATIC / EXPLANATORY, NOT LIVE SYSTEM DATA

02 / TRANSPORT STATE

Simplified TCP open and close states. Consult RFC 9293 for the complete state machine. SCHEMATIC / EXPLANATORY, NOT LIVE SYSTEM DATA

03 / TEST METHOD

Authorized testing loop: define scope, observe, reproduce, analyze, report and retest. SCHEMATIC / EXPLANATORY, NOT LIVE SYSTEM DATA

04 / GENERIC OBSERVATION TOPOLOGY

Generic client, observation point, and in-scope service topology. No real hosts or addresses are shown. SCHEMATIC / EXPLANATORY, NOT LIVE SYSTEM DATA

REFERENCE NOTES / 06

Method over mystique.

Each article names its uncertainty and links to the public specification or testing guide behind its factual claims.

A hands-on route from capture metadata through frames and TCP to the application exchange.

The familiar handshake is a compact state machine, not a promise that a remote service is healthy or authenticated.

Turn an authorized assessment into a small, repeatable set of network observations.

Build the harness, failure check, and reproducer alongside the input generator.

Record the conditions, change one input at a time, and label a protocol model by what the trace supports.

A compact report connects conditions, steps, evidence, impact, limits, and a way to verify the fix.