[aprssig] APRS digi from the digi point of view
Eric H. Christensen eric at christensenplace.usThu Jun 14 23:29:22 UTC 2007
- Previous message: [aprssig] APRS digi from the digi point of view
- Next message: [aprssig] APRS digi from the digi point of view
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Jim, IMHO, I'd like to see additional n-N protocols offered. Maybe up to five. In that manner you could support WIDEn-N, SSn-N, an Interstaten-N, and any other tactical net n-N that might be necessary for the area. Maybe have a check box saying if you want that particular n-N to be traceable or not. RELAY and WIDE should not be offered. We need to keep things going forward not backwards. My opinion, of course. 73s, Eric W4OTN Jim Wagner wrote: > OK, lets say someone is writing an application that COULD have APRS digi > function. The question is what digi alias schemes should said > application be prepared to support: > > (1) Simple name or call? Sure, all digis, APRS or not, need to do that > > (2) RELAY and WIDE? I know that they are deprecated, but should they be > offered? > > (3) WIDEn-N? Yes? > > (4) What about TRACEn-N? If so, what are the rules used by TRACE digis? > What do they substitute where? > > (5) Are there other NAMEn-N constructs in use? Do you allow an arbitrary > 5 char name? > > (6) Other digi reference schemes? > > Thanks > Jim, KA7EHK > > > _______________________________________________ > aprssig mailing list > aprssig at lists.tapr.org > https://lists.tapr.org/cgi-bin/mailman/listinfo/aprssig -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iQIVAwUBRnHPUFPETzpAxiDcAQKD8hAAmISNOI8LPTkJkGQ0Kxo9c+kY8O0I6FW6 xMpTo9nJ3eyzkyv2fdXt/w3qdCuqCN+dzp90ZJpmMjcr82BK7AGOc3IATx1i3USk WJ8h1Ugh7B1XJSVa6QiPaMEv8QTIKnir/ZuCHdJhViiaJ8Wps1odbvY9Bk0SReey dxHIGYE+aGuhOhMEWJcpISdHJU3rbZfWQvYvuWzyuAGj/7xoeCgg/VYaAeo0Woh1 HFTeqHwI5B6GdCWBG6ecpSKZYrmNZCcoQIZV90+3isDpWWz70FdZCmg1RhBiPV/U zmTZmzfGincLjDF7VwT6Op0bqjbL3bHpif7Bx1faTeps7oxiyHQcUhfnJxkQ7lh/ LgTennWhmJkTJ1DoMRgUz3pFR5K0cLIQXllpr4iybO7m+a/N/YRTlMBskpG7wKa7 KtsfPayh0gaNEldRjMiRm37Dp9tIypMVtrlVmo2Laqrc21LcpXsa8A/YnZYqC0RI LM0Vrh1sHyRppR8RG+YbDgGZV/gP5oMJ+gHbqAT/x3z5utOxONu0PDRmzxChwhyo 4DVoIA+/PHdoFStJsv0pdBlzdygbDXypwUv0CHKZIU7vNngQL5NCIONMZ54KybQv 5RZnccWvLVUOyU/4C9HYmgFQ3kEQVoDxDnBAoI7faqyz8i8YF2DrxJmtdyCNtkUK 6V0hiTFS/L0= =E6bL -----END PGP SIGNATURE-----
- Previous message: [aprssig] APRS digi from the digi point of view
- Next message: [aprssig] APRS digi from the digi point of view
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the aprssig mailing list
