[Secret] John Scudder's No Objection on charter-ietf-tigress-00-03: (with COMMENT)

John Scudder via Datatracker <noreply@ietf.org> Thu, 30 June 2022 01:06 UTC

Return-Path: <noreply@ietf.org>
X-Original-To: secret@ietf.org
Delivered-To: secret@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 44822C15AAC6; Wed, 29 Jun 2022 18:06:14 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: John Scudder via Datatracker <noreply@ietf.org>
To: The IESG <iesg@ietf.org>
Cc: tigress-chairs@ietf.org, secret@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 8.5.1
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: John Scudder <jgs@juniper.net>
Message-ID: <165655117426.26132.17929474703754734067@ietfa.amsl.com>
Date: Wed, 29 Jun 2022 18:06:14 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/secret/-PERANFe7oGZuIO2HwfbCsvAf_A>
Subject: [Secret] John Scudder's No Objection on charter-ietf-tigress-00-03: (with COMMENT)
X-BeenThere: secret@ietf.org
X-Mailman-Version: 2.1.39
List-Id: Secure Credential Transfer <secret.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/secret>, <mailto:secret-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/secret/>
List-Post: <mailto:secret@ietf.org>
List-Help: <mailto:secret-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/secret>, <mailto:secret-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 30 Jun 2022 01:06:14 -0000

John Scudder has entered the following ballot position for
charter-ietf-tigress-00-03: No Objection

When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)



The document, along with other ballot positions, can be found here:
https://datatracker.ietf.org/doc/charter-ietf-tigress/



----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------

I agree with Murray's comment that the second paragraph makes it appear a whole
lot like the solution is already decided, now all we have to do is figure out
how to back into it. :-(

Other than that, my only other comment is that this is the only time I've ever
seen an IETF charter feel the need to disclaim device UI considerations. Surely
that goes without saying?