search

openconfig / public

Repository for publishing OpenConfig models, documentation, and other material for the community.
Apache License 2.0
891 stars 645 forks source link

Use of prefix "inet" by both both ietf-inet-types and openconfig-inet-types creates a problem. #79

Closed mjethanandani closed 3 weeks ago

mjethanandani commented 7 years ago

openconfig-isis module imports ietf-inet-types with a prefix of inet. openconfig-isis also includes openconfig-isis-lsp which imports openconfig-inet-types with a prefix inet. Thus the module openconfig-isis has two modules using the same prefix, which controllers will have a problem resolving.

Suggest that openconfig-isis-lsp use openconfig-inet-types with a prefix like oc-inet to de-duplicate the prefix.

robshakir commented 7 years ago

According to RFC6020, this shouldn't be an issue. Imported modules are scoped according to the module or submodule that they are imported in, therefore it should not be the case that any tooling ends up with the scenario that it can resolve inet to ietf-inet-types in openconfig-isis-lsp, since openconfig-isis imports should not be available there. I recommend fixing this in the toolchain that you're using.

That being said, we'll address this for the sake of consistency such that inet is used in openconfig-isis to mean openconfig-inet-types as part of the wider move away from IETF modules.

github-actions[bot] commented 2 months ago

This issue is stale because it has been open 180 days with no activity. If you wish to keep this issue active, please remove the stale label or add a comment, otherwise will be closed in 14 days.