From cs594ir-admin@cs.utk.edu Thu May 1 05:08:11 2003 Received: from klutz.cs.utk.edu (klutz.cs.utk.edu [160.36.56.50]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA03227 for ; Thu, 1 May 2003 05:08:11 -0400 (EDT) Received: from localhost (localhost [127.0.0.1]) by smtp.cs.utk.edu (Postfix) with ESMTP id 33DA014235 for ; Thu, 1 May 2003 05:10:33 -0400 (EDT) Received: from klutz.cs.utk.edu ([127.0.0.1]) by localhost (klutz [127.0.0.1:10024]) (amavisd-new) with ESMTP id 11232-09 for ; Thu, 1 May 2003 05:10:32 -0400 (EDT) Received: from klutz.cs.utk.edu (localhost [127.0.0.1]) by smtp.cs.utk.edu (Postfix) with ESMTP id 62683141F3 for ; Thu, 1 May 2003 05:10:32 -0400 (EDT) Date: Thu, 01 May 2003 05:10:32 -0400 Message-ID: <20030501091032.1979.62646.Mailman@klutz.cs.utk.edu> Subject: cs.utk.edu mailing list memberships reminder From: mailman-owner@cs.utk.edu To: wrec-archive@ietf.org X-No-Archive: yes X-Ack: no Sender: cs594ir-admin@cs.utk.edu Errors-To: cs594ir-admin@cs.utk.edu X-BeenThere: cs594ir@klutz.cs.utk.edu X-Mailman-Version: 2.0.13 Precedence: bulk X-Virus-Scanned: by amavisd-new and ClamAntivirus This is a reminder, sent out once a month, about your cs.utk.edu mailing list memberships. It includes your subscription info and how to use it to change it or unsubscribe from a list. You can visit the URLs to change your membership status or configuration, including unsubscribing, setting digest-style delivery or disabling delivery altogether (e.g., for a vacation), and so on. In addition to the URL interfaces, you can also use email to make such changes. For more info, send a message to the '-request' address of the list (for example, wrec-request@cs.utk.edu) containing just the word 'help' in the message body, and an email message will be sent to you with instructions. If you have questions, problems, comments, etc, send them to mailman-owner@klutz.cs.utk.edu. Thanks! Passwords for wrec-archive@lists.ietf.org: List Password // URL ---- -------- wrec@cs.utk.edu enifbo http://klutz.cs.utk.edu/options/wrec/wrec-archive%40lists.ietf.org From wrec-admin@cs.utk.edu Thu May 8 12:56:07 2003 Received: from klutz.cs.utk.edu (klutz.cs.utk.edu [160.36.56.50]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA00023 for ; Thu, 8 May 2003 12:56:07 -0400 (EDT) Received: from localhost (localhost [127.0.0.1]) by smtp.cs.utk.edu (Postfix) with ESMTP id 88DBF14214; Thu, 8 May 2003 12:59:01 -0400 (EDT) Received: from klutz.cs.utk.edu ([127.0.0.1]) by localhost (klutz [127.0.0.1:10024]) (amavisd-new) with ESMTP id 28869-05; Thu, 8 May 2003 12:59:00 -0400 (EDT) Received: from klutz.cs.utk.edu (localhost [127.0.0.1]) by smtp.cs.utk.edu (Postfix) with ESMTP id 3C9361420B; Thu, 8 May 2003 12:59:00 -0400 (EDT) Received: from localhost (localhost [127.0.0.1]) by smtp.cs.utk.edu (Postfix) with ESMTP id 0CAD814128 for ; Thu, 8 May 2003 00:36:25 -0400 (EDT) Received: from klutz.cs.utk.edu ([127.0.0.1]) by localhost (klutz [127.0.0.1:10024]) (amavisd-new) with ESMTP id 00307-10 for ; Thu, 8 May 2003 00:36:24 -0400 (EDT) Received: from mail.mnot.net (adsl-67-119-69-242.dsl.sntc01.pacbell.net [67.119.69.242]) by smtp.cs.utk.edu (Postfix) with ESMTP id 68859140A2 for ; Thu, 8 May 2003 00:36:24 -0400 (EDT) Received: from mnot.net (adsl-67-119-69-246.dsl.sntc01.pacbell.net [67.119.69.246]) (using TLSv1 with cipher DES-CBC3-SHA (168/168 bits)) (No client certificate requested) by mail.mnot.net (Postfix) with ESMTP id 0853372BD; Wed, 7 May 2003 21:36:22 -0700 (PDT) Subject: RSS traces Content-Type: text/plain; charset=US-ASCII; format=flowed Mime-Version: 1.0 (Apple Message framework v552) Cc: wrec@cs.utk.edu To: ietf-http-wg@w3.org From: Mark Nottingham Content-Transfer-Encoding: 7bit Message-Id: <9DB30446-810E-11D7-82FF-000A27836A68@mnot.net> X-Mailer: Apple Mail (2.552) X-Virus-Scanned: by amavisd-new and ClamAntivirus Sender: wrec-admin@cs.utk.edu Errors-To: wrec-admin@cs.utk.edu X-BeenThere: wrec@cs.utk.edu X-Mailman-Version: 2.0.13 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: List-Unsubscribe: , List-Archive: Date: Wed, 7 May 2003 21:36:20 -0700 X-Virus-Scanned: by amavisd-new and ClamAntivirus Content-Transfer-Encoding: 7bit I'm slowly building a collection of traces for access to a relatively new kind of Web content - RSS feeds. If you're not familiar with it, RSS is a format that represents a list of items, each with its own title, description, link, and other metadata. Clients (often called "aggregators") periodically poll to build a view of the channel over time, adding new items in the representation to a local store. In this manner, one can keep abreast of news headlines and other chronologically-ordered lists. This format is becoming more popular, both because of increasing support (sites like MSDN, the New York Times and CNN all have RSS feeds) and the arrival of "weblogs" (which also uses RSS). There are a number of interesting questions about RSS that come to mind, including; - what is the polling interval? - how common is validation? - what is the rate of change for the RSS? - what is the size of the feed? - what times of day does polling happen? - how self-similar is RSS traffic (is is "lumpy" around the top of the hour, for example?) I suspect that RSS, because it is polled, is not at all typical Web traffic, and therefore places unusual requirements on Web servers and intermediaries. I also suspect that it may eventually require us to rethink distribution; invalidation and other approaches may become much more desirable, as opposed to polling. Rather than keep all of the fun for myself (I have a day job), I've placed the traces on the Web for the greater enjoyment of the caching and traffic characterization community ;) They are at: http://www.mnot.net/rss/traces/ (this will redirect to another site; please bookmark the URI above, in case it changes). So far, I have one trace; it has been anonymized (combined log format with the client IP, ident, userinfo, URI, referer and user-agent fields hashed or half-hashed). If there is another format that's more suitable, please tell me. This trace contains about 500,000 entries and represents a week's worth of access to a RSS "scraping" service; i.e., it's a Web site that processes other Web sites to produce a number of feeds. As such, it contains accesses to multiple feeds. Please tell me if this is interesting/useful, and send along any results you come up with. I'm working on getting more traces; stay tuned (are any of the repositories - e.g., W3C WCA, Internet Traffic Archive - still active? Neither has seen anything new in quite some time...). Regards, From wrec-admin@cs.utk.edu Thu May 8 14:11:06 2003 Received: from klutz.cs.utk.edu (klutz.cs.utk.edu [160.36.56.50]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA02148 for ; Thu, 8 May 2003 14:11:05 -0400 (EDT) Received: from localhost (localhost [127.0.0.1]) by smtp.cs.utk.edu (Postfix) with ESMTP id 07B8C140A5; Thu, 8 May 2003 14:14:02 -0400 (EDT) Received: from klutz.cs.utk.edu ([127.0.0.1]) by localhost (klutz [127.0.0.1:10024]) (amavisd-new) with ESMTP id 05590-07; Thu, 8 May 2003 14:14:01 -0400 (EDT) Received: from klutz.cs.utk.edu (localhost [127.0.0.1]) by smtp.cs.utk.edu (Postfix) with ESMTP id 07CF21408A; Thu, 8 May 2003 14:14:01 -0400 (EDT) Received: from localhost (localhost [127.0.0.1]) by smtp.cs.utk.edu (Postfix) with ESMTP id 0CAD814128 for ; Thu, 8 May 2003 00:36:25 -0400 (EDT) Received: from klutz.cs.utk.edu ([127.0.0.1]) by localhost (klutz [127.0.0.1:10024]) (amavisd-new) with ESMTP id 00307-10 for ; Thu, 8 May 2003 00:36:24 -0400 (EDT) Received: from mail.mnot.net (adsl-67-119-69-242.dsl.sntc01.pacbell.net [67.119.69.242]) by smtp.cs.utk.edu (Postfix) with ESMTP id 68859140A2 for ; Thu, 8 May 2003 00:36:24 -0400 (EDT) Received: from mnot.net (adsl-67-119-69-246.dsl.sntc01.pacbell.net [67.119.69.246]) (using TLSv1 with cipher DES-CBC3-SHA (168/168 bits)) (No client certificate requested) by mail.mnot.net (Postfix) with ESMTP id 0853372BD; Wed, 7 May 2003 21:36:22 -0700 (PDT) Subject: RSS traces Content-Type: text/plain; charset=US-ASCII; format=flowed Mime-Version: 1.0 (Apple Message framework v552) Cc: wrec@cs.utk.edu To: ietf-http-wg@w3.org From: Mark Nottingham Content-Transfer-Encoding: 7bit Message-Id: <9DB30446-810E-11D7-82FF-000A27836A68@mnot.net> X-Mailer: Apple Mail (2.552) X-Virus-Scanned: by amavisd-new and ClamAntivirus Sender: wrec-admin@cs.utk.edu Errors-To: wrec-admin@cs.utk.edu X-BeenThere: wrec@cs.utk.edu X-Mailman-Version: 2.0.13 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: List-Unsubscribe: , List-Archive: Date: Wed, 7 May 2003 21:36:20 -0700 X-Virus-Scanned: by amavisd-new and ClamAntivirus Content-Transfer-Encoding: 7bit I'm slowly building a collection of traces for access to a relatively new kind of Web content - RSS feeds. If you're not familiar with it, RSS is a format that represents a list of items, each with its own title, description, link, and other metadata. Clients (often called "aggregators") periodically poll to build a view of the channel over time, adding new items in the representation to a local store. In this manner, one can keep abreast of news headlines and other chronologically-ordered lists. This format is becoming more popular, both because of increasing support (sites like MSDN, the New York Times and CNN all have RSS feeds) and the arrival of "weblogs" (which also uses RSS). There are a number of interesting questions about RSS that come to mind, including; - what is the polling interval? - how common is validation? - what is the rate of change for the RSS? - what is the size of the feed? - what times of day does polling happen? - how self-similar is RSS traffic (is is "lumpy" around the top of the hour, for example?) I suspect that RSS, because it is polled, is not at all typical Web traffic, and therefore places unusual requirements on Web servers and intermediaries. I also suspect that it may eventually require us to rethink distribution; invalidation and other approaches may become much more desirable, as opposed to polling. Rather than keep all of the fun for myself (I have a day job), I've placed the traces on the Web for the greater enjoyment of the caching and traffic characterization community ;) They are at: http://www.mnot.net/rss/traces/ (this will redirect to another site; please bookmark the URI above, in case it changes). So far, I have one trace; it has been anonymized (combined log format with the client IP, ident, userinfo, URI, referer and user-agent fields hashed or half-hashed). If there is another format that's more suitable, please tell me. This trace contains about 500,000 entries and represents a week's worth of access to a RSS "scraping" service; i.e., it's a Web site that processes other Web sites to produce a number of feeds. As such, it contains accesses to multiple feeds. Please tell me if this is interesting/useful, and send along any results you come up with. I'm working on getting more traces; stay tuned (are any of the repositories - e.g., W3C WCA, Internet Traffic Archive - still active? Neither has seen anything new in quite some time...). Regards,