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

NGTCP2_ERR_RETRY #101

Open
jagerman opened this issue Feb 1, 2024 · 2 comments
Open

NGTCP2_ERR_RETRY #101

jagerman opened this issue Feb 1, 2024 · 2 comments

Comments

@jagerman
Copy link
Member

jagerman commented Feb 1, 2024

In looking at ngtcp2 example/server, I came across handling of NGTCP2_ERR_RETRY being a possible return value from ngtcp2_conn_read_pkt, along with a bunch of stuff in that same example c++ code to actually build and send a retry packet.

I'm thinking we should do the same.

@jagerman
Copy link
Member Author

jagerman commented Feb 2, 2024

Actually, on looking at this some more, this looks like quite a narrow edge case. Low priority.

@dr7ana
Copy link
Collaborator

dr7ana commented Feb 4, 2024

@jagerman i knocked out a code pathway for retry tokens on initial packets, we can reuse some of the methods for the return value case from ngtcp2_conn_read_pkt

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants