NG112 reference
Tls
Structured NG112 reference page.
112 readiness
Policy, location, routing, and response quality connected in one operational model.
Security
TLS for Emergency Signaling
TLS is useful only when certificates, names, trust anchors, renewal and troubleshooting are operationally mature. A perfect encryption plan that fails during renewal is a bad emergency service plan.
Emergency interface
->TLS handshake
->Trusted session
->Emergency transaction
What it does
TLS can protect emergency signaling confidentiality and integrity where supported by the architecture.
TLS can secure SIP and HTTP-based interfaces such as interconnect signaling and HELD.
How it works
- Authenticates endpoints through certificates.
- Encrypts and integrity-protects signaling or API traffic.
- Depends on lifecycle management for certificates and trust stores.
Key interfaces and protocols
- SIP over TLS
- HTTPS/HELD
- Certificate authorities
- Monitoring
Systems it interacts with
- SIP
- HELD
- BCF
- Security
- DNS/service discovery
Common failure modes
- Expired certificate
- Hostname mismatch
- Untrusted CA
- Clock drift breaks validation
Implementation considerations
- Automate renewal with emergency-safe change windows.
- Monitor expiry and failed handshakes.
- Document break-glass procedures.
Standards
- IETF TLS practices
- ETSI NG112 references
Related NG112 technologies
Related country deployments
No country deployments are listed here until independently verified against official or high-confidence sources.
Related articles
Sources
- RFC 5985: HTTP-Enabled Location Delivery - IETF, accessed 2026-08-31
- RFC 6442: Location Conveyance for SIP - IETF, accessed 2026-08-31
- ETSI TS 103 479 deliverable directory - ETSI, accessed 2026-08-31
Last verified: 2026-08-31
Advertisement