idnits 2.17.1 draft-melnikov-authentication-results-smime-00.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (March 13, 2013) is 4059 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) ** Obsolete normative reference: RFC 3501 (Obsoleted by RFC 9051) ** Obsolete normative reference: RFC 5451 (Obsoleted by RFC 7001) ** Obsolete normative reference: RFC 5751 (Obsoleted by RFC 8551) Summary: 3 errors (**), 0 flaws (~~), 1 warning (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group A. Melnikov 3 Internet-Draft Isode Ltd 4 Intended status: Standards Track March 13, 2013 5 Expires: September 14, 2013 7 Authentication-Results Registration for S/MIME signature verification 8 draft-melnikov-authentication-results-smime-00 10 Abstract 12 RFC 5451 specifies the Authentication-Results header field for 13 conveying results of message authentication checks. This document 14 defines a new authentication method to be used in the Authentication- 15 Results header field for S/MIME related signature checks. 17 Status of This Memo 19 This Internet-Draft is submitted in full conformance with the 20 provisions of BCP 78 and BCP 79. 22 Internet-Drafts are working documents of the Internet Engineering 23 Task Force (IETF). Note that other groups may also distribute 24 working documents as Internet-Drafts. The list of current Internet- 25 Drafts is at http://datatracker.ietf.org/drafts/current/. 27 Internet-Drafts are draft documents valid for a maximum of six months 28 and may be updated, replaced, or obsoleted by other documents at any 29 time. It is inappropriate to use Internet-Drafts as reference 30 material or to cite them other than as "work in progress." 32 This Internet-Draft will expire on September 14, 2013. 34 Copyright Notice 36 Copyright (c) 2013 IETF Trust and the persons identified as the 37 document authors. All rights reserved. 39 This document is subject to BCP 78 and the IETF Trust's Legal 40 Provisions Relating to IETF Documents 41 (http://trustee.ietf.org/license-info) in effect on the date of 42 publication of this document. Please review these documents 43 carefully, as they describe your rights and restrictions with respect 44 to this document. Code Components extracted from this document must 45 include Simplified BSD License text as described in Section 4.e of 46 the Trust Legal Provisions and are provided without warranty as 47 described in the Simplified BSD License. 49 Table of Contents 51 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 52 2. Conventions Used in This Document . . . . . . . . . . . . . . 2 53 3. "smime" Authentication Method . . . . . . . . . . . . . . . . 2 54 3.1. S/MIME Results . . . . . . . . . . . . . . . . . . . . . 2 55 4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 3 56 5. Security Considerations . . . . . . . . . . . . . . . . . . . 4 57 6. Normative References . . . . . . . . . . . . . . . . . . . . 5 58 Appendix A. Acknowledgements . . . . . . . . . . . . . . . . . . 5 59 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 5 61 1. Introduction 63 [RFC5451] specifies the Authentication-Results header field for 64 conveying results of message authentication checks. This document 65 defines a new authentication method to be used in the Authentication- 66 Results header field for S/MIME related signature checks. 68 [[Explain in more details use cases, such as a border MTA performing 69 check and MUA showing results.]] 71 2. Conventions Used in This Document 73 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 74 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 75 document are to be interpreted as described in [RFC2119]. 77 The formal syntax uses the Augmented Backus-Naur Form (ABNF) 78 [RFC5234] notation including the core rules defined in Appendix B of 79 RFC 5234 [RFC5234]. 81 3. "smime" Authentication Method 83 3.1. S/MIME Results 85 The result values used by [RFC5751] are as follows: 87 +-------------+-----------------------------------------------------+ 88 | Result code | Meaning | 89 +-------------+-----------------------------------------------------+ 90 | none | The message was not signed. | 91 | | | 92 | pass | The message was signed, the signature or signatures | 93 | | were acceptable to the verifier, and the | 94 | | signature(s) passed verification tests. | 95 | | | 96 | fail | The message was signed and the signature or | 97 | | signatures were acceptable to the verifier, but | 98 | | they failed the verification test(s). | 99 | | | 100 | policy | The message was signed but the signature or | 101 | | signatures were not acceptable to the verifier. | 102 | | | 103 | neutral | The message was signed but the signature or | 104 | | signatures contained syntax errors or were not | 105 | | otherwise able to be processed. This result SHOULD | 106 | | also be used for other failures not covered | 107 | | elsewhere in this list. | 108 | | | 109 | temperror | The message could not be verified due to some error | 110 | | that is likely transient in nature, such as a | 111 | | temporary inability to retrieve a public key. A | 112 | | later attempt may produce a final result. | 113 | | | 114 | permerror | The message could not be verified due to some error | 115 | | that is unrecoverable, such as a required header | 116 | | field being absent. A later attempt is unlikely to | 117 | | produce a final result. | 118 +-------------+-----------------------------------------------------+ 120 A signature is "acceptable to the verifier" if it passes local policy 121 checks (or there are no specific local policy checks). For example, 122 a verifier might require that the signature(s) on the message be 123 added using the DNS domain present in the From: header field of the 124 message, thus making third-party signatures unacceptable. [RFC5751] 125 advises that if a message fails verification, it should be treated as 126 an unsigned message. A report of "fail" here permits the receiver of 127 the report to decide how to handle the failure. A report of 128 "neutral" or "none" preempts that choice, ensuring the message will 129 be treated as if it had not been signed. 131 4. IANA Considerations 133 IANA is requested to add the the following entries to the "Email 134 Authentication Methods" subregistry of the "Email Authentication 135 Parameters" registry: 137 +--------+-----------+--------+------------------+------------------+ 138 | Method | Defined | ptype | property | value | 139 +--------+-----------+--------+------------------+------------------+ 140 | smime | [RFC5751] | body | smime-part | The MIME body | 141 | | | | | part reference | 142 | | | | | which contains | 143 | | | | | the signature. | 144 | | | | | See definition | 145 | | | | | of
in | 146 | | | | | Section 6.4.5 of | 147 | | | | | [RFC3501] | 148 | | | | | | 149 | smime | [RFC5751] | body | smime-identifier | The email | 150 | | | | | address | 151 | | | | | [RFC5322] | 152 | | | | | associated with | 153 | | | | | the S/MIME | 154 | | | | | signature. | 155 +--------+-----------+--------+------------------+------------------+ 157 IANA is requested to add the the following entries to the "Email 158 Authentication Result Names" subregistry of the "Email Authentication 159 Parameters" registry: 161 +-------------+--------------+------------+---------------+---------+ 162 | Code | Defined | Auth | Meaning | Status | 163 | | | Method | | | 164 +-------------+--------------+------------+---------------+---------+ 165 | none | this | smime | [this memo] | active | 166 | | document | | Section 3.1 | | 167 | | | | | | 168 | pass | this | smime | [this memo] | active | 169 | | document | | Section 3.1 | | 170 | | | | | | 171 | fail | this | smime | [this memo] | active | 172 | | document | | Section 3.1 | | 173 | | | | | | 174 | policy | this | smime | [this memo] | active | 175 | | document | | Section 3.1 | | 176 | | | | | | 177 | neutral | this | smime | [this memo] | active | 178 | | document | | Section 3.1 | | 179 | | | | | | 180 | temperror | this | smime | [this memo] | active | 181 | | document | | Section 3.1 | | 182 | | | | | | 183 | permerror | this | smime | [this memo] | active | 184 | | document | | Section 3.1 | | 185 +-------------+--------------+------------+---------------+---------+ 187 5. Security Considerations 189 TBD 191 6. Normative References 193 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 194 Requirement Levels", BCP 14, RFC 2119, March 1997. 196 [RFC3501] Crispin, M., "INTERNET MESSAGE ACCESS PROTOCOL - VERSION 197 4rev1", RFC 3501, March 2003. 199 [RFC5234] Crocker, D. and P. Overell, "Augmented BNF for Syntax 200 Specifications: ABNF", STD 68, RFC 5234, January 2008. 202 [RFC5322] Resnick, P., Ed., "Internet Message Format", RFC 5322, 203 October 2008. 205 [RFC5451] Kucherawy, M., "Message Header Field for Indicating 206 Message Authentication Status", RFC 5451, April 2009. 208 [RFC5751] Ramsdell, B. and S. Turner, "Secure/Multipurpose Internet 209 Mail Extensions (S/MIME) Version 3.2 Message 210 Specification", RFC 5751, January 2010. 212 Appendix A. Acknowledgements 214 Thank you to Murray S. Kucherawy for comments and corrections on 215 this document. 217 Author's Address 219 Alexey Melnikov 220 Isode Ltd 221 5 Castle Business Village 222 36 Station Road 223 Hampton, Middlesex TW12 2BX 224 UK 226 EMail: Alexey.Melnikov@isode.com