Re: [ietf-privacy] New Webiquette RFC

S Moonesamy <sm+ietf@elandsys.com> Sun, 17 April 2022 23:07 UTC

Return-Path: <sm@elandsys.com>
X-Original-To: ietf-privacy@ietfa.amsl.com
Delivered-To: ietf-privacy@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 838E03A18CA for <ietf-privacy@ietfa.amsl.com>; Sun, 17 Apr 2022 16:07:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.707
X-Spam-Level:
X-Spam-Status: No, score=-1.707 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, SPF_HELO_NONE=0.001, SPF_NONE=0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001] 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=elandsys.com
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 AQh8VPe_y-UP for <ietf-privacy@ietfa.amsl.com>; Sun, 17 Apr 2022 16:07:37 -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 9B1BB3A18C6 for <ietf-privacy@ietf.org>; Sun, 17 Apr 2022 16:07:36 -0700 (PDT)
Received: from DESKTOP-K6V9C2L.elandsys.com ([102.116.77.155]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id 23HN7KAP021816 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 17 Apr 2022 16:07:31 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1650236853; x=1650323253; i=@elandsys.com; bh=aan1BdnX6wzJFIGPNJSH2n3nm+YOM3MIqKVCraXFG6Y=; h=Date:To:From:Subject:In-Reply-To:References; b=QYfzFqT/NQUdDqLMt/Y/pUS+H3+WYdmiJrlfyJqq8pAx1XFFYUogbPY+MH5wE1RIK 0AqTU2nypnv+l0B3wfsmMRi6NipvDKtY4y+kSm9dRb4EwKUkakoT4WCiSFEDtZ21LI tm6fGfkTh0KIOBVc0OIHyLRv1pNzgN5ABHe0LBu4=
Message-Id: <6.2.5.6.2.20220417155032.16da2318@elandnews.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Sun, 17 Apr 2022 16:06:23 -0700
To: kate_9023+rfc@systemli.org, ietf-privacy@ietf.org
From: S Moonesamy <sm+ietf@elandsys.com>
In-Reply-To: <e27ce6c6-33aa-1acf-81c5-6ba430b4627d@systemli.org>
References: <9bb455e8-8dbb-9813-bc8e-6367c80b6063@systemli.org> <e27ce6c6-33aa-1acf-81c5-6ba430b4627d@systemli.org>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-privacy/1NdfShoSU2mrRU0ZWBAZWuq-ztA>
Subject: Re: [ietf-privacy] New Webiquette RFC
X-BeenThere: ietf-privacy@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Internet Privacy Discussion List <ietf-privacy.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-privacy>, <mailto:ietf-privacy-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-privacy/>
List-Post: <mailto:ietf-privacy@ietf.org>
List-Help: <mailto:ietf-privacy-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-privacy>, <mailto:ietf-privacy-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 17 Apr 2022 23:07:42 -0000

Hi Kate,
At 11:35 AM 17-04-2022, kate_9023+rfc@systemli.org wrote:
>I'm quite new at creating RFCs. I have recently submitted a draft 
>for a new webiquette and I am still searching a group which will 
>take care of it. It would fit into privacy as this new webiquette is 
>dealing with new internet technology such as deepfakes, sharing 
>photos of 3rd parties and so on and also deleting old information on 
>a regular basis good behavior. It's also quite short with only 9 
>pages and also covers cancel culture and mobbing. I think a document 
>like this is needed and important. Anyone here who'd like to take 
>care or helping me making an RFC out of it? Or guide me in the right direction?

I took a quick look at the draft.  The Introduction section is a bit 
short.  I suggest referring to the style guide as it may contain some 
guidance.  Some of the etiquette in the draft is not followed outside the IETF.

The topic you wrote about is not ideally suited for this mailing list 
as the draft is focused on etiquette.

It's unlikely that the memo will be published as a RFC if the editor 
insists on anonymity.

Regards,
S. Moonesamy