RFC Errata
Found 3 records.
Status: Verified (1)
RFC 1535, "A Security Problem and Proposed Correction With Widely Deployed DNS Software", October 1993
Source of RFC: LegacyArea Assignment: int
Errata ID: 4781
Status: Verified
Type: Editorial
Publication Format(s) : TEXT
Reported By: Harald Albrecht
Date Reported: 2016-08-18
Verifier Name: Éric Vyncke
Date Verified: 2024-01-12
Section Solution(s) says:
Given user@a.b.c.d. connecting to host those same two tries would appear as: x.b.c.d. and x.
It should say:
Given user@a.b.c.d. connecting to host x those same two tries would appear as: x.b.c.d. and x.
Notes:
The original example text in section "Solution(s)" does not list the specific host the user@a.b.c.d. wants to connect to. From the search items listed next, I would suspect that the user wants to connect to host "x". However, I'm not exactly sure. In any case, it would be helpful to clarify the text with respect to the search list given next.
Status: Held for Document Update (2)
RFC 1535, "A Security Problem and Proposed Correction With Widely Deployed DNS Software", October 1993
Source of RFC: LegacyArea Assignment: int
Errata ID: 1084
Status: Held for Document Update
Type: Editorial
Publication Format(s) : TEXT
Reported By: Justin Pryzby
Date Reported: 2007-11-27
Held for Document Update by: Sean Turner
Section Public vs... says:
it it is possible to "intercept" the search by matching against an
It should say:
it is possible to "intercept" the search by matching against an
Errata ID: 1085
Status: Held for Document Update
Type: Editorial
Publication Format(s) : TEXT
Reported By: Justin Pryzby
Date Reported: 2007-11-27
Held for Document Update by: Brian Haberman
Section Solution(s) says:
starburst,astro.DESERTU.EDU,
It should say:
starburst.astro.DESERTU.EDU, (only 90% sure about this change)