Esko Dijk <[email protected]> wrote: > 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?
Ideas:
a) some kind of magic option for the Uri-Path that is short for "/.well-known/"
Reading 7252, section 5.10.1, I don't see a way to do this, short of
exploiting the fact that "." and ".." is not otherwise allowed, and that
is icky.
b) allocating some new option Uri-WellKnown, which could contains a CBOR int,
and asking IANA to add a new column to the .well-known registry for this
integer.
I was pondering whether or not we needed to discover/negotiate if we'd use
this or not. I think mostly not: any RFC defining a .well-known entry would
say if they are doing this or not. Not clear to me that there are many
.well-known users other than RFC9148, cBRSKI, and of course... /core?rt.
> 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.
--
Michael Richardson <[email protected]>, Sandelman Software Works
-= IPv6 IoT consulting =- *I*LIKE*TRAINS*
signature.asc
Description: PGP signature
_______________________________________________ Anima mailing list -- [email protected] To unsubscribe send an email to [email protected]
