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
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804
805
806
807
808
809
810
811
812
813
814
815
816
817
818
819
820
821
822
823
824
825
826
827
828
829
830
831
832
833
834
835
836
837
|
<pre>Network Working Group E. Burger
Request for Comments: 5442 Consultant
Category: Informational G. Parsons
Nortel Networks
March 2009
<span class="h1">LEMONADE Architecture - Supporting Open Mobile Alliance (OMA)</span>
<span class="h1">Mobile Email (MEM) Using Internet Mail</span>
Status of This Memo
This memo provides information for the Internet community. It does
not specify an Internet standard of any kind. Distribution of this
memo is unlimited.
Copyright Notice
Copyright (c) 2009 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 in effect on the date of
publication of this document (<a href="http://trustee.ietf.org/license-info">http://trustee.ietf.org/license-info</a>).
Please review these documents carefully, as they describe your rights
and restrictions with respect to this document.
This document may contain material from IETF Documents or IETF
Contributions published or made publicly available before November
10, 2008. The person(s) controlling the copyright in some of this
material may not have granted the IETF Trust the right to allow
modifications of such material outside the IETF Standards Process.
Without obtaining an adequate license from the person(s) controlling
the copyright in such materials, this document may not be modified
outside the IETF Standards Process, and derivative works of it may
not be created outside the IETF Standards Process, except to format
it for publication as an RFC or to translate it into languages other
than English.
Abstract
This document specifies the architecture for mobile email, as
described by the Open Mobile Alliance (OMA), using Internet Mail
protocols. This architecture was an important consideration for much
of the work of the LEMONADE (Enhancements to Internet email to
Support Diverse Service Environments) working group in the IETF.
This document also describes how the LEMONADE architecture meets
OMA's requirements for their Mobile Email (MEM) service.
<span class="grey">Burger & Parsons Informational [Page 1]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span>
<span class="grey"><a href="./rfc5442">RFC 5442</a> LEMONADE Architecture March 2009</span>
Table of Contents
<a href="#section-1">1</a>. Introduction ....................................................<a href="#page-2">2</a>
<a href="#section-2">2</a>. OMA Mobile Email (MEM) ..........................................<a href="#page-2">2</a>
<a href="#section-2.1">2.1</a>. OMA MEM Requirements .......................................<a href="#page-2">2</a>
<a href="#section-2.2">2.2</a>. OMA MEM Architecture .......................................<a href="#page-3">3</a>
<a href="#section-2.2.1">2.2.1</a>. OMA MEM Logical Architecture ........................<a href="#page-3">3</a>
<a href="#section-2.2.2">2.2.2</a>. OMA MEM Deployment Issues ...........................<a href="#page-4">4</a>
<a href="#section-2.3">2.3</a>. OMA MEM Technical Specification ............................<a href="#page-6">6</a>
<a href="#section-3">3</a>. IETF LEMONADE Architecture ......................................<a href="#page-6">6</a>
3.1. Relationship between the OMA MEM and LEMONADE Logical
Architectures ..............................................<a href="#page-7">7</a>
3.2. LEMONADE Realization of OMA MEM with
non-LEMONADE-Compliant Servers .............................<a href="#page-9">9</a>
3.2.1. LEMONADE Realization of OMA MEM with
non-LEMONADE IMAP Servers ...........................<a href="#page-9">9</a>
3.2.2. LEMONADE Realization of OMA MEM with non-IMAP
Servers ............................................<a href="#page-10">10</a>
<a href="#section-4">4</a>. Filters and Server-to-Client Notifications and LEMONADE ........<a href="#page-11">11</a>
<a href="#section-5">5</a>. Security Considerations ........................................<a href="#page-13">13</a>
<a href="#section-6">6</a>. Acknowledgements ...............................................<a href="#page-13">13</a>
<a href="#section-7">7</a>. Informative References .........................................<a href="#page-13">13</a>
<span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Introduction</span>
This document describes the architecture of OMA Mobile Email (MEM)
using Internet Mail protocols defined by the IETF. The LEMONADE
working group has enhanced many of these protocols for use in the
mobile environment. The LEMONADE profile [<a href="#ref-PROFILE" title=""Internet Email to Support Diverse Service Environments (Lemonade) Profile"">PROFILE</a>] and its revision,
[<a href="#ref-PROFILE-bis" title=""The Lemonade Profile"">PROFILE-bis</a>], summarize such protocols and protocol use. This
document shows how the OMA MEM Requirements document [<a href="#ref-MEM-req" title=""Mobile Email Requirements Document"">MEM-req</a>], OMA
MEM Architecture [<a href="#ref-MEM-arch" title=""Mobile Email Architecture Document"">MEM-arch</a>], and OMA MEM Technical Specification
[<a href="#ref-MEM-ts" title=""Mobile Email Technical Specification"">MEM-ts</a>] relate to the work of LEMONADE in the IETF.
<span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. OMA Mobile Email (MEM)</span>
The OMA Mobile Email (MEM) sub-working group has spent some time
studying the requirements and architecture of mobile email. IETF
LEMONADE has been liaising with them and has based much of its
Internet Mail enhancements on their input. This section summarizes
the output of the OMA.
<span class="h3"><a class="selflink" id="section-2.1" href="#section-2.1">2.1</a>. OMA MEM Requirements</span>
The OMA MEM activity collected a set of use cases and derived
requirements for a Mobile Email (MEM) enabler. The OMA MEM
Requirements document [<a href="#ref-MEM-req" title=""Mobile Email Requirements Document"">MEM-req</a>] summarizes this work. Some
requirements relate to email protocols, some involve other OMA
<span class="grey">Burger & Parsons Informational [Page 2]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span>
<span class="grey"><a href="./rfc5442">RFC 5442</a> LEMONADE Architecture March 2009</span>
technologies outside the scope of the IETF, and some relate to
implementations and normative interoperability statements for clients
and servers.
<span class="h3"><a class="selflink" id="section-2.2" href="#section-2.2">2.2</a>. OMA MEM Architecture</span>
This section introduces the OMA MEM Architecture.
<span class="h4"><a class="selflink" id="section-2.2.1" href="#section-2.2.1">2.2.1</a>. OMA MEM Logical Architecture</span>
The OMA MEM activity has derived a logical architecture from the
requirements and use cases described in [<a href="#ref-MEM-req" title=""Mobile Email Requirements Document"">MEM-req</a>]. A simplification
for illustrative purposes is shown in Figure 1, where arrows indicate
content flows.
__________
| Other |
+---| Mobile |<--+
| | Enablers | |
| |__________| |
|ME-4 |ME-3
_v____ ___v____ ________
| |ME-1 | | | |
| MEM |-------->| MEM | I2 | Email |
|Client| ME-2| Server |<---->| Server |
|______|<--------|________| |________|
^
|ME-5
|
Figure 1: Basic OMA MEM Logical Architecture
Figure 1 identifies the following elements:
o The MEM client that implements the client-side functionality of
the OMA Mobile Email enabler. It is also responsible for
providing the mobile email user experience and interface to the
user and storing the email and data to be sent to the MEM server
when not connected.
o The MEM server that implements the server-side functionality of
the OMA Mobile Email (MEM) enabler.
o The MEM protocol between the MEM client and MEM server. It is
responsible for all the in-band data exchanges that take place
between the MEM client and server in order to update the MEM
<span class="grey">Burger & Parsons Informational [Page 3]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-4" ></span>
<span class="grey"><a href="./rfc5442">RFC 5442</a> LEMONADE Architecture March 2009</span>
client with email server changes and the email server with changes
in the MEM client, and in order to send new email from the email
server.
o Other OMA enablers that are needed to directly support the Mobile
Email enabler. They are out of the scope of the IETF but may
include support for:
* Client provisioning and management for over-the-air
installation of the MEM client on the device, provisioning of
the client settings, and revocation of client privileges.
* Messaging enablers for out-of-band notification, where out-of-
band notifications that are server-to-client event exchanges
are not transported by the MEM protocol but via other channels.
* Billing, charging, and so on.
OMA identifies different interfaces:
o ME-1: MEM client interface to interact via the MEM protocol with
the MEM server.
o ME-2: Corresponding interface of the MEM server.
o ME-3: Out-of-band MEM server interfaces; for example, to support
generation of server-to-client notifications.
o ME-4: Out-of-band MEM client interfaces (e.g., to receive server-
to-client notifications).
o ME-5: Interface for management of MEM enabler server settings,
user preferences, and filters, globally and per account.
The MEM server enables an email server. In a particular
implementation, the email server may be packaged with (internal to
it) the MEM server or be a separate component. In such cases,
interfaces to the email server are out of scope of the OMA MEM
specifications. In the present document, we focus on the case where
the backend consists of IETF IMAP and SUBMIT servers. However, we
also discuss the relationship to other cases. The I2 interface is an
OMA notation to designate protocol / interfaces that are not
specified by the MEM enabler but may be standardized elsewhere.
<span class="h4"><a class="selflink" id="section-2.2.2" href="#section-2.2.2">2.2.2</a>. OMA MEM Deployment Issues</span>
The OMA MEM Architecture document [<a href="#ref-MEM-arch" title=""Mobile Email Architecture Document"">MEM-arch</a>] further identifies
deployment models.
<span class="grey">Burger & Parsons Informational [Page 4]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-5" ></span>
<span class="grey"><a href="./rfc5442">RFC 5442</a> LEMONADE Architecture March 2009</span>
<span class="h5"><a class="selflink" id="section-2.2.2.1" href="#section-2.2.2.1">2.2.2.1</a>. OMA MEM Proxy</span>
The OMA MEM Architecture document [<a href="#ref-MEM-arch" title=""Mobile Email Architecture Document"">MEM-arch</a>] identifies OMA MEM
server proxies as server components that may be deployed ahead of
firewalls to facilitate firewall traversal.
<span class="h5"><a class="selflink" id="section-2.2.2.2" href="#section-2.2.2.2">2.2.2.2</a>. OMA MEM Deployment Cases</span>
OMA MEM identifies that each component (MEM client, MEM servers,
other enablers, and the email server) may be deployed in different
domains, possibly separated by firewalls and other network
intermediaries. MEM proxies may be involved in front of a firewall
that protects the MEM server domain.
OMA MEM targets support of configurations where:
o All components are within the same domain, such as in a mobile
operator.
o The MEM client and other enablers are in the mobile operator
domain, there is a MEM proxy, and the MEM server and email server
are in the domain of the email service provider.
o The MEM client and other enablers as well as a MEM proxy are in
the mobile operator domain, and the MEM server and email server
are in the domain of the email service provider.
o The MEM client and other enablers are in the mobile operator
domain, a MEM proxy is in a third-party service provider domain,
and the MEM server and email server are in the domain of the email
service provider.
o The MEM client, other enabler, and MEM server are in the mobile
operator domain, and the email server is in the domain of the
email service provider.
o The MEM client and other enablers are in the mobile operator
domain, the MEM server is in a third-party service provider
domain, and the email server is in the domain of the email service
provider.
The email service provider can be a third-party service provider, a
network service provider, or an enterprise email service.
<span class="grey">Burger & Parsons Informational [Page 5]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-6" ></span>
<span class="grey"><a href="./rfc5442">RFC 5442</a> LEMONADE Architecture March 2009</span>
<span class="h3"><a class="selflink" id="section-2.3" href="#section-2.3">2.3</a>. OMA MEM Technical Specification</span>
The OMA MEM activity will conclude with a specification for a Mobile
Email (MEM) enabler. The ongoing work is in the OMA MEM Technical
Specification [<a href="#ref-MEM-ts" title=""Mobile Email Technical Specification"">MEM-ts</a>]. LEMONADE is a basis for the mechanism.
However, some additional details that are outside the scope of the
IETF will also be included.
OMA provides ways to perform provisioning via OMA client provisioning
and device management. Other provisioning specifications are
available (e.g., SMS based).
OMA provides enablers to support out-of-band notification mechanisms,
filter specifications (such as XDM), and remote deactivate devices,
and to perform other non-Internet activities.
<span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. IETF LEMONADE Architecture</span>
This section introduces the LEMONADE Architecture.
The IETF LEMONADE activity has derived a LEMONADE profile
[<a href="#ref-PROFILE-bis" title=""The Lemonade Profile"">PROFILE-bis</a>] with the logical architecture represented in Figure 2,
where arrows indicate content flows.
______________
| |
_________| Notification |
| | Mechanism |
| |______________|
|Notif. ^
|Protocol |
| ___|______
| | | _____
__v__ IMAP | LEMONADE | ESMTP | |
| |<----------->| IMAP |<---------------| MTA |
| MUA |- | Store | |_____|
|_____| \ |__________|
\ |
\ |URLAUTH
\SUBMIT |
\ ____v_____
\ | | _____
\ | LEMONADE | ESMTP | |
---->| Submit |--------------->| MTA |
| Server | |_____|
|__________|
Figure 2: LEMONADE logical architecture
<span class="grey">Burger & Parsons Informational [Page 6]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-7" ></span>
<span class="grey"><a href="./rfc5442">RFC 5442</a> LEMONADE Architecture March 2009</span>
The LEMONADE profile [<a href="#ref-PROFILE" title=""Internet Email to Support Diverse Service Environments (Lemonade) Profile"">PROFILE</a>] assumes:
o IMAP protocol [<a href="./rfc3501" title=""INTERNET MESSAGE ACCESS PROTOCOL - VERSION 4rev1"">RFC3501</a>], including LEMONADE profile extensions
[<a href="#ref-PROFILE" title=""Internet Email to Support Diverse Service Environments (Lemonade) Profile"">PROFILE</a>].
o SUBMIT protocol [<a href="./rfc4409" title=""Message Submission for Mail"">RFC4409</a>], including LEMONADE profile extensions.
o LEMONADE profile compliant IMAP store connected to an MTA (Mail
Transfer Agent) via the ESMTP [<a href="#ref-EMAIL" title=""Simple Mail Transfer Protocol"">EMAIL</a>].
o LEMONADE profile compliant submit server connected to an MTA,
often via the ESMTP.
o Out-of-band server-to-client notifications relying on external
notification mechanisms (and notification protocols) that may be
out of the scope of the LEMONADE profile.
o LEMONADE-aware MUA (Mail User Agent). While use of out-of-band
notification is described in the LEMONADE profile, support for the
underlying notifications mechanisms/protocols is out of the scope
of the LEMONADE specifications.
Further details on the IETF email protocol stack and architecture can
be found in [<a href="#ref-MAIL" title=""Internet Mail Architecture"">MAIL</a>].
<span class="h3"><a class="selflink" id="section-3.1" href="#section-3.1">3.1</a>. Relationship between the OMA MEM and LEMONADE Logical</span>
<span class="h3"> Architectures</span>
Figure 3 illustrates the mapping of the IETF LEMONADE logical
architecture on the OMA MEM logical architecture.
<span class="grey">Burger & Parsons Informational [Page 7]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-8" ></span>
<span class="grey"><a href="./rfc5442">RFC 5442</a> LEMONADE Architecture March 2009</span>
_____________________
| Other_Mob. Enablers |
| |--------------| |
_________| Notification | |
| | | Mechanism | |
| | |______________| |
|Notif. |____________^________|
|Protocol ______|__________
ME-4 | | ___|_ME-3_ |
___|____ | | | | _____
| __v__ | IMAP | | LEMONADE | | ESMTP | |
|| |<----------->| IMAP |<-----------| MTA |
|| MUA || ME-2a | | Store | | |_____|
||_____||\ME-1 | |__________| |
| MEM | \ | | |
| Client| \ | |URLAUTH |
|_______| \SUBMIT | |
\ | ____v_____ |
\ | | | | _____
\ | | LEMONADE | | ESMTP | |
---->| Submit |----------->| MTA |
ME-2b | | Server | | |_____|
| |__________| |
|MEM Email |
|Server Server|
|_________________|
^
|ME-5
|
Figure 3: Mapping of LEMONADE Logical Architecture
onto the OMA MEM Logical Architecture
As described in <a href="#section-3">Section 3</a>, the LEMONADE profile assumes LEMONADE
profile compliant IMAP stores and SUBMIT servers. Because the
LEMONADE profile extends the IMAP store and the SUBMIT server, the
mobile enablement of email provided by the LEMONADE profile is
directly provided in these servers. Mapping to the OMA MEM logical
architecture for the case considered and specified by the LEMONADE
profile, we logically combine the MEM server and email server.
However, in LEMONADE we split them logically into a distinct LEMONADE
message store and a LEMONADE SUBMIT server. ME-2 consists of two
interfaces. ME-2a is IMAP extended according to the LEMONADE
profile. ME-2b is SUBMIT extended according to the LEMONADE profile.
The MUA is part of the MEM client.
<span class="grey">Burger & Parsons Informational [Page 8]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-9" ></span>
<span class="grey"><a href="./rfc5442">RFC 5442</a> LEMONADE Architecture March 2009</span>
The external notifications mechanism is part of the OMA enablers
specified by the OMA.
<span class="h3"><a class="selflink" id="section-3.2" href="#section-3.2">3.2</a>. LEMONADE Realization of OMA MEM with non-LEMONADE-Compliant</span>
<span class="h3"> Servers</span>
The OMA MEM activity is not limited to enabling LEMONADE-compliant
servers. It explicitly identifies the need to support other
backends. This is, of course, outside the scope of the IETF LEMONADE
activity.
<span class="h4"><a class="selflink" id="section-3.2.1" href="#section-3.2.1">3.2.1</a>. LEMONADE Realization of OMA MEM with non-LEMONADE IMAP Servers</span>
Figure 4 illustrates the case of IMAP servers that are not LEMONADE-
compliant. In such case, the I2 interface between the MEM server
components and the IMAP store and SUBMIT server are IMAP and SUBMIT
without LEMONADE extensions.
It is important to note the realizations are of a schematic nature
and do not dictate actual implementation. For example, one could
envision collocating the LEMONADE MEM enabler server and the submit
server shown in Figure 4 in a single instantiation of the
implementation. Likewise, we consciously label the LEMONADE MEM
enabler as neither an IMAP proxy nor an IMAP back-to-back user agent.
LEMONADE leaves the actual implementation to the developer.
<span class="grey">Burger & Parsons Informational [Page 9]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-10" ></span>
<span class="grey"><a href="./rfc5442">RFC 5442</a> LEMONADE Architecture March 2009</span>
______________
| |
_________| Notification |
| | Mechanism |
| |______________|
|Notif. ^
|Protocol |
| ___|______ _____________
| | LEMONADE | | | _____
__v__ IMAP | MEM | IMAP |NON-LEMONADE | ESMTP | |
| |<--------->|Enabler |<------>|IMAP |<----->| MTA |
| MUA |\ ME-2a | Server | |Store | |_____|
|_____| \ |__________| |_____________|
\ |
\ |URLAUTH
\SUBMIT |
\ ____v_____ _____________
\ | | | | _____
\ | LEMONADE | SUBMIT |NON-LEMONADE | ESMTP | |
-->| MEM | |Submit | | |
| Enabler |------->|Server |------>| MTA |
ME-2b | Server | | | |_____|
|__________| |_____________|
Figure 4: Architecture to Support Non-LEMONADE IMAP Servers
with a LEMONADE Realization of an OMA MEM Enabler
<span class="h4"><a class="selflink" id="section-3.2.2" href="#section-3.2.2">3.2.2</a>. LEMONADE Realization of OMA MEM with non-IMAP Servers</span>
Figure 5 illustrates the cases where the message store and submit
servers are not IMAP store or submit servers. They may be Post
Office Protocol (POP3) servers or other proprietary message stores.
<span class="grey">Burger & Parsons Informational [Page 10]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-11" ></span>
<span class="grey"><a href="./rfc5442">RFC 5442</a> LEMONADE Architecture March 2009</span>
______________
| |
_________| Notification |
| | Mechanism |
| |______________|
|Notif. ^
|Protocol |
| ___|______ _____________
| | LEMONADE | | | _____
__v__ IMAP | MEM | I2 |Proprietary | ESMTP | |
| |<--------->|Enabler |<------>|Message |<----->| MTA |
| MUA |\ ME-2a | Server | |Store | |_____|
|_____| \ |__________| |_____________|
\ |
\ |URLAUTH
\SUBMIT |
\ ____v_____ _____________
\ | | | | _____
\ | LEMONADE | I2 |Proprietary | ESMTP | |
-->| MEM | |Submit | | |
| Enabler |------->|Server |------>| MTA |
ME-2b | Server | | | |_____|
|__________| |_____________|
Figure 5: Architecture to Support Non-IMAP Servers with a LEMONADE
Realization of OMA MEM Enabler
I2 designates proprietary adapters to the backends.
<span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. Filters and Server-to-Client Notifications and LEMONADE</span>
OMA MEM Requirements [<a href="#ref-MEM-req" title=""Mobile Email Requirements Document"">MEM-req</a>] and Architecture [<a href="#ref-MEM-arch" title=""Mobile Email Architecture Document"">MEM-arch</a>] emphasize
the need to provide mechanisms for server-to-client notifications of
email events and filtering. Figure 6 illustrates how notification
and filtering works in the LEMONADE profile [<a href="#ref-PROFILE" title=""Internet Email to Support Diverse Service Environments (Lemonade) Profile"">PROFILE</a>].
<span class="grey">Burger & Parsons Informational [Page 11]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-12" ></span>
<span class="grey"><a href="./rfc5442">RFC 5442</a> LEMONADE Architecture March 2009</span>
______________
| |
_________| Notification |
| | Mechanism |
| |______________|
|Notif. ^
|Protocol -------\ _|__
| ______| ___\>|NF|____
| | | ---- | _____
__v__| IMAP |__ LEMONADE |___ ESMTP __| |
| |<-------->|VF| IMAP |DF |<--------|AF| MTA |
| MUA |\ ME-2a |-- Store |--- --|_____|
|_____| \ |_____________| ^
\_\_______________|_______|
\ |URLAUTH
\SUBMIT |
\ ____v_____
\ | | _____
\ | LEMONADE | ESMTP | |
---->| Submit |--------------->| MTA |
ME-2b | Server | |_____|
|__________|
Figure 6: Filtering Mechanism Defined in LEMONADE Architecture
In Figure 6, we define four categories of filters:
o AF: Administrative Filters - The email service provider usually
sets administrative filters. The user typically does not
configure AF. AF applies policies covering content filtering,
virus protection, spam filtering, etc.
o DF: Deposit Filters - Filters that are executed on deposit of new
emails. They can be defined as SIEVE filters [<a href="#ref-SIEVE" title=""Seive: An Email Filtering Language"">SIEVE</a>]. They can
include vacation notices [<a href="./rfc5230" title=""Sieve Email Filtering: Vacation Extension"">RFC5230</a>]. As SIEVE filters, one can
administer them using the SIEVE management protocol [<a href="#ref-MANAGESIEVE" title=""A Protocol for Remotely Managing Sieve Scripts"">MANAGESIEVE</a>].
o VF: View Filters - Filters that define which emails are visible to
the MUA. View filters can be performed via IMAP using the
facilities described in [<a href="#ref-NOTIFICATIONS" title=""Lemonade Notifications Architecture"">NOTIFICATIONS</a>].
o NF: Notification Filters - Filters that define for what email
server event an out-of-band notification is sent to the client, as
described in [<a href="#ref-NOTIFICATIONS" title=""Lemonade Notifications Architecture"">NOTIFICATIONS</a>].
Refer to the aforementioned references for implementation and
management of the respective filters.
<span class="grey">Burger & Parsons Informational [Page 12]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-13" ></span>
<span class="grey"><a href="./rfc5442">RFC 5442</a> LEMONADE Architecture March 2009</span>
<span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>. Security Considerations</span>
We note there are security risks associated with:
o Out-of-band notifications
o Server configuration by client
o Client configuration by server
o Presence of MEM proxy servers
o Presence of MEM servers as intermediaries
o Measures to address the need to traverse firewalls
We refer the reader to the relevant Internet Mail, IMAP, SUBMIT, and
Lemonade documents for how we address these issues.
<span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a>. Acknowledgements</span>
The authors acknowledge and appreciate the work and comments of the
IETF LEMONADE working group and the OMA MEM working group. We
extracted the contents of this document from sections of
[<a href="#ref-PROFILE-bis" title=""The Lemonade Profile"">PROFILE-bis</a>] by Stephane Maes, Alexey Melnikov, and Dave Cridland,
as well as sections of [<a href="#ref-NOTIFICATIONS" title=""Lemonade Notifications Architecture"">NOTIFICATIONS</a>] by Stephane Maes and Ray
Cromwell.
<span class="h2"><a class="selflink" id="section-7" href="#section-7">7</a>. Informative References</span>
[<a id="ref-EMAIL">EMAIL</a>] Klensin, J., "Simple Mail Transfer Protocol",
<a href="./rfc5321">RFC 5321</a>, October 2008.
[<a id="ref-MAIL">MAIL</a>] Crocker, D., <a style="text-decoration: none" href='https://www.google.com/search?sitesearch=datatracker.ietf.org%2Fdoc%2Fhtml%2F&q=inurl:draft-+%22Internet+Mail+Architecture%22'>"Internet Mail Architecture"</a>, Work
in Progress, October 2008.
[<a id="ref-MANAGESIEVE">MANAGESIEVE</a>] Melnikov, A. and T. Martin, "A Protocol for Remotely
Managing Sieve Scripts", Work in Progress,
January 2009.
[<a id="ref-MEM-arch">MEM-arch</a>] Open Mobile Alliance, "Mobile Email Architecture
Document", OMA,
<a href="http://member.openmobilealliance.org/ftp/public_documents/mwg/MEM/Permanent_documents/">http://member.openmobilealliance.org/ftp/</a>
<a href="http://member.openmobilealliance.org/ftp/public_documents/mwg/MEM/Permanent_documents/">public_documents/mwg/MEM/Permanent_documents/</a>
OMA-AD-Mobile_Email-V1_0_0-20070614-D.zip,
June 2007.
<span class="grey">Burger & Parsons Informational [Page 13]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-14" ></span>
<span class="grey"><a href="./rfc5442">RFC 5442</a> LEMONADE Architecture March 2009</span>
[<a id="ref-MEM-req">MEM-req</a>] Open Mobile Alliance, "Mobile Email Requirements
Document", OMA, <a href="http://www.openmobilealliance.org/">http://www.openmobilealliance.org/</a>,
Oct 2005.
[<a id="ref-MEM-ts">MEM-ts</a>] Open Mobile Alliance, "Mobile Email Technical
Specification", OMA, Work in Progress,
<a href="http://www.openmobilealliance.org/">http://www.openmobilealliance.org/</a>, Oct 2007.
[<a id="ref-NOTIFICATIONS">NOTIFICATIONS</a>] Gellens, R. and S. Maes, "Lemonade Notifications
Architecture", Work in Progress, July 2008.
[<a id="ref-PROFILE">PROFILE</a>] Maes, S. and A. Melnikov, "Internet Email to Support
Diverse Service Environments (Lemonade) Profile",
<a href="./rfc4550">RFC 4550</a>, June 2006.
[<a id="ref-PROFILE-bis">PROFILE-bis</a>] Cridland, D., Melnikov, A., and S. Maes, "The
Lemonade Profile", Work in Progress, September 2008.
[<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-RFC4409">RFC4409</a>] Gellens, R. and J. Klensin, "Message Submission for
Mail", <a href="./rfc4409">RFC 4409</a>, April 2006.
[<a id="ref-RFC5230">RFC5230</a>] Showalter, T. and N. Freed, "Sieve Email Filtering:
Vacation Extension", <a href="./rfc5230">RFC 5230</a>, January 2008.
[<a id="ref-SIEVE">SIEVE</a>] Guenther, P. and T. Showalter, "Seive: An Email
Filtering Language", <a href="./rfc5228">RFC 5228</a>, January 2008.
<span class="grey">Burger & Parsons Informational [Page 14]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-15" ></span>
<span class="grey"><a href="./rfc5442">RFC 5442</a> LEMONADE Architecture March 2009</span>
Authors' Addresses
Eric W. Burger
Consultant
New Hampshire
USA
Phone:
Fax: +1 530-267-7447
EMail: eburger@standardstrack.com
URI: <a href="http://www.standardstrack.com">http://www.standardstrack.com</a>
Glenn Parsons
Nortel Networks
3500 Carling Avenue
Ottawa, ON K2H 8E9
Canada
Phone: +1 613 763 7582
EMail: gparsons@nortel.com
Burger & Parsons Informational [Page 15]
</pre>
|
