%% You should probably cite draft-ietf-ntp-refid-updates-05 instead of this revision.
@techreport{ietf-ntp-refid-updates-03,
    number =    {draft-ietf-ntp-refid-updates-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-ietf-ntp-refid-updates/03/},
    author =    {Harlan Stenn and Sharon Goldberg},
    title =     {{Network Time Protocol REFID Updates}},
    pagetotal = 11,
    year =      2018,
    month =     jun,
    day =       6,
    abstract =  {RFC 5905 {[}RFC5905{]}, section 7.3, "Packet Header Variables", defines the value of the REFID, the system peer for the responding host. In the past, for IPv4 associations the IPv4 address is used, and for IPv6 associations the first four octets of the MD5 hash of the IPv6 are used. There are at least three shortcomings to this approach, and this proposal will address the three so noted. One is that knowledge of the system peer is "abusable" information and should not be generally available. The second is that the four octet hash of the IPv6 address looks very much like an IPv4 address, and this is confusing. The third is that a growing number of low-stratum servers want to offer leap-smeared time to their clients, and there is no obvious way to know if a server is offering accurate time or leap- smeared time.},
}