I suspect that this errata should be rejected.  RFC 6125 was published months 
after RFC 6066 and that makes this addition feel “new" to me and as such it’s 
inappropriate to change through the errata process; see [1].

spt

[1] 
https://datatracker.ietf.org/doc/statement-iesg-iesg-processing-of-rfc-errata-for-the-ietf-stream-20210507/

> On Mar 15, 2019, at 05:35, RFC Errata System <rfc-edi...@rfc-editor.org> 
> wrote:
> 
> The following errata report has been submitted for RFC6066,
> "Transport Layer Security (TLS) Extensions: Extension Definitions".
> 
> --------------------------------------
> You may review the report below and at:
> http://www.rfc-editor.org/errata/eid5658
> 
> --------------------------------------
> Type: Technical
> Reported by: Owen Friel <ofr...@cisco.com>
> 
> Section: 3
> 
> Original Text
> -------------
> 
> 
> Corrected Text
> --------------
> When a client uses DNS SRV to discover and connect to a server, the 
> client SHOULD include the "source domain" in the "host_name" and SHOULD
> NOT include the "derived domain", where "source domain" and "derived
> domain" are defined in RFC6125. 
> 
> Notes
> -----
> The original text is all fine, but it is missing some additional clarifying 
> text on use of SNI when a client users DNS SRV to discover the service it is 
> connecting to.
> 
> 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. 
> 
> --------------------------------------
> RFC6066 (draft-ietf-tls-rfc4366-bis-12)
> --------------------------------------
> Title               : Transport Layer Security (TLS) Extensions: Extension 
> Definitions
> Publication Date    : January 2011
> Author(s)           : D. Eastlake 3rd
> Category            : PROPOSED STANDARD
> Source              : Transport Layer Security
> Area                : Security
> Stream              : IETF
> Verifying Party     : IESG

_______________________________________________
TLS mailing list
TLS@ietf.org
https://www.ietf.org/mailman/listinfo/tls

Reply via email to