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
838
839
840
841
842
843
844
845
846
847
848
849
850
851
852
853
854
855
856
857
858
859
860
861
862
863
864
865
866
867
868
869
870
871
872
873
874
875
876
877
878
879
880
881
882
883
884
885
886
887
888
889
890
891
892
893
894
895
896
897
898
899
900
901
902
903
904
905
906
907
908
909
910
911
912
913
914
915
916
917
918
919
920
921
922
923
924
925
926
927
928
929
930
931
932
933
934
935
936
937
938
939
940
941
942
943
944
945
946
947
948
949
|
<pre>Network Working Group A. Barbir
Request for Comments: 3835 R. Penno
Category: Informational Nortel Networks
R. Chen
AT&T Labs
M. Hofmann
Bell Labs/Lucent Technologies
H. Orman
Purple Streak Development
August 2004
<span class="h1">An Architecture for Open Pluggable Edge Services (OPES)</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) The Internet Society (2004).
Abstract
This memo defines an architecture that enables the creation of an
application service in which a data provider, a data consumer, and
zero or more application entities cooperatively implement a data
stream service.
<span class="grey">Barbir, et al. Informational [Page 1]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span>
<span class="grey"><a href="./rfc3835">RFC 3835</a> An Architecture for OPES August 2004</span>
Table of Contents
<a href="#section-1">1</a>. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-2">2</a>
<a href="#section-2">2</a> . The Architecture . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-3">3</a>
<a href="#section-2.1">2.1</a>. OPES Entities. . . . . . . . . . . . . . . . . . . . . . <a href="#page-3">3</a>
<a href="#section-2.1.1">2.1.1</a>. Data Dispatcher. . . . . . . . . . . . . . . . . <a href="#page-5">5</a>
<a href="#section-2.2">2.2</a>. OPES Flows . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-6">6</a>
<a href="#section-2.3">2.3</a>. OPES Rules . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-6">6</a>
<a href="#section-2.4">2.4</a>. Callout Servers. . . . . . . . . . . . . . . . . . . . . <a href="#page-7">7</a>
<a href="#section-2.5">2.5</a>. Tracing Facility . . . . . . . . . . . . . . . . . . . . <a href="#page-8">8</a>
<a href="#section-3">3</a>. Security and Privacy Considerations . . . . . . . . . . . . . <a href="#page-9">9</a>
<a href="#section-3.1">3.1</a>. Trust Domains. . . . . . . . . . . . . . . . . . . . . . <a href="#page-9">9</a>
<a href="#section-3.2">3.2</a>. Establishing Trust and Service Authorization . . . . . . <a href="#page-11">11</a>
<a href="#section-3.3">3.3</a>. Callout Protocol . . . . . . . . . . . . . . . . . . . . <a href="#page-11">11</a>
<a href="#section-3.4">3.4</a>. Privacy. . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-12">12</a>
<a href="#section-3.5">3.5</a>. End-to-end Integrity . . . . . . . . . . . . . . . . . . <a href="#page-12">12</a>
<a href="#section-4">4</a>. IAB Architectural and Policy Considerations for OPES . . . . . <a href="#page-12">12</a>
<a href="#section-4.1">4.1</a>. IAB consideration (2.1) One-party Consent. . . . . . . . <a href="#page-12">12</a>
<a href="#section-4.2">4.2</a>. IAB consideration (2.2) IP-Layer Communications. . . . . <a href="#page-13">13</a>
<a href="#section-4.3">4.3</a>. IAB consideration (3.1 and 3.2) Notification . . . . . . <a href="#page-13">13</a>
<a href="#section-4.4">4.4</a>. IAB consideration (3.3) Non-Blocking . . . . . . . . . . <a href="#page-13">13</a>
<a href="#section-4.5">4.5</a>. IAB consideration (4.1) URI Resolution . . . . . . . . . <a href="#page-13">13</a>
<a href="#section-4.6">4.6</a>. IAB consideration (4.2) Reference Validity . . . . . . . <a href="#page-13">13</a>
4.7. IAB consideration (4.3) Application Addressing
Extensions . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-14">14</a>
<a href="#section-4.8">4.8</a>. IAB consideration (5.1) Privacy. . . . . . . . . . . . . <a href="#page-14">14</a>
<a href="#section-5">5</a>. Security Considerations . . . . . . . . . . . . . . . . . . . <a href="#page-14">14</a>
<a href="#section-6">6</a>. IANA Considerations . . . . . . . . . . . . . . . . . . . . . <a href="#page-14">14</a>
<a href="#section-7">7</a>. Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-14">14</a>
<a href="#section-8">8</a>. References . . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-15">15</a>
<a href="#section-8.1">8.1</a>. Normative References . . . . . . . . . . . . . . . . . . <a href="#page-15">15</a>
<a href="#section-8.2">8.2</a>. Informative References . . . . . . . . . . . . . . . . . <a href="#page-15">15</a>
<a href="#section-9">9</a>. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-15">15</a>
<a href="#section-10">10</a>. Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . <a href="#page-16">16</a>
<a href="#section-11">11</a>. Full Copyright Statement . . . . . . . . . . . . . . . . . . . <a href="#page-17">17</a>
<span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Introduction</span>
When supplying a data stream service between a provider and a
consumer, the need to provision the use of other application
entities, in addition to the provider and consumer, may arise. For
example, some party may wish to customize a data stream as a service
to a consumer. The customization step might be based on the
customer's resource availability (e.g., display capabilities).
In some cases it may be beneficial to provide a customization service
at a network location between the provider and consumer host rather
than at one of these endpoints. For certain services performed on
<span class="grey">Barbir, et al. Informational [Page 2]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span>
<span class="grey"><a href="./rfc3835">RFC 3835</a> An Architecture for OPES August 2004</span>
behalf of the end-user, this may be the only option of service
deployment. In this case, zero or more additional application
entities may participate in the data stream service. There are many
possible provisioning scenarios which make a data stream service
attractive. The OPES Use Cases and Deployment Scenarios [<a href="#ref-1" title=""Open Pluggable Edge Services (OPES) Use Cases and Deployment Scenarios"">1</a>] document
provides examples of OPES services. The document discusses services
that modify requests, services that modify responses, and services
that create responses. It is recommended that the document on OPES
Use Cases and Deployment Scenarios [<a href="#ref-1" title=""Open Pluggable Edge Services (OPES) Use Cases and Deployment Scenarios"">1</a>] be read before reading this
document.
This document presents the architectural components of Open Pluggable
Edge Services (OPES) that are needed in order to perform a data
stream service. The architecture addresses the IAB considerations
described in [<a href="#ref-2" title=""IAB Architectural and Policy Considerations for Open Pluggable Edge Services"">2</a>]. These considerations are covered in various parts
of the document. <a href="#section-2.5">Section 2.5</a> addresses tracing; <a href="#section-3">section 3</a> addresses
security considerations. <a href="#section-4">Section 4</a> provides a summary of IAB
considerations and how the architecture addresses them.
The document is organized as follows: <a href="#section-2">Section 2</a> introduces the OPES
architecture. <a href="#section-3">Section 3</a> discusses OPES security and privacy
considerations. <a href="#section-4">Section 4</a> addresses IAB considerations for OPES.
<a href="#section-5">Section 5</a> discusses security considerations. <a href="#section-6">Section 6</a> addresses
IANA considerations. <a href="#section-7">Section 7</a> provides a summary of the
architecture and the requirements for interoperability.
<span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. The Architecture</span>
The architecture of Open Pluggable Edge Services (OPES) can be
described in terms of three interrelated concepts, mainly:
o OPES entities: processes operating in the network;
o OPES flows: data flows that are cooperatively realized by the
OPES entities; and,
o OPES rules: these specify when and how to execute OPES services.
<span class="h3"><a class="selflink" id="section-2.1" href="#section-2.1">2.1</a>. OPES Entities</span>
An OPES entity is an application that operates on a data flow between
a data provider application and a data consumer application. OPES
entities can be:
o an OPES service application, which analyzes and possibly
transforms messages exchanged between the data provider
application and the data consumer application;
<span class="grey">Barbir, et al. Informational [Page 3]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-4" ></span>
<span class="grey"><a href="./rfc3835">RFC 3835</a> An Architecture for OPES August 2004</span>
o a data dispatcher, which invokes an OPES service application based
on an OPES ruleset and application-specific knowledge.
The cooperative behavior of OPES entities introduces additional
functionality for each data flow provided that it matches the OPES
rules. In the network, OPES entities reside inside OPES processors.
In the current work, an OPES processor MUST include a data
dispatcher. Furthermore, the data provider and data consumer
applications are not considered as OPES entities.
To provide verifiable system integrity (see <a href="#section-3.1">section 3.1</a> on trust
domains below) and to facilitate deployment of end-to-end encryption
and data integrity control, OPES processors MUST be:
o explicitly addressable at the IP layer by the end user (data
consumer application). This requirement does not preclude a chain
of OPES processors with the first one in the chain explicitly
addressed at the IP layer by the end user (data consumer
application).
o consented to by either the data consumer or data provider
application. The details of this process are beyond the scope of
the current work.
The OPES architecture is largely independent of the protocol that is
used by the data provider application and the data consumer
application to exchange data. However, this document selects HTTP
[<a href="#ref-3" title=""Hypertext Transfer Protocol -- HTTP/1.1"">3</a>] as the example for the underlying protocol in OPES flows.
<span class="grey">Barbir, et al. Informational [Page 4]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-5" ></span>
<span class="grey"><a href="./rfc3835">RFC 3835</a> An Architecture for OPES August 2004</span>
<span class="h4"><a class="selflink" id="section-2.1.1" href="#section-2.1.1">2.1.1</a>. Data Dispatcher</span>
Data dispatchers include a ruleset that can be compiled from several
sources and MUST resolve into an unambiguous result. The combined
ruleset enables an OPES processor to determine which service
applications to invoke for which data flow. Accordingly, the data
dispatcher constitutes an enhanced policy enforcement point, where
policy rules are evaluated and service-specific data handlers and
state information are maintained, as depicted in Figure 1.
+----------+
| callout |
| server |
+----------+
||
||
||
||
+--------------------------+
| +-----------+ || |
| | OPES | || |
| | service | || |
| |application| || |
| +-----------+ || |
| +----------------------+ |
OPES flow <---->| | data dispatcher and | |<----> OPES flow
| | policy enforcement | |
| +----------------------+ |
| OPES |
| processor |
+--------------------------+
Figure 1: Data Dispatchers
The architecture allows for more than one policy enforcement point to
be present on an OPES flow.
<span class="grey">Barbir, et al. Informational [Page 5]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-6" ></span>
<span class="grey"><a href="./rfc3835">RFC 3835</a> An Architecture for OPES August 2004</span>
<span class="h3"><a class="selflink" id="section-2.2" href="#section-2.2">2.2</a>. OPES Flows</span>
An OPES flow is a cooperative undertaking between a data provider
application, a data consumer application, zero or more OPES service
applications, and one or more data dispatchers.
Since policies are enforced by data dispatchers, the presence of at
least one data dispatcher is required in the OPES flow.
data OPES OPES data
consumer processor A processor N provider
+-----------+ +-----------+ . +-----------+ +-----------+
| data | | OPES | . | OPES | | data |
| consumer | | service | . | service | | provider |
|application| |application| . |application| |application|
+-----------+ +-----------+ . +-----------+ +-----------+
| | | | . | | | |
| HTTP | | HTTP | . | HTTP | | HTTP |
| | | | . | | | |
+-----------+ +-----------+ . +-----------+ +-----------+
| TCP/IP | | TCP/IP | . | TCP/IP | | TCP/IP |
+-----------+ +-----------+ . +-----------+ +-----------+
|| || || . || || ||
================ =====.======== ===========
| <----------------- OPES flow -------------------> |
Figure 2: An OPES flow
Figure 2 depicts two data dispatchers that are present in the OPES
flow. The architecture allows for one or more data dispatchers to be
present in any flow.
<span class="h3"><a class="selflink" id="section-2.3" href="#section-2.3">2.3</a>. OPES Rules</span>
OPES' policy regarding services and the data provided to them is
determined by a ruleset consisting of OPES rules. The rules consist
of a set of conditions and related actions. The ruleset is the
superset of all OPES rules on the processor. The OPES ruleset
determines which service applications will operate on a data stream.
In this model, all data dispatchers are invoked for all flows.
In order to ensure predictable behavior, the OPES architecture
requires the use of a standardized schema for the purpose of defining
and interpreting the ruleset. The OPES architecture does not require
a mechanism for configuring a ruleset into a data dispatcher. This
<span class="grey">Barbir, et al. Informational [Page 6]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-7" ></span>
<span class="grey"><a href="./rfc3835">RFC 3835</a> An Architecture for OPES August 2004</span>
is treated as a local matter for each implementation (e.g., through
the use of a text editor or a secure upload protocol), as long as
such a mechanism complies with the requirements set forth in <a href="#section-3">section</a>
<a href="#section-3">3</a>.
<span class="h3"><a class="selflink" id="section-2.4" href="#section-2.4">2.4</a>. Callout Servers</span>
The evaluation of the OPES ruleset determines which service
applications will operate on a data stream. How the ruleset is
evaluated is not the subject of the architecture, except to note that
it MUST result in the same unambiguous result in all implementations.
In some cases it may be useful for the OPES processor to distribute
the responsibility of service execution by communicating with one or
more callout servers. A data dispatcher invokes the services of a
callout server by using the OPES callout protocol (OCP). The
requirements for the OCP are given in [<a href="#ref-5" title=""Requirements for Open Pluggable Edge Services (OPES) Callout Protocols"">5</a>]. The OCP is application-
agnostic, being unaware of the semantics of the encapsulated
application protocol (e.g., HTTP). However, the data dispatcher MUST
incorporate a service aware vectoring capability that parses the data
flow according to the ruleset and delivers the data to either the
local or remote OPES service application.
<span class="grey">Barbir, et al. Informational [Page 7]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-8" ></span>
<span class="grey"><a href="./rfc3835">RFC 3835</a> An Architecture for OPES August 2004</span>
The general interaction situation is depicted in Figure 3, which
illustrates the positions and interaction of different components of
OPES architecture.
+--------------------------+
| +-----------+ |
| | OPES | |
| | service | | +---------------+ +-----------+
| |application| | | Callout | | Callout |
| +-----------+ | | Server A | | Server X |
| || | | +--------+ | | |
| +----------------------+ | | | OPES | | | |
| | data dispatcher | | | | Service| | | +--------+|
| +----------------------+ | | | Appl A | | | | OPES ||
| || || | | +--------+ | | |Service ||
| +---------+ +-------+ | | || | | | Appl X ||
| | HTTP | | | | | +--------+ | ... | +--------||
| | | | OCP |=========| | OCP | | | || |
| +---------+ +-------+ | | +--------+ | | +------+ |
| | | || | +---------------+ | | OCP | |
| | TCP/IP | =======================================| | |
| | | | | +------+ |
| +---------+ | +-----------+
+--------||-||-------------+
|| ||
+--------+ || || +--------+
|data |== =========================================|data |
|producer| |consumer|
+--------+ +--------+
Figure 3: Interaction of OPES Entities
<span class="h3"><a class="selflink" id="section-2.5" href="#section-2.5">2.5</a>. Tracing Facility</span>
The OPES architecture requires that each data dispatcher provides
tracing facilities that allow the appropriate verification of its
operation. The OPES architecture requires that tracing be feasible
on the OPES flow, per OPES processor, using in-band annotation. One
of those annotations could be a URI with more detailed information on
the OPES services being executed in the OPES flow.
Providing the ability for in-band annotation MAY require header
extensions on the application protocol that is used (e.g., HTTP).
However, the presence of an OPES processor in the data request/
response flow SHALL NOT interfere with the operations of non-OPES
aware clients and servers. Non-OPES clients and servers need not
support these extensions to the base protocol.
<span class="grey">Barbir, et al. Informational [Page 8]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-9" ></span>
<span class="grey"><a href="./rfc3835">RFC 3835</a> An Architecture for OPES August 2004</span>
OPES processors MUST obey tracing, reporting, and notification
requirements set by the center of authority in the trust domain to
which an OPES processor belongs. As part of these requirements, the
OPES processor may be instructed to reject or ignore such
requirements that originate from other trust domains.
<span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. Security and Privacy Considerations</span>
Each data flow MUST be secured in accordance with several policies.
The primary stakeholders are the data consumer and the data provider.
The secondary stakeholders are the entities to which they may have
delegated their trust. The other stakeholders are the owners of the
callout servers. Any of these parties may be participants in the
OPES flow.
These parties MUST have a model, explicit or implicit, describing
their trust policy, which of the other parties are trusted to operate
on data, and what security enhancements are required for
communication. The trust might be delegated for all data, or it
might be restricted to granularity as small as an application data
unit.
All parties that are involved in enforcing policies MUST communicate
the policies to the parties that are involved. These parties are
trusted to adhere to the communicated policies.
In order to delegate fine-grained trust, the parties MUST convey
policy information by implicit contract, by a setup protocol, by a
dynamic negotiation protocol, or in-line with application data
headers.
<span class="h3"><a class="selflink" id="section-3.1" href="#section-3.1">3.1</a>. Trust Domains</span>
The delegation of authority starts at either a data consumer or data
provider and moves to more distant entities in a "stepwise" fashion.
Stepwise means A delegates to B, and B delegates to C, and so forth.
The entities thus "colored" by the delegation are said to form a
trust domain with respect to the original delegating party. Here,
"Colored" means that if the first step in the chain is the data
provider, then the stepwise delegation "colors" the chain with that
data "provider" color. The only colors defined are the data
"provider" and the data "consumer". Delegation of authority
(coloring) propagates from the content producer start of authority or
from the content consumer start of authority, which may be different
from the end points in the data flow.
<span class="grey">Barbir, et al. Informational [Page 9]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-10" ></span>
<span class="grey"><a href="./rfc3835">RFC 3835</a> An Architecture for OPES August 2004</span>
Figure 4 illustrates administrative domains, out-of-band rules, and
policy distribution.
provider administrative domain consumer administrative domain
+------------------------------+ +-------------------------------+
| +--------------+ | | +--------------+ |
| |Provider | <- out-of-band rules, -> |Consumer | |
| |Administrative|~~>~~~: policies and ~<~|Administrative| |
| |Authority | : service authorization : |Authority | |
| +--------------+ : | | : +--------------+ |
| : : | | : : |
| : : | | : : |
| +----------+ : | | : +----------+ |
| | callout | +---------+ | | +---------+ | callout | |
| | server |====| | | | | |====| server | |
| +----------+ | | | | | | +----------+ |
| | OPES | | | | OPES | |
| +----------+ |processor| | | |processor| +----------+ |
| | | | | | | | | | | |
| | data | | | | | | | | data | |
| | provider | | | | | | | | consumer | |
| | | +---------+ | | +---------+ +----------+ |
| +----------+ || || | | || || +----------+ |
| || || || | | || || || |
| ============= ================= =========== |
| | | |
+-------------------------------+ +-------------------------------+
| <----------------- OPES flow -----------------> |
Figure 4: OPES administrative domains and policy distribution
In order to understand the trust relationships between OPES entities,
each is labeled as residing in an administrative domain. Entities
associated with a given OPES flow may reside in one or more
administrative domains.
An OPES processor may be in several trust domains at any time. There
is no restriction on whether the OPES processors are authorized by
data consumers and/or data providers. The original party has the
option of forbidding or limiting redelegation.
An OPES processor MUST have a representation of its trust domain
memberships that it can report in whole or in part for tracing
purposes. It MUST include the name of the party that delegated each
privilege to it.
<span class="grey">Barbir, et al. Informational [Page 10]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-11" ></span>
<span class="grey"><a href="./rfc3835">RFC 3835</a> An Architecture for OPES August 2004</span>
<span class="h3"><a class="selflink" id="section-3.2" href="#section-3.2">3.2</a>. Establishing Trust and Service Authorization</span>
The OPES processor will have a configuration policy specifying what
privileges the callout servers have and how they are to be
identified. OPES uses standard protocols for authentication and
other security communication with callout servers.
An OPES processor will have a trusted method for receiving
configuration information, such as rules for the data dispatcher,
trusted callout servers, primary parties that opt-in or opt-out of
individual services, etc.
Protocol(s) for policy/rule distribution are out of scope for this
document, but the OPES architecture assumes the existence of such a
mechanism.
Requirements for the authorization mechanism are set in a separate
document [<a href="#ref-4" title=""Policy, Authorization, and Enforcement Requirements of the Open Pluggable Edge Services (OPES)"">4</a>].
Service requests may be done in-band. For example, a request to
bypass OPES services could be signalled by a user agent using an HTTP
header string "Bypass-OPES". Such requests MUST be authenticated.
The way OPES entities will honor such requests is subordinate to the
authorization policies effective at that moment.
<span class="h3"><a class="selflink" id="section-3.3" href="#section-3.3">3.3</a>. Callout Protocol</span>
The determination of whether or not OPES processors will use the
measures that are described in the previous section during their
communication with callout servers depends on the details of how the
primary parties delegated trust to the OPES processors and the trust
relationship between the OPES processors and the callout server.
Strong authentication, message authentication codes, and encryption
SHOULD be used. If the OPES processors are in a single
administrative domain with strong confidentiality and integrity
guarantees, then cryptographic protection is recommended but
optional.
If the delegation mechanism names the trusted parties and their
privileges in some way that permits authentication, then the OPES
processors will be responsible for enforcing the policy and for using
authentication as part of that enforcement.
The callout servers MUST be aware of the policy governing the
communication path. They MUST not, for example, communicate
confidential information to auxiliary servers outside the trust
domain.
<span class="grey">Barbir, et al. Informational [Page 11]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-12" ></span>
<span class="grey"><a href="./rfc3835">RFC 3835</a> An Architecture for OPES August 2004</span>
A separate security association MUST be used for each channel
established between an OPES processor and a callout server. The
channels MUST be separate for different primary parties.
<span class="h3"><a class="selflink" id="section-3.4" href="#section-3.4">3.4</a>. Privacy</span>
Some data from OPES flow endpoints is considered "private" or
"sensitive", and OPES processors MUST advise the primary parties of
their privacy policy and respect the policies of the primary parties.
The privacy information MUST be conveyed on a per-flow basis. This
can be accomplished by using current available privacy techniques
such as P3P [<a href="#ref-7" title=""The Platform for Privacy Preferences 1.0 (P3P1.0) Specification"">7</a>] and HTTP privacy capabilities.
The callout servers MUST also participate in the handling of private
data, they MUST be prepared to announce their own capabilities, and
enforce the policy required by the primary parties.
<span class="h3"><a class="selflink" id="section-3.5" href="#section-3.5">3.5</a>. End-to-End Integrity</span>
Digital signature techniques can be used to mark data changes in such
a way that a third-party can verify that the changes are or are not
consistent with the originating party's policy. This requires an
inline method to specify policy and its binding to data, a trace of
changes and the identity of the party making the changes, and strong
identification and authentication methods.
Strong end-to-end integrity can fulfill some of the functions
required by "tracing".
<span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. IAB Architectural and Policy Considerations for OPES</span>
This section addresses the IAB considerations for OPES [<a href="#ref-2" title=""IAB Architectural and Policy Considerations for Open Pluggable Edge Services"">2</a>] and
summarizes how the architecture addresses them.
<span class="h3"><a class="selflink" id="section-4.1" href="#section-4.1">4.1</a>. IAB Consideration (2.1) One-Party Consent</span>
The IAB recommends that all OPES services be explicitly authorized by
one of the application-layer end-hosts (that is, either the data
consumer application or the data provider application).
The current work requires that either the data consumer application
or the data provider application consent to OPES services. These
requirements have been addressed in sections <a href="#section-2">2</a> (<a href="#section-2.1">section 2.1</a>) and 3.
<span class="grey">Barbir, et al. Informational [Page 12]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-13" ></span>
<span class="grey"><a href="./rfc3835">RFC 3835</a> An Architecture for OPES August 2004</span>
<span class="h3"><a class="selflink" id="section-4.2" href="#section-4.2">4.2</a>. IAB Consideration (2.2) IP-Layer Communications</span>
The IAB recommends that OPES processors must be explicitly addressed
at the IP layer by the end user (data consumer application).
This requirement has been addressed in <a href="#section-2.1">section 2.1</a>, by the
requirement that OPES processors be addressable at the IP layer by
the data consumer application.
<span class="h3"><a class="selflink" id="section-4.3" href="#section-4.3">4.3</a>. IAB Consideration (3.1 and 3.2) Notification</span>
The IAB recommends that the OPES architecture incorporate tracing
facilities. Tracing enables data consumer and data provider
applications to detect and respond to actions performed by OPES
processors that are deemed inappropriate to the data consumer or data
provider applications.
<a href="#section-3.2">Section 3.2</a> of this document discusses the tracing and notification
facilities that must be supported by OPES services.
<span class="h3"><a class="selflink" id="section-4.4" href="#section-4.4">4.4</a>. IAB Consideration (3.3) Non-Blocking</span>
The OPES architecture requires the specification of extensions to
HTTP. These extensions will allow the data consumer application to
request a non-OPES version of the content from the data provider
application. These requirements are covered in <a href="#section-3.2">Section 3.2</a>.
<span class="h3"><a class="selflink" id="section-4.5" href="#section-4.5">4.5</a>. IAB Consideration (4.1) URI Resolution</span>
This consideration recommends that OPES documentation must be clear
in describing OPES services as being applied to the result of URI
resolution, not as URI resolution itself.
This requirement has been addressed in sections <a href="#section-2.5">2.5</a> and <a href="#section-3.2">3.2</a>, by
requiring OPES entities to document all the transformations that have
been performed.
<span class="h3"><a class="selflink" id="section-4.6" href="#section-4.6">4.6</a>. IAB Consideration (4.2) Reference Validity</span>
This consideration recommends that all proposed services must define
their impact on inter- and intra-document reference validity.
This requirement has been addressed in <a href="#section-2.5">section 2.5</a> and throughout the
document whereby OPES entities are required to document the performed
transformations.
<span class="grey">Barbir, et al. Informational [Page 13]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-14" ></span>
<span class="grey"><a href="./rfc3835">RFC 3835</a> An Architecture for OPES August 2004</span>
<span class="h3"><a class="selflink" id="section-4.7" href="#section-4.7">4.7</a>. IAB Consideration (4.3) Application Addressing Extensions</span>
This consideration recommends that any OPES services that cannot be
achieved while respecting the above two considerations may be
reviewed as potential requirements for Internet application
addressing architecture extensions, but must not be undertaken as ad
hoc fixes.
The current work does not require extensions of the Internet
application addressing architecture.
<span class="h3"><a class="selflink" id="section-4.8" href="#section-4.8">4.8</a>. IAB Consideration (5.1) Privacy</span>
This consideration recommends that the overall OPES framework must
provide for mechanisms for end users to determine the privacy
policies of OPES intermediaries.
This consideration has been addressed in <a href="#section-3">section 3</a>.
<span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>. Security Considerations</span>
The proposed work has to deal with security from various
perspectives. There are security and privacy issues that relate to
data consumer application, callout protocol, and the OPES flow. In
[<a href="#ref-6" title=""Security Threats and Risks for Open Pluggable Edge Services (OPES)"">6</a>], there is an analysis of the threats against OPES entities.
<span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a>. IANA Considerations</span>
The proposed work will evaluate current protocols for OCP. If the
work determines that a new protocol needs to be developed, then there
may be a need to request new numbers from IANA.
<span class="h2"><a class="selflink" id="section-7" href="#section-7">7</a>. Summary</span>
Although the architecture supports a wide range of cooperative
transformation services, it has few requirements for
interoperability.
The necessary and sufficient elements are specified in the following
documents:
o the OPES ruleset schema, which defines the syntax and semantics of
the rules interpreted by a data dispatcher; and,
o the OPES callout protocol (OCP) [<a href="#ref-5" title=""Requirements for Open Pluggable Edge Services (OPES) Callout Protocols"">5</a>], which defines the
requirements for the protocol between a data dispatcher and a
callout server.
<span class="grey">Barbir, et al. Informational [Page 14]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-15" ></span>
<span class="grey"><a href="./rfc3835">RFC 3835</a> An Architecture for OPES August 2004</span>
<span class="h2"><a class="selflink" id="section-8" href="#section-8">8</a>. References</span>
<span class="h3"><a class="selflink" id="section-8.1" href="#section-8.1">8.1</a>. Normative References</span>
[<a id="ref-1">1</a>] Barbir, A., Burger, E., Chen, R., McHenry, S., Orman, H., and R.
Penno, "Open Pluggable Edge Services (OPES) Use Cases and
Deployment Scenarios", <a href="./rfc3752">RFC 3752</a>, April 2004.
[<a id="ref-2">2</a>] Floyd, S. and L. Daigle, "IAB Architectural and Policy
Considerations for Open Pluggable Edge Services", <a href="./rfc3238">RFC 3238</a>,
January 2002.
[<a id="ref-3">3</a>] Fielding, R., Gettys, J., Mogul, J., Frystyk, H., Masinter, L.,
Leach, P., and T. Berners-Lee, "Hypertext Transfer Protocol --
HTTP/1.1", <a href="./rfc2616">RFC 2616</a>, June 1999.
[<a id="ref-4">4</a>] Barbir, A., Batuner, O., Beck, A., Chan, T., and H. Orman,
"Policy, Authorization, and Enforcement Requirements of the Open
Pluggable Edge Services (OPES)", <a href="./rfc3838">RFC 3838</a>, August 2004.
[<a id="ref-5">5</a>] Beck, A., Hofmann, M., Orman, H., Penno, R., and A. Terzis,
"Requirements for Open Pluggable Edge Services (OPES) Callout
Protocols", <a href="./rfc3836">RFC 3836</a>, August 2004.
[<a id="ref-6">6</a>] Barbir, A., Batuner, O., Srinivas, B., Hofmann, M., and H.
Orman, "Security Threats and Risks for Open Pluggable Edge
Services (OPES)", <a href="./rfc3837">RFC 3837</a>, August 2004.
<span class="h3"><a class="selflink" id="section-8.2" href="#section-8.2">8.2</a>. Informative References</span>
[<a id="ref-7">7</a>] Cranor, L. et. al, "The Platform for Privacy Preferences 1.0
(P3P1.0) Specification", W3C Recommendation 16
<a href="http://www.w3.org/TR/2002/REC-P3P-20020416/">http://www.w3.org/TR/2002/REC-P3P-20020416/</a>, April 2002.
<span class="h2"><a class="selflink" id="section-9" href="#section-9">9</a>. Acknowledgements</span>
This document is the product of OPES WG. Oskar Batuner (Independent
consultant) and Andre Beck (Lucent) are additional authors that have
contributed to this document.
Earlier versions of this work were done by Gary Tomlinson (The
Tomlinson Group) and Michael Condry (Intel).
The authors gratefully acknowledge the contributions of: John Morris,
Mark Baker, Ian Cooper and Marshall T. Rose.
<span class="grey">Barbir, et al. Informational [Page 15]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-16" ></span>
<span class="grey"><a href="./rfc3835">RFC 3835</a> An Architecture for OPES August 2004</span>
<span class="h2"><a class="selflink" id="section-10" href="#section-10">10</a>. Authors' Addresses</span>
Abbie Barbir
Nortel Networks
3500 Carling Avenue
Nepean, Ontario K2H 8E9
Canada
Phone: +1 613 763 5229
EMail: abbieb@nortelnetworks.com
Yih-Farn Robin Chen
AT&T Labs - Research
180 Park Avenue
Florham Park, NJ 07932
US
Phone: +1 973 360 8653
EMail: chen@research.att.com
Markus Hofmann
Bell Labs/Lucent Technologies
Room 4F-513
101 Crawfords Corner Road
Holmdel, NJ 07733
US
Phone: +1 732 332 5983
EMail: hofmann@bell-labs.com
Hilarie Orman
Purple Streak Development
EMail: ho@alum.mit.edu
Reinaldo Penno
Nortel Networks
600 Technology Park Drive
Billerica, MA 01821
USA
EMail: rpenno@nortelnetworks.com
<span class="grey">Barbir, et al. Informational [Page 16]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-17" ></span>
<span class="grey"><a href="./rfc3835">RFC 3835</a> An Architecture for OPES August 2004</span>
<span class="h2"><a class="selflink" id="section-11" href="#section-11">11</a>. Full Copyright Statement</span>
Copyright (C) The Internet Society (2004). This document is subject
to the rights, licenses and restrictions contained in <a href="https://www.rfc-editor.org/bcp/bcp78">BCP 78</a>, and
except as set forth therein, the authors retain all their rights.
This document and the information contained herein are provided on an
"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET
ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED,
INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE
INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Intellectual Property
The IETF takes no position regarding the validity or scope of any
Intellectual Property Rights or other rights that might be claimed to
pertain to the implementation or use of the technology described in
this document or the extent to which any license under such rights
might or might not be available; nor does it represent that it has
made any independent effort to identify any such rights. Information
on the procedures with respect to rights in RFC documents can be
found in <a href="https://www.rfc-editor.org/bcp/bcp78">BCP 78</a> and <a href="https://www.rfc-editor.org/bcp/bcp79">BCP 79</a>.
Copies of IPR disclosures made to the IETF Secretariat and any
assurances of licenses to be made available, or the result of an
attempt made to obtain a general license or permission for the use of
such proprietary rights by implementers or users of this
specification can be obtained from the IETF on-line IPR repository at
<a href="http://www.ietf.org/ipr">http://www.ietf.org/ipr</a>.
The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary
rights that may cover technology that may be required to implement
this standard. Please address the information to the IETF at ietf-
ipr@ietf.org.
Acknowledgement
Funding for the RFC Editor function is currently provided by the
Internet Society.
Barbir, et al. Informational [Page 17]
</pre>
|
