1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
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
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
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
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
|
<pre>Internet Engineering Task Force (IETF) P. Resnick, Ed.
Request for Comments: 6855 Qualcomm Incorporated
Obsoletes: <a href="./rfc5738">5738</a> C. Newman, Ed.
Category: Standards Track Oracle
ISSN: 2070-1721 S. Shen, Ed.
CNNIC
March 2013
<span class="h1">IMAP Support for UTF-8</span>
Abstract
This specification extends the Internet Message Access Protocol
(IMAP) to support UTF-8 encoded international characters in user
names, mail addresses, and message headers. This specification
replaces <a href="./rfc5738">RFC 5738</a>.
Status of This Memo
This is an Internet Standards Track document.
This document is a product of the Internet Engineering Task Force
(IETF). It represents the consensus of the IETF community. It has
received public review and has been approved for publication by the
Internet Engineering Steering Group (IESG). Further information on
Internet Standards is available in <a href="./rfc5741#section-2">Section 2 of RFC 5741</a>.
Information about the current status of this document, any errata,
and how to provide feedback on it may be obtained at
<a href="http://www.rfc-editor.org/info/rfc6855">http://www.rfc-editor.org/info/rfc6855</a>.
Copyright Notice
Copyright (c) 2013 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to <a href="https://www.rfc-editor.org/bcp/bcp78">BCP 78</a> and the IETF Trust's Legal
Provisions Relating to IETF Documents
(<a href="http://trustee.ietf.org/license-info">http://trustee.ietf.org/license-info</a>) in effect on the date of
publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License.
<span class="grey">Resnick, et al. Standards Track [Page 1]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span>
<span class="grey"><a href="./rfc6855">RFC 6855</a> IMAP Support for UTF-8 March 2013</span>
Table of Contents
<a href="#section-1">1</a>. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-2">2</a>
<a href="#section-2">2</a>. Conventions Used in This Document . . . . . . . . . . . . . . <a href="#page-2">2</a>
3. "UTF8=ACCEPT" IMAP Capability and UTF-8 in IMAP
Quoted-Strings . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-3">3</a>
<a href="#section-4">4</a>. IMAP UTF8 "APPEND" Data Extension . . . . . . . . . . . . . . <a href="#page-4">4</a>
<a href="#section-5">5</a>. "LOGIN" Command and UTF-8 . . . . . . . . . . . . . . . . . . <a href="#page-5">5</a>
<a href="#section-6">6</a>. "UTF8=ONLY" Capability . . . . . . . . . . . . . . . . . . . . <a href="#page-5">5</a>
<a href="#section-7">7</a>. Dealing with Legacy Clients . . . . . . . . . . . . . . . . . <a href="#page-6">6</a>
<a href="#section-8">8</a>. Issues with UTF-8 Header Mailstore . . . . . . . . . . . . . . <a href="#page-7">7</a>
<a href="#section-9">9</a>. IANA Considerations . . . . . . . . . . . . . . . . . . . . . <a href="#page-8">8</a>
<a href="#section-10">10</a>. Security Considerations . . . . . . . . . . . . . . . . . . . <a href="#page-8">8</a>
<a href="#section-11">11</a>. References . . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-9">9</a>
<a href="#section-11.1">11.1</a>. Normative References . . . . . . . . . . . . . . . . . . <a href="#page-9">9</a>
<a href="#section-11.2">11.2</a>. Informative References . . . . . . . . . . . . . . . . . <a href="#page-10">10</a>
<a href="#appendix-A">Appendix A</a>. Design Rationale . . . . . . . . . . . . . . . . . . <a href="#page-11">11</a>
<a href="#appendix-B">Appendix B</a>. Acknowledgments . . . . . . . . . . . . . . . . . . . <a href="#page-11">11</a>
<span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Introduction</span>
This specification forms part of the Email Address
Internationalization protocols described in the Email Address
Internationalization Framework document [<a href="./rfc6530" title=""Overview and Framework for Internationalized Email"">RFC6530</a>]. It extends IMAP
[<a href="./rfc3501" title=""INTERNET MESSAGE ACCESS PROTOCOL - VERSION 4rev1"">RFC3501</a>] to permit UTF-8 [<a href="./rfc3629" title=""UTF-8, a transformation format of ISO 10646"">RFC3629</a>] in headers, as described in
"Internationalized Email Headers" [<a href="./rfc6532" title=""Internationalized Email Headers"">RFC6532</a>]. It also adds a
mechanism to support mailbox names using the UTF-8 charset. This
specification creates two new IMAP capabilities to allow servers to
advertise these new extensions.
This specification assumes that the IMAP server will be operating in
a fully internationalized environment, i.e., one in which all clients
accessing the server will be able to accept non-ASCII message header
fields and other information, as specified in <a href="#section-3">Section 3</a>. At least
during a transition period, that assumption will not be realistic for
many environments; the issues involved are discussed in <a href="#section-7">Section 7</a>
below.
This specification replaces an earlier, experimental approach to the
same problem [<a href="./rfc5738" title=""IMAP Support for UTF-8"">RFC5738</a>].
<span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. Conventions Used in This Document</span>
The key words "MUST", "MUST NOT", "SHOULD", "SHOULD NOT", and "MAY"
in this document are to be interpreted as defined in "Key words for
use in RFCs to Indicate Requirement Levels" [<a href="./rfc2119" title=""Key words for use in RFCs to Indicate Requirement Levels"">RFC2119</a>].
<span class="grey">Resnick, et al. Standards Track [Page 2]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span>
<span class="grey"><a href="./rfc6855">RFC 6855</a> IMAP Support for UTF-8 March 2013</span>
The formal syntax uses the Augmented Backus-Naur Form (ABNF)
[<a href="./rfc5234" title=""Augmented BNF for Syntax Specifications: ABNF"">RFC5234</a>] notation. In addition, rules from IMAP [<a href="./rfc3501" title=""INTERNET MESSAGE ACCESS PROTOCOL - VERSION 4rev1"">RFC3501</a>], UTF-8
[<a href="./rfc3629" title=""UTF-8, a transformation format of ISO 10646"">RFC3629</a>], Extensions to IMAP ABNF [<a href="./rfc4466" title=""Collected Extensions to IMAP4 ABNF"">RFC4466</a>], and IMAP "LIST" command
extensions [<a href="./rfc5258" title=""Internet Message Access Protocol version 4 - LIST Command Extensions"">RFC5258</a>] are also referenced. This document assumes that
the reader will have a reasonably good understanding of these RFCs.
<span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. "UTF8=ACCEPT" IMAP Capability and UTF-8 in IMAP Quoted-Strings</span>
The "UTF8=ACCEPT" capability indicates that the server supports the
ability to open mailboxes containing internationalized messages with
the "SELECT" and "EXAMINE" commands, and the server can provide UTF-8
responses to the "LIST" and "LSUB" commands. This capability also
affects other IMAP extensions that can return mailbox names or their
prefixes, such as NAMESPACE [<a href="./rfc2342" title=""IMAP4 Namespace"">RFC2342</a>] and ACL [<a href="./rfc4314" title=""IMAP4 Access Control List (ACL) Extension"">RFC4314</a>].
The "UTF8=ONLY" capability, described in <a href="#section-6">Section 6</a>, implies the
"UTF8=ACCEPT" capability. A server is said to support "UTF8=ACCEPT"
if it advertises either "UTF8=ACCEPT" or "UTF8=ONLY".
A client MUST use the "ENABLE" command [<a href="./rfc5161" title=""The IMAP ENABLE Extension"">RFC5161</a>] with the
"UTF8=ACCEPT" option (defined in <a href="#section-4">Section 4</a> below) to indicate to the
server that the client accepts UTF-8 in quoted-strings and supports
the "UTF8=ACCEPT" extension. The "ENABLE UTF8=ACCEPT" command is
only valid in the authenticated state.
The IMAP base specification [<a href="./rfc3501" title=""INTERNET MESSAGE ACCESS PROTOCOL - VERSION 4rev1"">RFC3501</a>] forbids the use of 8-bit
characters in atoms or quoted-strings. Thus, a UTF-8 string can only
be sent as a literal. This can be inconvenient from a coding
standpoint, and unless the server offers IMAP non-synchronizing
literals [<a href="./rfc2088" title=""IMAP4 non-synchronizing literals"">RFC2088</a>], this requires an extra round trip for each UTF-8
string sent by the client. When the IMAP server supports
"UTF8=ACCEPT", it supports UTF-8 in quoted-strings with the following
syntax:
quoted =/ DQUOTE *uQUOTED-CHAR DQUOTE
; QUOTED-CHAR is not modified, as it will affect
; other <a href="./rfc3501">RFC 3501</a> ABNF non-terminals.
uQUOTED-CHAR = QUOTED-CHAR / UTF8-2 / UTF8-3 / UTF8-4
UTF8-2 = <Defined in <a href="./rfc3629#section-4">Section 4 of RFC 3629</a>>
UTF8-3 = <Defined in <a href="./rfc3629#section-4">Section 4 of RFC 3629</a>>
UTF8-4 = <Defined in <a href="./rfc3629#section-4">Section 4 of RFC 3629</a>>
When this extended quoting mechanism is used by the client, the
server MUST reject, with a "BAD" response, any octet sequences with
<span class="grey">Resnick, et al. Standards Track [Page 3]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-4" ></span>
<span class="grey"><a href="./rfc6855">RFC 6855</a> IMAP Support for UTF-8 March 2013</span>
the high bit set that fail to comply with the formal syntax
requirements of UTF-8 [<a href="./rfc3629" title=""UTF-8, a transformation format of ISO 10646"">RFC3629</a>]. The IMAP server MUST NOT send UTF-8
in quoted-strings to the client unless the client has indicated
support for that syntax by using the "ENABLE UTF8=ACCEPT" command.
If the server supports "UTF8=ACCEPT", the client MAY use extended
quoted syntax with any IMAP argument that permits a string (including
astring and nstring). However, if characters outside the US-ASCII
repertoire are used in an inappropriate place, the results would be
the same as if other syntactically valid but semantically invalid
characters were used. Specific cases where UTF-8 characters are
permitted or not permitted are described in the following paragraphs.
All IMAP servers that support "UTF8=ACCEPT" SHOULD accept UTF-8 in
mailbox names, and those that also support the Mailbox International
Naming Convention described in <a href="./rfc3501#section-5.1.3">RFC 3501, Section 5.1.3</a>, MUST accept
UTF8-quoted mailbox names and convert them to the appropriate
internal format. Mailbox names MUST comply with the Net-Unicode
Definition (<a href="./rfc5198#section-2">[RFC5198], Section 2</a>) with the specific exception that
they MUST NOT contain control characters (U+0000-U+001F and U+0080-U+
009F), a delete character (U+007F), a line separator (U+2028), or a
paragraph separator (U+2029).
Once an IMAP client has enabled UTF-8 support with the "ENABLE
UTF8=ACCEPT" command, it MUST NOT issue a "SEARCH" command that
contains a charset specification. If an IMAP server receives such a
"SEARCH" command in that situation, it SHOULD reject the command with
a "BAD" response (due to the conflicting charset labels).
<span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. IMAP UTF8 "APPEND" Data Extension</span>
If the server supports "UTF8=ACCEPT", then the server accepts UTF-8
headers in the "APPEND" command message argument. A client that
sends a message with UTF-8 headers to the server MUST send them using
the "UTF8" data extension to the "APPEND" command. If the server
also advertises the "CATENATE" capability [<a href="./rfc4469" title=""Internet Message Access Protocol (IMAP) CATENATE Extension"">RFC4469</a>], the client can
use the same data extension to include such a message in a catenated
message part. The ABNF for the "APPEND" data extension and
"CATENATE" extension follows:
utf8-literal = "UTF8" SP "(" literal8 ")"
literal8 = <Defined in <a href="./rfc4466">RFC 4466</a>>
append-data =/ utf8-literal
cat-part =/ utf8-literal
<span class="grey">Resnick, et al. Standards Track [Page 4]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-5" ></span>
<span class="grey"><a href="./rfc6855">RFC 6855</a> IMAP Support for UTF-8 March 2013</span>
If an IMAP server supports "UTF8=ACCEPT" and the IMAP client has not
issued the "ENABLE UTF8=ACCEPT" command, the server MUST reject, with
a "NO" response, an "APPEND" command that includes any 8-bit
character in message header fields.
<span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>. "LOGIN" Command and UTF-8</span>
This specification does not extend the IMAP "LOGIN" command [<a href="./rfc3501" title=""INTERNET MESSAGE ACCESS PROTOCOL - VERSION 4rev1"">RFC3501</a>]
to support UTF-8 usernames and passwords. Whenever a client needs to
use UTF-8 usernames or passwords, it MUST use the IMAP "AUTHENTICATE"
command, which is already capable of passing UTF-8 usernames and
credentials.
Although using the IMAP "AUTHENTICATE" command in this way makes it
syntactically legal to have a UTF-8 username or password, there is no
guarantee that the user provisioning system utilized by the IMAP
server will allow such identities. This is an implementation
decision and may depend on what identity system the IMAP server is
configured to use.
<span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a>. "UTF8=ONLY" Capability</span>
The "UTF8=ONLY" capability indicates that the server supports
"UTF8=ACCEPT" (see <a href="#section-4">Section 4</a>) and that it requires support for UTF-8
from clients. In particular, this means that the server will send
UTF-8 in quoted-strings, and it will not accept the older
international mailbox name convention (modified UTF-7 [<a href="./rfc3501" title=""INTERNET MESSAGE ACCESS PROTOCOL - VERSION 4rev1"">RFC3501</a>]).
Because these are incompatible changes to IMAP, explicit server
announcement and client confirmation is necessary: clients MUST use
the "ENABLE UTF8=ACCEPT" command before using this server. A server
that advertises "UTF8=ONLY" will reject, with a "NO [CANNOT]"
response [<a href="./rfc5530" title=""IMAP Response Codes"">RFC5530</a>], any command that might require UTF-8 support and
is not preceded by an "ENABLE UTF8=ACCEPT" command.
IMAP clients that find support for a server that announces
"UTF8=ONLY" problematic are encouraged to at least detect the
announcement and provide an informative error message to the
end-user.
Because the "UTF8=ONLY" server capability includes support for
"UTF8=ACCEPT", the capability string will include, at most, one of
those and never both. For the client, "ENABLE UTF8=ACCEPT" is always
used -- never "ENABLE UTF8=ONLY".
<span class="grey">Resnick, et al. Standards Track [Page 5]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-6" ></span>
<span class="grey"><a href="./rfc6855">RFC 6855</a> IMAP Support for UTF-8 March 2013</span>
<span class="h2"><a class="selflink" id="section-7" href="#section-7">7</a>. Dealing with Legacy Clients</span>
In most situations, it will be difficult or impossible for the
implementer or operator of an IMAP (or POP) server to know whether
all of the clients that might access it, or the associated mail store
more generally, will be able to support the facilities defined in
this document. In almost all cases, servers that conform to this
specification will have to be prepared to deal with clients that do
not enable the relevant capabilities. Unfortunately, there is no
completely satisfactory way to do so other than for systems that wish
to receive email that requires SMTPUTF8 capabilities to be sure that
all components of those systems -- including IMAP and other clients
selected by users -- are upgraded appropriately.
When a message that requires SMTPUTF8 is encountered and the client
does not enable UTF-8 capability, choices available to the server
include hiding the problematic message(s), creating in-band or
out-of-band notifications or error messages, or somehow trying to
create a surrogate of the message with the intention of providing
useful information to that client about what has occurred. Such
surrogate messages cannot be actual substitutes for the original
message: they will almost always be impossible to reply to (either at
all or without loss of information) and the new header fields or
specialized constructs for server-client communications may go beyond
the requirements of current email specifications (e.g., [<a href="./rfc5322" title=""Internet Message Format"">RFC5322</a>]).
Consequently, such messages may confuse some legacy mail user agents
(including IMAP clients) or not provide expected information to
users. There are also trade-offs in constructing surrogates of the
original message between accepting complexity and additional
computation costs in order to try to preserve as much information as
possible (for example, in "Post-Delivery Message Downgrading for
Internationalized Email Messages" [<a href="./rfc6857" title=""Post-Delivery Message Downgrading for Internationalized Email Messages"">RFC6857</a>]) and trying to minimize
those costs while still providing useful information (for example, in
"Simplified POP and IMAP Downgrading for Internationalized Email"
[<a href="./rfc6858" title=""Simplified POP and IMAP Downgrading for Internationalized Email"">RFC6858</a>]).
Implementations that choose to perform downgrading SHOULD use one of
the standardized algorithms provided in <a href="./rfc6857">RFC 6857</a> or <a href="./rfc6858">RFC 6858</a>.
Getting downgrade algorithms right, and minimizing the risk of
operational problems and harm to the email system, is tricky and
requires careful engineering. These two algorithms are well
understood and carefully designed.
Because such messages are really surrogates of the original ones, not
really "downgraded" ones (although that terminology is often used for
convenience), they inevitably have relationships to the originals
that the IMAP specification [<a href="./rfc3501" title=""INTERNET MESSAGE ACCESS PROTOCOL - VERSION 4rev1"">RFC3501</a>] did not anticipate. This
brings up two concerns in particular: First, digital signatures
<span class="grey">Resnick, et al. Standards Track [Page 6]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-7" ></span>
<span class="grey"><a href="./rfc6855">RFC 6855</a> IMAP Support for UTF-8 March 2013</span>
computed over and intended for the original message will often not be
applicable to the surrogate message, and will often fail signature
verification. (It will be possible for some digital signatures to be
verified, if they cover only parts of the original message that are
not affected in the creation of the surrogate.) Second, servers that
may be accessed by the same user with different clients or methods
(e.g., POP or webmail systems in addition to IMAP or IMAP clients
with different capabilities) will need to exert extreme care to be
sure that UIDVALIDITY [<a href="./rfc3501" title=""INTERNET MESSAGE ACCESS PROTOCOL - VERSION 4rev1"">RFC3501</a>] behaves as the user would expect.
Those issues may be especially sensitive if the server caches the
surrogate message or computes and stores it when the message arrives
with the intent of making either form available depending on client
capabilities. Additionally, in order to cope with the case when a
server compliant with this extension returns the same UIDVALIDITY to
both legacy and "UTF8=ACCEPT"-aware clients, a client upgraded from
being non-"UTF8=ACCEPT"-aware MUST discard its cache of messages
downloaded from the server.
The best (or "least bad") approach for any given environment will
depend on local conditions, local assumptions about user behavior,
the degree of control the server operator has over client usage and
upgrading, the options that are actually available, and so on. It is
impossible, at least at the time of publication of this
specification, to give good advice that will apply to all situations,
or even particular profiles of situations, other than "upgrade legacy
clients as soon as possible".
<span class="h2"><a class="selflink" id="section-8" href="#section-8">8</a>. Issues with UTF-8 Header Mailstore</span>
When an IMAP server uses a mailbox format that supports UTF-8 headers
and it permits selection or examination of that mailbox without
issuing "ENABLE UTF8=ACCEPT" first, it is the responsibility of the
server to comply with the IMAP base specification [<a href="./rfc3501" title=""INTERNET MESSAGE ACCESS PROTOCOL - VERSION 4rev1"">RFC3501</a>] and the
Internet Message Format [<a href="./rfc5322" title=""Internet Message Format"">RFC5322</a>] with respect to all header
information transmitted over the wire. The issue of handling
messages containing non-ASCII characters in legacy environments is
discussed in <a href="#section-7">Section 7</a>.
<span class="grey">Resnick, et al. Standards Track [Page 7]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-8" ></span>
<span class="grey"><a href="./rfc6855">RFC 6855</a> IMAP Support for UTF-8 March 2013</span>
<span class="h2"><a class="selflink" id="section-9" href="#section-9">9</a>. IANA Considerations</span>
This document redefines two capabilities ("UTF8=ACCEPT" and
"UTF8=ONLY") in the "IMAP 4 Capabilities" registry [<a href="./rfc3501" title=""INTERNET MESSAGE ACCESS PROTOCOL - VERSION 4rev1"">RFC3501</a>]. Three
other capabilities that were described in the experimental
predecessor to this document ("UTF8=ALL", "UTF8=APPEND", "UTF8=USER")
are now OBSOLETE. IANA has updated the registry as follows:
OLD:
+--------------+-----------------+
| UTF8=ACCEPT | [<a href="./rfc5738" title=""IMAP Support for UTF-8"">RFC5738</a>] |
| UTF8=ALL | [<a href="./rfc5738" title=""IMAP Support for UTF-8"">RFC5738</a>] |
| UTF8=APPEND | [<a href="./rfc5738" title=""IMAP Support for UTF-8"">RFC5738</a>] |
| UTF8=ONLY | [<a href="./rfc5738" title=""IMAP Support for UTF-8"">RFC5738</a>] |
| UTF8=USER | [<a href="./rfc5738" title=""IMAP Support for UTF-8"">RFC5738</a>] |
+--------------+-----------------+
NEW:
+------------------------+---------------------+
| UTF8=ACCEPT | [<a href="./rfc6855">RFC6855</a>] |
| UTF8=ALL (OBSOLETE) | [<a href="./rfc5738" title=""IMAP Support for UTF-8"">RFC5738</a>] [<a href="./rfc6855">RFC6855</a>]|
| UTF8=APPEND (OBSOLETE) | [<a href="./rfc5738" title=""IMAP Support for UTF-8"">RFC5738</a>] [<a href="./rfc6855">RFC6855</a>]|
| UTF8=ONLY | [<a href="./rfc6855">RFC6855</a>] |
| UTF8=USER (OBSOLETE) | [<a href="./rfc5738" title=""IMAP Support for UTF-8"">RFC5738</a>] [<a href="./rfc6855">RFC6855</a>]|
+------------------------+---------------------+
<span class="h2"><a class="selflink" id="section-10" href="#section-10">10</a>. Security Considerations</span>
The security considerations of UTF-8 [<a href="./rfc3629" title=""UTF-8, a transformation format of ISO 10646"">RFC3629</a>] and SASLprep [<a href="./rfc4013" title=""SASLprep: Stringprep Profile for User Names and Passwords"">RFC4013</a>]
apply to this specification, particularly with respect to use of
UTF-8 in usernames and passwords. Otherwise, this is not believed to
alter the security considerations of IMAP.
Special considerations, some of them with security implications,
occur if a server that conforms to this specification is accessed by
a client that does not, as well as in some more complex situations in
which a given message is accessed by multiple clients that might use
different protocols and/or support different capabilities. Those
issues are discussed in <a href="#section-7">Section 7</a>.
<span class="grey">Resnick, et al. Standards Track [Page 8]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-9" ></span>
<span class="grey"><a href="./rfc6855">RFC 6855</a> IMAP Support for UTF-8 March 2013</span>
<span class="h2"><a class="selflink" id="section-11" href="#section-11">11</a>. References</span>
<span class="h3"><a class="selflink" id="section-11.1" href="#section-11.1">11.1</a>. Normative References</span>
[<a id="ref-RFC2119">RFC2119</a>] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", <a href="https://www.rfc-editor.org/bcp/bcp14">BCP 14</a>, <a href="./rfc2119">RFC 2119</a>, March 1997.
[<a id="ref-RFC3501">RFC3501</a>] Crispin, M., "INTERNET MESSAGE ACCESS PROTOCOL - VERSION
4rev1", <a href="./rfc3501">RFC 3501</a>, March 2003.
[<a id="ref-RFC3629">RFC3629</a>] Yergeau, F., "UTF-8, a transformation format of ISO
10646", STD 63, <a href="./rfc3629">RFC 3629</a>, November 2003.
[<a id="ref-RFC4013">RFC4013</a>] Zeilenga, K., "SASLprep: Stringprep Profile for User Names
and Passwords", <a href="./rfc4013">RFC 4013</a>, February 2005.
[<a id="ref-RFC4466">RFC4466</a>] Melnikov, A. and C. Daboo, "Collected Extensions to IMAP4
ABNF", <a href="./rfc4466">RFC 4466</a>, April 2006.
[<a id="ref-RFC4469">RFC4469</a>] Resnick, P., "Internet Message Access Protocol (IMAP)
CATENATE Extension", <a href="./rfc4469">RFC 4469</a>, April 2006.
[<a id="ref-RFC5161">RFC5161</a>] Gulbrandsen, A. and A. Melnikov, "The IMAP ENABLE
Extension", <a href="./rfc5161">RFC 5161</a>, March 2008.
[<a id="ref-RFC5198">RFC5198</a>] Klensin, J. and M. Padlipsky, "Unicode Format for Network
Interchange", <a href="./rfc5198">RFC 5198</a>, March 2008.
[<a id="ref-RFC5234">RFC5234</a>] Crocker, D. and P. Overell, "Augmented BNF for Syntax
Specifications: ABNF", STD 68, <a href="./rfc5234">RFC 5234</a>, January 2008.
[<a id="ref-RFC5258">RFC5258</a>] Leiba, B. and A. Melnikov, "Internet Message Access
Protocol version 4 - LIST Command Extensions", <a href="./rfc5258">RFC 5258</a>,
June 2008.
[<a id="ref-RFC5322">RFC5322</a>] Resnick, P., Ed., "Internet Message Format", <a href="./rfc5322">RFC 5322</a>,
October 2008.
[<a id="ref-RFC6530">RFC6530</a>] Klensin, J. and Y. Ko, "Overview and Framework for
Internationalized Email", <a href="./rfc6530">RFC 6530</a>, February 2012.
[<a id="ref-RFC6532">RFC6532</a>] Yang, A., Steele, S., and N. Freed, "Internationalized
Email Headers", <a href="./rfc6532">RFC 6532</a>, February 2012.
[<a id="ref-RFC6857">RFC6857</a>] Fujiwara, K., "Post-Delivery Message Downgrading for
Internationalized Email Messages", <a href="./rfc6857">RFC 6857</a>, March 2013.
<span class="grey">Resnick, et al. Standards Track [Page 9]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-10" ></span>
<span class="grey"><a href="./rfc6855">RFC 6855</a> IMAP Support for UTF-8 March 2013</span>
[<a id="ref-RFC6858">RFC6858</a>] Gulbrandsen, A., "Simplified POP and IMAP Downgrading for
Internationalized Email", <a href="./rfc6858">RFC 6858</a>, March 2013.
<span class="h3"><a class="selflink" id="section-11.2" href="#section-11.2">11.2</a>. Informative References</span>
[<a id="ref-RFC2088">RFC2088</a>] Myers, J., "IMAP4 non-synchronizing literals", <a href="./rfc2088">RFC 2088</a>,
January 1997.
[<a id="ref-RFC2342">RFC2342</a>] Gahrns, M. and C. Newman, "IMAP4 Namespace", <a href="./rfc2342">RFC 2342</a>,
May 1998.
[<a id="ref-RFC4314">RFC4314</a>] Melnikov, A., "IMAP4 Access Control List (ACL) Extension",
<a href="./rfc4314">RFC 4314</a>, December 2005.
[<a id="ref-RFC5530">RFC5530</a>] Gulbrandsen, A., "IMAP Response Codes", <a href="./rfc5530">RFC 5530</a>,
May 2009.
[<a id="ref-RFC5738">RFC5738</a>] Resnick, P. and C. Newman, "IMAP Support for UTF-8",
<a href="./rfc5738">RFC 5738</a>, March 2010.
<span class="grey">Resnick, et al. Standards Track [Page 10]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-11" ></span>
<span class="grey"><a href="./rfc6855">RFC 6855</a> IMAP Support for UTF-8 March 2013</span>
<span class="h2"><a class="selflink" id="appendix-A" href="#appendix-A">Appendix A</a>. Design Rationale</span>
This non-normative section discusses the reasons behind some of the
design choices in this specification.
The "UTF8=ONLY" mechanism simplifies diagnosis of interoperability
problems when legacy support goes away. In the situation where
backwards compatibility is not working anyway, the non-conforming
"just-send-UTF-8 IMAP" has the advantage that it might work with some
legacy clients. However, the difficulty of diagnosing
interoperability problems caused by a "just-send-UTF-8 IMAP"
mechanism is the reason the "UTF8=ONLY" capability mechanism was
chosen.
<span class="h2"><a class="selflink" id="appendix-B" href="#appendix-B">Appendix B</a>. Acknowledgments</span>
The authors wish to thank the participants of the EAI working group
for their contributions to this document, with particular thanks to
Harald Alvestrand, David Black, Randall Gellens, Arnt Gulbrandsen,
Kari Hurtta, John Klensin, Xiaodong Lee, Charles Lindsey, Alexey
Melnikov, Subramanian Moonesamy, Shawn Steele, Daniel Taharlev, and
Joseph Yee for their specific contributions to the discussion.
<span class="grey">Resnick, et al. Standards Track [Page 11]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-12" ></span>
<span class="grey"><a href="./rfc6855">RFC 6855</a> IMAP Support for UTF-8 March 2013</span>
Authors' Addresses
Pete Resnick (editor)
Qualcomm Incorporated
5775 Morehouse Drive
San Diego, CA 92121-1714
USA
Phone: +1 858 651 4478
EMail: presnick@qti.qualcomm.com
Chris Newman (editor)
Oracle
800 Royal Oaks
Monrovia, CA 91016
USA
Phone:
EMail: chris.newman@oracle.com
Sean Shen (editor)
CNNIC
No.4 South 4th Zhongguancun Street
Beijing, 100190
China
Phone: +86 10-58813038
EMail: shenshuo@cnnic.cn
Resnick, et al. Standards Track [Page 12]
</pre>
|
