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

Here be dragons #3421

Merged
merged 2 commits into from Feb 11, 2020
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
6 changes: 6 additions & 0 deletions draft-ietf-quic-transport.md
Expand Up @@ -5710,6 +5710,12 @@ that a peer is able to understand the frame. An endpoint can use a transport
parameter to signal its willingness to receive one or more extension frame types
with the one transport parameter.

Extensions that modify or replace core protocol functionality (including frame
Copy link
Member

Choose a reason for hiding this comment

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

do we want to be specific about this version?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

We don't yet know about the portability of extensions across versions. I'm kind of inclined to just leave that topic for future-us.

Copy link
Contributor

Choose a reason for hiding this comment

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

+1, this document only discusses this version. Any other version is future work

Copy link
Member

Choose a reason for hiding this comment

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

Makes sense, I agree.

types) will be difficult to combine with other extensions which modify or
replace the same functionality unless the behavior of the combination is
explicitly defined. Such extensions SHOULD define their interaction with
previously-defined extensions modifying the same protocol components.

Extension frames MUST be congestion controlled and MUST cause an ACK frame to
be sent. The exception is extension frames that replace or supplement the ACK
frame. Extension frames are not included in flow control unless specified
Expand Down