RE: OCP transport vote, commitment

> -----Original Message-----
> From: owner-ietf-openproxy(_at_)mail(_dot_)imc(_dot_)org
> [mailto:owner-ietf-openproxy(_at_)mail(_dot_)imc(_dot_)org]On Behalf Of jfcm
> Sent: Monday, May 12, 2003 4:58 AM
> To: Oskar Batuner; ietf-openproxy(_at_)imc(_dot_)org
> Subject: RE: OCP transport vote, commitment
>
>
>
> At 14:43 11/05/03, Oskar Batuner wrote:
> > My vote is:
> >
> >         ICAP/1.1:        0%
> >         OCP/OCPTRAN:    80%
> >         OCP/BEEP:       20%
> >
> > 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
> > in OCPTRAN.
> 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.
"We do not believe in voting. We believe in rough consensus and in 
running code."  - Harald Alvestrand