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.

Sign up for GitHub

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

noise: introduce an extension registry #453

Merged
merged 5 commits into from
Sep 23, 2022
Merged

noise: introduce an extension registry #453

Changes from 1 commit
Commits
Show all changes
5 commits
Select commit Hold shift + click to select a range
685ef18
noise: introduce an extension registry
marten-seemann Sep 14, 2022
7a517af
noise: remove WebRTC and stream muxer from NoiseExtensions
marten-seemann Sep 15, 2022
215419c
don't specify how many Noise extensions there are
marten-seemann Sep 16, 2022
0991510
improve description of extensions
marten-seemann Sep 16, 2022
b0818fa
noise: add Changelog
marten-seemann Sep 22, 2022
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
Prev Previous commit
Next Next commit
don't specify how many Noise extensions there are
  • Loading branch information
@marten-seemann
marten-seemann committed Sep 22, 2022
commit 215419c727be7d93c25e7b7cf5a96635a41195dc
7 changes: 3 additions & 4 deletions noise/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -292,10 +292,9 @@ mechanism, this specification defines an extension registry, modeled after
[RFC 9000](https://datatracker.ietf.org/doc/html/rfc9000#section-19.21)
(for QUIC).

This spec currently defines 3 extension code points for the `NoiseExtensions`
protobuf. Note that this document only defines the code point, and leaves
it up to the protocol using that code point to define semantics associated
with that code point.
Note that this document only defines the `NoiseExtensions` code points, and
leaves it up to the protocol using that code point to define semantics
associated with these code point.

Code points above 1024 MAY be used for experimentation. Code points up to
this value MUST be registered in this document before deployment.
Expand Down