Re: [ietf-privacy] New Webiquette RFC

kate_9023+rfc@systemli.org Sun, 17 April 2022 20:19 UTC

Return-Path: <kate_9023+rfc@systemli.org>
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 F1C083A0FAF for <ietf-privacy@ietfa.amsl.com>; Sun, 17 Apr 2022 13:19:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.109
X-Spam-Level:
X-Spam-Status: No, score=-2.109 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=systemli.org
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 2b5p5_XRukXo for <ietf-privacy@ietfa.amsl.com>; Sun, 17 Apr 2022 13:19:40 -0700 (PDT)
Received: from mail1.systemli.org (mail1.systemli.org [93.190.126.36]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 31DD43A0F61 for <ietf-privacy@ietf.org>; Sun, 17 Apr 2022 13:19:39 -0700 (PDT)
Message-ID: <b3a1041e-7e0f-d197-2fc7-d52c8f7777d4@systemli.org>
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=systemli.org; s=default; t=1650226776; bh=e6rfdWxhYAjHMZGvWb9LvMtmSuICVtbFMYEIlEH9chQ=; h=Date:Subject:To:References:From:In-Reply-To:From; b=8w/0VmlXyC2kEq8oeKaBHIjqOvwaogHq+wj4DBCvLXzSvr3IMBYZE/tLQfEfubh4U Q/V0nasqVbFjLrgHey9Gf49ZNa2jf/cnLxiji+g5kpZVW3znllE/cxPmGPIDGtvRkT uzGm92v/M43ixc6P/KLzUwpH0EZf1LBsBonX1qGDTNxsRkWfSKe9w9uwSGwTWfXcWC 1u+FrD3L0m6V2Y6ALCJId7KdEMX9rIfEFj2TDTLtUkALom6CQ5bKRPg/J/fJcT0G5T MvbE83Q72/PZOwkDx0Eex+JjNwG3JXavc0NOqMgSB/9fG4lbfoAwJNbQLQrXZTcDrZ fOcnAoZJsr6IA==
Date: Sun, 17 Apr 2022 22:19:35 +0200
MIME-Version: 1.0
Content-Language: en-US
To: ietf-privacy@ietf.org
References: <9bb455e8-8dbb-9813-bc8e-6367c80b6063@systemli.org> <e27ce6c6-33aa-1acf-81c5-6ba430b4627d@systemli.org> <740b6d5e-840a-af74-276b-8b4e6719ef96@huitema.net>
From: kate_9023+rfc@systemli.org
In-Reply-To: <740b6d5e-840a-af74-276b-8b4e6719ef96@huitema.net>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-privacy/cpIv6RKdGX176rBahP3nZgnA6-o>
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 20:19:45 -0000

I just want to submit a draft to make the world a little better. I did 
this individually without an employer in the background and on my own. I 
just followed the already existing RFC from Sally, I even wrote to her 
(unfortunately the email came back). I don't have to have my name all 
over the internet and I don't want to. I also could have done a better 
job of disguising the fact that it's not my real name. The IETF can 
hardly control this at all.
I could take a very common name and maybe many have already done that. 
Just from the individual email I know that IETF has very poor spam 
protection and for that reason alone you end up in a lot of spam lists 
and very quickly. I only want to establish a new webiquette as I see a 
lot of issues at in the internet at the moment.

On 17.04.22 21:14, Christian Huitema wrote:
> This submission raises an interesting question for the IETF: how to 
> treat anonymous (or pseudonymous) submissions?
>
> On one hand, there are lots of classic reasons for hiding behind a 
> pseudonym when participating in public discussions. On the other hand, 
> the IETF has to be protected against intellectual property issues and 
> against sabotage by external groups.
>
> Before submissions are accepted for publication, their authors have to 
> disclose whether they, or their employer, own intellectual property 
> rights on the technologies described in the draft. Failure to disclose 
> would influence the prosecution of intellectual property disputes that 
> might arise when third parties implement the technology. This provides 
> some degree of protection to implementers. But when the submission 
> cannot be traced to a specific company, these protections disappear, 
> and we might have a problem. So this is one source of tension between 
> standards and anonymity.
>
> The other source of tension is the risk of sabotage. Various groups 
> have tried to sabotage the standard process in the past, for example 
> to delay the deployment of encryption, or to introduce exploitable 
> bugs in security standards -- some of these tactics were exposed in 
> the Snowden revelations. Anonymous participation could allow these 
> groups to perform such sabotage in untraceable ways, which is 
> obviously not desirable.
>
> I think this issue of anonymous participation is worth discussing.
>
> -- Christian Huitema
>
>
> On 4/17/2022 11:35 AM, kate_9023+rfc@systemli.org wrote:
>> Dear all,
>>
>> 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?
>>
>> The draft can be found here: 
>> https://www.ietf.org/archive/id/draft-rfcxml-general-the-new-webiquette-00.txt
>>
>> Best Regards,
>>
>> Kate
>>
>> _______________________________________________
>> ietf-privacy mailing list
>> ietf-privacy@ietf.org
>> https://www.ietf.org/mailman/listinfo/ietf-privacy
>
> _______________________________________________
> ietf-privacy mailing list
> ietf-privacy@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf-privacy