Re: [ietf-privacy] New Webiquette RFC

Toerless Eckert <tte@cs.fau.de> Mon, 18 April 2022 12:19 UTC

Return-Path: <eckert@i4.informatik.uni-erlangen.de>
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 1B64D3A0CDA for <ietf-privacy@ietfa.amsl.com>; Mon, 18 Apr 2022 05:19:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.881
X-Spam-Level:
X-Spam-Status: No, score=-0.881 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.248, SPF_HELO_NONE=0.001, SPF_NEUTRAL=0.779, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001] autolearn=no 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 Z7p13o_3t8h3 for <ietf-privacy@ietfa.amsl.com>; Mon, 18 Apr 2022 05:19:23 -0700 (PDT)
Received: from faui40.informatik.uni-erlangen.de (faui40.informatik.uni-erlangen.de [IPv6:2001:638:a000:4134::ffff:40]) (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 8C3CA3A0CC7 for <ietf-privacy@ietf.org>; Mon, 18 Apr 2022 05:19:22 -0700 (PDT)
Received: from faui48e.informatik.uni-erlangen.de (faui48e.informatik.uni-erlangen.de [131.188.34.51]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by faui40.informatik.uni-erlangen.de (Postfix) with ESMTPS id 9DCF058C4AF; Mon, 18 Apr 2022 14:19:16 +0200 (CEST)
Received: by faui48e.informatik.uni-erlangen.de (Postfix, from userid 10463) id 87F934EAC3D; Mon, 18 Apr 2022 14:19:16 +0200 (CEST)
Date: Mon, 18 Apr 2022 14:19:16 +0200
From: Toerless Eckert <tte@cs.fau.de>
To: Ted Hardie <ted.ietf@gmail.com>
Cc: kate_9023+rfc@systemli.org, ietf-privacy@ietf.org
Message-ID: <Yl1XRNgzOfj0l66S@faui48e.informatik.uni-erlangen.de>
References: <9bb455e8-8dbb-9813-bc8e-6367c80b6063@systemli.org> <e27ce6c6-33aa-1acf-81c5-6ba430b4627d@systemli.org> <740b6d5e-840a-af74-276b-8b4e6719ef96@huitema.net> <4c4ca96c-bf09-b9aa-5734-7faaca9db07e@cs.tcd.ie> <4fdd08f6-f8f4-cc2b-0ef9-edc76153acf6@systemli.org> <CA+9kkMAgDdywwm3xbYv+tY4tNkTiPCHgf-T_VWRJ9_cmKZFW3A@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <CA+9kkMAgDdywwm3xbYv+tY4tNkTiPCHgf-T_VWRJ9_cmKZFW3A@mail.gmail.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-privacy/HyZCiqhoK5pyl9Xk_diG8Q7YUGg>
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: Mon, 18 Apr 2022 12:19:28 -0000

Intersting historic insight, thanks, Ted.

So, in summary: "The Internet is for End-Users, but the IETF is not" ?  ;-)

Sounds like a bit as if the state of IETF wrt. to what you write contradicts RFC8890.

Shouldn't be too difficult to attempt reviving FYI in some gen area WG
if we believed we actually wanted to do something about rfc8890 that 
does not well fit other areas.

Cheers
    Toerless

On Mon, Apr 18, 2022 at 09:53:37AM +0100, Ted Hardie wrote:
> Howdy,
> 
> 
> On Sun, Apr 17, 2022 at 9:18 PM <kate_9023+rfc@systemli.org> wrote:
> 
> > Thank you. I have oriented myself on this RFC:
> >
> >    [RFC1855]  Hambridge, S., "Netiquette Guidelines", FYI 28, RFC 1855,
> >               DOI 10.17487/RFC1855, October 1995,
> >               <https://www.rfc-editor.org/info/rfc1855> <https://www.rfc-editor.org/info/rfc1855>.
> >
> >
> > You will no doubt have noticed that this had both an RFC number and a
> designation as an FYI.  The FYI series has since been concluded:
> https://datatracker.ietf.org/doc/html/rfc6360 describes the action.  This
> is in part because that relevant part of the IETF (the User Services Area)
> had also wound down.
> 
> Given the decisions above, it would be difficult to identify a group within
> the IETF that could review an update to RFC 1855.
> 
> regards,
> 
> Ted Hardie
> 
> 
> 
> 
> > On 17.04.22 22:12, Stephen Farrell wrote:
> >
> > Perhaps if the author wishes the draft to proceed they will
> > be happy to self-identify, or perhaps not. I'd not worry
> > too much about the general problem 'till that's clear.
> >
> > The text of the draft itself seems innocuous enough. While
> > I'm not clear what useful purpose might be served by having
> > such text in an RFC, I'd be willing to be convinced but so
> > far remain to be convinced.
> >
> > Process-wise, I'd say unless this were modified to address
> > some IETF-specific issues (such as netiquette in developing
> > protocols) it'd likely be better targeted to the IAB or
> > ISE streams. (That's no reason to not discuss it here
> > though.)
> >
> > _______________________________________________
> > 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


-- 
---
tte@cs.fau.de