lints: add more context to w_subject_contains_malformed_arpa_ip
.
#345
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.
Section 7.1.4.2.1 of the BRs is a good citation for
e_subject_contains_reserved_arpa_ip
but isn't a great choice forw_subject_contains_malformed_arpa_ip
.When the
.arpa
address doesn't have enough labels, or can't be parsed as an IP address it's clear that it isn't an internal IP address and so 7.1.4.2.1 isn't a good citation. Section 3.2.2.6 talks about wildcard domains for "registry controlled" zones, and.arpa
is one of those (based on BCP49). A wildcard label is one way the.arpa
domain wouldn't parse as an IP.While the larger discussion on how
.arpa
domains that aren't formatted per RFC 3596 unfolds we can ref 3.2.2.6 and add a bit more context to the lint and description. It isn't perfect, but I think less confusing than ref'ing 7.1.4.2.1, which clearly doesn't apply.See also #343