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

Jump to bottom

Don't overload PING frame semantics #1091

Closed
janaiyengar opened this issue Feb 1, 2018 · 0 comments
Closed

Don't overload PING frame semantics #1091

janaiyengar opened this issue Feb 1, 2018 · 0 comments
Labels
-transport design An issue that affects the design of the protocol; resolution requires consensus. has-consensus An issue that the Chairs have determined has consensus, by canvassing the mailing list.

Comments

@janaiyengar
Copy link
Contributor

The PING frame is currently overloaded for reachability and path validation semantics. This is icky to implement, especially since an ACK is adequate in one case, while a PONG frame is required for the other. It would be nice to use separate frames for path validation and leave PING to be used for only reachability.
@janaiyengar janaiyengar mentioned this issue Feb 1, 2018
Merged
@martinthomson martinthomson added design An issue that affects the design of the protocol; resolution requires consensus. -transport labels Feb 1, 2018
@mnot mnot added the has-consensus An issue that the Chairs have determined has consensus, by canvassing the mailing list. label Mar 5, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
-transport design An issue that affects the design of the protocol; resolution requires consensus. has-consensus An issue that the Chairs have determined has consensus, by canvassing the mailing list.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@martinthomson @mnot @janaiyengar