[Ace] Re: Zaheduzzaman Sarker's No Objection on draft-ietf-ace-revoked-token-notification-08: (with COMMENT)

[Marco Tiloca <[e-mail]>]

Hello Zaheduzzaman,

Thanks a lot for your review! Please find in line below our detailed 
replies to your comments.

A Github PR where we have addressed your comments is available at [PR].

Unless any concern is raised, we plan to soon merge this PR (and the 
other ones related to other received reviews), and to submit the result 
as version -09 of the document.

Thanks,
/Marco

[PR] https://github.com/ace-wg/ace-revoked-token-notification/pull/14


On 2024-07-11 10:14, Zaheduzzaman Sarker via Datatracker wrote:
> Zaheduzzaman Sarker has entered the following ballot position for
> draft-ietf-ace-revoked-token-notification-08: No Objection
>
> When responding, please keep the subject line intact and reply to all
> email addresses included in the To and CC lines. (Feel free to cut this
> introductory paragraph, however.)
>
>
> Please refer tohttps://eur05.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ietf.org%2Fabout%2Fgroups%2Fiesg%2Fstatements%2Fhandling-ballot-positions%2F&data=05%7C02%7Cmarco.tiloca%40ri.se%7C5a303e7efd8e4b83642008dca1816f84%7C5a9809cf0bcb413a838a09ecc40cc9e8%7C0%7C0%7C638562824502304387%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C0%7C%7C%7C&sdata=jinOWw2rk30N62H78Ec4%2FpABk%2BzAmakx7fzN3FFzlUA%3D&reserved=0 
> for more information about how to handle DISCUSS and COMMENT positions.
>
>
> The document, along with other ballot positions, can be found here:
> https://eur05.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdatatracker.ietf.org%2Fdoc%2Fdraft-ietf-ace-revoked-token-notification%2F&data=05%7C02%7Cmarco.tiloca%40ri.se%7C5a303e7efd8e4b83642008dca1816f84%7C5a9809cf0bcb413a838a09ecc40cc9e8%7C0%7C0%7C638562824502314309%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C0%7C%7C%7C&sdata=EsTg4UEjFPiFEAupz9jMbcjMx3lIScE9sN5nWCc2dtw%3D&reserved=0
>
>
>
> ----------------------------------------------------------------------
> COMMENT:
> ----------------------------------------------------------------------
>
> Thanks for working on this specification. Thanks to Joerg Ott for the TSVART
> review.
>
> My review did not surface transport protocol related issues.However - can we
> define/refer/describe "diff queries" in this document? The meaning might be
> very obvious to the experts but describing it will improve the readablity of
> this specification and avoid misconceptions.

==>MT

Just like the term "full query" (that, admittedly, is at least more 
intuitive), the term "diff query" here does not have an obvious meaning 
that experts are expected to be familiar with.

In fact, both terms are introduced and specifically defined in the 
context of this document, when they first appear at the beginning of 
Section 5 "The TRL Endpoint" (see the two related bullet points).

Yet, we have extended the bullet list in Section 1.1 "Terminology", in 
order to early and shortly mention the two terms "full query" and "diff 
query". That is:

NEW:
 > * Full query: a type of query to the TRL, where the AS returns the 
token hashes of the revoked access tokens currently in the TRL and 
pertaining to the requester. Further details are specified in Section 5 
and Section 6.
 >
 > * Diff query: a type of query to the TRL, where the AS returns a list 
of diff entries, each related to one update occurred to the TRL and 
containing a set of token hashes pertaining to the requester. Further 
details are specified in Section 5 and Section 7.

<==

>
>

-- 
Marco Tiloca
Ph.D., Senior Researcher

Phone: [phone]

RISE Research Institutes of Sweden AB
Box 1263
164 29 Kista (Sweden)

Division: Digital Systems
Department: Computer Science
Unit: Cybersecurity

https://www.ri.se