[ntpwg] Additional text for SNTP

[Danny Mayer]

Dave,

The drive to add this came from the aberrent behavior of ws32time. This 
way it is made very clear that a standards conforming SNTP client will 
do the right thing. Specifying the allowed modes of the packets also 
helps people to know what ones to send out and to receive. We cannot 
assume that the Internet standards police when they eventually get off 
their coffee break will shut down the rascals.

Danny

David L. Mills wrote:
> Danny,
> 
> I'm not sure any words are necessary. An SNTP client is ipso facto a 
> client and by spec sends only mode-3 messages. We have defined an SNTP 
> server and an SNTP client, but not an SNTP peer. Also, I'm a little 
> uneasy about saying what an SNTP client can or cannot accept. It can't 
> have dependent clients, so in truth we don't care what it does with the 
> server packet other than to say if it follows the peer process rules it 
> will make good clock.
> 
> Dave
> 
> Danny Mayer wrote:
> 
>> I'd like to propose additional text be added to section 14 on SNTP in
>> the NTPv4 protocol draft. I'm requesting this addition due to an issue
>> that came up last week with an SNTP client.
>>
>> Suggested text:
>>
>> "An SNTP client MUST only send mode 3 packets (client) and MUST only
>> accept mode 4 (server) and mode 5 (broadcast) packets. An SNTP client
>> MAY send or receive mode 6 (NTP control) packet. All other packet modes
>> MUST be ignored.
>>
>> An SNTP server MUST not send mode 3 (client) packets."
>>
>> Any objections or refinements?
>>
>> Danny
>> _______________________________________________
>> ntpwg mailing list
>> ntpwg at lists.ntp.org
>> https://lists.ntp.org/mailman/listinfo/ntpwg
> 
> 
> _______________________________________________
> ntpwg mailing list
> ntpwg at lists.ntp.org
> https://lists.ntp.org/mailman/listinfo/ntpwg
>