Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Topic hierarchy editorial fixes #20

Merged
merged 3 commits into from Jul 2, 2018
Merged

Topic hierarchy editorial fixes #20

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
1ad56df
Editorial: clarified topic hierarchy example
akeranen Mar 19, 2018
50c13c1
updated topic hierarchy text
akeranen Mar 19, 2018
b466858
Merge branch 'master' into topic-hierarchy-fixes
mjkoster Jul 2, 2018
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
29 changes: 19 additions & 10 deletions draft-ietf-core-pubsub.md
View file
Open in desktop
Expand Up @@ -370,10 +370,10 @@ Client Broker

## CREATE {#sec-create}

A CoAP pubsub Broker SHOULD allow Clients to create new topics on the
Broker using CREATE. Some exceptions are for fixed Brokerless devices
and pre-configured Brokers in dedicated installations. A client wishing
to create a topic MUST use CoAP POST to the pubsub API with a payload
A CoAP pub/sub broker SHOULD allow Clients to create new topics on the
broker using CREATE. Some exceptions are for fixed brokerless devices
and pre-configured brokers in dedicated installations. A client wishing
to create a topic MUST use a CoAP POST to the pub/sub API with a payload
indicating the desired topic. The topic specification sent in the
payload MUST use a supported serialization of the CoRE link format
{{RFC6690}}. The target of the link MUST be a URI formatted
Expand Down Expand Up @@ -412,7 +412,16 @@ topic indefinitely if the Max-Age option is elided or is set to zero
upon topic creation. The lifetime of a topic MUST be refreshed upon
create operations with a target of an existing topic.

The CREATE operation is specified as follows:

Topic hierarchies can be created by creating parent topics. A parent
topic is created with a POST using ct (Content Format) link attribute
value which describes a supported serialization of the CoRE link
format {{RFC6690}}, such as application/link-format (ct=40) or its
JSON or CBOR serializations. If a topic is created which describes a
link serialization, that topic may then have sub-topics created under
it as shown in {{create-sub-fig}}.

The CREATE interface is specified as follows:

Interaction:
: Client -> Broker
Expand Down Expand Up @@ -484,20 +493,20 @@ Client Broker
~~~~
Client Broker
| |
| ------- POST /ps/ "<mainTopic>;ct=40" ------->|
| ----- POST /ps/ "<parent-topic>;ct=40" ------>|
| |
| <---------------- 2.01 Created ---------------|
| Location: /ps/mainTopic/ |
| Location: /ps/parent-topic/ |
| |
| --- POST /ps/mainTopic/ "<subTopic>;ct=50" -->|
|-- POST /ps/parent-topic/ "<subtopic>;ct=50" ->|
| |
| <---------------- 2.01 Created ---------------|
| Location: /ps/mainTopic/subTopic |
| Location: /ps/parent-topic/subtopic |
| |
| |

~~~~
{: #create-sub-fig title='Example of CREATE sub-topic' artwork-align="center"}
{: #create-sub-fig title='Example of CREATE of topic hierarchy' artwork-align="center"}



Expand Down