Update documentation for ENC_TIME_* constants

ENC_TIME_MIP6 and ENC_TIME_CLASSIC_MAC_OS_SECS were added recently by
factoring them out of specific dissectors, but they weren't documented.
I added documentation, based on comments in the dissector code they came
from.
This commit is contained in:
Nicolás Alvarez 2021-02-03 17:40:16 -03:00
parent 11c8f5c30b
commit 0e86ea6c57
2 changed files with 14 additions and 0 deletions

View File

@ -1830,6 +1830,13 @@ encodings that are currently supported are:
ENC_TIME_MSEC_NTP - 4-8 bytes, representing a count of milliseconds since ENC_TIME_MSEC_NTP - 4-8 bytes, representing a count of milliseconds since
the NTP epoch. (I.e., milliseconds since the NTP epoch.) the NTP epoch. (I.e., milliseconds since the NTP epoch.)
ENC_MIP6 - 8 bytes; the first 48 bits are seconds since the UN*X epoch
and the remaining 16 bits indicate the number of 1/65536's of a second
since that second.
ENC_TIME_CLASSIC_MAC_OS_SECS - 4-8 bytes, representing a count of seconds
since January 1, 1904, 00:00:00 UTC.
For FT_RELATIVE_TIME fields, the encoding specifies the form in which For FT_RELATIVE_TIME fields, the encoding specifies the form in which
the time stamp is specified, as well as its byte order. The time stamp the time stamp is specified, as well as its byte order. The time stamp
encodings that are currently supported are: encodings that are currently supported are:

View File

@ -577,6 +577,13 @@ void proto_report_dissector_bug(const char *format, ...)
* ENC_TIME_MSEC_NTP - 4-8 bytes, representing a count of milliseconds since * ENC_TIME_MSEC_NTP - 4-8 bytes, representing a count of milliseconds since
* the NTP epoch. (I.e., milliseconds since the NTP epoch.) * the NTP epoch. (I.e., milliseconds since the NTP epoch.)
* *
* ENC_MIP6 - 8 bytes; the first 48 bits are seconds since the UN*X epoch
* and the remaining 16 bits indicate the number of 1/65536's of a second
* since that second.
*
* ENC_TIME_CLASSIC_MAC_OS_SECS - 4-8 bytes, representing a count of seconds
* since January 1, 1904, 00:00:00 UTC.
*
* The backwards-compatibility names are defined as hex numbers so that * The backwards-compatibility names are defined as hex numbers so that
* the script to generate init.lua will add them as global variables, * the script to generate init.lua will add them as global variables,
* along with the new names. * along with the new names.