For BRSKI itself i am also not sure if the saving is worth it when we
count the relative byte savings. At most i might gain those bytes
for less likelyhood that my long payload won't exceed the MTU i have -
but eski/mcr would know better if thats an issue.
On the other hand, we're spending a lot more pain with all those binary
mappings in
constrained solutions with CoAP and CBOR - and then we get this really
totally unnecessaerily verbose, "make it nice to humans" (who the heck are
humans in IoT ?) coming from the web world in our face. Why ?!
But beside such a principled rant (?useless?):
How about i try to build an energy harvesting light switch that uses
LPwan to transmit commands and is hence very energy constrained.
My URLs are /.well-known/ctrl/0 or /.well-known/ctrl/1 to switch on/off
And if i think of the typical resolution from /.well-known to shorter
URLs, then that too creates a total useless layer of complexity. I'd
have to do this during provisioning of the switch, when i externally
power it so i can burn the result into flash, but if every possible
receiver does not necessarily guarantee the same resolution, then i
would have to collect the resolution of the receivers upfront, to kn ow
what to burn which may make my overall provisioning much more complicated.
Cheers
Toerless
On Tue, Jul 22, 2025 at 07:11:13AM +0200, Achim Kraus wrote:
> Hi Esko,
> Hi list,
>
> > could there be a new CoAP Option to express a particular path like
> > "/.well-known/foo" into a very short option e.g. 1 or 2 bytes overhead?
>
> I would assume this as "over optimization".
> Would it be possible to have some relevant examples along with the number of
> bytes in total and savings?
>
> In my experience, "/.well-known" is used mainly once at the begin of a
> sequence of request. It usually respond with a larger payload. Saving 10
> bytes doesn't pay off in scenarios, where 1000 bytes are in use.
>
> br
> Achim
>
>
> Am 21.07.25 um 16:11 schrieb Esko Dijk:
> > Just an idea that came up here in the ANIMA WG:
> > could there be a new CoAP Option to express a particular path like
> > "/.well-known/foo" into a very short option e.g. 1 or 2 bytes overhead?
> >
> > That could mitigate some concerns about using "/.well-known" type paths
> > which today adds many bytes of overhead to a message which has little
> > value because always identical for a particular application.
> >
> > The receiver is of course assumed to know this option, just like it
> > would know (guaranteed by system/solution design) the "/.well-known/foo"
> > path otherwise.
> >
> > A related idea is just an option to encode "/.well-known" in short form.
> >
> > thanks for any feedback/reactions you may have ;)
> >
> > Esko
> >
> > _______________________________________________
> > core mailing list -- [email protected]
> > To unsubscribe send an email to [email protected]
>
> _______________________________________________
> Anima mailing list -- [email protected]
> To unsubscribe send an email to [email protected]
--
---
[email protected]
_______________________________________________
Anima mailing list -- [email protected]
To unsubscribe send an email to [email protected]
