1999
DOI: 10.17487/rfc2511
|View full text |Cite
|
Sign up to set email alerts
|

Internet X.509 Certificate Request Message Format

Abstract: Internet X.509 Certificate Request Message Format Status of this Memo This document specifies an Internet standards track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the "Internet Official Protocol Standards" (STD 1) for the standardization state and status of this protocol. Distribution of this memo is unlimited.

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1
1

Citation Types

0
14
0
1

Year Published

2001
2001
2008
2008

Publication Types

Select...
4
4
1

Relationship

0
9

Authors

Journals

citations
Cited by 39 publications
(16 citation statements)
references
References 0 publications
0
14
0
1
Order By: Relevance
“…The modification process is started with the creation of a certificate request [10] keeping the same public key of the old certificate. However, some other fields must also be kept unchanged to ensure the path construction and validation [7,9] for the new certificate.…”
Section: Certificate Replacementmentioning
confidence: 99%
“…The modification process is started with the creation of a certificate request [10] keeping the same public key of the old certificate. However, some other fields must also be kept unchanged to ensure the path construction and validation [7,9] for the new certificate.…”
Section: Certificate Replacementmentioning
confidence: 99%
“…Communications between the EE, RA, and CA are driven by the standard Certificate Management Protocol (CMP), 20 which is in turn based on the syntax defined by the Certificate Re- quest Message Format (CRMF). 21 It is worth noting that, although not widely adopted, certificate management over CMS (CMC) 22 is also a proposed IETF draft standard for a certificate life-cycle management protocol. CMS 23 (Cryptographic Message Syntax) is the IETF standard for a cryptographic enveloping technique for protecting messages.…”
Section: The Infrastructure Topologymentioning
confidence: 99%
“…2. Our certificate request was designed to conform with the X.509 CRMF standard [15] and is shown below. A node chooses a serving coalition of the k least costly (in terms of hop count) shareholders it is aware of, and sends a CREQ (Certificate Request) message to these serving nodes.…”
Section: Figure 2 Creq Dispatch To Shareholdersmentioning
confidence: 99%