aws / s2n-quic Public

Notifications
Fork 124
Star 1.2k

Code
Issues 229
Pull requests 6
Actions
Security
Insights

Additional navigation options

Code
Issues
Pull requests
Actions
Security
Insights

Issues: aws/s2n-quic

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

229 Open 299 Closed

Author

Filter by author

Label

Filter by label

Use alt + click/return to exclude labels

or ⇧ + click/return for logical OR

Projects

Filter by project

Milestones

Filter by milestone

Assignee

Filter by who’s assigned

Assigned to nobody

Sort

Sort by

Newest Oldest Most commented Least commented Recently updated Least recently updated Best match

Most reactions

Issues list

Clients may discard new tokens client

Required for the s2n-quic client

compliance:MAY provider

#388 opened Jan 4, 2021 by rday

Unique NEW_TOKEN frames compliance:MUST provider

#387 opened Jan 4, 2021 by rday

Use retry token immediately client

Required for the s2n-quic client

compliance:MUST crate:transport

#386 opened Jan 4, 2021 by rday

Require token in initial packets if retry received compliance:MUST crate:transport

#385 opened Jan 4, 2021 by rday

Investigate if its needed to wait to send a NEW_CONNECTION_ID until previously retired connection IDs have been confirmed compliance:SHOULD connection_id_manager

#380 opened Dec 23, 2020 by WesleyRosenblum

Grease transport parameter interop

#377 opened Dec 22, 2020 by rday

Add bolero tests for PeerIdRegistry connection_id_manager enhancement

New feature or request

#372 opened Dec 18, 2020 by WesleyRosenblum

Make active_connection_id_limit configurable client

Required for the s2n-quic client

connection_id_manager connection_migration

#371 opened Dec 18, 2020 by WesleyRosenblum

Providers documentation