2011
DOI: 10.17487/rfc6277
|View full text |Cite
|
Sign up to set email alerts
|

Online Certificate Status Protocol Algorithm Agility

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
5

Citation Types

0
7
0

Year Published

2012
2012
2017
2017

Publication Types

Select...
3
2

Relationship

1
4

Authors

Journals

citations
Cited by 8 publications
(10 citation statements)
references
References 0 publications
0
7
0
Order By: Relevance
“…Additional mechanisms addressing PKIX operational requirements are specified in separate documents. This specification obsoletes [RFC2560] and [RFC6277]. The primary reason for the publication of this document is to address ambiguities that have been found since the publication of RFC 2560.…”
Section: Introductionmentioning
confidence: 99%
See 2 more Smart Citations
“…Additional mechanisms addressing PKIX operational requirements are specified in separate documents. This specification obsoletes [RFC2560] and [RFC6277]. The primary reason for the publication of this document is to address ambiguities that have been found since the publication of RFC 2560.…”
Section: Introductionmentioning
confidence: 99%
“…o Section 4.3 changes the set of cryptographic algorithms that clients must support and the set of cryptographic algorithms that clients should support as specified in [RFC6277].…”
Section: Introductionmentioning
confidence: 99%
See 1 more Smart Citation
“…If there are no more communication media than the own VANET, no trusted-third parties (like the corresponding CA) can be assumed to be permanently available. Thus, online certificate status protocol (OCSP) [28] or, in general, any online solution is not suitable for this context. Several CRLs distribution protocols have been proposed for this purpose.…”
Section: Introductionmentioning
confidence: 99%
“…In the process of dealing with the Online Certificate Status Protocol (OCSP) agility issues in [RFC6277], it was noted that we really wanted to describe information to be used in selecting a public key, but we did not have any way of doing so. This document fills that hole by defining a set of Secure/Multipurpose Internet Mail Extensions (S/MIME) Capability types for a small set of public key representations.…”
Section: Introductionmentioning
confidence: 99%