diff --git a/ps-rev/draft-ietf-core-coap-pubsub.html b/ps-rev/draft-ietf-core-coap-pubsub.html index 252f6c5..cb07e93 100644 --- a/ps-rev/draft-ietf-core-coap-pubsub.html +++ b/ps-rev/draft-ietf-core-coap-pubsub.html @@ -2042,63 +2042,67 @@

- - - - - - - - - - - + + + + + + + + + + + - - - - - - - - - - - - - - - - - - - - - + + + + + + + + + + + + + + + + + + + + + + + + + + + HALF - FULLY + FULLY CREATED - Delete - CREATED - Topic - Data - Publish - Create - Publish - Subscribe - Read/ - Read/ - Update - Delete - Delete - Update - - - Topic - Topic - - - DELETED + Delete + CREATED + Topic + Data + Publish + Create + Publish + Subscribe + Read/ + Read/ + Update + Delete + Delete + Update + Topic + Topic + DELETED
@@ -2129,8 +2133,199 @@

2.7. Topic Data Interactions

-

Interactions with the topic_data resource are covered in this section. In principle the behavior is the same as that of any other CoAP resource. -One variant is that the topic_data might be hosted in a different CoAP server than that of the topic resource.

+

Interactions with the topic_data resource are covered in this section. The interactions with topic_data are same as that of any other CoAP resource.

+

One variant shown in Figure 5 is where the resource is hosted. While the broker can create a topic_data resource when the topic is created, the client can select to host the data in a different CoAP server than that of the topic resource.

+
+
+
+
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + CoAP + server + 1 + [central-ps.example.com] + ┌ + ─ + ─ + ─ + ─ + ─ + ─ + ─ + ─ + ─ + ─ + ─ + ─ + ─ + ─ + ─ + ─ + ─ + ─ + ─ + ─ + ─ + │ + │ + CoAP + server + 2 + Topic + │ + [2001:db8::2:1] + │ + Collection + Resource + │ + ┌ + ─ + ─ + ─ + ─ + ─ + ─ + ─ + ─ + ─ + │ + │ + │ + │ + │ + ...... + ...... + ......... + │ + : + : + : + : + │ + │: + : + Topic + │ + Topic + : + : + : + ─────────── + : + Data + │ + Resource + : + _ + _ + : + : + : + │ + │: + : + Resource + │ + .... + .... + ......... + :.......: + │ + .... + .... + │ + │ + │ + Topic + : + _ + _ + : + ─ + ─ + ─ + ─ + ─ + ─ + ─ + ─ + ─ + ┘ + Data + : + : + │ + │ + Resource + : + : + :.......: + │ + │ + │ + └ + ─ + ─ + ─ + ─ + ─ + ─ + ─ + ─ + ─ + ─ + ─ + ─ + ─ + ─ + ─ + ─ + ─ + ─ + ─ + ─ + ─ + + +
+
+
Figure 5: +topic data hosted externally +
+

@@ -2310,7 +2505,7 @@

This document defines parameters used in the messages exchanged between a client and the broker during the topic creation and configuration process (see Section 2.2.2). The table below summarizes them and specifies the CBOR key to use instead of the full descriptive name.

Note that the media type application/core-pubsub+cbor MUST be used when these parameters are transported in the respective message fields.

-
+
 +-----------------+-----------+--------------+------------+
@@ -2326,7 +2521,7 @@ 

 +-----------------+-----------+--------------+------------+
-
Figure 5: +
Figure 6: CoAP Pubsub Parameters
diff --git a/ps-rev/draft-ietf-core-coap-pubsub.txt b/ps-rev/draft-ietf-core-coap-pubsub.txt index e38de16..281ec15 100644 --- a/ps-rev/draft-ietf-core-coap-pubsub.txt +++ b/ps-rev/draft-ietf-core-coap-pubsub.txt @@ -763,17 +763,18 @@ Table of Contents subscriber cannot yet observe the topic data resource nor read the latest data. - HALF FULLY - CREATED Delete CREATED - ___ Topic Data ___ Publish - ------------> | | <------------------ | | ------------. - Create |___| ------------------> |___| <-----------' - \ Publish / Subscribe - | ^ \ ___ / | ^ - Read/ | | '--> | | <--' | | Read/ - Update | | Delete |___| Delete | | Update - '-' Topic Topic '-' - DELETED + HALF FULLY + CREATED Delete CREATED + ____ Topic Data ____ Publish + ------------> | | <------------------- | | ------------. + Create | | | | | + |____| -------------------> |____| <-----------' + \ Publish / Subscribe + | ^ \ ___ / | ^ + Read/ | | '--> | | <--' | | Read/ + Update | | Delete |___| Delete | | Update + '-' Topic Topic '-' + DELETED Figure 4: Lifecycle of a Topic @@ -814,9 +815,39 @@ Table of Contents 2.7. Topic Data Interactions Interactions with the topic_data resource are covered in this - section. In principle the behavior is the same as that of any other - CoAP resource. One variant is that the topic_data might be hosted in - a different CoAP server than that of the topic resource. + section. The interactions with topic_data are same as that of any + other CoAP resource. + + One variant shown in Figure 5 is where the resource is hosted. While + the broker can create a topic_data resource when the topic is + created, the client can select to host the data in a different CoAP + server than that of the topic resource. + + CoAP server 1 + [central-ps.example.com] + ┌ ─ ─ ─ ─ ─ ─ ─ ─ ─ ─ ─ ─ ─ ─ ─ ─ ─ ─ ─ ─ ─ + │ + │ ___ CoAP server 2 + Topic / \ │ [2001:db8::2:1] + │ Collection \___/ + Resource \ │ ┌ ─ ─ ─ ─ ─ ─ ─ ─ ─ + │ \___________ │ + \ \ │ │ + │ \ ...... \ ...... ......... │ + : \___ : : \___ : │ │: ___ : Topic + │ Topic : / + \ : : / + \───────────/ \ : Data │ + Resource : \_|_/ : : \___/ : │ │: \___/ : Resource + │ ....|.... ......... :.......: │ + ....|.... │ │ + │ Topic : _|_ : ─ ─ ─ ─ ─ ─ ─ ─ ─ ┘ + Data : / \ : │ + │ Resource : \___/ : + :.......: │ + │ + │ + └ ─ ─ ─ ─ ─ ─ ─ ─ ─ ─ ─ ─ ─ ─ ─ ─ ─ ─ ─ ─ ─ + + Figure 5: topic data hosted externally 2.7.1. Publish @@ -1018,7 +1049,7 @@ Table of Contents | max_subscribers | TBD7 | uint (opt) | [RFC-XXXX] | +-----------------+-----------+--------------+------------+ - Figure 5: CoAP Pubsub Parameters + Figure 6: CoAP Pubsub Parameters 4. Security Considerations