Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

DNS-ID vs. dNSName #31

Closed
hannestschofenig opened this issue Oct 22, 2023 · 2 comments
Closed

DNS-ID vs. dNSName #31

hannestschofenig opened this issue Oct 22, 2023 · 2 comments
Assignees
Labels
cert certificate profiling

Comments

@hannestschofenig
Copy link
Collaborator

If the EUI-64 format is used to identify the subject of an end entity certificate, it MUST be encoded in a subjectAltName of type DNS-ID as a string of the form HH-HH-HH-HH-HH-HH-HH-HH where 'H' is one of the symbols '0'-'9' or 'A'-'F'.

Michael:
"DNS-ID" is not how 5280 calls it...
It uses dNSName.
I'm not sure I'd agree with dNSNAME, and you'll see that we tried to get something similar past RH on RFC8994, and wound up having to use otherName.

Thomas:
yeah, this bit reuses bits of RFC6125 glossary, which I thought was established terminology:

DNS-ID = a subjectAltName entry of type dNSName; see [PKIX]

Michael:

okay, that's news to me that we can call it the extension DNS-ID. I thought that was the check. And, I don't see how an EUI-64 going to pass a DNS-ID check.

@thomas-fossati thomas-fossati added the cert certificate profiling label Nov 13, 2023
@thomas-fossati
Copy link
Owner

ACTION: cross-check this against RFC9525 (which updates 6125)

@thomas-fossati thomas-fossati self-assigned this Sep 2, 2024
@mcr
Copy link
Collaborator

mcr commented Nov 18, 2024

closed by #53

@mcr mcr closed this as completed Nov 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
cert certificate profiling
Projects
None yet
Development

No branches or pull requests

3 participants