-
Notifications
You must be signed in to change notification settings - Fork 204
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
Minor mods to stream state machine text #988
Conversation
draft-ietf-quic-transport.md
Outdated
"open" when either send or receive stream is in a non-terminal state and | ||
"closed" when both send and receive streams are in a terminal state. | ||
Implementations might represent the state of the bidirectional stream as a | ||
composite of the states of the constituent send and receive streams. The |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nits:
I a prefer lower case 'may' to 'might' in the line above.
Should it states be plural?
I think constituent is unnecessary
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
done
containing a previous STOP_SENDING is lost. However, once either all stream | ||
data or a RST_STREAM frame has been received for the stream - that is, the | ||
stream is in any state other than "Recv" or "Size Known" - sending a | ||
STOP_SENDING frame is unnecessary. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Above you changed it so it's SHOULD. Should it be changed here as well?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think of this as justification for why it's a SHOULD above, so I'd prefer to leave this text as is.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
SHOULD doesn't make sense here.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks Ian, comments addressed.
draft-ietf-quic-transport.md
Outdated
"open" when either send or receive stream is in a non-terminal state and | ||
"closed" when both send and receive streams are in a terminal state. | ||
Implementations might represent the state of the bidirectional stream as a | ||
composite of the states of the constituent send and receive streams. The |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
done
containing a previous STOP_SENDING is lost. However, once either all stream | ||
data or a RST_STREAM frame has been received for the stream - that is, the | ||
stream is in any state other than "Recv" or "Size Known" - sending a | ||
STOP_SENDING frame is unnecessary. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think of this as justification for why it's a SHOULD above, so I'd prefer to leave this text as is.
Some rewording and added one normative.