IETF Logo Mail Archive

Re: [saag] [Pearg] Ten years after Snowden (2013 - 2023), is IETF keeping its promises?

Alan DeKok <aland@deployingradius.com> Thu, 05 January 2023 16:34 UTC

Return-Path: <aland@deployingradius.com>
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 9B097C151707; Thu, 5 Jan 2023 08:34:39 -0800 (PST)
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, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=unavailable autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7lJaXymbrlmj; Thu, 5 Jan 2023 08:34:35 -0800 (PST)
Received: from mail.networkradius.com (mail.networkradius.com [62.210.147.122]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B66F9C14F5E1; Thu, 5 Jan 2023 08:34:34 -0800 (PST)
Received: from smtpclient.apple (135-23-95-173.cpe.pppoe.ca [135.23.95.173]) by mail.networkradius.com (Postfix) with ESMTPSA id 945ED328; Thu, 5 Jan 2023 16:34:30 +0000 (UTC)
Authentication-Results: NetworkRADIUS; dmarc=none (p=none dis=none) header.from=deployingradius.com
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3696.120.41.1.1\))
Subject: Re: [saag] [Pearg] Ten years after Snowden (2013 - 2023), is IETF keeping its promises?
From: Alan DeKok <aland@deployingradius.com>
In-Reply-To: <7ab59bd6-9457-e639-943d-83210ebeb068@netmagic.com>
Date: Thu, 05 Jan 2023 11:34:28 -0500
Cc: Eric Rescorla <ekr@rtfm.com>, Vittorio Bertola <vittorio.bertola@open-xchange.com>, "ietf@ietf.org" <ietf@ietf.org>, "pearg@irtf.org" <pearg@irtf.org>, saag <saag@ietf.org>, "hrpc@irtf.org" <hrpc@irtf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <2C5C129D-69DF-4C84-8CAA-86E601D7C753@deployingradius.com>
References: <HE1PR0701MB305098F652DBC34E3C40810B89F49@HE1PR0701MB3050.eurprd07.prod.outlook.com> <764163366.39904.1672842828297@appsuite-gw2.open-xchange.com> <CABcZeBNA_nJ2waQVENUvEXro91wAYOcH0ZxWqbLH4hoKcGkosw@mail.gmail.com> <9658281.42904.1672912808774@appsuite-gw2.open-xchange.com> <CA+9kkMBLiijcAyLYn_6h8z3N00EDaxdP=f7P2-qUt4Bn1iSWEg@mail.gmail.com> <HE1PR0701MB30505DC24A725E014D60FE0189FA9@HE1PR0701MB3050.eurprd07.prod.outlook.com> <CABcZeBPc0r275AiCL=qWTnzFT9PoQ9WMHz+GcmQZG8pgv2dmbw@mail.gmail.com> <4EB76682-E75C-413B-906B-6C5C7404A91C@deployingradius.com> <7ab59bd6-9457-e639-943d-83210ebeb068@netmagic.com>
To: trutkowski@netmagic.com
X-Mailer: Apple Mail (2.3696.120.41.1.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/bvGsMSHYqIeUdVXn9Jueyyl0fRE>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: "IETF-Discussion. This is the most general IETF mailing list, intended for discussion of technical, procedural, operational, and other topics for which no dedicated mailing lists exist." <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: Thu, 05 Jan 2023 16:34:39 -0000

On Jan 5, 2023, at 11:00 AM, Tony Rutkowski <trutkowski.netmagic@gmail.com> wrote:
> All of this may explain the lack of "boots on the ground" in the IETF.  The boots have moved to other more pragmatic, real-world ground. :-)

  The IETF still has change control over key Internet protocols.  Which means that large swaths of the Internet rely on insecure / outdated / broken protocols.

  And that means those protocols won't be updated, even if some efforts have moved elsewhere.

  Alan DeKok.

v2.23.0 | Report a Bug | By Email