From roy26@prodigy.com Wed Jun 3 19:52:56 1998 Return-Path: Received: from almond.bmc.com (mail-gw1.bmc.com [198.64.253.22]) by amethyst.bmc.com (8.8.8/8.8.8) with ESMTP id TAA27407 for ; Wed, 3 Jun 1998 19:52:55 -0500 (CDT) From: roy26@prodigy.com Received: (from uucp@localhost) by almond.bmc.com (8.8.8/8.8.8) id TAA19157 for ; Wed, 3 Jun 1998 19:52:54 -0500 (CDT) Received: from firewall.bmc.com(192.245.162.250) by almond.bmc.com via smap (V2.0) id xma018411; Wed, 3 Jun 98 19:51:06 -0500 Received: (from uucp@localhost) by dresden.bmc.com (8.8.5/8.8.6) id TAA17930 for ; Wed, 3 Jun 1998 19:50:28 -0500 (CDT) Received: from tangelo.bmc.com(172.17.7.166) by dresden.bmc.com via smap (3.2) id xma017226; Wed, 3 Jun 98 19:49:43 -0500 Received: from dorothy.peer.com (dorothy.peer.com [192.146.153.65]) by tangelo.bmc.com (8.8.6 (PHNE_14041)/8.8.6) with ESMTP id TAA18210; Wed, 3 Jun 1998 19:50:10 -0500 (CDT) Received: from cashew.bmc.com (cashew.bmc.com [172.19.0.100]) by dorothy.peer.com (8.8.6 (PHNE_12836)/8.8.6) with ESMTP id RAA24363 for ; Wed, 3 Jun 1998 17:43:39 -0700 (PDT) Received: (from uucp@localhost) by cashew.bmc.com (8.8.8/8.8.8) id TAA01460 for ; Wed, 3 Jun 1998 19:43:38 -0500 (CDT) Received: from mail.tin.it(194.243.154.49) by cashew.bmc.com via smap (V2.0) id xma001448; Wed, 3 Jun 98 19:43:31 -0500 Received: from mail.tin.it (161.baltimore-02.md.dial-access.att.net [12.68.115.161]) by mail.tol.it (8.8.4/8.8.4) with SMTP id CAA08847; Thu, 4 Jun 1998 02:42:50 +0200 (MET DST) Date: Wed, 03 Jun 98 20:33:17 EST To: andy@megahardcore.com Subject: Awesome! Message-ID: <199805190417.AAA07146@rly-zb04.mx.aol.com> Reply-To: andy@megahardcore.com ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ This is intended for adults. If you are under 18, or viewing these materials is illegal where you live, please delete this now. ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ AWESOME! http://www.pornsitez.com/hardcore/xxxmovies/ ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ From mdb@server.marketingstrats.com Thu Jun 4 23:02:27 1998 Return-Path: Received: from almond.bmc.com (mail-gw1.bmc.com [198.64.253.22]) by amethyst.bmc.com (8.8.8/8.8.8) with ESMTP id XAA09836 for ; Thu, 4 Jun 1998 23:02:26 -0500 (CDT) Received: (from uucp@localhost) by almond.bmc.com (8.8.8/8.8.8) id XAA28394 for ; Thu, 4 Jun 1998 23:02:25 -0500 (CDT) Received: from firewall.bmc.com(192.245.162.250) by almond.bmc.com via smap (V2.0) id xma028000; Thu, 4 Jun 98 23:01:10 -0500 Received: (from uucp@localhost) by dresden.bmc.com (8.8.5/8.8.6) id XAA12496 for ; Thu, 4 Jun 1998 23:00:41 -0500 (CDT) Received: from tangelo.bmc.com(172.17.7.166) by dresden.bmc.com via smap (3.2) id xma012279; Thu, 4 Jun 98 23:00:13 -0500 Received: from dorothy.peer.com (dorothy.peer.com [192.146.153.65]) by tangelo.bmc.com (8.8.6 (PHNE_14041)/8.8.6) with ESMTP id XAA04666; Thu, 4 Jun 1998 23:00:36 -0500 (CDT) Received: from cashew.bmc.com (cashew.bmc.com [172.19.0.100]) by dorothy.peer.com (8.8.6 (PHNE_12836)/8.8.6) with ESMTP id UAA14498 for ; Thu, 4 Jun 1998 20:48:13 -0700 (PDT) Received: (from uucp@localhost) by cashew.bmc.com (8.8.8/8.8.8) id WAA15073 for ; Thu, 4 Jun 1998 22:48:11 -0500 (CDT) Received: from gauntlet.fv.com(207.67.199.118) by cashew.bmc.com via smap (V2.0) id xma015066; Thu, 4 Jun 98 22:48:07 -0500 Received: from shekel.fv.com (shekel.fv.com [207.67.199.130]) by gauntlet.fv.com (8.9.0/8.9.0) with ESMTP id UAA09653 for ; Thu, 4 Jun 1998 20:48:06 -0700 (PDT) Received: from gauntlet.fv.com (gauntlet-in.fv.com [10.0.0.2]) by shekel.fv.com (8.8.8/8.8.8) with ESMTP id UAA12163 for ; Thu, 4 Jun 1998 20:47:35 -0700 (PDT) Received: from server.marketingstrats.com ([208.18.192.30]) by gauntlet.fv.com (8.9.0/8.9.0) with ESMTP id UAA09643 for ; Thu, 4 Jun 1998 20:47:39 -0700 (PDT) Received: from DEFAULT (dialup-1.grb.earthreach.com [208.18.209.175]) by server.marketingstrats.com (8.8.7/8.8.7) with SMTP id WAA25434; Thu, 4 Jun 1998 22:45:19 -0500 Date: Thu, 4 Jun 1998 22:45:19 -0500 To: mdb@server.marketingstrats.com From: mdb@server.marketingstrats.com (Bass) Comments: Authenticated sender is Reply-to: mdb@server.marketingstrats.com Subject: from Donald Bass Message-Id: <199806041215SAA53242@post.marketingstrats.com> ***************************************************************************** This message is sent in compliance of the new e-mail bill:SECTION 301. Sender:Donald Bass,2482 garden hts ct.,greenbay,wi.ph:920-468-7910. email:mdb@marketingstrats.com. "Per Section 301, Paragraph (a)(2)(C) of S. 1618, further transmissions to you by the sender of this email may be stopped at no cost to you by sending a reply to this email address with the word "remove" in the subject line." ****************************************************************************** Greetings, I just read your posting online and was wondering if I could send you a free copy of an article I wrote called " THE TWO SECRET STRATEGIES FOR MARKETING ONLINE". Just e-mail me back and type "SEND" in the subject line for a free copy. Thank you, Donald Bass From rpresuhn@dorothy.peer.com Fri Jun 5 16:33:29 1998 Return-Path: Received: from almond.bmc.com (mail-gw1.bmc.com [198.64.253.22]) by amethyst.bmc.com (8.8.8/8.8.8) with ESMTP id QAA17766 for ; Fri, 5 Jun 1998 16:33:28 -0500 (CDT) Received: (from uucp@localhost) by almond.bmc.com (8.8.8/8.8.8) id QAA17683 for ; Fri, 5 Jun 1998 16:33:27 -0500 (CDT) Received: from firewall.bmc.com(192.245.162.250) by almond.bmc.com via smap (V2.0) id xma017078; Fri, 5 Jun 98 16:31:29 -0500 Received: (from uucp@localhost) by dresden.bmc.com (8.8.5/8.8.6) id QAA29196 for ; Fri, 5 Jun 1998 16:30:52 -0500 (CDT) Received: from tangelo.bmc.com(172.17.7.166) by dresden.bmc.com via smap (3.2) id xma028524; Fri, 5 Jun 98 16:30:21 -0500 Received: from dorothy.peer.com (dorothy.peer.com [192.146.153.65]) by tangelo.bmc.com (8.8.6 (PHNE_14041)/8.8.6) with ESMTP id QAA22209; Fri, 5 Jun 1998 16:30:48 -0500 (CDT) Received: (from rpresuhn@localhost) by dorothy.peer.com (8.8.6 (PHNE_12836)/8.8.6) id OAA02604 for agentx@peer.com; Fri, 5 Jun 1998 14:26:17 -0700 (PDT) Date: Fri, 5 Jun 1998 14:26:17 -0700 (PDT) From: Randy Presuhn Message-Id: <199806052126.OAA02604@dorothy.peer.com> To: agentx@peer.com Subject: reducing agentx spam Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Hi - I've noticed that most of the spam directed at the agentx list is being passed by way of the old address. Is there any need to keep that old address alive? It was a valuable service during the transition period, but I think it has become a liability. ----------------------------------------------------------------------- Randy Presuhn Email: rpresuhn@bmc.com http://www.bmc.com Voice: +1 408 616-3100 BMC Software, Inc. 965 Stewart Drive Fax: +1 408 616-3101 Sunnyvale, California 94086 USA ----------------------------------------------------------------------- In accordance with the BMC Communications Systems Use and Security Policy, I explicitly state that although my affiliation with BMC may be apparent, implied, or provided, my opinions are not necessarily those of BMC Software and that all external representations on behalf of BMC must first be cleared with a member of "the top management team." ----------------------------------------------------------------------- From bnatale@acecomm.com Fri Jun 5 16:49:28 1998 Return-Path: Received: from almond.bmc.com (mail-gw1.bmc.com [198.64.253.22]) by amethyst.bmc.com (8.8.8/8.8.8) with ESMTP id QAA17890 for ; Fri, 5 Jun 1998 16:49:18 -0500 (CDT) Received: (from uucp@localhost) by almond.bmc.com (8.8.8/8.8.8) id QAA19481 for ; Fri, 5 Jun 1998 16:49:17 -0500 (CDT) Received: from firewall.bmc.com(192.245.162.250) by almond.bmc.com via smap (V2.0) id xma019062; Fri, 5 Jun 98 16:48:05 -0500 Received: (from uucp@localhost) by dresden.bmc.com (8.8.5/8.8.6) id QAA14045 for ; Fri, 5 Jun 1998 16:47:33 -0500 (CDT) Received: from tangelo.bmc.com(172.17.7.166) by dresden.bmc.com via smap (3.2) id xma013000; Fri, 5 Jun 98 16:46:47 -0500 Received: from dorothy.peer.com (dorothy.peer.com [192.146.153.65]) by tangelo.bmc.com (8.8.6 (PHNE_14041)/8.8.6) with ESMTP id QAA24293; Fri, 5 Jun 1998 16:47:13 -0500 (CDT) Received: from almond.bmc.com (almond.bmc.com [172.17.0.100]) by dorothy.peer.com (8.8.6 (PHNE_12836)/8.8.6) with ESMTP id OAA04007; Fri, 5 Jun 1998 14:46:20 -0700 (PDT) Received: (from uucp@localhost) by almond.bmc.com (8.8.8/8.8.8) id QAA18666; Fri, 5 Jun 1998 16:46:19 -0500 (CDT) Received: from relay1.smtp.psi.net(38.8.14.2) by almond.bmc.com via smap (V2.0) id xma018635; Fri, 5 Jun 98 16:45:58 -0500 Received: from [192.152.208.5] (helo=acecomm.com) by relay1.smtp.psi.net with smtp (Exim 1.90 #1) id 0yi4IT-00073D-00; Fri, 5 Jun 1998 17:45:15 -0400 Received: from bnatale by acecomm.com (5.65/3.2.083191-ACE*COMM) id AA08543; Fri, 5 Jun 1998 17:47:36 -0400 Message-Id: <3.0.5.32.19980605174650.009c0340@nips.acec.com> X-Sender: natale@nips.acec.com X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.5 (32) Date: Fri, 05 Jun 1998 17:46:50 -0400 To: Randy Presuhn From: Bob Natale Subject: Re: reducing agentx spam Cc: agentx@peer.com In-Reply-To: <199806052126.OAA02604@dorothy.peer.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" >At 02:26 PM 6/5/98 -0700, you wrote: Hi Randy, >I've noticed that most of the spam directed at the agentx list is >being passed by way of the old address. Is there >any need to keep that old address alive? It was a valuable service >during the transition period, but I think it has become a liability. Agreed. Btw, everyone, *I've* got to kick things back into gear here... we need to get organized wrt the up-coming bake-off...I've got a revised charter to post for your comment (I'm just factoring in some recent comments from Bert now)...and get the "to do" list in shape...all my fault...been very busy with business and family matters, but starting to see some daylight now. Until then...have a good weekend! Cordially, BobN ------------ ISO 9001 Registered Quality Supplier ----------- Bob Natale | ACE*COMM | 301-721-3000 [v] Dir, Net Mgmt Prod | 704 Quince Orchard Rd | 301-721-3001 [f] bnatale@acecomm.com| Gaithersburg MD 20878 | www.acecomm.com ------------- Free downloads at www.winsnmp.com ------------- From kadeu28@demeter.psych.uw.edu.pl Sun Jun 7 02:03:35 1998 Return-Path: Received: from almond.bmc.com (mail-gw1.bmc.com [198.64.253.22]) by amethyst.bmc.com (8.8.8/8.8.8) with ESMTP id CAA00682 for ; Sun, 7 Jun 1998 02:03:34 -0500 (CDT) Received: (from uucp@localhost) by almond.bmc.com (8.8.8/8.8.8) id CAA08688 for ; Sun, 7 Jun 1998 02:03:33 -0500 (CDT) Received: from firewall.bmc.com(192.245.162.250) by almond.bmc.com via smap (V2.0) id xma008366; Sun, 7 Jun 98 02:02:38 -0500 Received: (from uucp@localhost) by dresden.bmc.com (8.8.5/8.8.6) id CAA09407 for ; Sun, 7 Jun 1998 02:02:08 -0500 (CDT) Received: from tangelo.bmc.com(172.17.7.166) by dresden.bmc.com via smap (3.2) id xma009239; Sun, 7 Jun 98 02:01:34 -0500 Received: from dorothy.bmc.com (dorothy.peer.com [192.146.153.65]) by tangelo.bmc.com (8.8.6 (PHNE_14041)/8.8.6) with ESMTP id CAA00485; Sun, 7 Jun 1998 02:02:02 -0500 (CDT) Received: from almond.bmc.com (almond.bmc.com [172.17.0.100]) by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) with ESMTP id XAA03358 for ; Sat, 6 Jun 1998 23:52:24 -0700 (PDT) Received: (from uucp@localhost) by almond.bmc.com (8.8.8/8.8.8) id BAA07193 for ; Sun, 7 Jun 1998 01:52:23 -0500 (CDT) Message-Id: <199806070652.BAA07193@almond.bmc.com> Received: from helios.man.lublin.pl(194.92.17.34) by almond.bmc.com via smap (V2.0) id xma007179; Sun, 7 Jun 98 01:52:01 -0500 Received: from merkury.pol.lublin.pl ([193.59.20.253]:3045 "EHLO merkury.pol.lublin.pl" ident: "NO-IDENT-SERVICE") by helios.man.lublin.pl with ESMTP id <7011-29213>; Sun, 7 Jun 1998 06:56:19 +0200 Received: from MERKURY/MAILQUEUE by merkury.pol.lublin.pl (Mercury 1.21); 7 Jun 98 06:56:18 +0100 Received: from MAILQUEUE by MERKURY (Mercury 1.21); 7 Jun 98 06:56:11 +0100 Received: from Plugs by merkury.pol.lublin.pl (Mercury 1.21); 7 Jun 98 06:56:07 +0100 To: kadeu28@demeter.psych.uw.edu.pl From: kadeu28@demeter.psych.uw.edu.pl (THE HOBBY PROS) Comments: Authenticated sender is Subject: CABLE DECSRAMBLER Now Only $6.00 !! Illegal-Object: Syntax error in Message-Id: value found on helios.man.lublin.pl: Message-Id: <1998060629XAA26707@564897845784511@Inovations.com.pol.lublin.pl> ^-illegal end of message identification Date: Sun, 7 Jun 1998 06:56:19 +0200 This is really cool! PREMIUM CHANNELS and PAY PER VIEW EVENTS **** FREE **** EASY to assemble plans for only $6.00 ! We will send your plans the day we receive your order! YOU WILL BE WATCHING HBO, SHOWTIME, THE MOVIE CHANNEL, Pay per view events, Adult stations, and any other scrambled signal NEXT WEEK! You can EASILY assemble a cable descrambler in less than 30 minutes! You have probably seen many advertisments for similar plans.... BUT OURS are BETTER! We have compared it to all the others and have actually IMPROVED the quality and SIMPLIFIED the design !!! ** We even include PHOTOS! ** OUR PLANS ARE BETTER! We have NEW, EASY TO READ,EASY to assemble plans for only $6.00! We have seen them advertised for as much as $29.00 and you have to wait weeks to receive them! WHAT THE OTHERS SAY IS TRUE! Parts are available at "The R***O S***k" Trademark rights do not allow us to use a national electronics retail chains' name but there is one in your town! Call and ask them BEFORE you order! They are very familiar with these plans and will tell you that it....... DOES INDEED WORK! ASK THEM! You will need part #'s 270-235 271-1325 278-212 RG59 coaxial cable, #12 copper wire, and a variable capacitor. They may have to special order the variable capacitor.... But WHY WAIT for a special order? WE have them! ** WE have secured a supply of the capacitors directly from the manufacturer, and We WILL include one with your plans for an ADDITIONAL $10.00 only! It is LEGAL, providing of course you use these plans for educational purposes only. IT'S FUN! We're sure you'll enjoy this! Our FAMILIES sure do! * you need one descrambler for each TV. NO MORE MONTHLY BILLS! $ 6.00 for plans only $10.00 for variable capacitor only $16.00 for The easy to assemble plans and one variable capacitor! Pay by check or money order payable to: The Hobby Pros 336 Bon Air Center #254 Greenbrae, Ca. 94904 Please provide a self addressed stamped envelope (.64) So we can RUSH your order to you! ot3 ^^ If this E-mail offends anyone, we apologize ......and feel free to use the DEL key. "By deleting your unwanted E-Mail you waste one key stroke, yet by throwing away paper mail you waste a planet! SAVE OUR TREES and support internet E-Mail instead of traditional mail"! ^^ From bnatale@acecomm.com Tue Jun 9 13:50:56 1998 Return-Path: Received: from almond.bmc.com (mail-gw1.bmc.com [198.64.253.22]) by amethyst.bmc.com (8.8.8/8.8.8) with ESMTP id NAA16626 for ; Tue, 9 Jun 1998 13:50:55 -0500 (CDT) Received: (from uucp@localhost) by almond.bmc.com (8.8.8/8.8.8) id NAA11684 for ; Tue, 9 Jun 1998 13:50:54 -0500 (CDT) Received: from firewall.bmc.com(192.245.162.250) by almond.bmc.com via smap (V2.0) id xma009344; Tue, 9 Jun 98 13:43:21 -0500 Received: (from uucp@localhost) by dresden.bmc.com (8.8.5/8.8.6) id NAA20510 for ; Tue, 9 Jun 1998 13:42:28 -0500 (CDT) Received: from tangelo.bmc.com(172.17.7.166) by dresden.bmc.com via smap (3.2) id xma019975; Tue, 9 Jun 98 13:42:07 -0500 Received: from dorothy.bmc.com (dorothy.peer.com [192.146.153.65]) by tangelo.bmc.com (8.8.6 (PHNE_14041)/8.8.6) with ESMTP id NAA02066; Tue, 9 Jun 1998 13:42:35 -0500 (CDT) Received: from cashew.bmc.com (cashew.bmc.com [172.19.0.100]) by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) with ESMTP id LAA21812 for ; Tue, 9 Jun 1998 11:37:30 -0700 (PDT) Received: (from uucp@localhost) by cashew.bmc.com (8.8.8/8.8.8) id NAA02334 for ; Tue, 9 Jun 1998 13:37:25 -0500 (CDT) Received: from relay1.smtp.psi.net(38.8.14.2) by cashew.bmc.com via smap (V2.0) id xma002301; Tue, 9 Jun 98 13:36:45 -0500 Received: from [192.152.208.5] (helo=acecomm.com) by relay1.smtp.psi.net with smtp (Exim 1.90 #1) id 0yjTGA-0001YC-00; Tue, 9 Jun 1998 14:36:38 -0400 Received: from bnatale by acecomm.com (5.65/3.2.083191-ACE*COMM) id AA13434; Tue, 9 Jun 1998 14:38:52 -0400 Message-Id: <3.0.5.32.19980609143811.009b11f0@nips.acec.com> X-Sender: natale@nips.acec.com X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.5 (32) Date: Tue, 09 Jun 1998 14:38:11 -0400 To: agentx@peer.com From: Bob Natale Subject: AgentX charter/milestone update Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Hi, Following some off-list exchanges with the ADs over the past month or so, I'd like to propose the following update of the AgentX charter: Done Publication of AgentX protocol specification (RFC 2257). Done Submit working draft version of AgentX MIB I-D. Jun 98 Collect and evaluate implementation reports (through bake-off). Jul 98 Conduct AgentX interoperability testing (July 23-24, Sunnyvale). Aug 98 Meet at 42nd IETF-CHICAGO (refine or revise RFC 2257). Sep 98 Petition IESG to advance RFC 2257 to Draft or recycle at Proposed. Oct 98 Submit final version of AgentX MIB I-D to IESG (for Proposed RFC). Nov 98 Submit working draft version of AgnetX API I-D. Jan 99 Submit final version of AgentX API I-D to IESG (for Info RFC). Feb 99 Evaluate necessary revisions to RFC 2257. Evaluate necessary revisions to AgentX MIB RFC. Mar 99 Meet at 44th IETF-TBD (begin SNMPv3 adaptation of AgentX) May 99 Publish SNMPv3 update of AgentX documents Please feel free to request clarification of any of that and/or to suggest any revisions/deletions/additions you feel may be necessary or desirable. Please do your best to get such comments submitted-- preferably on-list--by the end of this week, so that the ADs can review and approve our plan and carry it forward to the IESG. Thanks. Cordially, BobN ------------ ISO 9001 Registered Quality Supplier ----------- Bob Natale | ACE*COMM | 301-721-3000 [v] Dir, Net Mgmt Prod | 704 Quince Orchard Rd | 301-721-3001 [f] bnatale@acecomm.com| Gaithersburg MD 20878 | www.acecomm.com ------------- Free downloads at www.winsnmp.com ------------- From mwhite@cmu.edu Tue Jun 9 13:52:44 1998 Return-Path: Received: from almond.bmc.com (mail-gw1.bmc.com [198.64.253.22]) by amethyst.bmc.com (8.8.8/8.8.8) with ESMTP id NAA16642 for ; Tue, 9 Jun 1998 13:52:44 -0500 (CDT) Received: (from uucp@localhost) by almond.bmc.com (8.8.8/8.8.8) id NAA12094 for ; Tue, 9 Jun 1998 13:52:43 -0500 (CDT) Received: from firewall.bmc.com(192.245.162.250) by almond.bmc.com via smap (V2.0) id xmane5230; Tue, 9 Jun 98 13:31:40 -0500 Received: (from uucp@localhost) by dresden.bmc.com (8.8.5/8.8.6) id NAA14710 for ; Tue, 9 Jun 1998 13:02:50 -0500 (CDT) Received: from tangelo.bmc.com(172.17.7.166) by dresden.bmc.com via smap (3.2) id xma014120; Tue, 9 Jun 98 13:02:16 -0500 Received: from dorothy.bmc.com (dorothy.peer.com [192.146.153.65]) by tangelo.bmc.com (8.8.6 (PHNE_14041)/8.8.6) with ESMTP id NAA24148; Tue, 9 Jun 1998 13:02:31 -0500 (CDT) Received: from cashew.bmc.com (cashew.bmc.com [172.19.0.100]) by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) with ESMTP id KAA21660 for ; Tue, 9 Jun 1998 10:47:44 -0700 (PDT) Received: (from uucp@localhost) by cashew.bmc.com (8.8.8/8.8.8) id MAA29632 for ; Tue, 9 Jun 1998 12:47:43 -0500 (CDT) Received: from cmu1.acs.cmu.edu(128.2.35.186) by cashew.bmc.com via smap (V2.0) id xma029627; Tue, 9 Jun 98 12:47:29 -0500 Received: from SUBNET6-LO.DYNAMIC.NET.CMU.EDU (SUBNET6-LO.DYNAMIC.NET.CMU.EDU [128.2.6.95]) by cmu1.acs.cmu.edu (8.8.5/8.8.5) with SMTP id NAA20414 for ; Tue, 9 Jun 1998 13:47:23 -0400 (EDT) Date: Tue, 09 Jun 1998 13:47:45 -0400 From: "Matt White" To: agentx@peer.com Subject: Conceptual table indices Message-ID: <4046867482.897400065@SUBNET6-LO.DYNAMIC.NET.CMU.EDU> X-Mailer: Mulberry (Win32) [1.3.3, s/n S-100002] X-Authenticated: mwhite by cyrus.andrew.cmu.edu X-Licensed-To: site license MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit I have a question regarding index allocation that I believe Juergen brought up earlier but for which I do not recall there ever being a resolution. How do we handle conceptual tables with more than one indexing column? The RFC states that for conceptual tables indexed by more than one variable, an index may be allocated for each variable. This does not seem sufficient. For example, suppose that I have a table indexed by IP address and port number. If I wish to allocate a single address/port pair, the RFC seems to indicate that I should send an IndexAllocate PDU with two variable bindings, one for the IP address and another for the port number. If I do allocate these two indices, however, I have just allocated ALL rows with that IP address and all rows with that port number. While I can certainly see instances where this might be useful, there are also many instances where this behaviour is not desireable. Any thoughts on this? -Matt ---------- Matt White Network Systems Designer Canegie Mellon Computing Services From agentx-bugs@andrew.cmu.edu Tue Jun 9 14:04:22 1998 Return-Path: Received: from almond.bmc.com (mail-gw1.bmc.com [198.64.253.22]) by amethyst.bmc.com (8.8.8/8.8.8) with ESMTP id OAA16773 for ; Tue, 9 Jun 1998 14:04:21 -0500 (CDT) From: agentx-bugs@andrew.cmu.edu Received: (from uucp@localhost) by almond.bmc.com (8.8.8/8.8.8) id OAA15151 for ; Tue, 9 Jun 1998 14:04:20 -0500 (CDT) Received: from firewall.bmc.com(192.245.162.250) by almond.bmc.com via smap (V2.0) id xmax14446; Tue, 9 Jun 98 14:01:59 -0500 Received: (from uucp@localhost) by dresden.bmc.com (8.8.5/8.8.6) id NAA04950 for ; Tue, 9 Jun 1998 13:58:03 -0500 (CDT) Received: from tangelo.bmc.com(172.17.7.166) by dresden.bmc.com via smap (3.2) id xma004295; Tue, 9 Jun 98 13:57:38 -0500 Received: from dorothy.bmc.com (dorothy.peer.com [192.146.153.65]) by tangelo.bmc.com (8.8.6 (PHNE_14041)/8.8.6) with ESMTP id NAA05708; Tue, 9 Jun 1998 13:58:06 -0500 (CDT) Received: from almond.bmc.com (almond.bmc.com [172.17.0.100]) by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) with ESMTP id LAA21860 for ; Tue, 9 Jun 1998 11:52:13 -0700 (PDT) Received: (from uucp@localhost) by almond.bmc.com (8.8.8/8.8.8) id NAA11940 for ; Tue, 9 Jun 1998 13:52:12 -0500 (CDT) Received: from cmu1.acs.cmu.edu(128.2.35.186) by almond.bmc.com via smap (V2.0) id xma010824; Tue, 9 Jun 98 13:48:43 -0500 Received: from SUBNET6-LO.DYNAMIC.NET.CMU.EDU (SUBNET6-LO.DYNAMIC.NET.CMU.EDU [128.2.6.95]) by cmu1.acs.cmu.edu (8.8.5/8.8.5) with SMTP id OAA24342 for ; Tue, 9 Jun 1998 14:48:24 -0400 (EDT) Date: Tue, 09 Jun 1998 14:48:47 -0400 To: agentx@peer.com Subject: AgentX implementation available Message-ID: <4050529532.897403727@SUBNET6-LO.DYNAMIC.NET.CMU.EDU> X-Mailer: Mulberry (Win32) [1.3.3, s/n S-100002] X-Authenticated: mwhite by cyrus.andrew.cmu.edu X-Licensed-To: site license MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit We have an alpha quality implementation of a subset of the AgentX protocol available for ftp from: ftp://ftp.net.cmu.edu/pub/agentx/agentx-v0.1.tar.gz There is some documentation available at: http://www.net.cmu.edu/projects/agentx/ At this time, I have only tried to compile this code under Sparc Solaris 2.5.1. It compiles without difficulty using both the Sun and GNU compilers. I'd like to emphasize that this is an alpha release and that there is still a good amount of work to be done. However, I would appreciate any feedback on the current implementation as well as comments on what features people would like to see in future versions. Bug reports are solicited, patches even more so. Please send all correspondance to: agentx-bugs@andrew.cmu.edu -Matt ---------- Matt White Maintainer, AgentX Implementation Carnegie Mellon Computing Services From bnatale@acecomm.com Tue Jun 9 16:15:35 1998 Return-Path: Received: from almond.bmc.com (mail-gw1.bmc.com [198.64.253.22]) by amethyst.bmc.com (8.8.8/8.8.8) with ESMTP id QAA17969 for ; Tue, 9 Jun 1998 16:15:35 -0500 (CDT) Received: (from uucp@localhost) by almond.bmc.com (8.8.8/8.8.8) id QAA22627 for ; Tue, 9 Jun 1998 16:15:28 -0500 (CDT) Received: from firewall.bmc.com(192.245.162.250) by almond.bmc.com via smap (V2.0) id xma022014; Tue, 9 Jun 98 16:13:37 -0500 Received: (from uucp@localhost) by dresden.bmc.com (8.8.5/8.8.6) id QAA27676 for ; Tue, 9 Jun 1998 16:13:03 -0500 (CDT) Received: from tangelo.bmc.com(172.17.7.166) by dresden.bmc.com via smap (3.2) id xma026566; Tue, 9 Jun 98 16:12:12 -0500 Received: from dorothy.bmc.com (dorothy.peer.com [192.146.153.65]) by tangelo.bmc.com (8.8.6 (PHNE_14041)/8.8.6) with ESMTP id QAA00406; Tue, 9 Jun 1998 16:12:40 -0500 (CDT) Received: from cashew.bmc.com (cashew.bmc.com [172.19.0.100]) by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) with ESMTP id OAA22681 for ; Tue, 9 Jun 1998 14:08:07 -0700 (PDT) Received: (from uucp@localhost) by cashew.bmc.com (8.8.8/8.8.8) id QAA11635 for ; Tue, 9 Jun 1998 16:08:07 -0500 (CDT) Received: from relay1.smtp.psi.net(38.8.14.2) by cashew.bmc.com via smap (V2.0) id xma011603; Tue, 9 Jun 98 16:07:58 -0500 Received: from [192.152.208.5] (helo=acecomm.com) by relay1.smtp.psi.net with smtp (Exim 1.90 #1) id 0yjVc9-0004Ke-00; Tue, 9 Jun 1998 17:07:30 -0400 Received: from bnatale by acecomm.com (5.65/3.2.083191-ACE*COMM) id AA14099; Tue, 9 Jun 1998 15:22:31 -0400 Message-Id: <3.0.5.32.19980609152150.009acd50@nips.acec.com> X-Sender: natale@nips.acec.com X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.5 (32) Date: Tue, 09 Jun 1998 15:21:50 -0400 To: "Matt White" From: Bob Natale Subject: Re: Conceptual table indices Cc: agentx@peer.com In-Reply-To: <4046867482.897400065@SUBNET6-LO.DYNAMIC.NET.CMU.EDU> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" >At 01:47 PM 6/9/98 -0400, Matt White wrote: Hi Matt, >I have a question regarding index allocation that I believe Juergen brought >up earlier but for which I do not recall there ever being a resolution. Here's the full text of Mike's response to Juergen: >Subject: Re: index allocation >Date: Wed, 29 Apr 98 11:06:42 -0400 >From: Mike Daniele > >>Thanks Mike, this interpretation is fine with me. Anyway, this is >>something that should be clarified in a revision of the RFC. > >Agreed. Bob, Dale, are we keeping a list of suggested revisions? > >>I have another question. Lets assume I have a fooTable indexed by two >>columns fooA and fooB. I want to allocate a single entry in the >>table. I would send an agentx-IndexAllocate-PDU with v.name1 = fooA, >>and v.name2 = fooB. The corresponding data elements contain the index >>values I would like to allocate. Is this correct? > >Yes, as described in the 4th paragraph of 7.1.3. > >>If yes, what happens if I want to allocate indexes for two rows in >>fooTable? Am I correct to send an agentx-IndexAllocate-PDU with >>v.name1 = fooA, v.name2 = fooB, v.name3 = fooA and v.name4 = fooB and >>appropriate data elements? > >You could certainly do so if you wished. Or you could send multiple >agentx-IndexAllocate-PDUs, each containing fewer varbinds. >If you were requesting specific indexes be allocated, yes you'd >place those values in the appropriate v.data elements. > >>What happens if the data elements v.data1 and v.data3 have the same value? > >Then one of them would fail, per step 4) (c) in 7.1.2. And per step 4), >no index values would be allocated, and a response pdu indicating the error >would be returned. > >>I other words: How are complex index values grouped together? The text >>in section 7.1.2 looks like if each VarBind element is processed in >>isolation. > >They are, to the extent that each varbind contains a wholly defined >request for an index allocation, that can be processed individually. >(One way to think of it is that the master agent maintains a database > keyed by v.name values.) > >They are not, to the extent that if multiple varbinds are present in >the PDU, their index allocations either all succeed, or none succeed. > >I hope I understood your question. I don't understand why a subagent >would send multiple varbinds requesting exactly the same index allocation >(same v.name, same v.data, both NEW_INDEX and ANY_INDEX bits clear) >when the request can't possibly succeed... > >Regards, >Mike >How do we handle conceptual tables with more than one indexing column? >The RFC states that for conceptual tables indexed by more than one >variable, an index may be allocated for each variable. This does not >seem sufficient. It is sufficient for some cases and it may be insufficient for some others. >For example, suppose that I have a table indexed by IP address and port >number. If I wish to allocate a single address/port pair, the RFC seems >to indicate that I should send an IndexAllocate PDU with two variable >bindings, one for the IP address and another for the port number. Correct. >If I do allocate these two indices, however, I have just allocated ALL >rows with that IP address and all rows with that port number. Correct. >While I can certainly see instances where this might be useful, there >are also many instances where this behaviour is not desireable. Correct...leaving open the quantification and qualification of the "some" and "many" for the moment. >Any thoughts on this? If this particular limitation proves to be unacceptable, then perhaps we can use another flags bit on the IndexAllocate PDU to mean "the multiple varbinds in this PDU must be considered as a single index allocation value"...or something like that...? >Matt White >Network Systems Designer >Canegie Mellon Computing Services Cordially, BobN ------------ ISO 9001 Registered Quality Supplier ----------- Bob Natale | ACE*COMM | 301-721-3000 [v] Dir, Net Mgmt Prod | 704 Quince Orchard Rd | 301-721-3001 [f] bnatale@acecomm.com| Gaithersburg MD 20878 | www.acecomm.com ------------- Free downloads at www.winsnmp.com ------------- From keeney@mv.mv.com Tue Jun 9 19:18:27 1998 Return-Path: Received: from almond.bmc.com (mail-gw1.bmc.com [198.64.253.22]) by amethyst.bmc.com (8.8.8/8.8.8) with ESMTP id TAA19603 for ; Tue, 9 Jun 1998 19:18:27 -0500 (CDT) Received: (from uucp@localhost) by almond.bmc.com (8.8.8/8.8.8) id TAA04110 for ; Tue, 9 Jun 1998 19:18:25 -0500 (CDT) Received: from firewall.bmc.com(192.245.162.250) by almond.bmc.com via smap (V2.0) id xma003418; Tue, 9 Jun 98 19:16:18 -0500 Received: (from uucp@localhost) by dresden.bmc.com (8.8.5/8.8.6) id TAA23209 for ; Tue, 9 Jun 1998 19:15:40 -0500 (CDT) Received: from tangelo.bmc.com(172.17.7.166) by dresden.bmc.com via smap (3.2) id xma022707; Tue, 9 Jun 98 19:15:11 -0500 Received: from dorothy.bmc.com (dorothy.peer.com [192.146.153.65]) by tangelo.bmc.com (8.8.6 (PHNE_14041)/8.8.6) with ESMTP id TAA27884; Tue, 9 Jun 1998 19:15:40 -0500 (CDT) Received: from cashew.bmc.com (cashew.bmc.com [172.19.0.100]) by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) with ESMTP id RAA25029 for ; Tue, 9 Jun 1998 17:11:44 -0700 (PDT) Received: (from uucp@localhost) by cashew.bmc.com (8.8.8/8.8.8) id TAA21240 for ; Tue, 9 Jun 1998 19:11:44 -0500 (CDT) Received: from unknown(209.155.18.71) by cashew.bmc.com via smap (V2.0) id xma021231; Tue, 9 Jun 98 19:11:38 -0500 Received: from [208.134.174.47] by bugs.uoli.com (NTMail 3.03.0014/42.aab2) with ESMTP id qa031892 for ; Tue, 9 Jun 1998 18:07:08 -0600 Message-Id: <3.0.1.32.19980609201555.00946100@pop-cnh.mv.net> X-Sender: keeney-ke@pop-cnh.mv.net X-Mailer: Windows Eudora Pro Version 3.0.1 (32) Date: Tue, 09 Jun 1998 20:15:55 -0400 To: agentx@peer.com From: David Keeney Subject: Agentx Web site Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Hi, I have updated the Agentx web site with the information for Matt White's implementation. If anyone else would like to post their implementation on the Agentx web page just send me email. Even if you do not want to give very much information it would still be useful to know who is currently working on implementations. The Agentx web site is at http://www.scguild.com/agentx Thanks, David Keeney Software Contractors' Guild ------------------- From hardaker@oakdale.ucdavis.edu Fri Jun 12 09:34:35 1998 Return-Path: Received: from almond.bmc.com (mail-gw1.bmc.com [198.64.253.22]) by amethyst.bmc.com (8.8.8/8.8.8) with ESMTP id JAA24153 for ; Fri, 12 Jun 1998 09:34:35 -0500 (CDT) Received: (from uucp@localhost) by almond.bmc.com (8.8.8/8.8.8) id JAA28231 for ; Fri, 12 Jun 1998 09:34:35 -0500 (CDT) Received: from firewall.bmc.com(192.245.162.250) by almond.bmc.com via smap (V2.0) id xma022744; Fri, 12 Jun 98 09:19:12 -0500 Received: (from uucp@localhost) by dresden.bmc.com (8.8.5/8.8.6) id JAA18626 for ; Fri, 12 Jun 1998 09:18:39 -0500 (CDT) Received: from tangelo.bmc.com(172.17.7.166) by dresden.bmc.com via smap (3.2) id xma017471; Fri, 12 Jun 98 09:17:43 -0500 Received: from dorothy.bmc.com (dorothy.peer.com [192.146.153.65]) by tangelo.bmc.com (8.8.6 (PHNE_14041)/8.8.6) with ESMTP id LAA20852; Thu, 11 Jun 1998 11:14:45 -0500 (CDT) Received: from almond.bmc.com (almond.bmc.com [172.17.0.100]) by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) with ESMTP id JAA16376 for ; Thu, 11 Jun 1998 09:13:03 -0700 (PDT) Received: (from uucp@localhost) by almond.bmc.com (8.8.8/8.8.8) id LAA00533 for ; Thu, 11 Jun 1998 11:13:02 -0500 (CDT) Received: from oakdale.ucdavis.edu(169.237.210.82) by almond.bmc.com via smap (V2.0) id xma000528; Thu, 11 Jun 98 11:12:36 -0500 Received: (from hardaker@localhost) by oakdale.ucdavis.edu (8.7.1/8.7.3) id JAA07654; Thu, 11 Jun 1998 09:11:53 -0700 (PDT) Sender: hardaker@oakdale.ucdavis.edu To: Mike Daniele Cc: Bob Natale , wjhardaker@ucdavis.edu, agentx@peer.com Subject: Re: UCD-SNMP AgentX questions (answers) References: <9806111416.AA05828@bernie.zk3.dec.com> X-Face: #qW^}a%m*T^{A:Cp}$R\"38+d}41-Z}uU8,r%F#c#s:~Nzp0G9](s?,K49KJ]s"*7gvRgA SrAvQc4@/}L7Qc=w{)]ACO\R{LF@S{pXfojjjGg6c;q6{~C}CxC^^&~(F]`1W)%9j/iS/ IM",B1M.?{w8ckLTYD'`|kTr\i\cgY)P4 X-url: http://dcas.ucdavis.edu/~hardaker Organization: U.C.Davis, Information Technology - D.C.A.S. Mime-Version: 1.0 (generated by tm-edit 7.108) Content-Type: text/plain; charset=US-ASCII From: Wes Hardaker Date: 11 Jun 1998 09:11:52 -0700 In-Reply-To: Mike Daniele's message of "Thu, 11 Jun 98 10:16:21 -0400" Message-ID: Lines: 62 X-Mailer: Gnus v5.6.8/XEmacs 20.3 - "Vatican City" (sadly, I have Bob's first message at home, so I'll have to respond to that one later [ie, out of order])... >>>>> On Thu, 11 Jun 98 10:16:21 -0400, Mike Daniele said: >>> It would be best, in my eyes, if we could do something like: >>> >>> try to open 161 ourselves. >>> >>> if in use, open a agentX connection and register each of our >>> internal modules with the master agentX controller. >>> >>> if not in use, do what we have been doing and optionally open the >>> agentX port ourselves and handle the master functions. Mike> So perhaps a slightly better approach would be Mike> try to establish an AgentX session Mike> if that succeeds, register with whatever master agent is running Mike> if that doesn't succeed, do what you have been doing Well, but if 161 isn't opened, I say we should grab it (and possibly bring up the agentX port ourselves). IE, assume that you're an snmp agent directed on purpose to the default port... If the default port isn't being used, then it should be is my point. The point (since you missed it) behind my original message is that I wanted to do something more along the lines of: if (open the default port ourselves) { if (open the agentx port as a client) { register_as_agentX_client(); } else if (open the agentX port as a master) { accept agentX connections(); } accept snmp connections(); } else if (open the agentx port as a client) { register_as_agentX_client(); } } In this way, we've covered all bases. My original question was related to the fact the the agentX specifications imply that you shouldn't be both a master and a sub-agent. My reasoning for wanting to do both is that the people that use our agent already have a simple method of adding in sub-modules to our agent in a easy and semi-documented method. They would benefit from being on both sides of the fence without worrying about it. On machines with a vendor supplied master, they could use the same agent code as on the machines that don't. Of course, the drawback to this is that the agent's code would be much more bulky having to support all possible contingencies... (and its arguably a better solution to deploy both a true master and sub-agent ourselves rather than the above rolling of both into one application.) -- "Ninjas aren't dangerous. They're more afraid of you than you are of them." From daniele@zk3.dec.com Fri Jun 12 09:37:57 1998 Return-Path: Received: from almond.bmc.com (mail-gw1.bmc.com [198.64.253.22]) by amethyst.bmc.com (8.8.8/8.8.8) with ESMTP id JAA24198 for ; Fri, 12 Jun 1998 09:37:57 -0500 (CDT) Received: (from uucp@localhost) by almond.bmc.com (8.8.8/8.8.8) id JAA29495 for ; Fri, 12 Jun 1998 09:37:57 -0500 (CDT) Received: from firewall.bmc.com(192.245.162.250) by almond.bmc.com via smap (V2.0) id xma024187; Fri, 12 Jun 98 09:22:48 -0500 Received: (from uucp@localhost) by dresden.bmc.com (8.8.5/8.8.6) id JAA23199 for ; Fri, 12 Jun 1998 09:22:14 -0500 (CDT) Received: from tangelo.bmc.com(172.17.7.166) by dresden.bmc.com via smap (3.2) id xma021929; Fri, 12 Jun 98 09:21:12 -0500 Received: from dorothy.bmc.com (dorothy.peer.com [192.146.153.65]) by tangelo.bmc.com (8.8.6 (PHNE_14041)/8.8.6) with ESMTP id JAA05138; Thu, 11 Jun 1998 09:41:20 -0500 (CDT) Received: from almond.bmc.com (almond.bmc.com [172.17.0.100]) by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) with ESMTP id HAA16098 for ; Thu, 11 Jun 1998 07:20:32 -0700 (PDT) Received: (from uucp@localhost) by almond.bmc.com (8.8.8/8.8.8) id JAA27380 for ; Thu, 11 Jun 1998 09:20:25 -0500 (CDT) Received: from mail13.digital.com(192.208.46.30) by almond.bmc.com via smap (V2.0) id xma027365; Thu, 11 Jun 98 09:20:05 -0500 Received: from quarry.zk3.dec.com (quarry.zk3.dec.com [16.140.16.3]) by mail13.digital.com (8.8.8/8.8.8/WV1.0e) with SMTP id KAA06970; Thu, 11 Jun 1998 10:16:15 -0400 (EDT) Received: from bernie.zk3.dec.com by quarry.zk3.dec.com; (5.65v4.0/1.1.8.2/16Jan95-0946AM) id AA24633; Thu, 11 Jun 1998 10:12:50 -0400 Received: from localhost by bernie.zk3.dec.com; (5.65/1.1.8.2/22Aug96-1117AM) id AA05828; Thu, 11 Jun 1998 10:16:21 -0400 Message-Id: <9806111416.AA05828@bernie.zk3.dec.com> To: Bob Natale Cc: wjhardaker@ucdavis.edu, agentx@peer.com Subject: Re: UCD-SNMP AgentX questions (answers) In-Reply-To: Your message of "Wed, 10 Jun 98 11:46:49 EDT." <3.0.5.32.19980610114649.00962610@nips.acec.com> Date: Thu, 11 Jun 98 10:16:21 -0400 From: Mike Daniele X-Mts: smtp Hi, >>What I'm not sure of is why the protocol specifies that you be so >>strict with separating the master manager with the sub agents. >The intent of the spec, I believe, is to emphasize the *logical* >separation of the master agent from any particular sub-agent(s)-- >with one possible exception. Actually Bob I think you answered Wes' question best in the last sentence of your posting: >Remember that a primary purpose of AgentX is to enable an independently >developed sub-agent to interoperate with any independently developed master agent. The only way to accomplish this is by "strictly" defining how they should intoperate. >>It would be best, in my eyes, if we could do something like: >> >> try to open 161 ourselves. >> >> if in use, open a agentX connection and register each of our >> internal modules with the master agentX controller. >> >> if not in use, do what we have been doing and optionally open the >> agentX port ourselves and handle the master functions. >I can see nothing wrong with that plan...bear in mind that, while >not the primary scenario envisioned for AgentX, the master agent >*could* have its SNMP interface at some port other than UDP/161. So perhaps a slightly better approach would be try to establish an AgentX session if that succeeds, register with whatever master agent is running if that doesn't succeed, do what you have been doing >>The thing is that the agentx documentation actually states that there >>should be a separation between the implementations. I think I'm >>actually going to write the agentx group and ask them about it. My >>guess is that they would be worried about software bulk. I don't have enough context to understand the issue. Regards, Mike From A143c0KHk@1tin3.at.bmc.com Sat Jun 13 19:31:55 1998 Return-Path: Received: from almond.bmc.com (mail-gw1.bmc.com [198.64.253.22]) by amethyst.bmc.com (8.8.8/8.8.8) with ESMTP id TAA00483 for ; Sat, 13 Jun 1998 19:31:55 -0500 (CDT) Received: (from uucp@localhost) by almond.bmc.com (8.8.8/8.8.8) id TAA23737 for ; Sat, 13 Jun 1998 19:31:52 -0500 (CDT) From: A143c0KHk@1tin3.at.bmc.com Received: from firewall.bmc.com(192.245.162.250) by almond.bmc.com via smap (V2.0) id xma023369; Sat, 13 Jun 98 19:30:41 -0500 Received: (from uucp@localhost) by dresden.bmc.com (8.8.5/8.8.6) id TAA29868 for ; Sat, 13 Jun 1998 19:30:09 -0500 (CDT) Received: from tangelo.bmc.com(172.17.7.166) by dresden.bmc.com via smap (3.2) id xma029656; Sat, 13 Jun 98 19:30:01 -0500 Received: from dorothy.bmc.com (dorothy.peer.com [192.146.153.65]) by tangelo.bmc.com (8.8.6 (PHNE_14041)/8.8.6) with ESMTP id TAA28629; Sat, 13 Jun 1998 19:30:30 -0500 (CDT) Received: from cashew.bmc.com (cashew.bmc.com [172.19.0.100]) by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) with ESMTP id RAA02795 for ; Sat, 13 Jun 1998 17:21:28 -0700 (PDT) Received: (from uucp@localhost) by cashew.bmc.com (8.8.8/8.8.8) id TAA05247 for ; Sat, 13 Jun 1998 19:21:31 -0500 (CDT) Received: from gauntlet.fv.com(207.67.199.118) by cashew.bmc.com via smap (V2.0) id xma005235; Sat, 13 Jun 98 19:21:05 -0500 Received: from shekel.fv.com (shekel.fv.com [207.67.199.130]) by gauntlet.fv.com (8.9.0/8.9.0) with ESMTP id RAA23643 for ; Sat, 13 Jun 1998 17:20:41 -0700 (PDT) Received: from gauntlet.fv.com (gauntlet-in.fv.com [10.0.0.2]) by shekel.fv.com (8.9.0/8.9.0) with ESMTP id RAA25100 for ; Sat, 13 Jun 1998 17:20:37 -0700 (PDT) Received: from biff.stud.ntnu.no (biff.stud.ntnu.no [129.241.56.18]) by gauntlet.fv.com (8.9.0/8.9.0) with ESMTP id RAA23639 for ; Sat, 13 Jun 1998 17:20:30 -0700 (PDT) Received: from james.stud.ntnu.no (james.stud.ntnu.no [129.241.56.13]) by biff.stud.ntnu.no (8.8.8/8.8.8) with ESMTP id CAA09182; Sun, 14 Jun 1998 02:19:13 +0200 (MET DST) Received: from FpTefzK7J (1Cust79.tnt1.orl1.da.uu.net [208.250.77.79]) by james.stud.ntnu.no (8.8.8/8.8.8) with SMTP id CAA22521; Sun, 14 Jun 1998 02:18:32 +0200 (MET DST) DATE: 13 Jun 98 8:15:44 PM Reply-to: remove58@hotmail.com Message-ID: TO: mayma33@boo3k.com.it.bmc.com SUBJECT: Every Active Member Deserves A Paycheck! Every Active Member Deserves A Paycheck! No Sponsoring Required To Get A Paycheck! ***The True Network Marketers Dream.*** Simple And Unbelievably Lucrative! Click Here For More Information> http://www.gwc1.com/members/gg80/gwc1.htm To be removed - remove58@hotmail.com or call 904-282-0945 From DMOHI1Wov@meuz1it.net.bmc.com Sun Jun 14 06:40:03 1998 Return-Path: Received: from almond.bmc.com (mail-gw1.bmc.com [198.64.253.22]) by amethyst.bmc.com (8.8.8/8.8.8) with ESMTP id GAA00776 for ; Sun, 14 Jun 1998 06:40:02 -0500 (CDT) Received: (from uucp@localhost) by almond.bmc.com (8.8.8/8.8.8) id GAA12337 for ; Sun, 14 Jun 1998 06:39:59 -0500 (CDT) From: DMOHI1Wov@meuz1it.net.bmc.com Received: from firewall.bmc.com(192.245.162.250) by almond.bmc.com via smap (V2.0) id xma011839; Sun, 14 Jun 98 06:38:26 -0500 Received: (from uucp@localhost) by dresden.bmc.com (8.8.5/8.8.6) id GAA07815 for ; Sun, 14 Jun 1998 06:37:50 -0500 (CDT) Received: from tangelo.bmc.com(172.17.7.166) by dresden.bmc.com via smap (3.2) id xma007599; Sun, 14 Jun 98 06:37:21 -0500 Received: from dorothy.bmc.com (dorothy.peer.com [192.146.153.65]) by tangelo.bmc.com (8.8.6 (PHNE_14041)/8.8.6) with ESMTP id GAA08043; Sun, 14 Jun 1998 06:37:51 -0500 (CDT) Received: from cashew.bmc.com (cashew.bmc.com [172.19.0.100]) by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) with ESMTP id EAA03731 for ; Sun, 14 Jun 1998 04:34:04 -0700 (PDT) Received: (from uucp@localhost) by cashew.bmc.com (8.8.8/8.8.8) id GAA18995 for ; Sun, 14 Jun 1998 06:34:06 -0500 (CDT) Received: from zeus.tassie.net.au(203.19.156.71) by cashew.bmc.com via smap (V2.0) id xma018992; Sun, 14 Jun 98 06:33:52 -0500 Received: from rbFfFRc1U (1Cust223.tnt1.orl1.da.uu.net [208.250.77.223]) by zeus.tassie.net.au (8.8.7/8.8.7) with SMTP id VAA05369; Sun, 14 Jun 1998 21:28:01 +1000 (EST) (envelope-from DMOHI1Wov@meuz1it.net) DATE: 14 Jun 98 7:26:37 AM Message-ID: TO: cheque44k@bbay613.net.de.bmc.com SUBJECT: Every Active Member Deserves A Paycheck! Every Active Member Deserves A Paycheck! No Sponsoring Required To Get A Paycheck! ***The True Network Marketers Dream.*** Simple And Unbelievably Lucrative! Click Here For More Information> http://www.gwc1.com/members/tf92/gwc1.htm To be removed - remove58@hotmail.com or call 904-282-0945 From Lauren_Heintz@crow.bmc.com Wed Jun 17 15:17:07 1998 Return-Path: Received: from almond.bmc.com (mail-gw1.bmc.com [198.64.253.22]) by amethyst.bmc.com (8.8.8/8.8.8) with ESMTP id PAA00342 for ; Wed, 17 Jun 1998 15:17:06 -0500 (CDT) Received: (from uucp@localhost) by almond.bmc.com (8.8.8/8.8.8) id PAA20269 for ; Wed, 17 Jun 1998 15:16:56 -0500 (CDT) Received: from firewall.bmc.com(192.245.162.250) by almond.bmc.com via smap (V2.0) id xma019870; Wed, 17 Jun 98 15:15:48 -0500 Received: (from uucp@localhost) by dresden.bmc.com (8.8.5/8.8.6) id PAA25189 for ; Wed, 17 Jun 1998 15:15:14 -0500 (CDT) Received: from tangelo.bmc.com(172.17.7.166) by dresden.bmc.com via smap (3.2) id xma024382; Wed, 17 Jun 98 15:14:28 -0500 Received: from dorothy.bmc.com (dorothy.peer.com [192.146.153.65]) by tangelo.bmc.com (8.8.6 (PHNE_14041)/8.8.6) with ESMTP id PAA17074; Wed, 17 Jun 1998 15:14:53 -0500 (CDT) Received: from cherry.bmc.com (root@cherry.bmc.com [172.17.1.25]) by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) with ESMTP id NAA22687 for ; Wed, 17 Jun 1998 13:03:31 -0700 (PDT) Received: from lucille.bmc.com (lucille.peer.com [192.146.153.185]) by cherry.bmc.com with SMTP (8.8.6 (PHNE_14041)/8.7.3) id PAA01877; Wed, 17 Jun 1998 15:03:27 -0500 (CDT) Message-ID: <358820D8.330E@bmc.com> Date: Wed, 17 Jun 1998 13:02:32 -0700 From: Lauren Heintz Reply-To: Lauren_Heintz@crow.bmc.com Organization: Peer X-Mailer: Mozilla 3.03 (Win95; I) MIME-Version: 1.0 To: snmpv3@tis.com, agentx@peer.com Subject: SNMPv3 / AgentX bakeoff announcement. Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit This is a re-transmission of the earlier SNMPv3/AgentX bakeoff announcement. Please note that, with a few very special exceptions, attendance is only open to individuals and organizations who are planning to test their SNMPv3 and/or AgentX implementations. If you are planning to attend but haven't registered yet, I encourage you to register as soon as possible. Thanks, Lauren ------------------------------------------------ BMC Software invites you to participate in the SNMPv3 and AgentX combined bakeoffs, to be held the week of July 20 - 24 for interoperability testing of the latest SNMPv3 and AgentX implementations. This non-profit bakeoff will allow SNMPv3/AgentX developers and vendors to find and fix bugs in their SNMPv3 and/or AgentX implementations and help identify any issues with the proposed standards (RFCs 2257, 2271, 2272, 2273, 2274, 2275). When: SNMPv3 session: Mon-Wed, July 20-22, 1998, 9:30AM - 6:00 PM AgentX session: Thu-Fri, July 23-24, 1998 9:30AM - 6:00PM Where: BMC Software 965 Stewart Drive Sunnyvale, California 94086 Who to contact: Lauren Heintz (voice) 408-616-3169 (fax) 408-616-3101 Lauren_Heintz@bmc.com NOTE: Lauren will be out of office during the week June 1-5. Testing agenda: The respective working group (WG) chairs are responsible for preparing and publishing appropriate test plans by June 30, 1998. Fee: $100.00 per person, per day. What's Included: BMC Software will provide testing facilities, including one private 10BaseT network drop and ten IP addresses for each company, and approximately a 3 foot square area of table space (minimum). The network will not be connected to the Internet, so please plan for your email and FTP needs accordingly. Telephones will be available. Hot beverages, sodas and water. On-site morning and afternoon snacks, and lunch. Mutual non-disclosure agreement that each company/attendee must agree to, and sign, prior to entering the testing facilities. What you provide: One or more attendees. SNMPv3 and/or AgentX implementation(s) and test station (hardware), including a 10BaseT transceiver. Signed mutual non-disclosure agreement (provided upon request) for each attendee. You must use the MNDA BMC provides. All lodging and transportation and other expenses for your needs. How to register: Call Lauren Heintz to verify space availability, then send payment to be received by July 3, 1998, to Lauren Heintz at BMC Software at the above address along with names and phone numbers and email addresses of all attendees, and the number of days and actual dates of attendance. Also indicate the type of implementation and a list of equipment you will bring. Please indicate if you have special needs. Make checks payable to: BMC Software. Space is limited, so reserve early. Cancellations: Cancellations prior to July 3, 1998 are entitled to full refund. Cancellations on or after July 3, 1998 are entitled to 50% refund. Cancellations on or after July 13, 1998 receive no refund. Airport info: Sunnyvale is served by both the San Jose and San Francisco airports. You are responsible for all your transportation arrangements. We will provide directions to the Sunnyvale testing site upon request. Lodging: You are responsible for your own lodging arrangements. Residence Inn by Marriott, Silicon Valley II, 408-720-8893, is less than a five minute walk to BMC. Corporate rates start at approximately $175.00/night. Other hotels (not walking distance) abound in the Sunnyvale and Santa Clara areas with widely varying rates. Shipping/Receiving: With prior arrangement, you may ship your test stations to the BMC testing site up to one week in advance. BMC will provide storage for reasonably-sized test stations and their containers during the bakeoffs and one week prior. BMC cannot accept shipments requiring payment on receipt, nor can BMC fund return shipments before, during or after the bakeoffs. Return shipments may be sent directly from the BMC site if adequate funding is pre-arranged. To arrange for your shipping and receiving needs, please contact Lauren Heintz (see above). Disclaimers: BMC does not assume responsibility for anything not explicitly stated above, nor does BMC offer any implied warranty of fitness or guarantee of any service. BMC is not responsible for conducting the actual bakeoff tests or providing the SNMPv3 and/or AgentX test cases. BMC cannot accept responsibility for damage incurred to property on, or shipped to or from, BMC property. BMC also reserves the right to dispose of abandoned or unclaimed property after July 27, 1998, as it sees fit. BMC cannot accept responsibility for determining the exact cost of the bakeoffs, nor can BMC offer prorated refunds based on actual expenses incurred. In the event of unusual circumstances, BMC reserves the right to cancel this event at any time with a full (prior to July 20) or pro-rated (on or after July 20) refund of registration fees due to all registered attendees and without bearing or incurring any other expense or claim. BMC will make every reasonable attempt to ensure this event transpires as stated above. --------------------------------------------------------------------- Lauren Heintz BMC Software, Inc. (Silicon Valley Division) Voice: +1 408 616-3169 (Formerly PEER Networks) http://www.bmc.com Fax: +1 408 616-3339 965 Stewart Drive Email: Lheintz@bmc.com Sunnyvale, California 94086 USA --------------------------------------------------------------------- My opinions are my own and not necessarily those of BMC Software. --------------------------------------------------------------------- From rpresuhn@dorothy.bmc.com Wed Jun 17 16:55:36 1998 Return-Path: Received: from almond.bmc.com (mail-gw1.bmc.com [198.64.253.22]) by amethyst.bmc.com (8.8.8/8.8.8) with ESMTP id QAA01568 for ; Wed, 17 Jun 1998 16:55:36 -0500 (CDT) Received: (from uucp@localhost) by almond.bmc.com (8.8.8/8.8.8) id QAA27919 for ; Wed, 17 Jun 1998 16:55:26 -0500 (CDT) Received: from firewall.bmc.com(192.245.162.250) by almond.bmc.com via smap (V2.0) id xma027544; Wed, 17 Jun 98 16:54:14 -0500 Received: (from uucp@localhost) by dresden.bmc.com (8.8.5/8.8.6) id QAA24540 for ; Wed, 17 Jun 1998 16:53:41 -0500 (CDT) Received: from tangelo.bmc.com(172.17.7.166) by dresden.bmc.com via smap (3.2) id xma023770; Wed, 17 Jun 98 16:53:01 -0500 Received: from dorothy.bmc.com (dorothy.peer.com [192.146.153.65]) by tangelo.bmc.com (8.8.6 (PHNE_14041)/8.8.6) with ESMTP id QAA05909; Wed, 17 Jun 1998 16:53:26 -0500 (CDT) Received: (from rpresuhn@localhost) by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) id OAA25786 for agentx@peer.com; Wed, 17 Jun 1998 14:51:25 -0700 (PDT) Date: Wed, 17 Jun 1998 14:51:25 -0700 (PDT) From: Randy Presuhn Message-Id: <199806172151.OAA25786@dorothy.bmc.com> To: agentx@peer.com Subject: Re: UCD-SNMP AgentX questions (answers) Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Hi - | To: Mike Daniele | Cc: Bob Natale , wjhardaker@ucdavis.edu, agentx@peer.com | Subject: Re: UCD-SNMP AgentX questions (answers) | From: Wes Hardaker | Date: 11 Jun 1998 09:11:52 -0700 ... | Well, but if 161 isn't opened, I say we should grab it (and possibly | bring up the agentX port ourselves). IE, assume that you're an snmp | agent directed on purpose to the default port... If the default port | isn't being used, then it should be is my point. There are a couple of additional considerations, including: - giving the application the necessary permissions to grab these privileged ports - ensuring access to non-volatile configuration information, including the value of snmpEnableAuthenTraps for snmpv1 - access to the stored privacy and authentication keys for snmpv3 (how does the library find this stuff, and how does the user process get the rights to access it without opening a massive security hole?) - access to trap destination lists as in RFC 2273 Consider the implications of these issues for a library-level implementation of the application MIB, where the agentx support would presumably be just another library dependency, and the instrumented application's API calls would be at about the same level of abstraction as the ARM API, rather than at the protocol detail level of WinSNMP. This proposal would effectively require the user application, which did nothing more than innocently call an instrumentation API, to run setuid root! ... | In this way, we've covered all bases. My original question was | related to the fact the the agentX specifications imply that you | shouldn't be both a master and a sub-agent. .... I like to look at "master agent" and "sub-agent" as types of interfaces, so the relationship is "has-a" rather than "is-a". ----------------------------------------------------------------------- Randy Presuhn Email: rpresuhn@bmc.com http://www.bmc.com Voice: +1 408 616-3100 BMC Software, Inc. 965 Stewart Drive Fax: +1 408 616-3101 Sunnyvale, California 94086 USA ----------------------------------------------------------------------- In accordance with the BMC Communications Systems Use and Security Policy, I explicitly state that although my affiliation with BMC may be apparent, implied, or provided, my opinions are not necessarily those of BMC Software and that all external representations on behalf of BMC must first be cleared with a member of "the top management team." ----------------------------------------------------------------------- From hardaker@des.castles.com Fri Jun 19 12:29:46 1998 Return-Path: Received: from almond.bmc.com (mail-gw1.bmc.com [198.64.253.22]) by amethyst.bmc.com (8.8.8/8.8.8) with ESMTP id MAA12224 for ; Fri, 19 Jun 1998 12:29:45 -0500 (CDT) Received: (from uucp@localhost) by almond.bmc.com (8.8.8/8.8.8) id MAA07159 for ; Fri, 19 Jun 1998 12:29:31 -0500 (CDT) Received: from firewall.bmc.com(192.245.162.250) by almond.bmc.com via smap (V2.0) id xma006755; Fri, 19 Jun 98 12:28:02 -0500 Received: (from uucp@localhost) by dresden.bmc.com (8.8.5/8.8.6) id MAA04501 for ; Fri, 19 Jun 1998 12:27:27 -0500 (CDT) Received: from tangelo.bmc.com(172.17.7.166) by dresden.bmc.com via smap (3.2) id xma003926; Fri, 19 Jun 98 12:26:54 -0500 Received: from dorothy.bmc.com (dorothy.peer.com [192.146.153.65]) by tangelo.bmc.com (8.8.6 (PHNE_14041)/8.8.6) with ESMTP id MAA12688; Fri, 19 Jun 1998 12:27:23 -0500 (CDT) Received: from almond.bmc.com (almond.bmc.com [172.17.0.100]) by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) with ESMTP id KAA17715 for ; Fri, 19 Jun 1998 10:20:02 -0700 (PDT) Received: (from uucp@localhost) by almond.bmc.com (8.8.8/8.8.8) id MAA05372 for ; Fri, 19 Jun 1998 12:20:01 -0500 (CDT) Received: from des.castles.com(208.214.166.35) by almond.bmc.com via smap (V2.0) id xma005355; Fri, 19 Jun 98 12:19:43 -0500 Received: (from hardaker@localhost) by des.castles.com (8.8.7/8.8.7) id KAA04730; Fri, 19 Jun 1998 10:19:18 -0700 Sender: hardaker@des.castles.com To: Randy Presuhn Cc: agentx@peer.com Subject: Re: UCD-SNMP AgentX questions (answers) References: <199806172151.OAA25786@dorothy.bmc.com> X-Face: #qW^}a%m*T^{A:Cp}$R\"38+d}41-Z}uU8,r%F#c#s:~Nzp0G9](s?,K49KJ]s"*7gvRgA SrAvQc4@/}L7Qc=w{)]ACO\R{LF@S{pXfojjjGg6c;q6{~C}CxC^^&~(F]`1W)%9j/iS/ IM",B1M.?{w8ckLTYD'`|kTr\i\cgY)P4 X-url: http://dcas.ucdavis.edu/~hardaker Organization: U.C.Davis, Information Technology - D.C.A.S. Mime-Version: 1.0 (generated by tm-edit 7.108) Content-Type: text/plain; charset=US-ASCII From: Wes Hardaker Date: 19 Jun 1998 10:09:33 -0700 In-Reply-To: Randy Presuhn's message of "Wed, 17 Jun 1998 14:51:25 -0700 (PDT)" Message-ID: X-Mailer: Gnus v5.6.10/XEmacs 20.4 - "Emerald" Lines: 36 >>>>> On Wed, 17 Jun 1998 14:51:25 -0700 (PDT), Randy Presuhn said: Randy> | Well, but if 161 isn't opened, I say we should grab it (and possibly Randy> | bring up the agentX port ourselves). IE, assume that you're an snmp Randy> | agent directed on purpose to the default port... If the default port Randy> | isn't being used, then it should be is my point. Randy> - giving the application the necessary permissions to grab these Randy> privileged ports I consider that to be roughly the same error as failing to open it because it's already in use. Randy> - ensuring access to non-volatile configuration information, Randy> including the value of snmpEnableAuthenTraps for snmpv1 Randy> - access to the stored privacy and authentication keys for snmpv3 Randy> (how does the library find this stuff, and how does the user Randy> process get the rights to access it without opening a massive Randy> security hole?) Randy> - access to trap destination lists as in RFC 2273 Randy> Consider the implications of these issues for a library-level Randy> implementation of the application MIB, where the agentx support Randy> would presumably be just another library dependency ... Randy> This proposal would Randy> effectively require the user application, which did nothing Randy> more than innocently call an instrumentation API, to run setuid Randy> root! Those are good points, but I think I'm missing how it tied in with my question/statements... I'm implementing an agent, that will should always be run suid-root (in most cases at least)... -- "Ninjas aren't dangerous. They're more afraid of you than you are of them." From info@futureplayers.com Sat Jun 20 22:31:26 1998 Return-Path: Received: from almond.bmc.com (mail-gw1.bmc.com [198.64.253.22]) by amethyst.bmc.com (8.8.8/8.8.8) with ESMTP id WAA00520 for ; Sat, 20 Jun 1998 22:31:26 -0500 (CDT) From: info@futureplayers.com Received: (from uucp@localhost) by almond.bmc.com (8.8.8/8.8.8) id WAA28036 for ; Sat, 20 Jun 1998 22:31:25 -0500 (CDT) Received: from firewall.bmc.com(192.245.162.250) by almond.bmc.com via smap (V2.0) id xma027869; Sat, 20 Jun 98 22:30:35 -0500 Received: (from uucp@localhost) by dresden.bmc.com (8.8.5/8.8.6) id WAA19721 for ; Sat, 20 Jun 1998 22:30:03 -0500 (CDT) Received: from tangelo.bmc.com(172.17.7.166) by dresden.bmc.com via smap (3.2) id xma019234; Sat, 20 Jun 98 22:29:16 -0500 Received: from dorothy.bmc.com (dorothy.peer.com [192.146.153.65]) by tangelo.bmc.com (8.8.6 (PHNE_14041)/8.8.6) with ESMTP id WAA02136; Sat, 20 Jun 1998 22:29:43 -0500 (CDT) Received: from cashew.bmc.com (cashew.bmc.com [172.19.0.100]) by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) with ESMTP id UAA02045 for ; Sat, 20 Jun 1998 20:20:02 -0700 (PDT) Received: (from uucp@localhost) by cashew.bmc.com (8.8.8/8.8.8) id WAA07135 for ; Sat, 20 Jun 1998 22:20:01 -0500 (CDT) Received: from unknown(207.226.186.138) by cashew.bmc.com via smap (V2.0) id xma007133; Sat, 20 Jun 98 22:19:59 -0500 Received: from computername (pm3g-36.pacificnet.net [207.171.35.85]) by redwood.gps-net.com (8.8.7/8.8.5) with SMTP id VAA11753; Sat, 20 Jun 1998 21:16:03 -0500 (CDT) Message-Id: <199806210216.VAA11753@redwood.gps-net.com> Comments: Authenticated sender is To: info@futureplayers.com Date: Sat, 20 Jun 1998 18:34:22 +0000 X-Distribution: Bulk MIME-Version: 1.0 Content-type: text/plain; charset=ISO-8859-1 Content-transfer-encoding: Quoted-printable Subject: Dow Jones Futures and Options Reply-to: info@futureplayers.com Priority: normal X-mailer: Pegasus Mail for Win32 (v2.53/R1) ************************************************** If this e-mail reached you by mistake, we apologize. This is the only e-mail you will receive from us. If you would like to be removed, please forward this message to: remove@futureplayers.com ************************************************** At six a.m. on June 17th, 1998, you could have bought Japanese Yen future contract on a margin requirement of $2,160. By 12 noon , the contract could have been sold for a net profit of $5,000 - over 200% Profit in six hours! (Note however, that you would have lost this amount if you had sold the market without proper use of a buy-stop order.)This is an example of leverage usein the foreign exchange futures market. What is the next move? * Can the Dow Jones reach 10,000 this year, or has this bull market peaked? Dow Jones futures and options have been traded since October 1997. (You can call for daily recommendations.) * The price of crude oil is $12 per barrel! How long will prices remain at this level? * What will the impact of El Ni=F1o be on the Wheat, Soybean, and Corn this summer? A recent study by the Chicago Mercantile Exchange, one of the world's preeminent futures exchanges stated, "Portfolios with as much as 20% of assets in managed futures yielded up to 50% more than a portfolio of stocks and bonds along." The study concluded that an increase in performance using futures could be accomplished with a risk comparable to that of stocks and bonds. The next move is FREE! We invite you to learn about futures and options strategies; find out about discount futures, commodity funds and Dow Jones Futures; and become informed about the risks and opportunities in commodities and futures trading. This valuable information is FREE via our web site at http://www.futureplayers.com, or by phone at 800-454-9572. This is the first move you can take to join in over 500 million contracts of futures and options traded a year on US exchanges. + Sincerely, WWW.FUTUREPLAYERS.COM President Cannon Trading Inc. 9301 Wilshire Blvd. #614 Beverly Hills, CA 90210 310-859-9572 The material contained in this message is of opinion only and does not guarantee any profit. These are risky markets and only risk capital should be used. Past performances is not necessarily indicative of future results. + Source: National Futures Association - 1996 Annual Review From sales@no-isp.com Mon Jun 22 06:14:11 1998 Return-Path: Received: from almond.bmc.com (mail-gw1.bmc.com [198.64.253.22]) by amethyst.bmc.com (8.8.8/8.8.8) with ESMTP id GAA11352 for ; Mon, 22 Jun 1998 06:14:11 -0500 (CDT) Received: (from uucp@localhost) by almond.bmc.com (8.8.8/8.8.8) id GAA24515 for ; Mon, 22 Jun 1998 06:14:09 -0500 (CDT) Received: from firewall.bmc.com(192.245.162.250) by almond.bmc.com via smap (V2.0) id xma024223; Mon, 22 Jun 98 06:12:55 -0500 Received: (from uucp@localhost) by dresden.bmc.com (8.8.5/8.8.6) id GAA29400 for ; Mon, 22 Jun 1998 06:12:23 -0500 (CDT) Received: from tangelo.bmc.com(172.17.7.166) by dresden.bmc.com via smap (3.2) id xma029239; Mon, 22 Jun 98 06:11:50 -0500 Received: from dorothy.bmc.com (dorothy.peer.com [192.146.153.65]) by tangelo.bmc.com (8.8.6 (PHNE_14041)/8.8.6) with ESMTP id GAA17508; Mon, 22 Jun 1998 06:12:18 -0500 (CDT) Received: from cashew.bmc.com (cashew.bmc.com [172.19.0.100]) by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) with ESMTP id EAA04742 for ; Mon, 22 Jun 1998 04:05:02 -0700 (PDT) Received: (from uucp@localhost) by cashew.bmc.com (8.8.8/8.8.8) id GAA18133 for ; Mon, 22 Jun 1998 06:04:55 -0500 (CDT) Received: from unknown(202.144.227.6) by cashew.bmc.com via smap (V2.0) id xma018129; Mon, 22 Jun 98 06:04:34 -0500 Received: by it0.bud.net from localhost (router,SLMail V3.0); Mon, 22 Jun 1998 18:19:09 +0800 Received: by it0.bud.net from no-isp [202.144.227.51] (SLmail 3.0.2423); Mon, 22 Jun 1998 18:19:00 0800 Message-ID: <00c301bd9dc7$7fe1d040$4ae390ca@no-isp> From: "Instant Access" To: Subject: New Way to Access Internet Date: Mon, 22 Jun 1998 18:13:36 +0800 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_00C0_01BD9E0A.8E051040" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.2106.4 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.2106.4 This is a multi-part message in MIME format. ------=_NextPart_000_00C0_01BD9E0A.8E051040 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Dear User, =20 We hope that we are not inconveniencing you by sending you this E-mail. = If we are and you do not wish to receive any future product updates from = us, then please let us know by replying to sales@no-isp.com and we will = delete you from our mailing list. Again, please accept our apologies = for disturbing you. =20 If, however, you are looking for a fast and easy way to dial into the = Internet whenever you want and from wherever you are, then read on. =20 Our *Instant Access* service gives you *Internet-on-demand* and you = DON'T need to subscribe to an Internet Service Provider !! =20 a.. No monthly charges and no setup fee=20 b..=20 c.. No registration of any kind required=20 d..=20 e.. No Proxy in the way=20 f..=20 g.. Absolute ANONYMOUS login !!=20 h..=20 i.. Unlimited personal access duration=20 j..=20 k.. Fast connection=20 l..=20 m.. Access from all over the world=20 n..=20 o.. Nothing is censored on this network =20 Visit our site at www.no-isp.com for full details now. =20 Happy surfing! ------=_NextPart_000_00C0_01BD9E0A.8E051040 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
 
 
Dear = User,
 
We hope that we are = not=20 inconveniencing you by sending you this E-mail.  If we are and you = do not=20 wish to receive any future product updates from us, then please let us = know by=20 replying to sales@no-isp.com and = we will=20 delete you from our mailing list.  Again, please accept our = apologies for=20 disturbing you.
 
If, however, you are = looking for=20 a fast and easy way to dial into the Internet whenever you want and from = wherever you are, then read on.
 
Our *Instant Access* = service=20 gives you *Internet-on-demand* and you DON'T need to subscribe to an = Internet=20 Service Provider !!
 
  • No monthly = charges and no=20 setup fee=20
  • No registration = of any kind=20 required=20
  • No Proxy in the = way=20
  • Absolute = ANONYMOUS login=20 !!=20
  • Unlimited = personal access=20 duration=20
  • Fast = connection=20
  • Access from all = over the=20 world=20
  • Nothing is = censored on this=20 network
 
Visit our site at www.no-isp.com for = full=20 details now.
 
 
Happy = surfing!
 
------=_NextPart_000_00C0_01BD9E0A.8E051040-- From ashishkh@wipinfo.soft.net Mon Jun 22 09:40:30 1998 Return-Path: Received: from almond.bmc.com (mail-gw1.bmc.com [198.64.253.22]) by amethyst.bmc.com (8.8.8/8.8.8) with ESMTP id JAA13875 for ; Mon, 22 Jun 1998 09:40:30 -0500 (CDT) Received: (from uucp@localhost) by almond.bmc.com (8.8.8/8.8.8) id JAA05531 for ; Mon, 22 Jun 1998 09:40:28 -0500 (CDT) Received: from firewall.bmc.com(192.245.162.250) by almond.bmc.com via smap (V2.0) id xma004815; Mon, 22 Jun 98 09:38:44 -0500 Received: (from uucp@localhost) by dresden.bmc.com (8.8.5/8.8.6) id JAA15086 for ; Mon, 22 Jun 1998 09:38:11 -0500 (CDT) Received: from tangelo.bmc.com(172.17.7.166) by dresden.bmc.com via smap (3.2) id xma013823; Mon, 22 Jun 98 09:37:10 -0500 Received: from dorothy.bmc.com (dorothy.peer.com [192.146.153.65]) by tangelo.bmc.com (8.8.6 (PHNE_14041)/8.8.6) with ESMTP id JAA15719; Mon, 22 Jun 1998 09:37:40 -0500 (CDT) Received: from almond.bmc.com (almond.bmc.com [172.17.0.100]) by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) with ESMTP id HAA05106 for ; Mon, 22 Jun 1998 07:35:45 -0700 (PDT) Received: (from uucp@localhost) by almond.bmc.com (8.8.8/8.8.8) id JAA04065 for ; Mon, 22 Jun 1998 09:35:38 -0500 (CDT) Received: from agni.wipinfo.soft.net(164.164.6.20) by almond.bmc.com via smap (V2.0) id xma004048; Mon, 22 Jun 98 09:35:20 -0500 Received: from scan.wipinfo.soft.net by wipinfo.soft.net (SMI-8.6/SMI-SVR4) id UAA10972; Mon, 22 Jun 1998 20:01:24 -0500 Received: from 192.9.100.151 by scan.wipinfo.soft.net (InterScan E-Mail VirusWall NT) Received: from opel ([192.9.52.22]) by divya.wipinfo.soft.net (8.8.5/8.8.5) with SMTP id UAA00858 for ; Mon, 22 Jun 1998 20:07:47 +0530 Message-Id: <3.0.5.32.19980622200611.008fa100@tagore> X-Sender: ashishkh@tagore X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.5 (32) Date: Mon, 22 Jun 1998 20:06:11 To: agentx@peer.com From: Ashish Hanwadikar Subject: agentx-Ping PDU Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Hi all, The AgentX RFC defines agentx-Ping PDU so that subagent can monitor master agent's ability to send and receive agentx PDUs over a session. I want to know whether are there any guidelines about how to use agentx-Ping PDUs by subagent (or subagent library internally). Particularly, I want to know the frequency and conditions under which subagent should use agentx-Ping PDUs. One policy I can think of is to periodically ping the master agent. Other is when the master agent does'nt respond to subagent's agentx-notify, agentx-register, agentx-deregister etc. PDUs within certain time period. Is this thinking Okay? With Regds., Ashish Hanwadikar Technology Solutions, Wipro Limited Bangalore-27 http://www.geocities.com/SiliconValley/Bay/5393/ Email: ashishkh@writeme.com Ph: +91-80-2241730 Ext. 3315 From rpresuhn@dorothy.bmc.com Mon Jun 22 13:39:41 1998 Return-Path: Received: from almond.bmc.com (mail-gw1.bmc.com [198.64.253.22]) by amethyst.bmc.com (8.8.8/8.8.8) with ESMTP id NAA16968 for ; Mon, 22 Jun 1998 13:39:41 -0500 (CDT) Received: (from uucp@localhost) by almond.bmc.com (8.8.8/8.8.8) id NAA21839 for ; Mon, 22 Jun 1998 13:39:39 -0500 (CDT) Received: from firewall.bmc.com(192.245.162.250) by almond.bmc.com via smap (V2.0) id xma021268; Mon, 22 Jun 98 13:37:53 -0500 Received: (from uucp@localhost) by dresden.bmc.com (8.8.5/8.8.6) id NAA00236 for ; Mon, 22 Jun 1998 13:37:20 -0500 (CDT) Received: from tangelo.bmc.com(172.17.7.166) by dresden.bmc.com via smap (3.2) id xma028553; Mon, 22 Jun 98 13:36:14 -0500 Received: from dorothy.bmc.com (dorothy.peer.com [192.146.153.65]) by tangelo.bmc.com (8.8.6 (PHNE_14041)/8.8.6) with ESMTP id NAA04698; Mon, 22 Jun 1998 13:36:43 -0500 (CDT) Received: (from rpresuhn@localhost) by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) id LAA14615 for agentx@peer.com; Mon, 22 Jun 1998 11:33:35 -0700 (PDT) Date: Mon, 22 Jun 1998 11:33:35 -0700 (PDT) From: Randy Presuhn Message-Id: <199806221833.LAA14615@dorothy.bmc.com> To: agentx@peer.com Subject: Re: agentx-Ping PDU Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Hi - > Date: Mon, 22 Jun 1998 20:06:11 > To: agentx@peer.com > From: Ashish Hanwadikar > Subject: agentx-Ping PDU ... > The AgentX RFC defines agentx-Ping PDU so that subagent can monitor > master agent's ability to send and receive agentx PDUs over a session. I > want to know whether are there any guidelines about how to use agentx-Ping > PDUs by subagent (or subagent library internally). Particularly, I want to > know the frequency and conditions under which subagent should use > agentx-Ping PDUs. One use of this PDU is in clause 6.2.11, to retrieve sysUpTime. Other than that, the guidelines for use will be environment specific. For local connections (the most common use of AgentX protocol) master agent termination is quickly detected by the loss of the underlying transport. The same could be accomplished by the use of TCP keepalives over a non-local connection, subject to all the usual admonitions about keepalives being bad for networks. Its real value is in determining whether a master agent is still (at least somewhat) working. The "when" and "why" a particular subagent would need to know will depend on the environment. > One policy I can think of is to periodically ping the master agent. And what action would be taken when a response doesn't arrive within the designated interval? > Other is when the master agent does'nt respond to subagent's agentx-notify, > agentx-register, agentx-deregister etc. PDUs within certain time period. ... Reasonable, but not quite right for notifications. Clause 7.1.11 says: | Except in the case of a `notOpen' error as described in (1) | above, no agentx-Response-PDU is sent to the subagent when the | master agent finishes processing the notification. ----------------------------------------------------------------------- Randy Presuhn Email: rpresuhn@bmc.com http://www.bmc.com Voice: +1 408 616-3100 BMC Software, Inc. 965 Stewart Drive Fax: +1 408 616-3101 Sunnyvale, California 94086 USA ----------------------------------------------------------------------- In accordance with the BMC Communications Systems Use and Security Policy, I explicitly state that although my affiliation with BMC may be apparent, implied, or provided, my opinions are not necessarily those of BMC Software and that all external representations on behalf of BMC must first be cleared with a member of "the top management team." ----------------------------------------------------------------------- From ashishkh@wipinfo.soft.net Tue Jun 23 09:40:21 1998 Return-Path: Received: from almond.bmc.com (mail-gw1.bmc.com [198.64.253.22]) by amethyst.bmc.com (8.8.8/8.8.8) with ESMTP id JAA02081 for ; Tue, 23 Jun 1998 09:40:20 -0500 (CDT) Received: (from uucp@localhost) by almond.bmc.com (8.8.8/8.8.8) id JAA10275 for ; Tue, 23 Jun 1998 09:40:19 -0500 (CDT) Received: from firewall.bmc.com(192.245.162.250) by almond.bmc.com via smap (V2.0) id xma010053; Tue, 23 Jun 98 09:39:20 -0500 Received: (from uucp@localhost) by dresden.bmc.com (8.8.5/8.8.6) id JAA20961 for ; Tue, 23 Jun 1998 09:38:49 -0500 (CDT) Received: from tangelo.bmc.com(172.17.7.166) by dresden.bmc.com via smap (3.2) id xma020597; Tue, 23 Jun 98 09:38:30 -0500 Received: from dorothy.bmc.com (dorothy.peer.com [192.146.153.65]) by tangelo.bmc.com (8.8.6 (PHNE_14041)/8.8.6) with ESMTP id JAA08378; Tue, 23 Jun 1998 09:38:55 -0500 (CDT) Received: from cashew.bmc.com (cashew.bmc.com [172.19.0.100]) by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) with ESMTP id HAA23720 for ; Tue, 23 Jun 1998 07:27:06 -0700 (PDT) Received: (from uucp@localhost) by cashew.bmc.com (8.8.8/8.8.8) id JAA19464 for ; Tue, 23 Jun 1998 09:26:55 -0500 (CDT) Received: from agni.wipinfo.soft.net(164.164.6.20) by cashew.bmc.com via smap (V2.0) id xma019413; Tue, 23 Jun 98 09:26:28 -0500 Received: from scan.wipinfo.soft.net by wipinfo.soft.net (SMI-8.6/SMI-SVR4) id PAA20020; Tue, 23 Jun 1998 15:58:24 -0500 Received: from 192.9.100.151 by scan.wipinfo.soft.net (InterScan E-Mail VirusWall NT) Received: from opel ([192.9.52.22]) by divya.wipinfo.soft.net (8.8.5/8.8.5) with SMTP id QAA09601 for ; Tue, 23 Jun 1998 16:01:57 +0530 Message-Id: <3.0.5.32.19980623155945.00914550@tagore> X-Sender: ashishkh@tagore X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.5 (32) Date: Tue, 23 Jun 1998 15:59:45 To: agentx@peer.com From: Ashish Hanwadikar Subject: Transport Mappings Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Hi all, While going through AgentX RFC I had following questions: 1) The Transport Mappings TCP and UNIX Domain Socket are compulsory or optional? The AgentX RFC just mentions the two transport Domains. However, it does not say whether the Master Agent or Sub Agents should always implement TCP or UNIX Domain Sockets. My guess is that the Transport Mappings are purely optional. If implementation of Transport Mapping are purely optional, then detection of whether master agent is running or not is difficult to be detected by the subagent library or subagent implementation. However, following algo might help: a) The sysadm knows whether Master Agent has been installed on the node or not. So, most probably he also knows the various transport mappings supported by Master Agent. Thus, he can always set some configuration parameters in the subagent library or subagent implementations giving the details of the transport mappings and their associated port etc. b) Based on the configuration information in the files, the subagent startup code tries to make transport connection with each of the transport mappings mentioned in the configuration file. c) If connections can be made to the master agent through one or more transports then it chooses the best transport mechanism available. d) Otherwise, it can either ask the user to spawn the master agent and/or log a message and exit e) One more alternative here is to include the master agent code as a separate module alongwith subagent api or code. Thus, if no master agent is available then subagent implementation can take over that responsibility. This behavior can be tailored through some parameter in the config files or whatever mechanism available. With this approach it is the sysadm's, or whoever is responsible for installation, responsibility to synchronize the configuration information of the master agent and the multiple subagent api/implementation. With this synchronization done I don't think we need to really check if the master agent or snmp agent is listening on port 161 etc. As a fallback when none of the above work, then as a last resort we can actually try using port 161 or some default agentx transport like TCP/705 etc. Thanks. With Regds., Ashish Hanwadikar Technology Solutions, Wipro Limited Bangalore-27 http://www.geocities.com/SiliconValley/Bay/5393/ Email: ashishkh@writeme.com Ph: +91-80-2241730 Ext. 3315 From rpresuhn@dorothy.bmc.com Tue Jun 23 18:56:31 1998 Return-Path: Received: from almond.bmc.com (mail-gw1.bmc.com [198.64.253.22]) by amethyst.bmc.com (8.8.8/8.8.8) with ESMTP id SAA08924 for ; Tue, 23 Jun 1998 18:56:31 -0500 (CDT) Received: (from uucp@localhost) by almond.bmc.com (8.8.8/8.8.8) id SAA14754 for ; Tue, 23 Jun 1998 18:56:30 -0500 (CDT) Received: from firewall.bmc.com(192.245.162.250) by almond.bmc.com via smap (V2.0) id xma014009; Tue, 23 Jun 98 18:54:15 -0500 Received: (from uucp@localhost) by dresden.bmc.com (8.8.5/8.8.6) id SAA28756 for ; Tue, 23 Jun 1998 18:53:42 -0500 (CDT) Received: from tangelo.bmc.com(172.17.7.166) by dresden.bmc.com via smap (3.2) id xma028104; Tue, 23 Jun 98 18:52:59 -0500 Received: from dorothy.bmc.com (dorothy.peer.com [192.146.153.65]) by tangelo.bmc.com (8.8.6 (PHNE_14041)/8.8.6) with ESMTP id SAA09956; Tue, 23 Jun 1998 18:53:27 -0500 (CDT) Received: (from rpresuhn@localhost) by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) id QAA27732 for agentx@peer.com; Tue, 23 Jun 1998 16:51:01 -0700 (PDT) Date: Tue, 23 Jun 1998 16:51:01 -0700 (PDT) From: Randy Presuhn Message-Id: <199806232351.QAA27732@dorothy.bmc.com> To: agentx@peer.com Subject: Re: Transport Mappings Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Hi - > Date: Tue, 23 Jun 1998 15:59:45 > To: agentx@peer.com > From: Ashish Hanwadikar > Subject: Transport Mappings ... > 1) The Transport Mappings TCP and UNIX Domain Socket are compulsory or > optional? > The AgentX RFC just mentions the two transport Domains. However, it does > not say whether the Master Agent or Sub Agents should always implement TCP > or UNIX Domain Sockets. > > My guess is that the Transport Mappings are purely optional. ... That'd be my reading of the current words. I'd prefer it if support for the TCP mapping were mandatory, but I can live with the current language. > If implementation of Transport Mapping are purely optional, then detection > of whether master agent is running or not is difficult to be detected by > the subagent library or subagent implementation. ... It's not THAT hard. One can use getservbyname() as well as the old "just try it" approach. One can even do this to support multiple subagent protocols over multiple transports. ... > e) One more alternative here is to include the master agent code as a > separate module alongwith subagent api or code. Thus, if no master agent is > available then subagent implementation can take over that responsibility. > This behavior can be tailored through some parameter in the config files or > whatever mechanism available. ... Deja vu. The access rights needed within a system for a master agent (for privacy/authentication keys and access control information) should not be within reach of a typical subagent. It's one thing to trigger the activation of a master agent if none is found; it's quite another to BECOME the master agent if no one else is doing the job. ----------------------------------------------------------------------- Randy Presuhn Email: rpresuhn@bmc.com http://www.bmc.com Voice: +1 408 616-3100 BMC Software, Inc. 965 Stewart Drive Fax: +1 408 616-3101 Sunnyvale, California 94086 USA ----------------------------------------------------------------------- In accordance with the BMC Communications Systems Use and Security Policy, I explicitly state that although my affiliation with BMC may be apparent, implied, or provided, my opinions are not necessarily those of BMC Software and that all external representations on behalf of BMC must first be cleared with a member of "the top management team." ----------------------------------------------------------------------- From ashishkh@wipinfo.soft.net Wed Jun 24 00:10:45 1998 Return-Path: Received: from almond.bmc.com (mail-gw1.bmc.com [198.64.253.22]) by amethyst.bmc.com (8.8.8/8.8.8) with ESMTP id AAA12881 for ; Wed, 24 Jun 1998 00:10:44 -0500 (CDT) Received: (from uucp@localhost) by almond.bmc.com (8.8.8/8.8.8) id AAA26033 for ; Wed, 24 Jun 1998 00:10:43 -0500 (CDT) Received: from firewall.bmc.com(192.245.162.250) by almond.bmc.com via smap (V2.0) id xma025446; Wed, 24 Jun 98 00:08:49 -0500 Received: (from uucp@localhost) by dresden.bmc.com (8.8.5/8.8.6) id AAA05510 for ; Wed, 24 Jun 1998 00:08:09 -0500 (CDT) Received: from tangelo.bmc.com(172.17.7.166) by dresden.bmc.com via smap (3.2) id xma004921; Wed, 24 Jun 98 00:07:22 -0500 Received: from dorothy.bmc.com (dorothy.peer.com [192.146.153.65]) by tangelo.bmc.com (8.8.6 (PHNE_14041)/8.8.6) with ESMTP id AAA08745; Wed, 24 Jun 1998 00:07:52 -0500 (CDT) Received: from almond.bmc.com (almond.bmc.com [172.17.0.100]) by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) with ESMTP id WAA29666 for ; Tue, 23 Jun 1998 22:05:15 -0700 (PDT) Received: (from uucp@localhost) by almond.bmc.com (8.8.8/8.8.8) id AAA24667 for ; Wed, 24 Jun 1998 00:05:07 -0500 (CDT) Received: from agni.wipinfo.soft.net(164.164.6.20) by almond.bmc.com via smap (V2.0) id xma024635; Wed, 24 Jun 98 00:04:58 -0500 Received: from scan.wipinfo.soft.net by wipinfo.soft.net (SMI-8.6/SMI-SVR4) id KAA01078; Wed, 24 Jun 1998 10:29:54 -0500 Received: from 192.9.100.151 by scan.wipinfo.soft.net (InterScan E-Mail VirusWall NT) Received: from opel ([192.9.52.22]) by divya.wipinfo.soft.net (8.8.5/8.8.5) with SMTP id KAA16929 for ; Wed, 24 Jun 1998 10:36:09 +0530 Message-Id: <3.0.5.32.19980624103433.00946cb0@tagore> X-Sender: ashishkh@tagore X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.5 (32) Date: Wed, 24 Jun 1998 10:34:33 To: agentx@peer.com From: Ashish Hanwadikar Subject: UNIX Domain Sockets Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Hi all, I want to know whether Microsoft NT/win95 supports UNIX Domain sockets or not. I searched for it msdn, but could not find it out. The Simple Times Article in March 1998 issue by Matt White on "An OverView of AgentX Protocol" says in "Security Issues" Subsection that "Fortunately, there are implementations of Unix domain sockets for all major platforms, including Microsoft Windows". If that is the case where can I get the implementation of UNIX domain sockets on NT/95? Thanks in advance, With Regds., Ashish Hanwadikar Technology Solutions, Wipro Limited Bangalore-27 http://www.geocities.com/SiliconValley/Bay/5393/ Email: ashishkh@writeme.com Ph: +91-80-2241730 Ext. 3315 From mwhite@andrew.cmu.edu Wed Jun 24 10:45:28 1998 Return-Path: Received: from almond.bmc.com (mail-gw1.bmc.com [198.64.253.22]) by amethyst.bmc.com (8.8.8/8.8.8) with ESMTP id KAA20694 for ; Wed, 24 Jun 1998 10:45:28 -0500 (CDT) Received: (from uucp@localhost) by almond.bmc.com (8.8.8/8.8.8) id KAA25882 for ; Wed, 24 Jun 1998 10:45:26 -0500 (CDT) Received: from firewall.bmc.com(192.245.162.250) by almond.bmc.com via smap (V2.0) id xma025667; Wed, 24 Jun 98 10:44:50 -0500 Received: (from uucp@localhost) by dresden.bmc.com (8.8.5/8.8.6) id KAA11236 for ; Wed, 24 Jun 1998 10:44:17 -0500 (CDT) Received: from tangelo.bmc.com(172.17.7.166) by dresden.bmc.com via smap (3.2) id xma010027; Wed, 24 Jun 98 10:43:17 -0500 Received: from dorothy.bmc.com (dorothy.peer.com [192.146.153.65]) by tangelo.bmc.com (8.8.6 (PHNE_14041)/8.8.6) with ESMTP id KAA00975; Wed, 24 Jun 1998 10:43:39 -0500 (CDT) Received: from almond.bmc.com (almond.bmc.com [172.17.0.100]) by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) with ESMTP id IAA02147 for ; Wed, 24 Jun 1998 08:37:12 -0700 (PDT) Received: (from uucp@localhost) by almond.bmc.com (8.8.8/8.8.8) id KAA24340 for ; Wed, 24 Jun 1998 10:37:09 -0500 (CDT) Received: from cmu1.acs.cmu.edu(128.2.35.186) by almond.bmc.com via smap (V2.0) id xma024323; Wed, 24 Jun 98 10:36:50 -0500 Received: from freehold.net.cmu.edu (FREEHOLD.NET.CMU.EDU [128.2.6.69]) by cmu1.acs.cmu.edu (8.8.5/8.8.5) with SMTP id LAA20936; Wed, 24 Jun 1998 11:33:04 -0400 (EDT) Date: Wed, 24 Jun 1998 11:33:03 -0400 (EDT) From: Matthew White X-Sender: mwhite@freehold.net.cmu.edu To: Ashish Hanwadikar cc: agentx@peer.com Subject: Re: UNIX Domain Sockets In-Reply-To: <3.0.5.32.19980624103433.00946cb0@tagore> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Ashish: The Cygnus GCC for windows supports unix domain sockets. You can get more information from http://www.cygnus.com/. -Matt On Wed, 24 Jun 1998, Ashish Hanwadikar wrote: > Hi all, > I want to know whether Microsoft NT/win95 supports UNIX Domain > sockets or not. I searched for it msdn, but could not find it out. The > Simple Times Article in March 1998 issue by Matt White on "An OverView of > AgentX Protocol" says in "Security Issues" Subsection that "Fortunately, > there are implementations of Unix domain sockets for all major platforms, > including Microsoft Windows". > If that is the case where can I get the implementation of UNIX domain > sockets on NT/95? > Thanks in advance, > > With Regds., > Ashish Hanwadikar > Technology Solutions, > Wipro Limited > Bangalore-27 > http://www.geocities.com/SiliconValley/Bay/5393/ > Email: ashishkh@writeme.com > Ph: +91-80-2241730 Ext. 3315 > > ---------- Matt White Network Systems Designer Carnegie Mellon Computing Services From daniele@zk3.dec.com Thu Jun 25 12:41:54 1998 Return-Path: Received: from almond.bmc.com (mail-gw1.bmc.com [198.64.253.22]) by amethyst.bmc.com (8.8.8/8.8.8) with ESMTP id MAA10047 for ; Thu, 25 Jun 1998 12:41:54 -0500 (CDT) Received: (from uucp@localhost) by almond.bmc.com (8.8.8/8.8.8) id MAA10599 for ; Thu, 25 Jun 1998 12:41:53 -0500 (CDT) Received: from firewall.bmc.com(192.245.162.250) by almond.bmc.com via smap (V2.0) id xma010273; Thu, 25 Jun 98 12:40:33 -0500 Received: (from uucp@localhost) by dresden.bmc.com (8.8.5/8.8.6) id MAA26675 for ; Thu, 25 Jun 1998 12:40:00 -0500 (CDT) Received: from tangelo.bmc.com(172.17.7.166) by dresden.bmc.com via smap (3.2) id xma026308; Thu, 25 Jun 98 12:39:43 -0500 Received: from dorothy.bmc.com (dorothy.peer.com [192.146.153.65]) by tangelo.bmc.com (8.8.6 (PHNE_14041)/8.8.6) with ESMTP id MAA02731; Thu, 25 Jun 1998 12:40:09 -0500 (CDT) Received: from cashew.bmc.com (cashew.bmc.com [172.19.0.100]) by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) with ESMTP id KAA16172 for ; Thu, 25 Jun 1998 10:25:23 -0700 (PDT) Received: (from uucp@localhost) by cashew.bmc.com (8.8.8/8.8.8) id MAA08198 for ; Thu, 25 Jun 1998 12:25:23 -0500 (CDT) Received: from mail11.digital.com(192.208.46.10) by cashew.bmc.com via smap (V2.0) id xma008191; Thu, 25 Jun 98 12:25:03 -0500 Received: from quarry.zk3.dec.com (fquarry.zk3.dec.com [16.140.160.9]) by mail11.digital.com (8.8.8/8.8.8/WV1.0f) with SMTP id NAA27472 for ; Thu, 25 Jun 1998 13:24:57 -0400 (EDT) Received: from bernie.zk3.dec.com by quarry.zk3.dec.com; (5.65v4.0/1.1.8.2/16Jan95-0946AM) id AA17978; Thu, 25 Jun 1998 13:24:56 -0400 Received: from localhost by bernie.zk3.dec.com; (5.65/1.1.8.2/22Aug96-1117AM) id AA04982; Thu, 25 Jun 1998 13:24:57 -0400 Message-Id: <9806251724.AA04982@bernie.zk3.dec.com> To: agentx@peer.com Subject: Testing: some early results and net availability Date: Thu, 25 Jun 98 13:24:57 -0400 From: Mike Daniele X-Mts: smtp Hi, We've done some testing of DEC's subagent library vis a vis Peer/BMC's master agent. In general, the news is good. We've been able to open a session, register multiple regions, and have some SNMP Get and GetNext requests handled correctly end to end. I wanted to note 2 things that might help avoid problems for others: 1) SearchRange ending OID Cannot be identical to the SearchRange starting OID. 7.2.2.2 states that for next/bulk, a subagent must return a variable such that > - If the ending OID is not null, the variable's name > lexicographically precedes the ending OID. If the SearchRange's ending oid == its starting oid, the subagent can't legally return anything. 2) Register PDU's optional range upper bound (r.upper_bound) This field is present only if r.range_subid is non-zero. If r.range_subid is 0, the PDU ends with r.region. It does NOT contain (a 0-valued) r.upper_bound in this case. Note to editors: We should discuss r.upper_bound in sections 6.2.3 and 6.2.4 in a separate paragraph, just like we do with all the other fields. We should also include an example that has no upper bound. We have master and subagents available for testing (via TCP over the internet) if other folks are interested in doing so before the bakeoff. Thanks Lauren @ BMC, the testing so far has been very valuable. Regards, Mike From bnatale@acecomm.com Tue Jun 30 11:04:02 1998 Return-Path: Received: from almond.bmc.com (mail-gw1.bmc.com [198.64.253.22]) by amethyst.bmc.com (8.8.8/8.8.8) with ESMTP id LAA19452 for ; Tue, 30 Jun 1998 11:04:02 -0500 (CDT) Received: (from uucp@localhost) by almond.bmc.com (8.8.8/8.8.8) id LAA14503 for ; Tue, 30 Jun 1998 11:03:54 -0500 (CDT) Received: from firewall.bmc.com(192.245.162.250) by almond.bmc.com via smap (V2.0) id xma014205; Tue, 30 Jun 98 11:03:10 -0500 Received: (from uucp@localhost) by dresden.bmc.com (8.8.5/8.8.6) id LAA21487 for ; Tue, 30 Jun 1998 11:02:37 -0500 (CDT) Received: from tangelo.bmc.com(172.17.7.166) by dresden.bmc.com via smap (3.2) id xma020843; Tue, 30 Jun 98 11:02:06 -0500 Received: from dorothy.bmc.com (dorothy.peer.com [192.146.153.65]) by tangelo.bmc.com (8.8.6 (PHNE_14041)/8.8.6) with ESMTP id LAA14446; Tue, 30 Jun 1998 11:02:25 -0500 (CDT) Received: from almond.bmc.com (almond.bmc.com [172.17.0.100]) by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) with ESMTP id IAA18530 for ; Tue, 30 Jun 1998 08:43:43 -0700 (PDT) Received: (from uucp@localhost) by almond.bmc.com (8.8.8/8.8.8) id KAA11264 for ; Tue, 30 Jun 1998 10:43:41 -0500 (CDT) Received: from relay2.smtp.psi.net(38.8.188.2) by almond.bmc.com via smap (V2.0) id xma011245; Tue, 30 Jun 98 10:43:11 -0500 Received: from [192.152.208.5] (helo=acecomm.com) by relay2.smtp.psi.net with smtp (Exim 1.90 #1) for agentx@peer.com id 0yr2YW-0000bN-00; Tue, 30 Jun 1998 11:42:58 -0400 Received: from bnatale by acecomm.com (5.65/3.2.083191-ACE*COMM) id AA06228; Tue, 30 Jun 1998 11:45:00 -0400 Message-Id: <9806301545.AA06228@acecomm.com> X-Sender: natale@nips.acec.com X-Mailer: QUALCOMM Windows Eudora Pro Version 4.0 Date: Tue, 30 Jun 1998 11:44:41 -0400 To: agentx@peer.com From: Bob Natale Subject: Updated goals and milestones Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hi, The AgentX page at www.ietf.org has been updated with= the following: Goals and Milestones: Done Publication of AgentX protocol specification Done Submit working draft version of AgentX MIB I-D. Jun 98 Collect and evaluate implementation reports (through bake-off). Jul 98 Conduct AgentX interoperability testing (July 23-24, Sunnyvale). Aug 98 Meet at 42nd IETF-Chicago (refine or revise RFC 2257). Sep 98 Petition IESG to advance RFC 2257 to Draft or recycle at Proposed Oct 98 Submit final version of AgentX MIB I-D to IESG for consideration as Proposed. Nov 98 Submit initial draft version of AgentX API I-D Dec 98 Submit interim draft version of AgentX API I-D. Jan 99 Submit final version of AgentX API I-D to IESG for consideration as an Informational RFC. Feb 99 Evaluate necessary revisions to RFC 2257. Feb 99 Evaluate necessary revisions to AgentX MIB RFC. Mar 99 Meet at 44th IETF to Assess status of AgentX deployment Determine need for AgentX v2 (Protocol, MIB, or API) Plan future work items accordingly. Apr 99 Submit new charter proposal to IESG or retire WG. I have submitted a request for a single 2hr meeting slot in Chicago...I have not yet received notification of the scheduled time and place. The basic agenda will include: - the usual preliminaries - review implementation status reports - review bake-off results, findings - review list of open issues - review status of AgentX MIB - review need/desire for a standard AgentX API - review status of SNMPv3 and DISMAN wrt AgentX - recommend working plan wrt any of the above items - the usual summaries Comments on any of the above are welcomed...as are proposed mods (additions/deletions/changes) to the agenda outline. Cordially, BobN ------------ ISO 9001 Registered Quality Supplier ----------- Bob Natale=A0=A0=A0=A0=A0=A0=A0=A0 | ACE*COMM=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0= =A0=A0=A0 | 301-721-3000 [v] Dir, Net Mgmt Prod | 704 Quince Orchard Rd | 301-721-3001 [f] bnatale@acecomm.com| Gaithersburg MD 20878 | www.acecomm.com ------------- Free downloads at www.winsnmp.com -------------