Correcting error about RFC 3683 [Re: Fwd: Can the USA welcome IETF]
Brian E Carpenter <brc@zurich.ibm.com> Tue, 18 October 2005 08:49 UTC
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1ERn9g-0008AQ-Ra; Tue, 18 Oct 2005 04:49:08 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1ERn9e-0008AH-Nm for ietf@megatron.ietf.org; Tue, 18 Oct 2005 04:49:06 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA13887 for <ietf@ietf.org>; Tue, 18 Oct 2005 04:48:59 -0400 (EDT)
Received: from mtagate1.uk.ibm.com ([195.212.29.134]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1ERnL8-0005sA-KL for ietf@ietf.org; Tue, 18 Oct 2005 05:01:00 -0400
Received: from d06nrmr1407.portsmouth.uk.ibm.com (d06nrmr1407.portsmouth.uk.ibm.com [9.149.38.185]) by mtagate1.uk.ibm.com (8.12.10/8.12.10) with ESMTP id j9I8mokD204148 for <ietf@ietf.org>; Tue, 18 Oct 2005 08:48:52 GMT
Received: from d06av02.portsmouth.uk.ibm.com (d06av02.portsmouth.uk.ibm.com [9.149.37.228]) by d06nrmr1407.portsmouth.uk.ibm.com (8.12.10/NCO/VERS6.7) with ESMTP id j9I8moZO183548 for <ietf@ietf.org>; Tue, 18 Oct 2005 09:48:50 +0100
Received: from d06av02.portsmouth.uk.ibm.com (loopback [127.0.0.1]) by d06av02.portsmouth.uk.ibm.com (8.12.11/8.13.3) with ESMTP id j9I8mnr1012739 for <ietf@ietf.org>; Tue, 18 Oct 2005 09:48:49 +0100
Received: from sihl.zurich.ibm.com (sihl.zurich.ibm.com [9.4.16.232]) by d06av02.portsmouth.uk.ibm.com (8.12.11/8.12.11) with ESMTP id j9I8mnw0012730; Tue, 18 Oct 2005 09:48:49 +0100
Received: from zurich.ibm.com (sig-9-145-129-216.de.ibm.com [9.145.129.216]) by sihl.zurich.ibm.com (AIX4.3/8.9.3p2/8.9.3) with ESMTP id KAA46696; Tue, 18 Oct 2005 10:48:48 +0200
Message-ID: <4354B6EF.4080606@zurich.ibm.com>
Date: Tue, 18 Oct 2005 10:48:47 +0200
From: Brian E Carpenter <brc@zurich.ibm.com>
Organization: IBM
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.6) Gecko/20040113
X-Accept-Language: en, fr, de
MIME-Version: 1.0
To: Eduardo Mendez <eduamendez@gmail.com>
References: <8ee2e61f0510151351q11626c4fi@mail.gmail.com> <20051017134307.GB6043@nokia.com> <8ee2e61f0510170727o69743ccew@mail.gmail.com> <8ee2e61f0510170732u22a94cf1l@mail.gmail.com>
In-Reply-To: <8ee2e61f0510170732u22a94cf1l@mail.gmail.com>
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0fa76816851382eb71b0a882ccdc29ac
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org
Subject: Correcting error about RFC 3683 [Re: Fwd: Can the USA welcome IETF]
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
Eduardo, As you have already been told, this is not a prosecution. It is an internal procedure of the IETF, intended to protect our work against alleged disruption. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Brian E Carpenter IETF Chair Eduardo Mendez wrote: > I corrected error (underlined). Apologies. > > ---------- Forwarded message ---------- > From: Eduardo Mendez <eduamendez@gmail.com> > Date: 17-oct-2005 16:27 > Subject: Re: Can the USA welcome IETF (was: Last Call under RFC 3683 > concerning Dean Anderson (reissued)) > To: David Kessens <david.kessens@nokia.com> > > > 2005/10/17, David Kessens <david.kessens@nokia.com>: > >>I don't appreciate your suggestion that there could be another motive >>for reissuing the Last Call as the explanation in the note that >>accompanied the reissued Last Call message was quite clear in it's >>motivation. > > > Mr. David, > I am sorry you do not appreciate. > This is may be we do not share the same culture. > Every culture is to be respected. > > For your information. There are other countries when the procescutor > makes such a mistake it kils the procescution. This protects the > rights of the accused person. > > What you did increases the rights of the accusator. > You also are the victim, a law maker, a judge, and an appeal judge. > There are countries where you must ask another AD to procescute. > > There are countries where one is not allowed to say: > "Mr. X did wrong". > One must say: > "Mr. X seems to have done wrong". > Or Mr. X can sue you and win. > Everyone is innocent; except when the Judge said he is not. > And there is no appeal. > --------------------------- > Sorry: I mean. "and you stay innoncent until the end of the appeal". > > So, sorry if I hurt you. > > Eduardo Mendez > > >>The Last Call was reissued since the first message was inadvertently >>send to the the IETF announce list (where all other IETF Last Call >>messages are send) instead of the IETF discussion list as specified by >>RFC 3683. It seemed prudent to reset the Last Call timer to avoid any >>conflicts on whether the Last Call would have been of sufficient >>duration. > > > NB. You created a conflict on duration: it is too long. > "Sufficient" is a word like if you had made your mind as a Juge. > In true Justice lawyers would use it. > Your rights can be defended only if you defend the rights of everyone? > > _______________________________________________ > Ietf mailing list > Ietf@ietf.org > https://www1.ietf.org/mailman/listinfo/ietf > _______________________________________________ Ietf mailing list Ietf@ietf.org https://www1.ietf.org/mailman/listinfo/ietf
- Re: Can the USA welcome IETF Melinda Shore
- Can the USA welcome IETF (was: Last Call under RF… Eduardo Mendez
- Re: Can the USA welcome IETF (was: Last Call unde… Marc Manthey
- Was: Last Call under RFC 3683 [...] Frank Ellermann
- Re: Can the USA welcome IETF (was: Last Call unde… Spencer Dawkins
- Re: Can the USA welcome IETF (was: Last Call unde… David Kessens
- Re: Can the USA welcome IETF (was: Last Call unde… Spencer Dawkins
- Fwd: Can the USA welcome IETF (was: Last Call und… Eduardo Mendez
- Re: Fwd: Can the USA welcome IETF (was: Last Call… Noel Chiappa
- Re: Fwd: Can the USA welcome IETF (was: Last Call… Eduardo Mendez
- Re: Fwd: Can the USA welcome IETF (was: Last Call… Dave Singer
- Re: Fwd: Can the USA welcome IETF Scott W Brim
- Re: Fwd: Can the USA welcome IETF Eduardo Mendez
- Re: Fwd: Can the USA welcome IETF Eduardo Mendez
- Re: Fwd: Can the USA welcome IETF Scott W Brim
- Re: Fwd: Can the USA welcome IETF bill
- Re: Can the USA welcome IETF Ted Hardie
- Re: Can the USA welcome IETF william(at)elan.net
- Re: Can the USA welcome IETF Bill Manning
- Re: Fwd: Can the USA welcome IETF (was: Last Call… Alexis Turner
- Re: Fwd: Can the USA welcome IETF (was: Last Call… Dean Anderson
- Re: Fwd: Can the USA welcome IETF Dean Anderson
- Re: Fwd: Can the USA welcome IETF shogunx
- Re: Fwd: Can the USA welcome IETF (was: Last Call… Sandy Wills
- Re: Fwd: Can the USA welcome IETF Dean Anderson
- Re: Fwd: Can the USA welcome IETF Eduardo Mendez
- Re: Can the USA welcome IETF Eduardo Mendez
- Re: Fwd: Can the USA welcome IETF Sandy Wills
- Re: Fwd: Can the USA welcome IETF (was: Last Call… Doug Ewell
- Please be relevant and professional [Re: Fwd: Can… Brian E Carpenter
- Objective statements about behaviour [Re: Fwd: Ca… Brian E Carpenter
- Correcting error about RFC 3683 [Re: Fwd: Can the… Brian E Carpenter
- Correcting errors about IETF [Re: Fwd: Can the US… Brian E Carpenter
- Re: Correcting errors about IETF [Re: Fwd: Can th… JFC (Jefsey) Morfin
- Re: Correcting errors about IETF [Re: Fwd: Can th… Dean Anderson
- Re: Fwd: Can the USA welcome IETF (was: Last Call… Dean Anderson