[core] CoAP: non-traditional response forms

[Carsten Bormann <[e-mail]>]

I have submitted a new draft, draft-bormann-core-responses-00.txt.

This is trying to outline additional ways CoAP responses may be formed, beyond those defined in RFC 7252.

This draft is a reaction to developments within LWM2M and OCF that are not yet all public.

I expect these ideas to be controversial.
(I myself am not convinced that any of these approaches should be pursued.) 
But they would solve real problems.

I cannot possible ask Jaime to allocate agenda tine for this this week before there was a mailing list discussion.  So please fire away…

Grüße, Carsten

Name:		draft-bormann-core-responses
Title:		CoAP: Non-traditional response forms
Htmlized:       https://tools.ietf.org/html/draft-bormann-core-responses-00
Abstract:
  In CoAP as defined by RFC 7252, responses are always unicast back to
  a client that posed a request.  The present memo describes two forms
  of responses that go beyond that model.  These descriptions are not
  intended as advocacy for adopting these approaches immediately, they
  are provided to point out potential avenues for development that
  would have to be carefully evaluated.