%% You should probably cite draft-stenn-ntp-extension-fields-09 instead of this revision. @techreport{stenn-ntp-extension-fields-03, number = {draft-stenn-ntp-extension-fields-03}, type = {Internet-Draft}, institution = {Internet Engineering Task Force}, publisher = {Internet Engineering Task Force}, note = {Work in Progress}, url = {https://datatracker.ietf.org/doc/draft-stenn-ntp-extension-fields/03/}, author = {Harlan Stenn}, title = {{Network Time Protocol Version 4 (NTPv4) Extension Fields}}, pagetotal = 16, year = 2017, month = dec, day = 4, abstract = {Network Time Protocol version 4 (NTPv4) defines the optional usage of extension fields. An extension field, as defined in RFC 5905 {[}RFC5905{]} and RFC 5906 {[}RFC5906{]}, resides after the end of the NTP header, and supplies optional capabilities or information that is not conveyed in the standard NTP header. This document updates RFC 5905 {[}RFC5905{]} by clarifying some points regarding NTP extension fields and their usage with legacy Message Authentication Codes (MACs). This proposal obsoletes RFC 7822 {[}RFC7822{]}.}, }