Complete Section 5.3 Proxying

[zach@…]

Some open issues on Proxying:

o Are interception proxies are still required to deal with a)

sleeping nodes and b) protecting Internet HTTP traffic from
overwhelming the CoAP network?

o But interception proxies breaks end-to-end IP encapsulation and

requires support at the routing level

o Often the interception proxy is the same as the HTTP-to-CoAP

gateway, so we need to decide how these topics dovetail

o In Chopan, the sleeping problem was tackled by having sleeping

nodes check-in with their proxies while awake, notify model might
solve this problem to some extent but still have to coordinate the
sleep/awake times

o In Chopan we actually used caching to deal with POSTs, etc because

otherwise how do you send a request to a sleeping node? The
current caching sections are to be exclusive to GETs, but we still
need to solve the problem for other types if methods.

[zach@…]

In coap-01 we should aim at completing the proxying specification with these featues:

• Normal proxying using Uri-Full Option to indicate actual destination.
• Support for GET caching

In coap-02 we can also consider further improvements such as these, which in the mean time can be discussed in coap-misc:

• Intercept proxying
• Caching of POST and dealing with sleeping nodes

[zach@…]

coap-01 section completed. Will make a new ticket for coap-02 improvements later.