RFC 4236: HTTP Adaptation with Open Pluggable Edge Services (OPES)

Open Pluggable Edge Services (OPES) framework documents several application-agnostic mechanisms such as OPES tracing, OPES bypass, and OPES callout protocol.…

Read RFC 4236 on the RFC Editor

Outgoing relationships (10 related RFCs)

Normative reference — RFC 2616: Hypertext Transfer Protocol -- HTTP/1.1
Normative reference — RFC 3897: Open Pluggable Edge Services (OPES) Entities and End Points Communication
Normative reference — RFC 4037: Open Pluggable Edge Services (OPES) Callout Protocol (OCP) Core
Informative reference — RFC 3238: IAB Architectural and Policy Considerations for Open Pluggable Edge Services
Informative reference — RFC 3835: An Architecture for Open Pluggable Edge Services (OPES)
Informative reference — RFC 3752: Open Pluggable Edge Services (OPES) Use Cases and Deployment Scenarios
Informative reference — RFC 3837: Security Threats and Risks for Open Pluggable Edge Services (OPES)
Informative reference — RFC 3838: Policy, Authorization, and Enforcement Requirements of the Open Pluggable Edge Services (OPES)
Informative reference — RFC 3914: Open Pluggable Edge Services (OPES) Treatment of IAB Considerations
Informative reference — RFC 3836: Requirements for Open Pluggable Edge Services (OPES) Callout Protocols

Incoming relationships (2 related RFCs)

Normatively referenced by — RFC 4496: Open Pluggable Edge Services (OPES) SMTP Use Cases
Informatively referenced by — RFC 4902: Integrity, Privacy, and Security in Open Pluggable Edge Services (OPES) for SMTP