Re: [Rats] draft-ounsworth-rats-x509-evidence-00

[Henk Birkholz <[e-mail]>]

Hi Hannes,

If we agree on a content style template/example based for the "new" 
Claims in the I-D, I'll commit to adding the existing EAT Claims (only 
Claims that made it to the registry yet) based on that style asap.

Viele Grüße,

Henk

On 09.11.23 15:48, [e-mail] wrote:
> Hi Henk,
> 
> I am wondering whether it takes long to make this mapping of the claims. Since you expressed interesting in helping with the draft, this may be something you could be looking at 😉
> 
> Now I am more worried about the time delay introduced via the process.
> 
> Ciao
> Hannes
> 
> -----Original Message-----
> From: Henk Birkholz <[e-mail]>
> Sent: Donnerstag, 9. November 2023 15:43
> To: [e-mail]; 'Carl Wallace' <[e-mail]>; [e-mail]
> Subject: Re: [Rats] draft-ounsworth-rats-x509-evidence-00
> 
> On 09.11.23 15:40, [e-mail] wrote:
>> Hi Carl,
>>
>> A few responses below:
>>
>> * The use of CBOR/COSE in SUIT: At the start of the SUIT working group the participants expressed a strong preference to use CBOR/COSE and didn't want to use ASN.1/CMS. Brendan and I had written a draft that used ASN.1, which was inspired by work Russ did. It happens that work being proposed does not align with the expectations of the group. I remember Henk and Carsten being vocal proponents of CBOR & COSE at that time. Was it a good idea to use CBOR/COSE instead of ASN.1/CMS? Now that the standardization and implementation work is almost finished it is a bit too late to ask this question again.
>>
>> * Do we want to provide claim definitions in ASN.1 format (as we do in the draft)? That was our understanding from the design team discussions.
>>
>> * Should we keep the definition of the CBOR/COSE claim definitions in sync with the ASN.1 format? I believe there is value in doing so. There does not seem to be anything wrong with the semantics of the claims in EAT. We have received feedback already for better alignment since we have introduced a few bugs in the -00 submission.
>>
>> * A question you did not ask was: Should all claims in EAT also be described in an ASN.1 format? Currently the draft only contains a subset of the claims. I have been asking myself the same question. It is somewhat likely that sooner or later all claims defined in EAT will need to be available in ASN.1 format.
> 
> Had the same thought, did not dare to voice it. I can imagine Mike groaning (as he wants to move fast). Not sure, if this I-D is the one to do that. Mike?
> 
>>
>> Ciao
>> Hannes
>>
>> -----Original Message-----
>> From: RATS <[e-mail]> On Behalf Of Carl Wallace
>> Sent: Donnerstag, 9. November 2023 14:45
>> To: Henk Birkholz <[e-mail]>; [e-mail]
>> Subject: Re: [Rats] draft-ounsworth-rats-x509-evidence-00
>>
>>
>> On 11/9/23, 8:09 AM, "RATS on behalf of Henk Birkholz" <[e-mail] <mailto:[e-mail]> on behalf of [e-mail] <mailto:[e-mail]>> wrote:
>>
>>
>> I think this discussion is mood as was pointed out in the meeting already. Please see:
>>
>>
>> https://www.rfc-editor.org/rfc/rfc9334.html#figure-9
>> <https://www.rfc-editor.org/rfc/rfc9334.html#figure-9>
>>
>> [CW] I don't think that diagram renders this discussion moot. X.509 certificate-based attestations have existed since before RATS (and before we called attestation evidence). There's not even much question about potential for including claims in an X.509 certificate within current RATS documents (see section C.3 of EAT). I think the questions are: 1) do we want to provide ASN.1 definitions for claims and 2) do we want to keep claim definitions (roughly) in sync across ASN.1/CBOR/JSON. Re: 1), there's seems to be general acceptance of defining claims in ASN.1 for the most part (though no one really answered Brendan's question regarding why ASN.1 was disallowed for SUIT but is allowed here). Question 2) needs some more discussion. There was an exchange between Mike and Laurence during the presentation yesterday that highlights a potential difference of opinion between I-D author(s) and participants in the working group that could impact the adoption question.
>>
>> On 09.11.23 14:05, [e-mail] <mailto:[e-mail]> wrote:
>>> Hi Laurence,
>>>
>>> The charter says:
>>>
>>> “
>>>
>>> Standardize data models that implement and secure the defined
>>> information model (e.g., CBOR Web Token structures [RFC8392
>>> <https://datatracker.ietf.org/doc/rfc8392/>
>>> <https://datatracker.ietf.org/doc/rfc8392/&gt;>], JSON Web Token
>>> structures
>>> [RFC7519 <https://datatracker.ietf.org/doc/rfc7519/> <https://datatracker.ietf.org/doc/rfc7519/&gt;>]).
>>>
>>> “
>>>
>>> CWT and JWT are mentioned as examples. The group already works on
>>> another evidence format, namely the TPM-based stuff.
>>>
>>> I would say that the document fits nicely within the scope of the charter.
>>>
>>> Regarding the document split. I am open to discussions about your
>>> suggestion, which assumes adoption in the group.
>>>
>>> Ciao
>>>
>>> Hannes
>>>
>>> *From:*RATS <[e-mail] <mailto:[e-mail]>>
>>> *On Behalf Of *lgl island-resort.com
>>> *Sent:* Donnerstag, 9. November 2023 13:59
>>> *To:* rats <[e-mail] <mailto:[e-mail]>>
>>> *Subject:* [Rats] draft-ounsworth-rats-x509-evidence-00
>>>
>>> I think it might be better to split this into two drafts.
>>>
>>> First, define how to put CWT/JWT claims into ASN.1 and make an X.509
>>> attestation token.
>>>
>>> Second, define the FIPS and CC status claims for CBOR, JSON and ASN.1.
>>>
>>> I wish we didn’t have to do the first, but understand that we might.
>>> Note that the RATS charter says we work on CBOR and JSON. There was a
>>> little discussion about ASN.1 back in the early days and we certainly
>>> put it off back then. There was also YANG discussion. Search the RATS
>>> mail archive for ASN.1.
>>>
>>> I’m much more interested in the FIPS and CC status claims. I would
>>> like to define them for CBOR, JSON and ASN.1. If they are booleans
>>> this is trivial. The would get registered in the CWT and JWT IANA registries.
>>>
>>> One of the reasons I’d like to define them for CBOR and JSON is so
>>> there’s a known and accepted way to translate their ASN.1 claims into JSON.
>>>
>>> Also, the X.509 definition should be for Attestation Results as well
>>> as Evidence. There’s no reason to restrict it and there’s no work to
>>> allow use as Attestation Results.
>>>
>>> LL
>>>
>>> (sent incorrectly the first time only to the rats-chairs; meant it
>>> for the list)
>>>
>>>
>>> _______________________________________________
>>> RATS mailing list
>>> [e-mail] <mailto:[e-mail]>
>>> https://www.ietf.org/mailman/listinfo/rats
>>> <https://www.ietf.org/mailman/listinfo/rats>
>>
>>
>> _______________________________________________
>> RATS mailing list
>> [e-mail] <mailto:[e-mail]>
>> https://www.ietf.org/mailman/listinfo/rats
>> <https://www.ietf.org/mailman/listinfo/rats>
>>
>>
>>
>>
>> _______________________________________________
>> RATS mailing list
>> [e-mail]
>> https://www.ietf.org/mailman/listinfo/rats
>>
>