Found 4 records.

Status: Verified (4)

RFC 9399, "Internet X.509 Public Key Infrastructure: Logotypes in X.509 Certificates", May 2023

Errata ID: 7534
Status: Verified
Type: Editorial
Publication Format(s) : TEXT, PDF, HTML
Reported By: Preston Locke
Date Reported: 2023-06-05
Verifier Name: RFC Editor
Date Verified: 2023-06-05

Section 6 says:

   After a certification path is successfully validated, the replying
   party trusts the information that the CA includes in the certificate,
   including any certificate extensions.

It should say:

   After a certification path is successfully validated, the relying
   party trusts the information that the CA includes in the certificate,
   including any certificate extensions.

Notes:

The phrase "replying party" is a typo and should be "relying party"

Errata ID: 7535
Status: Verified
Type: Editorial
Publication Format(s) : TEXT, PDF, HTML
Reported By: Preston Locke
Date Reported: 2023-06-05
Verifier Name: RFC Editor
Date Verified: 2023-06-05

Section 6 says:

   Consequently, if relying party software accepts a CA, then it should
   be prepared to (unquestioningly) display the associated logotypes to
   its human user, given that it is configured to do so.  Information
   about the logotypes is provided so that the replying party software
   can select the one that will best meet the needs of the human user.
   This choice depends on the abilities of the human user, as well as
   the capabilities of the platform on which the replaying party
   software is running.

It should say:

   Consequently, if relying party software accepts a CA, then it should
   be prepared to (unquestioningly) display the associated logotypes to
   its human user, given that it is configured to do so.  Information
   about the logotypes is provided so that the relying party software
   can select the one that will best meet the needs of the human user.
   This choice depends on the abilities of the human user, as well as
   the capabilities of the platform on which the relying party
   software is running.

Notes:

The phrases "replying party" and "replaying party" are typos and should be "relying party"

Errata ID: 7536
Status: Verified
Type: Editorial
Publication Format(s) : TEXT, PDF, HTML
Reported By: Preston Locke
Date Reported: 2023-06-05
Verifier Name: RFC Editor
Date Verified: 2023-06-05

Section 6 says:

   Care is needed when designing replying party software to ensure that
   an appropriate context of logotype information is provided.

It should say:

   Care is needed when designing relying party software to ensure that
   an appropriate context of logotype information is provided.

Notes:

The phrase "replying party" is a typo and should be "relying party"

Errata ID: 8140
Status: Verified
Type: Editorial
Publication Format(s) : TEXT, PDF, HTML
Reported By: David Schinazi
Date Reported: 2024-10-14
Verifier Name: RFC Editor
Date Verified: 2024-10-24

Section 10 says:

In addition, the use of an encrypted DNS mechanism, such as DNS over
TLS (DoT) [RFC7858] or DNS over HTTPS (DoH) [RFC9230], hides the name
resolution traffic, which is usually a first step in fetching remote
logotype objects.

It should say:

In addition, the use of an encrypted DNS mechanism, such as DNS over
TLS (DoT) [RFC7858] or DNS over HTTPS (DoH) [RFC8484], hides the name
resolution traffic, which is usually a first step in fetching remote
logotype objects.

Notes:

RFC 9399 mentions DNS over HTTPS (DoH) in an example. For this purpose it
includes an informative reference for DoH. Except the reference is wrong.
RFC 9399 incorrectly references RFC 9230 (ODoH) instead of RFC 8484 (DoH).

Report New Errata