Debian Codegraph @

rfc6212.html

raw
1 <pre>Internet Engineering Task Force (IETF) M. Kucherawy
2 Request for Comments: 6212 Cloudmark, Inc.
3 Category: Standards Track April 2011
4 ISSN: 2070-1721
5
6
7 <span class="h1">Authentication-Results Registration for Vouch by Reference Results</span>
8
9 Abstract
10
11 This memo updates the registry of properties in Authentication-
12 Results: message header fields to allow relaying of the results of a
13 Vouch By Reference query.
14
15 Status of This Memo
16
17 This is an Internet Standards Track document.
18
19 This document is a product of the Internet Engineering Task Force
20 (IETF). It represents the consensus of the IETF community. It has
21 received public review and has been approved for publication by the
22 Internet Engineering Steering Group (IESG). Further information on
23 Internet Standards is available in <a href="./rfc5741#section-2">Section&nbsp;2 of RFC 5741</a>.
24
25 Information about the current status of this document, any errata,
26 and how to provide feedback on it may be obtained at
27 <a href="http://www.rfc-editor.org/info/rfc6212">http://www.rfc-editor.org/info/rfc6212</a>.
28
29 Copyright Notice
30
31 Copyright (c) 2011 IETF Trust and the persons identified as the
32 document authors. All rights reserved.
33
34 This document is subject to <a href="https://www.rfc-editor.org/bcp/bcp78">BCP 78</a> and the IETF Trust's Legal
35 Provisions Relating to IETF Documents
36 (<a href="http://trustee.ietf.org/license-info">http://trustee.ietf.org/license-info</a>) in effect on the date of
37 publication of this document. Please review these documents
38 carefully, as they describe your rights and restrictions with respect
39 to this document. Code Components extracted from this document must
40 include Simplified BSD License text as described in Section 4.e of
41 the Trust Legal Provisions and are provided without warranty as
42 described in the Simplified BSD License.
43
44
45
46
47
48
49
50
51
52 <span class="grey">Kucherawy Standards Track [Page 1]</span></pre>
53 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span>
54 <span class="grey"><a href="./rfc6212">RFC 6212</a> Auth-Results VBR Registration April 2011</span>
55
56
57 Table of Contents
58
59 <a href="#section-1">1</a>. Introduction ....................................................<a href="#page-2">2</a>
60 <a href="#section-2">2</a>. Keywords ........................................................<a href="#page-2">2</a>
61 <a href="#section-3">3</a>. Discussion ......................................................<a href="#page-2">2</a>
62 <a href="#section-4">4</a>. Definition ......................................................<a href="#page-3">3</a>
63 <a href="#section-5">5</a>. IANA Considerations .............................................<a href="#page-4">4</a>
64 <a href="#section-6">6</a>. Security Considerations .........................................<a href="#page-5">5</a>
65 <a href="#section-7">7</a>. References ......................................................<a href="#page-5">5</a>
66 <a href="#section-7.1">7.1</a>. Normative References .......................................<a href="#page-5">5</a>
67 <a href="#section-7.2">7.2</a>. Informative References .....................................<a href="#page-5">5</a>
68 <a href="#appendix-A">Appendix A</a>. Authentication-Results Examples .......................<a href="#page-6">6</a>
69 <a href="#appendix-A.1">A.1</a>. VBR Results ................................................<a href="#page-6">6</a>
70 <a href="#appendix-B">Appendix B</a>. Acknowledgements ......................................<a href="#page-7">7</a>
71
72 <span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Introduction</span>
73
74 [<a id="ref-AUTHRES">AUTHRES</a>] defined a new header field for electronic mail messages
75 that presents the results of a message authentication effort in a
76 machine-readable format. In the interim, a proposal for rudimentary
77 domain-level reputation assessment, called Vouch By Reference, [<a href="#ref-VBR" title="&quot;Vouch By Reference&quot;">VBR</a>]
78 was published and is now beginning to see popular use.
79
80 This memo thus registers an additional reporting property allowing a
81 VBR result to be relayed as an annotation in a message header.
82
83 <span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. Keywords</span>
84
85 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
86 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
87 document are to be interpreted as described in [<a href="#ref-KEYWORDS" title="&quot;Key words for use in RFCs to Indicate Requirement Levels&quot;">KEYWORDS</a>].
88
89 <span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. Discussion</span>
90
91 Vouch By Reference [<a href="#ref-VBR" title="&quot;Vouch By Reference&quot;">VBR</a>] introduced a mechanism by which a message
92 receiver can query a "vouching" service to determine whether or not a
93 trusted third party is willing to state that mail from a particular
94 source can be considered legitimate. When this assessment is done at
95 an inbound border mail gateway, it would be useful to relay the
96 result of that assessment to internal mail entities such as filters
97 or user agents.
98
99 Reactions to the information contained in an Authentication-Results
100 header field that contains VBR (or any) results are not specified
101 here, as they are entirely a matter of local policy at the receiver.
102
103
104
105
106
107
108 <span class="grey">Kucherawy Standards Track [Page 2]</span></pre>
109 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span>
110 <span class="grey"><a href="./rfc6212">RFC 6212</a> Auth-Results VBR Registration April 2011</span>
111
112
113 <span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. Definition</span>
114
115 This memo adds to the "Email Authentication Methods" registry,
116 created by IANA upon publication of [<a href="#ref-AUTHRES" title="&quot;Message Header Field for Indicating Message Authentication Status&quot;">AUTHRES</a>], the following:
117
118 o The method "vbr"; and
119
120 o Associated with that method, the properties (reporting items)
121 "header.md" and "header.mv".
122
123 If "header.md" is present, its value MUST be the DNS domain name
124 about which a VBR query was made. If "header.mv" is present, its
125 value MUST be the DNS domain name that was queried as the potential
126 voucher for the "header.md" domain.
127
128 If the VBR query was made based on the content of a "VBR-Info" header
129 field present on an incoming message, "header.md" is typically taken
130 from the "md" tag of the "VBR-Info" header field, and "header.mv" is
131 typically one of the values of the "mv" tag in the "VBR-Info" header
132 field on that message. However, [<a href="#ref-VBR" title="&quot;Vouch By Reference&quot;">VBR</a>] permits a different mechanism
133 for selection of the subject domain and/or list of vouchers, ignoring
134 those present in any "VBR-Info" header field the message might have
135 included. A server could even conduct a VBR query when no "VBR-Info"
136 field was present, based on locally configured policy options. Where
137 such mechanisms are applied, the verifying server MAY generate an
138 Authentication-Results field to relay the results of the VBR query.
139
140 This memo also adds to the "Email Authentication Result Names"
141 registry the following result codes and definitions:
142
143 none: No valid VBR-Info header was found in the message, or a domain
144 name to be queried could not be determined.
145
146 pass: A VBR query was completed, and the vouching service queried
147 gave a positive response.
148
149 fail: A VBR query was completed, and the vouching service queried
150 did not give a positive response, or the message contained
151 multiple VBR-Info header fields with different "mc" values
152 (see [<a href="#ref-VBR" title="&quot;Vouch By Reference&quot;">VBR</a>]).
153
154 temperror: A VBR query was attempted but could not be completed due
155 to some error that is likely transient in nature, such as a
156 temporary DNS error. A later attempt may produce a final result.
157
158
159
160
161
162
163
164 <span class="grey">Kucherawy Standards Track [Page 3]</span></pre>
165 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-4" ></span>
166 <span class="grey"><a href="./rfc6212">RFC 6212</a> Auth-Results VBR Registration April 2011</span>
167
168
169 permerror: A VBR query was attempted but could not be completed due
170 to some error that is likely not transient in nature, such as a
171 permanent DNS error. A later attempt is unlikely to produce a
172 final result.
173
174 <span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>. IANA Considerations</span>
175
176 Per [<a href="#ref-IANA" title="">IANA</a>], the following items have been added to the "Email
177 Authentication Methods" registry:
178
179 +------------+----------+--------+----------------+-----------------+
180 | Method | Defined | ptype | property | value |
181 +------------+----------+--------+----------------+-----------------+
182 | vbr | <a href="./rfc6212">RFC 6212</a> | header | md | DNS domain name |
183 | | | | | used as the |
184 | | | | | subject of a |
185 | | | | | VBR query |
186 +------------+----------+--------+----------------+-----------------+
187 | vbr | <a href="./rfc6212">RFC 6212</a> | header | mv | DNS domain name |
188 | | | | | of the entity |
189 | | | | | acting as |
190 | | | | | the voucher |
191 +------------+----------+--------+----------------+-----------------+
192
193 Also, the following items have been added to the "Email
194 Authentication Result Names" registry:
195
196 +-----------+--------------+------------+---------+-----------------+
197 | Code | Existing/New | Defined In | Method | Meaning |
198 +-----------+--------------+------------+---------+-----------------+
199 | none | existing | <a href="./rfc5451">RFC 5451</a> | vbr | <a href="#section-4">Section 4</a> of |
200 | | | | (added) | <a href="./rfc6212">RFC 6212</a> |
201 +-----------+--------------+------------+---------+-----------------+
202 | pass | existing | <a href="./rfc5451">RFC 5451</a> | vbr | <a href="#section-4">Section 4</a> of |
203 | | | | (added) | <a href="./rfc6212">RFC 6212</a> |
204 +-----------+--------------+------------+---------+-----------------+
205 | fail | existing | <a href="./rfc5451">RFC 5451</a> | vbr | <a href="#section-4">Section 4</a> of |
206 | | | | (added) | <a href="./rfc6212">RFC 6212</a> |
207 +-----------+--------------+------------+---------+-----------------+
208 | temperror | existing | <a href="./rfc5451">RFC 5451</a> | vbr | <a href="#section-4">Section 4</a> of |
209 | | | | (added) | <a href="./rfc6212">RFC 6212</a> |
210 +-----------+--------------+------------+---------+-----------------+
211 | permerror | existing | <a href="./rfc5451">RFC 5451</a> | vbr | <a href="#section-4">Section 4</a> of |
212 | | | | (added) | <a href="./rfc6212">RFC 6212</a> |
213 +-----------+--------------+------------+---------+-----------------+
214
215
216
217
218
219
220 <span class="grey">Kucherawy Standards Track [Page 4]</span></pre>
221 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-5" ></span>
222 <span class="grey"><a href="./rfc6212">RFC 6212</a> Auth-Results VBR Registration April 2011</span>
223
224
225 <span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a>. Security Considerations</span>
226
227 This memo creates a mechanism for relaying [<a href="#ref-VBR" title="&quot;Vouch By Reference&quot;">VBR</a>] results using the
228 structure already defined by [<a href="#ref-AUTHRES" title="&quot;Message Header Field for Indicating Message Authentication Status&quot;">AUTHRES</a>]. The Security Considerations
229 sections of those documents should be consulted.
230
231 <span class="h2"><a class="selflink" id="section-7" href="#section-7">7</a>. References</span>
232
233 <span class="h3"><a class="selflink" id="section-7.1" href="#section-7.1">7.1</a>. Normative References</span>
234
235 [<a id="ref-AUTHRES">AUTHRES</a>] Kucherawy, M., "Message Header Field for Indicating
236 Message Authentication Status", <a href="./rfc5451">RFC 5451</a>, April 2009.
237
238 [<a id="ref-KEYWORDS">KEYWORDS</a>] Bradner, S., "Key words for use in RFCs to Indicate
239 Requirement Levels", <a href="https://www.rfc-editor.org/bcp/bcp14">BCP 14</a>, <a href="./rfc2119">RFC 2119</a>, March 1997.
240
241 [<a id="ref-VBR">VBR</a>] Hoffman, P., Levine, J., and A. Hathcock, "Vouch By
242 Reference", <a href="./rfc5518">RFC 5518</a>, April 2009.
243
244 <span class="h3"><a class="selflink" id="section-7.2" href="#section-7.2">7.2</a>. Informative References</span>
245
246 [<a id="ref-IANA">IANA</a>] Narten, T. and H. Alvestrand, "Guidelines for Writing an
247 IANA Considerations Section in RFCs", <a href="https://www.rfc-editor.org/bcp/bcp26">BCP 26</a>, <a href="./rfc5226">RFC 5226</a>,
248 May 2008.
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276 <span class="grey">Kucherawy Standards Track [Page 5]</span></pre>
277 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-6" ></span>
278 <span class="grey"><a href="./rfc6212">RFC 6212</a> Auth-Results VBR Registration April 2011</span>
279
280
281 <span class="h2"><a class="selflink" id="appendix-A" href="#appendix-A">Appendix A</a>. Authentication-Results Examples</span>
282
283 This section presents an example of the use of this new header field
284 to indicate VBR results.
285
286 <span class="h3"><a class="selflink" id="appendix-A.1" href="#appendix-A.1">A.1</a>. VBR Results</span>
287
288 A message that triggered a VBR query, returning a result:
289
290 Authentication-Results: mail-router.example.net;
291 dkim=pass (good signature) header.d=newyork.example.com
292 header.b=oINEO8hg;
293 vbr=pass (voucher.example.net)
294 header.md=newyork.example.com
295 header.mv=voucher.example.org
296 Received: from newyork.example.com
297 (newyork.example.com [192.0.2.250])
298 by mail-router.example.net (8.11.6/8.11.6)
299 for &lt;[email protected]&gt;
300 with ESMTP id i7PK0sH7021929;
301 Fri, Feb 15 2002 17:19:22 -0800
302 DKIM-Signature: v=1; a=rsa-sha256; s=rashani;
303 d=newyork.example.com;
304 t=1188964191; c=relaxed/simple;
305 h=From:Date:To:VBR-Info:Message-Id:Subject;
306 bh=sEu28nfs9fuZGD/pSr7ANysbY3jtdaQ3Xv9xPQtS0m7=;
307 b=oINEO8hgn/gnunsg ... 9n9ODSNFSDij3=
308 From: [email protected]
309 Date: Fri, Feb 15 2002 16:54:30 -0800
310 To: [email protected]
311 VBR-Info: md=newyork.example.com; mc=list;
312 mv=voucher.example.org
313 Message-Id: &lt;[email protected]&gt;
314 Subject: here's a sample
315
316 Example 1: Header Field Reporting Results from a VBR Query
317
318 Here we see an example of a message that was signed using DomainKeys
319 Identified Mail (DKIM) and that also included a VBR-Info header
320 field. On receipt, it is found that the "md=" field in the latter
321 and the "d=" field in the former matched, and also that the DKIM
322 signature verified, so a VBR query was performed. The vouching
323 service, voucher.example.org, indicated that the sender can be
324 trusted, so a "pass" result is included in the Authentication-Results
325 field affixed prior to delivery.
326
327
328
329
330
331
332 <span class="grey">Kucherawy Standards Track [Page 6]</span></pre>
333 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-7" ></span>
334 <span class="grey"><a href="./rfc6212">RFC 6212</a> Auth-Results VBR Registration April 2011</span>
335
336
337 <span class="h2"><a class="selflink" id="appendix-B" href="#appendix-B">Appendix B</a>. Acknowledgements</span>
338
339 The author wishes to acknowledge the following for their review and
340 constructive criticism of this proposal: JD Falk, John Levine, and
341 Alessandro Vesely.
342
343 Author's Address
344
345 Murray S. Kucherawy
346 Cloudmark, Inc.
347 128 King St., 2nd Floor
348 San Francisco, CA 94107
349 US
350
351 Phone: +1 415 946 3800
352 EMail: [email protected]
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388 Kucherawy Standards Track [Page 7]
389 </pre>