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

Provision for including Extension information in Capability Response #75

Open
amanand opened this issue May 20, 2020 · 2 comments
Open

Comments

@amanand
Copy link

amanand commented May 20, 2020

Hi,
The CapabilityResponse currently has the extension field but i think it is for exporting additional message through extensions. However can we have another field in the Capability response to include the extension information, i.e the extension ID (name and value) and the Extension message name?
If not, then what is the best way to publish the extension IDs to avoid conflict in multi vendor scenarios?

Thanks
Amish

@robshakir
Copy link
Contributor

Hi!

Extensions should only use IDs that are currently assigned -- right now, this is just 999 (EXPERIMENTAL) for which no inter-op is expected. If you need an extension ID, per the discussion in https://github.com/openconfig/reference/blob/master/rpc/gnmi/gnmi-extensions.md - please send a PR to this repo with the next ID and a link to the specification for how this extension is used.

We specifically chose this approach (registered extension IDs) vs. proto.Any to maximise the opportunity for interoperability within the protocol.

Thanks,
r.

@amanand
Copy link
Author

amanand commented May 27, 2020

Hi Rob,
Thanks for you reply. I have created the following pull request for adding Juniper's extension ID:
#76

Thanks
Amish

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