[tz] Introduction and apology for slamming you "with that TZ is a legal thing" commentary out of the blue.

Todd Glassey tglassey at certichron.com
Thu Oct 20 16:41:00 UTC 2011


So I need to properly introduce myself to explain why I said what I said 
on the list. I am a professional timekeeper meaning that I and my team 
operate clocks which end users rely on.  My team runs 10 of the NIST 
public access timebase systems and is expanding the availability of UTC 
to include PTP and other evidence-control tools as add-ons for traceable 
time.

That said - the TZ data is used in virtually all commercial and 
electronic document/instrument processing systems operational today. The 
problem is that the Time Zone data itself (while created through a 
standards process) has largely been managed as  an ad-hoc offering and 
this was accepted everywhere because the party and hosting entity for 
this were the US Government NIH and Dr. Olson.

But with the good Dr.s retirement there is a need to formalize this 
process and expand its controls so that the data remains both properly 
managed and available to all. So the question is how to do that, and I 
have pushed back that this effort is much more important and needs to be 
managed outside an IETF process because of the lack of control the IETF 
has designed into its framework.

This specific project is one which needs a level of oversight that the 
IETF process doesnt put in place for changes and content updates to the DB.

What needs to happen I believe is that this effort should define a 
process wherein any legal authority can request a IANA update to the 
data base and have that processed in a fixed timeframe outside of any 
continued IETF review. This is not an excuse to make a new IETF WG to 
control the world... its about letting the world operate in a manner 
which doesnt impose the IETF's judgement or political opinions on anyone 
either.

That said my proposal is to morph the current I-D by adding an inline 
update process to the CONTENT RECORDS of the DB and a NEW RECORD 
Addition Policy and Practice through IANA and not the IETF.

In closing - My apologies for antagonizing anyone, and I would point out 
that since we do about 300M timesettings per day - all tied to TZ's I 
would retort I may be one of the only people here who is NOT a troll...

Todd

-- 
Todd S. Glassey - CISM CIFI
CTO Certichron Inc

This message contains information which may be confidential and/or privileged. Unless you are the intended recipient (or authorized to receive for the intended recipient), you may not read, use, copy or disclose to anyone the message or any information contained in the message. If you have received the message in error, please advise the sender by reply e-mail and delete the message and any attachment(s) thereto without retaining any copies.

Further we have a formal OPT OUT Policy posted on our website pertaining to the use of any Email Addresses gleaned or taken from any source, web, mailing lists, previous customer lists etc. In all instances we choose to formally OPT OUT and this notice constitutes formal disclosure that you may not collect, buy or sell or provide access to this email address or any pertaining to our DNS MX Record Publication License posted on the web at http://www-wp.certichron.com/?page_id=3947.




More information about the tz mailing list