From f4afc52e1e9bb787bd7e6c7224a6f3c85f7a8582 Mon Sep 17 00:00:00 2001 From: chrysn Date: Wed, 11 Jan 2017 13:21:52 +0100 Subject: [PATCH 1/6] Spec: Add links to blockwise and observe --- spec.html | 10 ++++++++++ 1 file changed, 10 insertions(+) diff --git a/spec.html b/spec.html index 12b3e43..abd6337 100644 --- a/spec.html +++ b/spec.html @@ -45,6 +45,16 @@

Other specifications

Several other specifications work together to support using CoAP.

+

Blockwise transfer

+

+ RFC 7959 + describes how payloads larger than a single package are transferred. +

+

Observation

+

+ RFC 7641 + allows clients to receive continuous updates when a resource is changed. +

Link-format

RFC 6690 From 68bb1e5206648de74680ffe861206a6f17a2e678 Mon Sep 17 00:00:00 2001 From: chrysn Date: Fri, 23 Jun 2017 19:03:45 +0200 Subject: [PATCH 2/6] Spec: Add etch and HTTP mapping, restructure into paragraphs With the addition of FETCH/PATCH and HTTP mapping, the list of "other specifications" would get unwieldily long if every document got its own h3. Grouping the specifications and giving each one just a paragraph should make the list usable for some more documents. --- spec.html | 34 +++++++++++++++++++++++----------- 1 file changed, 23 insertions(+), 11 deletions(-) diff --git a/spec.html b/spec.html index abd6337..463dcf3 100644 --- a/spec.html +++ b/spec.html @@ -45,27 +45,39 @@

Other specifications

Several other specifications work together to support using CoAP.

-

Blockwise transfer

+

More mechanisms

- RFC 7959 - describes how payloads larger than a single package are transferred. + With the block-wise transfer modes of + RFC 7959, + resource representations larger than a single package can be exchanged.

-

Observation

+ The observation mechanism introduced in RFC 7641 - allows clients to receive continuous updates when a resource is changed. + allows clients to receive continuous updates whenever a resource is changed.

-

Link-format

+

Explored details

+

+ Employing the basic multicast functionality defined in RFC 7252, + RFC 7390 + provides additional information and protocol flows for how to use CoAP for group communication. +

+

+ RFC 8075 + establishes rules how CoAP services can be proxied to HTTP, + and how methods and media types are mapped. +

+

New formats

RFC 6690 - defines the CoAP link-format, a simple format for exposing the + defines the CoAP link-format, a simple format for exposing the resources offered by a CoAP server as the basis for a resource directory.

-

Group comm

- Employing the basic multicast functionality defined in RFC 7252, - RFC 7390 - provides additional information and protocol flows for how to use CoAP for group communication. + With + RFC 8132, + the methods PATCH and FETCH are introduced, and + the use of JSON based patch formats is enabled.

From b920c1542d0438f0db63690cde4773d66c6740db Mon Sep 17 00:00:00 2001 From: chrysn Date: Wed, 16 Oct 2024 17:14:14 +0200 Subject: [PATCH 3/6] other specs: FETCH/PATCH is more a protocol extension --- spec.html | 11 +++++------ 1 file changed, 5 insertions(+), 6 deletions(-) diff --git a/spec.html b/spec.html index 463dcf3..fc8aa50 100644 --- a/spec.html +++ b/spec.html @@ -56,6 +56,11 @@

More mechanisms

RFC 7641 allows clients to receive continuous updates whenever a resource is changed.

+

+ With + RFC 8132, + the methods PATCH and FETCH are introduced. +

Explored details

Employing the basic multicast functionality defined in RFC 7252, @@ -73,12 +78,6 @@

New formats

defines the CoAP link-format, a simple format for exposing the resources offered by a CoAP server as the basis for a resource directory.

-

- With - RFC 8132, - the methods PATCH and FETCH are introduced, and - the use of JSON based patch formats is enabled. -

Dependent specifications

From ecde507ca6fd84e8b351ecbdb2f8d73c2d296463 Mon Sep 17 00:00:00 2001 From: chrysn Date: Wed, 16 Oct 2024 17:19:55 +0200 Subject: [PATCH 4/6] spec: Extend formats --- spec.html | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/spec.html b/spec.html index fc8aa50..2176d95 100644 --- a/spec.html +++ b/spec.html @@ -78,6 +78,10 @@

New formats

defines the CoAP link-format, a simple format for exposing the resources offered by a CoAP server as the basis for a resource directory.

+

+ SenML (RFC8428) is convenient for transporting sensor and actuator data. + Problem details can be expressed concisely using the format defined in RFC9290. +

Dependent specifications

From c7ebd152f8722341739354b9fa1c30bce1e11b65 Mon Sep 17 00:00:00 2001 From: chrysn Date: Wed, 16 Oct 2024 17:20:04 +0200 Subject: [PATCH 5/6] spec: Add EDHOC/OSCORE --- spec.html | 3 +++ 1 file changed, 3 insertions(+) diff --git a/spec.html b/spec.html index 2176d95..e304861 100644 --- a/spec.html +++ b/spec.html @@ -61,6 +61,9 @@

More mechanisms

RFC 8132, the methods PATCH and FETCH are introduced.

+

Security extensions

+

OSCORE (RFC8613) provides symmetric end-to-end security; + EDHOC (RFC9528) enables asymmetric key exchange for OSCORE and other protocols.

Explored details

Employing the basic multicast functionality defined in RFC 7252, From af5cac2c25d8a8c12d05bc70dc7cce807c937bc2 Mon Sep 17 00:00:00 2001 From: chrysn Date: Wed, 16 Oct 2024 17:31:05 +0200 Subject: [PATCH 6/6] specs: Update for better looks This moves content formats with dependent specifications, and shortens or rearranges the strong highlights for a more pleasant and accessible look. --- spec.html | 28 +++++++++++++++------------- 1 file changed, 15 insertions(+), 13 deletions(-) diff --git a/spec.html b/spec.html index e304861..d2907d5 100644 --- a/spec.html +++ b/spec.html @@ -41,7 +41,7 @@

IANA registry

-

Other specifications

+

Extension specifications

Several other specifications work together to support using CoAP.

@@ -62,8 +62,8 @@

More mechanisms

the methods PATCH and FETCH are introduced.

Security extensions

-

OSCORE (RFC8613) provides symmetric end-to-end security; - EDHOC (RFC9528) enables asymmetric key exchange for OSCORE and other protocols.

+

OSCORE (RFC8613) provides symmetric end-to-end security; + EDHOC (RFC9528) enables asymmetric key exchange for OSCORE and other protocols.

Explored details

Employing the basic multicast functionality defined in RFC 7252, @@ -75,16 +75,6 @@

Explored details

establishes rules how CoAP services can be proxied to HTTP, and how methods and media types are mapped.

-

New formats

-

- RFC 6690 - defines the CoAP link-format, a simple format for exposing the - resources offered by a CoAP server as the basis for a resource directory. -

-

- SenML (RFC8428) is convenient for transporting sensor and actuator data. - Problem details can be expressed concisely using the format defined in RFC9290. -

Dependent specifications

@@ -102,5 +92,17 @@

LWM2M

open-source implementations of the LWM2M standard are available for the client and server sides. Some basic testing support is also available on-line at coap.me.

+

Content formats

+

+ RFC 6690 + defines the CoAP link-format, a simple format for exposing the + resources offered by a CoAP server as the basis for a resource directory. +

+

+ SenML (RFC8428) is convenient for transporting sensor and actuator data. +

+

+ A format for describing concise problem details is defined in RFC9290. +