Skip to main content

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

Revision differences

Document history

Date By Action
2018-12-20
(System)
Received changes through RFC Editor sync (changed abstract to 'The Open Pluggable Edge Services (OPES) framework is application agnostic. Application-specific adaptations extend that framework. Previous …
Received changes through RFC Editor sync (changed abstract to 'The Open Pluggable Edge Services (OPES) framework is application agnostic. Application-specific adaptations extend that framework. Previous work has focused on HTTP and work for SMTP is in progress. These protocols differ fundamentally in the way data flows, and it turns out that existing OPES requirements and IAB considerations for OPES need to be reviewed with regards to how well they fit for SMTP adaptation. This document analyzes aspects about the integrity of SMTP and mail message adaptation by OPES systems and about privacy and security issues when the OPES framework is adapted to SMTP. It also lists requirements that must be considered when creating the "SMTP adaptation with OPES" document.

The intent of this document is to capture this information before the current OPES working group shuts down. This is to provide input for subsequent working groups or individual contributors that may pick up the OPES/SMTP work at a later date. This memo provides information for the Internet community.')
2015-10-14
(System) Notify list changed from opes-chairs@ietf.org to (None)
2007-05-28
Amy Vezza State Changes to RFC Published from RFC Ed Queue by Amy Vezza
2007-05-28
Amy Vezza [Note]: 'RFC 4902' added by Amy Vezza
2007-05-25
(System) RFC published