2010
DOI: 10.17487/rfc5914
|View full text |Cite
|
Sign up to set email alerts
|

Trust Anchor Format

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1

Citation Types

0
23
0

Year Published

2010
2010
2022
2022

Publication Types

Select...
5
2
1

Relationship

2
6

Authors

Journals

citations
Cited by 15 publications
(23 citation statements)
references
References 3 publications
0
23
0
Order By: Relevance
“…The TAL is analogous to the TrustAnchorInfo data structure specified in [RFC5914], which is on the Standards Track. That specification could be used to represent the TAL, if one defined an rsync URI extension for that data structure.…”
Section: Trust Anchor Locator Formatmentioning
confidence: 99%
“…The TAL is analogous to the TrustAnchorInfo data structure specified in [RFC5914], which is on the Standards Track. That specification could be used to represent the TAL, if one defined an rsync URI extension for that data structure.…”
Section: Trust Anchor Locator Formatmentioning
confidence: 99%
“…| However, [RFC5914] defines several formats for representing trust | anchor information, including self-signed certificates, and [RFC5937] | provides an example of how such information may be used to initialize | the path validation inputs. Implementations are free to make use of | any additional information that is included in a trust anchor | representation, or to ignore such information.…”
Section: Yeementioning
confidence: 99%
“…However, if the store containing this TA is used by multiple applications that serve different purposes, the same key may be used (inappropriately) to validate other types of objects such as certificates or Online Certificate Status Protocol (OCSP) responses. Prior to publication of [RFC5914], there was no standard general-purpose mechanism for limiting the applicability (scope) of a trust anchor. A common practice to address this problem is to place different TAs in different stores and limit the set of applications that access a given TA store.…”
Section: Problem Statementmentioning
confidence: 99%
“…The requirements stated in this document were prepared prior to the publication of [RFC5914] and [RFC5934]. The document was not published at that time to allow for changes in requirements during the development of the associated technical specifications.…”
mentioning
confidence: 99%
See 1 more Smart Citation