Three servers A, B, and C, all of which are members of the CoAP group above and of the application group "gp1". Each server X (with X equal to A, B, or C): listens to its own address ADDR_X and port number PORT_X; and listens to the address ADDR_GRP and port number PORT_GRP. For each server its PORT_X may be different from PORT_GRP or may be equal to it, in general.¶
-
In Figure 15, the client sends a Non-confirmable GET request to the CoAP group, targeting the resource "temperature" in the application group "gp1". All servers reply with a 2.05 (Content) response, although the response from server B is lost. As source port number of their response, servers A and B use the destination port number of the request, i.e., PORT_GRP. Instead, server C uses its own port number PORT_C.¶
+
In Figure 15, the client sends a Non-confirmable GET request to the CoAP group, targeting the resource "temperature" in the application group "gp1".¶
In Figure 16, the client sends a Non-confirmable GET request to the CoAP group, targeting and requesting to observe the resource "temperature" in the application group "gp1". All servers reply with a 2.05 (Content) notification response. As source port number of their response, servers A and B use the destination port number of the request, i.e., PORT_GRP. Instead, server C uses its own port number PORT_C. Some time later, all servers send a 2.05 (Content) notification response, with the new representation of the "temperature" resource as payload.¶
+
In Figure 16, the client sends a Non-confirmable GET request to the CoAP group, targeting and requesting to observe the resource "temperature" in the application group "gp1".¶
In Figure 17, the client sends a Non-confirmable GET request to the CoAP group, targeting the resource "log" in the application group "gp1", and requesting a blockwise transfer. All servers reply with a 2.05 (Content) response including the first block. As source port number of its response, each server uses its own port number. After obtaining the first block, the client requests the following blocks separately from each server, by means of unicast exchanges.¶
+
In Figure 17, the client sends a Non-confirmable GET request to the CoAP group, targeting the resource "log" in the application group "gp1", and requesting a blockwise transfer.¶
-
diff --git a/carsten-wglc-2/draft-ietf-core-groupcomm-bis.txt b/carsten-wglc-2/draft-ietf-core-groupcomm-bis.txt
index 4b5739c..dbdd8d5 100644
--- a/carsten-wglc-2/draft-ietf-core-groupcomm-bis.txt
+++ b/carsten-wglc-2/draft-ietf-core-groupcomm-bis.txt
@@ -3637,11 +3637,7 @@ Appendix D. Examples of Message Exchanges
In Figure 15, the client sends a Non-confirmable GET request to the
CoAP group, targeting the resource "temperature" in the application
- group "gp1". All servers reply with a 2.05 (Content) response,
- although the response from server B is lost. As source port number
- of their response, servers A and B use the destination port number of
- the request, i.e., PORT_GRP. Instead, server C uses its own port
- number PORT_C.
+ group "gp1".
Client A B C
| | | |
@@ -3654,6 +3650,15 @@ Appendix D. Examples of Message Exchanges
| | | | Uri-Path: "gp1"
| | | | Uri-Path: "temperature"
| | | |
+
+ All servers reply with a 2.05 (Content) response, although the
+ response from server B is lost.
+
+ As source port number of their response, servers A and B use the
+ destination port number of the request, i.e., PORT_GRP.
+
+ | | | |
+ | | | |
|<---------------+ | | Source: ADDR_A:PORT_GRP
| 2.05 | | | Destination: ADDR_CLIENT:PORT_CLIENT
| | | | Header: 2.05 (T=NON, Code=2.05, MID=0x60b1)
@@ -3665,6 +3670,11 @@ Appendix D. Examples of Message Exchanges
| | | | Header: 2.05 (T=NON, Code=2.05, MID=0x01a0)
| | | | Token: 0x86
| | | | Payload: "20.9 C"
+ | | | |
+
+ As source port number of its response, server C uses its own port
+ number PORT_C.
+
| | | |
| | | |
|<---------------------+ Source: ADDR_C:PORT_C
@@ -3679,13 +3689,7 @@ Appendix D. Examples of Message Exchanges
In Figure 16, the client sends a Non-confirmable GET request to the
CoAP group, targeting and requesting to observe the resource
- "temperature" in the application group "gp1". All servers reply with
- a 2.05 (Content) notification response. As source port number of
- their response, servers A and B use the destination port number of
- the request, i.e., PORT_GRP. Instead, server C uses its own port
- number PORT_C. Some time later, all servers send a 2.05 (Content)
- notification response, with the new representation of the
- "temperature" resource as payload.
+ "temperature" in the application group "gp1".
Client A B C
| | | |
@@ -3699,6 +3703,14 @@ Appendix D. Examples of Message Exchanges
| | | | Uri-Path: "gp1"
| | | | Uri-Path: "temperature"
| | | |
+
+ All servers reply with a 2.05 (Content) notification response.
+
+ As source port number of their response, servers A and B use the
+ destination port number of the request, i.e., PORT_GRP.
+
+ | | | |
+ | | | |
|<---------------+ | | Source: ADDR_A:PORT_GRP
| 2.05 | | | Destination: ADDR_CLIENT:PORT_CLIENT
| | | | Header: 2.05 (T=NON, Code=2.05, MID=0x60b1)
@@ -3712,6 +3724,11 @@ Appendix D. Examples of Message Exchanges
| | | | Token: 0x86
| | | | Observe: 13
| | | | Payload: "20.9 C"
+
+ As source port number of its response, server C uses its own port
+ number PORT_C.
+
+ | | | |
| | | |
|<---------------------+ Source: ADDR_C:PORT_C
| 2.05 | | | Destination: ADDR_CLIENT:PORT_CLIENT
@@ -3721,8 +3738,12 @@ Appendix D. Examples of Message Exchanges
| | | | Payload: "21.0 C"
| | | |
- // The temperature changes ...
+ Some time later, the temperature changes.
+
+ All servers send a 2.05 (Content) notification response, with the
+ new representation of the "temperature" resource as payload.
+ | | | |
| | | |
|<---------------+ | | Source: ADDR_A:PORT_GRP
| 2.05 | | | Destination: ADDR_CLIENT:PORT_CLIENT
@@ -3751,11 +3772,7 @@ Appendix D. Examples of Message Exchanges
In Figure 17, the client sends a Non-confirmable GET request to the
CoAP group, targeting the resource "log" in the application group
- "gp1", and requesting a blockwise transfer. All servers reply with a
- 2.05 (Content) response including the first block. As source port
- number of its response, each server uses its own port number. After
- obtaining the first block, the client requests the following blocks
- separately from each server, by means of unicast exchanges.
+ "gp1", and requesting a blockwise transfer.
Client A B C
| | | |
@@ -3769,6 +3786,15 @@ Appendix D. Examples of Message Exchanges
| | | | Uri-Path: "log"
| | | | Block2: 0/0/64
| | | |
+
+ All servers reply with a 2.05 (Content) response including the first
+ block.
+
+ As source port number of its response, each server uses its own port
+ number.
+
+ | | | |
+ | | | |
|<---------------+ | | Source: ADDR_A:PORT_A
| 2.05 | | | Destination: ADDR_CLIENT:PORT_CLIENT
| | | | Header: 2.05 (T=NON, Code=2.05, MID=0x60b1)
@@ -3789,6 +3815,13 @@ Appendix D. Examples of Message Exchanges
| | | | Token: 0x86
| | | | Block2: 0/1/64
| | | | Payload: 0x0c00 ...
+ | | | |
+
+ After obtaining the first block, the client requests the following
+ blocks separately from each server, by means of unicast exchanges.
+
+ The client requests the following blocks from server A.
+
| | | |
| GET | | |
+--------------->| | | Source: ADDR_CLIENT:PORT_CLIENT
@@ -3823,6 +3856,10 @@ Appendix D. Examples of Message Exchanges
| | | | Token: 0xa7
| | | | Block2: 2/0/64
| | | | Payload: 0x0a02 ...
+ | | | |
+
+ The client requests the following blocks from server B.
+
| | | |
| GET | | |
+------------------>| | Source: ADDR_CLIENT:PORT_CLIENT
@@ -3857,6 +3894,10 @@ Appendix D. Examples of Message Exchanges
| | | | Token: 0xb7
| | | | Block2: 2/0/64
| | | | Payload: 0x0b02 ...
+ | | | |
+
+ The client requests the following blocks from server C.
+
| | | |
| GET | | |
+--------------------->| Source: ADDR_CLIENT:PORT_CLIENT