IP address reference identities #685
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
martinthomson
commented
Jan 22, 2021
martinthomson
force-pushed
the
add-ip-id
branch
from
2c8f2a6
to
1eba27d
Compare
This is how it works in practice. RFC 6125 is due for an update, I guess. iPAddress subjectAltName has been supported for years and years, but it never managed to capture it properly. This is definitely a big change in that it now outlaws CN-ID. And the definition of IP-ID here is probably overreach, but I don't see how we can avoid that. I don't want to update RFC 6125 here (as much as it needs updating), so making the definition standalone seemed like the right way to handle it. Closes httpwg#680.
martinthomson
force-pushed
the
add-ip-id
branch
from
1eba27d
to
9be0301
Compare
reschke
reviewed
Jan 24, 2021
reschke
reviewed
Jan 24, 2021
royfielding
reviewed
Jan 24, 2021
royfielding
reviewed
Jan 24, 2021
royfielding
reviewed
Jan 24, 2021
Co-authored-by: Julian Reschke <julian.reschke@gmx.de>
Co-authored-by: Julian Reschke <julian.reschke@gmx.de>
Co-authored-by: Roy T. Fielding <fielding@gbiv.com>
royfielding
approved these changes
Jan 24, 2021
reschke
reviewed
Jan 25, 2021
reschke
approved these changes
Jan 25, 2021
Co-authored-by: Julian Reschke <julian.reschke@gmx.de>
kaduk
reviewed
Feb 1, 2021
| <section title="IP-ID reference identity" anchor="https.ip-id"> | ||
| <t> | ||
| A server that is identified using an IP address literal in the "host" field | ||
| of an "https" URI has a reference identity of type IP-ID. An IP version 4 |
There was a problem hiding this comment.
I note that in the recently approved draft-ietf-dtn-tcpclv4, we used the term IPADDR-ID for the iPAddress SAN.
If we think that IP-ID is better, I can try to reach out to get the DTN doc changed during AUTH48 to be consistent.
triple-underscore
added a commit
to triple-underscore/triple-underscore.github.io
that referenced
this pull request
Feb 8, 2021
Make reference to Caching less specific editorial semantics httpwg/http-core#746 Clarify status code range semantics httpwg/http-core#717 IP address reference identities httpwg/http-core#685 Try to better define "strong" encryption httpwg/http-core#695 Use overwrite rather than "white out" editorial semantics httpwg/http-core#699 A content-type converts abstract data into bits semantics httpwg/http-core#702 Cite conditional requests in 412 definition httpwg/http-core#721 Clarify that selection between multiple acceptable codings is only relevant when some of the acceptable ones are redundant editorial semantics httpwg/http-core#720 Values of newly defined fields should only use VCHAR/SP/HTAB editorial semantics httpwg/http-core#718 move paragraph about delimiters down editorial semantics httpwg/http-core#716 Remove 6919 language editorial has-proposal semantics httpwg/http-core#693
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is how it works in practice.
RFC 6125 is due for an update, I guess. iPAddress subjectAltName has been
supported for years and years, but it never managed to capture it properly.
This is definitely a big change in that it now outlaws CN-ID. And the
definition of IP-ID here is probably overreach, but I don't see how we can
avoid that. I don't want to update RFC 6125 here (as much as it needs
updating), so making the definition standalone seemed like the right way to
handle it.
Closes #680.