Clarify counter - Githubissues

core-wg / echo-request-tag

Other

0 stars 0 forks source link

Closed chrysn closed 3 years ago

chrysn commented 4 years ago

The mentions of counting Echo values was seen as confusing in the reviews, especially given that we didn't

Open steps:

[ ] Add distinction (in seccons? where the features are introduced?) of what one may want from an Echo, and what properties are required to be provided ("Want aliveness? Must be unpredictable even when having seen value as another client.") (CA)
[x] read through it again for nits and (CA)
[x] check whether this is the outcome we want of yesterday's call (GS, JPM)

gselander commented 4 years ago

I added some more commits:

Barry’s two comments leftover from Christian’s latest fix.
Some rephrasing in new example of persistent counters
Rephrased occurrences of “unless counter … “ in security considerations since it wasn’t clear if that was the only exception
Aligned terminology

I think only the first "Open step" above remains to do.

chrysn commented 3 years ago

Yes, and that's probably excessive for now.

Thanks for the updates, I'm merging this and will finish the changelog to submit as -11