-={ 2021-04-19 23:45:56.368925895+00:00 }=-

Hey August!

 AA> This is my view as I take a glance above the laptop.

That is a nice view, other than the window that is.  ;-)

 AA> Not sure. It seems that you have some fine priority ideas.

I think so except a tad too radical for fidonet despite the fact that a simple update to the packed MSG header's datetime field only brings us up to date to 1989 standards.  However it isn't obsolete ... yet.  (YYYY-MM-DD hh:mm:ss(+|-)utc_offset).  If the (+|-)utc_offset is dropped then the remainder fits in EXACTLY in the field specified for the DateTime field so it is attractive given that.  However that is still too radical for the abandonware crowd who are being used as an excuse even though it is debatable whether or not these particular nodelisted sysops actually exist.  Anytime I have asked for evidence I've been ignored ... or worse ... and then ignored.  I don't actually mind since I've managed to survive it all as well as come up with suitable fixes to make it all work at my end of things.

My personal favorite is the hex output of unixtime seconds-nanoseconds but moreso as a unique serialno such as used in MSGID/REPLY kludges.  However I personally don't want to screw with that particular document especially considering how embedded it has become in fidonet MSGing.  Also given that I have a fix that is good up to 2106 takes the heat off of any need to alter or replace fts-0009.001.  Some clarification on what constitutes an origAddr would be helpful.  As far as your suggestion for a 8 character serial number I believe it is already covered and is to it's favour although there are still those who will argue that point.  Isn't that always the case?

Life is good,
Maurice

... Ea¨e wis man m‘g witan spell and eac secgan.
    Easily may a wise man understand a story, and tell it too.
--- GNU bash, version 5.1.4(1)-release (x86_64-motorshed-linux-gnu)