RFC Errata
Found 2 records.
Status: Rejected (2)
RFC 7050, "Discovery of the IPv6 Prefix Used for IPv6 Address Synthesis", November 2013
Note: This RFC has been updated by RFC 8880
Source of RFC: behave (tsv)
Errata ID: 5152
Status: Rejected
Type: Technical
Publication Format(s) : TEXT
Reported By: Mark Andrews
Date Reported: 2017-10-11
Rejected by: Magnus Westerlund
Date Rejected: 2021-01-13
Section IANA Conside says:
N/A
It should say:
8.x DNSSEC ipv4only.arpa MUST be insecurely delegated. This allows ISP's to modify / generate AAAA responses for ipv4only.arpa AAAA queries that will pass through unmodified caching servers as required by 8.1 (4).
Notes:
The protocol as described does not work when there is a validating caching server in the resolution path.
IANA should have been instructed to insecurely delegate ipv4only.arpa. This allows ISP's to modify the
AAAA response without running foul of DNSSEC validation.
--VERIFIER NOTES--
So this errata was correct on the issue, but errata was not the appropriate way of resolving this issue. RFC 8880 that updates RFC 7050 specifies a resolution to this errata.
Errata ID: 6270
Status: Rejected
Type: Technical
Publication Format(s) : TEXT
Reported By: Mark Andrews
Date Reported: 2020-09-01
Rejected by: Magnus Westerlund
Date Rejected: 2021-01-13
Section 3.4 says:
"PTR" query #2 for "2001:db8:43::192.0.0.170
It should say:
"PTR" query #2 for "2001:db8:43::192.0.0.171
Notes:
The second PTR query should be for the reverse of the DNS64 mapped well known address 192.0.0.171. This looks like a cut-and-paste error where 170 was not changed to 171.
--VERIFIER NOTES--
After discussion on Behave mailing list it appears that the example is not in contradiction with what the RFC specifies. There was some additional discussion around this for other potential improvements that should be considered in case the specification is revised.
Mail thread: https://mailarchive.ietf.org/arch/msg/behave/KuvD2ppb9LLD3LnzS-DJ7wVCgvc/