Re: time offset, adjustments, and related discussions
Re: time offset, adjustments, and related discussions
"Bill Blanton" <bblanton@REMOVEmagicnet.net> wrote in message
news:uUjBU9pIJHA.788@TK2MSFTNGP06.phx.gbl...
|
| "MEB" <meb@not
here@hotmail.com> wrote in message
news:eTPJ9spIJHA.4568@TK2MSFTNGP06.phx.gbl...
| >
| > "Bill Blanton" <bblanton@REMOVEmagicnet.net> wrote in message
| > news:uQoaEdpIJHA.2208@TK2MSFTNGP02.phx.gbl...
| > |
| > | "MEB" <meb@not
here@hotmail.com> wrote in message
| > news:uSMgkeaIJHA.4836@TK2MSFTNGP03.phx.gbl...
| > | >
| > | > "Bill Blanton" <bblanton@REMOVEmagicnet.net> wrote in message
| > | > news:e6$%23lXXIJHA.1308@TK2MSFTNGP02.phx.gbl...
| > | > | "MEB" <meb@not
here@hotmail.com> wrote in message
| > | > news:ePHqXtMIJHA.4408@TK2MSFTNGP06.phx.gbl...
| > | > | > "Bill Blanton" <bblanton@REMOVEmagicnet.net> wrote in message
| > | > |
| > | > | > | > | GMT/UTC is still a constant. The time at longitude 0.
| > | > | > | > | The (manipulative) variable is the "time zone" factor of
the
| > | > equation.
| > | > | > | > |
| > | > | > | > | If you are calculating your geographic location, you need
to
| > | > adjust
| > | > | > | > | accordingly.
| > | > | > | >
| > | > | > | > Then what you suggest is that mariners and aviators adjust
their
| > | > | > | > chronometer to DST [should that be required] adding that
| > calculation
| > | > to the
| > | > | > | > equation to determine position?
| > | > | > |
| > | > |
| > | > | > |
| > | > | > | I'm not suggesting they do or don't adjust to DST. But yeah,
| > whatever
| > | > your
| > | > | > | clock's offset to the constant, you'd have to calculate that
in.
| > There
| > | > is only
| > | > | > | the one "point in time", no matter what the clock reads.
| > | > | > |
| > | > | >
| > | > | > So we come full circle, to how easy, yet sloppy, this time
| > adjustment
| > | > | > method is. The ONLY way to allow this {for this to work} using
this
| > | > method,
| > | > | > is to modify EVERY computer and network around the world each
and
| > every
| > | > time
| > | > | > some modification is made.
| > | > |
| > | > | I don't see it as sloppy really. You have the agreed upon
"constant"
| > GMT,
| > | > and
| > | > | then you modify that according to your "zone". Add or subtract the
| > offset
| > | > | from the "clock" to determine "universal time".
| > | > |
| > | > | What's the alternative? We could all use the GMT/UTC. (I wouldn't
have
| > to
| > | > go
| > | > | to work until noon, though the sun would be rising).
| > | > |
| > | > |
| > | > | > A failure ANYWHERE throws the entire system off.
| > | > |
| > | > | It does in a way... though it wasn't too catastrophic in this
case.
| > | > |
| > | > |
| > | > | > This also would seem to allow some vulnerabilities to occur.
Server
| > | > | > identifiers, DNS, registrar services, message headers, IP packet
| > | > formation,
| > | > | > and other, could, potentially, be affected due to actual
physical
| > | > location
| > | > | > variances.
| > | > |
| > | > | That's soemthing to think about...however;
| > | > |
| > | > | The variances (or offsets of) the "physical location" don't matter
as
| > long
| > | > as
| > | > | you resolve correctly to the constant..
| > | > |
| > | > | Where you are doesn't matter as long as your time offset to GMT is
| > | > correct. I
| > | > | could set my clock forward 9 more minutes EST/DST, and then fly to
the
| > | > Pacific
| > | > | coast. As long as I adjust my offset accordingly, say GMT -03:51,
and
| > my
| > | > clock
| > | > | is still at EST/DST+00:09, then it will resolve to GMT correctly.
And
| > if
| > | > I'm
| > | > | navigating I need to take that offset into consideration to get
the
| > time
| > | > at
| > | > | longitude zero.
| > | > |
| > | >
| > | > Yes that would work for you, but you ONLY. It would NOT work for the
| > | > airline, terminal, flight controllers, or others around you either
where
| > you
| > | > took off or where you landed.. Nor would it work personally if you
| > needed to
| > | > be somewhere at a specific time, UNLESS you constantly adjusted real
| > time to
| > | > your private time in addition to any real time offsets [having not
| > further
| > | > changed your personal watch/clock].
| > |
| > | I don't want to belabor this.. if you know the time at point zero on a
| > sphere,
| > | and the angle of the sun, you can calculate your latitude.
| > |
| > | I don't know enough about sextants, chronometers, and the positions of
the
| > | stars to explain it any better.
| > |
| > | As far as the aviation industry, I'm pretty sure they use GPS.
| > |
| > |
| > |
| > |
| > | > Need we re-review the [projected and at times real] panic that
ensued
| > | > during the millenium change over and the BIOS, OS, and related
issues
| > [such
| > | > as 1999 - 999 - 99]. I think not, as they where reviewed and
documented
| > on
| > | > hundreds of sites, government bulletins, software updates, BIOS and
| > other
| > | > related... what COULD have happened is also well documented,
moreover,
| > these
| > | > DID cause numerous issues, from electric supply failures, to system
and
| > | > network crashes, Internet interruption, to numerous others. Of
course we
| > | > made it through those times... but they DO display both the
| > vulnerabilities
| > | > AND other related to any such issues.
| > | >
| > | > Think that might help explain why XP and VISTA use GMT/UTC? And why
I
| > think
| > | > this is zone shift a sloppy way to provide the changes?
| > |
| > | So again, what do you propose as an alternative?
| > |
| >
| > Ah how about something more appropriate, like a TIME change.. you know,
| > uhoh, here's the date, here's the change, one hour back on the clock....
| > UHOH, here's the date, here's the change, one hour up on the clock.
Isn't
| > that what you do with your watch and clocks?
|
| Why should it be the "same time" on the East side of the zone as the West
| side of the zone? Maybe we should all be on sidereal time?
|
http://tycho.usno.navy.mil/sidereal.html
|
|
| > But wait you say, how would I synchronize with the Atomic clocks I
| > contact,,, they work only from actual time adjusted to offset.... hmmm,
| > how about, uhoh, here's the date, here's the change, all automatic
[network]
| > modifications are so adjusted.. makes the need adjusted properly to the
| > clock control program or other control... keeps you GPS located and
makes
| > the network fully synced.... wacha tink, do da servers uz DST zone shift
er
| > GMT/UTC offset wif clock change
|
| I really have no idea what you're trying to say...
|
Okay then, let's get down to it::::
ALL of the issues have already been set forth and resolved when dealing
with the Internet, time, connected networks, protocol formation and
requirements, and pretty much everything else.. of course always open to
modification and updates, but the basics must be followed
Start here:
http://www.ietf.org/rfc/rfc2616.txt - Hypertext Transfer Protocol -- HTTP/1.1
popover here generally:
http://www.w3.org/TR/NOTE-datetime
add this in:
http://www.ietf.org/rfc/rfc2396.txt - Uniform Resource Identifiers (URI):
Generic Syntax
notice this:
http://www.w3.org/XML/Schema -
consider this:
http://www.w3.org/TR/1999/REC-xml-names-19990114/Overview.html - Namespaces
in XML, and modifications
you might cruise around over here:
http://www.cni.org/ - the Coalition for Networked Information
Of course there are dozens more, but this should provide a base to work
from....
Oh, don't forget this since nothing happens out here without it:
http://www.sans.org/info/3871 - TCP/IP handbook in PDF
http://www.cisco.com/en/US/docs/internetworking/technology/handbook/Internet-Protocols.html -
Cisco - Internet Protocols
And if you feel up to it, compare IPv6 to IPv4....
--
MEB
http://peoplescounsel.org
a Peoples' counsel
_ _
~~
\