Hello,
Andy Bierman wrote:
2.1.1. capabilities
From RFC4741: "The device uses capabilities to announce the set of
data models that the device implements."
This to me means that the device MUST advertise all it's models as
capabilities as well. So the models will be included both in the
capabilities and the schemas branch. Please indicate this.
<sharon>
Experience has shown that was a not the best way to get data model
definitions. I don't think we need to repeat that advise here. We
may want to remove it in an update to RFC4741.
</sharon>
I think it is useful to send the module capabilities in the <hello>.
The very first the manager needs to do is get these module caps,
so it can make sure compatible versions of all the relevant modules
are loaded. Unless the manager is using a proprietary mechanism
(e.g., identifying packages or profiles, not individual modules),
then it will take the same amount of bandwidth and memory for
the <get> as the <hello>.
>
Andy
Andy, according to RFC4741 do you consider it mandatory to advertise all
data models?
- yes
- no
- yes, but as this is a mistake, we should forget it?
