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

Define requirements for handling packets #724

Merged
merged 10 commits into from Oct 13, 2017
Merged

Define requirements for handling packets #724

Changes from 1 commit
Commits
Show all changes
10 commits
Select commit Hold shift + click to select a range
7e5281b
Define requirements for handling packets
martinthomson Aug 11, 2017
de2821f
Review comments
martinthomson Aug 21, 2017
0d0f98d
Capitalize Client Initial
martinthomson Oct 9, 2017
a9c6512
Expand more on the need for bufferring
martinthomson Oct 9, 2017
39ea0bb
Allow a stateless reset in addition to discard
martinthomson Oct 10, 2017
cec3573
Allow consumption of VN in response to 0-RTT
martinthomson Oct 10, 2017
9d7cdb1
Add forward ref to packetization section
martinthomson Oct 11, 2017
e5fb23b
Jana's comments
martinthomson Oct 12, 2017
aa50d14
Downgrade discard requirement to MAY prior to handshake
martinthomson Oct 12, 2017
d816e03
Remove text
martinthomson Oct 12, 2017
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
9 changes: 4 additions & 5 deletions draft-ietf-quic-transport.md
View file
Open in desktop
Expand Up @@ -910,11 +910,10 @@ diagnostic or security purposes.
For servers, packets that aren't associated with a connection potentially create
Copy link
Contributor

Choose a reason for hiding this comment

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

nit: What about "aren't associated with an existing connection"

Copy link
Member Author

Choose a reason for hiding this comment

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

I was trying to save words here. I figured that this was used enough to be implicit by now.

a new connection. However, only packets that use the long packet header and
that are at least the minimum size defined for the protocol version can be
initial packets. Unless the server is buffering 0-RTT packets, a server MAY
discard packets with a short header or packets that are smaller than the
smallest minimum size for any version that the server supports. A server that
discards a packet that cannot be associated with a connection MAY also generate
a stateless reset ({{stateless-reset}}).
initial packets. A server MAY discard packets with a short header or packets
that are smaller than the smallest minimum size for any version that the server
supports. A server that discards a packet that cannot be associated with a
connection MAY also generate a stateless reset ({{stateless-reset}}).

This version of QUIC defines a minimum size for initial packets of 1200 octets
(see {{packetization}}). Versions of QUIC that define smaller minimum initial
Expand Down