Skip to content

Commit 874c71f

Browse files
ElodinLaarzElodinLaarz
committed
turns out its a github thing
1 parent 942c5c1 commit 874c71f

1 file changed

Lines changed: 15 additions & 15 deletions

File tree

‎rpc/gnmi/gnmi-specification.md‎

Lines changed: 15 additions & 15 deletions
Original file line numberDiff line numberDiff line change
@@ -319,13 +319,13 @@ type. It should be noted that the target never utilises the `Encoding`
319319
enumeration to declare to the client the type of encoding utilised, hence the
320320
client must infer the encoding from the populated `TypedValue` field.
321321

322-
| Name | Description | `TypedValue` field | `Encoding` Value |
322+
| Name | Description | `TypedValue` field | `Encoding` Value |
323323
| --------- | -------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------- | ---------------- |
324-
| JSON | A JSON encoded string as per [2.3.1](#231-json-and-json_ietf). | `json_val` | 0 |
325-
| Bytes | An arbitrary sequence of bytes as per [2.3.2](#232-bytes). | `bytes_val` | 1 |
326-
| Proto | A [Protobuf](https://developers.google.com/protocol-buffers/) encoded message using scalar values as per [Section 2.3.3](#233-protobuf). | `string_val`, `int_val`, `uint_val`, `bool_val`, `bytes_val`, `float_val`, `leaflist_val` | 2 |
327-
| ASCII | An ASCII encoded string representing text formatted according to a target-defined convention (described in [Section 2.3.4](#234-ascii)). | `ascii_val` | 3 |
328-
| JSON_IETF | A JSON encoded string as per [2.3.1](#231-json-and-json_ietf) using JSON encoding compatible with [RFC 7951](https://tools.ietf.org/html/rfc7951). | `json_ietf_val` | 4 |
324+
| JSON | A JSON encoded string as per [2.3.1](#231-json-and-json_ietf). | `json_val` | 0 |
325+
| Bytes | An arbitrary sequence of bytes as per [2.3.2](#232-bytes). | `bytes_val` | 1 |
326+
| Proto | A [Protobuf](https://developers.google.com/protocol-buffers/) encoded message using scalar values as per [Section 2.3.3](#233-protobuf). | `string_val`, `int_val`, `uint_val`, `bool_val`, `bytes_val`, `float_val`, `leaflist_val` | 2 |
327+
| ASCII | An ASCII encoded string representing text formatted according to a target-defined convention (described in [Section 2.3.4](#234-ascii)). | `ascii_val` | 3 |
328+
| JSON_IETF | A JSON encoded string as per [2.3.1](#231-json-and-json_ietf) using JSON encoding compatible with [RFC 7951](https://tools.ietf.org/html/rfc7951). | `json_ietf_val` | 4 |
329329

330330
### 2.3.1 JSON and JSON_IETF
331331

@@ -995,12 +995,12 @@ request a telemetry stream (see [Section
995995

996996
The following table clarifies the target behaviors for `Get` for certain scenarios:
997997

998-
| GetRequest Scenario | Target Behavior |
998+
| GetRequest Scenario | Target Behavior |
999999
| ------------------------------------------------------------------------------------------------------------------------ | ------------------------- |
1000-
| Requested paths exist or a YANG default value is [in use](https://datatracker.ietf.org/doc/html/rfc7950#section-7.6.1). | Value(s) are returned |
1001-
| Requested paths are syntactically correct but one or more paths neither exist (yet) nor has a YANG default value in use. | Return `NOT_FOUND` |
1002-
| Requested paths are syntactically correct but one or more paths is not implemented by the server. | Return `UNIMPLEMENTED` |
1003-
| One or more requested paths is syntactically incorrect. | Return `INVALID_ARGUMENT` |
1000+
| Requested paths exist or a YANG default value is [in use](https://datatracker.ietf.org/doc/html/rfc7950#section-7.6.1). | Value(s) are returned |
1001+
| Requested paths are syntactically correct but one or more paths neither exist (yet) nor has a YANG default value in use. | Return `NOT_FOUND` |
1002+
| Requested paths are syntactically correct but one or more paths is not implemented by the server. | Return `UNIMPLEMENTED` |
1003+
| One or more requested paths is syntactically incorrect. | Return `INVALID_ARGUMENT` |
10041004

10051005
## 3.4 Modifying State
10061006

@@ -1739,12 +1739,12 @@ to configuration.
17391739

17401740
The following table clarifies the target behaviors for `Subscribe` for certain scenarios:
17411741

1742-
| Subscription Scenario | ONCE/POLL | STREAM |
1742+
| Subscription Scenario | ONCE/POLL | STREAM |
17431743
| ------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------- | --------------------------------------------------------------- |
1744-
| Subscribed paths exist or a YANG default value is [in use](https://datatracker.ietf.org/doc/html/rfc7950#section-7.6.1). | Value(s) are returned | Value(s) are returned |
1744+
| Subscribed paths exist or a YANG default value is [in use](https://datatracker.ietf.org/doc/html/rfc7950#section-7.6.1). | Value(s) are returned | Value(s) are returned |
17451745
| Subscribed paths are syntactically correct but one or more paths neither exist (yet) nor has a YANG default value in use. | No value returned for non-existent paths | nothing is sent for non-existent paths (yet), RPC is not closed |
1746-
| Subscribed paths are syntactically correct but one or more paths is not implemented by the server. | Return `UNIMPLEMENTED` | Return `UNIMPLEMENTED` |
1747-
| One or more subscribed paths is syntactically incorrect. | Return `INVALID_ARGUMENT` | Return `INVALID_ARGUMENT` |
1746+
| Subscribed paths are syntactically correct but one or more paths is not implemented by the server. | Return `UNIMPLEMENTED` | Return `UNIMPLEMENTED` |
1747+
| One or more subscribed paths is syntactically incorrect. | Return `INVALID_ARGUMENT` | Return `INVALID_ARGUMENT` |
17481748

17491749
# 4 Appendix: Current Protobuf Message and Service Specification
17501750

0 commit comments

Comments
 (0)