IETF Logo Mail Archive

Filleted clients [Re: Approaching the IETF - A View from Civil Society]

Brian E Carpenter <brian.e.carpenter@gmail.com> Tue, 01 August 2023 21:09 UTC

Return-Path: <brian.e.carpenter@gmail.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 9E389C151554 for <ietf@ietfa.amsl.com>; Tue, 1 Aug 2023 14:09:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.108
X-Spam-Level:
X-Spam-Status: No, score=-2.108 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, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01] 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 ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Hc_EYfcVISyw for <ietf@ietfa.amsl.com>; Tue, 1 Aug 2023 14:09:41 -0700 (PDT)
Received: from mail-pl1-x62f.google.com (mail-pl1-x62f.google.com [IPv6:2607:f8b0:4864:20::62f]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 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 1EF81C151545 for <ietf@ietf.org>; Tue, 1 Aug 2023 14:09:41 -0700 (PDT)
Received: by mail-pl1-x62f.google.com with SMTP id d9443c01a7336-1bba48b0bd2so38986885ad.3 for <ietf@ietf.org>; Tue, 01 Aug 2023 14:09:41 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1690924180; x=1691528980; h=content-transfer-encoding:in-reply-to:from:references:cc:to :content-language:subject:user-agent:mime-version:date:message-id :from:to:cc:subject:date:message-id:reply-to; bh=EXsfg0GOAQEgFiIWzOV4AYXTnPBV+Oc9y4YznLUZrjU=; b=C6XRkSMKA+E8LRHfAa1ywaNVVlNoP5PyJFlC0CE17d0A6oCHW14YQq9Ga22Be59y/y HHc4O4LxTaO64ZrTQk/ifkuzG87R8w8m1EcV8+oNoC8Fqi7+p34tL9ni3SB2LusnEl35 KH8lmVBv+BkC6l9wne3JangNxsyt9TzXn97WYuDAIyudkEjuKH9oknM0/Jxa5pFr9Wgm wiY2AOyJSiL8AVOAc2ImhfkJpTYxePRdxs//cF1GAY218Yrkj28yUiYyew0QejNis+jN AHwIfGQ7eUeG00yo8b+DdNTBx4fvCnZMevn0e+RdPNc1cUvRn+G+0AcIA/FEo3YUh0lc dgag==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1690924180; x=1691528980; h=content-transfer-encoding:in-reply-to:from:references:cc:to :content-language:subject:user-agent:mime-version:date:message-id :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=EXsfg0GOAQEgFiIWzOV4AYXTnPBV+Oc9y4YznLUZrjU=; b=Zm2cGRP4XNwmDwrAq6UpMgNgHuPPkaRFeFkvssckzlepWG6Kfck1rFGj3qKFPMvoI7 HAdzrofunlj7CGKbLRVQ5OXLI04SKAFPbrvxu29R3Ez+lNoPX2h/u+4JcF94me5SEYpQ qF6NtaK98P9s5Yu5eOAuEttu8O1ETUGfRDW3+9J7WwNNnqxRzwFCt6pKExA0OkIBMBka bjXx2nWTmRPnAxkBsAO/gF4kAy6zEnWniwpXScd27l1rRtEyWZ/Bu0NHL5XZCEia3qPE qEf/85NfjWEx9WlUr5NaUiDihcwBenvqJndBikltsNtwhpdc2DXtceEBW0TGCD6t6y6I 87lg==
X-Gm-Message-State: ABy/qLaNgmM1LdtpacflXk48F5Fc0+O/T/i6k16tDdgBSj5pGfwAdSoD 4W/V+Ffpp7r7o7F+wlaCO97NFAzWOx7lHg==
X-Google-Smtp-Source: APBJJlHdT0nEtcwIEcuRVM/0dSJ/zRKUQMt8SGw3d6DIL7f1kiD+OH0unsZmQLyPHJaTThCuPsWLjg==
X-Received: by 2002:a17:903:1112:b0:1bb:2ccc:c321 with SMTP id n18-20020a170903111200b001bb2cccc321mr16489043plh.48.1690924180452; Tue, 01 Aug 2023 14:09:40 -0700 (PDT)
Received: from ?IPV6:2406:e003:10cc:9901:b2e1:1101:7ba7:19fd? ([2406:e003:10cc:9901:b2e1:1101:7ba7:19fd]) by smtp.gmail.com with ESMTPSA id p16-20020a170902e75000b0019ee045a2b3sm10858520plf.308.2023.08.01.14.09.38 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Tue, 01 Aug 2023 14:09:39 -0700 (PDT)
Message-ID: <9478bdf3-321a-1cb6-44d5-f920029d32f0@gmail.com>
Date: Wed, 02 Aug 2023 09:09:34 +1200
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:91.0) Gecko/20100101 Thunderbird/91.10.0
Subject: Filleted clients [Re: Approaching the IETF - A View from Civil Society]
Content-Language: en-US
To: Nick Hilliard <nick@foobar.org>
Cc: IETF discussion list <ietf@ietf.org>
References: <CWXP265MB515399A8746EA36E51ACE60EC205A@CWXP265MB5153.GBRP265.PROD.OUTLOOK.COM> <6FF7FAED-5EAD-4E02-B3AD-F31B85D44AA9@network-heretics.com> <E3A2182F-827E-4D87-85AA-0045878CC04E@istaff.org> <CABrd9ST8L3gMRibmysddNZqXPaL-ZL2ESuXXEP6V_fv23EYzAQ@mail.gmail.com> <30c86520-2709-bda7-3298-357ae756c667@foobar.org> <21e3b07d-445f-8af9-fb44-12c045c4ac3e@gmail.com> <6c7bd833-36d2-dcd8-228f-77f8041541ce@foobar.org>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
In-Reply-To: <6c7bd833-36d2-dcd8-228f-77f8041541ce@foobar.org>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/fpoaQTwqv6rSOoYQjMoiuv0IUcs>
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: Tue, 01 Aug 2023 21:09:42 -0000


On 02-Aug-23 08:12, Nick Hilliard wrote:
> Brian E Carpenter wrote on 01/08/2023 03:26:
>> I was under the illusion that RFC1984 + RFC2804 made this point quite
>> clear.
>> Do you think we need an RFC that says more?
> 
> The contents of rfc1984 aged well. One potential addition: the current
> round of proposals include suggestions to fillet various classes of
> encryption clients, for example personal messaging systems. This is
> slightly different to the topics discussed in rfc1984, but in the
> current round of encryption angst, no less of a problem.

Correct. Those two RFCs don't talk about backdoors in the host, for example.
Neither does RFC7258.

Who's going to write the draft, and will the IETF+IESG support it?

    Brian

v2.46.0 | Report a Bug | By Email | System Status