Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Question: [email protected] deprecated parts? #905

Open
maksimvuleta opened this issue Dec 1, 2020 · 1 comment
Open

Question: [email protected] deprecated parts? #905

maksimvuleta opened this issue Dec 1, 2020 · 1 comment

Comments

@maksimvuleta
Copy link

What is the purpose of the deprecated parts in the [email protected] module?

The typedef interface-state-ref and container interfaces-state have the status deprecated.

Is it planned to remove this typedef and container from YANG module, or change the status to obsolete?
I do not see any purpose to have it in the yang data tree as the leaves from the container interfaces-state are already defined as the part of the container interfaces.

@miroslavKovacPantheon
Copy link
Contributor

Hello,

According to yang RFC 7950 you can only add new typedef. This is for backward compatibility.

For example - I am creating a module and importing ietf-interfaces because of that typedef but I am not defining revision for that import. I use that typedef in my module and later I would update all the imported modules to the latest ones. If I have followed all the rules of yang RFC then I should be able to do that. If that typedef would be removed I would not be able to use that module any more for my purposes.

The backward compatibility is very important in yang and this is why you should never removed any node typedef notification rpc or anything similar only deprecate it and then obsolete it later.

Regards,
Miroslav kovac

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants