RFC 4902: Integrity, Privacy, and Security in Open Pluggable Edge Services (OPES) for SMTP
In plain English — editorial summary, not part of the RFC
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.
Document record
- Document ID
- RFC4902
- Published
- May 2007
- Authors
- M. Stecher
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- app
- Pages
- 14
- Also known as
- —
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 4918HTTP Extensions for Web Distributed Authoring and Versioning (WebDAV)Updated
June 2007
- RFC 4947Address Resolution Mechanisms for IP Datagrams over MPEG-2 NetworksCurrent
July 2007
- RFC 4952Overview and Framework for Internationalized EmailObsoleted
July 2007
- RFC 4978The IMAP COMPRESS ExtensionCurrent
August 2007
- RFC 4991A Common Schema for Internet Registry Information Service Transfer ProtocolsCurrent
August 2007
- RFC 4992XML Pipelining with Chunks for the Internet Registry Information ServiceUpdated
August 2007
- RFC 4993A Lightweight UDP Transfer Protocol for the Internet Registry Information ServiceCurrent
August 2007
- RFC 4810Long-Term Archive Service RequirementsCurrent
March 2007
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?