Skip to content

Update congestion-control-charter.md #40

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

Open
zaheduzzaman wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Update congestion-control-charter.md #40

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions congestion-control-charter.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -4,9 +4,9 @@ RFC 5033 describes a Best Current Practice to evaluate new congestion control al

Since RFC 5033 was published, many conditions have changed. Congestion control algorithm proponents now often have the opportunity to test and deploy at scale without IETF review. The set of protocols using these algorithms has spread beyond TCP and SCTP to include DCCP, QUIC, and beyond. There is more interest in specialized use cases such as data centers and real-time protocols. Finally, the community has gained much more experience with indications of congestion beyond packet loss.

The Congestion Control Working Group will review some of the impediments to congestion control work occurring in the IETF and can generalize transports from TCP to all of the relevant transport protocols. This will inform a revision of RFC 5033 (5033bis) that encourages IETF review of congestion control proposals and standardization of mature congestion control algorithms.
The Congestion Control Working Group will analyze some of the impediments to congestion control work occurring in the IETF and can generalize transports from TCP to all of the relevant transport protocols. This will inform a revision of RFC 5033 (5033bis) that encourages IETF review of congestion control proposals and standardization of mature congestion control algorithms.

The congestion control expertise in the working group also makes it a natural venue to take on other work related to indications of congestion such as delay, queuing algorithms, rate pacing, multipath, interaction with other layers, among others. In particular, it can address congestion control algorithms with empirical evidence of safety and stated intent to deploy by major implementations. The working group is intended to be a home for such work, and it is chartered to adopt proposals in this space if such congestion control algorithms are presented before or after the completion of the primary deliverable i.e. 5033bis.
The congestion control expertise in the working group also makes it a natural venue to take on other work related to indications of congestion such as delay, queuing algorithms, rate pacing, multipath, interaction with other layers, among others. In particular, it can address congestion control algorithms with empirical evidence of safety (for example - avoiding congestion collapse) and stated intent to deploy by major implementations. The working group is intended to be a home for such work, and it is chartered to adopt proposals in this space if such congestion control algorithms are presented before or after the completion of the primary deliverable i.e. 5033bis.

The group will coordinate closely with other relevant working and research groups, including ICCRG, TCPM, QUIC, and TSVWG. Documents in CCWG will remain as transport protocol agnostic as possible, but they may have short specific instructions, such as header options or parameter formats, for one or more protocols. Documents that are wholly specific to mechanisms in a single protocol will remain in the maintenance working group for that protocol. Algorithms proposed for Experimental status, in consultation with ICCRG, based on an assessment of their maturity and likelihood of near-term wide-scale deployment, are in scope.

Expand Down