Re: Possible RFC 3683 PR-action
Stephane Bortzmeyer <bortzmeyer@nic.fr> Tue, 25 March 2008 07:55 UTC
Return-Path: <ietf-bounces@ietf.org>
X-Original-To: ietfarch-ietf-archive@core3.amsl.com
Delivered-To: ietfarch-ietf-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 891D428C3F3; Tue, 25 Mar 2008 00:55:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.472
X-Spam-Level:
X-Spam-Status: No, score=-100.472 tagged_above=-999 required=5 tests=[AWL=-0.385, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_EQ_FR=0.35, HELO_MISMATCH_ORG=0.611, RDNS_NONE=0.1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id w6oWWz5m4Cbd; Tue, 25 Mar 2008 00:55:43 -0700 (PDT)
Received: from core3.amsl.com (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 28DAF28C2CC; Tue, 25 Mar 2008 00:55:43 -0700 (PDT)
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 578463A6935 for <ietf@core3.amsl.com>; Tue, 25 Mar 2008 00:55:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OWmAVtxnmOl9 for <ietf@core3.amsl.com>; Tue, 25 Mar 2008 00:55:38 -0700 (PDT)
Received: from mx2.nic.fr (mx2.nic.fr [192.134.4.11]) by core3.amsl.com (Postfix) with ESMTP id DA2673A6B54 for <ietf@ietf.org>; Tue, 25 Mar 2008 00:55:37 -0700 (PDT)
Received: from mx2.nic.fr (localhost [127.0.0.1]) by mx2.nic.fr (Postfix) with SMTP id 04DA21C012E; Tue, 25 Mar 2008 08:53:16 +0100 (CET)
Received: from relay2.nic.fr (relay2.nic.fr [192.134.4.163]) by mx2.nic.fr (Postfix) with ESMTP id F36AB1C0128; Tue, 25 Mar 2008 08:53:15 +0100 (CET)
Received: from bortzmeyer.nic.fr (batilda.nic.fr [192.134.4.69]) by relay2.nic.fr (Postfix) with ESMTP id F06B158EBC5; Tue, 25 Mar 2008 08:53:15 +0100 (CET)
Date: Tue, 25 Mar 2008 08:53:15 +0100
From: Stephane Bortzmeyer <bortzmeyer@nic.fr>
To: Harald Tveit Alvestrand <harald@alvestrand.no>
Subject: Re: Possible RFC 3683 PR-action
Message-ID: <20080325075315.GA8111@nic.fr>
References: <002801c88988$bba6fda0$6801a8c0@oemcomputer> <004101c88ac1$f57d2600$6801a8c0@oemcomputer> <5b0cbc7c0803201738s6138a1a4m2fbb546286a9c2ed@mail.gmail.com> <47e4022e.14025a0a.2c46.2519SMTPIN_ADDED@mx.google.com> <5b0cbc7c0803220222x5b345773oe11dcadc448b7635@mail.gmail.com> <20080322193659.527613A692F@core3.amsl.com> <8EFB68EAE061884A8517F2A755E8B60A02C693ACF4@NA-EXMSG-W601.wingroup.windeploy.ntdev.microsoft.com> <20080324153956.0FF6A28C459@core3.amsl.com> <47E87ABF.9020002@alvestrand.no>
MIME-Version: 1.0
Content-Disposition: inline
In-Reply-To: <47E87ABF.9020002@alvestrand.no>
X-Operating-System: Debian GNU/Linux 4.0
X-Kernel: Linux 2.6.18-6-686 i686
Organization: NIC France
X-URL: http://www.nic.fr/
User-Agent: Mutt/1.5.13 (2006-08-11)
Cc: Christian Huitema <huitema@windows.microsoft.com>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.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://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
On Tue, Mar 25, 2008 at 05:08:31AM +0100, Harald Tveit Alvestrand <harald@alvestrand.no> wrote a message of 28 lines which said: > we had this exact problem with the many identities of "Jeff > Williams"; he had enough pseudo-personalities on the list that he > would sometimes claim to have a majority, jut from his own postings. Since IETF does not vote, it is certainly not an issue here? _______________________________________________ IETF mailing list IETF@ietf.org https://www.ietf.org/mailman/listinfo/ietf
- Re: [Ltru] Possible RFC 3683 PR-action LB
- Re: [Ltru] Possible RFC 3683 PR-action Randy Presuhn
- Re: [Ltru] Possible RFC 3683 PR-action Russ Housley
- Re: [Ltru] Possible RFC 3683 PR-action LB
- Re: [Ltru] Possible RFC 3683 PR-action Sam Hartman
- Re: Possible RFC 3683 PR-action Stephane Bortzmeyer
- Re: [Ltru] Possible RFC 3683 PR-action Russ Housley
- RE: [Ltru] Possible RFC 3683 PR-action Christian Huitema
- Re: [Ltru] Possible RFC 3683 PR-action Theodore Tso
- Re: [Ltru] Possible RFC 3683 PR-action Peter Constable
- Re: Possible RFC 3683 PR-action Stephane Bortzmeyer
- RE: [Ltru] Possible RFC 3683 PR-action Russ Housley
- RE: [Ltru] Possible RFC 3683 PR-action Wes Beebee (wbeebee)
- Re: [Ltru] Possible RFC 3683 PR-action LB
- RE: Possible RFC 3683 PR-action Tamir Melamed
- Re: [Ltru] Possible RFC 3683 PR-action Harald Tveit Alvestrand
- Re: Possible RFC 3683 PR-action Stephane Bortzmeyer
- Re: Possible RFC 3683 PR-action Theodore Tso
- Re: Possible RFC 3683 PR-action Frank Ellermann
- Re: Possible RFC 3683 PR-action Spencer Dawkins
- Re: Possible RFC 3683 PR-action David Conrad
- Re: Possible RFC 3683 PR-action Russ Housley
- Re: Possible RFC 3683 PR-action Theodore Tso
- Re: Possible RFC 3683 PR-action John Levine
- Re: Possible RFC 3683 PR-action Peter Constable
- Re: Possible RFC 3683 PR-action Noel Chiappa
- Re: Possible RFC 3683 PR-action Michael Thomas
- Re: Possible RFC 3683 PR-action Melinda Shore
- RE: [Ltru] Possible RFC 3683 PR-action Russ Housley
- Re: Possible RFC 3683 PR-action Noel Chiappa
- Re: Possible RFC 3683 PR-action Simon Josefsson
- RE: Possible RFC 3683 PR-action Peter Constable
- Re: Possible RFC 3683 PR-action Melinda Shore
- Re: [Ltru] Possible RFC 3683 PR-action Spencer Dawkins
- Re: Possible RFC 3683 PR-action Theodore Tso
- Re: Possible RFC 3683 PR-action Edward Lewis
- Re: Possible RFC 3683 PR-action Melinda Shore
- Re: Possible RFC 3683 PR-action Michael Thomas
- Re: Possible RFC 3683 PR-action Simon Josefsson
- Re: Possible RFC 3683 PR-action Joel Jaeggli
- Re: Possible RFC 3683 PR-action Edward Lewis
- Re: Possible RFC 3683 PR-action Frank Ellermann
- Re: Possible RFC 3683 PR-action Simon Josefsson
- Re: Possible RFC 3683 PR-action Russ Housley
- Re: Possible RFC 3683 PR-action Hallam-Baker, Phillip
- Re: Possible RFC 3683 PR-action Theodore Tso
- Re: Possible RFC 3683 PR-action Thierry Moreau
- Re: Possible RFC 3683 PR-action Simon Josefsson
- RE: Possible RFC 3683 PR-action Darryl (Dassa) Lynch
- Pseudonym side-effects [Re: Possible RFC 3683 PR-… Brian E Carpenter
- Corporate side-effect [Re: Possible RFC 3683 PR-a… Brian E Carpenter
- Re: Possible RFC 3683 PR-action Russ Housley
- Re: Possible RFC 3683 PR-action Simon Josefsson
- Re: Possible RFC 3683 PR-action stewe
- Re: Possible RFC 3683 PR-action Simon Josefsson
- Re: Possible RFC 3683 PR-action Noel Chiappa
- Re: Possible RFC 3683 PR-action Frank Ellermann
- Re: Possible RFC 3683 PR-action Doug Ewell
- Re: Possible RFC 3683 PR-action Stephan Wenger
- Re: Possible RFC 3683 PR-action Simon Josefsson
- Re: Possible RFC 3683 PR-action Simon Josefsson
- Re: Possible RFC 3683 PR-action Simon Josefsson
- Re: Possible RFC 3683 PR-action Bert
- Re: Possible RFC 3683 PR-action Stephane Bortzmeyer
- <draft-ietf-ipr-3978-incoming-08.txt> as a BCP (w… Frank Ellermann
- Re: Possible RFC 3683 PR-action John C Klensin
- RE: Possible RFC 3683 PR-action Hadriel Kaplan
- Re: Possible RFC 3683 PR-action Doug Ewell
- Re: Possible RFC 3683 PR-action John C Klensin
- Re: Possible RFC 3683 PR-action Stephane Bortzmeyer
- Re: Possible RFC 3683 PR-action Frank Ellermann
- Re: Possible RFC 3683 PR-action Brian E Carpenter
- Re: Possible RFC 3683 PR-action Harald Tveit Alvestrand
- Re: Possible RFC 3683 PR-action John C Klensin
- Re: Possible RFC 3683 PR-action Dean Anderson