idnits 2.17.1 draft-melnikov-authentication-results-smime-02.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. == There are 2 instances of lines with non-RFC2606-compliant FQDNs in the document. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (October 11, 2013) is 3847 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 7001 (Obsoleted by RFC 7601) ** Obsolete normative reference: RFC 5751 (Obsoleted by RFC 8551) Summary: 4 errors (**), 0 flaws (~~), 2 warnings (==), 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 October 11, 2013 5 Expires: April 14, 2014 7 Authentication-Results Registration for S/MIME signature verification 8 draft-melnikov-authentication-results-smime-02 10 Abstract 12 RFC 7001 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 April 14, 2014. 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 Internet-DrafAuthentication-Results Registration for S/MIME October 2013 51 Table of Contents 53 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 54 2. Conventions Used in This Document . . . . . . . . . . . . . . 2 55 3. "smime" Authentication Method . . . . . . . . . . . . . . . . 2 56 3.1. S/MIME Results . . . . . . . . . . . . . . . . . . . . . 2 57 3.2. Examples . . . . . . . . . . . . . . . . . . . . . . . . 3 58 4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 5 59 5. Security Considerations . . . . . . . . . . . . . . . . . . . 6 60 6. References . . . . . . . . . . . . . . . . . . . . . . . . . 6 61 6.1. Normative References . . . . . . . . . . . . . . . . . . 6 62 6.2. Informative References . . . . . . . . . . . . . . . . . 7 63 Appendix A. Acknowledgements . . . . . . . . . . . . . . . . . . 7 65 1. Introduction 67 [RFC7001] specifies the Authentication-Results header field for 68 conveying results of message authentication checks. As S/MIME 69 signature verification (and alteration) is sometimes implemented in 70 border message transfer agents, guards and gateways (for example see 71 [RFC3183]), there is a need to convey signature verification status 72 to Mail User Agents (MUA) and downstream filters. This document 73 defines a new authentication method to be used in the Authentication- 74 Results header field for S/MIME related signature checks. 76 2. Conventions Used in This Document 78 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 79 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 80 document are to be interpreted as described in [RFC2119]. 82 The formal syntax uses the Augmented Backus-Naur Form (ABNF) 83 [RFC5234] notation including the core rules defined in Appendix B of 84 RFC 5234 [RFC5234]. 86 3. "smime" Authentication Method 88 3.1. S/MIME Results 90 The result values used by [RFC5751] are as follows: 92 +-------------+-----------------------------------------------------+ 93 | Result code | Meaning | 94 +-------------+-----------------------------------------------------+ 95 | none | The message was not signed. | 96 | | | 97 | pass | The message was signed, the signature or signatures | 98 | | were acceptable to the verifier, and the | 100 Internet-DrafAuthentication-Results Registration for S/MIME October 2013 102 | | signature(s) passed verification tests. | 103 | | | 104 | fail | The message was signed and the signature or | 105 | | signatures were acceptable to the verifier, but | 106 | | they failed the verification test(s). | 107 | | | 108 | policy | The message was signed but the signature or | 109 | | signatures were not acceptable to the verifier. | 110 | | | 111 | neutral | The message was signed but the signature or | 112 | | signatures contained syntax errors or were not | 113 | | otherwise able to be processed. This result SHOULD | 114 | | also be used for other failures not covered | 115 | | elsewhere in this list. | 116 | | | 117 | temperror | The message could not be verified due to some error | 118 | | that is likely transient in nature, such as a | 119 | | temporary inability to retrieve a certificate or | 120 | | CRL. A later attempt may produce a final result. | 121 | | | 122 | permerror | The message could not be verified due to some error | 123 | | that is unrecoverable, such as a required header | 124 | | field being absent or the signer's certificate not | 125 | | being available. A later attempt is unlikely to | 126 | | produce a final result. | 127 +-------------+-----------------------------------------------------+ 129 A signature is "acceptable to the verifier" if it passes local policy 130 checks (or there are no specific local policy checks). For example, 131 a verifier might require that the signature(s) on the message be 132 added using the DNS domain present in the From: header field of the 133 message, thus making third-party signatures unacceptable. [RFC5751] 134 advises that if a message fails verification, it should be treated as 135 an unsigned message. A report of "fail" here permits the receiver of 136 the report to decide how to handle the failure. A report of 137 "neutral" or "none" preempts that choice, ensuring the message will 138 be treated as if it had not been signed. 140 3.2. Examples 142 Return-Path: 143 Authentication-Results: example.com; 144 auth=fail (CRL validation failure) 145 body.smime-identifier=aliceDss@examples.com 146 body.smime-part=2 147 Received: from ietfa.amsl.com (localhost [IPv6:::1]) 148 by ietfa.amsl.com (Postfix) with ESMTP id 2875111E81A0; 150 Internet-DrafAuthentication-Results Registration for S/MIME October 2013 152 Fri, 06 Sep 2002 00:35:14 -0700 (PDT) 153 MIME-Version: 1.0 154 To: User2@examples.com 155 From: aliceDss@examples.com 156 Subject: Example 4.8 157 Message-Id: <020906002550300.249@examples.com> 158 Date: Fri, 06 Sep 2002 00:25:21 -0700 159 Content-Type: multipart/signed; 160 micalg=SHA1; 161 boundary="----=_NextBoundry____Fri,_06_Sep_2002_00:25:21"; 162 protocol="application/pkcs7-signature" 164 This is a multi-part message in MIME format. 166 ------=_NextBoundry____Fri,_06_Sep_2002_00:25:21 168 This is some sample content. 169 ------=_NextBoundry____Fri,_06_Sep_2002_00:25:21 170 Content-Type: application/pkcs7-signature; name=smime.p7s 171 Content-Transfer-Encoding: base64 172 Content-Disposition: attachment; filename=smime.p7s 174 MIIDdwYJKoZIhvcNAQcCoIIDaDCCA2QCAQExCTAHBgUrDgMCGjALBgkqhkiG9w0BBwGgggL 175 gMIIC3DCCApugAwIBAgICAMgwCQYHKoZIzjgEAzASMRAwDgYDVQQDEwdDYXJsRFNTMB4XDT 176 k5MDgxNzAxMTA0OVoXDTM5MTIzMTIzNTk1OVowEzERMA8GA1UEAxMIQWxpY2VEU1MwggG2M 177 IIBKwYHKoZIzjgEATCCAR4CgYEAgY3N7YPqCp45PsJIKKPkR5PdDteoDuxTxauECE//lOFz 178 SH4M1vNESNH+n6+koYkv4dkwyDbeP5u/t0zcX2mK5HXQNwyRCJWb3qde+fz0ny/dQ6iLVPE 179 /sAcIR01diMPDtbPjVQh11Tl2EMR4vf+dsISXN/LkURu15AmWXPN+W9sCFQDiR6YaRWa4E8 180 baj7g3IStii/eTzQKBgCY40BSJMqo5+z5t2UtZakx2IzkEAjVc8ssaMMMeUF3dm1nizaoFP 181 VjAe6I2uG4Hr32KQiWn9HXPSgheSz6Q+G3qnMkhijt2FOnOLl2jB80jhbgvMAF8bUmJEYk2 182 RL34yJVKU1a14vlz7BphNh8Rf8K97dFQ/5h0wtGBSmA5ujY5A4GEAAKBgFzjuVp1FJYLqXr 183 d4z+p7Kxe3L23ExE0phaJKBEj2TSGZ3V1ExI9Q1tv5VG/+onyohs+JH09B41bY8i7RaWgSu 184 OF1s4GgD/oI34a8iSrUxq4Jw0e7wi/ZhSAXGKsZfoVi/G7NNTSljf2YUeyxDKE8H5BQP1Gp 185 2NOM/Kl4vTyg+W4o4GBMH8wDAYDVR0TAQH/BAIwADAOBgNVHQ8BAf8EBAMCBsAwHwYDVR0j 186 BBgwFoAUcEQ+gi5vh95K03XjPSC8QyuT8R8wHQYDVR0OBBYEFL5sobPjwfftQ3CkzhMB4v3 187 jl/7NMB8GA1UdEQQYMBaBFEFsaWNlRFNTQGV4YW1wbGUuY29tMAkGByqGSM44BAMDMAAwLQ 188 IUVQykGR9CK4lxIjONg2q1PWdrv0UCFQCfYVNSVAtcst3a53Yd4hBSW0NevTFjMGECAQEwG 189 DASMRAwDgYDVQQDEwdDYXJsRFNTAgIAyDAHBgUrDgMCGjAJBgcqhkjOOAQDBC4wLAIUM/mG 190 f6gkgp9Z0XtRdGimJeB/BxUCFGFFJqwYRt1WYcIOQoGiaowqGzVI 192 ------=_NextBoundry____Fri,_06_Sep_2002_00:25:21-- 194 Internet-DrafAuthentication-Results Registration for S/MIME October 2013 196 4. IANA Considerations 198 IANA is requested to add the the following entries to the "Email 199 Authentication Methods" subregistry of the "Email Authentication 200 Parameters" registry: 202 +--------+-----------+--------+------------------+------------------+ 203 | Method | Defined | ptype | property | value | 204 +--------+-----------+--------+------------------+------------------+ 205 | smime | [RFC5751] | body | smime-part | The MIME body | 206 | | | | | part reference | 207 | | | | | which contains | 208 | | | | | the signature. | 209 | | | | | See definition | 210 | | | | | of
in | 211 | | | | | Section 6.4.5 of | 212 | | | | | [RFC3501] | 213 | | | | | | 214 | smime | [RFC5751] | body | smime-identifier | The email | 215 | | | | | address | 216 | | | | | [RFC5322] | 217 | | | | | associated with | 218 | | | | | the S/MIME | 219 | | | | | signature. Note | 220 | | | | | that this email | 221 | | | | | address can | 222 | | | | | correspond to a | 223 | | | | | counter | 224 | | | | | signature. | 225 +--------+-----------+--------+------------------+------------------+ 227 IANA is requested to add the the following entries to the "Email 228 Authentication Result Names" subregistry of the "Email Authentication 229 Parameters" registry: 231 +-------------+--------------+------------+---------------+---------+ 232 | Code | Defined | Auth | Meaning | Status | 233 | | | Method | | | 234 +-------------+--------------+------------+---------------+---------+ 235 | none | this | smime | [this memo] | active | 236 | | document | | Section 3.1 | | 237 | | | | | | 238 | pass | this | smime | [this memo] | active | 239 | | document | | Section 3.1 | | 240 | | | | | | 241 | fail | this | smime | [this memo] | active | 242 | | document | | Section 3.1 | | 244 Internet-DrafAuthentication-Results Registration for S/MIME October 2013 246 | | | | | | 247 | policy | this | smime | [this memo] | active | 248 | | document | | Section 3.1 | | 249 | | | | | | 250 | neutral | this | smime | [this memo] | active | 251 | | document | | Section 3.1 | | 252 | | | | | | 253 | temperror | this | smime | [this memo] | active | 254 | | document | | Section 3.1 | | 255 | | | | | | 256 | permerror | this | smime | [this memo] | active | 257 | | document | | Section 3.1 | | 258 +-------------+--------------+------------+---------------+---------+ 260 5. Security Considerations 262 This document doesn't add new security considerations not already 263 covered by [RFC7001] and [RFC5751]. In particular security 264 considerations related to use of weak cryptography over plaintext, 265 weakening and breaking of cryptographic algorithms over time, as well 266 as changing the behavior of message processing based on presence of a 267 signature specified in [RFC5751] are relevant to this document. 268 Similarly, the following security considerations specified in 269 [RFC7001] are particularly relevant to this document: Forged Header 270 Fields, Misleading Results, Internal MTA Lists and Compromised 271 Internal Hosts. 273 6. References 275 6.1. Normative References 277 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 278 Requirement Levels", BCP 14, RFC 2119, March 1997. 280 [RFC3501] Crispin, M., "INTERNET MESSAGE ACCESS PROTOCOL - VERSION 281 4rev1", RFC 3501, March 2003. 283 [RFC5234] Crocker, D. and P. Overell, "Augmented BNF for Syntax 284 Specifications: ABNF", STD 68, RFC 5234, January 2008. 286 [RFC5322] Resnick, P., Ed., "Internet Message Format", RFC 5322, 287 October 2008. 289 [RFC7001] Kucherawy, M., "Message Header Field for Indicating 290 Message Authentication Status", RFC 7001, September 2013. 292 Internet-DrafAuthentication-Results Registration for S/MIME October 2013 294 [RFC5751] Ramsdell, B. and S. Turner, "Secure/Multipurpose Internet 295 Mail Extensions (S/MIME) Version 3.2 Message 296 Specification", RFC 5751, January 2010. 298 6.2. Informative References 300 [RFC3183] Dean, T. and W. Ottaway, "Domain Security Services using S 301 /MIME", RFC 3183, October 2001. 303 Appendix A. Acknowledgements 305 Thank you to Murray S. Kucherawy and Steve Kille for comments and 306 corrections on this document. 308 Author's Address 310 Alexey Melnikov 311 Isode Ltd 312 5 Castle Business Village 313 36 Station Road 314 Hampton, Middlesex TW12 2BX 315 UK 317 EMail: Alexey.Melnikov@isode.com