idnits 2.17.1 draft-iab-opes-01.txt: Skipping this file; it looks like a tombstone file to me. -------------------------------------------------------------------------------- 1 A new Request for Comments is now available in online RFC libraries. 3 RFC 3238 5 Title: IAB Architectural and Policy Considerations for 6 Open Pluggable Edge Services 7 Author(s): Internet Architecture Board (IAB), 8 S. Floyd, L. Daigle 9 Status: Informational 10 Date: January 2002 11 Mailbox: iab@iab.org 12 Pages: 17 13 Characters: 42336 14 Updates/Obsoletes/SeeAlso: NONE 16 I-D Tag: draft-iab-opes-01.txt 18 URL: ftp://ftp.rfc-editor.org/in-notes/rfc3238.txt 20 This document includes comments and recommendations by the IAB on 21 some architectural and policy issues related to the chartering of 22 Open Pluggable Edge Services (OPES) in the IETF. OPES are services 23 that would be deployed at application-level intermediaries in the 24 network, for example, at a web proxy cache between the origin server 25 and the client. These intermediaries would transform or filter 26 content, with the explicit consent of either the content provider or 27 the end user. 29 This document is a product of the Internet Architecture Board. 31 This memo provides information for the Internet community. It does 32 not specify an Internet standard of any kind. Distribution of this 33 memo is unlimited. 35 This announcement is sent to the IETF list and the RFC-DIST list. 36 Requests to be added to or deleted from the IETF distribution list 37 should be sent to IETF-REQUEST@IETF.ORG. Requests to be 38 added to or deleted from the RFC-DIST distribution list should 39 be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. 41 Details on obtaining RFCs via FTP or EMAIL may be obtained by sending 42 an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 43 help: ways_to_get_rfcs. For example: 45 To: rfc-info@RFC-EDITOR.ORG 46 Subject: getting rfcs 48 help: ways_to_get_rfcs 50 Requests for special distribution should be addressed to either the 51 author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless 52 specifically noted otherwise on the RFC itself, all RFCs are for 53 unlimited distribution.echo 54 Submissions for Requests for Comments should be sent to 55 RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC 56 Authors, for further information.