Shouldn't this be the time at which the record was created in the server (close to the time at which the measurement was taken).
In the case of other streams defined in TR548, a similar thing is achieved by using "token" in each record and expecting the client to keep track of the last token it has consumed; and in case of reconnection, the client specifes the token from which the server has to send again. And the server can use the information in the token to identify a specific position in the log that provides the stream.
It will be good to maintain the same concept for gNMI subscriptions also. That is, use the start time to identify a specific position in the log and start sending from there. In this case, the specified time has to be correlated to a position in the log and this position will depend on when the record was created in the log and not when the record was sent previously to any consumer.
It will be problematic for the server to keep track of when each record is sent to the consuming client.
Sec 6.3.3 says the following:
What does it mean the "time the record was sent"?
Shouldn't this be the time at which the record was created in the server (close to the time at which the measurement was taken). In the case of other streams defined in TR548, a similar thing is achieved by using "token" in each record and expecting the client to keep track of the last token it has consumed; and in case of reconnection, the client specifes the token from which the server has to send again. And the server can use the information in the token to identify a specific position in the log that provides the stream.
It will be good to maintain the same concept for gNMI subscriptions also. That is, use the
starttime to identify a specific position in the log and start sending from there. In this case, the specified time has to be correlated to a position in the log and this position will depend on when the record was created in the log and not when the record was sent previously to any consumer.It will be problematic for the server to keep track of when each record is sent to the consuming client.
CC: @nigel-r-davis , @amazzini