idnits 2.17.1 draft-elson-icap-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 3507 5 Title: Internet Content Adaptation Protocol (ICAP) 6 Author(s): J. Elson, A. Cerpa 7 Status: Informational 8 Date: April 2003 9 Mailbox: jelson@cs.ucla.edu, cerpa@cs.ucla.edu 10 Pages: 49 11 Characters: 98772 12 Updates/Obsoletes/SeeAlso: None 14 I-D Tag: draft-elson-icap-01.txt 16 URL: ftp://ftp.rfc-editor.org/in-notes/rfc3507.txt 18 ICAP, the Internet Content Adaption Protocol, is a protocol aimed 19 at providing simple object-based content vectoring for HTTP 20 services. ICAP is, in essence, a lightweight protocol for 21 executing a "remote procedure call" on HTTP messages. It allows ICAP 22 clients to pass HTTP messages to ICAP servers for some sort of 23 transformation or other processing ("adaptation"). The server 24 executes its transformation service on messages and sends back 25 responses to the client, usually with modified messages. Typically, 26 the adapted messages are either HTTP requests or HTTP responses. 28 This memo provides information for the Internet community. It does 29 not specify an Internet standard of any kind. Distribution of this 30 memo is unlimited. 32 This announcement is sent to the IETF list and the RFC-DIST list. 33 Requests to be added to or deleted from the IETF distribution list 34 should be sent to IETF-REQUEST@IETF.ORG. Requests to be 35 added to or deleted from the RFC-DIST distribution list should 36 be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. 38 Details on obtaining RFCs via FTP or EMAIL may be obtained by sending 39 an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 40 help: ways_to_get_rfcs. For example: 42 To: rfc-info@RFC-EDITOR.ORG 43 Subject: getting rfcs 45 help: ways_to_get_rfcs 47 Requests for special distribution should be addressed to either the 48 author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless 49 specifically noted otherwise on the RFC itself, all RFCs are for 50 unlimited distribution.echo 51 Submissions for Requests for Comments should be sent to 52 RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC 53 Authors, for further information.