anima-wg / constrained-voucher

This is a repo for the IETF Internet Draft about constrained vouchers in CBOR
2 stars 4 forks source link

Review HB: clarify what proximity is, and why it is important #134

Closed mcr closed 2 years ago

mcr commented 3 years ago
> (3) Overview of Protocol

> It is not immediately clear what 'proximity' means here (the term is not listed
> in the Terminology section). A quick recap of roles and interactions would not
> hurt, I think, but that can also be addressed by adding more contextual text to
> the Intro. "Most Pledges using these constrained": maybe just remove the
> "these" - it made me read it as a back-reference to time-based vouchers. The
> term "pinned" used here could benefit a from a tad bit more expositional text -
> it is a term relevant to a lot of security aspects in this memo and deserves a
> proper introduction.
EskoDijk commented 3 years ago

Can we reference RFC 8366 for the 'proximity' proof concept?

EskoDijk commented 3 years ago

For 'proximity' concept: To add reference, in Section 4.

mcr commented 2 years ago

Can we reference RFC 8366 for the 'proximity' proof concept?

RFC8366 is actually pretty sparse about proximity.

EskoDijk commented 2 years ago

RFC 8995 explains proximity somewhat better I think, but you need to assemble all the text parts together that mention "proximity" to get a complete view - so not a single section we can point to.