Opened 12 years ago

Closed 12 years ago

#20 closed protocol enhancement (fixed)

Proxying clarification

Reported by: zach@… Owned by:
Priority: major Milestone: coap-02
Component: coap Version:
Severity: - Keywords:


The following changes with regard to Section 5.3. Proxying are proposed:

  • A new list item is required for the steps upon receiving a Uri-Authority header. In the case that this option is received by an end-point which does not support proxying, then an error is returned as specified in Section 2.5.1 since the option is critical.
  • The behaviour when a proxy receives a request with a Uri-Authority of the proxy itself should be clarified. It is proposed that the proxy returns a 400 Bad Request in this case.
  • The Uri-Scheme Option is not actually required in the current CoAP design, and this proposes that the option be removed for simplicity. A CoAP-CoAP proxy simply assumes that the scheme is coap:// and a CoAP-HTTP proxy assumes that the scheme is http://. This obviously means that a proxy on the same port can't support both CoAP-CoAP and CoAP-HTTP functionality (something people can surely live with) as it wouldn't know which to perform.

Change History (1)

comment:1 Changed 12 years ago by zach@…

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

The third change was made in coap-02 and Uri-Scheme was removed. The first two changes are no longer relevant due to Ticket #23.

Note: See TracTickets for help on using tickets.