Discussion:
[core] Confirmable message
Ana Minaburo
2017-01-24 08:42:08 UTC
Permalink
Hi Peter

In the draft, draft-vanderstok-core-comi-11.txt, you mention that a
confirmable message is mandatory for carry CoMi requests. We understand
that for setting a value it is necessary to be sure that the information
has been correctly received. In LPWAN WG we are studying the way to
compress header and reduce traffic on very constraint links. Do you think,
it could be possible to suppress this constraint and allow the use of NON
confirmable messages ?

Thanks

Ana
peter van der Stok
2017-01-24 09:08:51 UTC
Permalink
Hi Ana,

thanks for the motivated suggestion.
We can change the text such that every implementation MUST support the
confirmable requests, and MAY support non-confirmable requests.

would that do the trick? It is then possible that a client that accesses
unknowingly a LPWAN server uses confirmable requests and cannot use
non-confirmable requests.

Other variations are possible. But I like to restrict the number of
request possibilities.

Peter
Post by Ana Minaburo
Hi Peter
In the draft, draft-vanderstok-core-comi-11.txt, you mention that a
confirmable message is mandatory for carry CoMi requests. We
understand that for setting a value it is necessary to be sure that
the information has been correctly received. In LPWAN WG we are
studying the way to compress header and reduce traffic on very
constraint links. Do you think, it could be possible to suppress this
constraint and allow the use of NON confirmable messages ?
Thanks
Ana
_______________________________________________
core mailing list
https://www.ietf.org/mailman/listinfo/core
Michel Veillette
2017-01-30 14:41:21 UTC
Permalink
Hi Ana

In CoMI, "NON confirmable messages" are supported though notifications.
In section https://tools.ietf.org/html/draft-ietf-core-comi-00#section-5.5.1, the sentence
"To check that the client is still alive, the server MUST send confirmable notifications once in a while."
implicitly confirm this option.

Regards,
Michel

From: core [mailto:core-***@ietf.org] On Behalf Of Ana Minaburo
Sent: Tuesday, January 24, 2017 3:42 AM
To: Core <***@ietf.org>; peter van der Stok <***@xs4all.nl>
Subject: [core] Confirmable message

Hi Peter
In the draft, draft-vanderstok-core-comi-11.txt, you mention that a confirmable message is mandatory for carry CoMi requests. We understand that for setting a value it is necessary to be sure that the information has been correctly received. In LPWAN WG we are studying the way to compress header and reduce traffic on very constraint links. Do you think, it could be possible to suppress this constraint and allow the use of NON confirmable messages ?

Thanks

Ana
peter van der Stok
2017-01-31 07:54:55 UTC
Permalink
Hi Ana,

Why not solve this in the gateway and elide the Con flag?
Removes the problem of not LPWAN aware clients contacting LPWAN servers.

Peter
Post by peter van der Stok
Hi Ana
In CoMI, "NON confirmable messages" are supported though
notifications.
In section
https://tools.ietf.org/html/draft-ietf-core-comi-00#section-5.5.1 [1],
the sentence
"To check that the client is still alive, the server MUST send
confirmable notifications once in a while."
implicitly confirm this option.
Regards,
Michel
SENT: Tuesday, January 24, 2017 3:42 AM
SUBJECT: [core] Confirmable message
Hi Peter
In the draft, draft-vanderstok-core-comi-11.txt, you mention that a
confirmable message is mandatory for carry CoMi requests. We
understand that for setting a value it is necessary to be sure that
the information has been correctly received. In LPWAN WG we are
studying the way to compress header and reduce traffic on very
constraint links. Do you think, it could be possible to suppress this
constraint and allow the use of NON confirmable messages ?
Thanks
Ana
------
[1] https://tools.ietf.org/html/draft-ietf-core-comi-00#section-5.5.1
_______________________________________________
core mailing list
https://www.ietf.org/mailman/listinfo/core
Loading...