RFC 6108 on Comcast's Web Notification System Design
rfc-editor@rfc-editor.org Thu, 24 February 2011 00:59 UTC
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ietf-announce@core3.amsl.com
Delivered-To: ietf-announce@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id F0E993A6A14 for <ietf-announce@core3.amsl.com>; Wed, 23 Feb 2011 16:59:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.448
X-Spam-Level:
X-Spam-Status: No, score=-102.448 tagged_above=-999 required=5 tests=[AWL=0.152, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8w9cmXqHiLVJ for <ietf-announce@core3.amsl.com>; Wed, 23 Feb 2011 16:59:35 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1890:1112:1::2f]) by core3.amsl.com (Postfix) with ESMTP id F1CAC3A6968 for <ietf-announce@ietf.org>; Wed, 23 Feb 2011 16:59:34 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id 197CCE0746; Wed, 23 Feb 2011 17:00:20 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 6108 on Comcast's Web Notification System Design
From: rfc-editor@rfc-editor.org
Message-Id: <20110224010020.197CCE0746@rfc-editor.org>
Date: Wed, 23 Feb 2011 17:00:20 -0800
Cc: rfc-editor@rfc-editor.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf-announce>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 24 Feb 2011 00:59:36 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 6108
Title: Comcast's Web Notification System Design
Author: C. Chung, A. Kasyanov,
J. Livingood, N. Mody,
B. Van Lieu
Status: Informational
Stream: Independent
Date: February 2011
Mailbox: chae_chung@cable.comcast.com,
alexander_kasyanov@cable.comcast.com,
jason_livingood@cable.comcast.com,
nirmal_mody@cable.comcast.com,
brian@vanlieu.net
Pages: 24
Characters: 55329
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-livingood-web-notification-09.txt
URL: http://www.rfc-editor.org/rfc/rfc6108.txt
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.
INFORMATIONAL: This memo provides information for the Internet community.
It does not specify an Internet standard of any kind. Distribution of
this memo is unlimited.
This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
http://www.ietf.org/mailman/listinfo/ietf-announce
http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist
For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html.
For downloading RFCs, see http://www.rfc-editor.org/rfc.html.
Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org. Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.
The RFC Editor Team
Association Management Solutions, LLC