Re: [Cbor] I-D Action: draft-ietf-cbor-time-tag-02.txt

Carsten Bormann <cabo@tzi.org> Tue, 04 October 2022 22:00 UTC

Return-Path: <cabo@tzi.org>
X-Original-To: cbor@ietfa.amsl.com
Delivered-To: cbor@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AC5E0C14CE2B for <cbor@ietfa.amsl.com>; Tue, 4 Oct 2022 15:00:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.907
X-Spam-Level:
X-Spam-Status: No, score=-6.907 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, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] 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 oky--1tS1wiU for <cbor@ietfa.amsl.com>; Tue, 4 Oct 2022 15:00:35 -0700 (PDT)
Received: from gabriel-smtp.zfn.uni-bremen.de (smtp.zfn.uni-bremen.de [134.102.50.15]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BF4CAC14F73B for <cbor@ietf.org>; Tue, 4 Oct 2022 15:00:35 -0700 (PDT)
Received: from [192.168.217.124] (p5089abf5.dip0.t-ipconnect.de [80.137.171.245]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by gabriel-smtp.zfn.uni-bremen.de (Postfix) with ESMTPSA id 4Mhs8K3bVgzDCcf; Wed, 5 Oct 2022 00:00:33 +0200 (CEST)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.7\))
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <166492047271.16403.14599656441412624513@ietfa.amsl.com>
Date: Wed, 05 Oct 2022 00:00:33 +0200
X-Mao-Original-Outgoing-Id: 686613633.00506-7cc2dce7a2a37f4342a85d9beb028029
Content-Transfer-Encoding: quoted-printable
Message-Id: <A7F6327F-5C78-49AF-9243-D478FD6C1774@tzi.org>
References: <166492047271.16403.14599656441412624513@ietfa.amsl.com>
To: cbor@ietf.org
X-Mailer: Apple Mail (2.3608.120.23.2.7)
Archived-At: <https://mailarchive.ietf.org/arch/msg/cbor/oNsjP2YHFhQnOTEnh-A8hB15OUw>
Subject: Re: [Cbor] I-D Action: draft-ietf-cbor-time-tag-02.txt
X-BeenThere: cbor@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: "Concise Binary Object Representation \(CBOR\)" <cbor.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/cbor>, <mailto:cbor-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/cbor/>
List-Post: <mailto:cbor@ietf.org>
List-Help: <mailto:cbor-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/cbor>, <mailto:cbor-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 04 Oct 2022 22:00:37 -0000

Time-tag-02 fills in proposals for all the TBDs that were outstanding in the text.
This version is intended by the authors as ready for working-group last call, synchronized with a WGLC of the IXDTF specification in SEDATE.

The diff should be quite self-explanatory (and is, except maybe for the IANA tables, quite bite-sized):
> https://www.ietf.org/rfcdiff?url2=draft-ietf-cbor-time-tag-02


I have proposed this update for discussion at the CBOR interim tomorrow.

Grüße, Carsten


> On 2022-10-04, at 23:54, internet-drafts@ietf.org wrote:
> 
> 
> A New Internet-Draft is available from the on-line Internet-Drafts directories.
> This draft is a work item of the Concise Binary Object Representation Maintenance and Extensions WG of the IETF.
> 
>        Title           : Concise Binary Object Representation (CBOR) Tags for Time, Duration, and Period
>        Authors         : Carsten Bormann
>                          Ben Gamari
>                          Henk Birkholz
>  Filename        : draft-ietf-cbor-time-tag-02.txt
>  Pages           : 17
>  Date            : 2022-10-04
> 
> Abstract:
>   The Concise Binary Object Representation (CBOR, RFC 8949) is a data
>   format whose design goals include the possibility of extremely small
>   code size, fairly small message size, and extensibility without the
>   need for version negotiation.
> 
>   In CBOR, one point of extensibility is the definition of CBOR tags.
>   RFC 8949 defines two tags for time: CBOR tag 0 (RFC3339 time as a
>   string) and tag 1 (Posix time as int or float).  Since then,
>   additional requirements have become known.  The present document
>   defines a CBOR tag for time that allows a more elaborate
>   representation of time, as well as related CBOR tags for duration and
>   time period.  It is intended as the reference document for the IANA
>   registration of the CBOR tags defined.
> 
> 
>   // The present version (-02) fills in proposals for all TBDs that
>   // were outstanding.
> 
> 
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-ietf-cbor-time-tag/
> 
> There is also an HTML version available at:
> https://www.ietf.org/archive/id/draft-ietf-cbor-time-tag-02.html
> 
> A diff from the previous version is available at:
> https://www.ietf.org/rfcdiff?url2=draft-ietf-cbor-time-tag-02