RFC 3897: Open Pluggable Edge Services (OPES) Entities and End Points Communication

This memo documents tracing and non-blocking (bypass) requirements for Open Pluggable Edge Services (OPES). This memo provides information for the Internet…

Read RFC 3897 on the RFC Editor

Outgoing relationships (6 related RFCs)

Normative reference — RFC 3835: An Architecture for Open Pluggable Edge Services (OPES)
Normative reference — RFC 3837: Security Threats and Risks for Open Pluggable Edge Services (OPES)
Normative reference — RFC 3838: Policy, Authorization, and Enforcement Requirements of the Open Pluggable Edge Services (OPES)
Informative reference — RFC 3238: IAB Architectural and Policy Considerations for Open Pluggable Edge Services
Informative reference — RFC 2804: IETF Policy on Wiretapping
Informative reference — RFC 3752: Open Pluggable Edge Services (OPES) Use Cases and Deployment Scenarios

Incoming relationships (4 related RFCs)

Normatively referenced by — RFC 3914: Open Pluggable Edge Services (OPES) Treatment of IAB Considerations
Normatively referenced by — RFC 4236: HTTP Adaptation with Open Pluggable Edge Services (OPES)
Informatively referenced by — RFC 4037: Open Pluggable Edge Services (OPES) Callout Protocol (OCP) Core
Informatively referenced by — RFC 4902: Integrity, Privacy, and Security in Open Pluggable Edge Services (OPES) for SMTP