This erratum should be rejected. RFC 4035 defines "indeterminate" in
Section 4.4.3. RFC 4035 and RFC 4033 define "indeterminate" differently.
--Paul Hoffman
On 16 Jun 2018, at 7:29, RFC Errata System wrote:
The following errata report has been submitted for RFC7672,
"SMTP Security via Opportunistic DNS-Based Authentication of Named
Entities (DANE) Transport Layer Security (TLS)".
--------------------------------------
You may review the report below and at:
http://www.rfc-editor.org/errata/eid5395
--------------------------------------
Type: Technical
Reported by: Matt McCutchen <[email protected]>
Section: 2.1.1
Original Text
-------------
DNS records that would be
classified "indeterminate" in the sense of [RFC4035] are simply
classified as "insecure".
Corrected Text
--------------
DNS records that would be
classified "indeterminate" in the sense of [RFC4033] are simply
classified as "insecure".
Notes
-----
Instructions:
-------------
This erratum is currently posted as "Reported". If necessary, please
use "Reply All" to discuss whether it should be verified or
rejected. When a decision is reached, the verifying party
can log in to change the status and edit the report, if necessary.
--------------------------------------
RFC7672 (draft-ietf-dane-smtp-with-dane-19)
--------------------------------------
Title : SMTP Security via Opportunistic DNS-Based
Authentication of Named Entities (DANE) Transport Layer Security (TLS)
Publication Date : October 2015
Author(s) : V. Dukhovni, W. Hardaker
Category : PROPOSED STANDARD
Source : DNS-based Authentication of Named Entities
Area : Security
Stream : IETF
Verifying Party : IESG
_______________________________________________
dane mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/dane
