Agree on a retransmission interval
01The timeout option proposes how many seconds to wait before retransmitting. Acceptance echoes the requested value.
Separate invalid-reply example: the server returns timeout=2 after a request for 3. The client rejects this unacceptable OACK with ERROR 8 and terminates.
Source for this drawing: RFC 2349 · Read RFC source: Timeout Interval · p.2 ↗
New to this? Start hereA quick picture + helpful background
A message needs an address.
Think of a packet as a small addressed envelope. Devices pass it onward; transport protocols decide what delivery promises an application gets.
Helpful first, if these ideas are unfamiliar
These pictures are analogies to help you learn. The linked RFC explains the actual rules.
Terms in this drawing
Related RFCs and changes
“Updates” changes part of an earlier RFC. “Obsoletes” replaces it. This list shows selected related documents.
timeout is case-insensitive; its value is an ASCII number from 1 through 255 seconds, terminated by a zero octet.
- timeout is case-insensitive; its value is an ASCII number from 1 through 255 seconds, terminated by a zero octet.
- If the server accepts timeout, the OACK value must match the client request; it is not a smaller counter-offer.
- Only acknowledged options become active after the appropriate confirmation. A client rejects an unacceptable OACK with ERROR code 8 and terminates (RFC2347).
The RFC uses lowercase must, not an RFC2119 conventions block. Preserve its exact-match requirement. Names and values end with zero octets; field widths are schematic.
Read the RFC section ↗