Re: OPES and Email
Tony Hansen <[email protected]>
| Newsgroups | gmane.ietf.smtp,gmane.ietf.rfc822 |
|---|---|
| Message-ID | <[email protected]> |
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 An edge service is a service plugged into the side of an existing service. For example, real time call outs from within HTTP servers or SMTP servers to virus scanners or spam blockers are examples of edge services. An open pluggable edge service is an edge service that meets certain criteria that allows them to be swapped in and out. For example, you could swap out company X's virus scanner and replace it with company Y's. Or cascade a series of virus scanners from multiple sources. The OPES framework has defined such a set of criteria for edge services. In addition, the OPES framework includes a profile for how these services could be plugged into an HTTP server. The RFCs 3238, 3752, 3835-3838 and 4037 all discuss OPES. In particular, RFC 3752 covers a variety of use cases that are fairly generic. The internet draft OPES SMTP Use Cases expands on the core set with use cases that could be considered more specific to email. I hope this helps. Tony Hansen [email protected] Frank Ellermann wrote: > Tony Hansen wrote: > >> I don't know if you saw the recent I-D documents that came out, >> entitled OPES SMTP Use Cases >> draft-ietf-opes-smtp-use-cases-02.txt). > > Yes, I saw the announcement, and then decided that "somebody" will > probably explain what OPES is, I've not the faintest idea. > >> The Open Pluggable Edge Services (OPES) framework is application >> agnostic. > > Yes, and I'm OPES agnostic... ;-) So what is it ? Bye, Frank -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (MingW32) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFCzepPxsSylYhzrRYRAntxAJsFnajq8/Upce1W6VCBMBR6HQXpvwCeJ3MW xv2Lgx2KzGC7c5SpodgvxYc= =apK2 -----END PGP SIGNATURE-----