Re: Document Action: 'Integrity, privacy and security in OPES for SMTP' to Informational RFC

This is a multi-part message in MIME format.
--------------020601080303000305060408
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

Thanks to everyone in the OPES WG for your work in getting this document
put to bed.

This concludes the chartered work of the Working Group. Anyone who
wishes to carry on the work of the WG is encouraged to do so using
individual submissions. The mailing list will remain open and available
for anyone to use to discuss such individual internet drafts.

Thanks again to everyone for the fine work that's been accomplished over
these past many years:

  RFC 3752  2002-08  OPES Use Cases and Deployment Scenarios
  RFC 3835  2002-12  An Architecture for OPES
  RFC 3836  2002-12  Requirements for OPES Callout Protocols
  RFC 3837  2003-12  Security Threats and Risks for OPES
  RFC 3838  2004-04  Policy, Authorization & Enforcement Req'ts of OPES
  RFC 3897  2004-05  OPES entities and end points communication
  RFC 3914  2004-04  OPES Treatment of IAB Considerations
  RFC 4037  2004-05  OPES Callout Protocol (OCP) Core
  RFC 4236  2005-11  HTTP Adaptation with OPES
  RFC 4496  2006-01  OPES SMTP Use Cases
  RFC ????  2007-02  Integrity, privacy and security in OPES for SMTP

Your OPES co-chairs,

	Markus Hofmann & Tony Hansen

The IESG wrote:
> The IESG has approved the following document:
> 
> - 'Integrity, privacy and security in OPES for SMTP '
>    <draft-ietf-opes-smtp-security-03.txt> as an Informational RFC
> 
> This document is the product of the Open Pluggable Edge Services Working 
> Group. 



--------------020601080303000305060408--