RFC 6108: Comcast's Web Notification System Design
In plain English — editorial summary, not part of the RFC
The objective of this document is to describe a method of providing critical end-user notifications to web browsers, which has been deployed by Comcast, an Internet Service Provider (ISP). Such a notification system is being used to provide near-immediate notifications to customers, such as to warn them that their traffic exhibits patterns that are indicative of malware or virus infection. There are other proprietary systems that can perform such notifications, but those systems utilize Deep Packet Inspection (DPI) technology. In contrast to DPI, this document describes a system that does not rely upon DPI, and is instead based in open IETF standards and open source applications. This document is not an Internet Standards Track specification; it is published for informational purposes.
Document record
- Document ID
- RFC6108
- Published
- February 2011
- Authors
- C. Chung; A. Kasyanov; J. Livingood; N. Mody; B. Van Lieu
- Status
- HISTORIC
- Stream
- INDEPENDENT
- Area
- —
- Pages
- 24
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 6057Comcast's Protocol-Agnostic Congestion Management SystemCurrent
December 2010
- RFC 6561Recommendations for the Remediation of Bots in ISP NetworksCurrent
March 2012
- RFC 5632Comcast's ISP Experiences in a Proactive Network Provider Participation for P2P (P4P) Technical TrialCurrent
September 2009
- 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 6036Emerging Service Provider Scenarios for IPv6 DeploymentObsoleted
October 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?