Skip to main content

Bootstrapping STIR Deployments with Self-Signed Certs and Callbacks

Document Type Expired Internet-Draft (individual)
Expired & archived
Authors Jonathan Rosenberg , Cullen Fluffy Jennings
Last updated 2018-09-02 (Latest revision 2018-03-01)
RFC stream (None)
Intended RFC status (None)
Stream Stream state (No stream defined)
Consensus boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Expired
Telechat date (None)
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:


Robocalling has become an increasing problem in the Public Switched Telephone Network (PSTN). A partial remedy for it is the provision of an authenticated caller ID in the PSTN, which today is lacking. Secure Telephone Identity Revisited (STIR) provides this through the usage of signed payloads in Session Initiation Protocol (SIP) calls. However, STIR deployment requires a global certificate system which allows for worldwide issuance of certifications that attest to which numbers a provider is responsible for. Such a system is likely to take years to rollout. To accelerate STIR deployment, this draft proposes a technique wherein STIR can be used without certificates that attest to number ownership. This is done through a combination of self-signed certificates, reverse callbacks and cached validations.


Jonathan Rosenberg
Cullen Fluffy Jennings

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)