# Notes on -revoked-token-notification-07

[toc]

## Review

Archived at: https://mailarchive.ietf.org/arch/msg/ace/gFhIBwJHdc_nN3v9ZuTakkAuohA/

## General (DONE)

In the captions of the figures:

* s/Full Query/full query

* s/Diff Query/diff query

## Section 1.1 (DONE)

Add the following two new definitions in the terminology.

* Token hash pertaining to a requester: a token hash corresponding to an access token pertaining to that requester, i.e., an administrator or a registered device.

* TRL update pertaining to a requester: an update to the TRL through which token hashes pertaining to that requester have been added to the TRL or removed from the TRL.

## Section 3.1.2 (DONE)

OLD
> The access token can be uploaded to the RS by means of a POST request to the /authz-info endpoint (see Section 5.10.1 of [RFC9200]), using a media-type different from "application/ace+cbor" (e.g., like in [RFC9202]). In such a case, TOKEN_INFO is the payload of the POST request.

NEW
> The access token can be uploaded to the RS by means of a POST request to the /authz-info endpoint (see Section 5.10.1 of [RFC9200]), using a CoAP Content-Format or HTTP media-type that reflects the format of the access token, if available (e.g., "application/cwt" for CWTs), or "application/octet-stream" otherwise. When doing so (e.g., like in [RFC9202]), TOKEN_INFO is the payload of the POST request.

In the following three bullet points:

* s/In such a case,/When doing so,

## Section 5 (DONE)

OLD
> Diff query: the AS returns a list of diff entries. Each diff entry is related to one of the most recent updates to the TRL, with such an update performed in the subset of the TRL pertaining to the requester.
>
> The entry associated with one of such updates contains the list of token hashes that were added to or removed from the TRL at that update, and for which the corresponding revoked access tokens pertain to the requester.

NEW
> Diff query: the AS returns a list of diff entries. Each diff entry is related to one update occurred to the TRL, and it contains a set of token hashes pertaining to the requester. In particular, all such token hashes were added to the TRL or removed from the TRL at the update related to the diff entry in question.

## Section 5 (DONE)

OLD
> If it supports diff queries, the AS MAY additionally support its "Cursor" extension, which has two benefits. First, the AS can avoid excessively long messages when several diff entries have to be transferred, by delivering several diff query responses, each containing one adjacent subset at a time. Second, a requester can retrieve diff entries associated with TRL updates that, even if not the most recent ones, occurred after a TRL update indicated as reference point.

NEW
> If it supports diff queries, the AS MAY additionally support its "Cursor" extension, which has two benefits. First, the AS can avoid excessively long messages when several diff entries have to be transferred, by delivering several diff query responses, each containing one adjacent subset of diff entries at a time. Second, a requester can retrieve diff entries associated with TRL updates that, even if not the most recent ones, occurred after a TRL update associated with a diff entry indicated as reference point.

## Section 5.2 (DONE)

OLD
> If the AS supports diff queries, it is able to transfer a list of diff entries, as a series of TRL updates. That is, when replying to a diff query performed by a requester, the AS specifies the most recent updates to the subset of the TRL pertaining to that requester.

NEW
> If the AS supports diff queries, it is able to transfer a list of diff entries, each of which is related to one update occurred to the TRL (see Section 5). That is, when replying to a diff query performed by a requester, the AS specifies the diff entries related to the most recent TRL updates pertaining to the requester.

## Section 5.2 (DONE)

OLD
> The following defines how the AS builds and maintains consistent histories of TRL updates for each registered device and administrator, hereafter referred to as requesters.

NEW
> The following defines how the AS builds and maintains an ordered list of diff entries, for each registered device and administrator, hereafter referred to as requesters. In particular, a requester's diff entry associated with a TRL update contains a set of token hashes pertaining to that requester, which were added to the TRL or removed from the TRL at that update.

## Section 5.2 (DONE)

OLD
> The AS defines the single, constant positive integer MAX\_N >= 1. For each requester, the AS maintains an update collection of maximum MAX\_N series items. For each requester, the AS MUST keep track of the MAX\_N most recent updates to the subset of the TRL that pertains to the requester.

NEW
> The AS defines the single, constant positive integer MAX\_N >= 1. For each requester, the AS maintains an update collection of maximum MAX\_N series items, each of which is a diff entry. For each requester, the AS MUST keep track of the MAX\_N most recent TRL updates pertaining to the requester.

## Section 5.2 (DONE)

OLD
> This occurs when the number of TRL updates pertaining to the requester and currently stored at the AS is equal to MAX_N.

NEW
> (empty)

## Section 5.2.1 (DONE)

OLD
> When maintaining the history of updates to the TRL, the following applies separately for each requester's update collection.

NEW
> The following applies separately for each requester's update collection.

## Section 7 (DONE)

OLD
> The AS determines U = min(NUM, SIZE), where SIZE <= MAX_N. In particular, SIZE is the number of TRL updates pertaining to the requester and currently stored at the AS.

NEW
> The AS determines U = min(NUM, SIZE), where SIZE <= MAX_N. In particular, SIZE is the number of diff entries currently stored in the requester's update collection.

## Section 7 (DONE)

OLD
> That is, the first 'diff_entry' element of 'diff_set_value' relates to the most recent update to the subset of the TRL pertaining to the requester. The second 'diff_entry' element relates to the second from last most recent update to that subset, and so on.

NEW
> That is, the first 'diff_entry' element of 'diff_set_value' relates to the most recent TRL update pertaining to the requester. The second 'diff_entry' element relates to the second from last most recent TRL update pertaining to the requester, and so on.

## Section 8.1 (DONE)

OLD
> as corresponding to the most recent update pertaining to the requester that occurred to the TRL.

NEW
> as corresponding to the most recent TRL update pertaining to the requester.

## Section 8.2.2 (DONE)

OLD
> corresponding to the most recent update pertaining to the requester and returned in this diff query response.

NEW
> corresponding to the most recent TRL update pertaining to the requester and returned in this diff query response.

## Section 8.2.3 (DONE)

OLD
> This occurs when the item Y (and possibly further ones after it) has been previously removed from the history of updates for that requester (see step 5 at Section 5.2).

NEW
> This occurs when the item Y (and possibly further ones after it) has been previously removed from the update collection for that requester (see step 5 at Section 5.2).

## Section 8.2.3 (DONE)

OLD
> That is, the 'cursor' parameter takes the 'index' value of the series item in the update collection corresponding to the most recent update pertaining to the requester and returned in this diff query response.

NEW
> That is, the 'cursor' parameter takes the 'index' value of the series item in the update collection corresponding to the most recent TRL update pertaining to the requester and returned in this diff query response.

## Appendix A (DONE)

OLD
> That is, a diff query enables the transfer of a series of TRL updates, with the AS specifying U <= MAX_N diff entries as the U most recent updates to the subset of the TRL pertaining to a requester, i.e., a registered device or an administrator.

NEW
> That is, a diff query enables the transfer of a series of diff entries, with the AS specifying U <= MAX_N diff entries as related to the U most recent TRL updates pertaining to a requester, i.e., a registered device or an administrator.

## Appendix B (DONE)

In the "Description" of MAX_N

OLD
Max number of TRL updates stored per requester

NEW
Max number of series items in the update collection of each requester

## Appendix C (DONE)

OLD
a 'max_n' parameter, specifying the value of MAX_N, i.e., the maximum number of TRL updates pertaining to each registered device that the AS retains for that device (see Section 7);

NEW
a 'max_n' parameter, specifying the value of MAX_N, i.e., the maximum number of series items that the AS retains in the update collection associated with a registered device (see Section 7);

## Appendix C.5 (DONE)

s/MAX_DIFF_BATCH=5/MAX_DIFF_BATCH = 5