Hi，
The question is not very different from the UDP to UDP proxying case.
Something is different.
If a request came in via a UDP CON (which is the equivalent of using a
reliable transport protocol),
should the proxy use CON or NON for the forwarded request?
If it keeps the semantics end-to-end, the proxy just forwards the message.
If it has the semantics hop-by-hop, the proxy can decide what type of
message to transfer.
Regards,
Gengyu WEI
Network Technology Center
School of Computer
Beijing University of Posts and Telecommunications
-----原始邮件-----
From: Carsten Bormann
Sent: Tuesday, May 02, 2017 2:01 PM
To: weigengyu
Cc: Yoshifumi Nishida ; Brian Raymor ; tsv-art(_at_)ietf(_dot_)org ;
draft-ietf-core-coap-tcp-tls(_at_)ietf(_dot_)org ; core(_at_)ietf(_dot_)org ; ietf(_at_)ietf(_dot_)org
Subject: Re: [core] TSV-ART review of draft-ietf-core-coap-tcp-tls-07
On May 2, 2017, at 07:31, weigengyu <weigengyu(_at_)bupt(_dot_)edu(_dot_)cn>
wrote:
The problem is when the C2C Proxy have got a message form the CoAP/TCP
side,
how the Proxy make a decision to delivery CON or NON message carrying CoAP
over UDP?
The question is not very different from the UDP to UDP proxying case.
If a request came in via a UDP CON (which is the equivalent of using a
reliable transport protocol), should the proxy use CON or NON for the
forwarded request?
I’d say, in both cases, CON should be the default way of forwarding the
reliable request.
But there may be specific cases where a NON may be appropriate — CoAP does
not provide the client with a way to control the proxy here.
Is that a problem? Tell me more about your use case.
Grüße, Carsten