<html><P><FONT face=Arial size=2>From a strictly regulatory perspective (U.S.), are not the ID requirements the same for all RF transmissions, regardless of mode?<BR><BR>For instance, it is not uncommon for stations (and repeaters) transmitting voice to ID in CW, even though the communication was not CW? Is it permissable to transmit an APRS packet containing tactical call sign, yet ID on the transmitted frequency via voice (or CW) every 10 minutes, and at the end of transmission? Is not the legal requirement to identify the "station", not the packet, as far as the FCC is concerned.<BR><BR>Just a question (ducking).<BR><BR><BR>Jeff<BR>N5TEV<BR></FONT><BR>-----Original Message-----<BR>From: Andrew Rich [mailto:vk4tec@tech-software.net]<BR>Sent: Monday, September 14, 2009 07:12 PM<BR>To: 'Tom Hayward', 'TAPR APRS Mailing List'<BR>Subject: *** SPAM *** Re: [aprssig] TAC-5<BR><BR>Hmm<BR><BR>Interesting<BR><BR>Seems the APRS-IS can introduce all sorts of LAW clashes - hee hee<BR><BR>Our law says EACH packet should contain an ID of the orginating station<BR><BR>Not to be confused with VOICE, that requires you to IDENT every X minutes<BR><BR><BR><BR>----------------------------------------------------------<BR>Andrew Rich<BR>Airways Technical Officer Grade 4<BR>Surveillance - RADAR ADS-B<BR>Amateur Radio Callsign VK4TEC<BR>email: vk4tec@tech-software.net<BR>web: www.tech-software.net<BR>----- Original Message ----- <BR>From: "Tom Hayward" <esarfl@gmail.com><BR>To: "Andrew Rich" <vk4tec@tech-software.net>; "TAPR APRS Mailing List" <BR><aprssig@tapr.org><BR>Sent: Sunday, September 13, 2009 7:50 AM<BR>Subject: Re: [aprssig] TAC-5<BR><BR><BR>On Sat, Sep 12, 2009 at 2:42 PM, Andrew Rich <vk4tec@tech-software.net> <BR>wrote:<BR>> Maybe he needs to put a callsign instead of TAC-5<BR><BR>Why? He's not violating the AX.25 protocol or any US law. Tactical<BR>callsigns are perfectly legal in the US. We commonly use them to give<BR>context to digipeater names, but they can also be used on trackers.<BR>The legal identification requirement is satisfied by his callsign in<BR>the status text.<BR><BR>Tom KD7LXL<BR><BR><BR>> ----- Original Message -----<BR>> From: Cap Pennell<BR>> To: 'TAPR APRS Mailing List'<BR>> Sent: Sunday, September 13, 2009 6:31 AM<BR>> Subject: Re: [aprssig] TAC-5<BR>><BR>> That's Walter's TinyTrak3 station.<BR>><BR>> But the K1IMD-14 digipeater is mis-configured now trapping WIDE1-1 packets<BR>> (though heard direct by a IGate), and the digipeater with the Alias of<BR>> WIDE1-1 is very unfortunately not even traceable.<BR>><BR>><BR>><BR>> TAC-5>APT311,WIDE1-1*,WIDE2-1,qAS,K1IMD:>KA2RGI-14<BR>> TAC-5>APT311,K1IMD-14*,WIDE1,WIDE2-1,qAR,W1OEM:$GPRMC,200847,A,4105.8410,N,07221.6001,W,007,181,120909,,*06<BR>><BR>><BR>><BR>> Perhaps the K1IMD-14 KPC-3 v8.2 TNC needs the modern setting of UIdigi<BR>> WIDE1-1 . <grin><BR>><BR>><BR>><BR>> 73, Cap KE6AFE<BR>><BR>><BR>><BR>> From: aprssig-bounces@tapr.org [mailto:aprssig-bounces@tapr.org] On Behalf<BR>> Of Andrew Rich (Home)<BR>> Sent: Saturday, September 12, 2009 9:32 AM<BR>> To: TAPR APRS Mailing List<BR>> Subject: [aprssig] TAC-5<BR>><BR>><BR>><BR>> Nice callsign<BR>><BR>><BR>><BR>> TAC-5>APT311,WIDE1-1,W1DX,WIDE2*,qAR,N1OBU-13:$GPRMC,163020,A,4105.1359,N,07226.6615,W,004,271,120909,,*01<BR>> TAC-5>APT311,W1DX,WIDE1*,WIDE2-1,qAR,N1OBU-13:$GPRMC,163026,A,4105.1332,N,07226.6710,W,004,226,120909,,*0C<BR>> TAC-5>APT311,K1IMD-14*,WIDE1,WIDE2-1,qAR,W1OEM:$GPRMC,163032,A,4105.1273,N,07226.6759,W,003,199,120909,,*00<BR>> TAC-5>APT311,W1NLC*,WIDE2-1,qAR,N1OBU-13:$GPRMC,163039,A,4105.1247,N,07226.6786,W,000,249,120909,,*03<BR>><BR>><BR>><BR>><BR>><BR>> ----------------------------------------------------------<BR>> Andrew Rich<BR>> Airways Technical Officer Grade 4<BR>> Surveillance - RADAR ADS-B<BR>> Amateur Radio Callsign VK4TEC<BR>> email: vk4tec@tech-software.net<BR>> web: www.tech-software.net<BR>><BR>> ________________________________<BR>><BR>> _______________________________________________<BR>> aprssig mailing list<BR>> aprssig@tapr.org<BR>> https://www.tapr.org/cgi-bin/mailman/listinfo/aprssig<BR>><BR>> ________________________________<BR>><BR>> No virus found in this incoming message.<BR>> Checked by AVG - www.avg.com<BR>> Version: 8.5.409 / Virus Database: 270.13.92/2364 - Release Date: 09/11/09<BR>> 17:51:00<BR>><BR>> _______________________________________________<BR>> aprssig mailing list<BR>> aprssig@tapr.org<BR>> https://www.tapr.org/cgi-bin/mailman/listinfo/aprssig<BR>><BR>><BR><BR><BR>--------------------------------------------------------------------------------<BR><BR><BR><BR>No virus found in this incoming message.<BR>Checked by AVG - www.avg.com<BR>Version: 8.5.409 / Virus Database: 270.13.92/2364 - Release Date: 09/11/09 <BR>17:51:00<BR><BR><BR>_______________________________________________<BR>aprssig mailing list<BR>aprssig@tapr.org<BR>https://www.tapr.org/cgi-bin/mailman/listinfo/aprssig<BR></P></html>