[Sedate] Antw: Re: [art] Antw: [EXT] Re: [Ntp] [Cbor] Two specifications on timestamps nearing WGLC

Ulrich Windl <Ulrich.Windl@rz.uni-regensburg.de> Thu, 20 October 2022 15:05 UTC

Return-Path: <Ulrich.Windl@rz.uni-regensburg.de>
X-Original-To: sedate@ietfa.amsl.com
Delivered-To: sedate@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BD562C14F73B; Thu, 20 Oct 2022 08:05:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.91
X-Spam-Level:
X-Spam-Status: No, score=-6.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id q6iy5rmEePKm; Thu, 20 Oct 2022 08:05:35 -0700 (PDT)
Received: from mx2.uni-regensburg.de (mx2.uni-regensburg.de [IPv6:2001:638:a05:137:165:0:3:bdf8]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DE8EAC14F734; Thu, 20 Oct 2022 08:05:30 -0700 (PDT)
Received: from mx2.uni-regensburg.de (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id 69D736000050; Thu, 20 Oct 2022 17:05:17 +0200 (CEST)
Received: from gwsmtp.uni-regensburg.de (gwsmtp1.uni-regensburg.de [132.199.5.51]) by mx2.uni-regensburg.de (Postfix) with ESMTP id 4A628600004D; Thu, 20 Oct 2022 17:05:17 +0200 (CEST)
Received: from uni-regensburg-smtp1-MTA by gwsmtp.uni-regensburg.de with Novell_GroupWise; Thu, 20 Oct 2022 17:05:18 +0200
Message-Id: <635163AC020000A10004EC4E@gwsmtp.uni-regensburg.de>
X-Mailer: Novell GroupWise Internet Agent 18.4.1
Date: Thu, 20 Oct 2022 17:05:16 +0200
From: Ulrich Windl <Ulrich.Windl@rz.uni-regensburg.de>
To: cabo@tzi.org
Cc: art@ietf.org, cbor@ietf.org, "ntp@ietf.org" <ntp@ietf.org>, sedate@ietf.org, "tictoc@ietf.org" <tictoc@ietf.org>
References: <19C0959C-2DFF-4FA6-9691-792CD2AF5E09@tzi.org> <f7a05134-7ec0-411a-fcc5-d0e80c74d6c6@it.aoyama.ac.jp> <2620A4D0-F624-4E31-BDD1-860B40F7A31D@tzi.org> <193653.1665119732@dooku> <CA4866D1-C1E7-4C58-9D85-088A02885FD0@tzi.org> <9621884E0BC501528B6BB591@PSB> <F30D7B75-B3D3-4B99-83B7-809B2EF4B760@tzi.org> <8ED6029F05884D21580EA2AF@PSB> <6350EDD1020000A10004EBFC@gwsmtp.uni-regensburg.de> <8E62549B-9BA2-4275-9E9A-B2F9B75A8930@tzi.org>
In-Reply-To: <8E62549B-9BA2-4275-9E9A-B2F9B75A8930@tzi.org>
Mime-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 8bit
Content-Disposition: inline
Archived-At: <https://mailarchive.ietf.org/arch/msg/sedate/l5EOzMqbkFJCg8SDrykYjNZHz-0>
Subject: [Sedate] Antw: Re: [art] Antw: [EXT] Re: [Ntp] [Cbor] Two specifications on timestamps nearing WGLC
X-BeenThere: sedate@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Serialising Extended Data About Times and Events <sedate.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sedate>, <mailto:sedate-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/sedate/>
List-Post: <mailto:sedate@ietf.org>
List-Help: <mailto:sedate-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sedate>, <mailto:sedate-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 20 Oct 2022 15:05:36 -0000

>>> Carsten Bormann <cabo@tzi.org> schrieb am 20.10.2022 um 15:29 in Nachricht
<8E62549B-9BA2-4275-9E9A-B2F9B75A8930@tzi.org>:
> On 20. Oct 2022, at 08:42, Ulrich Windl <Ulrich.Windl@rz.uni-regensburg.de>

> wrote:
>> 
>>> On the other hand, 3339 contains references to ISO 8601:1988
>>> and, for that matter, ISO 8601:2000 and at least the former is
>>> rather close to normative.  So, give the availability (or last
>> 
>> You won't like this type of comment, but isn't a reference to a standard, 
> that is not available anymore, equivalent to referring to no standard?
>> I did not inspect ISO standards, but for any evolving standard I'd expect 
> that the previous versions should be derivable from the current one; 
> otherwise it's just nonsense.
> 
> I’m not sure I understand what exactly you are expecting here, but we should

> not discuss this in generalities, but for the specific standard that we want

> to maintain.

What I wanted to express is: It seems old versions of the standard just seemed
to have vanished, and only newer versions are available.
So when referring to an old version that practically does not exist any more
(i.e. is not readable), any reference to such version is void.

[...]

Regards,
Ulrich Windl

> Grüße, Carsten