This page is related to an active IETF Working Group.
The Constrained RESTful Environments (CoRE) WG was created out of the 6LowApp activity (see concluded 6lowapp WG for historical information).
This wiki is used for collecting information that is not, or not yet, material for CoRE Internet-Drafts, RFCs or IANA registries.
Most of the current work on the WG drafts happens on the CoRE-WG GitHub organization: https://github.com/core-wg
With respect to the mode of operation of the repository, the CoRE WG follows the lead of the HTTPBIS WG. Specifically that means that GitHub issues are welcome to record editorial issues as well as technical ones; as are "pull requests" (forks of the repository with fixes for an issue). However, technical discussion should not happen in the forums implicitly created by the issues, but on the CoRE WG mailing list.
The CoRE WG completed specifications can be found at the CoRE Datatracker documents page. Scroll down to "RFCs".
On top of this page is an up-to-date listing of the current Internet-Drafts and their status.
IETF administrative information about CoRE is available from the CoRE Datatracker.
There's a site for testing CoAP: https://coap.me/
A website for all things CoAP: https://coap.space
Some ancillary information about CoRE, including some examples and test vectors, additional explanatory resources etc. is at: https://github.com/core-wg/wiki/wiki
The IANA registries for CoRE WG documents can be found here.
For a number of these registries, in the subsections below, this Wiki page keeps supplemental information based on consensus from the WG, or discussions on the core-parameters mailing list. This is particular information that is not kept in the IANA registries themselves or in related RFCs.
The CoAP Content-Formats registry has the following additional remarks:
In the range 256-9999 IETF Review or IESG Approval, the sub-range 1000-9999 is currently earmarked (informally reserved) for an experiment to automatically assign Content-Format IDs to existing media types as registered by IANA in the Media Types registry.
Content-Format 434 is earmarked for application/sdf+json (see thread)
The Resource Type (rt=) Link Target Attribute Values registry enables implementers of (IoT) devices to learn about, and potentially re-use, functionality that was defined/registered by others. This can ease and accelerate the development and testing of such devices.
However, by its definition the registry only includes plain (string) values, while URIs (including URNs) are never included. The following page keeps track of known URIs used to encode Resource Types.
The Interface Description (if=) Link Target Attribute Values registry, similar to the above, enables implementers to re-use interface types.
The below page keeps track of known URIs used to encode Interface Descriptions.
We are a very active working group with a lot of personal draft submissions being maintained. In order to maintain common objectives for progressing work, the following page maintains an Agile backlog of work items that are the next highest priority for the working group. This page is to be reviewed and updated periodically (e.g. at IETF meetings). This is not however a formal tool of the IETF, and acceptance of a draft as a WG item follows normal IETF procedure.
The CoRE protocols have been tested in more formal "plugtest" events organized by ETSI. More info about these can be found at the ETSI plugtests page
The first of these plugtests took place collocated with IETF83 in Paris, March 2012. A second plugtest took place near the ETSI premises on Nov 28–30, 2012. The third CoAP plugtest tested the final, approved version of CoAP and included DTLS and OMA LWM2M tests, taking place in Las Vegas on November 19–22, 2013. A quick summary of the results is here. The fourth CoAP plugtest, taking place in London March 2014, tested the base specification in conjunction with the final updates to Observe. A quick summary of the results is here.