From owner-rtfm@auckland.ac.nz Thu Jun 22 14:32:45 2000 Received: from mailhost.auckland.ac.nz (mailhost.auckland.ac.nz [130.216.1.4]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA12520 for ; Thu, 22 Jun 2000 14:32:42 -0400 (EDT) Received: (from majordom@localhost) by mailhost.auckland.ac.nz (8.9.2/8.9.2/8.9.2-ua) id FAA15889; Fri, 23 Jun 2000 05:09:11 +1200 (NZST) Received: from caida.org (ipn.caida.org [192.172.226.30]) by mailhost.auckland.ac.nz (8.9.2/8.9.2/8.9.2-ua) with ESMTP id FAA15882 for ; Fri, 23 Jun 2000 05:09:07 +1200 (NZST) Received: from localhost (nevil@localhost) by caida.org (8.8.8/8.7.3) with ESMTP id KAA27233; Thu, 22 Jun 2000 10:09:02 -0700 (PDT) Date: Thu, 22 Jun 2000 10:09:02 -0700 (PDT) From: Nevil Brownlee To: Scott Bradner , Allison Mankin cc: rtfm@auckland.ac.nz Subject: RTFM at Pittsburg IETF Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-rtfm@auckland.ac.nz Precedence: bulk Hello Scott & Allison: Over the last few months there has been discussion on the RTFM mailing list about reviving the WG to pursue two goals: a) Develop a standard method (protocol, API, whatever) for changing rulests in an RTFM meter 'on the fly,' i.e. while they are running (e.g. to add/delete networks from a list of networks for which flow data is being collected). b) Review the 'New Attributes' RFC (2274) so as to decide which of these turn out to be really useful, and produce an 'RTFM Meter extensions' RFC so as to allow standardised implementation for them. I'd appreciate your guidance as to the best way to do this. In particular, can we simply revive the existing RTFM WG with a revised charter, do we need to run a BOF so as to start a new WG, or what? Cheers, Nevil ------------------------------------------------------------- Nevil Brownlee Visiting Researcher Phone: (858) 822 0893 CAIDA, San Diego