[calsify] Fwd: New Timestamp Draft

Ujjwal Sharma <ryzokuken@igalia.com> Fri, 22 January 2021 21:23 UTC

Return-Path: <ryzokuken@igalia.com>
X-Original-To: calsify@ietfa.amsl.com
Delivered-To: calsify@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8BDBC3A150C for <calsify@ietfa.amsl.com>; Fri, 22 Jan 2021 13:23:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.599
X-Spam-Level:
X-Spam-Status: No, score=-0.599 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, RCVD_IN_SORBS_WEB=1.5, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=igalia.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dqe0MYTbtzsd for <calsify@ietfa.amsl.com>; Fri, 22 Jan 2021 13:23:48 -0800 (PST)
Received: from fanzine.igalia.com (fanzine.igalia.com [178.60.130.6]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BC7C73A150D for <calsify@ietf.org>; Fri, 22 Jan 2021 13:23:47 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=igalia.com; s=20170329; h=Content-Transfer-Encoding:Content-Type:In-Reply-To:MIME-Version:Date:Message-ID:From:Cc:To:References:Subject; bh=kt1vVx7UZR/6LbvB+VjaNrRDE6QeD8KHkaodkZJf0H4=; b=g4HtD/7C1Cfvg8ZFlK1Z479pSfNpQROTjY/gBr/n5lkQyrnTlj7NzDKqSpsyyDNXAT+0RI0inYE5YQNFRWrtSNwdQCS1uEMjtY0hnmTWeHTzp97xE4ZPEMrLU7xqzUdg2Q3mWqXSfuNGGKiHwsgdTDkBm2G82KvMRUvwk8Iv9SSPcXVsbvaaysveLSI+PPPXDpOEC1stPVYirrpQaq9xV8+U24a87WkidK8avcvl5Bxl82cBBOWebBVmbnUWOq+MnZBHDeHf+wjr4gg3yQkIdt5WfQhqHZwNDKYUpCIvNBVW45cszNqrQagbzT7UNx08Ouo2LPVx+XI6PttpnSjySQ==;
Received: from [183.83.210.210] (helo=[192.168.0.190]) by fanzine.igalia.com with esmtpsa (Cipher TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim) id 1l33uD-00014L-OP; Fri, 22 Jan 2021 22:23:45 +0100
References: <5927c3a3-9539-553d-598a-18d8bdadb244@igalia.com>
To: "calsify@ietf.org" <calsify@ietf.org>
Cc: Ned Freed <ned.freed@mrochek.com>
From: Ujjwal Sharma <ryzokuken@igalia.com>
Organization: Igalia S.L.
X-Forwarded-Message-Id: <5927c3a3-9539-553d-598a-18d8bdadb244@igalia.com>
Message-ID: <c9a1caed-829a-2339-21c1-5f0970110863@igalia.com>
Date: Sat, 23 Jan 2021 02:53:34 +0530
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.6.1
MIME-Version: 1.0
In-Reply-To: <5927c3a3-9539-553d-598a-18d8bdadb244@igalia.com>
Content-Type: text/plain; charset="utf-8"
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/calsify/L7JzzyKTBrBml-I30xQ_arpK7dM>
Subject: [calsify] Fwd: New Timestamp Draft
X-BeenThere: calsify@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: <calsify.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/calsify>, <mailto:calsify-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/calsify/>
List-Post: <mailto:calsify@ietf.org>
List-Help: <mailto:calsify-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/calsify>, <mailto:calsify-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 22 Jan 2021 21:23:52 -0000

CCing the Calsify ML because I didn't include it in the original email
by mistake.

-------- Forwarded Message --------
Subject: Re: [calsify] New Timestamp Draft
Date: Sat, 23 Jan 2021 02:51:00 +0530
From: Ujjwal Sharma <ryzokuken@igalia.com>
Organization: Igalia S.L.
To: Ned Freed <ned.freed@mrochek.com>

Hi Ned!

I could not agree with you more on the different matters. Here's the
response to the specific points raised by you.

On 23/01/2021 12.17 am, Ned Freed wrote:
> +1. The stability of this specification has been invaluable.

Please refer to my email to Eliot for more clarification on this.
Overall, this is a goal that I share wholeheartedy, and the whole idea
behind the new draft is to design it in a way that is very generalized
and that allows us to avoid any further additions to it and keep a
similar level of stability. Note for example the deferring of key
selection and standardization to bodies like IANA and Unicode consortium.

> +1. And if there's some sort of liason with ISO or whoever is responsible 
> for this, they should be engaged.

My understanding of the situation has been that this liason would be
CalConnect. By all means, we have been collaborating quite closely with
them, thanks to the amazing efforts of Ronald Tse and have plans to work
with them further to enable greater adoption.

Hope this helps, please feel free to ask for further clarifications.

Best,
Ujjwal

-- 
Ujjwal "Ryzokuken" Sharma (he/him)

Compilers Hacker, Node.js Core Collaborator and Speaker