>> Due diligence in system engineering should not be controversial. > > ... and it should come with a cost estimate.
So let's see. (Putting aside the actual system requirements for the moment.) The comparative costs and risks of UTC without leap seconds are unknown relative to the status quo (UTC with leap seconds). The system engineering and project management methods to generate such a cost estimate and risk analysis are well known and are as highly respected as best practices can be. But it is deemed unacceptable to apply these in the least regard because there is naturally some cost to preparing such. (One might, however, point out that these best practices likely minimize that cost.) And to top the hubris off with a cherry, it's the folks supporting the status quo who are expected to provide a cost estimate for the process of preparing the system engineering report. One might expect a guy who had been the victim of a DoS attack due to bad engineering would be a little less dismissive and devil-may-care about due diligence. Risks? What risks? Rob --
<<inline: ostrich-head-in-sand-sign.gif>>
_______________________________________________ LEAPSECS mailing list [email protected] http://six.pairlist.net/mailman/listinfo/leapsecs
