Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update gNPSI README to use the correct full form of gNPSI, fixes typos and formatting. #18

Merged
merged 1 commit into from
Sep 12, 2024
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 6 additions & 6 deletions README.md
Original file line number Diff line number Diff line change
@@ -1,4 +1,4 @@
# Generic Network Packet Streaming Interface(gNPSI)
# gRPC Network Packet Streaming Interface(gNPSI)

## Objective

Expand All @@ -22,12 +22,12 @@ Further, only either UDP or RPC streaming would be supported at any point in tim

### Provide Sample over gRPC

Have single gNSI RPC's in the service and include typing in response
Have single gNPSI RPC's in the service and include typing in response

* Pro's
* Pros
* Single RPC entry point
* Samples are easily serialized for consumption later
* Con's
* Cons
* Requires the most business logic on the collector and agent to handle how errors handled for requests for a protocol that isn't configured or supported is handled.


Expand All @@ -41,8 +41,8 @@ See [proto](https://github.com/openconfig/gnpsi/tree/main/proto)

The device provides the gRPC server, like gNMI and gNOI. The collection system would then need a list of devices to connect to.

* Pros:
* Pros
* Congruity with gNMI and gNOI.
* Failure to connect is available in a single location, easing debugging and triage.
* Cons:
* Cons
* Discovery is pushed onto the collection system which can leave a device disconnected.
Loading