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

Server Packet Handling when you recognize the connection #3837

Closed
ekr opened this issue Jul 8, 2020 · 0 comments · Fixed by #3867
Closed

Server Packet Handling when you recognize the connection #3837

ekr opened this issue Jul 8, 2020 · 0 comments · Fixed by #3867
Labels
-transport editorial An issue that does not affect the design of the protocol; does not require consensus.

Comments

@ekr
Copy link
Collaborator

ekr commented Jul 8, 2020

S 5.2.2 says:

Packets with a supported version, or no version field, are matched to a
connection using the connection ID or - for packets with zero-length connection
IDs - the local address and port. If the packet doesn't match an existing
connection, the server continues below.

So, this tells us what to do if we don't match, but not if we do match. I know this is a nit, but I think there should be some kind of pointer after the first sentence.

martinthomson added a commit that referenced this issue Jul 8, 2020
Not saying explicitly that was a small oversight.

Closes #3837.
@martinthomson martinthomson added -transport editorial An issue that does not affect the design of the protocol; does not require consensus. labels Jul 8, 2020
@LPardue LPardue added this to Triage in Late Stage Processing Jul 8, 2020
@LPardue LPardue moved this from Triage to Editorial Issues in Late Stage Processing Jul 8, 2020
Late Stage Processing automation moved this from Editorial Issues to Issue Handled Jul 9, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
-transport editorial An issue that does not affect the design of the protocol; does not require consensus.
Projects
Late Stage Processing
  
Issue Handled
Development

Successfully merging a pull request may close this issue.

2 participants