]> Conditional Query Parameters for CoAP Observe Tampere University
Kalevantie 4 Tampere 33100 Finland bilhanan.silverajan@tuni.fi
Dogtiger Labs
524 H Street Antioch, CA 94509 USA michaeljohnkoster@gmail.com
Qualcomm Technologies, Inc.
5775 Morehouse Drive San Diego 92121 USA asoloway@qti.qualcomm.com
Applications CoRE Working Group This specification defines Conditional Notification and Control Query Parameters compatible with CoAP Observe (RFC7641). About This Document Status information for this document may be found at . Discussion of this document takes place on the core Working Group mailing list (), which is archived at . Subscribe at . Source for this draft and an issue tracker can be found at .
Introduction IETF Standards for Internet of Things (IoT) communication in constrained environments define the Constrained Application Protocol (CoAP) , a RESTful application protocol, as well as a set of related information standards that may be used to represent machine data and machine metadata in REST interfaces. This specification defines Conditional Notification and Control Parameters for use with CoAP Observe .
Terminology The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in BCP 14 when, and only when, they appear in all capitals, as shown here. This specification requires readers to be familiar with all the terms and concepts that are discussed in and . This specification makes use of the following additional terminology:
Notification Band:
A resource value range that may be bounded by a minimum and maximum value or may be unbounded having either a minimum or maximum value.
"xs:boolean" and "xs:decimal" types:
Data types from XML Schema , used in this document to describe boolean and scalar values in CoAP resources. The "xs:" prefix notation is used solely for type indication and does not imply the use of XML or XML Schema in protocol encoding.
Conditional Query Parameters This specification defines conditional query parameters (or more simply, "conditional parameters" in this document) for use with CoRE Observe . Conditional parameters provide fine-grained control of notification and synchronization of resource states. A CoAP client conveys conditional parameters as metadata using the query component of a CoAP URI. A conditional parameter can be represented as a "name=value" query parameter or simply a "name" without a value. A conditional parameter can be one of two kinds: A conditional notification parameter, or a conditional control parameter. Multiple conditional parameters in a query component are separated with an ampersand "&". Support for conditional parameters is OPTIONAL and is determined on a per-resource basis. A resource that is observable MAY support the conditional parameters defined in this document. A resource that supports them MAY advertise this using the "core.conditional" interface type. This specification also defines conditional query parameters as parameters that apply to scalar and boolean values in CoAP resources. While complex data structures (e.g., SenML, CBOR arrays, or other structured formats) are commonly used in IoT systems, this document does not provide explicit guidance on how conditional parameters should interact with these formats. This specification assumes that there are finite quantization effects in the internal or external updates to the value representing the state of a resource; specifically, that a resource state may be updated at any time with any valid value. We therefore avoid any continuous-time assumptions in the description of the conditional parameters and instead use the phrase "sampled value" to refer to a member of a sequence of values that may be internally observed from the resource state over time.
Overview If a CoAP client is interested in obtaining all the state representations of a resource from a CoAP server as they change, the client is able to do so by using CoAP Observe. If a CoAP client is instead interested in receiving only state representations fulfilling certain constraints (such as a minimum/maximum value), it can do so by indicating conditional parameters as query parameters in its request to a CoAP server, when registering its interest in observing a resource. The usage of conditional parameters employs the notion of resource state projection. This is an idea that aligns with established practices employed by RESTful API designs that allow clients to retrieve specific representations or subsets of a resource’s data, enhancing efficiency and flexibility. In constrained environments, CoAP clients can employ resource state projections as a technique to reduce unnecessary data transfer in constrained environments. By using Observe with query parameters, the client requests the server to project a new state from the current resource representation and deliver only a subset of updates, based on the received requests. When a server receives a request containing conditional query parameters from a client, the server maintains a projected resource state separate from a resource state requested without conditional query parameters. The mechanism can be explained in the following subsections in terms of registration, operation and cancellation.
Advertising Support for Conditional Parameters A resource that supports the conditional parameters MAY advertise this by including the interface description "core.conditional" as a target attribute (if="core.conditional") in its link description. A client that discovers this interface type on a resource can therefore use conditional parameters with that resource. The "core.conditional" interface type MAY be used together with other target attributes, including a resource type ("rt=") and the observable attribute ("obs") . For example: ;rt="core.s";if="core.conditional";obs ]]> Advertising the "core.conditional" interface type is OPTIONAL. A resource MAY support the conditional parameters defined in this document without advertising this interface type; for example, the applicable interpretation of the query component may be established by another specification or by the context in which the resource is used. Conversely, advertising this interface type does not by itself guarantee that any particular conditional parameter is supported; a resource that advertises it handles conditional parameters it does not support as described in . This document does not define a mechanism for discovering which individual conditional parameters a resource supports; such fine-grained discovery can be defined in future specifications.
Registration In this example, three CoAP endpoints are shown: Clients A and B are interested in obtaining updates to state representations describing the current CO2 level, provided by a CoAP Server. In , Client A uses CoAP Observe to register its interest in receiving all updates to the CO2 resource state from the Server.
Client A registers and receives one notification of the current state and one state update. │ │ │ │ │ │ │ │ │ 2.05 Content │ │ │ Token: 0x42 │ │ │ Observe: 12 │ │ │ Payload: "600" │ │<──────────────┼────────────────────────+ │ │ │ │ │ │ │ │ 2.05 Content │ │ │ Token: 0x42 │ │ │ Observe: 23 │ │ │ Payload: "800" │ │<──────────────┼────────────────────────+ │ │ │ ]]>
Client B, on the other hand is interested in receiving only a subset of updates from the Server. In , Client B is depicted using CoAP Observe with a conditional parameter to register its interest in receiving specific updates to the CO2 resource state from the Server. The Server provides a representation of the current state and creates a new state projection registering Client B's interest.
Client B registers with conditional parameters, and receives one notification of the current state and a state projection is created. │ │ │ │ │ │ 2.05 Content │ │ │ Token: 0x66 │ │ │ Observe: 20 │ Resource State │ │ Payload: "800" │ Projection │ │<───────────────────────+ .................. │ │ +--->. /CO2?c.gt=1000 . │ │ │ .................. │ │ │ . │ │ │ . │ │ │ . ]]>
Operation In subsequent interactions for providing state updates, the Server will continue to provide all state updates to Client A, while Client B receives state updates fulfilling the conditions specified by the conditional parameter.
Clients A and B receiving CO2 state updates from the Server, without and with conditional parameters, respectively. . /CO2?c.gt=1000 . │ │ │ .................. │ │ │ . │ │ 2.05 Content │ . │ │ Token: 0x42 │ . │ │ Observe: 29 │ . │ │ Payload: "1000" │ . │<──────────────┼────────────────────────+ . │ │ │ . │ │ 2.05 Content │ . │ │ Token: 0x66 │ . │ │ Observe: 23 │ . │ │ Payload: "1100" │ . │ │<───────────────────────┤-------------+ │ │ │ . │ │ 2.05 Content │ . │ │ Token: 0x42 │ . │ │ Observe: 33 │ . │ │ Payload: "1100" │ . │<──────────────┼────────────────────────+ . │ │ │ . ]]>
Cancellation A client that wishes to cancel an existing registration can do so in accordance with Section 3.6 of . If a client wishes to explicitly cancel an existing registration by issuing a GET request, it MUST also additionally supply the original URI containing the conditional parameters that was conveyed to the server during the registration. This is depicted in for Client B.
Client B explicitly cancelling an existing registration. . /CO2?c.gt=1000 . │ │ │ .................. │ │ │ . │ │ │ . │ │ GET /CO2?c.gt=1000 │ . │ │ Token: 0x66 │ . │ │ Observe: 1 │ . │ +────────────────────────┤------------>. │ │ │ . │ │ │ . │ │ 2.05 Content │ . │ │ Token: 0x66 │ . │ │ Payload: "900" │ . │ │<───────────────────────┤-------------+ │ │ │ │ │ │ │ │ │ ]]>
Conditional Notification Parameters Conditional Notification Parameters define the conditions that trigger a notification. Conditional Notification Parameters SHOULD be evaluated on all potential notifications from a resource, whether resulting from an internal server-driven sampling process or from external update requests to the server. The set of Conditional Notification Parameters defined here allows a client to control how often a notification is received and how much a representation state should change in order to trigger a notification. One or more Conditional Notification Parameters MAY be included in an Observe request. Conditional Notification Parameters are defined below: Conditional Notification Parameters
Parameter Name Value Type
Greater Than c.gt xs:decimal
Less Than c.lt xs:decimal
Change Step c.st xs:decimal (>0)
Notification Band c.band (none)
Edge c.edge xs:boolean
Greater Than (c.gt) When present, Greater Than indicates the upper limit value the sampled value SHOULD cross before triggering a notification. A notification is sent whenever the sampled value crosses the specified upper limit value, relative to the last reported value, and the time for "c.pmin" has elapsed since the last notification. The sampled value is sent in the notification. If the value continues to rise, no notifications are generated as a result of "c.gt". If the value drops below the upper limit value then a notification is sent, subject again to the "c.pmin" time. The Greater Than parameter MUST be supported on resources with a scalar numeric value.
Less Than (c.lt) When present, Less Than indicates the lower limit value the resource value SHOULD cross before triggering a notification. A notification is sent whenever the sampled value crosses the specified lower limit value, relative to the last reported value, and the time for "c.pmin" has elapsed since the last notification. The sampled value is sent in the notification. If the value continues to fall no notifications are generated as a result of "c.lt". If the value rises above the lower limit value then a new notification is sent, subject to the "c.pmin" time. The Less Than parameter MUST be supported on resources with a scalar numeric value.
Change Step (c.st) When present, Change step indicates how much the value representing a resource state SHOULD change before triggering a notification, compared to the previous resource state. Upon reception of a query including the "c.st" parameter, the current resource state representing the most recently sampled value is reported, and then set as the last reported value (last_rep_v). When a subsequent sampled value or update of the resource state differs from the last reported state by an amount, positive or negative, greater than or equal to "c.st", and the time for "c.pmin" has elapsed since the last notification, a notification is sent and the last reported value is updated to the new resource state sent in the notification. The change step MUST be greater than zero, otherwise the receiver MUST return a CoAP error code 4.00 "Bad Request". The Change Step parameter MUST be supported on resources with a scalar numeric value. Note: due to sampling and other constraints, e.g., "c.pmin", the change in resource states received in two sequential notifications may differ by more than "c.st".
Notification Band (c.band) The Notification Band parameter allows a bounded or unbounded (based on a minimum or maximum) value range that may trigger multiple notifications. This enables use cases where different ranges result in differing behaviour. For example, in monitoring the temperature of machinery, whilst the temperature is in the normal operating range, only periodic updates are needed. However as the temperature moves to more abnormal ranges, more frequent state updates may be sent to clients. Without a notification band, a transition across a Less Than (c.lt), or Greater Than (c.gt) limit only generates one notification. This means that it is not possible to describe a case where multiple notifications are sent so long as the limit is exceeded. The "c.band" parameter works as a modifier to the behaviour of "c.gt" and "c.lt". Its use is determined only by its presence, as this parameter takes no value. Therefore, if "c.band" is present in a query, "c.gt", "c.lt", or both, MUST be included. When "c.band" is present with "c.lt" but without "c.gt", the lower bound for the notification band (notification band minimum) is defined. Notifications occur when the resource value is equal to or above the notification band minimum. No maximum values exist for the band. When "c.band" is present with "c.gt" but without "c.lt", the upper bound for the notification band (notification band maximum) is defined. Notifications occur when the resource value is equal to or below the notification band maximum. No minimum values exist for the band. If "c.band" is specified and the value of "c.gt" is less than that of "c.lt", in-band notification occurs. That is, notification occurs whenever the resource value is between the "c.gt" and "c.lt" values, including equal to "c.gt" or "c.lt". If "c.band" is specified and the value of "c.gt" is greater than that of "c.lt", out-of-band notification occurs. That is, notification occurs when the resource value is not between the "c.gt" and "c.lt" values, excluding equal to "c.gt" and "c.lt". The Notification Band parameter MUST be supported on resources with a scalar numeric value.
Edge (c.edge) When present, the Edge parameter indicates interest for receiving notifications of either the falling edge or the rising edge transition of a boolean resource state. When the value of the "c.edge" parameter is 0 (False), the server notifies the client each time a resource state changes from True to False. When the value of the "c.edge" parameter is 1 (True), the server notifies the client each time a resource state changes from False to True. The "c.edge" parameter MUST be supported on resources with a boolean value.
Conditional Control Parameters Conditional Control Parameters define the time intervals between consecutive notifications as well as the cadence of the evaluation of the conditions that trigger a notification. Conditional Control Parameters can be used to configure the internal server-driven sampling process for performing evaluations of the conditions of a resource. One or more Conditional Control Parameters MAY be included in an Observe request. Conditional Control Parameters are defined below: Conditional Control Parameters
Parameter Name Value Type
Minimum Period (s) c.pmin xs:decimal (>0)
Maximum Period (s) c.pmax xs:decimal (>0)
Minimum Evaluation Period (s) c.epmin xs:decimal (>0)
Maximum Evaluation Period (s) c.epmax xs:decimal (>0)
Confirmable Notification c.con xs:boolean
Minimum Period (c.pmin) When present, Minimum Period indicates the minimum time, in seconds, between two consecutive notifications (whether or not the resource state has changed). The value is a floating-point number, allowing for sub-second precision (e.g., 0.5 for half a second or 0.01 for 10 milliseconds). If a server does not support sub-second intervals, it MAY round the value up to the nearest supported resolution. In the absence of this parameter, the minimum period is up to the server. Minimum Period MUST be greater than zero, otherwise the receiver MUST return a CoAP error code 4.00 "Bad Request". A server MAY update the resource state with the last sampled value that occurred during the "c.pmin" interval, after the "c.pmin" interval expires. Note: due to finite quantization effects, the time between notifications may be greater than "c.pmin" even when the sampled value changes within the "c.pmin" interval. "c.pmin" may or may not be used to drive the internal sampling process.
Maximum Period (c.pmax) When present, Maximum Period indicates the maximum time, in seconds, between two consecutive notifications (regardless of whether or not the resource state has changed). The value is a floating-point number, allowing for sub-second precision (e.g., 0.5 for half a second or 0.01 for 10 milliseconds). If a server does not support sub-second intervals, it MAY round the value up to the nearest supported resolution. In the absence of this parameter, the maximum period is up to the server. Maximum Period MUST be greater than zero and MUST be greater than or equal to Minimum Period (if present), otherwise the receiver MUST return a CoAP error code 4.00 "Bad Request".
Minimum Evaluation Period (c.epmin) When present, Minimum Evaluation Period indicates the minimum time, in seconds, the client recommends to the server to wait between two consecutive evaluations of the conditions of a resource, since the client has no interest in the server doing more frequent evaluations. The value is a floating-point number, allowing for sub-second precision (e.g., 0.5 for half a second or 0.01 for 10 milliseconds). If a server does not support sub-second intervals, it MAY round the value up to the nearest supported resolution. When the value of Minimum Evaluation Period expires after the previous evaluation, the server MAY immediately perform a new evaluation. In the absence of this parameter, the minimum evaluation period is not defined and thus not used by the server. The server MAY use "c.pmin", if defined, as a guidance on the desired evaluation cadence. Minimum Evaluation Period MUST be greater than zero, otherwise the receiver MUST return a CoAP error code 4.00 "Bad Request".
Maximum Evaluation Period (c.epmax) When present, Maximum Evaluation Period indicates the maximum time, in seconds, the server MAY wait between two consecutive evaluations of the conditions of a resource. The value is a floating-point number, allowing for sub-second precision (e.g., 0.5 for half a second or 0.01 for 10 milliseconds). If a server does not support sub-second intervals, it MAY round the value up to the nearest supported resolution. When the value of Maximum Evaluation Period expires after the previous evaluation, the server MUST immediately perform a new evaluation. In the absence of this parameter, the maximum evaluation period is not defined and thus not used by the server. Maximum Evaluation Period MUST be greater than zero and MUST be greater than Minimum Evaluation Period (if present), otherwise the receiver MUST return a CoAP error code 4.00 "Bad Request".
Confirmable Notification (c.con) When present with a value of 1 (True), Confirmable Notification indicates that a notification MUST be confirmable, i.e., the server MUST send the notification in a confirmable CoAP message, to request an acknowledgement from the client. When present with a value of 0 (False), Confirmable Notification indicates a notification can be confirmable or non-confirmable, i.e., it can be sent in a confirmable or a non-confirmable CoAP message.
Server processing of Conditional Parameters Conditional Notification Parameters and Conditional Control Parameters may be present in the same query. However, they are not defined at multiple prioritization levels. The server sends a notification whenever any of the parameter conditions are met, upon which it updates its last notification value and time to prepare for the next notification. When Conditional Notification Parameters and Conditional Control Parameters are present in the same query, notifications may be subjected to the presence of a Conditional Control Parameter such as "c.pmin" or "c.pmax". Only one notification occurs when there are multiple conditions being met at the same time. As a general example, the pseudocode illustrated in shows one way to determine when a notification is to be sent. A resource that receives a conditional parameter it does not support MUST treat that parameter as having no effect on the observation, and MUST process the remainder of the request as usual. Such a request MUST NOT be rejected solely because a conditional parameter is not supported. For example, if a client sends "GET /temp?c.gt=25&c.newthing=5" (Observe), and the server supports "c.gt" but does not support "c.newthing", the server returns the usual "2.05 Content" with an Observe option after successfully processing the request, exactly as if only "c.gt" had been sent.
Implementation Considerations If a conditional parameter is provided with an inappropriate data type (e.g., "c.edge=10" where "c.edge" is expected to be boolean), the server MUST reject the request with 4.00 Bad Request. When "c.pmax" and "c.pmin" are equal, the expected behaviour is that notifications will be sent every (c.pmin == c.pmax) seconds. However, these notifications can only be fulfilled by the server on a best effort basis. Because "c.pmin" and "c.pmax" are designed as acceptable tolerance bounds for sending state updates, a query from an interested client containing equal "c.pmin" and "c.pmax" values must not be seen as a hard real-time scheduling contract between the client and the server. The use of the notification band minimum and maximum allows for a synchronization whenever a change in the resource value occurs. Theoretically, this could occur in-line with the server internal sample period or as defined by the "c.epmin" and "c.epmax" values for determining the resource value. Implementors SHOULD consider the resolution needed before updating the resource, e.g., updating the resource when a temperature sensor value changes by 0.001 degree versus 1 degree. When a server has multiple observations with different measurement cadences as defined by the "c.epmin" and "c.epmax" values, the server MAY evaluate all observations when performing the measurement of any one observation. An implementation might choose to apply conditions like c.gt or c.lt to the v (value) field in SenML-based resources. However, this behavior is not defined in this document. Implementers are encouraged to consider how such formats may be adapted in their specific deployments. Future extensions or additional mechanisms may provide explicit guidance on supporting conditional parameters for complex data structures as well as data structures having multiple records. This specification defines conditional parameters that can be used with CoAP Observe relationships between CoAP clients and CoAP servers. However, it is recognised that the presence of one or more proxies between a client and a server can interfere with clients receiving resource updates, if a proxy does not supply resource representations when the value remains unchanged (e.g., if "c.pmax" is set, and the server sends multiple updates when the resource state contains the same value). A server SHOULD use the Max-Age option to mitigate this, by setting Max-Age to be less than or equal to "c.pmax".
Security Considerations The security considerations in apply. Additionally, the security considerations in also apply, particularly towards mitigating amplification attacks. As noted in , an attacker could craft GET requests combining observations with conditional parameters such as c.pmax or c.epmax with values that are below a minimum implementation-specific threshold. If a server receives such a request and is unwilling to register the observer client, the server MAY silently ignore the registration request and process the GET request as usual. The resulting response MUST NOT include an Observe Option, the absence of which signals to the client that it will not be added to the list of observers by the server.
IANA Considerations This document has the following actions for IANA: Note to RFC Editor: Please replace all occurrences of "[RFC-XXXX]" with the RFC number of this specification and delete this paragraph. This document establishes the "Conditional parameters" registry within the "Constrained RESTful Environments (CoRE) Parameters" registry group. Each entry in the registry must include:
  • Name: This is the human-readable name and description of the conditional parameter,
  • Parameter: This is the short name, as used in query parameters,
  • Value Type: The value type of the parameter (if any),
  • Reference: The link to reference documentation, which must give details describing the conditional notification or control parameter and how it is to be processed.
Initial entries in this subregistry are as follows: New Conditional Parameters registry
Name Parameter Value Type Change Controller Reference
Minimum Period (s) c.pmin xs:decimal (>0) IETF RFC XXXX
Maximum Period (s) c.pmax xs:decimal (>0) IETF RFC XXXX
Minimum Evaluation Period (s) c.epmin xs:decimal (>0) IETF RFC XXXX
Maximum Evaluation Period (s) c.epmax xs:decimal (>0) IETF RFC XXXX
Confirmable Notification c.con xs:boolean IETF RFC XXXX
Greater Than c.gt xs:decimal IETF RFC XXXX
Less Than c.lt xs:decimal IETF RFC XXXX
Change Step c.st xs:decimal (>0) IETF RFC XXXX
Notification Band c.band (none) IETF RFC XXXX
Edge c.edge xs:boolean IETF RFC XXXX
The IANA policy for future additions to the subregistry is Expert Review, as described in . The evaluation of a registration request should consider the following points:
  • Clarity and correctness of registrations. Experts are expected to check the clarity of purpose and use of the new conditional parameters and associated query parameters, which have to be clearly defined in the corresponding reference documentation. Conditional parameters that do not meet these objectives of clarity and completeness MUST NOT be registered.
  • Point squatting is to be discouraged. Reviewers are encouraged to get sufficient information for registration requests to ensure that a new conditional parameter is likely to be used in deployments and is not going to duplicate one that is already registered. To reduce the potential for conflict with commonly used query parameter names, it is strongly recommended that new entry names be prepended with "c." (such as entries described in ).
This document also registers the following entry in the "Interface Description (if=) Link Target Attribute Values" registry within the "Constrained RESTful Environments (CoRE) Parameters" registry group. Interface Type for Conditional Parameters Support
Value Description Reference
core.conditional Advertisement of support for conditional parameters RFC XXXX
References Normative References Constrained RESTful Environments (CoRE) Link Format This specification defines Web Linking using a link format for use by constrained web servers to describe hosted resources, their attributes, and other relationships between links. Based on the HTTP Link Header field defined in RFC 5988, the Constrained RESTful Environments (CoRE) Link Format is carried as a payload and is assigned an Internet media type. "RESTful" refers to the Representational State Transfer (REST) architecture. A well-known URI is defined as a default entry point for requesting the links hosted by a server. [STANDARDS-TRACK] The Constrained Application Protocol (CoAP) The Constrained Application Protocol (CoAP) is a specialized web transfer protocol for use with constrained nodes and constrained (e.g., low-power, lossy) networks. The nodes often have 8-bit microcontrollers with small amounts of ROM and RAM, while constrained networks such as IPv6 over Low-Power Wireless Personal Area Networks (6LoWPANs) often have high packet error rates and a typical throughput of 10s of kbit/s. The protocol is designed for machine- to-machine (M2M) applications such as smart energy and building automation. CoAP provides a request/response interaction model between application endpoints, supports built-in discovery of services and resources, and includes key concepts of the Web such as URIs and Internet media types. CoAP is designed to easily interface with HTTP for integration with the Web while meeting specialized requirements such as multicast support, very low overhead, and simplicity for constrained environments. Observing Resources in the Constrained Application Protocol (CoAP) The Constrained Application Protocol (CoAP) is a RESTful application protocol for constrained nodes and networks. The state of a resource on a CoAP server can change over time. This document specifies a simple protocol extension for CoAP that enables CoAP clients to "observe" resources, i.e., to retrieve a representation of a resource and keep this representation updated by the server over a period of time. The protocol follows a best-effort approach for sending new representations to clients and provides eventual consistency between the state observed by each client and the actual resource state at the server. Guidelines for Writing an IANA Considerations Section in RFCs Many protocols make use of points of extensibility that use constants to identify various protocol parameters. To ensure that the values in these fields do not have conflicting uses and to promote interoperability, their allocations are often coordinated by a central record keeper. For IETF protocols, that role is filled by the Internet Assigned Numbers Authority (IANA). To make assignments in a given registry prudently, guidance describing the conditions under which new values should be assigned, as well as when and how modifications to existing values can be made, is needed. This document defines a framework for the documentation of these guidelines by specification authors, in order to assure that the provided guidance for the IANA Considerations is clear and addresses the various issues that are likely in the operation of a registry. This is the third edition of this document; it obsoletes RFC 5226. XML Schema Part 2: Datatypes Second Edition Key words for use in RFCs to Indicate Requirement Levels In many standards track documents several words are used to signify the requirements in the specification. These words are often capitalized. This document defines these words as they should be interpreted in IETF documents. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements. Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words RFC 2119 specifies common key words that may be used in protocol specifications. This document aims to reduce the ambiguity by clarifying that only UPPERCASE usage of the key words have the defined special meanings. Informative References Amplification Attacks Using the Constrained Application Protocol (CoAP) Ericsson AB Ericsson AB Energy Harvesting Solutions Protecting Internet of Things (IoT) devices against attacks is not enough. IoT deployments need to make sure that they are not used for Distributed Denial-of-Service (DDoS) attacks. DDoS attacks are typically done with compromised devices or with amplification attacks using a spoofed source address. This document gives examples of different theoretical amplification attacks using the Constrained Application Protocol (CoAP). The goal with this document is to raise awareness and to motivate generic and protocol-specific recommendations on the usage of CoAP. Some of the discussed attacks can be mitigated by not using NoSec or by using the Echo option.
Pseudocode: Processing Conditional Parameters This appendix is informative. It describes the possible logic of how a server processes conditional parameters to determine when to send a notification to a client. Note: The pseudocode is not exhaustive nor should it be treated as reference code. It depicts a subset of the conditional parameters described in this specification.
Pseudocode showing the logic for processing conditional parameters band ) #define LT_EXISTS ( r->lt ) #define GT_EXISTS ( r->gt ) #define EPMIN_TRUE ( curr_time - r->last_sampled_time >= r->epmin ) #define EPMAX_TRUE ( curr_time - r->last_sampled_time > r->epmax ) #define PMIN_TRUE ( curr_time - r->last_reported_time >= r->pmin ) #define PMAX_TRUE ( curr_time - r->last_reported_time > r->pmax ) #define LT_TRUE ( r->curr_state < r->lt ^ r->prev_state < r->lt ) #define GT_TRUE ( r->curr_state > r->gt ^ r->prev_state > r->gt ) #define ST_TRUE ( abs( r->curr_state - r->prev_state ) >= r->st ) #define INBAND_TRUE ( gt < lt && \\ (gt <= curr_state && curr_state <= lt )) #define OUTOFBAND_TRUE ( lt < gt && \\ (gt < curr_state || curr_state < lt )) #define BANDMIN_TRUE ( r->lt <= r->curr_state) #define BANDMAX_TRUE (r->curr_state <= r->gt) if PMAX_TRUE { return true; } if PMIN_TRUE { if !BAND_EXISTS { if LT_TRUE || GT_TRUE || ST_TRUE { return true; } } else { if ( (BANDMIN_TRUE && !GT_EXISTS) || \ (BANDMAX_TRUE && !LT_EXISTS) || \ INBAND_TRUE || \ OUTOFBAND_TRUE ) { return true; } } } return false; } ]]>
Examples This appendix is informative. It provides some examples of the use of Conditional Parameters. Note: For brevity, only the method or response code is shown in the header field.
Minimum Period (c.pmin) example
Client registers and receives one notification of the current state and one of a new state state when c.pmin time expires. | Header: GET 4 | GET | Token: 0x4a 5 | | Uri-Path: temperature 6 | | Uri-Query: c.pmin="10" 7 | | Observe: 0 (register) 8 | | 9 ____________ |<-----+ Header: 2.05 10 | 2.05 | Token: 0x4a 11 18.5 Cel | | Observe: 9 12 | | Payload: "18.5" 13 | | ____________ 14 | | 15 | | 23 Cel 16 | | 17 | | 18 | | 19 | | ____________ 20 ____________ |<-----+ Header: 2.05 21 | 2.05 | 26 Cel Token: 0x4a 22 26 Cel | | Observe: 20 23 | | Payload: "26" 24 | | 25 | | ]]>
Maximum Period (c.pmax) example
Client registers and receives one notification of the current state, one of a new state and one of an unchanged state when c.pmax time expires. | Header: GET 4 | GET | Token: 0x4a 5 | | Uri-Path: temperature 6 | | Uri-Query: c.pmax="20" 7 | | Observe: 0 (register) 8 | | 9 ____________ |<-----+ Header: 2.05 10 | 2.05 | Token: 0x4a 11 18.5 Cel | | Observe: 9 12 | | Payload: "18.5" 13 | | 14 | | 15 | | ____________ 16 ____________ |<-----+ Header: 2.05 17 | 2.05 | 23 Cel Token: 0x4a 18 23 Cel | | Observe: 16 19 | | Payload: "23" 20 | | 21 | | 22 | | 23 | | 24 | | 25 | | 26 | | 27 | | 28 | | 29 | | 30 | | 31 | | 32 | | 33 | | 34 | | 35 | | 36 | | ____________ 37 ____________ |<-----+ Header: 2.05 38 | 2.05 | 23 Cel Token: 0x4a 39 23 Cel | | Observe: 37 40 | | Payload: "23" 41 | | 42 | | ]]>
Greater Than (c.gt) example
Client registers and receives one notification of the current state and one of a new state when it passes through the greater than threshold of 25. | Header: GET 4 | GET | Token: 0x4a 5 | | Uri-Path: temperature 6 | | Uri-Query: c.gt=25 7 | | Observe: 0 (register) 8 | | 9 ____________ |<-----+ Header: 2.05 10 | 2.05 | Token: 0x4a 11 18.5 Cel | | Observe: 9 12 | | Payload: "18.5" 13 | | 14 | | 15 | | ____________ 16 ____________ |<-----+ Header: 2.05 17 | 2.05 | 26 Cel Token: 0x4a 18 26 Cel | | Observe: 16 29 | | Payload: "26" 20 | | 21 | | ]]>
Greater Than (c.gt) and Period Max (c.pmax) example
Client registers and receives one notification of the current state, one when c.pmax time expires, and one of a new state when it passes through the greater than threshold of 25. | Header: GET 4 | GET | Token: 0x4a 5 | | Uri-Path: temperature 6 | | Uri-Query: c.pmax=20&c.gt=25 7 | | Observe: 0 (register) 8 | | 9 ____________ |<-----+ Header: 2.05 10 | 2.05 | Token: 0x4a 11 18.5 Cel | | Observe: 9 12 | | Payload: "18.5" 13 | | 14 | | 15 | | 16 | | 17 | | 18 | | 19 | | 20 | | 21 | | 22 | | 23 | | 24 | | 25 | | 26 | | 27 | | 28 | | 29 | | ____________ 30 ____________ |<-----+ Header: 2.05 31 | 2.05 | 23 Cel Token: 0x4a 32 23 Cel | | Observe: 30 33 | | Payload: "23" 34 | | 35 | | 36 | | ____________ 37 ____________ |<-----+ Header: 2.05 38 | 2.05 | 26 Cel Token: 0x4a 39 26 Cel | | Observe: 37 40 | | Payload: "26" 41 | | 42 | | ]]>
Acknowledgements The authors wish to thank Christian Amsüss, Carsten Bormann, Esko Dijk, Klaus Hartke, Jaime Jiménez, John Mattsson, David Navarro, Mert Ocak, Ines Robles, Marco Tiloca and Hannes Tschofenig for discussions, feedback and reviews of this document.
Changelog draft-ietf-core-conditional-attributes-14
  • Minor edits for clarification and language
draft-ietf-core-conditional-attributes-13
  • Added support for discovery with "if=" interface type
  • Clarified no-op handling of unsupported parameters
  • Minor corrections and clarifications
draft-ietf-core-conditional-attributes-12
  • Added "xs:boolean" and "xs:decimal" types in Terminology
  • Added avoidance of complex data structures in Section 3
  • Extra text regarding resource state projection in Section 3.1
  • Implementation Considerations now discusses SenML as well as if= interface descriptions.
draft-ietf-core-conditional-attributes-11
  • Title of the document changed, and conditional attributes are now called conditional query parameters for accuracy.
  • Clarifying decimal support for conditional control parameters.
  • Text for error handling of type mismatches added
  • Editorial fixes
draft-ietf-core-conditional-attributes-10
  • Rectifying text and a table column in IANA Considerations, that version -09 erroneously omitted.
draft-ietf-core-conditional-attributes-09
  • IANA Considerations section updated
  • Editorial and formatting fixes
draft-ietf-core-conditional-attributes-08
  • Various editorial fixes and corrections based on review comments on mailing list from Marco Tiloca.
draft-ietf-core-conditional-attributes-07
  • Expanded how conditional attributes work with Observe in sections 3.1 to 3.4
  • Addressed early review from IoT Directorate
  • Security Considerations section expanded
draft-ietf-core-conditional-attributes-06
  • Removed code block from Section 3.5
  • Added an appendix containing pseudocode for server processing.
draft-ietf-core-conditional-attributes-05
  • Multiple (mostly editorial) clarifications and updates based on review comments on mailing list from Marco Tiloca.
draft-ietf-core-conditional-attributes-04
  • Reference code updated to include behaviour for edge attribute.
draft-ietf-core-conditional-attributes-03
  • Attribute names updated to create uniqueness for use as conditional observe attributes.
draft-ietf-core-conditional-attributes-02
  • Clarifications on usage and value of the band parameter
  • Implementation considerations for proxies added
  • Security considerations added
  • IANA considerations added
draft-ietf-core-conditional-attributes-01
  • Clarifications on True and False values for Edge and Con Attributes
  • Alan Soloway added as author
draft-ietf-core-conditional-attributes-00
  • Conditional Atttributes section from draft-ietf-core-dynlink-13 separated into own WG draft
Contributors
Australia cngroves.std@gmail.com
ARM
Vuokatti Finland zach.shelby@arm.com
Schneider-Electric
Grenoble France matthieu.vial@schneider-electric.com
Huawei
Xi’an, Shaanxi Province China jintao.zhu@huawei.com