diff --git a/draft-ietf-rats-eat.html b/draft-ietf-rats-eat.html index 8cf30413..28392a92 100644 --- a/draft-ietf-rats-eat.html +++ b/draft-ietf-rats-eat.html @@ -1033,11 +1033,11 @@ Internet-Draft EAT -January 2024 +April 2024 Lundblade, et al. -Expires 17 July 2024 +Expires 3 October 2024 [Page] @@ -1050,12 +1050,12 @@
draft-ietf-rats-eat-latest
Published:
- +
Intended Status:
Standards Track
Expires:
-
+
Authors:
@@ -1064,6 +1064,7 @@
G. Mandyam
+
Mediatek USA
J. O'Donoghue
@@ -1105,7 +1106,7 @@

time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress."

- This Internet-Draft will expire on 17 July 2024.

+ This Internet-Draft will expire on 3 October 2024.

[COSE.X509.Draft]
@@ -4854,11 +4854,11 @@

[SUIT.Manifest]
-Moran, B., Tschofenig, H., Birkholz, H., Zandberg, K., and O. Rønningstad, "A Concise Binary Object Representation (CBOR)-based Serialization Format for the Software Updates for Internet of Things (SUIT) Manifest", Work in Progress, Internet-Draft, draft-ietf-suit-manifest-24, , <https://datatracker.ietf.org/doc/html/draft-ietf-suit-manifest-24>.
+Moran, B., Tschofenig, H., Birkholz, H., Zandberg, K., and O. Rønningstad, "A Concise Binary Object Representation (CBOR)-based Serialization Format for the Software Updates for Internet of Things (SUIT) Manifest", Work in Progress, Internet-Draft, draft-ietf-suit-manifest-25, , <https://datatracker.ietf.org/doc/html/draft-ietf-suit-manifest-25>.

[UCCS]
-Birkholz, H., O'Donoghue, J., Cam-Winget, N., and C. Bormann, "A CBOR Tag for Unprotected CWT Claims Sets", Work in Progress, Internet-Draft, draft-ietf-rats-uccs-07, , <https://datatracker.ietf.org/doc/html/draft-ietf-rats-uccs-07>.
+Birkholz, H., O'Donoghue, J., Cam-Winget, N., and C. Bormann, "A CBOR Tag for Unprotected CWT Claims Sets", Work in Progress, Internet-Draft, draft-ietf-rats-uccs-09, , <https://datatracker.ietf.org/doc/html/draft-ietf-rats-uccs-09>.
[W3C.GeoLoc]
@@ -6133,6 +6133,7 @@

Giridhar Mandyam
+
Mediatek USA
- + Mediatek USA
giridhar.mandyam@gmail.com
@@ -46,12 +46,12 @@ carl@redhoundsoftware.com - + Security RATS signing attestation cbor - + An Entity Attestation Token (EAT) provides an attested claims set that describes state and characteristics of an entity, @@ -62,7 +62,7 @@ claims. - +
Introduction @@ -1264,7 +1264,7 @@ It can occur in any place that a CWT or JWT occurs, for example as a submodule n MUST be wrapped in a byte string when the encoding is CBOR and be base64url-encoded when the encoding is JSON - For CBOR-encoded detached EAT bundles, tag TBD602 can be used to identify it. + For CBOR-encoded detached EAT bundles, tag 602 can be used to identify it. The standard rules apply for use or non-use of a tag. When it is sent as a submodule, it is always sent as a tag to distinguish it from the other types of nested tokens. The digests of the detached claims sets are associated with detached Claims-Sets by label/name. @@ -1273,7 +1273,7 @@ Since the names are used only in the detached EAT bundle, they can be very short -ueid-label = JC< "ueid", 256 > -sueids-label = JC< "sueids", 257 > -oemid-label = JC< "oemid", 258 > -hardware-model-label = JC< "hwmodel", 259 > -hardware-version-label = JC< "hwversion", 260 > -oem-boot-label = JC< "oemboot", 262 > -debug-status-label = JC< "dbgstat", 263 > -location-label = JC< "location", 264 > -profile-label = JC< "eat_profile",265 > -submods-label = JC< "submods", 266 > - -uptime-label = JC< "uptime", TBD > -boot-seed-label = JC< "bootseed", TBD > -intended-use-label = JC< "intuse", TBD > -dloas-label = JC< "dloas", TBD > -sw-name-label = JC< "swname", TBD > -sw-version-label = JC< "swversion", TBD > -manifests-label = JC< "manifests", TBD > -measurements-label = JC< "measurements", TBD > -measurement-results-label = JC< "measres" , TBD > -boot-count-label = JC< "bootcount", TBD > +nonce-label = JC< "eat_nonce", 10 > +ueid-label = JC< "ueid", 256 > +sueids-label = JC< "sueids", 257 > +oemid-label = JC< "oemid", 258 > +hardware-model-label = JC< "hwmodel", 259 > +hardware-version-label = JC< "hwversion", 260 > +uptime-label = JC< "uptime", 261 > +oem-boot-label = JC< "oemboot", 262 > +debug-status-label = JC< "dbgstat", 263 > +location-label = JC< "location", 264 > +profile-label = JC< "eat_profile", 265 > +submods-label = JC< "submods", 266 > +boot-count-label = JC< "bootcount", 267 > +boot-seed-label = JC< "bootseed", 268 > +dloas-label = JC< "dloas", 269 > +sw-name-label = JC< "swname", 270 > +sw-version-label = JC< "swversion", 271 > +manifests-label = JC< "manifests", 272 > +measurements-label = JC< "measurements", 273 > +measurement-results-label = JC< "measres" , 274 > +intended-use-label = JC< "intuse", 275 > ]]> @@ -2243,7 +2242,7 @@ Claim 262 should be renamed from "secboot" to "oemboot" in the JWT registry and JWT Claim Name: "hwversion"
  • - Claim Key: TBD 260 + Claim Key: 260
  • Claim Value Type(s): array @@ -2387,7 +2386,7 @@ Claim 262 should be renamed from "secboot" to "oemboot" in the JWT registry and JWT Claim Name: "uptime"
  • - Claim Key: TBD + Claim Key: 261
  • Claim Value Type(s): uint @@ -2411,7 +2410,7 @@ Claim 262 should be renamed from "secboot" to "oemboot" in the JWT registry and JWT Claim Name: "bootcount"
  • - Claim Key: TBD + Claim Key: 267
  • Claim Value Type(s): uint @@ -2435,7 +2434,7 @@ Claim 262 should be renamed from "secboot" to "oemboot" in the JWT registry and JWT Claim Name: "bootseed"
  • - Claim Key: TBD + Claim Key: 268
  • Claim Value Type(s): bstr @@ -2459,7 +2458,7 @@ Claim 262 should be renamed from "secboot" to "oemboot" in the JWT registry and JWT Claim Name: "dloas"
  • - Claim Key: TBD + Claim Key: 269
  • Claim Value Type(s): array @@ -2483,7 +2482,7 @@ Claim 262 should be renamed from "secboot" to "oemboot" in the JWT registry and JWT Claim Name: "swname"
  • - Claim Key: TBD + Claim Key: 270
  • Claim Value Type(s): tstr @@ -2507,7 +2506,7 @@ Claim 262 should be renamed from "secboot" to "oemboot" in the JWT registry and JWT Claim Name: "swversion"
  • - Claim Key: TBD + Claim Key: 271
  • Claim Value Type(s): array @@ -2531,7 +2530,7 @@ Claim 262 should be renamed from "secboot" to "oemboot" in the JWT registry and JWT Claim Name: "manifests"
  • - Claim Key: TBD + Claim Key: 272
  • Claim Value Type(s): array @@ -2555,7 +2554,7 @@ Claim 262 should be renamed from "secboot" to "oemboot" in the JWT registry and JWT Claim Name: "measurements"
  • - Claim Key: TBD + Claim Key: 273
  • Claim Value Type(s): array @@ -2579,7 +2578,7 @@ Claim 262 should be renamed from "secboot" to "oemboot" in the JWT registry and JWT Claim Name: "measres"
  • - Claim Key: TBD + Claim Key: 274
  • Claim Value Type(s): array @@ -2603,7 +2602,7 @@ Claim 262 should be renamed from "secboot" to "oemboot" in the JWT registry and JWT Claim Name: "intuse"
  • - Claim Key: TBD + Claim Key: 275
  • Claim Value Type(s): uint @@ -2663,7 +2662,7 @@ specification reference. - TBD602 + 602 array Detached EAT Bundle @@ -3146,7 +3145,7 @@ specification reference. Nexus Group - + This document specifies a CBOR encoding of X.509 certificates. The resulting certificates are called C509 Certificates. The CBOR @@ -3155,16 +3154,17 @@ specification reference. eUICC, and CA/Browser Forum Baseline Requirements profiles. When used to re-encode DER encoded X.509 certificates, the CBOR encoding can in many cases reduce the size of RFC 7925 profiled certificates - with over 50%. The CBOR encoded structure can alternatively be + with over 50% while also significantly reducing memory and code size + compared to ASN.1. The CBOR encoded structure can alternatively be signed directly ("natively signed"), which does not require re- encoding for the signature to be verified. The document also - specifies C509 COSE headers, a C509 TLS certificate type, and a C509 - file format. + specifies C509 Certificate Signing Requests, C509 COSE headers, a + C509 TLS certificate type, and a C509 file format. - + @@ -3181,7 +3181,7 @@ specification reference. Universität Bremen TZI - + When transported over secure channels, CBOR Web Token (CWT, RFC 8392) Claims Sets may not need the protection afforded by wrapping them @@ -3192,7 +3192,7 @@ specification reference. - + @@ -3211,7 +3211,7 @@ specification reference. Nordic Semiconductor - + This specification describes the format of a manifest. A manifest is a bundle of metadata about code/data obtained by a recipient (chiefly @@ -3224,7 +3224,7 @@ specification reference. - + @@ -4316,1116 +4316,1117 @@ document:
    • diff --git a/index.html b/index.html index f8f7c32b..b2f0f339 100644 --- a/index.html +++ b/index.html @@ -141,7 +141,7 @@

    Preview for branch bstr-again

    EAT plain text - same as master + diff with master

    Preview for branch bundle