[Ntp] I-D Action: draft-ietf-ntp-refid-updates-02.txt
internet-drafts@ietf.org Tue, 05 December 2017 05:39 UTC
Return-Path: <internet-drafts@ietf.org>
X-Original-To: ntp@ietf.org
Delivered-To: ntp@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id D8665124B18; Mon, 4 Dec 2017 21:39:12 -0800 (PST)
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
X-Test-IDTracker: no
X-IETF-IDTracker: 6.66.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <151245235284.13882.9522986234259479107@ietfa.amsl.com>
Date: Mon, 04 Dec 2017 21:39:12 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/ntp/LT6mSXHRlKa02gBd17Rs0PgxKGU>
Subject: [Ntp] I-D Action: draft-ietf-ntp-refid-updates-02.txt
X-BeenThere: ntp@ietf.org
X-Mailman-Version: 2.1.22
List-Id: <ntp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ntp>, <mailto:ntp-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ntp/>
List-Post: <mailto:ntp@ietf.org>
List-Help: <mailto:ntp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ntp>, <mailto:ntp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 05 Dec 2017 05:39:13 -0000
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 REFID Updates Authors : Harlan Stenn Sharon Goldberg Filename : draft-ietf-ntp-refid-updates-02.txt Pages : 11 Date : 2017-12-04 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. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-ntp-refid-updates/ There are also htmlized versions available at: https://tools.ietf.org/html/draft-ietf-ntp-refid-updates-02 https://datatracker.ietf.org/doc/html/draft-ietf-ntp-refid-updates-02 A diff from the previous version is available at: https://www.ietf.org/rfcdiff?url2=draft-ietf-ntp-refid-updates-02 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/
- [Ntp] I-D Action: draft-ietf-ntp-refid-updates-02… internet-drafts