Hi Michel,
> Le 5 juin 2015 à 17:17, Michel Veillette <[email protected]> > a écrit : > > Hi Alexander > > In your presentation at 6TiSCH, you propose the following data node ID > structure. > > • 32 bits YANG ID > – 20 bits for module ID (assigned by IETF) > – 10 bits for data node ID (generated deterministically) > > Based on this structure, we can reserve module ID zero for aliases. > I was just summarizing what was discussed on the discussion in CoMI. Actually, it is 30 bits YANG ID, but that’s for purposes to be consistent with the YANG hash and I don’t mind keeping it 30 bits. > If we want to minimize both the network an node resources require by this > alias mechanism, we can map an entire module to this space. > This can be implemented by a single integer resource (e.g. leaf > alliassedModule { type uint32 } ) > This approach require 4 bytes per CoMI server accessed. > It is possible to map an entire module to the alias space and this is up to the operator. However, if you load two modules which redefine the same alias you will loose the benefit from it. Maybe it would be interesting to be able to specify that you want the aliases from THIS specific module to be used. If the /mg/0 alias is reserved for managing the aliases, this could be simply saying: POST /mg/0 { "source_uri" : "/mg/BAA" } where /mg/BAA is the YANG id of the module (20 bits module ID + 10 bits set to 0). This way, the server will know: OK, get the alias mapping from the YANG scheme of module with ID = B (as defined by the IETF). Or, you can dynamically configure the mapping: POST /mg/0 { YANG_id : alias, YANG_id : alias, YANG_id : alias } > If we want a more complex but more flexible aliases mechanism, your proposed > map of (allias, YANG ID) seem the solution. > However, we have to consider that this structure can be as large as 1250 > bytes per CoMI server accessed if limited to 256 aliases. This is assuming you need a separate mapping for each server. I would suppose that in a network you’ll have a single alias mapping (maybe two?) - after all, you’re trying to optimize the management of your devices (servers). So, typically you’d map all 6tisch devices with aliases 1-10 (channel, slot, etc.) and use that on them, and on all other you’d access the full ID. Best, Alexander > > <image001.jpg> > Michel Veillette > System Architecture Director > Trilliant Inc. > Tel: 450-375-0556 ext. 237 > [email protected] <mailto:[email protected]> > www.trilliantinc.com <http://www.trilliantinc.com/>
_______________________________________________ 6tisch mailing list [email protected] https://www.ietf.org/mailman/listinfo/6tisch
