search

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: Abstract needs to standalone #133

Closed mcr closed 2 years ago

mcr commented 3 years ago 
> The abstract requires more (concise!) context and outline of the general
> problem so that context-specific terms used can be easily understood, e.g.,
> 'Pledge' or its relationship to 'owner'. Imagine the abstract being the only
> thing visible in a document indexing and management system and phrase it as
> such. The "new" CoAP protocol defined seems to be a complement to an HTTPS
> protocol, which the reader has to guess is defined either by RFC8366 or BRSKI
> (this is cleared up early in the Intro). Why is it not CoAPS, if its complement
> is HTTPS? Ultimately, you shall not use references in an abstract and that is
> the root cause for this need for guessing here, I think.
EskoDijk commented 2 years ago

See PR for new text proposal. Note that still some refs are included in the abstract; seeing that it can be handy to indicate which RFCs are updated in the abstract. (But can always remove if needed)