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

Barry Leiba's Transport Comment 3 #4560

Closed
LPardue opened this issue Jan 6, 2021 · 1 comment · Fixed by #4719
Closed

Barry Leiba's Transport Comment 3 #4560

LPardue opened this issue Jan 6, 2021 · 1 comment · Fixed by #4719
Labels
-transport iesg An issue raised during IESG review.

Comments

@LPardue
Copy link
Member

LPardue commented Jan 6, 2021

Barry Leiba said:

— Section 4 —

It is necessary to limit the amount of data that a receiver could
buffer, to prevent a fast sender from overwhelming a slow receiver,
or to prevent a malicious sender from consuming a large amount of
memory at a receiver.

You’re not talking about limiting the ability of the receiver (“could buffer”),
but limiting the potential buffering requirement on the client (“has to
buffer”), yes?

@LPardue LPardue added -transport iesg An issue raised during IESG review. labels Jan 6, 2021
@LPardue LPardue added this to the transport-iesg milestone Jan 6, 2021
@martinthomson
Copy link
Member

receiver/client is an invalid comparison here, so this is a bit of a confusing question. The point is to ensure that a receiver can limit what space it commits for buffering.

@larseggert larseggert added this to Triage in Late Stage Processing via automation Jan 11, 2021
Late Stage Processing automation moved this from Triage to Issue Handled Jan 12, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
-transport iesg An issue raised during IESG review.
Projects
Late Stage Processing
  
Issue Handled
Development

Successfully merging a pull request may close this issue.

2 participants