OpenBCM V1.13 (Linux)

Packet Radio Mailbox

DB0FHN

[JN59NK Nuernberg]

 Login: GUEST





  
ZL3AI  > APRDIG   04.02.03 10:06l 247 Lines 9444 Bytes #999 (0) @ WW
BID : 831-ZL3AI
Read: GUEST
Subj: TAPR Digest, Jan 30, 5/8
Path: DB0FHN<DB0RGB<DB0FSG<DB0ZKA<DB0GPP<DB0LX<DB0RBS<DB0SEL<DB0ZDF<DB0GE<
      F6KFT<LX0PAC<LX0HST<HA3PG<CT2GWY<VK3TE<VK4TUB<ZL2BAU<ZL3VML
Sent: 030203/0915Z @:ZL3VML.#80.NZL.OC #:58724 [Chch-NZ] FBB7.00i $:831-ZL3AI
From: ZL3AI@ZL3VML.#80.NZL.OC
To  : APRDIG@WW

Subject: Re: Words of Warning
From: Miller Scott Contr 30SCS/FTI <Scott.Miller@vandenberg.af.mil>
Date: Thu, 30 Jan 2003 20:52:11 -0000
X-Message-Number: 31

And fun stuff like routing is what I'm trying to lay the groundwork for
here.  The current spec is so hairy as it is that big changes are bound to
cause problems.  Not that people shouldn't keep working on it... there's
still much that can be done with it and learned from it.

Scott / N1VG

----------------------------------------------------------------------

Subject: Re: Words of Warning
From: Miller Scott Contr 30SCS/FTI <Scott.Miller@vandenberg.af.mil>
Date: Thu, 30 Jan 2003 20:55:43 -0000
X-Message-Number: 32

Non-interference is indeed the Prime Directive.  =]  Rest assured that I
intend to take all reasonable steps to prevent any experimentation from
adversely affecting the existing network.

----------------------------------------------------------------------

Subject: Re: Input needed
From: "Pat Karp" <pkarp@conwaycorp.net>
Date: Thu, 30 Jan 2003 15:11:34 -0600
X-Message-Number: 33

>Some questions for the list regarding a new spec:
>
>Should it continue to use UNPROTO or should it be a true layer 3 protocol?

I think your going about it the right way.  A standard for conversion will
be needed but if the system takes off then things will be upgraded at some
point.  The conversion will aid in backwards compatibility.

>Should station speeds be in km/hr or m/sec?
>(Don't even think about MPH - the spec will be strictly SI units.)

Here I would say km/hr.  More then likly the speeds will be fast enought.

>What about wind speeds?

The same here as for Station speed

>What precision should temperatures support?  (i.e. 1/10 degree, 1/100
>degree)

Go 1/100 Right now I don't know of a need for it being that accurate.  But
at some point for some reason it might be needed.

>Are maidenhead reports still used/needed?

Don't know about this one at all.  LOL

Pat

----------------------------------------------------------------------

Subject: ISS operational??
From: "Bob D." <n2iph@comcast.net>
Date: Thu, 30 Jan 2003 16:55:30 -0500
X-Message-Number: 34

Anyone know if the ISS packet station is operational?
Looking at the ariss.net web page shows only one person getting in over the
past 29 days.

Is the digi call still RS0ISS, or NOCALL ?

I've looked at the various web pages but found nothing recent about
operational status or the current call.

Hoping to make the next pass coming up in 30 minutes.

----------------------------------------------------------------------

Subject: Message queuing and acks?
From: Miller Scott Contr 30SCS/FTI <Scott.Miller@vandenberg.af.mil>
Date: Thu, 30 Jan 2003 22:16:50 -0000
X-Message-Number: 35

While reading over the spec on station-to-station messaging, a thought
occured to me.  Would it be possible to configure certain stations (maybe
WIDEs and IGATEs) to queue messages sent by end users, and provide an
'in-transit' ack?  A queue ack would indicate to the sending station that
the message has been accepted by a reliable station (and hopefully commited
to non-volatile memory) for delivery, and the sending station could quit
retransmitting the message with the assurance that it'll be passed on and
acknowledged if required.

Is there anything like this currently implemented?

Scott / N1VG

----------------------------------------------------------------------

Subject: RE: New spec - working notes
From:     Jeff King <jeff@aerodata.net>
Date: Thu, 30 Jan 2003 17:52:49 -0500
X-Message-Number: 36

Bob Bruninga wrote regarding Cpt Scott's protocol thoughts:

>I guess I dont know what problem it is that you are trying to solve with
>a whole new "APRS" protocol?

He sees a need and is filling it. Doesn't mean you need to see it or even
need to agree with it. All that matters is he sees a personal need. The
fact that he is sharing it with us, IMHO, is gravy.

>The big problem with APRS is total overload on the national user channel,
>and I dont see that any of that is a significant "protocol" problem.

What?!? Lets not continue this group psychosis. There are *serious* flaws
in the level one and level two implementations of APRS, and these are a
fundamental part of the protocol.  The inventors of AX.25 never ever
intended it to be used on a mega lan with flood digipeating with UI frames.

More to the point, lets compare two *micro-controller friendly* protocols
that give the positional accuracy in the meter or less range. On one hand
we have RAW NEMA strings, something on the order of 85 bytes or greater, on
the other hand the base 2 protocol Scott is suggesting around 18 bytes. At
level two of the protocol, that is about a 75% decrease in packet size.
Certainly not the magic bullet but if implemented, a step in the right
direction.

But you are right in that if no-one implements it is not worth the
electrons it takes to talk about it, but I for one like to see this kind of
forward thinking on the SIG.

It is exactly why I got my ham license and we should encourage innovation
and open thought every chance we get.

73

Jeff

----------------------------------------------------------------------

Subject: Re: Words of Warning
From: "Pat Karp" <pkarp@conwaycorp.net>
Date: Thu, 30 Jan 2003 17:04:37 -0600
X-Message-Number: 37

I agree Alex!  There are things that need to be taken into account and I
think Scott is attempting to do so.  At this point other then folk offering
opinions and criticism.   The only one actively working on this project is
Scott.   No harm is being done!  Why not support his efforts by answering
his questions and let him go at it.  When the time for test come I would be
more then happy to actively help out.   This is one of the aspects that
Amateur radio is about.  It seems that some maybe threatened by the creation
of a new system.  Some have an invested interest in APRS.  That is no reason
to discourage someone from creating a new system.  With any luck Amateur
radio benefited from it.

I'm thinking that discussing this with the aprsspec group may not be a good
idea.  The reason is simple!  There is too many people in that group that
have an invested interest ($$) that will be opposed of any thing that will
threaten the way APRS is today.   This group is OK because there are enough
here that do not have such an interest.   The APRS backbone group would be
interested in the progress on this system.  However if there is too much
needed to implement this system as a Backbone then another backbone system
will be pursued.   But in the mean time I fully support his efforts.

Pat

----------------------------------------------------------------------

Subject: Re: Input needed
<LYR30523-118055-2003.01.30-12.02.12--kb2scs#optonline.net@lists.tapr.org>
From: kb2scs@optonline.net
Date: Thu, 30 Jan 2003 18:14:24 -0500
X-Message-Number: 38

Hi Scott
I can see that you have put a lot of work into your new spec.

I have a question. I understand that in the beginning this spec will be
used for a backbone system. In other words not on 144.390

I have briefly read your emails so I may have missed something.

This new binary format is it to be placed in the data portion of an 
AX25 packet?

The reason I ask is because of the existing hard ware (TNCs)
A TNC even in KISS mode expects to see an AX25 header with a flag byte at 
the beginning and a FCS and then another flag byte at the end.

Now if your answer is in order to use your protocol a user would have to get 
new hardware then I see this as a major problem.

----------------------------------------------------------------------

Subject: Re: Words of Warning
From: Miller Scott Contr 30SCS/FTI <Scott.Miller@vandenberg.af.mil>
Date: Thu, 30 Jan 2003 23:18:20 -0000
X-Message-Number: 39

Thanks, Pat.  Yeah, I think that the aprsspec group as a whole may not be
too keen on the whole idea.  Tough.  I'm looking for suggestions,
contributions, and constructive criticism, not approval.

James Jefferson has generously offered his time to help develop a prototype
message gateway.  With luck, we'll have some code to play with inside a
week.  Keep the suggestions coming.

Scott / N1VG

----------------------------------------------------------------------

Subject: RE: New spec - working notes
From:     Jeff King <jeff@aerodata.net>
Date: Thu, 30 Jan 2003 18:20:35 -0500
X-Message-Number: 40

>All the code to convert a NMEA string into the Mic-E, and transmit in
>AX-25 fits in a 1k PPIC controller, presently costing a couple bucks. Even
>if you could make it easier to do the conversion (which I doubt), where is
>the need? Why should a tracker use a new format, when the old one works
>fine?

If your happy with 60 foot granularity and trackers in the atlantic and
lost in china, then by all means, stay with MIC-E.

GPS, with SA off and now WAAS easily has the capability to define locations
down to the lane a vehicle is in. While this may not be an issue for casual
users, applications like APRSWORLD have shown that the positional data we
hams collect can be mined for uses we never even thought of. 

And if you don't understand the above, then I'll put it another way:
"What good is a baby"?

Keep the good ideas coming Scott and don't let the naysayers discourage you.
I am following your project with great interest.

-Jeff

----------------------------------------------------------------------



Read previous mail | Read next mail


 16.11.2026 07:02:53lGo back Go up