Open mystiker opened 2 weeks ago
Supporting TIMING-MARK requires intrusive handling of special IAC sequences, with no subnegotiation involved, making it hard to integrate smoothly with existing code. It would demand extra parsing logic just to detect and respond to IAC TIMING-MARK commands, which adds clutter to an otherwise clean data handling pipeline.
Consequently, we won’t be adding support for it. This option is implicit declined.
However, we might reconsider this IF we have another valid reason to parse the output data for IAC Commands.
Description: Implement support for the Telnet TIMING-MARK option to enable synchronization points in the data stream between client and server. This option is useful for measuring network latency and ensuring that specific points in communication have been reached, making it valuable for real-time applications where precise timing is required.
Details:
Option Code: 6
Functionality:
Expected Workflow:
IAC DO TIMING-MARK
to request support for TIMING-MARK.IAC WILL TIMING-MARK
, the requesting side can periodically sendIAC TIMING-MARK
as a marker.IAC TIMING-MARK
, confirming that the marker has been received and signaling a synchronization point.Acceptance Criteria:
References: