[aprssig] Is the APRS Spec for APRS Data Type Identifier just randomly ignored? Should it be?
James Washer washer at trlp.comThu Aug 18 17:08:52 UTC 2005
- Previous message: [aprssig] Is the APRS Spec for APRS Data Type Identifier just randomly ignored? Should it be?
- Next message: [aprssig] Is the APRS Spec for APRS Data Type Identifier just randomly ignored? Should it be?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
That's my point... APRS is based on BEACON-style destinations.. I'm (still) just aguing that it if you send a packet that has a valid-dti in the dti position, the rest of the packet should "follow the rules for that dti", or be ignored. You are correct the the "T" was unforunate. - jim On Thu, 18 Aug 2005 12:16:07 -0400 Steve Dimse <steve at dimse.com> wrote: > > On Aug 18, 2005, at 11:56 AM, James Washer wrote: > > > The reason I asked this, is that destination=BEACON is explicitly > > included in the APRS spec, hence, it's not correct to say a > > destination=BEACON packet is NOT an APRS packet. > > > > BEACON is a destination callsign defined in the APRS spec, which > simply means it is included in the default ALTNET. Giving something a > destination of BEACON does not make it either an APRS packet or a non- > APRS packet. In fact, it specifically is in the spec so that non-APRS > station on an APRSS network can be seen. > > Steve K4HG > > _______________________________________________ > aprssig mailing list > aprssig at lists.tapr.org > https://lists.tapr.org/cgi-bin/mailman/listinfo/aprssig
- Previous message: [aprssig] Is the APRS Spec for APRS Data Type Identifier just randomly ignored? Should it be?
- Next message: [aprssig] Is the APRS Spec for APRS Data Type Identifier just randomly ignored? Should it be?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the aprssig mailing list
