I-D Action: draft-stenn-ntp-suggest-refid-04.txt

internet-drafts@ietf.org Wed, 03 October 2018 07:14 UTC

MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
Cc: ntp@ietf.org
Subject: I-D Action: draft-stenn-ntp-suggest-refid-04.txt
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: ntp@ietf.org
Message-ID: <153855084340.9120.16478721588737058749@ietfa.amsl.com>
Date: Wed, 03 Oct 2018 00:14:03 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/i-d-announce/qkxBYrfT2wsrofG2pH6Czojfeac>

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Network Time Protocol WG of the IETF.

        Title           : Network Time Protocol Suggest REFID Extension Field
        Author          : Harlan Stenn
	Filename        : draft-stenn-ntp-suggest-refid-04.txt
	Pages           : 6
	Date            : 2018-10-03

Abstract:
   NTP has been widely used through several revisions, with the latest
   being RFC 5905 [RFC5905].  A core component of the protocol and the
   algorithms is the Reference ID, or REFID, which is used to identify
   the source of time used for synchronization.  Traditionally, when the
   source of time was another system the REFID was the IPv4 address of
   that other system.  The core purpose of the REFID is to prevent a
   one-degree timing loop, where if A has several timing sources that
   include B, if B decides to get its time from A we don't want A then
   deciding to get its time from B.  The REFID is considered to be
   "public data" and is a vital core-component of the base NTP packet.
   If a system's REFID is the IPv4 address of its system peer, an
   attacker can try to use that information to send spoofed time packets
   to either or both the target or the target's server, attempting to
   cause a disruption in time service.  This proposal is a backward-
   compatible way for a time source to tell its peers or clients "If you
   use me as your system peer, use this nonce as your REFID."  This
   nonce SHOULD be untraceable to the original system, and if it is used
   as the REFID this type of attack is prevented.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-stenn-ntp-suggest-refid/

There are also htmlized versions available at:
https://tools.ietf.org/html/draft-stenn-ntp-suggest-refid-04
https://datatracker.ietf.org/doc/html/draft-stenn-ntp-suggest-refid-04

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-stenn-ntp-suggest-refid-04


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

I-D Action: draft-stenn-ntp-suggest-refid-04.txt internet-drafts