3 ms·
Is that still true? https://www.rfc-editor.org/rfc/rfc3443.txt https://www.rfc-editor.org/rfc/rfc3443.txt has no mention of seconds. It just says that outputTT
by emmelaich 3y ago
Is that still true? https://www.rfc-editor.org/rfc/rfc3443.txt https://www.rfc-editor.org/rfc/rfc3443.txt has no mention of seconds.
It just says that outputTTL is (inputTTL - 1). With some exceptions.
[edit: I missed that that RFC is for MPLS but would be interested in your comment anyway; the definitive version seems to be https://datatracker.ietf.org/doc/html/rfc1122 https://datatracker.ietf.org/doc/html/rfc1122]
- js2 3y agoRFC 791: > The time is measured in units of seconds, but since every module that processes a datagram must decrease the TTL by at least one even if it process the datagram in less than a second, the TTL must be thought of only as an upper bound on the time a datagram may exist. https://www.rfc-editor.org/rfc/rfc791.html https://www.rfc-editor.org/rfc/rfc791.html The equivalent field in IPv6 is named hop limit in recognition of how the TTL field is used in practice with IPv4: https://www.rfc-editor.org/rfc/rfc2460.html https://www.rfc-editor.org/rfc/rfc2460.html