IETF Logo Mail Archive

Re: [Cbor] [core] YANG-CBOR, Date formats

Carsten Bormann <cabo@tzi.org> Wed, 06 July 2022 18:02 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 C3BB7C15A745; Wed, 6 Jul 2022 11:02:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.909
X-Spam-Level:
X-Spam-Status: No, score=-6.909 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, 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 ZlJZiBYiaglw; Wed, 6 Jul 2022 11:02:47 -0700 (PDT)
Received: from gabriel-smtp.zfn.uni-bremen.de (gabriel-smtp.zfn.uni-bremen.de [IPv6:2001:638:708:32::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 AB9BCC15A742; Wed, 6 Jul 2022 11:02:47 -0700 (PDT)
Received: from [192.168.217.118] (p5089ad4f.dip0.t-ipconnect.de [80.137.173.79]) (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 4LdS7T25NrzDCbR; Wed, 6 Jul 2022 20:02:45 +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: <7378.1657129816@localhost>
Date: Wed, 06 Jul 2022 20:02:44 +0200
Cc: Esko Dijk <esko.dijk@iotconsultancy.nl>, "cbor@ietf.org" <cbor@ietf.org>, "core@ietf.org" <core@ietf.org>, anima@ietf.org
X-Mao-Original-Outgoing-Id: 678823364.645691-595c407505d015bb848040827908756f
Content-Transfer-Encoding: quoted-printable
Message-Id: <4CBE269A-0983-43C0-A23E-E5266493F1A3@tzi.org>
References: <CALaySJLPtUjdfVss17noK=18RyczpcCGNu=im8CBpiQz=WiLWA@mail.gmail.com> <CALaySJKUNh-AkJa87sCDpzf9OHV8H367VQyzyozXCCXxphUARw@mail.gmail.com> <CALaySJ+P2sP7BU7bNSxRJBByyp04rzVZuukq_e+9wbb5WPRSFQ@mail.gmail.com> <CALaySJKxht1gd1+3mNiAH-kLUAxjdPPk3doK50C_xS74LG+YTQ@mail.gmail.com> <CALaySJJNXpcaBhWQiK+4vmUk+s6mfMvwQFnB9d4YfDtdet09OQ@mail.gmail.com> <CALaySJ+8qLX6kuqXcRp6-OHU_MBkkASfH80bf2EePueduMsCTw@mail.gmail.com> <CALaySJJ+rhJMOfhhc9jDxz_9y+VpyrNoMcFy_b00Ui05c+g4zw@mail.gmail.com> <258768.1656499296@dooku> <274622.1656503120@dooku> <2913DF0F-8F46-47E0-92AE-C29E5AE20578@tzi.org> <DU0P190MB197851016C1B73DD8E86F2B9FD809@DU0P190MB1978.EURP190.PROD.OUTLOOK.COM> <7378.1657129816@localhost>
To: Michael Richardson <mcr+ietf@sandelman.ca>
X-Mailer: Apple Mail (2.3608.120.23.2.7)
Archived-At: <https://mailarchive.ietf.org/arch/msg/cbor/MsXI81gBX7OD8hLtBPxr-0JqZf0>
Subject: Re: [Cbor] [core] YANG-CBOR, Date formats
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: Wed, 06 Jul 2022 18:02:50 -0000

> 
>> We can do the same for date fields, e.g.
>> "created-on" -> "created-on-epochtime"
>> "expires-on" -> "expires-on-epochtime"
> 
> I don't mind doing this.
> Does it establish some precedent that others may dislike?

I don’t think there is anything with bespoke formats.
The need to do something at the serialization layer comes in when you want to use some standard modules.
If this is not needed here, just go ahead and define data types specific to constrained environments.

Grüße, Carsten

v2.23.0 | Report a Bug | By Email