2005
DOI: 10.17487/rfc4158
|View full text |Cite
|
Sign up to set email alerts
|

Internet X.509 Public Key Infrastructure: Certification Path Building

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1

Citation Types

0
32
0
1

Year Published

2006
2006
2021
2021

Publication Types

Select...
5
3
2

Relationship

0
10

Authors

Journals

citations
Cited by 65 publications
(35 citation statements)
references
References 1 publication
0
32
0
1
Order By: Relevance
“…Any entity can authenticate itself via its certificate, as long as it owns the associated private key, which is never transmitted over the network. The certificate management requires a Public Key Infrastructure (PKI) [20], in which specific trusted entities, called Certification Authorities (CA), are in charge of certificate delivery. The TeSLA architecture has its own PKI, to manage the certificates within the TeSLA domain on one hand; and within the institution domain on the other hand.…”
Section: Securing the Tesla Architecturementioning
confidence: 99%
“…Any entity can authenticate itself via its certificate, as long as it owns the associated private key, which is never transmitted over the network. The certificate management requires a Public Key Infrastructure (PKI) [20], in which specific trusted entities, called Certification Authorities (CA), are in charge of certificate delivery. The TeSLA architecture has its own PKI, to manage the certificates within the TeSLA domain on one hand; and within the institution domain on the other hand.…”
Section: Securing the Tesla Architecturementioning
confidence: 99%
“…Path building [7], and validation [8] have been central issues in PKI domain extensions. There have been proposed three major methods of path construction models: hierarchical, mutual, and bridge models.…”
Section: Related Workmentioning
confidence: 99%
“…For example, typical operations in the context of a public-key infrastructure may involve extra network communication handshakes with the public-key infrastructure and with certification authorities and may typically involve additional processing steps in the end systems. These operations would include validating digital certificates (RFC 3029, [24]), ascertaining the revocation status of digital certificates (RFC 2560, [23]), asserting certificate policies, construction of certification path(s) ( [26]), requesting and obtaining necessary certificates (RFC 2511, [25]), and management of certificates for such purposes ( [22]). Such steps and tasks all result in further delay of the key agreement or key establishment phase among the end systems, which negatively affects setup time.…”
Section: Euchner Standards Track [Page 3]mentioning
confidence: 99%