[core] draft-bierman-core-yid-00 open questions

[Michel Veillette <[e-mail]>]

Hi Andy

Following if my answers to the questions listed in draft-bierman-core-yid-00

1) When to assign a module-id

Developers should be in control of when this activity is performed based on the estimated amount of work required to reassign IDs (from temporary assigned IDs within the experimental range to the final IDs) and the impacts on the encoding efficiency of assigning a non stable list of YANG items which generate non sequential IDs. If the developer already own a range of YID/SID, the activity can be perform at any time.

It is important to note that the registration of the resulting .sid file(s) is done independently of the registration of the SID range. When registering a SID range, the module or list of modules targeted is not provided. This give the full freedom to developers to assign IDs when needed.

2) How to support private numbering

A range called "Experimental" spanning both the 16 and 32 bits unsigned integer have been assigned to this purpose.
https://tools.ietf.org/html/draft-somaraju-core-sid-01#section-7.1

3) How to combine registries

Not needed, all registrars, SDO shall receive a specific range from IANA.

4) Should more YANG statements be numbered

Yes
rpc, action, notification, module, submodule, feature

5a) How to support anyxml

anyxml represents a single data node with an arbitrary content.
This data node have a single ID assigned to it the same way as any other data node, nothing special is required.

5b) How to support anydata

The anydata define an instance of an unspecified schema node (leaf, leaf-list, container, list).
All possible schema node supported by an anydata need to be register to one of the .sid files.
It is the responsibility of the developer(s) to add these SIDs to one or multiple .sid files manually if not already present.
A section need to be added to the draft to clearly describe this approach.

Regards,
Michel Veillette