[Date
Prev][Date
Next] [Chronological]
[Thread]
[Top]
[aprsspec] non-offical Draft paper outline
- To: "APRS Spec Discussion List" <aprsspec@lists.tapr.org>
- Subject: [aprsspec] non-offical Draft paper
outline
- From: Jeff King <jeff@aerodata.net>
- Date: Wed, 07 Feb 2001 18:49:47 -0500
- List-Owner: <mailto:owner-aprsspec@lists.tapr.org>
- List-Software: Lyris Server version 3.0
- List-Subscribe: <mailto:subscribe-aprsspec@lists.tapr.org>
- List-Unsubscribe: <mailto:leave-aprsspec-11589P@lists.tapr.org>
- Organization: Aero Data Systems, Inc.
- References:
<LYR22299-133733-2001.02.07-17.57.56--jeff#aerodata.net@lists.tapr.org>
I just wrote down some things I'd like to see in a draft
outline. I am sure I missed some things. Please add what is
missing.
Thanks
Jeff
-----
We really have three tasks here.
1. Document what exists so someone can develop applications for it.
2. Document need ommisions and fixes (to both server and clients) (*)
3. Document extensions (**)
Don't forget we do need to get on paper what exists as well
as what needs to be fixed and what needs to be extended. Here is my
view on it:
OVERVIEW of APRSERVE network (use Steve's papers)
BASIC STUFF
Connecting to the server (basic port numbers)
Decoding posits (reference to APRS protocol document?)
Client verfication ( source code snippet)
Enter posits
MESSAGING
Overview (use Steve's paper)
Sending messages ( APRS protocol document?)
Recieving messages
Internal server communication (port numbers ect)
Message passing
**Extensions to messaging
RF message gateway selection
Least hop routing
Least power routing
FILTERING
Message Dup's (source code snippet or structure description)
*Non-complient packet filtering
**Geo-Filtering
By feed
By client (might be OK on smaller FAST servers)
CLIENTS
Connection to the server, rules
Messaging rules
I see you, you see me, (flood broadcast)
**Who are my RF neighbors
**What are their RF footprints
**List of stations nearby (lat/lon)
**Least power routing
**Server selection of gateway message station
Client gateway rules
*Only gateway APRS complient packets
*No protocol conversions done on gatewayed packets
*No math conversions done on any gatewayed frames
Future extensions/fixes (framework for developers, not set in stone)
Go over justifications for extensions and food for thought.
Anyways, that is my laymans view of it.
-Jeff
---
You are currently subscribed to aprsspec as: lyris.aprsspec@tapr.org
To unsubscribe send a blank email to leave-aprsspec-11589P@lists.tapr.org
Questions regarding the SIG go to the SIG administrator: wa1lou@tapr.org