[ntpwg] exposed data

[TS Glassey]

----- Original Message ----- 
From: "Danny Mayer" <mayer at ntp.isc.org>
To: "David L. Mills" <mills at udel.edu>
Cc: <ntpwg at ntp.org>
Sent: Tuesday, December 18, 2007 9:22 PM
Subject: Re: [ntpwg] exposed data


> David L. Mills wrote:
>> Harlan,
>>
>> The mode-6 protocol itself is not an issue; it just reveals what the
>> server sends. The ntpq program, which just lights up what is revealled
>> by the server, is not an issue. The ntpq program should never reveal
>> data on its own, which is why the flash decodes are so contentious.

Why not?

>> These decodes use local interpretation which can be at odds with the
>> documentation and server design.

Sure but that is a key part of being able to audit the code.

> > This violates my original design which
>> required using only the data the server sends. If decodes are needed,
>> the server should send them.

The there would need to be a method of making that happen which doesnt exist 
now.

>>
>> The ntpq program, protocol and server revelations were never intended to
>> be standardized.

Then remove it from the package since NO code which is not standardized 
should be included in the distribution.

>> The program was and is used as a diagnostic, the
>> details of which can be adjusted and/or expanded from time to time,
>> especailly as new features like orphan and Autokey are implemnted and
>> tested.

Yes but its functionality needs to be formally documented and tested with 
any release.

>> The program should be flexible and usable, even with warts.
>>
>> Your mission has absolutely no legs in the context of the protocol, ntpq
>> or revealled informatio. It has absolultely brilliant legs for the MIB
>> mission and should be seriously discussed in that context.
>>
>> Dave
>
> I agree.
>
> Danny
> _______________________________________________
> ntpwg mailing list
> ntpwg at lists.ntp.org
> https://lists.ntp.org/mailman/listinfo/ntpwg