Re: [ietf-privacy] New Webiquette RFC

Christian Huitema <huitema@huitema.net> Sun, 17 April 2022 19:14 UTC

Return-Path: <huitema@huitema.net>
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 384253A0E10 for <ietf-privacy@ietfa.amsl.com>; Sun, 17 Apr 2022 12:14:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, NICE_REPLY_A=-0.001, SPF_HELO_NONE=0.001, T_SCC_BODY_TEXT_LINE=-0.01, T_SPF_PERMERROR=0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 iiT-_zzwLs5M for <ietf-privacy@ietfa.amsl.com>; Sun, 17 Apr 2022 12:14:54 -0700 (PDT)
Received: from mx36-out21.antispamcloud.com (mx36-out21.antispamcloud.com [209.126.121.69]) (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 715B33A0E06 for <ietf-privacy@ietf.org>; Sun, 17 Apr 2022 12:14:54 -0700 (PDT)
Received: from xse464.mail2web.com ([66.113.197.210] helo=xse.mail2web.com) by mx257.antispamcloud.com with esmtp (Exim 4.92) (envelope-from <huitema@huitema.net>) id 1ngAMB-0000DB-Oy for ietf-privacy@ietf.org; Sun, 17 Apr 2022 21:14:52 +0200
Received: from xsmtp22.mail2web.com (unknown [10.100.68.61]) by xse.mail2web.com (Postfix) with ESMTPS id 4KhKWT2fnYz9Xl for <ietf-privacy@ietf.org>; Sun, 17 Apr 2022 12:14:45 -0700 (PDT)
Received: from [10.5.2.15] (helo=xmail05.myhosting.com) by xsmtp22.mail2web.com with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.92) (envelope-from <huitema@huitema.net>) id 1ngAM9-0007RF-7m for ietf-privacy@ietf.org; Sun, 17 Apr 2022 12:14:45 -0700
Received: (qmail 17593 invoked from network); 17 Apr 2022 19:14:44 -0000
Received: from unknown (HELO [192.168.1.107]) (Authenticated-user:_huitema@huitema.net@[172.58.43.237]) (envelope-sender <huitema@huitema.net>) by xmail05.myhosting.com (qmail-ldap-1.03) with ESMTPA for <ietf-privacy@ietf.org>; 17 Apr 2022 19:14:44 -0000
Message-ID: <740b6d5e-840a-af74-276b-8b4e6719ef96@huitema.net>
Date: Sun, 17 Apr 2022 12:14:44 -0700
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:91.0) Gecko/20100101 Thunderbird/91.8.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>
From: Christian Huitema <huitema@huitema.net>
In-Reply-To: <e27ce6c6-33aa-1acf-81c5-6ba430b4627d@systemli.org>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Originating-IP: 66.113.197.210
X-Spampanel-Domain: xsmtpout.mail2web.com
X-Spampanel-Username: 66.113.197.0/24
Authentication-Results: antispamcloud.com; auth=pass smtp.auth=66.113.197.0/24@xsmtpout.mail2web.com
X-Spampanel-Outgoing-Class: unsure
X-Spampanel-Outgoing-Evidence: Combined (0.15)
X-Recommended-Action: accept
X-Filter-ID: Pt3MvcO5N4iKaDQ5O6lkdGlMVN6RH8bjRMzItlySaT9WLQux0N3HQm8ltz8rnu+BPUtbdvnXkggZ 3YnVId/Y5jcf0yeVQAvfjHznO7+bT5w2h9ThF8Uk+TkhFXcJpmcVNaIcTUrFt5pQyDECiKPE3tcV PSoHm0W/3adFfiYl2nvV28MmMJ0JDp/pqY6cBdF6/T4GcPvCLvSpAEEGy7kYxlS0H3VPGe6eSMvB 4vlS4o8vfHLnl+FtU3ZaDlGQjFNyQ1wxxCKPU4P2YhYmbbATd5VOD7pnxvtc2suw3rDWuZsTcgXN 9+bI2hCkAO68TIOIVgW9/bktU41htiJ8fk7NkK7VZqJmzCeHtqZ+QtMgTB0iLwRMaKsK8lAeAhb+ aZDw2IovQ3/ZWsthDvd0snMbK9QGtxAJEXKNeGZQyJQlGXr2dK6UtSEdwn3yFtfkzf2ggTHzfqZI wwACW9bQ+KDdJhsM51Mye8eo6Y/hXEFbc9MIm4qZ5/UkJuZ+By/rOgnAjLG/aPmBdHQHE38dhhiy dz8PrNOXiYDxFIn9L24NLWSh5EgREISIk8pBl2w/QHqwjS7UkVihpqIaIpf9QIiqPrZIF8ronaI7 xIN6o34ogH/74O4hBSz/kkmPgL+fgIguz902kqnkEXZAWjOIh4pqpA7jPNTmvjfzqWc87xWIkKVp cVMJzW8LWO34W/TACmBab3UQT3xbkHqpqmyCe4PiKVv0wNAmy0z4NCWU5AbBg6tDVPQ6fMev1BMP vQ9qu4cW0z6bhalFEM/pjPCQA+BAliEhDqtxmPsoCEX6XCXis3y3h1ESmlc3/lS5x7qxkdla2YbM hrOUjXRMZvRLL2JYJgz29vdPUOiPruVrrOM/NixRXxKF5tPxTxfD0dMN+t5ZZP1TBpq7cC9pkYPz hIePItYq/lrmOIggGSbFQcaLnZSN9/YGRrhMRGhIOTxMW00yF8F1u0YDQf8cLP9taeSLFY0fPBnF 89BphpBNlUg+TzHwBTL1+6vDOMemz/4I88NDcmnEJ4r7C+SwLRamrhQTd3PrpJpP5ewAjeqkzRNl ucyd+NO2McmveAr4ch9F7rE89jihx+Za/cV70jOJzN2r4A==
X-Report-Abuse-To: spam@quarantine11.antispamcloud.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-privacy/cClO8xtxMFsrGa2-A6R4uRtX2PA>
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 19:14:59 -0000

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