Totally agree.

Regardless of my position on this specific draft, if it has been declared
"no consensus", now it not wise to go forward, declare consensus and
accept the appeal.

Credibility is first.

Regards,
Jordi






-----Mensaje original-----
De: Noel Chiappa <j...@mercury.lcs.mit.edu>
Responder a: <j...@mercury.lcs.mit.edu>
Fecha: Tue,  5 Jul 2011 10:44:29 -0400 (EDT)
Para: <ietf@ietf.org>, <v6...@ietf.org>
CC: <j...@mercury.lcs.mit.edu>
Asunto: Re: [v6ops] draft-ietf-v6ops-6to4-to-historic

>    > From: Ronald Bonica <rbon...@juniper.net>
>
>    >>> I think that I get it. There is no IETF consensus regarding the
>    >>> compromise proposed below. ...
>
>    >> But there is no rough consensus to do that either.
>
>    > That is the claim of an appeal on the table. Let's run the appeal
>    > process and figure out whether that claim is valid.
>
>Sorry, this makes no sense.
>
>You can't go ahead with draft-ietf-v6ops-6to4-to-historic if there is no
>basic consensus in the IETF as a whole to do so - and your previous
>declaration (on Saturday) basically accepted that there was no such basic
>consensus (otherwise why withdraw the ID).
>
>So now there is going to be a reversal, and the document is going to go
>ahead
>- i.e. you must now be taking the position that there _is_ basic
>consensus in
>the IETF (without which you could not proceed the ID).
>
>The effect of this sort of thing on the reputation of I* should be obvious
>to all.
>
>       Noel
>_______________________________________________
>v6ops mailing list
>v6...@ietf.org
>https://www.ietf.org/mailman/listinfo/v6ops



**********************************************
IPv4 is over
Are you ready for the new Internet ?
http://www.consulintel.es
The IPv6 Company

This electronic message contains information which may be privileged or 
confidential. The information is intended to be for the use of the 
individual(s) named above. If you are not the intended recipient be aware that 
any disclosure, copying, distribution or use of the contents of this 
information, including attached files, is prohibited.



_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www.ietf.org/mailman/listinfo/ietf

Reply via email to