mrisher/smtp-sts

Sabrina comments

Closed this issue · 0 comments

IESG/Authors/WG Chairs:

The IANA Services Operator has completed its review of draft-ietf-uta-smtp-tlsrpt-17. If any part of this review is inaccurate, please let us know.

The IANA Services Operator has a question about one of the actions requested in the IANA Considerations section of this document.

The IANA Services Operator understands that, upon approval of this document, there are five actions which we must complete.

First, in the Permanent Message Header Field Names registry on the Message Headers registry page located at:

https://www.iana.org/assignments/message-headers/

two new registrations will be made as follows:

Header Field Name: TLS-Report-Domain
Template:
Protocol: mail
Status: standard
Reference: [ RFC-to-be ]

Header Field Name: TLS-Report-Submitter
Template:
Protocol: mail
Status: standard
Reference: [ RFC-to-be ]

As this document requests registrations in an Expert Review (see RFC 8126) registry, we will initiate the required Expert Review via a separate request. Expert review will need to be completed before your document can be approved for publication as an RFC.

IANA Question --> Is the Template field for these registrations to be blank (i.e. no template)?

Second, section 6.2 of the current document makes this request:

"This document registers a new parameter "report-type="tlsrpt"" under "multipart/report" top-level media type for use with [RFC6522]. The media type suitable for use as a report-type is defined in the following section."

IANA Question --> In what registry should this registration be made? In the MIME Media Type Sub-Parameter Registries there is no sub-parameter registry for multipart/report media type. And, IANA has made no new registrations as a result of RFC 6522.

Third, in the application registry on the Media Types registry page located at:

https://www.iana.org/assignments/media-types/

the following registration will be made:

Name: tlsrpt+json
Template: [ TBD-at-Registration ]
Reference: [ RFC-to-be ]

Fourth, also in the application registry on the Media Types registry page located at:

https://www.iana.org/assignments/media-types/

the following registration will be made:

Name: tlsrpt+gzip
Template: [ TBD-at-Registration ]
Reference: [ RFC-to-be ]

Fourth, a new registry is to be created called the STARTTLS Validation Result Types. The new registry will be managed via Expert Review as defined in RFC 8126.

IANA Question --> Where should this new registry be located? Should it be added to an existing registry page? If not, does it belong in an existing category at http://www.iana.org/protocols?

There are initial registrations in the new registry as follows:

+-------------------------------+---------------+
| Result Type | Reference |
+-------------------------------+---------------+
| "starttls-not-supported" | [ RFC-to-be ] | "certificate-host-mismatch"
| | [ RFC-to-be ] | "certificate-expired" | [ RFC-to-be ] |
| "tlsa-invalid" | [ RFC-to-be ] | "dnssec-invalid" | [ RFC-to-be ] |
| "dane-required" | [ RFC-to-be ] | "certificate-not-trusted" | [
| RFC-to-be ] | "sts-policy-invalid" | [ RFC-to-be ] |
| "sts-webpki-invalid" | [ RFC-to-be ] | "validation-failure" | [
| RFC-to-be ] |
+-------------------------------+---------------+

IANA Question --> are the quotation marks to remain around each text string in the Result Type field?

The IANA Services Operator understands that these are the only actions required to be completed upon approval of this document.

Note: The actions requested in this document will not be completed until the document has been approved for publication as an RFC. This message is meant only to confirm the list of actions that will be performed.