Re: [Cbor] Working group last call on draft-ietf-cbor-time-tag-04

Barry Leiba <barryleiba@computer.org> Tue, 17 January 2023 13:41 UTC

Return-Path: <barryleiba@gmail.com>
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 B588CC14F75F for <cbor@ietfa.amsl.com>; Tue, 17 Jan 2023 05:41:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.547
X-Spam-Level:
X-Spam-Status: No, score=-1.547 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FORGED_FROMDOMAIN=0.096, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.25, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=no 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 gazTohuardqu for <cbor@ietfa.amsl.com>; Tue, 17 Jan 2023 05:41:20 -0800 (PST)
Received: from mail-ej1-f52.google.com (mail-ej1-f52.google.com [209.85.218.52]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 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 0B504C14EB14 for <cbor@ietf.org>; Tue, 17 Jan 2023 05:41:20 -0800 (PST)
Received: by mail-ej1-f52.google.com with SMTP id hw16so63573228ejc.10 for <cbor@ietf.org>; Tue, 17 Jan 2023 05:41:19 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=content-transfer-encoding:to:subject:message-id:date:from :in-reply-to:references:mime-version:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=+SMMxzJgFdMhW7GefxmPYoB6FP86dOrTyqiKNqrfmw8=; b=fvvIgRfqMDvzdTs490jgwDsbEZZFrz1yFNBlu3TmuKT9St/ahRH8muTnnTWyp3rwNx d4c50etusA1dECg/Rc/f5yUuScqpw934GWJNc9yLSJQr38BdB2nCFBEa42cfPZH/lAHC b6jJS9H/D2q7KW0pGJEzNH5dArdPnrJtzOqwVMN9lCmbEWD9XUFhUgHgbsjmSI7l8GHQ m9xYPnDo5Lm4CeLg+w7Kru5jL0pn9LRnlrTBsL0Sk3CjwOkh2oWnV6CyVjihkhUvHz1c GFRdFQuwm4u2EYewU5i9NXkesIKtQey2+VXXsVtSWfUM7Td1oA//x5crkIi6S4+QB9NG 5byg==
X-Gm-Message-State: AFqh2komnX1XqOdI8kCpHHqz94quKARIYqJ/i/Gj3MncoQ3fFjsuh4Zr 6E5eqELnkzIz1K6W8f0VATuqOkHbtJn8fGPhxGVV2H7V
X-Google-Smtp-Source: AMrXdXtn65Z19ObLj9H7q+B3E44Inq7WD48dnE9fihXxidxQcfgDAMjJBlf1Wex023CMJxp4iRVx3+vYjw9WRLHlZTk=
X-Received: by 2002:a17:906:aada:b0:86c:b928:3e44 with SMTP id kt26-20020a170906aada00b0086cb9283e44mr387591ejb.264.1673962877891; Tue, 17 Jan 2023 05:41:17 -0800 (PST)
MIME-Version: 1.0
References: <CALaySJKTDJqN_9aBLUYxHo3ei7e+NFndZPa3zQNg4p-zaL+KXA@mail.gmail.com>
In-Reply-To: <CALaySJKTDJqN_9aBLUYxHo3ei7e+NFndZPa3zQNg4p-zaL+KXA@mail.gmail.com>
From: Barry Leiba <barryleiba@computer.org>
Date: Tue, 17 Jan 2023 08:41:06 -0500
Message-ID: <CALaySJK6hYdudOeEEarH2-MHvndjvJDL0djNL1wGZ13LML+L6g@mail.gmail.com>
To: cbor@ietf.org
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/cbor/Nhmd8foeN-PXFE4apMkvTz7aKq0>
Subject: Re: [Cbor] Working group last call on draft-ietf-cbor-time-tag-04
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, 17 Jan 2023 13:41:23 -0000

As document shepherd, I have one issue that I want to discuss about
this document: its intended RFC status.

It is currently specified as Informational, which is sufficient for
simply making a code-point registration.  But I think the document
goes a bit beyond that, specifying how to use time elements in CBOR,
such that it's likely to be normatively referenced as a standard for
that.  We should consider whether Proposed Standard is more
appropriate at this point.

Comments?

Barry

On Wed, Jan 11, 2023 at 1:16 PM Barry Leiba <barryleiba@computer.org> wrote:
>
> Now begins a working group last call on “CBOR Tags for Time, Duration,
> and Period”, to end on Friday, 27 January 2023.  Please give the
> document a good look and post any comments to the CBOR mailing list.
> It would also be helpful to get a few “I reviewed it and it’s ready”
> comments.
>
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-ietf-cbor-time-tag/
>
> A diff from the previous version is available at:
> https://author-tools.ietf.org/iddiff?url2=draft-ietf-cbor-time-tag-04&url1=draft-ietf-cbor-time-tag-02
>
> --
> Barry