Re: [ietf-privacy] New Webiquette RFC

Bernard Aboba <bernard.aboba@gmail.com> Sun, 17 April 2022 19:49 UTC

Return-Path: <bernard.aboba@gmail.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 6860F3A15AF for <ietf-privacy@ietfa.amsl.com>; Sun, 17 Apr 2022 12:49:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.107
X-Spam-Level:
X-Spam-Status: No, score=-7.107 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, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, 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=gmail.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 mNp3OWttehFW for <ietf-privacy@ietfa.amsl.com>; Sun, 17 Apr 2022 12:48:57 -0700 (PDT)
Received: from mail-vs1-xe34.google.com (mail-vs1-xe34.google.com [IPv6:2607:f8b0:4864:20::e34]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6041A3A15AE for <ietf-privacy@ietf.org>; Sun, 17 Apr 2022 12:48:57 -0700 (PDT)
Received: by mail-vs1-xe34.google.com with SMTP id i34so10121580vsv.6 for <ietf-privacy@ietf.org>; Sun, 17 Apr 2022 12:48:57 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=CxdeOSi1U1JYIc778z1B/e46x85ug3Natmie3bl7dFc=; b=AjO+B7sp5AIMfv4e8OrYM2x71i39a56khHSaV1ZxacZ2E8fZt57Nk++4sVkXrf19jA WmTU1TyoRuJeGSQBXtpo9K/UoVWqQlzq0kBHzZCasLZANQfrOAFCSc7gcbs62L7VOJhh f8fJSEUTVDqjVz+zU6u142xdgc97TIcfGaQT5uaUDUdkeNbRFuncoldzrJdbp8H98roI 3adJ8R9SFcpEYZZy8Hcl++2SboHoub440+au5YWTka87bcXl9DATuaiifhLhoCBA32bv vLlMZVMT2P+zrV0qkRoG5gLMdQQD+accckb4QnL/Xaqh1TyYujfx7D47ekp6KaX1gTYG aueg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=CxdeOSi1U1JYIc778z1B/e46x85ug3Natmie3bl7dFc=; b=6qeL4i0z4pOFROQpbBugEFuBFVT91qduKExaFs86fHbEM5Tp3ntlVrf9vQek8LiMTo 93nzY01zrsV6Fta3SYQuosWuZDyC1UW/fSwi9YILsLD1Z2e/27UbBgi08onYX9ELGWGb 1KguiC7N4hOGfwi2w/7J7zx7/0JCv4+KLQR/6hN4x4KFFB6Ppf0H3wKFKMsVQAx8TuVN GHE5p+26/qWigckPpQlX3q6J/E1Sd2HLEfJ4CgXwQG6zhIWPlXMhKq5HRig+uLgYX+oP sCSblhqN/qDjVtxWj+jwTCEv9ZJAg9PMeHB4cGtmn+aDfhOz9UN3TTUEz9ZZVol7IRZ1 YLrg==
X-Gm-Message-State: AOAM533DlWrucW2/jboFA7Ao5Vcag/iIFGrqM0wc9d7dt4QpqRvYsHOB 5XmVgD3LxTUA2M4XV8HyEPMav9rGBsztniB6k42w7eA/AHo=
X-Google-Smtp-Source: ABdhPJzOp1NqjM+5YX2dekR9fDCTAfHgzxjSo3lFD03CaY+wSnHtY4E3qb8F/5isMcQ/Gk+zFNt9rEpe8YMtpqjZxIY=
X-Received: by 2002:a05:6102:f95:b0:32a:56cf:7ae6 with SMTP id e21-20020a0561020f9500b0032a56cf7ae6mr379540vsv.24.1650224935682; Sun, 17 Apr 2022 12:48:55 -0700 (PDT)
MIME-Version: 1.0
References: <9bb455e8-8dbb-9813-bc8e-6367c80b6063@systemli.org> <e27ce6c6-33aa-1acf-81c5-6ba430b4627d@systemli.org> <740b6d5e-840a-af74-276b-8b4e6719ef96@huitema.net>
In-Reply-To: <740b6d5e-840a-af74-276b-8b4e6719ef96@huitema.net>
From: Bernard Aboba <bernard.aboba@gmail.com>
Date: Sun, 17 Apr 2022 12:48:45 -0700
Message-ID: <CAOW+2dt1d7R2q2KRA1zza84Q4iYaxN6gU0QDr1irHBsD-yC25g@mail.gmail.com>
To: Christian Huitema <huitema@huitema.net>
Cc: ietf-privacy@ietf.org
Content-Type: multipart/alternative; boundary="0000000000001745de05dcdeefdf"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-privacy/kOuYsSNNeYM_98APXr17xM3gEQM>
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:49:03 -0000

The questions you refer to are not new.  The same issues (IPR policy
conformance and hidden agendas) have been raised with respect to the
affiliations of ‘consultants’ who are hired by clients who wish to remain
anonymous.  AFAICT, the IETF has never required that consultants divulge
their clients, even to the nomcom.

Anonymous participation takes this trend one step further.  The W3C does
not allow anonymous participation due to IPR concerns, but their IPR policy
is also significantly different, since W3C is membership-based (and not
particularly friendly to ‘consultants’ or small businesses).

We might decide that this anonymous participation is one step too far, but
my take is that IETF crossed an important line long ago.

On Sun, Apr 17, 2022 at 12:15 Christian Huitema <huitema@huitema.net> 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
>