Re: [Ntp] NTP WG virtual interim -- Thursday, 17 September 2020, 1530 - 1700 UTC

[Hal Murray <[e-mail]>]

> 4. Call for Adoption results/discussion on draft-mlichvar-ntp-alternative-port
> 7.  Any updates on NTP v5 requirements and next steps

Crazy thought dept...  Can we combine those?  Can we quickly come up with a 
packet format for v5 that has few enough changes so we can implement it 
quickly and also has room/hooks for everything we want to do tomorrow?

--------

> 6.  Any updates on NTS Development, Measurement and Testing

I think we are beyond testing-- mostly waiting for the RFC to come out so we 
have a flag to wave.

What sort of measurements would be helpful?  I have a couple of servers in the 
pool.

The biggest surprise to me was the amount of crap the NTS-KE server gets on 
port 123.  I assume it's bad guys probing.  See the bottom 2 lines below.

uptime:                 165729

NTS client sends:            36399
NTS client recvs good:       35948
NTS client recvs w error:    0
NTS server recvs good:       36938
NTS server recvs w error:    11595
NTS server sends:            36938
NTS make cookies:            127470
NTS decode cookies:          47970
NTS decode cookies old:      554
NTS decode cookies too old:  0
NTS decode cookies error:    0
NTS KE probes good:          28
NTS KE probes_bad:           5
NTS KE serves good:          9984
NTS KE serves_bad:           13374


-- 
These are my opinions.  I hate spam.