Review of draft-ietf-core-conditional-attributes-10

[bsilverajan]

From https://mailarchive.ietf.org/arch/msg/core/JFK9bJOBiZfP_TNFgcWUMOWOf0c/

Editorial

- that work with
+ compatible with
 
- machine-to-machine communication
+ machine-to-machine (M2M)
(or maybe)
+ Internet of Things (IoT) communication
 
- describe the Constrained Application Protocol (CoAP)
+ define the Constrained Application Protocol (CoAP)
 
- 3 CoAP endpoints
+ three CoAP endpoints
 
- query paramets
+ query parameters
 
- parameter can only be supported on resources
+ parameter MUST be supported on resources
 
- error code 4.00 "Bad Request" (or equivalent).
+ error code 4.00 "Bad Request".
 
- the interest of Client B is registered
+ Client B's interest is registered
 
- and creates a new state projection in which the interest of Client B is registered
+ and creates a new state projection registering Client B's interest
 
- an attacker might choose to craft GET requests, in which observations are requested together with conditional attributes
+ an attacker could craft GET requests combining observations with conditional attributes
 
- completeness must not be registered.
+ completeness MUST NOT be registered.
(I am not sure if normative language applies to IANA policies though)
 
- Point squatting should be discouraged
+ Point squatting is to be discouraged