An Architecture for Open Pluggable Edge Services (OPES)

Integrity, Privacy, and Security in Open Pluggable Edge Services (OPES) for SMTP

“…The application agnostic architecture of OPES [7] requires that "OPES processors MUST be consented to by either the data consumer or data provider application" (OPES processor is the email gateway for OPES/ SMTP). This cannot prevent the consent-less introduction of OPES processors by noncompliant OPES entities.…”

Open Pluggable Edge Services (OPES) Entities and End Points Communication

“…The Open Pluggable Edge Services (OPES) architecture [1] enables cooperative application services (OPES services) between a data provider, a data consumer, and zero or more OPES processors. The application services under consideration analyze and possibly transform application-level messages exchanged between the data provider and the data consumer.…”

“…The architecture document [1] requires that tracing is supported in-band. This design goal limits the type of application protocols that OPES can support.…”

Security Threats and Risks for Open Pluggable Edge Services (OPES)

“…The Open Pluggable Edge Services (OPES) [1] architecture enables cooperative application services (OPES services) between a data provider, a data consumer, and zero or more OPES processors. The application services under consideration analyze and possibly transform application-level messages exchanged between the data provider and the data consumer.…”

“…The OPES processor can distribute the responsibility of service execution by communicating and collaborating with one or more remote callout servers. The details of the OPES architecture can be found in [1].…”