IETF Logo Mail Archive

Re: Possible RFC 3683 PR-action

Stephane Bortzmeyer <bortzmeyer@nic.fr> Tue, 01 April 2008 20:43 UTC

Return-Path: <ietf-bounces@ietf.org>
X-Original-To: ietf-archive@megatron.ietf.org
Delivered-To: ietfarch-ietf-archive@core3.amsl.com
Received: from core3.amsl.com (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 4555228C264; Tue, 1 Apr 2008 13:43:10 -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 4E6723A6C47 for <ietf@core3.amsl.com>; Tue, 1 Apr 2008 13:43:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
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 NyRjeWt3WJXH for <ietf@core3.amsl.com>; Tue, 1 Apr 2008 13:43:08 -0700 (PDT)
Received: from mail.bortzmeyer.org (aetius.bortzmeyer.org [217.70.190.232]) by core3.amsl.com (Postfix) with ESMTP id 785763A6EEE for <ietf@ietf.org>; Tue, 1 Apr 2008 13:43:08 -0700 (PDT)
Received: by mail.bortzmeyer.org (Postfix, from userid 10) id C1E8131D6C; Tue, 1 Apr 2008 22:43:04 +0200 (CEST)
Received: by mail.sources.org (Postfix, from userid 1000) id 7C16E11685; Tue, 1 Apr 2008 22:41:08 +0200 (CEST)
Date: Tue, 01 Apr 2008 22:41:08 +0200
From: Stephane Bortzmeyer <bortzmeyer@nic.fr>
To: ietf@ietf.org
Subject: Re: Possible RFC 3683 PR-action
Message-ID: <20080401204108.GA4139@sources.org>
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>
Mime-Version: 1.0
Content-Disposition: inline
In-Reply-To: <8EFB68EAE061884A8517F2A755E8B60A02C693ACF4@NA-EXMSG-W601.wingroup.windeploy.ntdev.microsoft.com>
X-Transport: UUCP rules
X-Operating-System: Debian GNU/Linux 3.1
User-Agent: Mutt/1.5.9i
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 Sun, Mar 23, 2008 at 08:45:19AM -0700,
 Christian Huitema <huitema@windows.microsoft.com> wrote 
 a message of 12 lines which said:

> Does the IETF have a policy regarding misrepresented identities?

For instance, I claim that the person mentioned in section 10 of RFC
5242 may be actually the same person who is the target of a PR-action,
with just a small modification of his name. If this is true, he cannot
post on IETF mailing lists and should be banned of "Acknowledgments"
sections as well!


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

v2.23.0 | Report a Bug | By Email