[TLS] Re: FATT process update
Rob Sayre <sayrer@gmail.com> Wed, 06 November 2024 18:41 UTC
Return-Path: <sayrer@gmail.com>
X-Original-To: tls@ietfa.amsl.com
Delivered-To: tls@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CAEDFC1ECA95 for <tls@ietfa.amsl.com>; Wed, 6 Nov 2024 10:41:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.103
X-Spam-Level:
X-Spam-Status: No, score=-2.103 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_BLOCKED=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, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=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 ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hFMA44xlyK_v for <tls@ietfa.amsl.com>; Wed, 6 Nov 2024 10:41:01 -0800 (PST)
Received: from mail-pj1-x102e.google.com (mail-pj1-x102e.google.com [IPv6:2607:f8b0:4864:20::102e]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F33BEC1F7D91 for <tls@ietf.org>; Wed, 6 Nov 2024 10:41:00 -0800 (PST)
Received: by mail-pj1-x102e.google.com with SMTP id 98e67ed59e1d1-2e2e6a1042dso96842a91.2 for <tls@ietf.org>; Wed, 06 Nov 2024 10:41:00 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1730918460; x=1731523260; darn=ietf.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=aJfM4U45kxOasBnGwY21lCeL0RmuoisdYEK2PFwQ8UQ=; b=IgyvJFi2Isgb8yq1syHwgJ+EQVUwjaUiKu0ASwTVnXK8w7fkTMOAG2OAjPv8W8dlYe ELJ4Pc31RYqDhPZT8F2w/SepTxrvFxidzhBC3LKKJyvRPGHI/BAdntfkuyLsvwPfQwWH RNtsxXUm1g8YfqQSvAZeptbBSlWTkGAWkteXsR7UMoeJE5OZojd0QlXqCN20XLuGgN3p dLk9GiDX8cHykNxwLyFk5WMmOS5IaBlB4HQGTJmK01P41KvgcJEvckdpnqjW0C39LXrM lbKBtcoOkJjS7pyTGDa4qFn9mx+ve0OGQZfGRLsFccauF6bp5f2R1ox9XQ/iIbyYhVLH U4fw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1730918460; x=1731523260; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=aJfM4U45kxOasBnGwY21lCeL0RmuoisdYEK2PFwQ8UQ=; b=U+1v2jtAGBdeExPkLAyWk8ILum1xh+wnYWNYcpgRuG0t2uQVcVQ1i9y/FP6LzMzxzg ZUUUcXdPWp0D0YeNWRVCJe4FG2WURPLnQuMfzU6VX5Ns3Jm0os+Yeg6shiTVr4950XqP XdXnrfgJsJA9Grc6aPrcWaVqx39Ag9PzsXVmcxy94p7gCShN/W7vun6svoIX8VKokycP 80NyeY/krS0yDSxZtfXbDsp3QvcewvT/CcOCIpRNsTD8jucoNBe/OQIYsMIAMWl0O5zJ iNCa2UomW4LagTtuwDRH75B6IPha3LY77Qa4TIHk26w9kKgjXstaiuFbKB0c57lStO6j 7Cuw==
X-Forwarded-Encrypted: i=1; AJvYcCW4Sq3gXmv+FxeOj9m91dQMGy18VUlcNtgP0JBVQamOXzxrbTRTiYb7iqy/oiJfTQ0iXbo=@ietf.org
X-Gm-Message-State: AOJu0Yxs7Lvok02jzFikKq/0YHZHHWhEB0lQDdjL7SpCfyGft329GHf/ qY4ekq7VfLJIZbZPY+gIBBbT6U7gcsfxSNKlGcJkI/SMhlR7Oakjik5EFPGlC61HxvQ98ElsxNn w+6ir9scHK9FNuQQmrB6A6GWlrxQ0sNAs
X-Google-Smtp-Source: AGHT+IEzAYPCDIGxgFQfAeUcrgIRMdl2pldVet7xpD47d1ikIhORhlrQJA4pwBFATYxYxDVm2rvFAmpwDILnxo/L2+k=
X-Received: by 2002:a17:90b:3948:b0:2d3:cd27:c480 with SMTP id 98e67ed59e1d1-2e94c538ef7mr30870060a91.33.1730918460328; Wed, 06 Nov 2024 10:41:00 -0800 (PST)
MIME-Version: 1.0
References: <CAOgPGoDAm=thO6O3xsm_HTJ+K8=mWkqVgYXZbm5Cw6K_pO1Tew@mail.gmail.com> <f6cfd4f0-421e-459e-a26c-4bd8f545d913@cs.tcd.ie>
In-Reply-To: <f6cfd4f0-421e-459e-a26c-4bd8f545d913@cs.tcd.ie>
From: Rob Sayre <sayrer@gmail.com>
Date: Wed, 06 Nov 2024 10:40:49 -0800
Message-ID: <CAChr6SxCvxZieRQkapOPfSnzuMDmU=iF+eNjHX-UKhaVRYZFvg@mail.gmail.com>
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Content-Type: multipart/alternative; boundary="000000000000f6921a062642db57"
Message-ID-Hash: 6YNFRFRS4WDGH7R4I4GGSJIBYTW5P5YK
X-Message-ID-Hash: 6YNFRFRS4WDGH7R4I4GGSJIBYTW5P5YK
X-MailFrom: sayrer@gmail.com
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-tls.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: tls@ietf.org
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [TLS] Re: FATT process update
List-Id: "This is the mailing list for the Transport Layer Security working group of the IETF." <tls.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/tls/pBTbHY61kRbaXDbWdhRKRPbgcO4>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tls>
List-Help: <mailto:tls-request@ietf.org?subject=help>
List-Owner: <mailto:tls-owner@ietf.org>
List-Post: <mailto:tls@ietf.org>
List-Subscribe: <mailto:tls-join@ietf.org>
List-Unsubscribe: <mailto:tls-leave@ietf.org>
On Wed, Nov 6, 2024 at 10:00 AM Stephen Farrell <stephen.farrell@cs.tcd.ie> wrote: > > The process/description is getting better thanks. > Yes, agree. > > Using the term liaison will confuse people so be > better to change that. > Yep, it's correct English/French, but it has an IETF meaning that is more specialized. But, see below about this issue and others. > > I still dislike encouraging private discussion of > drafts - that's not really in the spirit of the > IETF at all. > I think it is OK to do this. We could compare it to the way we keep IESG minutes. These people are busy in a similar way, and they need a somewhat private process in order to respect their time. I think the current document is way too long. What we can do is make it a regular IETF design team. I think we did need this detail to figure out what we are doing, but all the extensive explanations are not necessary for the final output. I'm not going to do a PR to delete them, because it doesn't feel good to do a PR that just deletes other people's work. But I would encourage the authors to pick up a red pen with an aim for many deletions. The edit I will suggest is this, to start: "The FATT panel is similar to a design team as defined in Section 6.5 in RFC 2418". I would say that should go. If we start with ""The FATT panel is a design team as defined in Section 6.5 in RFC 2418". Then, a lot of the process details can also go, since I doubt they will be followed anyway. Not because what's there now is wrong, but because they will just do their own thing. We can once again refer to: https://datatracker.ietf.org/doc/statement-iesg-on-design-teams-20011221/ Here, we're interested in the last phrase: "* any design team that lasts for more than a few months should make regular public reports on what they are doing." thanks, Rob
- [TLS] FATT process update Joseph Salowey
- [TLS] Re: FATT process update Rob Sayre
- [TLS] Re: FATT process update Salz, Rich
- [TLS] Re: FATT process update Rob Sayre
- [TLS] Re: FATT process update Stephen Farrell
- [TLS] Re: FATT process update Rob Sayre
- [TLS] Re: FATT process update Salz, Rich
- [TLS] Re: FATT process update Stephen Farrell
- [TLS] Re: FATT process update Muhammad Usama Sardar