Re: [art] [core] Artart last call review of draft-ietf-core-coap-tcp-tls-07

Hi Matthias,

while I can imagine uses cases like that, I don’t believe that a specification has to be exhaustive in listing its use cases.  The CoAP over WebSockets work was motivated by getting full CoAP functionality into a browser by providing a way for JavaScript code to use a proxy, and maybe it is enough to point this out in the specification.  I don’t think it is expedient to add use cases that tend to press unrelated buttons in people — even if they are made possible by the generality of the specification.  Implementers will find out anyway...

Grüße, Carsten

> On Apr 19, 2017, at 19:58, Kovatsch, Matthias <matthias.kovatsch@siemens.com> wrote:
> 
> Hi there
> 
> I am picking up this discussion again, as I was made aware of another use case for CoAP-over-WebSockets related to firewalls or shielded networks: without having looked into the details, HTTP CONNECT apparently does not allow for OAuth, while upgrading to WebSockets can make use of OAuth to establish a secure channel between two edge CoAP proxies that, for instance, forward requests from devices behind one firewall to devices behind another firewall.
> 
> Best wishes
> Matthias
> 
> _______________________________________________
> art mailing list
> art@ietf.org
> https://www.ietf.org/mailman/listinfo/art
> 