Wireshark-bugs: [Wireshark-bugs] [Bug 6611] NTP packets incorrectly display the date for a times
Date Index · Thread Index · Other Months · All Mailing Lists
Date Prev · Date Next · Thread Prev · Thread Next
From: bugzilla-daemon@xxxxxxxxxxxxx
Date: Tue, 29 Nov 2011 06:52:07 -0800 (PST)
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=6611

--- Comment #7 from Daniel Rich <qianyilong@xxxxxxxxx> 2011-11-29 06:52:06 PST ---
> 
> In reference to the RFC, zero is used to indicate 'no value', hence NULL is
> appropriate.

Fair enough, that makes sense that it should be treated as 'no value' or NULL,
but what is the correct thing to display for a NULL value. I think it still
makes more sense to display Jan 1 1900. This would only be displayed for the
NULL value and would properly communicate to the user that there is no data.

Since Jan 1, 1970 is a valid date that corresponds to valid non-zero non-NULL
data it seems to me that a NULL value should not display that date.

If you guys are ok with that collision between a NULL value and non-NULL value
I am fine with leaving it as is since it is fairly minor and deals with dates
that shouldn't happen anytime soon.

-- 
Configure bugmail: https://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching all bug changes.