Open
Conversation
Owner
Hmm. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This is another take on how we actually can work with standins. After discussing with @vvilimek and reading RFC 7951 and 9254, we found out that transcoding is not resolved in these documents at all, and therefore it makes no sense to suddenly specify all the intermediate nodes and round trips here.
I have split the transcoding into a separate document, mentioning also Netconf / Restconf / Coreconf translation, as there is quite a lot to work through.
We also thought about how to distribute the answer to "which standins have been used", and realized that in addition to the main yang file, one always also needs to distribute the SID files, and therefore the channels are already there. Thus one can simply create another file, this time specifying how the values are encoded, and distribute it along. We should then add this into the Constrained YANG Library.
This pull request is mostly a request for comments and discussion. There is some more work needed and I don't wanna dump time into making things precisely if you find some major problems. Yet as for now, we think that this is a more viable path than what we were trying to do before.
(This pull request semantically supersedes #10)