IETF Logo Mail Archive

Re: On harassment at IETF

S Moonesamy <sm+ietf@elandsys.com> Sun, 31 March 2019 08:11 UTC

Return-Path: <sm@elandsys.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 221801200B6 for <ietf@ietfa.amsl.com>; Sun, 31 Mar 2019 01:11:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.7
X-Spam-Level:
X-Spam-Status: No, score=-1.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=opendkim.org header.b=pKVHt4xO; dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=elandsys.com header.b=dJzNrsYK
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YLUy5DjRtijU for <ietf@ietfa.amsl.com>; Sun, 31 Mar 2019 01:11:41 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id EE6E412008F for <ietf@ietf.org>; Sun, 31 Mar 2019 01:11:40 -0700 (PDT)
Received: from DESKTOP-K6V9C2L.elandsys.com ([197.224.146.192]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id x2V8BScB003885 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 31 Mar 2019 01:11:37 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1554019899; x=1554106299; bh=hf9ajVN9Eelzub4JoQy7GxQVtva8eK+NGiD3OTVwEPU=; h=Date:To:From:Subject:In-Reply-To:References; b=pKVHt4xO3ESNA4bX+Q5omxsPLS/lfJcT4lkcdkGaWMGQ2/8fEFsHKXgHJxI+hWTQe CY1WLMveW59W9l0mnmk+UmpmVbxojNbewS3RLU1XY9nzOa8JaeTMHHOgc2UJpDgFG/ so9XY7btdAN4Oi3g6Gi3LqG4dwuHt3c14aiBBGdU=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1554019899; x=1554106299; i=@elandsys.com; bh=hf9ajVN9Eelzub4JoQy7GxQVtva8eK+NGiD3OTVwEPU=; h=Date:To:From:Subject:In-Reply-To:References; b=dJzNrsYKf/GPcu3YreS/ePWAjLzx7q3FFgM6mIX8HI7z+6Qe+d2+izlDFkiF5KxhP ASe9P2HnrnTu5CeOqRyh14mtoHqnBBPk6tCsV/yT57+TtH5XJNGAwXH3ens/60xHer xNKVpeT0+nTm69p/bNHNSSmPY4y2I3ZdP2eBeIqA=
Message-Id: <6.2.5.6.2.20190330233421.11167ae8@elandnews.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Sun, 31 Mar 2019 01:09:40 -0700
To: "Dr. Pala" <madwolf@openca.org>, ietf@ietf.org
From: S Moonesamy <sm+ietf@elandsys.com>
Subject: Re: On harassment at IETF
In-Reply-To: <3c47fdfd-4207-fac6-cfbe-68fdc7a0ac58@openca.org>
References: <91e75af7-03f9-7565-5a9f-26f5f7bc9f29@openca.org> <FCE33107-1AF5-47B7-9F46-3BDD281E4DEB@live555.com> <79b0861a-b309-876a-47c7-7961e8fbf961@openca.org> <3c47fdfd-4207-fac6-cfbe-68fdc7a0ac58@openca.org>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/naVOBpkJw0Ar-J-v55mKgttPKbU>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.29
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: <https://mailarchive.ietf.org/arch/browse/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: Sun, 31 Mar 2019 08:11:42 -0000

Dear Dr. Pala,

I read the emails which you sent about the topic.  I was somewhat 
surprised by the initial email as there are procedures specified in 
RFC 7776 [1] to address the topic.  It is expected that those 
procedures are well-advertised so that a person who encountered such 
a problem can contact someone who can help him/her.  Written 
communication is not the ideal means of communication to understand 
what happened.  It could also be awkward for the person to do 
that.  I hope that you have already received a positive response from 
the person(s) responsible for the RFC 7776 procedures.

Regards,
S. Moonesamy

1. https://www.rfc-editor.org/rfc/rfc7776.txt

v2.23.0 | Report a Bug | By Email