Integrity, Privacy, and Security in Open Pluggable Edge Services (OPES) for SMTP
draft-ietf-opes-smtp-security-03

Approval announcement
Draft of message to be sent after approval:

Announcement

From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Cc: Internet Architecture Board <iab@iab.org>,
    RFC Editor <rfc-editor@rfc-editor.org>, 
    opes mailing list <ietf-openproxy@imc.org>, 
    opes chair <opes-chairs@tools.ietf.org>
Subject: Document Action: 'Integrity, privacy and security in 
         OPES for SMTP' to Informational RFC 

The IESG has approved the following document:

- 'Integrity, privacy and security in OPES for SMTP '
   <draft-ietf-opes-smtp-security-04.txt> as an Informational RFC

This document is the product of the Open Pluggable Edge Services Working 
Group. 

The IESG contact persons are Ted Hardie and Lisa Dusseault.

A URL of this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-opes-smtp-security-04.txt

Ballot Text

Technical Summary
 
    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 privacy and
   security issues when the OPES framework is adapted to SMTP and lists
   requirements that must be considered when creating the "SMTP
   adaptation with OPES" document.
 
Working Group Summary
 
 There was consensus to publish this document as a record of the
  working group's discussion.  There were comments on the IETF
  Last Call; an updated document was produced to address them.
 
Protocol Quality
 
 This document was reviewed for the IESG by Ted Hardie.

RFC Editor Note