RFC 4496: Open Pluggable Edge Services (OPES) SMTP Use Cases
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. This document describes OPES SMTP use cases and deployment scenarios in preparation for SMTP adaptation with OPES. This memo provides information for the Internet community.
Document record
- Document ID
- RFC4496
- Published
- May 2006
- Authors
- M. Stecher; A. Barbir
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- app
- Pages
- 12
- Also known as
- —
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 4510Lightweight Directory Access Protocol (LDAP): Technical Specification Road MapCurrent
June 2006
- RFC 4511Lightweight Directory Access Protocol (LDAP): The ProtocolCurrent
June 2006
- RFC 4512Lightweight Directory Access Protocol (LDAP): Directory Information ModelsCurrent
June 2006
- RFC 4513Lightweight Directory Access Protocol (LDAP): Authentication Methods and Security MechanismsUpdated
June 2006
- RFC 4514Lightweight Directory Access Protocol (LDAP): String Representation of Distinguished NamesCurrent
June 2006
- RFC 4515Lightweight Directory Access Protocol (LDAP): String Representation of Search FiltersCurrent
June 2006
- RFC 4516Lightweight Directory Access Protocol (LDAP): Uniform Resource LocatorCurrent
June 2006
- RFC 4517Lightweight Directory Access Protocol (LDAP): Syntaxes and Matching RulesCurrent
June 2006
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?