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

Packetization structure #463

Closed
martinthomson opened this issue Apr 25, 2017 · 0 comments
Closed

Packetization structure #463

martinthomson opened this issue Apr 25, 2017 · 0 comments
Labels
-transport editorial An issue that does not affect the design of the protocol; does not require consensus.

Comments

@martinthomson
Copy link
Member

We have a bunch of things in Section 9 (Packetization) that aren't very well structured: PMTUD, frame assembly into packets, retransmission, acknowledgements, etc... This could be restructured a little to make it more accessible.

@martinthomson martinthomson added editorial An issue that does not affect the design of the protocol; does not require consensus. -transport labels Apr 25, 2017
martinthomson added a commit that referenced this issue Jan 16, 2018
In line with our established principles for retransmission, I've reworked the
description of packetization.  The description now concentrates on the
information that is being repaired in response to perceived loss.  This should
help avoid the confusion about retransmission.

Two new subsections are added to the packetization section.  One covers the
processing of packets and includes the existing text on processing requirements
before acknowledgment.  The other includes the retransmission logic.

The retransmission section still mentions frame types, but I've tried to make
that secondary to the description of the information that is being repaired.

I also removed mention of "Regular QUIC packets", which only occurred in 3
places.

Closes #463, #765.
martinthomson added a commit that referenced this issue Jan 16, 2018
In line with our established principles for retransmission, I've reworked the
description of packetization.  The description now concentrates on the
information that is being repaired in response to perceived loss.  This should
help avoid the confusion about retransmission.

Two new subsections are added to the packetization section.  One covers the
processing of packets and includes the existing text on processing requirements
before acknowledgment.  The other includes the retransmission logic.

The retransmission section still mentions frame types, but I've tried to make
that secondary to the description of the information that is being repaired.

I also removed mention of "Regular QUIC packets", which only occurred in 3
places.

Closes #463, #765.
martinthomson added a commit that referenced this issue Feb 13, 2018
In line with our established principles for retransmission, I've reworked the
description of packetization.  The description now concentrates on the
information that is being repaired in response to perceived loss.  This should
help avoid the confusion about retransmission.

Two new subsections are added to the packetization section.  One covers the
processing of packets and includes the existing text on processing requirements
before acknowledgment.  The other includes the retransmission logic.

The retransmission section still mentions frame types, but I've tried to make
that secondary to the description of the information that is being repaired.

I also removed mention of "Regular QUIC packets", which only occurred in 3
places.

Closes #463, #765.
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
None yet
Development

No branches or pull requests

1 participant