rfc7601v2.txt		rfc7601.txt
	skipping to change at page 2, line 26		skipping to change at page 2, line 26
	1.5.4. Other Terms . . . . . . . . . . . . . . . . . . . . . 8		1.5.4. Other Terms . . . . . . . . . . . . . . . . . . . . . 8
	1.6. Trust Environment . . . . . . . . . . . . . . . . . . . . 8		1.6. Trust Environment . . . . . . . . . . . . . . . . . . . . 8
	2. Definition and Format of the Header Field . . . . . . . . . . 9		2. Definition and Format of the Header Field . . . . . . . . . . 9
	2.1. General Description . . . . . . . . . . . . . . . . . . . 9		2.1. General Description . . . . . . . . . . . . . . . . . . . 9
	2.2. Formal Definition . . . . . . . . . . . . . . . . . . . . 10		2.2. Formal Definition . . . . . . . . . . . . . . . . . . . . 10
	2.3. Property Types (ptypes) and Properties . . . . . . . . . 12		2.3. Property Types (ptypes) and Properties . . . . . . . . . 12
	2.4. The "policy" ptype . . . . . . . . . . . . . . . . . . . 13		2.4. The "policy" ptype . . . . . . . . . . . . . . . . . . . 13
	2.5. Authentication Identifier Field . . . . . . . . . . . . . 14		2.5. Authentication Identifier Field . . . . . . . . . . . . . 14
	2.6. Version Tokens . . . . . . . . . . . . . . . . . . . . . 15		2.6. Version Tokens . . . . . . . . . . . . . . . . . . . . . 15
	2.7. Defined Methods and Result Values . . . . . . . . . . . . 15		2.7. Defined Methods and Result Values . . . . . . . . . . . . 15
	2.7.1. DKIM and DomainKeys . . . . . . . . . . . . . . . . . 15		2.7.1. DKIM and DomainKeys . . . . . . . . . . . . . . . . . 16
	2.7.2. SPF and Sender ID . . . . . . . . . . . . . . . . . . 17		2.7.2. SPF and Sender ID . . . . . . . . . . . . . . . . . . 18
	2.7.3. "iprev" . . . . . . . . . . . . . . . . . . . . . . . 18		2.7.3. "iprev" . . . . . . . . . . . . . . . . . . . . . . . 19
	2.7.4. SMTP AUTH . . . . . . . . . . . . . . . . . . . . . . 19		2.7.4. SMTP AUTH . . . . . . . . . . . . . . . . . . . . . . 20
	2.7.5. Other Registered Codes . . . . . . . . . . . . . . . 20		2.7.5. Other Registered Codes . . . . . . . . . . . . . . . 21
	2.7.6. Extension Methods . . . . . . . . . . . . . . . . . . 20		2.7.6. Extension Methods . . . . . . . . . . . . . . . . . . 21
	2.7.7. Extension Result Codes . . . . . . . . . . . . . . . 21		2.7.7. Extension Result Codes . . . . . . . . . . . . . . . 22
	3. The "iprev" Authentication Method . . . . . . . . . . . . . . 22		3. The "iprev" Authentication Method . . . . . . . . . . . . . . 22
	4. Adding the Header Field to a Message . . . . . . . . . . . . 23		4. Adding the Header Field to a Message . . . . . . . . . . . . 23
	4.1. Header Field Position and Interpretation . . . . . . . . 24		4.1. Header Field Position and Interpretation . . . . . . . . 25
	4.2. Local Policy Enforcement . . . . . . . . . . . . . . . . 25		4.2. Local Policy Enforcement . . . . . . . . . . . . . . . . 26
	5. Removing Existing Header Fields . . . . . . . . . . . . . . . 26		5. Removing Existing Header Fields . . . . . . . . . . . . . . . 26
	6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 27		6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 27
	6.1. The Authentication-Results Header Field . . . . . . . . . 27		6.1. The Authentication-Results Header Field . . . . . . . . . 27
	6.2. "Email Authentication Methods" Registry Description . . . 27		6.2. "Email Authentication Methods" Registry Description . . . 28
	6.3. "Email Authentication Methods" Registry Update . . . . . 28		6.3. "Email Authentication Methods" Registry Update . . . . . 29
	6.4. "Email Authentication Property Types" Registry . . . . . 30		6.4. "Email Authentication Property Types" Registry . . . . . 30
	6.5. "Email Authentication Result Names" Description . . . . . 30		6.5. "Email Authentication Result Names" Description . . . . . 31
	6.6. "Email Authentication Result Names" Update . . . . . . . 31		6.6. "Email Authentication Result Names" Update . . . . . . . 32
	6.7. SMTP Enhanced Status Codes . . . . . . . . . . . . . . . 32		6.7. SMTP Enhanced Status Codes . . . . . . . . . . . . . . . 33
	7. Security Considerations . . . . . . . . . . . . . . . . . . . 32		7. Security Considerations . . . . . . . . . . . . . . . . . . . 33
	7.1. Forged Header Fields . . . . . . . . . . . . . . . . . . 32		7.1. Forged Header Fields . . . . . . . . . . . . . . . . . . 33
	7.2. Misleading Results . . . . . . . . . . . . . . . . . . . 34		7.2. Misleading Results . . . . . . . . . . . . . . . . . . . 35
	7.3. Header Field Position . . . . . . . . . . . . . . . . . . 34		7.3. Header Field Position . . . . . . . . . . . . . . . . . . 35
	7.4. Reverse IP Query Denial-of-Service Attacks . . . . . . . 35		7.4. Reverse IP Query Denial-of-Service Attacks . . . . . . . 35
	7.5. Mitigation of Backscatter . . . . . . . . . . . . . . . . 35		7.5. Mitigation of Backscatter . . . . . . . . . . . . . . . . 36
	7.6. Internal MTA Lists . . . . . . . . . . . . . . . . . . . 35		7.6. Internal MTA Lists . . . . . . . . . . . . . . . . . . . 36
	7.7. Attacks against Authentication Methods . . . . . . . . . 35		7.7. Attacks against Authentication Methods . . . . . . . . . 36
	7.8. Intentionally Malformed Header Fields . . . . . . . . . . 35		7.8. Intentionally Malformed Header Fields . . . . . . . . . . 36
	7.9. Compromised Internal Hosts . . . . . . . . . . . . . . . 36		7.9. Compromised Internal Hosts . . . . . . . . . . . . . . . 36
	7.10. Encapsulated Instances . . . . . . . . . . . . . . . . . 36		7.10. Encapsulated Instances . . . . . . . . . . . . . . . . . 37
	7.11. Reverse Mapping . . . . . . . . . . . . . . . . . . . . . 36		7.11. Reverse Mapping . . . . . . . . . . . . . . . . . . . . . 37
	8. References . . . . . . . . . . . . . . . . . . . . . . . . . 36		8. References . . . . . . . . . . . . . . . . . . . . . . . . . 37
	8.1. Normative References . . . . . . . . . . . . . . . . . . 37		8.1. Normative References . . . . . . . . . . . . . . . . . . 37
	8.2. Informative References . . . . . . . . . . . . . . . . . 37		8.2. Informative References . . . . . . . . . . . . . . . . . 38
	Appendix A. Legacy MUAs . . . . . . . . . . . . . . . . . . . . 40		Appendix A. Legacy MUAs . . . . . . . . . . . . . . . . . . . . 42
	Appendix B. Authentication-Results Examples . . . . . . . . . . 41		Appendix B. Authentication-Results Examples . . . . . . . . . . 42
	B.1. Trivial Case; Header Field Not Present . . . . . . . . . 41		B.1. Trivial Case; Header Field Not Present . . . . . . . . . 42
	B.2. Nearly Trivial Case; Service Provided, but No		B.2. Nearly Trivial Case; Service Provided, but No
	Authentication Done . . . . . . . . . . . . . . . . . . . 41		Authentication Done . . . . . . . . . . . . . . . . . . . 43
	B.3. Service Provided, Authentication Done . . . . . . . . . . 42		B.3. Service Provided, Authentication Done . . . . . . . . . . 44
	B.4. Service Provided, Several Authentications Done, Single		B.4. Service Provided, Several Authentications Done, Single
	MTA . . . . . . . . . . . . . . . . . . . . . . . . . . . 43		MTA . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
	B.5. Service Provided, Several Authentications Done, Different		B.5. Service Provided, Several Authentications Done, Different
	MTAs . . . . . . . . . . . . . . . . . . . . . . . . . . 44		MTAs . . . . . . . . . . . . . . . . . . . . . . . . . . 46
	B.6. Service Provided, Multi-tiered Authentication Done . . . 45		B.6. Service Provided, Multi-tiered Authentication Done . . . 48
	B.7. Comment-Heavy Example . . . . . . . . . . . . . . . . . . 47		B.7. Comment-Heavy Example . . . . . . . . . . . . . . . . . . 49
	Appendix C. Operational Considerations about Message		Appendix C. Operational Considerations about Message
	Authentication . . . . . . . . . . . . . . . . . . . 48		Authentication . . . . . . . . . . . . . . . . . . . 50
	Appendix D. Changes since RFC 7001 . . . . . . . . . . . . . . . 49		Appendix D. Changes since RFC 7001 . . . . . . . . . . . . . . . 51
	Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . . 51		Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . . 53
	Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 51		Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 53
	1. Introduction		1. Introduction
	This document describes a header field called Authentication-Results		This document describes a header field called Authentication-Results
	for electronic mail messages that presents the results of a message		for electronic mail messages that presents the results of a message
	authentication effort in a machine-readable format. The intent of		authentication effort in a machine-readable format. The intent of
	the header field is to create a place to collect such data when		the header field is to create a place to collect such data when
	message authentication mechanisms are in use so that a Mail User		message authentication mechanisms are in use so that a Mail User
	Agent (MUA) and downstream filters can make filtering decisions and/		Agent (MUA) and downstream filters can make filtering decisions and/
	or provide a recommendation to the user as to the validity of the		or provide a recommendation to the user as to the validity of the
	skipping to change at page 32, line 12		skipping to change at page 32, line 42
	"auth", and "iprev" methods have had their "Specification" fields		"auth", and "iprev" methods have had their "Specification" fields
	replaced as follows:		replaced as follows:
	dkim: Section 2.7.1 of this document (RFC 7601)		dkim: Section 2.7.1 of this document (RFC 7601)
	domainkeys: Section 2.7.1 of this document (RFC 7601)		domainkeys: Section 2.7.1 of this document (RFC 7601)
	spf: for "hardfail", Section 2.4.2 of [RFC5451]; for all others,		spf: for "hardfail", Section 2.4.2 of [RFC5451]; for all others,
	Section 2.7.2 of this document (RFC 7601)		Section 2.7.2 of this document (RFC 7601)
	sender-id: for "hardfail", Section 2.4.2 of [RFC5451] ; for all		sender-id: for "hardfail", Section 2.4.2 of [RFC5451]; for all
	others, Section 2.7.2 of this document (RFC 7601)		others, Section 2.7.2 of this document (RFC 7601)
	auth: Section 2.7.4 of this document (RFC 7601)		auth: Section 2.7.4 of this document (RFC 7601)
	iprev: Section 2.7.3 of this document (RFC 7601)		iprev: Section 2.7.3 of this document (RFC 7601)
	o All entries for "dkim-adsp" that were missing an explicit		o All entries for "dkim-adsp" that were missing an explicit
	reference to a defining document now reference [ADSP] in their		reference to a defining document now reference [ADSP] in their
	"Specification" fields.		"Specification" fields.
	skipping to change at page 37, line 4		skipping to change at page 37, line 31
	7.11. Reverse Mapping		7.11. Reverse Mapping
	Although Section 3 of this memo includes explicit support for the		Although Section 3 of this memo includes explicit support for the
	"iprev" method, its value as an authentication mechanism is limited.		"iprev" method, its value as an authentication mechanism is limited.
	Implementers of both this proposal and agents that use the data it		Implementers of both this proposal and agents that use the data it
	relays are encouraged to become familiar with the issues raised by		relays are encouraged to become familiar with the issues raised by
	[DNSOP-REVERSE] when deciding whether or not to include support for		[DNSOP-REVERSE] when deciding whether or not to include support for
	"iprev".		"iprev".
	8. References		8. References
	8.1. Normative References		8.1. Normative References
	[ABNF] Crocker, D., Ed. and P. Overell, "Augmented BNF for Syntax		[ABNF] Crocker, D., Ed. and P. Overell, "Augmented BNF for Syntax
	Specifications: ABNF", STD 68, RFC 5234, DOI 10.17487/		Specifications: ABNF", STD 68, RFC 5234,
	RFC5234, January 2008,		DOI 10.17487/RFC5234, January 2008,
	<http://www.rfc-editor.org/info/rfc5234>.		<http://www.rfc-editor.org/info/rfc5234>.
	[IANA-HEADERS]		[IANA-HEADERS]
	Klyne, G., Nottingham, M., and J. Mogul, "Registration		Klyne, G., Nottingham, M., and J. Mogul, "Registration
	Procedures for Message Header Fields", BCP 90, RFC 3864,		Procedures for Message Header Fields", BCP 90, RFC 3864,
	DOI 10.17487/RFC3864, September 2004,		DOI 10.17487/RFC3864, September 2004,
	<http://www.rfc-editor.org/info/rfc3864>.		<http://www.rfc-editor.org/info/rfc3864>.
	[KEYWORDS]		[KEYWORDS]
	Bradner, S., "Key words for use in RFCs to Indicate		Bradner, S., "Key words for use in RFCs to Indicate
	Requirement Levels", BCP 14, RFC 2119, DOI 10.17487/		Requirement Levels", BCP 14, RFC 2119,
	RFC2119, March 1997,		DOI 10.17487/RFC2119, March 1997,
	<http://www.rfc-editor.org/info/rfc2119>.		<http://www.rfc-editor.org/info/rfc2119>.
	[MAIL] Resnick, P., Ed., "Internet Message Format", RFC 5322, DOI		[MAIL] Resnick, P., Ed., "Internet Message Format", RFC 5322,
	10.17487/RFC5322, October 2008,		DOI 10.17487/RFC5322, October 2008,
	<http://www.rfc-editor.org/info/rfc5322>.		<http://www.rfc-editor.org/info/rfc5322>.
	[MIME] Freed, N. and N. Borenstein, "Multipurpose Internet Mail		[MIME] Freed, N. and N. Borenstein, "Multipurpose Internet Mail
	Extensions (MIME) Part One: Format of Internet Message		Extensions (MIME) Part One: Format of Internet Message
	Bodies", RFC 2045, DOI 10.17487/RFC2045, November 1996,		Bodies", RFC 2045, DOI 10.17487/RFC2045, November 1996,
	<http://www.rfc-editor.org/info/rfc2045>.		<http://www.rfc-editor.org/info/rfc2045>.
	[SMTP] Klensin, J., "Simple Mail Transfer Protocol", RFC 5321,		[SMTP] Klensin, J., "Simple Mail Transfer Protocol", RFC 5321,
	DOI 10.17487/RFC5321, October 2008,		DOI 10.17487/RFC5321, October 2008,
	<http://www.rfc-editor.org/info/rfc5321>.		<http://www.rfc-editor.org/info/rfc5321>.
	8.2. Informative References		8.2. Informative References
	[ADSP] Allman, E., Fenton, J., Delany, M., and J. Levine,		[ADSP] Allman, E., Fenton, J., Delany, M., and J. Levine,
	"DomainKeys Identified Mail (DKIM) Author Domain Signing		"DomainKeys Identified Mail (DKIM) Author Domain Signing
	Practices (ADSP)", RFC 5617, DOI 10.17487/RFC5617, August		Practices (ADSP)", RFC 5617, DOI 10.17487/RFC5617, August
	2009, <http://www.rfc-editor.org/info/rfc5617>.		2009, <http://www.rfc-editor.org/info/rfc5617>.
	[AR-VBR] Kucherawy, M., "Authentication-Results Registration for		[AR-VBR] Kucherawy, M., "Authentication-Results Registration for
	Vouch by Reference Results", RFC 6212, DOI 10.17487/		Vouch by Reference Results", RFC 6212,
	RFC6212, April 2011,		DOI 10.17487/RFC6212, April 2011,
	<http://www.rfc-editor.org/info/rfc6212>.		<http://www.rfc-editor.org/info/rfc6212>.
	[ATPS] Kucherawy, M., "DomainKeys Identified Mail (DKIM)		[ATPS] Kucherawy, M., "DomainKeys Identified Mail (DKIM)
	Authorized Third-Party Signatures", RFC 6541, DOI		Authorized Third-Party Signatures", RFC 6541,
	10.17487/RFC6541, February 2012,		DOI 10.17487/RFC6541, February 2012,
	<http://www.rfc-editor.org/info/rfc6541>.		<http://www.rfc-editor.org/info/rfc6541>.
	[AUTH] Siemborski, R., Ed. and A. Melnikov, Ed., "SMTP Service		[AUTH] Siemborski, R., Ed. and A. Melnikov, Ed., "SMTP Service
	Extension for Authentication", RFC 4954, DOI 10.17487/		Extension for Authentication", RFC 4954,
	RFC4954, July 2007,		DOI 10.17487/RFC4954, July 2007,
	<http://www.rfc-editor.org/info/rfc4954>.		<http://www.rfc-editor.org/info/rfc4954>.
	[AUTH-ESC]		[AUTH-ESC]
	Kucherawy, M., "Email Authentication Status Codes", RFC		Kucherawy, M., "Email Authentication Status Codes",
	7372, DOI 10.17487/RFC7372, September 2014,		RFC 7372, DOI 10.17487/RFC7372, September 2014,
	<http://www.rfc-editor.org/info/rfc7372>.		<http://www.rfc-editor.org/info/rfc7372>.
	[DKIM] Crocker, D., Ed., Hansen, T., Ed., and M. Kucherawy, Ed.,		[DKIM] Crocker, D., Ed., Hansen, T., Ed., and M. Kucherawy, Ed.,
	"DomainKeys Identified Mail (DKIM) Signatures", STD 76,		"DomainKeys Identified Mail (DKIM) Signatures", STD 76,
	RFC 6376, DOI 10.17487/RFC6376, September 2011,		RFC 6376, DOI 10.17487/RFC6376, September 2011,
	<http://www.rfc-editor.org/info/rfc6376>.		<http://www.rfc-editor.org/info/rfc6376>.
	[DMARC] Kucherawy, M., Ed. and E. Zwicky, Ed., "Domain-based		[DMARC] Kucherawy, M., Ed. and E. Zwicky, Ed., "Domain-based
	Message Authentication, Reporting, and Conformance		Message Authentication, Reporting, and Conformance
	(DMARC)", RFC 7489, DOI 10.17487/RFC7489, March 2015,		(DMARC)", RFC 7489, DOI 10.17487/RFC7489, March 2015,
	<http://www.rfc-editor.org/info/rfc7489>.		<http://www.rfc-editor.org/info/rfc7489>.
	[DNS] Mockapetris, P., "Domain names - implementation and		[DNS] Mockapetris, P., "Domain names - implementation and
	specification", STD 13, RFC 1035, DOI 10.17487/RFC1035,		specification", STD 13, RFC 1035, DOI 10.17487/RFC1035,
	November 1987, <http://www.rfc-editor.org/info/rfc1035>.		November 1987, <http://www.rfc-editor.org/info/rfc1035>.
	[DNS-IP6] Thomson, S., Huitema, C., Ksinant, V., and M. Souissi,		[DNS-IP6] Thomson, S., Huitema, C., Ksinant, V., and M. Souissi,
	"DNS Extensions to Support IP Version 6", RFC 3596, DOI		"DNS Extensions to Support IP Version 6", RFC 3596,
	10.17487/RFC3596, October 2003,		DOI 10.17487/RFC3596, October 2003,
	<http://www.rfc-editor.org/info/rfc3596>.		<http://www.rfc-editor.org/info/rfc3596>.
	[DNSOP-REVERSE]		[DNSOP-REVERSE]
	Senie, D. and A. Sullivan, "Considerations for the use of		Senie, D. and A. Sullivan, "Considerations for the use of
	DNS Reverse Mapping", Work in Progress, draft-ietf-dnsop-		DNS Reverse Mapping", Work in Progress, draft-ietf-dnsop-
	reverse-mapping-considerations-06, March 2008.		reverse-mapping-considerations-06, March 2008.
	[DOMAINKEYS]		[DOMAINKEYS]
	Delany, M., "Domain-Based Email Authentication Using		Delany, M., "Domain-Based Email Authentication Using
	Public Keys Advertised in the DNS (DomainKeys)", RFC 4870,		Public Keys Advertised in the DNS (DomainKeys)", RFC 4870,
	DOI 10.17487/RFC4870, May 2007,		DOI 10.17487/RFC4870, May 2007,
	<http://www.rfc-editor.org/info/rfc4870>.		<http://www.rfc-editor.org/info/rfc4870>.
	[DSN] Moore, K. and G. Vaudreuil, "An Extensible Message Format		[DSN] Moore, K. and G. Vaudreuil, "An Extensible Message Format
	for Delivery Status Notifications", RFC 3464, DOI		for Delivery Status Notifications", RFC 3464,
	10.17487/RFC3464, January 2003,		DOI 10.17487/RFC3464, January 2003,
	<http://www.rfc-editor.org/info/rfc3464>.		<http://www.rfc-editor.org/info/rfc3464>.
	[EMAIL-ARCH]		[EMAIL-ARCH]
	Crocker, D., "Internet Mail Architecture", RFC 5598, DOI		Crocker, D., "Internet Mail Architecture", RFC 5598,
	10.17487/RFC5598, July 2009,		DOI 10.17487/RFC5598, July 2009,
	<http://www.rfc-editor.org/info/rfc5598>.		<http://www.rfc-editor.org/info/rfc5598>.
	[IANA-CONSIDERATIONS]		[IANA-CONSIDERATIONS]
	Narten, T. and H. Alvestrand, "Guidelines for Writing an		Narten, T. and H. Alvestrand, "Guidelines for Writing an
	IANA Considerations Section in RFCs", BCP 26, RFC 5226,		IANA Considerations Section in RFCs", BCP 26, RFC 5226,
	DOI 10.17487/RFC5226, May 2008,		DOI 10.17487/RFC5226, May 2008,
	<http://www.rfc-editor.org/info/rfc5226>.		<http://www.rfc-editor.org/info/rfc5226>.
	[IMAP] Crispin, M., "INTERNET MESSAGE ACCESS PROTOCOL - VERSION		[IMAP] Crispin, M., "INTERNET MESSAGE ACCESS PROTOCOL - VERSION
	4rev1", RFC 3501, DOI 10.17487/RFC3501, March 2003,		4rev1", RFC 3501, DOI 10.17487/RFC3501, March 2003,
	skipping to change at page 39, line 29		skipping to change at page 40, line 10
	[POP3] Myers, J. and M. Rose, "Post Office Protocol - Version 3",		[POP3] Myers, J. and M. Rose, "Post Office Protocol - Version 3",
	STD 53, RFC 1939, DOI 10.17487/RFC1939, May 1996,		STD 53, RFC 1939, DOI 10.17487/RFC1939, May 1996,
	<http://www.rfc-editor.org/info/rfc1939>.		<http://www.rfc-editor.org/info/rfc1939>.
	[PRA] Lyon, J., "Purported Responsible Address in E-Mail		[PRA] Lyon, J., "Purported Responsible Address in E-Mail
	Messages", RFC 4407, DOI 10.17487/RFC4407, April 2006,		Messages", RFC 4407, DOI 10.17487/RFC4407, April 2006,
	<http://www.rfc-editor.org/info/rfc4407>.		<http://www.rfc-editor.org/info/rfc4407>.
	[RFC5451] Kucherawy, M., "Message Header Field for Indicating		[RFC5451] Kucherawy, M., "Message Header Field for Indicating
	Message Authentication Status", RFC 5451, DOI 10.17487/		Message Authentication Status", RFC 5451,
	RFC5451, April 2009,		DOI 10.17487/RFC5451, April 2009,
	<http://www.rfc-editor.org/info/rfc5451>.		<http://www.rfc-editor.org/info/rfc5451>.
	[RFC6008] Kucherawy, M., "Authentication-Results Registration for		[RFC6008] Kucherawy, M., "Authentication-Results Registration for
	Differentiating among Cryptographic Results", RFC 6008,		Differentiating among Cryptographic Results", RFC 6008,
	DOI 10.17487/RFC6008, September 2010,		DOI 10.17487/RFC6008, September 2010,
	<http://www.rfc-editor.org/info/rfc6008>.		<http://www.rfc-editor.org/info/rfc6008>.
	[RFC6577] Kucherawy, M., "Authentication-Results Registration Update		[RFC6577] Kucherawy, M., "Authentication-Results Registration Update
	for Sender Policy Framework (SPF) Results", RFC 6577, DOI		for Sender Policy Framework (SPF) Results", RFC 6577,
	10.17487/RFC6577, March 2012,		DOI 10.17487/RFC6577, March 2012,
	<http://www.rfc-editor.org/info/rfc6577>.		<http://www.rfc-editor.org/info/rfc6577>.
	[RFC7001] Kucherawy, M., "Message Header Field for Indicating		[RFC7001] Kucherawy, M., "Message Header Field for Indicating
	Message Authentication Status", RFC 7001, DOI 10.17487/		Message Authentication Status", RFC 7001,
	RFC7001, September 2013,		DOI 10.17487/RFC7001, September 2013,
	<http://www.rfc-editor.org/info/rfc7001>.		<http://www.rfc-editor.org/info/rfc7001>.
	[RFC7410] Kucherawy, M., "A Property Types Registry for the		[RFC7410] Kucherawy, M., "A Property Types Registry for the
	Authentication-Results Header Field", RFC 7410, DOI		Authentication-Results Header Field", RFC 7410,
	10.17487/RFC7410, December 2014,		DOI 10.17487/RFC7410, December 2014,
	<http://www.rfc-editor.org/info/rfc7410>.		<http://www.rfc-editor.org/info/rfc7410>.
	[RRVS] Mills, W. and M. Kucherawy, "The Require-Recipient-Valid-		[RRVS] Mills, W. and M. Kucherawy, "The Require-Recipient-Valid-
	Since Header Field and SMTP Service Extension", RFC 7293,		Since Header Field and SMTP Service Extension", RFC 7293,
	DOI 10.17487/RFC7293, July 2014,		DOI 10.17487/RFC7293, July 2014,
	<http://www.rfc-editor.org/info/rfc7293>.		<http://www.rfc-editor.org/info/rfc7293>.
	[SECURITY]		[SECURITY]
	Rescorla, E. and B. Korver, "Guidelines for Writing RFC		Rescorla, E. and B. Korver, "Guidelines for Writing RFC
	Text on Security Considerations", BCP 72, RFC 3552, DOI		Text on Security Considerations", BCP 72, RFC 3552,
	10.17487/RFC3552, July 2003,		DOI 10.17487/RFC3552, July 2003,
	<http://www.rfc-editor.org/info/rfc3552>.		<http://www.rfc-editor.org/info/rfc3552>.
	[SENDERID]		[SENDERID]
	Lyon, J. and M. Wong, "Sender ID: Authenticating E-Mail",		Lyon, J. and M. Wong, "Sender ID: Authenticating E-Mail",
	RFC 4406, DOI 10.17487/RFC4406, April 2006,		RFC 4406, DOI 10.17487/RFC4406, April 2006,
	<http://www.rfc-editor.org/info/rfc4406>.		<http://www.rfc-editor.org/info/rfc4406>.
	[SMIME-REG]		[SMIME-REG]
	Melnikov, A., "Authentication-Results Registration for S/		Melnikov, A., "Authentication-Results Registration for S/
	MIME Signature Verification", RFC 7281, DOI 10.17487/		MIME Signature Verification", RFC 7281,
	RFC7281, June 2014,		DOI 10.17487/RFC7281, June 2014,
	<http://www.rfc-editor.org/info/rfc7281>.		<http://www.rfc-editor.org/info/rfc7281>.
	[SPF] Kitterman, S., "Sender Policy Framework (SPF) for		[SPF] Kitterman, S., "Sender Policy Framework (SPF) for
	Authorizing Use of Domains in Email, Version 1", RFC 7208,		Authorizing Use of Domains in Email, Version 1", RFC 7208,
	DOI 10.17487/RFC7208, April 2014,		DOI 10.17487/RFC7208, April 2014,
	<http://www.rfc-editor.org/info/rfc7208>.		<http://www.rfc-editor.org/info/rfc7208>.
	[VBR] Hoffman, P., Levine, J., and A. Hathcock, "Vouch By		[VBR] Hoffman, P., Levine, J., and A. Hathcock, "Vouch By
	Reference", RFC 5518, DOI 10.17487/RFC5518, April 2009,		Reference", RFC 5518, DOI 10.17487/RFC5518, April 2009,
	<http://www.rfc-editor.org/info/rfc5518>.		<http://www.rfc-editor.org/info/rfc5518>.
End of changes. 29 change blocks.
	72 lines changed or deleted		73 lines changed or added
This html diff was produced by rfcdiff 1.41. The latest version is available from http://tools.ietf.org/tools/rfcdiff/