Re: [Rats] I-D Action: draft-ietf-rats-eat-20.txt

Carsten Bormann <cabo@tzi.org> Sat, 17 June 2023 12:27 UTC

Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.7\))
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <168669220478.20924.5666203131876501501@ietfa.amsl.com>
Date: Sat, 17 Jun 2023 14:27:06 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <F12D8D6D-563A-45F6-A09F-73BF96BF9E9F@tzi.org>
References: <168669220478.20924.5666203131876501501@ietfa.amsl.com>
To: rats@ietf.org
Archived-At: <https://mailarchive.ietf.org/arch/msg/rats/H8qXwQywD0W6x4QcC9Iwd5LYl2s>
Subject: Re: [Rats] I-D Action: draft-ietf-rats-eat-20.txt
Precedence: list

I’m not following this draft closely, but I have a quick editorial comment:

Section 2 (terminology) defines the term "Base64url Encoding”, referencing RFC 4648 as well as RFC 7515 to fill in the open questions from RFC 4648.

So far, so good.

This term is then never used.

A term "base64url encoded” (or [correct] variant spelling “base64url-encoded”) is used in multiple places.  One of the places restates its own reference to RFC 4648, but doesn’t restate the reference to RFC 7515 and the text required with that.  This restatement is very misleading as it strongly implies RFC 7515 is *not* used here; the reference needs to be removed.  In the other places I find the term is simply used, which assumes the reader will think to look up the term in the terminology and make the match with the different term.  An internal cross-reference might help.

Grüße, Carsten

> On 2023-06-13, at 23:36, internet-drafts@ietf.org wrote:
> 
> 
> A New Internet-Draft is available from the on-line Internet-Drafts
> directories. This Internet-Draft is a work item of the Remote ATtestation
> ProcedureS (RATS) WG of the IETF.
> 
>   Title           : The Entity Attestation Token (EAT)
>   Authors         : Laurence Lundblade
>                     Giridhar Mandyam
>                     Jeremy O'Donoghue
>                     Carl Wallace
>   Filename        : draft-ietf-rats-eat-20.txt
>   Pages           : 100
>   Date            : 2023-06-13
> 
> Abstract:
>   An Entity Attestation Token (EAT) provides an attested claims set
>   that describes state and characteristics of an entity, a device like
>   a smartphone, IoT device, network equipment or such.  This claims set
>   is used by a relying party, server or service to determine how much
>   it wishes to trust the entity.
> 
>   An EAT is either a CBOR Web Token (CWT) or JSON Web Token (JWT) with
>   attestation-oriented claims.
> 
> The IETF datatracker status page for this Internet-Draft is:
> https://datatracker.ietf.org/doc/draft-ietf-rats-eat/
> 
> There is also an htmlized version available at:
> https://datatracker.ietf.org/doc/html/draft-ietf-rats-eat-20
> 
> A diff from the previous version is available at:
> https://author-tools.ietf.org/iddiff?url2=draft-ietf-rats-eat-20
> 
> Internet-Drafts are also available by rsync at rsync.ietf.org::internet-drafts
> 
>

[Rats] I-D Action: draft-ietf-rats-eat-20.txt internet-drafts
Re: [Rats] I-D Action: draft-ietf-rats-eat-20.txt Carsten Bormann
Re: [Rats] I-D Action: draft-ietf-rats-eat-20.txt lgl island-resort.com