Rob Shakir

Hi! Thanks for the contributions. Two requests: * Please sign the CLA for contributions - either individually or as a corporate signer. * Please update the `openconfig-version` for the file...

Thanks for the proposal here -- and the documentation links. This looks reasonable to me. @dplore @rolandphung @hellt @rgwilton - PTAL here :-)

From our meeting on 7th January 2021: - We will split out the RPCs so that we can have per-service authorisation on an RPC-level. - Must users already be created...

We are proposing to move these pattern statements to using an extension rather than the inbuilt pattern statement. This needs to be synchronised with changes to tooling that parses the...

I would propose the following migration strategy: * Define the new extension name - and add handling in client libraries. In goyang, I propose to support this natively as though...

All of your top points are about YANG release management. As I've said in the IETF before, the big-bang-let's-change-everything-at-once release model seems antiquated, and makes life difficult for tools authors....

I think there's also some further complexity here that comes from (RFC7951)[https://tools.ietf.org/html/rfc7951] too. In this specification, YANG `decimal64`, `uint64` and `int64` are encoded as strings. This means that in JSON...

The other question, apologies, where would we encounter `Infinity` or `NaN` in a context that these are valid values for a leaf in a schema? It wasn't immediately obvious for...

i don't think the way that this PR proposes to make this change is compatible with the modelling approach we have for import policies today. the import policies that are...

Hi! 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,...