OCSP Usage for Secure Telephone Identity Certificates
draft-ietf-stir-certificates-ocsp-00
| Document | Type | Expired Internet-Draft (stir WG) | |
|---|---|---|---|
| Last updated | 2017-09-14 (latest revision 2017-03-13) | ||
| Stream | IETF | ||
| Intended RFC status | (None) | ||
| Formats |
Expired & archived
pdf
htmlized (tools)
htmlized
bibtex
|
||
| Stream | WG state | Dead WG Document | |
| Document shepherd | No shepherd assigned | ||
| IESG | IESG state | Expired | |
| Consensus Boilerplate | Unknown | ||
| Telechat date | |||
| Responsible AD | (None) | ||
| Send notices to | (None) | ||
https://www.ietf.org/archive/id/draft-ietf-stir-certificates-ocsp-00.txt
Abstract
When certificates are used as credentials to attest the assignment or ownership of telephone numbers, some mechanism is required to convey certificate freshness to relying parties. This document specifies the use of the Online Certificate Status Protocol (OCSP) as a means of retrieving real-time status information about such certificates, defining new extensions to compensate for the dynamism of telephone number assignments.
Authors
Jon Peterson
(jon.peterson@neustar.biz)
Sean Turner
(sean@sn3rd.com)
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)