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

[connect-tcp] Move capsule negotiation into the Upgrade Token #2926

Merged
merged 2 commits into from
Oct 21, 2024

Conversation

bemasc
Copy link
Contributor

@bemasc bemasc commented Oct 21, 2024

Closes #2922

Copy link
Contributor

@LPardue LPardue left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Wfm


Server support for the Capsule Protocol is REQUIRED. Servers MUST confirm use of the Capsule Protocol by echoing the "Capsule-Protocol: ?1" header in their response.
Clients of this specification MAY implement "connect-tcp", "connect-tcp-capsule", or both. Accordingly, templated TCP proxy servers for arbitrary clients MUST implement both Upgrade Tokens.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't see why servers MUST implement both. One solution could be to use SHOULD instead (see below). Another option would be to add a sentence saying that servers that only expect one kind of client MAY only implement one of these Upgrade Tokens.

Suggested change
Clients of this specification MAY implement "connect-tcp", "connect-tcp-capsule", or both. Accordingly, templated TCP proxy servers for arbitrary clients MUST implement both Upgrade Tokens.
Clients of this specification MAY implement "connect-tcp", "connect-tcp-capsule", or both. Accordingly, templated TCP proxy servers for arbitrary clients SHOULD implement both Upgrade Tokens to improve compatibility.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

OK, I've rephrased this to highlight an exemption for restricted deployments.

@bemasc bemasc added the connect-tcp draft-ietf-httpbis-connect-tcp label Oct 21, 2024
Copy link
Contributor

@DavidSchinazi DavidSchinazi left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks!

@bemasc bemasc merged commit 70a77ca into main Oct 21, 2024
2 checks passed
@bemasc bemasc deleted the bemasc-connect-tcp-capsules branch October 21, 2024 20:46
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
connect-tcp draft-ietf-httpbis-connect-tcp
Development

Successfully merging this pull request may close these issues.

connect-tcp: should capsules be negotiated or always on?
3 participants