RFC 3897: Open Pluggable Edge Services (OPES) Entities and End Points Communication
In plain English — editorial summary, not part of the RFC
This memo documents tracing and non-blocking (bypass) requirements for Open Pluggable Edge Services (OPES). This memo provides information for the Internet community.
Document record
- Document ID
- RFC3897
- Published
- September 2004
- Authors
- A. Barbir
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- app
- Pages
- 14
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 9197Data Fields for In Situ Operations, Administration, and Maintenance (IOAM)Current
May 2022
- RFC 9378In Situ Operations, Administration, and Maintenance (IOAM) DeploymentCurrent
April 2023
- RFC 9452Network Service Header (NSH) Encapsulation for In Situ OAM (IOAM) DataCurrent
August 2023
- RFC 9551Framework of Operations, Administration, and Maintenance (OAM) for Deterministic Networking (DetNet)Current
March 2024
- RFC 3888Message Tracking Model and RequirementsCurrent
September 2004
- RFC 3887Message Tracking Query ProtocolUpdated
September 2004
- RFC 3886An Extensible Message Format for Message Tracking ResponsesCurrent
September 2004
- RFC 3885SMTP Service Extension for Message TrackingCurrent
September 2004
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?