[aprssig] AX25 Protocol group (Jack Chomley

[Scott Miller]

It'll only affect AX.25 applications if anyone elects to use the new 
protocol.  If the extension is not being done in a manner that's 
backwards-compatible... well, good luck with that!  It's not like 
someone can throw a switch and turn off AX.25 2.2, and unless there's a 
compelling reason to switch for a large portion of the user population, 
no one's going to bother.

Is the working group even a going concern these days?  Or has it been 
reconstituted?  Last time I tried to get a PID assigned NO ONE seemed to 
be answering the mail there.

Scott
N1VG

Phillip wrote:
> Hi Jack,
>                 I think you should re read what I sent,
>  
> It appears that Barry  VK2AAB who is a WIA Federal Councillor for the 
> VK2 area
> may know more about this . I have asked him for more information.
>  
>  From what I can gather from his message is, that this appears to be a 
> for gone conclusion
> and that these changes are going to happen some time .
>  
> This will impact on every application that uses the ax25 protocol  if I 
> am not
> mistaken.
>  
> Does this impact on the APRS spec and those that produce
> firmware for trackers etc.
>  
> Remembering that there are over 5000 Kenwood D7 series
> aprs capable radios that probably can't be upgraded
>  
> UI-View will not be able to be upgraded
>  
> Every TNC will need to be upgraded .
>  
> I hope someone can answer this
>  
> 73 Phillip
> ZL2TZE
>  
> ------------------------------------------------------------------------------------------
>    10.) Re: AX25 Protocol group (Jack Chomley
>   Message: 10
> Date: Mon, 02 Jun 2008 09:16:21 +1000
> From: Jack Chomley <radio at irock.com.au <mailto:radio at irock.com.au>>
> Subject: Re: [aprssig] AX25 Protocol group
> To: TAPR APRS Mailing List <aprssig at lists.tapr.org 
> <mailto:aprssig at lists.tapr.org>>
> Message-ID: <7.0.0.16.2.20080602091449.02304858 at irock.com.au 
> <mailto:7.0.0.16.2.20080602091449.02304858 at irock.com.au>>
> Content-Type: text/plain; charset="us-ascii"
>  
> Why not just put the extended call in Beacon text?
>  
> 73s
>  
> Jack VK4JRC
>  
>  
> At 08:26 AM 2/06/2008, you wrote:
>  >
>  >Hi,
>  >       I have heard that the above group may be looking at altering the
>  >callsign fields to allow for extended callsigns
>  >
>  >Eg WB6XXX/VK9   or VK9XXX/WB6
>  >
>  >If this happens then all ax25 firmware / software will have to be 
> re-written
>  >   What a job
>  >
>  >Has anyone else heard this ???
>  >
>  >
>  > From : VK2AAB
>  >
>  >To : PACKET at WW
>  >
>  >Type/status : B$
>  >
>  >Date/time : 29-Apr 20:27
>  >
>  >BID (MID) : 1968_VK2AAB
>  >
>  >Message # : 373091
>  >
>  >Title : Re:Time to switch off AX25
>  >
>  >Path: !ZL2WA!ZL2BAU!7M3TJZ!DK0WUE!I0TVL!CX2SA!VK2DOT!VK2TV!VK2AAB!
>  >
>  >From: VK2AAB at VK2AAB.#SYD.NSW.AUS.OC <mailto:VK2AAB at VK2AAB.#SYD.NSW.AUS.OC>
>  >
>  >To : PACKET at WW
>  >
>  >Ray might be interested to know that the ax25 protocol group will be 
> making
>  >
>  >changes for variable length callsign fields.
>  >
>  >It is not just a problem for Australianxxx calls.
>  >
>  >There are other special needs such as portable operation VK2AAB/ZL2 etc.
>  >
>  >They are working this year on other changes but it is definately in their
>  >
>  >todo list.
>  >
>  >I did not know that Roger had requested the source code be destroyed.
>  >
>  >Thats a shame, from memory I think someone volunteered to him to take 
> it over.
>  >
>  >73 Barry VK2AAB
>  >
>  >
>  >73 Phillip
>  >ZL2TZE
>  >
> 	
> 
> <http://www.incredimail.com/index.asp?id=509&lang=9&rui=58529483>
> 
> 
> ------------------------------------------------------------------------
> 
> _______________________________________________
> aprssig mailing list
> aprssig at lists.tapr.org
> https://lists.tapr.org/cgi-bin/mailman/listinfo/aprssig