Hi,
May be we are all
missing the point here, or I am miss reading it.
The device will not
send the message in HTTP, so how will the proxy work. Device
will generate a CoAP message (not sure what format it would
be as the message format for UDP and TCP are different).
Please note we are talking about the Non IP support where
the device does not have an IP address. It will send the
message as a signalling message to the wireless network.
The SCEF in wireless
core network (TS 23.682) will push this message as received
inside a HTTP message (HTTP Payload) as the north interface
for SCEF is HTTP REST based.
Now, say in CoAP
stack like we have UDP, TCP we have a HTTP connector, which
receives the HTTP message looks at the payload and does the
CoAP handling. So, I have few basic questions. What CoAP
message format it would be (UDP, TCP ????). If you look at https://tools.ietf.org/html/draft-ietf-core-coap-tcp-tls-05 you
will see that the message format for TCP and UDP are
different. ?
Can you please
confirm how you think the HTTP to UDP proxy work? Are
you thinking to develop an intermediate node which get the
CoAP message as an HTTP payload and it extracts the message
and creates an UDP tunnel to the CoAP server and sends the
message? What advantage do you see for this rather than
modifying the CoAP stack?
Kindly let us know.
Thanks, Santos
