At 14:43 11/05/03, Oskar Batuner wrote:
My vote is:
Initially I was much more in favor of BEEP. One of the main
reasons to shift my preferences to OCP/OCPTRAN is what Alex
calls "clone and modify" approach to reusing BEEP mechanisms
I will add thios to the page today. I have however a concern about that
you guys with better experience about IETF's way may respond.
This presupposes that BEEP mechanisms are carved in stone. What
if they update sometimes in a way OCPTRAN cannot or does not
want to support. What will be the real life impact (this was as stated
the reason why I kept interest in the BEEP solution too).
Here I'm in favor of reusing not just ideas, but the whole
sections of the BEEP protocol mechanisms.
As far as I understand Hilarie has objections against reusing
BEEP security mechanisms. If this is the case we should make a
decision on that too.
Incoming mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.478 / Virus Database: 275 - Release Date: 06/05/03