RFC 3238: IAB Architectural and Policy Considerations for Open Pluggable Edge Services
In plain English — editorial summary, not part of the RFC
This document includes comments and recommendations by the IAB on some architectural and policy issues related to the chartering of Open Pluggable Edge Services (OPES) in the IETF. OPES are services that would be deployed at application-level intermediaries in the network, for example, at a web proxy cache between the origin server and the client. These intermediaries would transform or filter content, with the explicit consent of either the content provider or the end user. This memo provides information for the Internet community.
Document record
- Document ID
- RFC3238
- Published
- January 2002
- Authors
- S. Floyd; L. Daigle
- Status
- INFORMATIONAL
- Stream
- IAB
- Area
- —
- Pages
- 17
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 2902Overview of the 1998 IAB Routing WorkshopCurrent
August 2000
- RFC 2101IPv4 Address Behaviour TodayCurrent
February 1997
- RFC 3177IAB/IESG Recommendations on IPv6 Address Allocations to SitesObsoleted
September 2001
- RFC 3002Overview of 2000 IAB Wireless Internetworking WorkshopCurrent
December 2000
- RFC 2727IAB and IESG Selection, Confirmation, and Recall Process: Operation of the Nominating and Recall CommitteesObsoleted
February 2000
- RFC 2282IAB and IESG Selection, Confirmation, and Recall Process: Operation of the Nominating and Recall CommitteesObsoleted
February 1998
- RFC 2130The Report of the IAB Character Set Workshop held 29 February - 1 March, 1996Updated
April 1997
- RFC 2027IAB and IESG Selection, Confirmation, and Recall Process: Operation of the Nominating and Recall CommitteesObsoleted
October 1996
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?