Hi Sabrina, Received.
Thank you! Sarah Tarrant RFC Production Center > On Aug 3, 2026, at 11:08 AM, Sabrina Tanamal via RT > <[email protected]> wrote: > > RFC Editor: > > We've completed the actions for the following RFC-to-be: > > draft-ietf-dnsop-structured-dns-error-27 > > ACTION 1: > > We've added the following entry to the DNS EDNS0 Option Codes (OPT) registry: > > 26 Structured DNS Error Standard [RFC-ietf-dnsop-structured-dns-error-27] > > Please see > https://www.iana.org/assignments/dns-parameters > > ACTION 2: > > We've created the following registries and placed them under the "Domain Name > System (DNS) Parameters" registry group: > > EXTRA-TEXT JSON Names > Registration Procedure(s): IETF Review > Reference: [RFC-ietf-dnsop-structured-dns-error-27] > > JSON Name Field Meaning Description Reference > c contact The contact details of the IT/InfoSec team to report misclassified > DNS filtering [RFC-ietf-dnsop-structured-dns-error-27, Section 4] > j justification UTF-8-encoded [RFC5198] textual justification for a > particular DNS filtering [RFC-ietf-dnsop-structured-dns-error-27, Section 4] > s sub-error Integer representing the sub-error code for this DNS filtering > case [RFC-ietf-dnsop-structured-dns-error-27, Section 4] > o organization UTF-8-encoded human-friendly name of the organization that > filtered this particular DNS query [RFC-ietf-dnsop-structured-dns-error-27, > Section 4] > l language Indicates the language of the "j" and "o" fields as defined in > [RFC5646] [RFC-ietf-dnsop-structured-dns-error-27, Section 4] > > Contact URI Schemes > Registration Procedure(s): IETF Review > Reference: [RFC-ietf-dnsop-structured-dns-error-27] > > Name Meaning Reference > tel Telephone Number [RFC3966] > mailto Internet mail [RFC6068] > > Extended DNS Sub-Error Codes > Registration Procedure(s): IETF Review > Reference: [RFC-ietf-dnsop-structured-dns-error-27] > > Number Meaning EDE Codes Applicability Reference > 0 Reserved Not used [RFC-ietf-dnsop-structured-dns-error-27, Section 6.1] > 1 Malware "Blocked", "Blocked by Upstream DNS Server", "Filtered" [RFC5901, > Section 5.5] > 2 Phishing "Blocked", "Blocked by Upstream DNS Server", "Filtered" [RFC5901, > Section 5.5] > 3 Spam "Blocked", "Blocked by Upstream DNS Server", "Filtered" [RFC4949] > 4 Spyware "Blocked", "Blocked by Upstream DNS Server", "Filtered" [RFC4949] > 5 Network operator policy "Blocked" [RFC-ietf-dnsop-structured-dns-error-27, > Section 6.2] > 6 DNS operator policy "Blocked" [RFC-ietf-dnsop-structured-dns-error-27, > Section 6.3] > 7-255 Unassigned > > Please see > https://www.iana.org/assignments/dns-parameters > > ACTION 3: > > We've added the following entry to the Extended DNS Error Codes registry: > > 35 Blocked by Upstream DNS Server [RFC-ietf-dnsop-structured-dns-error-27] > > Please see > https://www.iana.org/assignments/dns-parameters > > Please let us know when an RFC number has been assigned and the date of > publication by sending a new message to <[email protected]>. > > Thanks, > > Sabrina Tanamal > IANA > -- auth48archive mailing list -- [email protected] To unsubscribe send an email to [email protected]
