[Interop-dev] Round 2: Network Device Config JSON Schema

[Nemesis]

Hey,

On 11/05/2014 08:45 PM, Mitar wrote:

[CUT]

> and it should not be a required attribute, so that the applications that
> do not deal with this attribute just ignore it.
> Just related comment: I think we should not require anything. For the
> sake of extensibility. We just define that if you want to put something
> in, you should put it in this and this way, but if you do not know how
> to generate something, you do not have to. The consumer has to know how
> to handle missing fields and extra fields, no?

No required field sounds a great way to get started.


[CUT]

>> I would also like to have a vendor/manufacturer, which it's easy to get
>> from the mac address prefix.
> I think this should go to the consumer. I would not like to store the
> MAC prefix table on the nodes to have to support this.
>

I agree with you that it's foolish to have the mac prefix tables on the
nodes.

I can still add this attribute in my implementations (mostly netengine),
but it would be nice to have it (optional as all other attributes).

For example, the agent on openwrt could return the JSON without the
manufacturer attribute, but a library like netengine can add it on the
server side.

What do you think?

Federico