| Re: [cf-dev] CoAP general: CoAP over TCP and observing |
|
Hi Martin, Let me first point you to the specification of the wanted behavior: so instead of RST, the client is intended to either ignore the notify or to close the TCP connection. (By the way, the californium coap over tcp still needs some work
J ). If you’re interested in the discussion of details of the core RFCs, there is a mailing list
http://www.ietf.org/mail-archive/web/core/current/threads.html and a status page https://trac.tools.ietf.org/wg/core/ Sometimes there are also discussion on the github repos (as on https://github.com/core-wg/coap-tcp-tls) Hope this helps. Mit freundlichen Grüßen / Best regards Achim Kraus Bosch Software Innovations GmbH Communications (INST/ECS4) Stuttgarter Straße 130 71332 Waiblingen GERMANY Registered office: Berlin, Register court: Amtsgericht Charlottenburg, HRB 148411 B Executives: Dr.-Ing.
Rainer Kallenbach; Michael Hahn Von: cf-dev-bounces@xxxxxxxxxxx [mailto:cf-dev-bounces@xxxxxxxxxxx]
Im Auftrag von Martin Scheffler Hi all, is there a mailing list to discuss general CoAP issues? I think there is a conflict between rfc 7641 for observing resources and the draft for CoAP over TCP. To cancel an observation the observer should send a RESET message to the observed resource. This is not possible when using the TCP transfer
because RESET messages are part of the reliability mechanism not included in the TCP spec. Is there any work done on the observable spec? Or is that dead? Thanks for answers or for pointing me to a better place to discuss this! Cheers, Martin |