jiebi/ids-paragraph-commentary-corpus huggingface dataset:
Draft: draft-ietf-core-senml-etch

Commentary: Addressing review comments from Carsten
Fetch Records MUST NOT contain other fields than name, base name,
time, base time, unit, and base unit.  Implementations MUST reject
and generate an error for a Fetch Pack with other fields.
Fetch Records MUST NOT contain other fields than name, base name,
time, base time, unit, and base unit.  Implementations MUST reject
and generate an error for a Fetch Pack with other fields.  RFC8132
Section 2.2 provides guidance for FETCH request error handling, e.g.,
using the 4.22 (Unprocessable Entity) CoAP error response code.
The (i)PATCH method can be used to change the fields of SenML
Records, to add new Records, and to remove existing Records.  The
names, times, and units of the Patch Records are given and matched in
same way as for the Fetch Records, except each Patch Record MUST
match at most one Target Record.  A Patch Record matching more than
one Target Record is considered invalid.  Patch Packs can also
include new values and other SenML fields for the Records.
Application of Patch Packs is idempotent; hence PATCH and iPATCH
methods for SenML Packs are equivalent.
The (i)PATCH method can be used to change the fields of SenML
Records, to add new Records, and to remove existing Records.  The
names, times, and units of the Patch Records are given and matched in
same way as for the Fetch Records, except each Patch Record MUST
match at most one Target Record.  A Patch Record matching more than
one Target Record is considered invalid (patching multiple Target
Records with one Patch Record would result in multiple copies of the
same record).  Patch Packs can also include new values and other
SenML fields for the Records.  Application of Patch Packs is
idempotent; hence PATCH and iPATCH methods for SenML Packs are
equivalent.
The Patch Records MUST be applied in the same sequence they are in
the Patch Pack.
Implementations MUST reject and generate an error for Patch Packs
with invalid Records.  If a Patch Pack is rejected, the state of the
Target Pack is not changed, i.e., either all or none of the Patch
Records are applied.
The Patch Records MUST be applied in the same sequence they are in
the Patch Pack.  If multiple Patch Packs are being processed at the
same time, the result MUST be equivalent to applying them in one
sequence.
Implementations MUST reject and generate an error for Patch Packs
with invalid Records.  If a Patch Pack is rejected, the state of the
Target Pack is not changed, i.e., either all or none of the Patch
Records are applied.  RFC8132 Section 3.4 provides guidance for error
handling with PATCH and iPATCH requests, e.g., using the 4.22
(Unprocessable Entity) and 4.09 (Conflict) CoAP error response codes.
Draft: draft-ietf-core-senml-etch

Commentary: more details for security consideration on record names noted this applies to SenSML too updated extensibility mechanism 
 The  checks fail because this PR has still year 2019 in the draft . The PR fixes that too .
This document defines two new media types, one using the JavaScript
Object Notation (JSON) RFC8259 and one using the Concise Binary
Object Representation (CBOR) RFC7049, which can be used with the CoAP
FETCH, PATCH, and iPATCH methods for resources represented with the
SenML data model.  The rest of the document uses term "(i)PATCH" when
referring to both methods as the semantics of the new media types are
the same for the CoAP PATCH and iPATCH methods.
This document defines two new media types, one using the JavaScript
Object Notation (JSON) RFC8259 and one using the Concise Binary
Object Representation (CBOR) RFC7049, which can be used with the CoAP
FETCH, PATCH, and iPATCH methods for resources represented with the
SenML data model (i.e., for both SenML and Sensor Streaming
Measurement Lists (SenSML) data).  The rest of the document uses term
"(i)PATCH" when referring to both methods as the semantics of the new
media types are the same for the CoAP PATCH and iPATCH methods.
All other Fetch Record fields than name, base name, time, base time,
unit, and base unit MUST be ignored.
Fetch Records MUST NOT contain other fields than name, base name,
time, base time, unit, and base unit.  Implementations MUST reject
and generate an error for a Fetch Pack with other fields.
The SenML mandatory to understand fields extensibility mechanism (see
section 4.4 in RFC8428) does not apply to Patch Packs, i.e., unknown
fields MUST NOT generate an error but such fields are treated like
any other field (e.g., added to Patch target records where
applicable).
This specification allows only a small subset of SenML fields in
Fetch Records but future specifications may enable new fields for
Fetch Records and possibly also new fields for selecting targets for
Patch Records.
In FETCH and (i)PATCH requests, the client can pass arbitrary names
to the target resource for manipulation.  The resource implementer
must take care to only allow access to names that are actually part
of (or accessible through) the target resource.
In FETCH and (i)PATCH requests, the client can pass arbitrary names
to the target resource for manipulation.  The resource implementer
must take care to only allow access to names that are actually part
of (or accessible through) the target resource.  In particular the
receiver needs to ensure that any input does not lead to uncontrolled
special interpretation by the system.
Draft: draft-ietf-core-senml-etch

Commentary: Addressing  's ,  's , and Warren 's IESG review comments .
Fragment identification is supported by analogously applying fragment
identifiers as specified in Section 9 of RFC8428 to the Fetch/Patch
Records.
Fragment identification for Records of Fetch and Patch Packs uses the
same mechanism as SenML JSON/CBOR fragment identification (see
Section 9 of RFC8428), i.e., "rec" scheme followed by a comma-
separated list of Record positions or range(s) of Records.  For
example, to select the 3rd and 5th Record of a Fetch or Patch Pack, a
fragment identifier "rec=3,5" can be used in the URI of the Fetch or
Patch Pack resource.
Draft: draft-ietf-core-senml-etch

Commentary: “ Are show ” 
 Should clarify that null value for deleting records should always be in " v " field regardless of the value type used in the Record . 
 Also example of deleting would be useful
If a Patch Record has a value field with value null, the matched
Record (if any) is removed from the Pack.
If a Patch Record has a value ("v") field with value null, the
matched Record (if any) is removed from the Pack.
IANA is requested to assign CoAP Content-Format IDs for the SenML
PATCH and FETCH media types in the "CoAP Content-Formats" sub-
registry, within the "CoRE Parameters" registry RFC7252.  All IDs are
assigned from the "IETF Review or IESG Approval" range.  The assigned
IDs are show in tbl-coap-content-formats.
IANA is requested to assign CoAP Content-Format IDs for the SenML
PATCH and FETCH media types in the "CoAP Content-Formats" sub-
registry, within the "CoRE Parameters" registry RFC7252.  The
assigned IDs are shown in tbl-coap-content-formats.