@techreport{elson-opes-icap-01,
    number =    {draft-elson-opes-icap-01},
    type =      {Internet-Draft},
    institution =   {Internet Engineering Task Force},
    publisher = {Internet Engineering Task Force},
    note =      {Work in Progress},
    url =       {https://datatracker.ietf.org/doc/draft-elson-opes-icap/01/},
    author =    {Jeremy Elson},
    title =     {{ICAP the Internet Content Adaptation Protocol}},
    pagetotal = 31,
    year =      2001,
    month =     feb,
    day =       28,
    abstract =  {ICAP, the Internet Content Adaptation Protocol, is part of an evolving architecture that facilitates better distribution and caching for the web. ICAP is, in essence, a lightweight protocol for executing a 'remote procedure call' on HTTP messages. That is, it allows ICAP clients to pass HTTP messages to ICAP servers for 'adaptation' -- some sort of transformation or other processing. The server executes its transformation service on messages and sends back responses to the client, usually with modified messages. The adapted messages may be either HTTP requests or HTTP responses.},
}