Skip to content

timestamp in SetResponse (proto vs. spec) #63

@allyn-wade

Description

@allyn-wade

Looking at the latest gnmi.proto, the use of timestamp within an UpdateResult has been deprecated, in favor of a single timestamp within the SetResponse.

However Section 3.4.2 still discusses using the timestamp within the UpdateResult, and makes no mention of the higher-level timestamp.

I presume that the proto is correct and the spec just hasn't been updated to agree yet - can this be clarified?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions