[saag] A few comments

S Moonesamy <sm+ietf@elandsys.com> Wed, 05 August 2026 13:01 UTC

Return-Path: <sm@elandsys.com>
X-Original-To: saag@mail2.ietf.org
Delivered-To: saag@mail2.ietf.org
Received: from localhost (localhost [127.0.0.1]) by mail2.ietf.org (Postfix) with ESMTP id 44F6D12414968 for <saag@mail2.ietf.org>; Wed, 5 Aug 2026 06:01:19 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1785934879; bh=abjEJuJgUJTiIbMST+VRIfdsOfdQXSzxOvzyvN0hNso=; h=Date:To:From:Subject:In-Reply-To:References; b=Iy5fhvF/dbLZHvLJO6Quut7EGEowaPDk3ni1OEvw61QRtFxaNZSGeTBW0oQqSi/Ax bj6KZIEiH8/drOWvko/ZrDcLmSkiBfauAf3le1hwsOBXK2G50DbWOzy1GrR8I3fCtI b5+lhZ12k1Il1QicU1w7bABEZqIv89o0g+2suWIY=
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -1.7
X-Spam-Level:
X-Spam-Status: No, score=-1.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=no autolearn_force=no
Authentication-Results: mail2.ietf.org (amavisd-new); dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=elandsys.com
Received: from mail2.ietf.org ([166.84.6.31]) by localhost (mail2.ietf.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HXHlDmrUMH2i for <saag@mail2.ietf.org>; Wed, 5 Aug 2026 06:01:18 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by mail2.ietf.org (Postfix) with ESMTP id 4EB3A12413B68 for <saag@ietf.org>; Wed, 5 Aug 2026 06:00:30 -0700 (PDT)
Received: from DESKTOP-K6V9C2L.elandsys.com ([102.117.145.19]) (authenticated bits=0) by mx.elandsys.com (8.15.2/8.14.5) with ESMTPSA id 675Cx3b7029911 (version=TLSv1 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 5 Aug 2026 05:59:58 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=elandsys.com; s=mail; t=1785934800; x=1786021200; i=@elandsys.com; bh=abjEJuJgUJTiIbMST+VRIfdsOfdQXSzxOvzyvN0hNso=; h=Date:To:From:Subject:In-Reply-To:References; b=Ko5BpwYSemiTLiYnl7A6lO11P7S6ks8vWABk9DTJ3LHAd685YJeAyA1IadXE9msBv nsbcKBXXzhl+GS2toBj9fK9/y23/sXTeXfqY7QFPEyeyfYcdB+SHzOCtUF4c1C8cOW Ujt8Tjd1wa7J4COzQocWwQ2xqCGLAWBP44AG/Gdg=
Message-Id: <6.2.5.6.2.20260805042440.0fcb28d8@elandnews.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Wed, 05 Aug 2026 05:55:57 -0700
To: Tanja Lange <tanja@hyperelliptic.org>, saag@ietf.org
From: S Moonesamy <sm+ietf@elandsys.com>
In-Reply-To: <amypaHNTh0Ya7XF+@ein.win.tue.nl>
References: <CAEzBKQ4fymnSeo8tgqMLOfKopvMGk4xnDq=SQJKf-RBL4-uh6g@mail.gmail.com> <CAEEbLAbhZUpempA9Rvjhm1qrLfBWXa_2ntdfpO20cqDu0h5fbQ@mail.gmail.com> <CAEzBKQ6NOzQc66T+SEdSvLa2gxjtO77DYUUWuTfr99zV_a-Ofg@mail.gmail.com> <c8a74833-35cd-44a0-8992-e5463a82aa8f@dennis-jackson.uk> <F95592F7-6E60-4835-B21C-B5B1954084F7@kenkubota.de> <b3321e23-5f9b-4f8a-8bd9-d2cca2800d67@lear.ch> <amypaHNTh0Ya7XF+@ein.win.tue.nl>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Message-ID-Hash: 56AOBK2BEV3UW6ZISFRF46AQWA4ZGGVQ
X-Message-ID-Hash: 56AOBK2BEV3UW6ZISFRF46AQWA4ZGGVQ
X-MailFrom: sm@elandsys.com
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-saag.ietf.org-0; header-match-saag.ietf.org-1; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [saag] A few comments
List-Id: Security Area Advisory Group <saag.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/saag/KdbrdBK2Rn5JVKjAFYRaJB9Av-Q>
List-Archive: <https://mailarchive.ietf.org/arch/browse/saag>
List-Help: <mailto:saag-request@ietf.org?subject=help>
List-Owner: <mailto:saag-owner@ietf.org>
List-Post: <mailto:saag@ietf.org>
List-Subscribe: <mailto:saag-join@ietf.org>
List-Unsubscribe: <mailto:saag-leave@ietf.org>

Dear Ms Lange,

I read the comment which was sent to the TLS mailing list.  I'll 
comment on the following:

At 06:55 AM 31-07-2026, Tanja Lange wrote:
>The requests I've seen, starting right after the chairs announced their
>decision that there was consensus in favor of the document, are asking for
>which input was discarded or counted higher or lower. I cannot do the
>"homework" of checking this because I don't know the mechanism used.

There isn't a defined mechanism on how to decide whether a document 
is ready for publication.  The practice has been to do a working 
group last call and assess the feedback.  I remember that you 
reviewed a draft (it had some crypto stuff) which I submitted a while 
ago.  I would most likely give your feedback some weight on the 
technical aspects.  I would also do something similar for other 
participants.  The weighing would be on the technical points.

If a technical point was not adequately considered, the person who 
raised the point might raise it again during the Last Call.  If there 
were several points which were not adequately considered, there would 
be more people raising them during the Last Call.  It makes sense (to 
me) to inform the community about the concerns.

The tricky part is finding a balance instead of having a majority 
calling the shots [1].  Let's assume that I did a count and ended up 
with 51% in favour (re. RFC 2418, Page 13).  If that was any type of 
consensus, it's not that different from voting and it is definitely 
not anything close to finding a balance.

Regards,
S. Moonesamy

1. https://www.britannica.com/dictionary/shot