Re: [Rats] FW: New Version Notification for draft-lundblade-rats-eat-media-type-00.txt

Hi RATS & Thomas,

Let me briefly describe why I took a different path than RATS.

Ever since my XML/XSD days back in Y2K, I have used *self-identifying objects* based on a top-level identifier.  After abandoning XML, I applied this concept to JSON [1], and more recently to CBOR [2].

Using this method, the media type (when needed) is simply the core type: text/xml, application/json, and application/cbor respectively.

To make end-points capable dealing with multiple object types, a register of accepted object types is needed.  In my own designs, the entire object is read (into a DOM-like structure), and subsequently dispatched to the object-specific executor.

Self-identified objects can be stored as well as embedded in other objects without loosing their type id.

Unlike application-specific methods, this concept is designed to be fully universal.  The JSON-variant is inspired by the pretty high-profile verified credentials [3] effort.

Thanx,
Anders

1] {"@context": "https://example.com/myobject", json-data}

2] 211TBD(["https://example.com/myobject", cbor-data])

3] https://www.w3.org/TR/vc-data-model/#example-a-simple-example-of-a-verifiable-credential

On 2022-05-26 10:31, Thomas Fossati wrote:
> Hi RATS,
> 
> Laurence, Henk and I have put together a short draft that defines and registers a bunch of media types for EAT.
> 
> Have a look and tell us what you think.
> 
> Cheers, thanks!
> 
> *From: *internet-drafts@ietf.org <internet-drafts@ietf.org>
> *Date: *Thursday, 26 May 2022 at 08:36
> *To: *Henk Birkholz <henk.birkholz@sit.fraunhofer.de>, Laurence Lundblade <lgl@securitytheory.com>, Thomas Fossati <Thomas.Fossati@arm.com>
> *Subject: *New Version Notification for draft-lundblade-rats-eat-media-type-00.txt
> 
> 
> A new version of I-D, draft-lundblade-rats-eat-media-type-00.txt
> has been successfully submitted by Laurence Lundblade and posted to the
> IETF repository.
> 
> Name:           draft-lundblade-rats-eat-media-type
> Revision:       00
> Title:          EAT Media Types
> Document date:  2022-05-26
> Group:          Individual Submission
> Pages:          12
> URL: https://www.ietf.org/archive/id/draft-lundblade-rats-eat-media-type-00.txt <https://www.ietf.org/archive/id/draft-lundblade-rats-eat-media-type-00.txt>
> Status: https://datatracker.ietf.org/doc/draft-lundblade-rats-eat-media-type/ <https://datatracker.ietf.org/doc/draft-lundblade-rats-eat-media-type/>
> Html: https://www.ietf.org/archive/id/draft-lundblade-rats-eat-media-type-00.html <https://www.ietf.org/archive/id/draft-lundblade-rats-eat-media-type-00.html>
> Htmlized: https://datatracker.ietf.org/doc/html/draft-lundblade-rats-eat-media-type <https://datatracker.ietf.org/doc/html/draft-lundblade-rats-eat-media-type>
> 
> 
> Abstract:
>     Payloads used in Remote Attestation Procedures may require an
>     associated media type for their conveyance, for example when used in
>     RESTful APIs.
> 
>     This memo defines media types to be used for Entity Attestation
>     Tokens (EAT).
> 
> 
> 
> 
> The IETF Secretariat
> 
> IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.
> 
> _______________________________________________
> RATS mailing list
> RATS@ietf.org
> https://www.ietf.org/mailman/listinfo/rats