This page describes likely next steps for MTRP development.

• hop-by-hop reliable unicast ACK
• reliability-aware routing refinement
• better diagnostics and event reporting
• improved testing around route flaps and failover

• constrained-profile security improvements
• border-router patterns for limited radios
• fragmentation for data frames
• smarter route aging and recovery behavior

• group or multicast-style addressing
• application-efficient one-to-many state distribution
• bridge-aware topology handling
• richer transport diversity

MTRP should stay careful about scope.

A useful rule is:

• implement what improves real bench and field behavior
• delay features that add large state or protocol complexity without immediate benefit

A strong next step is usually:

• hop-by-hop ACK for reliable unicast
• use ACK outcome to improve reliability metrics
• then revisit reliability-aware path selection