Add ENC_TIME_MSEC_NTP and use it in packet-gtpv2.c

While at it fix expert info a typo and an calculation.

Change-Id: I071a36edb7eed5f58708b98aebcb24bc6c34f2a8
Reviewed-on: https://code.wireshark.org/review/20766
Petri-Dish: Anders Broman <a.broman58@gmail.com>
Tested-by: Petri Dish Buildbot <buildbot-no-reply@wireshark.org>
Reviewed-by: Anders Broman <a.broman58@gmail.com>

1 files changed, 4 insertions, 1 deletions

diff --git a/doc/README.dissector b/doc/README.dissector
index 41297df7ae..ac57159991 100644
--- a/doc/README.dissector
+++ b/doc/README.dissector
@@ -1604,7 +1604,7 @@ encodings that are currently supported are:
         timespec with a 4-byte time_t.)
 
     ENC_TIME_NTP - 8 bytes; the first 4 bytes are seconds since the NTP
-        epoch (1901-01-01 00:00:00 GMT) and the next 4 bytes are 1/2^32's of
+        epoch (1900-01-01 00:00:00 GMT) and the next 4 bytes are 1/2^32's of
         a second since that second.  (I.e., a 64-bit count of 1/2^32's of a
         second since the NTP epoch, with the upper 32 bits first and the
         lower 32 bits second, even when little-endian.)
@@ -1635,6 +1635,9 @@ encodings that are currently supported are:
         second since the UN*X epoch; see section 5.3.1 "Timestamp Option"
         in RFC 3971.
 
+    ENC_TIME_MSEC_NTP - 4-8 bytes, representing a count of milliseconds since
+        the NTP epoch.  (I.e., milliseconds since the NTP epoch.)
+
 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
 encodings that are currently supported are: