AtHeartEngineer/specs
1
0
Fork 0
mirror of https://github.com/vacp2p/specs.git synced 2026-01-09 15:28:03 -05:00
Code Issues Packages Projects Releases Wiki Activity

fix link to protobuf spec & grammar issues

Browse Source
This commit is contained in:
Yusef Napora
2019-07-08 14:10:04 -04:00
parent 50884872c7
commit 83da4f0643
1 changed files with 5 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files

9
plaintext/README.md
View File

@@ -45,7 +45,7 @@ The plaintext protocol described in this document has the protocol id of
`/plaintext/1.1.0`.
An earlier version, `/plaintext/1.0.0`, was implemented in several languages,
but did not include any exchange of public keys or peer ids. This led to
but it did not include any exchange of public keys or peer ids. This led to
undefined behavior in parts of libp2p that assumed the presence of a peer id.
As version `1.0.0` had no associated wire protocol, it was never specified.
@@ -124,14 +124,15 @@ key and peer id for the remote peer in their local peer metadata storage (e.g.
go-libp2p's [peerstore][go-libp2p-peerstore], or js-libp2p's
[peer-book][js-peer-book]).
Following delivery of `Exchange` message, the plaintext protocol is complete. No
response is required, as it is assumed that peers will close the connection if
peer id validation fails.
Following delivery of `Exchange` messages, the plaintext protocol is complete.
No response is required, as it is assumed that peers will close the connection
if peer id validation fails.
Once the exchange is complete, the remainder of the [connection upgrade
process][conn-spec-conn-upgrade] takes place, and a stream multiplexer is
negotiated if the underlying transport requires one.
[protobuf-spec]: https://developers.google.com/protocol-buffers/docs/reference/proto2-spec
[secio-spec]: ../secio/README.md
[tls-spec]: ../tls/tls.md
[peer-id-spec]: ../peer-ids/peer-ids.md