1.3.6.1.4.1.61513Apr 5
@aprsfi is aprsorg that is handling deviceids different from the aprs foundation?
Show threadaprs.fiApr 5
@xssfox No, at least I'm not aware of any other allocations happening than https://github.com/aprsorg/aprs-deviceid
GitHub - aprsorg/aprs-deviceid: APRS device identification data: tocalls.txt + mic-e-types.txt current master allocations (YAML, JSON, XML)

APRS device identification data: tocalls.txt + mic-e-types.txt current master allocations (YAML, JSON, XML) - aprsorg/aprs-deviceid

GitHub
Show thread1.3.6.1.4.1.61513Apr 5
@aprsfi I received this which goes to https://how.aprs.works/aprs101-pdf-is-obsolete/
Show threadaprs.fiApr 5

@xssfox Hmm. I'm sorry, I'm not following. Is there some contradiction there?

https://how.aprs.works/aprs-device-identification-database/

APRS Device Identification Database (aka tocalls)

History In the past, Bob Bruninga (WB4APR) maintained two documents on the original aprs.org website: * tocalls.txt - DEPRECATED * mic-e-types.txt - DEPRECATED (mic-e-types are not covered in this document) Any vendor or individual who wanted a new APRS device identifier had to contact Bob directly. He took care

How APRS Works
Show thread1.3.6.1.4.1.61513Apr 5
@aprsfi oh I mean is APRS Org the same group of people as APRS Foundation. It's a bit confusing that there is an aprsorg GitHub org and then APRS foundation running under wb2osz GitHub account
Show threadaprs.fi
@xssfox Only now I realise my brain failed to properly parse your original clear and simple question in the first post. I guess the answer is, I'm currently handing out the identifiers on behalf of the APRS Foundation, and they're happily pointing everyone towards my database, and it's also published for downloading on their CDN capacity & domain name.
Apr 5 at 7:09amWeb