Authority to Citizen Alert (ATOCA)

At the IETF#77 meeting today we had quite constructive discussion about the Authority to Citizen Alert (ATOCA) BOF-follow up. We focused our discussion on the charter text and you can find the updated text here:

You can provide your comments by joining the mailing list, see

I also did an audio recording of the meeting but I have to check how the quality worked out before I put it online.

In any case, the documents that turned out to be relevant for this work turn out to be the following onces:

  • Requirements, Terminology, and Framework: This document needs to be updated to reflect the different scenarios, which version -02 of the same draft already covered. This specific document talks about ‘exigent’ communication to replace the term ‘authority’. However, in today’s discussion the participants share their unhappiness about switching away from the term ‘authority’ since it is already widely established.
  • SIP Event Package for the distribution of Common Alerting Protocol (CAP) payloads: This document defines an event package for SIP to distribute CAP essentially filling in a registration template for event packages. A new MIME type is also defined.
  • Conveying a CAP message in a SIP message is not defined in a separate document even though there is a description of a CAP delivery for citizen-to-authority communication (i.e., communication in the reverse direction).
  • An interesting specification is the definition of Service URNs for early warning categories (such as ‘’), as described in draft-rosen-ecrit-lost-early-warning. The basic idea is that an entity uses LoST with the findService request (including location and the previously mentioned new Service URNs) to find a server they can then send a subscription to in order to receive notifications.

In our discussions today we also noted that the specification for CAP over XMPP already exists with XEP-0127.

Leave a Reply

Your email address will not be published. Required fields are marked *