search

core-wg / core-problem-details

Other
1 stars 1 forks source link

The "x dash" problem #2

Closed thomas-fossati closed 2 years ago

thomas-fossati commented 4 years ago

Context: RFC 6648, in particular the analysis in Appendix B

The problem is if the producer never updates to the public format, consumers – not just CoAP clients but the whole logging pipeline – need to cope for an indefinite amount of time.

Unfortunately, consumers don’t seem to have much leverage.

We define a private-to-public migration plan from the onset, but to what extent is that effective in preventing the problem?

We need to provide discussion on strategies for minimising the risk of “eternal pollution” (e.g., use an automated software update mechanism.)


cabo commented 2 years ago

-04 of course still has a form of the x-dash problem (for custom problem details entries), but it is minimized as far as we can by strictly separating the "play as I like" space (URIs) from the registered space (numbers). It is not clear how this can be further improved.