| |
ZL3AI > APRDIG 11.09.03 11:00l 118 Lines 4203 Bytes #999 (0) @ WW
BID : 1892-ZL3AI
Read: GUEST
Subj: TAPR Digest, Sep 08, 7/7
Path: DB0FHN<DB0RGB<DB0MRW<OK0PKL<OK0PPL<DB0RES<ON0AR<VK6HGR<VK3KAY<ZL2BAU<
ZL3VML
Sent: 030910/1408Z @:ZL3VML.#80.NZL.OC #:8093 [Chch-NZ] FBB7.00i $:1892-ZL3AI
From: ZL3AI@ZL3VML.#80.NZL.OC
To : APRDIG@WW
Subject: Re: Homeport
From: "Andrew Rich" <vk4tec@hotmail.com>
Date: Tue, 09 Sep 2003 13:02:00 +1000
X-Message-Number: 48
Hello ! People remeber us ? The people OUTSIDE of the USA ?
>From: Steve Jones <s.jones@rogers.com>
>Reply-To: Steve Jones <s.jones@rogers.com>
>To: "TAPR APRS Special Interest Group" <aprssig@lists.tapr.org>
>Subject: [aprssig] Re: Homeport
>Date: Mon, 08 Sep 2003 20:36:22 -0400
>
>on 9/8/03 8:08 PM, Randy Allen at ka0azs@earthlink.net wrote:
>
>>Would it be significantly shorter in terms of packet length to define
>>Homeport by Grid Square rather that Lat/Long, and also be more universal
>>than Airport and FIPS codes?
>
>Also keep in mind APRS is used worldwide. FIPS means nothing to anybody
>outside the US.
>
>Airport codes and CLLI's are used worldwide and could be good choices.
>
>Whatever is decided, please make sure it's universal and not just US.
>
>--
>Steve <s.jones@rogers.com>
----------------------------------------------------------------------
Subject: RE: Adding location "SMARTS" to APRS (HLR VLR)
From: "Scott Miller" <scott@home.miller.org>
Date: Mon, 8 Sep 2003 20:22:00 -0700
X-Message-Number: 49
I think this is a good idea - only don't make it a SQL-based database like
findu or aprsworld. Make it dynamic dns (or maybe LDAP) and treat it like a
network naming service. DNS queries are lightweight, fast, cached, and
easily distributed. Plenty of bulletproof software is available for many
platforms. If you've never looked at the guts of DNS (see RFC 1034, 'Domain
Names - Concepts and Facilities') it's capable of doing a lot more than
associating a name to an IP address.
Plus, it's already got a geographic record format (see RFC 1876, DNS LOC),
so you can use that to store the last position and such. A TXT record could
store the last status text from the station, and other records could be used
to indicate route.
When sending a message to N1VG-3, for example, a client program (or IGATE)
might look up n1vg-3.db.aprs.net and get back an RT (route-through) record
indicating the 'local' IGATEs in order of preference.
The concept does work. I set up a test domain some months back under
aprs.home.miller.org and opentrac.net and wrote a simple gateway to create
resource records from the APRS-IS stream. Not very efficient in its current
form, but it works. If you're going to be updating positions with every
report, it's going to be a little more dynamic than your average dynamic
DNS, but I think it's still doable.
Scott
N1VG
----------------------------------------------------------------------
Subject: Re: Homeport
From: James Jefferson <jj@aprsworld.net>
Date: Tue, 9 Sep 2003 03:31:56 +0000
X-Message-Number: 50
>Hello ! People remeber us ? The people OUTSIDE of the USA ?
FIPS codes are universal down to the second level administrative district.
That means for the USA it would contain:
Country
State
County
Adapt that to whatever your country uses to express political boundaries and
it is still the same. There's nothing US centric or magical about assigning
numbers.
-Jim KB0THN
----------------------------------------------------------------------
Subject: Re: Homeport
From: "Scott Miller" <scott@home.miller.org>
Date: Mon, 8 Sep 2003 20:46:36 -0700
X-Message-Number: 51
OpenTrac already uses ISO 3166-2 codes to provide country code and
subdivision - enough for specifying the state/province, at least.
The concept I'm working on with OpenTrac for indicating message destination
is similar to the APRS filter strings - it'll let you specify a combination
of budlist, area, country code, station type, and so on. In fact, the goal
is to make it parse exactly the same as the feed filter - one says 'here's
what I'm interested in', and the other says 'here's what this message is
relevant to.' It serves to address station-to-station messages, designate
area bulletins, and so on. In the context of a backbone network, it'll be
used to negotiate between nodes what data they want to hear over the
backbone link.
Jim, how are you with BIND? Seems like aprsworld would be the ideal test
site for APRS DNS.
Scott
N1VG
---
END OF DIGEST
Read previous mail | Read next mail
| |
