[art] resolving time frames

Joe Touch <touch@isi.edu> Mon, 27 March 2017 19:34 UTC

Return-Path: <touch@isi.edu>
X-Original-To: art@ietfa.amsl.com
Delivered-To: art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C5CBA129440 for <art@ietfa.amsl.com>; Mon, 27 Mar 2017 12:34:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.899
X-Spam-Level:
X-Spam-Status: No, score=-6.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RVFD6nslVHDf for <art@ietfa.amsl.com>; Mon, 27 Mar 2017 12:34:41 -0700 (PDT)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 598D41274D2 for <art@ietf.org>; Mon, 27 Mar 2017 12:34:41 -0700 (PDT)
Received: from [128.9.184.151] ([128.9.184.151]) (authenticated bits=0) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id v2RJYGoX001785 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Mon, 27 Mar 2017 12:34:16 -0700 (PDT)
To: art@ietf.org
From: Joe Touch <touch@isi.edu>
Message-ID: <f1719642-5b85-b2c1-fe87-0ad878a6fe2a@isi.edu>
Date: Mon, 27 Mar 2017 12:34:16 -0700
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="------------CA0EB7FAAA3A8C1FDDF4AE80"
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Archived-At: <https://mailarchive.ietf.org/arch/msg/art/Ht4pkPg17IZ9b2_tmOIUAW-2AA0>
Subject: [art] resolving time frames
X-BeenThere: art@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Applications and Real-Time Area Discussion <art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/art>, <mailto:art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/art/>
List-Post: <mailto:art@ietf.org>
List-Help: <mailto:art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/art>, <mailto:art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 27 Mar 2017 19:34:43 -0000

Hi, all,

I've participated in discussions on issues with differences in time
frames twice in the past year on the main IETF list and on HTTPBIS WG:

https://mailarchive.ietf.org/arch/msg/ietf/To8dZTn9uBJLnzqIvEDPpNnA1rc
<https://mailarchive.ietf.org/arch/msg/ietf/To8dZTn9uBJLnzqIvEDPpNnA1rc>

https://lists.w3.org/Archives/Public/ietf-http-wg/2017JanMar/0406.html
<https://lists.w3.org/Archives/Public/ietf-http-wg/2017JanMar/0406.html>

This suggested the need for documenting the issue for clarification, so
that we can avoid such protracted debates in the future. As a result, I
wrote document indicated below for discussion here.

Feedback welcome.

Joe

----------

A new version of I-D, draft-touch-time-01.txt
has been successfully submitted by Joe Touch and posted to the
IETF repository.

Name:		draft-touch-time
Revision:	01
Title:		Resolving Multiple Time Scales in the Internet
Document date:	2017-03-27
Group:		Individual Submission
Pages:		17
URL:            https://www.ietf.org/internet-drafts/draft-touch-time-01.txt
Status:         https://datatracker.ietf.org/doc/draft-touch-time/
Htmlized:       https://tools.ietf.org/html/draft-touch-time-01
Htmlized:       https://datatracker.ietf.org/doc/html/draft-touch-time-01
Diff:           https://www.ietf.org/rfcdiff?url2=draft-touch-time-01

Abstract:
   Internet systems use a variety of time scales, which can complicate
   time comparisons and calculations. This document explains these
   various ways of indicating time and explains how they can be used
   together safely. This document is intended as a companion to
   Internet time as discussed in RFC 3339.