draft-ietf-uta-smtp-tlsrpt-19.txt		draft-ietf-uta-smtp-tlsrpt-20.txt
	skipping to change at page 1, line 16 ¶		skipping to change at page 1, line 16 ¶
	Expires: November 3, 2018 Comcast, Inc		Expires: November 3, 2018 Comcast, Inc
	B. Ramakrishnan		B. Ramakrishnan
	Yahoo!, Inc		Yahoo!, Inc
	J. Jones		J. Jones
	Microsoft, Inc		Microsoft, Inc
	M. Risher		M. Risher
	Google, Inc		Google, Inc
	May 2, 2018		May 2, 2018
	SMTP TLS Reporting		SMTP TLS Reporting
	draft-ietf-uta-smtp-tlsrpt-19		draft-ietf-uta-smtp-tlsrpt-20
	Abstract		Abstract
	A number of protocols exist for establishing encrypted channels		A number of protocols exist for establishing encrypted channels
	between SMTP Mail Transfer Agents, including STARTTLS, DANE TLSA, and		between SMTP Mail Transfer Agents, including STARTTLS, DANE TLSA, and
	MTA-STS. These protocols can fail due to misconfiguration or active		MTA-STS. These protocols can fail due to misconfiguration or active
	attack, leading to undelivered messages or delivery over unencrypted		attack, leading to undelivered messages or delivery over unencrypted
	or unauthenticated channels. This document describes a reporting		or unauthenticated channels. This document describes a reporting
	mechanism and format by which sending systems can share statistics		mechanism and format by which sending systems can share statistics
	and specific information about potential failures with recipient		and specific information about potential failures with recipient
	skipping to change at page 13, line 46 ¶		skipping to change at page 13, line 46 ¶
	Part of the report body includes the policy that is applied when		Part of the report body includes the policy that is applied when
	attemping relay to the destination.		attemping relay to the destination.
	For DANE TLSA policies, this is a JSON array of strings each		For DANE TLSA policies, this is a JSON array of strings each
	representing the RDATA of a single TLSA resource record as a space-		representing the RDATA of a single TLSA resource record as a space-
	separated list of its four TLSA fields; the fields are in		separated list of its four TLSA fields; the fields are in
	presentation format (defined in [RFC6698] Section 2.2) with no		presentation format (defined in [RFC6698] Section 2.2) with no
	internal spaces or grouping parentheses:		internal spaces or grouping parentheses:
	[ "3 0 1		[
	1F850A337E6DB9C609C522D136A475638CC43E1ED424F8EEC8513D747D1D085D", "3		"3 0 1 1F850A337E6DB9C609C522D136A475638CC43E1ED424F8EEC8513D747D1D085D",
	0 1 12350A337E6DB9C6123522D136A475638CC43E1ED424F8EEC8513D747D1D1234"		"3 0 1 12350A337E6DB9C6123522D136A475638CC43E1ED424F8EEC8513D747D1D1234"
	]		]
	For MTA-STS policies, this is an array of JSON strings that		For MTA-STS policies, this is an array of JSON strings that
	represents the policy that is declared by the receiving site,		represents the policy that is declared by the receiving site,
	including any errors that may be present. Note that where there are		including any errors that may be present. Note that where there are
	multiple "mx" values, they must be listed as separate "mx" elements		multiple "mx" values, they must be listed as separate "mx" elements
	in the policy array, rather as a single nested "mx" sub-array.		in the policy array, rather as a single nested "mx" sub-array.
	[ "version: STSv1", "mode: report", "mx: mx1.example.com", "mx:		[
	mx2.example.com", "mx: mx.backup-example.com", "max_age: 12345678" ]		"version: STSv1",
			"mode: report",
			"mx: mx1.example.com",
			"mx: mx2.example.com",
			"mx: mx.backup-example.com",
			"max_age: 12345678"
			]
	5. Report Delivery		5. Report Delivery
	Reports can be delivered either as an email message via SMTP or via		Reports can be delivered either as an email message via SMTP or via
	HTTP POST.		HTTP POST.
	5.1. Report Filename		5.1. Report Filename
	The filename is RECOMMENDED to be constructed using the following		The filename is RECOMMENDED to be constructed using the following
	ABNF:		ABNF:
End of changes. 3 change blocks.
	7 lines changed or deleted		13 lines changed or added
This html diff was produced by rfcdiff 1.46. The latest version is available from http://tools.ietf.org/tools/rfcdiff/