jiebi/ids-paragraph-commentary-corpus huggingface dataset:
Draft: draft-ietf-core-oscore-groupcomm

Commentary: So far , it was used 1x in abbreviated form , and 2x as " CWT Claims Sets ( CCS ) " . The abbreviation was problematic the way it was used while being a reference into RFC8392 , it was not defined there . I 'm not 100 % happy with dropping the term " CCS " because it having an abbreviation is a good pointer for users to see that this is an established , good and compact thing to use ( right ? ) , but I 'd rather spare readers the confusion of clicking through to 8392 and not finding the letters " CCS " . I 'd be happy with any better handling of the possible confusion , this is just the best I 'm coming up with .
Authentication credential: set of information associated with an
entity, including that entity's public key and parameters
associated with the public key.  Examples of authentication
credentials are CBOR Web Tokens (CWTs) and CWT Claims Sets (CCSs)
RFC8392, X.509 certificates RFC7925 and C509 certificates I-
D.ietf-cose-cbor-encoded-cert.  Further details about
authentication credentials are provided in sec-pub-key-format.
Authentication credential: set of information associated with an
entity, including that entity's public key and parameters
associated with the public key.  Examples of authentication
credentials are CBOR Web Tokens (CWTs) and CWT Claims Sets
RFC8392, X.509 certificates RFC7925 and C509 certificates I-
D.ietf-cose-cbor-encoded-cert.  Further details about
authentication credentials are provided in sec-pub-key-format.
If authentication credentials are CBOR Web Tokens (CWTs) or CWT
Claims Sets (CCSs) RFC8392, the public key algorithm is fully
described by a COSE key type and its "kty" and "crv" parameters.
If authentication credentials are CBOR Web Tokens (CWTs) or CWT
Claims Sets RFC8392, the public key algorithm is fully described
by a COSE key type and its "kty" and "crv" parameters.
For example, an X.509 certificate is provided as its direct binary
serialization.  If C509 certificates or CWTs are used as
authentication credentials, each is provided as the binary
serialization of a (possibly tagged) CBOR array.  If CCSs are used as
authentication credentials, each is provided as the binary
serialization of a CBOR map.
For example, an X.509 certificate is provided as its direct binary
serialization.  If C509 certificates or CWTs are used as
authentication credentials, each is provided as the binary
serialization of a (possibly tagged) CBOR array.  If CWT Claims Sets
are used as authentication credentials, each is provided as the
binary serialization of a CBOR map.
Draft: draft-ietf-core-oscore-groupcomm

Commentary: It looks good to me also . The only point I had was to maybe have a more descriptive title for the web link figure . Something like the below perhaps ? Usage of the " gosc " attribute in a web link 
 Thanks , good point ! Just to emphasize that it is an example , we may go for :
The use of Group OSCORE or OSCORE RFC8613 MAY be indicated by a
target "gosc" attribute in a web link RFC8288 to a resource, e.g.,
using a link-format document RFC6690 if the resource is accessible
over CoAP.
The "gosc" attribute is a hint indicating that the destination of
that link is only accessible using Group OSCORE or OSCORE, and
unprotected access to it is not supported.  Note that this is simply
a hint, it does not include any security context material or any
other information required to run Group OSCORE or OSCORE.
A value MUST NOT be given for the "gosc" attribute; any present value
MUST be ignored by parsers.  The "gosc" attribute MUST NOT appear
more than once in a given link-value; occurrences after the first
MUST be ignored by parsers.
When a link-value includes the "gosc" attribute, the link-value MUST
also include the "osc" attribute defined in Section 9 of RFC8613.  If
the endpoint parsing the link-value supports Group OSCORE and
understands the "gosc" attribute, then the parser MUST ignore the
"osc" attribute, which is overshadowed by the "gosc" attribute.
The example in fig-web-link-example shows a use of the "gosc"
attribute: the client does resource discovery on a server and gets
back a list of resources, one of which includes the "gosc" attribute
indicating that the resource is protected with Group OSCORE or
OSCORE.  The link-format notation (see Section 5 of RFC6690) is used.
Note to RFC Editor: Please replace "[This Document]" with the RFC
number of this document and delete this paragraph.
Note to RFC Editor: Please replace "[RFC-XXXX]" with the RFC number
of this document and delete this paragraph.
IANA is asked to add the following entry to the "OSCORE Flag Bits"
registry within the "Constrained RESTful Environments (CoRE)
Parameters" registry group.