Skip to content

Commit

Permalink
Script updating gh-pages from d7be8b1. [ci skip]
Browse files Browse the repository at this point in the history
  • Loading branch information
ID Bot committed May 5, 2024
1 parent 5c78cf0 commit 2cf7978
Show file tree
Hide file tree
Showing 8 changed files with 1,169 additions and 17,392 deletions.
47 changes: 20 additions & 27 deletions draft-ietf-rats-eat.html
View file
Original file line number Diff line number Diff line change
Expand Up @@ -1033,11 +1033,11 @@
<thead><tr>
<td class="left">Internet-Draft</td>
<td class="center">EAT</td>
<td class="right">April 2024</td>
<td class="right">May 2024</td>
</tr></thead>
<tfoot><tr>
<td class="left">Lundblade, et al.</td>
<td class="center">Expires 17 October 2024</td>
<td class="center">Expires 6 November 2024</td>
<td class="right">[Page]</td>
</tr></tfoot>
</table>
Expand All @@ -1050,12 +1050,12 @@
<dd class="internet-draft">draft-ietf-rats-eat-latest</dd>
<dt class="label-published">Published:</dt>
<dd class="published">
<time datetime="2024-04-15" class="published">15 April 2024</time>
<time datetime="2024-05-05" class="published">5 May 2024</time>
</dd>
<dt class="label-intended-status">Intended Status:</dt>
<dd class="intended-status">Standards Track</dd>
<dt class="label-expires">Expires:</dt>
<dd class="expires"><time datetime="2024-10-17">17 October 2024</time></dd>
<dd class="expires"><time datetime="2024-11-06">6 November 2024</time></dd>
<dt class="label-authors">Authors:</dt>
<dd class="authors">
<div class="author">
Expand Down Expand Up @@ -1106,7 +1106,7 @@ <h2 id="name-status-of-this-memo">
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."<a href="#section-boilerplate.1-3" class="pilcrow"></a></p>
<p id="section-boilerplate.1-4">
This Internet-Draft will expire on 17 October 2024.<a href="#section-boilerplate.1-4" class="pilcrow"></a></p>
This Internet-Draft will expire on 6 November 2024.<a href="#section-boilerplate.1-4" class="pilcrow"></a></p>
</section>
</div>
<div id="copyright">
Expand Down Expand Up @@ -1580,7 +1580,7 @@ <h2 id="name-copyright-notice">
<p id="section-toc.1-1.18.1"><a href="#appendix-G" class="auto internal xref">Appendix G</a>.  <a href="#name-changes-from-previous-draft" class="internal xref">Changes from Previous Drafts</a></p>
<ul class="compact toc ulBare ulEmpty">
<li class="compact toc ulBare ulEmpty" id="section-toc.1-1.18.2.1">
<p id="section-toc.1-1.18.2.1.1"><a href="#appendix-G.1" class="auto internal xref">G.1</a>.  <a href="#name-from-draft-ietf-rats-eat-25" class="internal xref">From draft-ietf-rats-eat-25</a></p>
<p id="section-toc.1-1.18.2.1.1"><a href="#appendix-G.1" class="auto internal xref">G.1</a>.  <a href="#name-from-draft-ietf-rats-eat-24" class="internal xref">From draft-ietf-rats-eat-24</a></p>
</li>
</ul>
</li>
Expand Down Expand Up @@ -2592,11 +2592,10 @@ <h4 id="name-manifests-software-manifest">
In some cases EAT submodules may be used instead of the array structure in this claim for multiple manifests.<a href="#section-4.2.15-6" class="pilcrow"></a></p>
<p id="section-4.2.15-7">A CoSWID manifest <span class="bcp14">MUST</span> be a payload CoSWID, not an evidence CoSWID.
These are defined in <span>[<a href="#RFC9393" class="cite xref">RFC9393</a>]</span>.<a href="#section-4.2.15-7" class="pilcrow"></a></p>
<p id="section-4.2.15-8">A Software Updates for Internet of Things (SUIT) Manifest <span>[<a href="#SUIT.Manifest" class="cite xref">SUIT.Manifest</a>]</span> may be used.<a href="#section-4.2.15-8" class="pilcrow"></a></p>
<p id="section-4.2.15-9">This claim is extensible for use of manifest formats beyond those mentioned in this document.
<p id="section-4.2.15-8">This claim is extensible for use of manifest formats beyond those mentioned in this document.
No particular manifest format is preferred.
For manifest interoperability, an EAT profile as defined in <a href="#profiles" class="auto internal xref">Section 6</a>, should be used to specify which manifest format(s) are allowed.<a href="#section-4.2.15-9" class="pilcrow"></a></p>
<div class="lang-CDDL sourcecode" id="section-4.2.15-10">
For manifest interoperability, an EAT profile as defined in <a href="#profiles" class="auto internal xref">Section 6</a>, should be used to specify which manifest format(s) are allowed.<a href="#section-4.2.15-8" class="pilcrow"></a></p>
<div class="lang-CDDL sourcecode" id="section-4.2.15-9">
<pre>
$$Claims-Set-Claims //= (
manifests-label =&gt; manifests-type
Expand All @@ -2613,10 +2612,7 @@ <h4 id="name-manifests-software-manifest">
$manifest-body-cbor /= bytes .cbor untagged-coswid
$manifest-body-json /= base64-url-text

$manifest-body-cbor /= bytes .cbor SUIT_Envelope
$manifest-body-json /= base64-url-text

</pre><a href="#section-4.2.15-10" class="pilcrow"></a>
</pre><a href="#section-4.2.15-9" class="pilcrow"></a>
</div>
</section>
</div>
Expand Down Expand Up @@ -3287,7 +3283,7 @@ <h4 id="name-claims-requirements">
<p id="section-6.3.12-4">A profile may constrain the definition of claims that are defined in this document or elsewhere.
For example, a profile may require the EAT nonce be a certain length or the "location" claim always include the altitude.<a href="#section-6.3.12-4" class="pilcrow"></a></p>
<p id="section-6.3.12-5">Some claims are "pluggable" in that they allow different formats for their content.
The "manifests" claim (<a href="#manifests" class="auto internal xref">Section 4.2.15</a>) along with the measurement and "measurements" (<a href="#measurements" class="auto internal xref">Section 4.2.16</a>) claims are examples of this, allowing the use of CoSWID, SUIT Manifest and other formats.
The "manifests" claim (<a href="#manifests" class="auto internal xref">Section 4.2.15</a>) along with the measurement and "measurements" (<a href="#measurements" class="auto internal xref">Section 4.2.16</a>) claims are examples of this, allowing the use of CoSWID and other formats.
A profile should specify which formats are allowed to be sent, with the assumption that the corresponding CoAP content types have been registered.
A profile should require the receiver to accept all formats that are allowed to be sent.<a href="#section-6.3.12-5" class="pilcrow"></a></p>
<p id="section-6.3.12-6">Further, if there is variation within a format that is allowed, the profile should specify which variations can be sent.
Expand Down Expand Up @@ -3668,9 +3664,6 @@ <h4 id="name-payload-cddl">
$manifest-body-cbor /= bytes .cbor untagged-coswid
$manifest-body-json /= base64-url-text

$manifest-body-cbor /= bytes .cbor SUIT_Envelope
$manifest-body-json /= base64-url-text


$$Claims-Set-Claims //= (
measurements-label =&gt; measurements-type
Expand Down Expand Up @@ -4787,10 +4780,6 @@ <h3 id="name-normative-references">
<dd>
<span class="refAuthor">Birkholz, H.</span>, <span class="refAuthor">Fitzgerald-McKay, J.</span>, <span class="refAuthor">Schmidt, C.</span>, and <span class="refAuthor">D. Waltermire</span>, <span class="refTitle">"Concise Software Identification Tags"</span>, <span class="seriesInfo">RFC 9393</span>, <span class="seriesInfo">DOI 10.17487/RFC9393</span>, <time datetime="2023-06" class="refDate">June 2023</time>, <span>&lt;<a href="https://www.rfc-editor.org/rfc/rfc9393">https://www.rfc-editor.org/rfc/rfc9393</a>&gt;</span>. </dd>
<dd class="break"></dd>
<dt id="SUIT.Manifest">[SUIT.Manifest]</dt>
<dd>
<span class="refAuthor">Moran, B.</span>, <span class="refAuthor">Tschofenig, H.</span>, <span class="refAuthor">Birkholz, H.</span>, <span class="refAuthor">Zandberg, K.</span>, and <span class="refAuthor">O. Rønningstad</span>, <span class="refTitle">"A Concise Binary Object Representation (CBOR)-based Serialization Format for the Software Updates for Internet of Things (SUIT) Manifest"</span>, <span class="refContent">Work in Progress</span>, <span class="seriesInfo">Internet-Draft, draft-ietf-suit-manifest-25</span>, <time datetime="2024-02-05" class="refDate">5 February 2024</time>, <span>&lt;<a href="https://datatracker.ietf.org/doc/html/draft-ietf-suit-manifest-25">https://datatracker.ietf.org/doc/html/draft-ietf-suit-manifest-25</a>&gt;</span>. </dd>
<dd class="break"></dd>
<dt id="ThreeGPP.IMEI">[ThreeGPP.IMEI]</dt>
<dd>
<span class="refAuthor">3GPP</span>, <span class="refTitle">"3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; Numbering, addressing and identification"</span>, <time datetime="2019" class="refDate">2019</time>, <span>&lt;<a href="https://portal.3gpp.org/desktopmodules/Specifications/SpecificationDetails.aspx?specificationId=729">https://portal.3gpp.org/desktopmodules/Specifications/SpecificationDetails.aspx?specificationId=729</a>&gt;</span>. </dd>
Expand Down Expand Up @@ -6046,14 +6035,18 @@ <h2 id="name-changes-from-previous-draft">
<p id="appendix-G-2">The following is a list of known changes since the immediately previous drafts. This list is
non-authoritative. It is meant to help reviewers see the significant
differences. A comprehensive history is available via the IETF Datatracker's record for this document.<a href="#appendix-G-2" class="pilcrow"></a></p>
<div id="from-draft-ietf-rats-eat-25">
<div id="from-draft-ietf-rats-eat-24">
<section id="appendix-G.1">
<h3 id="name-from-draft-ietf-rats-eat-25">
<a href="#appendix-G.1" class="section-number selfRef">G.1. </a><a href="#name-from-draft-ietf-rats-eat-25" class="section-name selfRef">From draft-ietf-rats-eat-25</a>
<h3 id="name-from-draft-ietf-rats-eat-24">
<a href="#appendix-G.1" class="section-number selfRef">G.1. </a><a href="#name-from-draft-ietf-rats-eat-24" class="section-name selfRef">From draft-ietf-rats-eat-24</a>
</h3>
<p id="appendix-G.1-1">The changes from draft-24, not draft 25, are listed here as draft-24 is what was accepted after IETF last call and draft-25 was kind of a false start.<a href="#appendix-G.1-1" class="pilcrow"></a></p>
<ul class="normal">
<li class="normal" id="appendix-G.1-1.1">
<p id="appendix-G.1-1.1.1">Change SUIT Manifest reference back to normative<a href="#appendix-G.1-1.1.1" class="pilcrow"></a></p>
<li class="normal" id="appendix-G.1-2.1">
<p id="appendix-G.1-2.1.1">Address some small claim data type naming issues that came to light when IANA completed the registrations requested by this document. In particular, the CDDL type names are used.<a href="#appendix-G.1-2.1.1" class="pilcrow"></a></p>
</li>
<li class="normal" id="appendix-G.1-2.2">
<p id="appendix-G.1-2.2.1">Remove all dependence on SUIT Manifest to break schedule interlock with RFC Editor. Use of SUIT-Manifest is peripheral to the core of EAT. It was mostly a content type pre-registration. The modification consisted of the removal of one sentence, a few more words and two lines of CDDL.<a href="#appendix-G.1-2.2.1" class="pilcrow"></a></p>
</li>
</ul>
</section>
Expand Down
48 changes: 21 additions & 27 deletions draft-ietf-rats-eat.txt
View file
Original file line number Diff line number Diff line change
Expand Up @@ -5,12 +5,12 @@
RATS L. Lundblade
Internet-Draft Security Theory LLC
Intended status: Standards Track G. Mandyam
Expires: 17 October 2024 Mediatek USA
Expires: 6 November 2024 Mediatek USA
J. O'Donoghue
Qualcomm Technologies Inc.
C. Wallace
Red Hound Software, Inc.
15 April 2024
5 May 2024


The Entity Attestation Token (EAT)
Expand Down Expand Up @@ -42,7 +42,7 @@ Status of This Memo
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 October 2024.
This Internet-Draft will expire on 6 November 2024.

Copyright Notice

Expand Down Expand Up @@ -193,7 +193,7 @@ Table of Contents
F.1.3. CBOR Certificate COSE Header Parameters
F.1.4. Claim-Based Key Identification
Appendix G. Changes from Previous Drafts
G.1. From draft-ietf-rats-eat-25
G.1. From draft-ietf-rats-eat-24
Contributors
Authors' Addresses

Expand Down Expand Up @@ -1288,9 +1288,6 @@ Table of Contents
A CoSWID manifest MUST be a payload CoSWID, not an evidence CoSWID.
These are defined in [RFC9393].

A Software Updates for Internet of Things (SUIT) Manifest
[SUIT.Manifest] may be used.

This claim is extensible for use of manifest formats beyond those
mentioned in this document. No particular manifest format is
preferred. For manifest interoperability, an EAT profile as defined
Expand All @@ -1312,9 +1309,6 @@ Table of Contents
$manifest-body-cbor /= bytes .cbor untagged-coswid
$manifest-body-json /= base64-url-text

$manifest-body-cbor /= bytes .cbor SUIT_Envelope
$manifest-body-json /= base64-url-text

4.2.16. measurements (Measurements) Claim

The "measurements" claim contains descriptions, lists, evidence or
Expand Down Expand Up @@ -2058,9 +2052,9 @@ Table of Contents
Some claims are "pluggable" in that they allow different formats for
their content. The "manifests" claim (Section 4.2.15) along with the
measurement and "measurements" (Section 4.2.16) claims are examples
of this, allowing the use of CoSWID, SUIT Manifest and other formats.
A profile should specify which formats are allowed to be sent, with
the assumption that the corresponding CoAP content types have been
of this, allowing the use of CoSWID and other formats. A profile
should specify which formats are allowed to be sent, with the
assumption that the corresponding CoAP content types have been
registered. A profile should require the receiver to accept all
formats that are allowed to be sent.

Expand Down Expand Up @@ -2419,9 +2413,6 @@ Table of Contents
$manifest-body-cbor /= bytes .cbor untagged-coswid
$manifest-body-json /= base64-url-text

$manifest-body-cbor /= bytes .cbor SUIT_Envelope
$manifest-body-json /= base64-url-text


$$Claims-Set-Claims //= (
measurements-label => measurements-type
Expand Down Expand Up @@ -3284,15 +3275,6 @@ Table of Contents
RFC 9393, DOI 10.17487/RFC9393, June 2023,
<https://www.rfc-editor.org/rfc/rfc9393>.

[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-25, 5 February
2024, <https://datatracker.ietf.org/doc/html/draft-ietf-
suit-manifest-25>.

[ThreeGPP.IMEI]
3GPP, "3rd Generation Partnership Project; Technical
Specification Group Core Network and Terminals; Numbering,
Expand Down Expand Up @@ -4475,9 +4457,21 @@ Appendix G. Changes from Previous Drafts
history is available via the IETF Datatracker's record for this
document.

G.1. From draft-ietf-rats-eat-25
G.1. From draft-ietf-rats-eat-24

The changes from draft-24, not draft 25, are listed here as draft-24
is what was accepted after IETF last call and draft-25 was kind of a
false start.

* Address some small claim data type naming issues that came to
light when IANA completed the registrations requested by this
document. In particular, the CDDL type names are used.

* Change SUIT Manifest reference back to normative
* Remove all dependence on SUIT Manifest to break schedule interlock
with RFC Editor. Use of SUIT-Manifest is peripheral to the core
of EAT. It was mostly a content type pre-registration. The
modification consisted of the removal of one sentence, a few more
words and two lines of CDDL.

Contributors

Expand Down

0 comments on commit 2cf7978

Please sign in to comment.