Rob Shakir

@dplore PTAL, apologies for the delay.

Hi Benoit, In the specification that we're just working through the last stages on publishing (see #31), we added an `error` field to the `SubscribeResponse` message. The accompanying specification discusses...

@pborman I think this could be achieved with what we have today - using `NotFound` to indicate that there is a temporary reason that the path does not exist (valid...

On the path validity discussion - I started some library work in response to an internal bug that Marcus raised; let's try and get precise definitions in code therein, and...

I'm not sure that I understand the question here. In general, we can consider that a subscription to (using the `PathElem` syntax): ``` path: < elem: < name: "interfaces" >...

Yes -- this looks correct (with the exception that gNMI paths do not use the namespace prefix).

Yes - it sounds like `event_timestamp` is what should be in the `Notification` of the gNMI message - and that this proto should carry `export_timestamp` and `gnmi_export_timestamp` or something similar...

Thanks for updating the proto -- please ping the PR when the change is made. I'm happy for you to start a well-known extension issue to discuss which fields we...

Hi! Today, we don't explicitly require that paths in a `SetRequest` are fully resolved -- indeed, we allow them specifically for `delete` cases. There's clearly some complexity with handling this...

Hi Aaron, Apologies, I missed this issue previously. Currently, we're proposing that for unkeyed lists, they are not referenced individually. For telemetry values, this means that they would need to...