IETF Logo Mail Archive

Re: USA dominion: Re: IESG Statement On Oppressive or Exclusionary Language

Toerless Eckert <tte@cs.fau.de> Sat, 25 July 2020 22:25 UTC

Return-Path: <eckert@i4.informatik.uni-erlangen.de>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9C08F3A0B48 for <ietf@ietfa.amsl.com>; Sat, 25 Jul 2020 15:25:30 -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, HEADER_FROM_DIFFERENT_DOMAINS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-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 qF2ivmD92Pnq for <ietf@ietfa.amsl.com>; Sat, 25 Jul 2020 15:25:29 -0700 (PDT)
Received: from faui40.informatik.uni-erlangen.de (faui40.informatik.uni-erlangen.de [131.188.34.40]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 181033A0B47 for <ietf@ietf.org>; Sat, 25 Jul 2020 15:25:28 -0700 (PDT)
Received: from faui48f.informatik.uni-erlangen.de (faui48f.informatik.uni-erlangen.de [131.188.34.52]) by faui40.informatik.uni-erlangen.de (Postfix) with ESMTP id 1ECA1548047; Sun, 26 Jul 2020 00:25:24 +0200 (CEST)
Received: by faui48f.informatik.uni-erlangen.de (Postfix, from userid 10463) id 11C62440043; Sun, 26 Jul 2020 00:25:24 +0200 (CEST)
Date: Sun, 26 Jul 2020 00:25:24 +0200
From: Toerless Eckert <tte@cs.fau.de>
To: Joe Touch <touch@strayalpha.com>
Cc: "Salz, Rich" <rsalz@akamai.com>, "<ietf@ietf.org>" <ietf@ietf.org>
Subject: Re: USA dominion: Re: IESG Statement On Oppressive or Exclusionary Language
Message-ID: <20200725222524.GN43465@faui48f.informatik.uni-erlangen.de>
References: <20200725211141.GK43465@faui48f.informatik.uni-erlangen.de> <7C08DF59-1CD1-4749-829A-603B4C228177@strayalpha.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <7C08DF59-1CD1-4749-829A-603B4C228177@strayalpha.com>
User-Agent: Mutt/1.10.1 (2018-07-13)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/k228KLHeIMtsF5lKKH1VBp1HAeA>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 25 Jul 2020 22:25:31 -0000

On Sat, Jul 25, 2020 at 03:12:31PM -0700, Joe Touch wrote:
> >> ISOC chapters have little to nothing to do with RFCs.
> > 
> > What do you mean ? If i join an ISOC chapter, i am not allowed anymore to read RFCs ?
> 
> No, but reading, implementing, or discussing RFCs isn???t the point of ISOC chapters.
> 
> I.e., they???re not really representative of the community of people who read or use RFCs any more than LEGO robot club members.
> 

Hahaha. You're good in snipe remarks today.

ISOC is even doing regular? teaching session for network operators,
i would be suprised if none of the IETF is ever read by operators.

Also remember that ISOC itself is somehow involved in financing the IETF,

And finally: if nobody reads RFCs, who the heck are we doing the more "polite"
words for ? Just ourselves ?

Cheers
    Toerless

v2.23.0 | Report a Bug | By Email