ietf-openproxy
[Top] [All Lists]

RE: New ICAP draft

2001-06-15 12:13:26

Translation from Italian to English ("bucate the situated one to us"),
to/from WAP, ad insertion, CDN selection, anonymization, virus
detection, etc.  All the things that the OPES examples talk about.

Hilarie

"Farag, Hany M (Hany)" <hfarag(_at_)lucent(_dot_)com> 06/15/01 01:05PM >>>

Hi all,
I don't understand what this suppose to mean in sec 7.3 in the ICAP draft:

"In contrast, ICAP is meant to cause changes in the semantics of messages
on their way from origin servers to users.  The criteria for a correctly
operating proxy are no longer as easy to define.  This will make
validation of ICAP services significantly more difficult. Incorrect
adaptations may lead to security vulnerabilities that were not present
in the unadapted content."

what changes are to be made? and why?

Thanks
Hany Farag 

-----Original Message-----
From: Alberto Cerpa [mailto:cerpa(_at_)lecs(_dot_)cs(_dot_)ucla(_dot_)edu] 
Sent: Friday, June 15, 2001 10:48 AM
To: ietf-openproxy(_at_)imc(_dot_)org 
Subject: New ICAP draft



Hi all,

Here is the draft we promised to deliver by the end of this week.  The
draft can be found at:
http://www.circlemud.org/~jelson/icap-1.72.txt 

We think it is pretty well polish and a cleaner version. We have tried
to incorporate in it all the comments we received from the list the last
couple of weeks. We hope to receive further comments form the group in
the following weeks.  Let us reemphasize that this is just a draft, and
we will probably update it as we receive feedback from the group.

The plan is to submit another draft to the list after we receive some
comments, then generate a new updated draft and submit it as an I-D.
After a couple of weeks for yet another round of comments and
suggestions we would like to finally submit it as an RFC Informational.

Comments are very welcome.

Regards,
Jer & Al.




<Prev in Thread] Current Thread [Next in Thread>