Skip to content

Add signedPeerRecord and discussion of message sizes to identify#709

Open
achingbrain wants to merge 2 commits intomasterfrom
docs/add-signed-peer-record-and-message-sizes-to-identify
Open

Add signedPeerRecord and discussion of message sizes to identify#709
achingbrain wants to merge 2 commits intomasterfrom
docs/add-signed-peer-record-and-message-sizes-to-identify

Conversation

@achingbrain
Copy link
Copy Markdown
Member

Adds the missing signedPeerRecord field and an implementation notes section to discuss max message sizes and how to send/receive multiple identify messages during one transaction.

Also updates the language around receiving messages to make it clear that multiple messages may be sent.

Adds the missing `signedPeerRecord` field and an implementation notes
section to discuss max message sizes and how to send/receive multiple
identify messages during one transaction.
Comment thread identify/README.md Outdated
Comment thread identify/README.md
should break it up into smaller chunks.

For optimum backwards compatibility the first message SHOULD NOT exceed 2KB.
Subsequent messages SHOULD NOT exceed 4KB.
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can signed peer records be subdivided? I suspect they can themselves exceed 4 KB.

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

One possible issue is signature size of signed peer records if/when libp2p supports post quantum signatures - 4KB would be too small for ML-DSA-44 and ML-DSA-65, 8KB would be too small for ML-DSA-87

| Variant | Public key (bytes) | Signature (bytes) |
| --- | ---: | ---: | ---: |
| ML-DSA-44 | 1312 | 2420 |
| ML-DSA-65 | 1952 | 3309 |
| ML-DSA-87 | 2592 | 4627 |

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: Triage

Development

Successfully merging this pull request may close these issues.

5 participants