Re: Sergeant at arms: please deal with mars.techno.cat@gmail.com

Abdussalam Baryun <abdussalambaryun@gmail.com> Tue, 22 October 2013 20:42 UTC

Return-Path: <abdussalambaryun@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 43C7211E832A for <ietf@ietfa.amsl.com>; Tue, 22 Oct 2013 13:42:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.53
X-Spam-Level:
X-Spam-Status: No, score=-2.53 tagged_above=-999 required=5 tests=[AWL=0.069, BAYES_00=-2.599, HTML_MESSAGE=0.001, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id iYxQwbqajhRw for <ietf@ietfa.amsl.com>; Tue, 22 Oct 2013 13:42:08 -0700 (PDT)
Received: from mail-pd0-x22b.google.com (mail-pd0-x22b.google.com [IPv6:2607:f8b0:400e:c02::22b]) by ietfa.amsl.com (Postfix) with ESMTP id 5F54621E8099 for <ietf@ietf.org>; Tue, 22 Oct 2013 13:40:12 -0700 (PDT)
Received: by mail-pd0-f171.google.com with SMTP id z10so11005083pdj.16 for <ietf@ietf.org>; Tue, 22 Oct 2013 13:40:03 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=TgMBJTKBqvx+pNcRgaUOLN88Nd78NK2hdIWcC6r4CJg=; b=CL2HslzSunaEjlWpNom0/smQ7uklrRsCQxI05dZsOlQHXFmOFHCDID1UiBqJU7JkT8 B/Tj2apD/ZpKIfx4w/KTMaBt9IwRBuQ6zgGW+FecmBvxRvdYQ6wlwCisObiSbjjueFaA KxlMUzbod05eFqQAP9LHX1CDvWCm4w9TDwHN4ZAFgc/R+th5BdhPDYwfngvJ8P6U9pBQ wR5HVuUNKhBNeOQaQuqKJ0UIWIAyy7Z8QZSfwbkllOzdc3+pOJcG18zAsPEU+aVOXwg1 ZHIxdVhW/erXzCXs72BjS3jETvQZAGwPjA67Ivc9sdzVpci2uEnwqkA/Lz2vZY6zYpez uLzg==
MIME-Version: 1.0
X-Received: by 10.66.165.106 with SMTP id yx10mr9005047pab.159.1382474403868; Tue, 22 Oct 2013 13:40:03 -0700 (PDT)
Received: by 10.69.8.5 with HTTP; Tue, 22 Oct 2013 13:40:03 -0700 (PDT)
In-Reply-To: <61EE8145-2184-44C1-8163-424F97F8286C@piuha.net>
References: <5262FB95.8080500@gmail.com> <CAK41CSRKhD9W5WWm3xBJeb4U8Q6TbfG1EHnY_0BN7fC1QvO=iA@mail.gmail.com> <52657B0B.3080701@gmail.com> <m21u3d5zvo.wl%randy@psg.com> <5266B4A4.9020301@dcrocker.net> <5266C6CA.30900@gmail.com> <0B5A250AE70FD6B21DD3CF4C@JcK-HP8200.jck.com> <5266CE7C.2020503@gmail.com> <61EE8145-2184-44C1-8163-424F97F8286C@piuha.net>
Date: Tue, 22 Oct 2013 21:40:03 +0100
Message-ID: <CADnDZ88ZaSU=VR6-xCR5vEWXJX=VzMg9a0m7owQP5CbGeu_-RQ@mail.gmail.com>
Subject: Re: Sergeant at arms: please deal with mars.techno.cat@gmail.com
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: ietf <ietf@ietf.org>
Content-Type: multipart/alternative; boundary="047d7b86c342c0f5f104e95a6750"
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
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>
X-List-Received-Date: Tue, 22 Oct 2013 20:42:09 -0000

>
>
>
As I noticed that f2f meetings should present their name before talking so
it is good no anonymous talks. I think there is a hidden problem in
anonymous posting, how can I network with someone I cannot trust because
he/she does not trust participants by sharing identity. I post with a
known name but get some participants discredits me with that name (a reason
why some people hide real names), so they taking things to personal or
trying to make poster become change to anonymous or become with no trust of
the IETF system.

All should respect others, so we can work together with more trust. I am
against IETF allowing workers becoming anonymous because no one will trust
it or even follow it. I started to be afraid that most IETF management or
participants or authors may have registered without their real name.

An anonymous poster should go through a process with a known participant to
proof that he/she is not attacking the system. That participant may sponsor
the anonymous poster to enable the continue of anonymous remote
participation.

AB