idnits 2.17.1 draft-melnikov-authentication-results-smime-01.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 : ---------------------------------------------------------------------------- ** There are 16 instances of too long lines in the document, the longest one being 2 characters in excess of 72. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (April 19, 2013) is 4024 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: 4 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 April 19, 2013 5 Expires: October 21, 2013 7 Authentication-Results Registration for S/MIME signature verification 8 draft-melnikov-authentication-results-smime-01 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 October 21, 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 3.2. Examples . . . . . . . . . . . . . . . . . . . . . . . . 3 56 4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 4 57 5. Security Considerations . . . . . . . . . . . . . . . . . . . 6 58 6. Normative References . . . . . . . . . . . . . . . . . . . . 6 59 Appendix A. Acknowledgements . . . . . . . . . . . . . . . . . . 6 60 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 6 62 1. Introduction 64 [RFC5451] specifies the Authentication-Results header field for 65 conveying results of message authentication checks. This document 66 defines a new authentication method to be used in the Authentication- 67 Results header field for S/MIME related signature checks. 69 [[Explain in more details use cases, such as a border MTA performing 70 check and MUA showing results.]] 72 2. Conventions Used in This Document 74 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 75 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 76 document are to be interpreted as described in [RFC2119]. 78 The formal syntax uses the Augmented Backus-Naur Form (ABNF) 79 [RFC5234] notation including the core rules defined in Appendix B of 80 RFC 5234 [RFC5234]. 82 3. "smime" Authentication Method 84 3.1. S/MIME Results 86 The result values used by [RFC5751] are as follows: 88 +-------------+-----------------------------------------------------+ 89 | Result code | Meaning | 90 +-------------+-----------------------------------------------------+ 91 | none | The message was not signed. | 92 | | | 93 | pass | The message was signed, the signature or signatures | 94 | | were acceptable to the verifier, and the | 95 | | signature(s) passed verification tests. | 96 | | | 97 | fail | The message was signed and the signature or | 98 | | signatures were acceptable to the verifier, but | 99 | | they failed the verification test(s). | 100 | | | 101 | policy | The message was signed but the signature or | 102 | | signatures were not acceptable to the verifier. | 103 | | | 104 | neutral | The message was signed but the signature or | 105 | | signatures contained syntax errors or were not | 106 | | otherwise able to be processed. This result SHOULD | 107 | | also be used for other failures not covered | 108 | | elsewhere in this list. | 109 | | | 110 | temperror | The message could not be verified due to some error | 111 | | that is likely transient in nature, such as a | 112 | | temporary inability to retrieve a certificate or | 113 | | CRL. A later attempt may produce a final result. | 114 | | | 115 | permerror | The message could not be verified due to some error | 116 | | that is unrecoverable, such as a required header | 117 | | field being absent or the signer's certificate not | 118 | | being available. A later attempt is unlikely to | 119 | | produce a final result. | 120 +-------------+-----------------------------------------------------+ 122 A signature is "acceptable to the verifier" if it passes local policy 123 checks (or there are no specific local policy checks). For example, 124 a verifier might require that the signature(s) on the message be 125 added using the DNS domain present in the From: header field of the 126 message, thus making third-party signatures unacceptable. [RFC5751] 127 advises that if a message fails verification, it should be treated as 128 an unsigned message. A report of "fail" here permits the receiver of 129 the report to decide how to handle the failure. A report of 130 "neutral" or "none" preempts that choice, ensuring the message will 131 be treated as if it had not been signed. 133 3.2. Examples 135 Authentication-Results: example.com; 136 auth=fail (CRL validation failure) 137 body.smime-identifier=aliceDss@examples.com 138 body.smime-part=2 139 MIME-Version: 1.0 140 To: User2@examples.com 141 From: aliceDss@examples.com 142 Subject: Example 4.8 143 Message-Id: <020906002550300.249@examples.com> 144 Date: Fri, 06 Sep 2002 00:25:21 -0300 145 Content-Type: multipart/signed; 146 micalg=SHA1; 147 boundary="----=_NextBoundry____Fri,_06_Sep_2002_00:25:21"; 148 protocol="application/pkcs7-signature" 150 This is a multi-part message in MIME format. 152 ------=_NextBoundry____Fri,_06_Sep_2002_00:25:21 154 This is some sample content. 155 ------=_NextBoundry____Fri,_06_Sep_2002_00:25:21 156 Content-Type: application/pkcs7-signature; name=smime.p7s 157 Content-Transfer-Encoding: base64 158 Content-Disposition: attachment; filename=smime.p7s 160 MIIDdwYJKoZIhvcNAQcCoIIDaDCCA2QCAQExCTAHBgUrDgMCGjALBgkqhkiG9w0BBwGgggL 161 gMIIC3DCCApugAwIBAgICAMgwCQYHKoZIzjgEAzASMRAwDgYDVQQDEwdDYXJsRFNTMB4XDT 162 k5MDgxNzAxMTA0OVoXDTM5MTIzMTIzNTk1OVowEzERMA8GA1UEAxMIQWxpY2VEU1MwggG2M 163 IIBKwYHKoZIzjgEATCCAR4CgYEAgY3N7YPqCp45PsJIKKPkR5PdDteoDuxTxauECE//lOFz 164 SH4M1vNESNH+n6+koYkv4dkwyDbeP5u/t0zcX2mK5HXQNwyRCJWb3qde+fz0ny/dQ6iLVPE 165 /sAcIR01diMPDtbPjVQh11Tl2EMR4vf+dsISXN/LkURu15AmWXPN+W9sCFQDiR6YaRWa4E8 166 baj7g3IStii/eTzQKBgCY40BSJMqo5+z5t2UtZakx2IzkEAjVc8ssaMMMeUF3dm1nizaoFP 167 VjAe6I2uG4Hr32KQiWn9HXPSgheSz6Q+G3qnMkhijt2FOnOLl2jB80jhbgvMAF8bUmJEYk2 168 RL34yJVKU1a14vlz7BphNh8Rf8K97dFQ/5h0wtGBSmA5ujY5A4GEAAKBgFzjuVp1FJYLqXr 169 d4z+p7Kxe3L23ExE0phaJKBEj2TSGZ3V1ExI9Q1tv5VG/+onyohs+JH09B41bY8i7RaWgSu 170 OF1s4GgD/oI34a8iSrUxq4Jw0e7wi/ZhSAXGKsZfoVi/G7NNTSljf2YUeyxDKE8H5BQP1Gp 171 2NOM/Kl4vTyg+W4o4GBMH8wDAYDVR0TAQH/BAIwADAOBgNVHQ8BAf8EBAMCBsAwHwYDVR0j 172 BBgwFoAUcEQ+gi5vh95K03XjPSC8QyuT8R8wHQYDVR0OBBYEFL5sobPjwfftQ3CkzhMB4v3 173 jl/7NMB8GA1UdEQQYMBaBFEFsaWNlRFNTQGV4YW1wbGUuY29tMAkGByqGSM44BAMDMAAwLQ 174 IUVQykGR9CK4lxIjONg2q1PWdrv0UCFQCfYVNSVAtcst3a53Yd4hBSW0NevTFjMGECAQEwG 175 DASMRAwDgYDVQQDEwdDYXJsRFNTAgIAyDAHBgUrDgMCGjAJBgcqhkjOOAQDBC4wLAIUM/mG 176 f6gkgp9Z0XtRdGimJeB/BxUCFGFFJqwYRt1WYcIOQoGiaowqGzVI 178 ------=_NextBoundry____Fri,_06_Sep_2002_00:25:21-- 180 4. IANA Considerations 182 IANA is requested to add the the following entries to the "Email 183 Authentication Methods" subregistry of the "Email Authentication 184 Parameters" registry: 186 +--------+-----------+--------+------------------+------------------+ 187 | Method | Defined | ptype | property | value | 188 +--------+-----------+--------+------------------+------------------+ 189 | smime | [RFC5751] | body | smime-part | The MIME body | 190 | | | | | part reference | 191 | | | | | which contains | 192 | | | | | the signature. | 193 | | | | | See definition | 194 | | | | | of
in | 195 | | | | | Section 6.4.5 of | 196 | | | | | [RFC3501] | 197 | | | | | | 198 | smime | [RFC5751] | body | smime-identifier | The email | 199 | | | | | address | 200 | | | | | [RFC5322] | 201 | | | | | associated with | 202 | | | | | the S/MIME | 203 | | | | | signature. | 204 +--------+-----------+--------+------------------+------------------+ 206 IANA is requested to add the the following entries to the "Email 207 Authentication Result Names" subregistry of the "Email Authentication 208 Parameters" registry: 210 +-------------+--------------+------------+---------------+---------+ 211 | Code | Defined | Auth | Meaning | Status | 212 | | | Method | | | 213 +-------------+--------------+------------+---------------+---------+ 214 | none | this | smime | [this memo] | active | 215 | | document | | Section 3.1 | | 216 | | | | | | 217 | pass | this | smime | [this memo] | active | 218 | | document | | Section 3.1 | | 219 | | | | | | 220 | fail | this | smime | [this memo] | active | 221 | | document | | Section 3.1 | | 222 | | | | | | 223 | policy | this | smime | [this memo] | active | 224 | | document | | Section 3.1 | | 225 | | | | | | 226 | neutral | this | smime | [this memo] | active | 227 | | document | | Section 3.1 | | 228 | | | | | | 229 | temperror | this | smime | [this memo] | active | 230 | | document | | Section 3.1 | | 231 | | | | | | 232 | permerror | this | smime | [this memo] | active | 233 | | document | | Section 3.1 | | 234 +-------------+--------------+------------+---------------+---------+ 236 5. Security Considerations 238 TBD 240 6. Normative References 242 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 243 Requirement Levels", BCP 14, RFC 2119, March 1997. 245 [RFC3501] Crispin, M., "INTERNET MESSAGE ACCESS PROTOCOL - VERSION 246 4rev1", RFC 3501, March 2003. 248 [RFC5234] Crocker, D. and P. Overell, "Augmented BNF for Syntax 249 Specifications: ABNF", STD 68, RFC 5234, January 2008. 251 [RFC5322] Resnick, P., Ed., "Internet Message Format", RFC 5322, 252 October 2008. 254 [RFC5451] Kucherawy, M., "Message Header Field for Indicating 255 Message Authentication Status", RFC 5451, April 2009. 257 [RFC5751] Ramsdell, B. and S. Turner, "Secure/Multipurpose Internet 258 Mail Extensions (S/MIME) Version 3.2 Message 259 Specification", RFC 5751, January 2010. 261 Appendix A. Acknowledgements 263 Thank you to Murray S. Kucherawy and Steve Kille for comments and 264 corrections on this document. 266 Author's Address 268 Alexey Melnikov 269 Isode Ltd 270 5 Castle Business Village 271 36 Station Road 272 Hampton, Middlesex TW12 2BX 273 UK 275 EMail: Alexey.Melnikov@isode.com