[Rats] John Scudder's No Objection on charter-ietf-rats-01-00: (with COMMENT)

John Scudder via Datatracker <noreply@ietf.org> Wed, 04 May 2022 20:48 UTC

Return-Path: <noreply@ietf.org>
X-Original-To: rats@ietf.org
Delivered-To: rats@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id A21C3C159A3E; Wed, 4 May 2022 13:48:18 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: John Scudder via Datatracker <noreply@ietf.org>
To: The IESG <iesg@ietf.org>
Cc: rats-chairs@ietf.org, rats@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 8.1.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: John Scudder <jgs@juniper.net>
Message-ID: <165169729864.21964.9834851467209462620@ietfa.amsl.com>
Date: Wed, 04 May 2022 13:48:18 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/rats/7TXKdLqINE3KL2EIH_a2_xCyNBA>
Subject: [Rats] John Scudder's No Objection on charter-ietf-rats-01-00: (with COMMENT)
X-BeenThere: rats@ietf.org
X-Mailman-Version: 2.1.34
List-Id: Remote ATtestation procedureS <rats.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rats>, <mailto:rats-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rats/>
List-Post: <mailto:rats@ietf.org>
List-Help: <mailto:rats-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rats>, <mailto:rats-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 04 May 2022 20:48:18 -0000

John Scudder has entered the following ballot position for
charter-ietf-rats-01-00: 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-rats/



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

I’m a little confused by:

5. Standardize interoperable protocols to securely convey evidence and
attestation results with a strong preference to use existing protocols.

The intent seems right, but if you “use existing protocols” doesn’t that mean
you aren’t “standardizing… protocols” (because they’ve already been
standardized)?

Nit, looks like a CRLF got lost before the second asterisk here:

* operational state and measurements of steps which led to the operational
state, or * other factors that could influence trust decisions.