Skip to content

Conversation

@robshakir
Copy link
Member

 * (M) rpc/gnmi/gnmi-extensions.md
  - Add clarification that unknown extensions must not be treated
    as an error.
  - Add clarification that known extensions that are invalid may
    be treated as an error.

 * (M) rpc/gnmi/gnmi-extensions.md
  - Add clarification that unknown extensions must not be treated
    as an error.
  - Add clarification that known extensions that are invalid may
    be treated as an error.
@robshakir
Copy link
Member Author

@LimeHat
Copy link

LimeHat commented Apr 7, 2025

Lgtm. Thanks.

Copy link

@earies earies left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Content LGTM.

Also update the revision date and version?

Should we also update to the gnmi spec and gnmi_ext.proto?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Updated revision date + version.

What do you propose we update in the gNMI spec + proto? Part of the reasons for the modularity of specs we have is to prevent there being a single doc that is somewhat unmaintainable.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@dplore friendly ping.

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

Successfully merging this pull request may close these issues.

4 participants