| |
ZL3AI > APRS 29.10.00 15:52l 219 Lines 8127 Bytes #999 (0) @ WW
BID : 34159_ZL3AI
Read: GUEST
Subj: TAPR Digest, Oct 25, 4/6
Path: DB0MRW<OK0PKL<OK0PPR<OK0PRG<OK0POK<9A0YRB<HI8GN<KP4IG<WB0TAX<WB7AWL<
WA7V<KB7FRV<VK4WIT<ZS6RO<ZL3VML
Sent: 001027/1025Z @:ZL3VML.#80.NZL.OC #:45149 [Chch-NZ] FBB7.00g25 $:34159_ZL3
From: ZL3AI@ZL3VML.#80.NZL.OC
To : APRS@WW
unusual for IGATES to have times that are off by minutes, hours, or even days.
If a time standard were adopted it should include a provision for an APRS time
message. This message could be originated by servers, and gated to RF if
desired. If APRS applications were modified to accept this message, it would
permit the syncrhonization of all stations to the same time base. The
applications would have the responsibility of adjusting the system date time if
permitted by user settings.
Perhaps this thread should be on the APRSspec list?
Bill KC9XG
On Wednesday, October 25, 2000 1:16 PM, Sadowski, Allan
[SMTP:allan.sadowski@ncshp.org] wrote:
Snip
> I'd like to throw an "issue" into the debate ring for consideration....
>
> Everyone standardize on GMT/Zulu/CUT/moniker of choice that we all know is
> the same but called different things... the name isn't what's important...
> but rather that we are all on the same clock.... and that applications that
> recieve local data that can't (or won't) be changed by the originator...
> (NWS weather I think I've heard is one example) all be changed to the same
> clock...
>
> ALOHA
> AH6LS
..
----------------------------------------------------------------------
Subject: Re: Next Layer of Standards
From: Earl Needham <kd5xb@amsat.org>
Date: Wed, 25 Oct 2000 12:48:08 -0600
X-Message-Number: 20
At 2:15 PM -0400 10/25/00, Sadowski, Allan wrote:
><snip>
>Everyone standardize on GMT/Zulu/CUT/moniker of choice that we all know is
>the same but called different things... the name isn't what's important...
>but rather that we are all on the same clock.... and that applications that
>recieve local data that can't (or won't) be changed by the originator...
>(NWS weather I think I've heard is one example) all be changed to the same
>clock...
You know what?
I used to transmit weather warnings, until people started
chewing me out for doing so in MOUNTAIN time instead of ZULU time.
They all tried to tell me that NWS puts out weather warnings, etc.,
in Z time, but the funny thing is that my local NWS transmitter uses
local time, the email I receive is in local time, etc. In fact, I
have NEVER received NWS information in Z time.
At any rate, I no longer transmit weather watches and
warnings. Chewed out once too often, I guess.
7 3
Earl
Earl Needham, KD5XB mailto:KD5XB@AMSAT.ORG
Clovis, New Mexico DM84jk N34d 25.446m W103d 12.700m (or so)
Pet peeve: breath is a noun, breathe is a verb (When you take a
breath, you breathe...)
----------------------------------------------------------------------
Subject: Re: aprssig digest: October 24, 2000
From: "Tom Clarke" <fclarke@erols.com>
Date: Wed, 25 Oct 2000 15:10:37 -0400
X-Message-Number: 21
Hi Bob, the last trip I made up to Maine with APRS was in June and most of
the activity is in Bangor and Augusta. There is also a gate in Belgrade.
Never had much luck in the Portland area. The folks up in Augusta are quite
keen on APRS and I could always count on activity. Pretty quiet from Boston
Beltway north on 95 until nearing Augusta.
Lotsa nice mountains for digis though!
73 de Tom/W4OKW
----------------------------------------------------------------------
Subject: RE: Next Layer of Standards
From: Timothy J Salo <tjs@tc.umn.edu>
Date: Wed, 25 Oct 2000 14:33:05 -0500
X-Message-Number: 22
> From: Bill Diaz <billdiaz@megsinet.net>
> Subject: [aprssig] RE: Next Layer of Standards
> Date: Wed, 25 Oct 2000 13:48:19 -0500
>
> If a standard for time is adopted, we should also provide a universal
> method to allow users to set their clocks to the correct time. Presently,
> it is not unusual for IGATES to have times that are off by minutes, hours,
> or even days.
Because IGATES are, by definition, attached to the Internet, a number of
straight-forward technical solutions are available.
IGATES could, for example, synchronize the system clock of the machine
on which they run. Technologies include Network Time Protocol (NTP)
(RFC 1305), a complex protocol that provides sub-millisecond time
synchronization and Time Protocol (RFC 868) a very simple protocol that
probably provides time synchronization on the order of a second or less.
Alternatively, IGATES could simply maintain their own clock, rather than
tinker with the host machine's system clock.
IGATES could use any convenient Internet source for time synchronization.
Alternatively, the APRS servers could all offer time synchronization
services to the IGATES (since the IGATES have to communicate with the
APRS servers anyway, it seems like a convenient place from which to receive
time synchronization).
Of course, IGATES could also use GPS receivers for time synchronization.
> If a time standard were adopted it should include a provision for an APRS
> time message. This message could be originated by servers, and gated to RF
> if desired. If APRS applications were modified to accept this message, it
> would permit the synchronization of all stations to the same time base. The
> applications would have the responsibility of adjusting the system date time
> if permitted by user settings.
This sounds like a really useful idea. However, propagation delays are a
bit harder to determine over the (multi-hop) APRS RF (or RF/Internet)
paths. On the other hand, this still seems worth thinking about.
It would also be nice if APRS clients used these on-the-air time messages
to synchronize their local clocks.
-tjs
----------------------------------------------------------------------
Subject: RE: Next Layer of Standards
From: Alex <kg4ecv@amsat.org>
Date: Wed, 25 Oct 2000 16:02:55 -0400
X-Message-Number: 23
I don't know if the hardware is readily available or not, but this would
be a nice application for a digi with a DCF77 or WWV receiver (or
perhaps a GPS receiver), rather than an Igate (which often first has to
go through a digi to be heard). Especially since propagation times of
packets are very hard to predict within acceptable margins of error, a
client application should probably only accept packets heard from the
Time Server within one or two hops. But that of course depends on the
application. For most applications it would already be nice if we would
know that we're talking about the _same_ time (utc, local...), but I
think that that already is covered by the current standard if I'm not
mistaken.
73s,
Alex
Bill Diaz wrote:
>
> llan,
> If a standard for time is adopted, we should also provide a universal method
> to allow users to set their clocks to the correct time. Presently, it is not
> unusual for IGATES to have times that are off by minutes, hours, or even days.
<snip>
> Perhaps this thread should be on the APRSspec list?
>
> Bill KC9XG
----------------------------------------------------------------------
Subject: RE: Next Layer of Standards
From: Bill Diaz <billdiaz@megsinet.net>
Date: Wed, 25 Oct 2000 15:18:57 -0500
X-Message-Number: 24
Tim,
On Wednesday, October 25, 2000 2:33 PM, Timothy J Salo [SMTP:tjs@tc.umn.edu]
wrote:
> > From: Bill Diaz <billdiaz@megsinet.net>
> > Subject: [aprssig] RE: Next Layer of Standards
> > Date: Wed, 25 Oct 2000 13:48:19 -0500
> >
snip
> Because IGATES are, by definition, attached to the Internet, a number of
> straight-forward technical solutions are available.
>
> IGATES could, for example, synchronize the system clock of the machine
> on which they run. Technologies include Network Time Protocol (NTP)
> (RFC 1305), a complex protocol that provides sub-millisecond time
> synchronization and Time Protocol (RFC 868) a very simple protocol that
> probably provides time synchronization on the order of a second or less.
>
snip
>
> IGATES could use any convenient Internet source for time synchronization.
This is not being done by many IGATES now. Requires running a seperate
application periodically to set the clock.
> Alternatively, the APRS servers could all offer time synchronization
> services to the IGATES (since the IGATES have to communicate with the
Read previous mail | Read next mail
| |