@techreport{stenn-ntp-extension-fields-09,
    number =    {draft-stenn-ntp-extension-fields-09},
    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/09/},
    author =    {Harlan Stenn and Professor David L. Mills},
    title =     {{Network Time Protocol Version 4 (NTPv4) Extension Fields}},
    pagetotal = 13,
    year =      2019,
    month =     mar,
    day =       26,
    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 cannot be conveyed in the basic NTP packet. This document updates RFC 5905 {[}RFC5905{]} by clarifying some points regarding NTP extension fields and their usage with legacy Message Authentication Codes (MACs), and removes wasteful requirements added by RCF 7822 {[}RFC7822{]}. This proposal deprecates RFC 7822 {[}RFC7822{]}. RFC EDITOR: PLEASE REMOVE THE FOLLOWING PARAGRAPH BEFORE PUBLISHING: The source code and issues list for this draft can be found in https://github.com/hstenn/ietf-ntp-extension-fields},
}