RFC 6057: Comcast's Protocol-Agnostic Congestion Management System
In plain English — editorial summary, not part of the RFC
This document describes the congestion management system of Comcast Cable, a large cable broadband Internet Service Provider (ISP) in the U.S. Comcast completed deployment of this congestion management system on December 31, 2008. This document is not an Internet Standards Track specification; it is published for informational purposes.
Document record
- Document ID
- RFC6057
- Published
- December 2010
- Authors
- C. Bastian; T. Klieber; J. Livingood; J. Mills; R. Woundy
- Status
- HISTORIC
- Stream
- IETF
- Area
- —
- Pages
- 29
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 5632Comcast's ISP Experiences in a Proactive Network Provider Participation for P2P (P4P) Technical TrialCurrent
September 2009
- RFC 6561Recommendations for the Remediation of Bots in ISP NetworksCurrent
March 2012
- RFC 7646Definition and Use of DNSSEC Negative Trust AnchorsCurrent
September 2015
- RFC 3750Unmanaged Networks IPv6 Transition ScenariosCurrent
April 2004
- RFC 3704Ingress Filtering for Multihomed NetworksUpdated
March 2004
- RFC 2827Network Ingress Filtering: Defeating Denial of Service Attacks which employ IP Source Address SpoofingUpdated
May 2000
- RFC 6108Comcast's Web Notification System DesignCurrent
February 2011
- RFC 6065Using Authentication, Authorization, and Accounting Services to Dynamically Provision View-Based Access Control Model User-to-Group MappingsCurrent
December 2010
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?