Network Time Protocol Best Current Practices
RFC 8633
also known as BCP 223
Revision differences
Document history
Date | By | Action |
---|---|---|
2023-12-12
|
(System) | Imported membership of rfc8633 in bcp223 via sync to the rfc-index |
2023-12-12
|
(System) | No history of BCP223 is currently available in the datatracker before this point |
2019-10-18
|
Bernie Volz | Assignment of request for Early review by INTDIR to Tatuya Jinmei was marked no-response |
2019-08-19
|
Gunter Van de Velde | Closed request for Last Call review by OPSDIR with state 'Overtaken by Events' |
2019-08-19
|
Gunter Van de Velde | Assignment of request for Last Call review by OPSDIR to Joe Clarke was marked no-response |
2019-07-18
|
(System) | Received changes through RFC Editor sync (created alias RFC 8633, changed abstract to 'The Network Time Protocol (NTP) is one of the oldest protocols … Received changes through RFC Editor sync (created alias RFC 8633, changed abstract to 'The Network Time Protocol (NTP) is one of the oldest protocols on the Internet and has been widely used since its initial publication. This document is a collection of best practices for the general operation of NTP servers and clients on the Internet. It includes recommendations for the stable, accurate, and secure operation of NTP infrastructure. This document is targeted at NTP version 4 as described in RFC 5905.', changed pages to 26, changed standardization level to Best Current Practice, changed state to RFC, added RFC published event at 2019-07-18, changed IESG state to RFC Published, created alias BCP 223) |
2019-07-18
|
(System) | RFC published |