You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
The text was updated successfully, but these errors were encountered:
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.
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
The text was updated successfully, but these errors were encountered: