Opened 10 years ago

Closed 10 years ago

#263 closed protocol defect (fixed)

Proxied responses to multicast request can't be distinguished by client

Reported by: esko.dijk@… Owned by: draft-ietf-core-coap@…
Priority: minor Milestone: post-WGLC-1
Component: coap Version: coap-12
Severity: - Keywords:
Cc:

Description

(This ticket is either protocol defect or editorial, depending on viewpoint.)

Section 8.2.2 of core-coap-12 describes a multicast request via a CoAP proxy. The proxy sends all responses back to the client. However, the client can't identify from which CoAP server any particular response is coming. (With regular non-proxied multicast, the IP source address provides this information. For a proxied request, all responses coming back carry the IP address of the CoAP proxy as the source IP address.)

This ticket is meant to record our decision on this matter:
1- do we define a method such that the client can identify responses by IP address of the responding CoAP server?
2- do we leave it as now and recommend/mention that the server includes some form of self-identification in a response to a multicast request?
3- do nothing
(4- any other?)

Change History (2)

comment:1 Changed 10 years ago by hartke@…

The client might not even be aware that it made a multicast request, e.g., if it follows some link and sends

Proxy-Uri: coap://xyzzy.example.net/s/temp

and xyzzy.example.net resolves to an IP multicast address.

comment:2 Changed 10 years ago by cabo@…

  • Resolution set to fixed
  • Status changed from new to closed

Fixed in [1108]:

Fix #257.
Close #263 by referring to coap-misc.

Note: See TracTickets for help on using tickets.