Re: [calsify] New Timestamp Draft

Ujjwal Sharma <ryzokuken@igalia.com> Wed, 13 January 2021 18:25 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 40C493A12DA for <calsify@ietfa.amsl.com>; Wed, 13 Jan 2021 10:25:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.361
X-Spam-Level:
X-Spam-Status: No, score=-2.361 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, NICE_REPLY_A=-0.262, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham 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 H767U2WuSUXt for <calsify@ietfa.amsl.com>; Wed, 13 Jan 2021 10:25:19 -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 A725F3A12E5 for <calsify@ietf.org>; Wed, 13 Jan 2021 10:25:12 -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:References:To:From:Subject; bh=kTbMDGsI1jDPB4bFnr8Qd11B7ltCMvQNv7nus95E8Sw=; b=VntnFogxsAIYDaK6khZKFpy15gx8mvh8/lDzliaBmd/iU/mfybIUOZ1mAGeYpl8uZVvHryL1TXrQf+RekWvbdkugeOAfr8jvpx9mqJJ44PAy3IKmdy9B85gn8JWDTucIhCysiZnFKamnKj++boIaox4TGtiXFR9Al/9cBYR6Gi0xFn9CvwGER52kCxqRcO6jzo0BacqbgOLo1fPDOQmo1fPbdN6jmrVqcTLv/zR11fu8m/pu85HGYI+fHQMm4MxbnEuWTkXFpaLbjLWbO8knBUBuGX4+QQkmSyRfSx9Nj6ddZ+2oDwCVsPc9uNqW+xIzg1AHTX2pUNRHwrBrme3AyA==;
Received: from [45.122.44.244] (helo=[192.168.0.110]) by fanzine.igalia.com with esmtpsa (Cipher TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim) id 1kzkpS-0005kQ-9m for <calsify@ietf.org>; Wed, 13 Jan 2021 19:25:10 +0100
From: Ujjwal Sharma <ryzokuken@igalia.com>
To: "calsify@ietf.org" <calsify@ietf.org>
References: <36725ce1-307a-945e-63bf-af98f4b85338@igalia.com>
Organization: Igalia S.L.
Message-ID: <a78e1a49-de7b-d2ed-c112-0bbd0cb62399@igalia.com>
Date: Wed, 13 Jan 2021 23:54:39 +0530
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.6.0
MIME-Version: 1.0
In-Reply-To: <36725ce1-307a-945e-63bf-af98f4b85338@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/ozRSwkz5Y-qppdYS_0VNc82iIBM>
Subject: Re: [calsify] 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: Wed, 13 Jan 2021 18:25:28 -0000

One question: given things move forward smoothly, how do I proceed?
Should I apply for this document to be adopted by the calext WG? I
suppose the fastest way to proceed is to present it at the next IETF
meeting?



Ujjwal

On 12/01/2021 4.03 am, Ujjwal Sharma wrote:
> Hi Calsify folks!
> 
> I am sorry for the long delay, I got a little sidetracked working on
> other things, but I'm happy to inform you all that I have something that
> resembles a first draft for the updated timestamps RFC.
> 
> Here's where you can find it:
> 
> Datatracker:
> https://datatracker.ietf.org/doc/draft-ryzokuken-datetime-extended/
> GitHub: https://github.com/ryzokuken/draft-ryzokuken-datetime-extended
> 
> I would request you all to take a look at it when you can and let me
> know what you think. You can file a GitHub issue or email me directly.
> 
> There's a few open discussions regarding the exact format and how the
> interaction with bodies like the Unicode consortium work, so please feel
> free to send me your thoughts regarding that as well.
> 
> Also, some references/bibliography is not perfectly functional yet
> because I am still relatively new to authoring RFCs using Metanorma but
> I'm actively looking into it.
> 
> Thanks and looking forward to hear from you,
> Ujjwal
> 

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

Compilers Hacker, Node.js Core Collaborator and Speaker