sos

April 20, 2023 53rd IETF - SIPPING 1

sos

Henning SchulzrinneColumbia University

April 20, 2023 53rd IETF - SIPPING 2

Summary

Address convention:– sip:sos@local-domain if known– sip:sos@aor-domain if not known– also: sos.service (e.g., sos.police, sos.fire,

sos.rescue) for specific services

Should UA translate 911 and 112 to sos?

First proxy that recognizes sos routes to appropriate emergency call center– maybe just use sos@aor-domain always

April 20, 2023 53rd IETF - SIPPING 3

Summary of discussion Out of scope: service behavior

– no caller-initiated disconnect even PSTN can’t do this

– call back Out of scope: finding appropriate

emergency call center– likely to be country-specific– currently, proprietary protocols (e.g., Intrado)

but use of universal identifier simplifies UA design:– accidental disconnect prevention– inclusion of location information

April 20, 2023 53rd IETF - SIPPING 4

Going forward

Status: WG item? I? BCP? PS? Unlike service URIs, agreement very

helpful– prevent accidental assignment to non-

emergency use (e.g., ad-hoc conference)– UA behavior

Informal coordination with NENA transition WG

Consider it ready for WGLC (except for IANA consideration section)