IETF Logo Mail Archive

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

Vadim Goncharov <vadimnuclight@gmail.com> Thu, 19 January 2023 19:27 UTC

Return-Path: <vadimnuclight@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 7E4B7C14F74A for <cbor@ietfa.amsl.com>; Thu, 19 Jan 2023 11:27:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level:
X-Spam-Status: No, score=-2.098 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 x9NaKf0iZEkt for <cbor@ietfa.amsl.com>; Thu, 19 Jan 2023 11:27:57 -0800 (PST)
Received: from mail-ej1-x635.google.com (mail-ej1-x635.google.com [IPv6:2a00:1450:4864:20::635]) (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 58990C14F731 for <cbor@ietf.org>; Thu, 19 Jan 2023 11:27:57 -0800 (PST)
Received: by mail-ej1-x635.google.com with SMTP id u19so8342618ejm.8 for <cbor@ietf.org>; Thu, 19 Jan 2023 11:27:57 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=content-transfer-encoding:mime-version:references:in-reply-to :message-id:subject:cc:to:from:date:from:to:cc:subject:date :message-id:reply-to; bh=UvQ+p87+nbwb48AWUapxNI1apfxOItT+wtWGa2lqaX4=; b=q0adTtTqyesy6bGq6am3yANz/sKZBSrX/0W+VPIIA+SyrWBDS+yki+4FVBrVKKf+mB LlfcdDFkjQ25ey7xUvFD4wL6ng5eJjhC4uOdLZwiqTYshTAQqpKiJ5b9OLvKSgsyeOJv jhDUR8Eu1QXSnEKgfZzVTWoH9BY09qsllgJvowBenz3QCZSOYtYIiqjtjgficoDxl3Hf RG9VYJou3gs7rFhlMgQTwS9UAOZw3UW2TLrUBa819+Q8FcNgHjgScE5KqiteSY6GhEYV hlQlCMbxQa19GJAKrEEdoHx6W9k8SSfYcJPfxdQySYAxGzOQVnuHeB9wvtGI3G/oflF1 LE5w==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=content-transfer-encoding:mime-version:references:in-reply-to :message-id:subject:cc:to:from:date:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=UvQ+p87+nbwb48AWUapxNI1apfxOItT+wtWGa2lqaX4=; b=WtpL+tPXEUgklPQHfYz5xpvKEkeYDs2vZv7XH2mJLKvh+jL88716bhjQVqX6x3rc2M LTwBXXzjdekoJM2P8dHQCHuLWTG2Z33TNQF3m9XJYnE5a0xEwV85Vwy5oL42BYhOlpV1 BuOnMOrMIuRj2/U0tc8HX/F/ZLbHkzoPXmFwvjFTbt1AqHqFFVrmDANRiu2BzvI4U4HN 3dcN6Vss9PVM9lVHrpQVTu1dVSMCPeRsGcY6j5uw2meCEOQcmfF2eLzjyok1a/yrUEQk uWOQGDLfu3mCM3PVsu1W5xEMVHt8l7eOr5nmk95UW0H8875QMuwH9pI/W8BSIBMmaSRa U08w==
X-Gm-Message-State: AFqh2krPJeDG7WyYYDrwPlz/mWrHswSTAJoFAWbcsknupC/bHmPoN9r4 RfFgFryXV05KUNx1rMQvw1U=
X-Google-Smtp-Source: AMrXdXvQhnJtNibJjBxxglq0LjCQfKV0/ggiymR6hRF1HCfF+jwZYvguY03sg39RfRUnUS7m507HcA==
X-Received: by 2002:a17:906:16c5:b0:7be:e26a:6104 with SMTP id t5-20020a17090616c500b007bee26a6104mr11732551ejd.52.1674156475328; Thu, 19 Jan 2023 11:27:55 -0800 (PST)
Received: from nuclight (broadband-77-37-180-193.ip.moscow.rt.ru. [77.37.180.193]) by smtp.gmail.com with ESMTPSA id r2-20020a17090609c200b007bd28b50305sm16673066eje.200.2023.01.19.11.27.54 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Thu, 19 Jan 2023 11:27:55 -0800 (PST)
Date: Thu, 19 Jan 2023 22:27:53 +0300
From: Vadim Goncharov <vadimnuclight@gmail.com>
To: Carsten Bormann <cabo@tzi.org>
Cc: Emile Cormier <emile.cormier.jr@gmail.com>, cbor@ietf.org
Message-ID: <20230119222753.7c3744b7@nuclight>
In-Reply-To: <C10ACFB0-9C44-4B17-A18E-BAE367984065@tzi.org>
References: <167345627851.15097.9738487459393843034@ietfa.amsl.com> <CAM70yxD2Z52JsJ=XHFFrJWFuAEG5oHv-B8gf6zRYVK4fhpDpeQ@mail.gmail.com> <0B9B7A5E-D61E-4B97-9CE5-9A8AE7055F50@tzi.org> <20230117004326.5642c6ab@nuclight> <CAM70yxAs=9S-H6ve2HfDf5W=f4cKGZ3B=AXJV==vm26ERs9-mg@mail.gmail.com> <20230117204606.2b742f14@nuclight> <CAM70yxAeLGmiPyidn1zc64rjRcKNHp7hSUt+d6veH-AqguObkw@mail.gmail.com> <20230117220443.6c5054e7@nuclight> <CAM70yxBbNtn0D91tZ1mSY3Cg-MMVnpaCodius5MWH-wEjQHu-g@mail.gmail.com> <5EFA83F3-7FD3-4B11-A23A-8D98E59542AB@tzi.org> <CAM70yxCm7PV9bD5Wf=rJpVHKrTpZ+kRyHWW+_E5vQF9s6BYusg@mail.gmail.com> <C10ACFB0-9C44-4B17-A18E-BAE367984065@tzi.org>
X-Mailer: Claws Mail 3.19.0 (GTK+ 2.24.33; amd64-portbld-freebsd12.3)
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/cbor/UjJHJCxRo2Rh-QkMBWmDzPVlMuA>
Subject: Re: [Cbor] I-D Action: draft-ietf-cbor-time-tag-04.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: Thu, 19 Jan 2023 19:27:59 -0000

On Thu, 19 Jan 2023 00:18:25 +0100
Carsten Bormann <cabo@tzi.org> wrote:

> > What about the ability to encode a local time having an unspecified
> > time zone? The C++ std::chrono::local_time duration is computed
> > from the date time of day the same way as std::chrono::sys_time
> > (POSIX), except that the time zone is unspecified instead of UTC.
> > All that would be needed is a "Local" time scale to be added to the
> > time scale registry. I already understand that you want to launch
> > the time tag RFC with only the UTC and TAI time scales for now.  
> 
> As was discussed over in SEDATE as well, there even are some noises
> that NTPv5 might adopt such a locally defined time scale (naysayers
> notwithstanding that argue that NTP can only be used internet-wide
> where such a locally defined time scale would not apply).

Sounds like not a very good idea... BTW, do they have changes in format
to suport e.g. decimal? And what/where is SEDATE ?

-- 
WBR, @nuclight

v2.43.4 | Report a Bug | By Email | System Status