From ashishkh@wipinfo.soft.net Wed Oct 7 09:26:11 1998 Return-Path: Received: from tangelo.bmc.com ([172.17.7.166]) by amethyst.bmc.com (8.8.8/8.8.8) with ESMTP id JAA17999 for ; Wed, 7 Oct 1998 09:26:10 -0500 (CDT) 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 JAA04808; Wed, 7 Oct 1998 09:12:00 -0500 (CDT) Received: from tangelo.bmc.com (root@tangelo.bmc.com [172.17.7.166]) by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) with ESMTP id HAA11367 for ; Wed, 7 Oct 1998 07:08:42 -0700 (PDT) Received: from fw-us-hou1.bmc.com (fw-us-hou1.bmc.com [172.17.0.250]) by tangelo.bmc.com (8.8.6 (PHNE_14041)/8.8.6) with SMTP id JAA03606 for ; Wed, 7 Oct 1998 09:08:36 -0500 (CDT) Received: from scan.wipinfo.soft.net by donald.wipinfo.soft.net (SMI-8.6/SMI-SVR4) id TAA15177; Wed, 7 Oct 1998 19:41:41 -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 TAA04551; Wed, 7 Oct 1998 19:39:29 +0530 From: "Ashish Hanwadikar" To: "Bob Natale" Cc: "Agentx" Subject: RE: AgentX Registration/Deregistration Date: Wed, 7 Oct 1998 19:38:29 +0530 Message-ID: <002401bdf1fb$f5f918f0$163409c0@opel.wipinfo.soft.net> MIME-Version: 1.0 X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook 8.5, Build 4.71.2173.0 Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V4.72.2106.4 In-Reply-To: <9808072209.AA06108@acecomm.com> Content-Type: multipart/mixed; boundary="----=_NextPart_000_0025_01BDF22A.0FB154F0" This is a multi-part message in MIME format. ------=_NextPart_000_0025_01BDF22A.0FB154F0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit -----Original Message----- From: Bob Natale [mailto:bnatale@acecomm.com] Sent: Saturday, August 08, 1998 3:39 AM To: Shawn A. Routhier Cc: agentx@peer.com Subject: Re: AgentX Registration/Deregistration >At 8/7/98 04:59 PM, Shawn A. Routhier wrote: Hi Shawn, <...> >I think, but am not sure, that you missed my point. Perhaps...if so, I apologize. (Trying to get a bunch of things done before heading out for a week's worth of vacation! :-) >The words in the current draft "...implements objects >starting at this value" (agentxRegStart) and "...implements >objects up to but not including this value" (agentxRegEnd) >cover all of the objects from the first to the last even if >the registration request had holes in it due to specifying >objectids after the range. For a concrete example, assume >a sub agent registers ifentry.{1--22}.1, the above words >would also imply that the range covers ifentry.1.2, >ifentry.1.3 etc. Hmmm. I failed to make that interpretation of those words...and still do. I believe the various descriptions we give of such range registrations include a phrase like "for example, to register an entire row in some table".... >I don't think that's what we want. Right...but I think I've just seen the possible source of the different readings you and I are making. I read (into it, perhaps) that the INSTANCE_REGISTRATION bit was set on the associated agentx-Register-PDU operation and, therefore, I use the .22 subid as the one to increment and my agentxRegEnd value becomes ifEntry.23[.1]. That is, I treat the instance part as a logical suffix not as part of the ending object name itself. Well, take the following case: Agent #1 registers ifEntry.[1-22].1 and Agent #2 registers ifEntry.[1-22].2. Then how do we maintain agentxRegStart and agentxRegEnd for the two regions. It will look like start end Region #1 ifEntry.1.1 ifEntry.23.1 Region #2 ifEntry.1.2 ifEntry.23.2 Now, for a SNMP Get Request for ifEntry.1.2, two regions contain ifEntry.1.2. Both have same length (no one is more specific than the other). Whoever was registered with higher priority will get AgentX Get Request. The algorithm for AgentX GET pdu dispatching does not say anything about such conditions. Eventhough, implicitly, the region #2 should honor the request because it handles the entries with suffix 2 (if instance registration flag is set, the suffix can be called as index). In fact, it says little about regions with range_subid. It does not mention such regions in dispatching nor in the registration algorithms. I think meaning of region with range_subid should be made very very clear in the RFC. >I don't believe we need to change the objects in the mib, >only the wording of the description to make it clear which >elements are included in a range. Ok...if I'm right about the source of our different readings, then I think we need to change both the MIB description text, as you say, and perhaps add some clarifying text to RFC 2257, Section 6.2.3, "The agentx-Register-PDU", as (I think) might have been recommended by someone else earlier (this concerns "The master agent may save this information to optimize subsequent operational dispatching."). If you have any candidate text for either place, please post it. >I also think the concept of having a scheme that won't work >correctly for certain values of subids (2^^32-1) is suspect >and would prefer to see some other option. In general, I agree with you (I think I noted this in an earlier posting [but might have opted to leave it out for some wrong reasons!]). However, it's not really "certain values"; it's only one value it's not unheard of to allow for "special processing" on a single boundary value. Granted, again, it's not the most beautiful way in the world to do it. > It MUST be rejected, per the u.region test in RFC 2257 Sec. 7.1.6, > Processing the agentx-Unregister-PDU: > > "4) If u.region, u.priority, and the indicated context do not match > an existing registration made during this session, the agentx- > Response-PDU is returned with res.error set to > 'unknownRegistration'." > >I think there are different ways of reading that. When registering, >a request that has a range included may be viewed as either a single >blob or a range of regions to register. You are taking the former >view. I do not believe the current wording prohibits the latter view. >In the latter case if u.region was one of the regions registered then >it would be valid to unregister it. Note that u.region would be >matched against r.region and that the range information is NOT carried >in the *.region fields. Literally true...but the range info is carried in the PDU with the *.region info in both cases and is a virtual extension of those fields. I wouldn't mind adding more clarifying text [and I hope you will propose what you think will work best], but I would not like to have the meaning changed to allow for such "subset" deregistrations. 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 ------------- Ashish K Hanwadikar Senior Software Engineer, Wipro Infotech, Technology Solutions, Bangalore INDIA ------=_NextPart_000_0025_01BDF22A.0FB154F0 Content-Type: text/x-vcard; name="Ashish K Hanwadikar.vcf" Content-Transfer-Encoding: quoted-printable Content-Disposition: attachment; filename="Ashish K Hanwadikar.vcf" BEGIN:VCARD VERSION:2.1 N:Hanwadikar;Ashish;K;; FN:Ashish K Hanwadikar ORG:Wipro Infotech, Technology Solutions;Technology Solutions TITLE:Senior Software Engineer TEL;WORK;VOICE:+91-80-2241730 Ext. 3315 TEL;HOME;VOICE:+91-80-2241730 Ext. 3315 ADR;WORK:;Mission Road LABEL;WORK:Mission Road ADR;HOME;ENCODING=3DQUOTED-PRINTABLE:;;Wipro Limited=3D0D=3D0A30 Mission = Road,=3D0D=3D0A1st Main,=3D0D=3D0AS.R. Nagar;Bangalo=3D re;Karnataka;560 027;INDIA LABEL;HOME;ENCODING=3DQUOTED-PRINTABLE:Wipro Limited=3D0D=3D0A30 Mission = Road,=3D0D=3D0A1st Main,=3D0D=3D0AS.R. Nagar=3D0D=3D0ABang=3D alore, Karnataka 560 027=3D0D=3D0AINDIA URL:http://www.geocities.com/SiliconValley/Bay/5393/ URL:http://www.geocities.com/SiliconValley/Bay/5393 EMAIL;PREF;INTERNET:ashishkh@wipinfo.soft.net REV:19980630T133122Z END:VCARD ------=_NextPart_000_0025_01BDF22A.0FB154F0-- From cyberink@ink-refills.com Mon Oct 12 01:43:45 1998 Return-Path: Received: from tangelo.bmc.com ([172.17.7.166]) by amethyst.bmc.com (8.8.8/8.8.8) with ESMTP id BAA21555 for ; Mon, 12 Oct 1998 01:43:44 -0500 (CDT) 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 BAA28940; Mon, 12 Oct 1998 01:41:13 -0500 (CDT) Received: from tangelo.bmc.com (root@tangelo.bmc.com [172.17.7.166]) by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) with ESMTP id XAA12036 for ; Sun, 11 Oct 1998 23:36:19 -0700 (PDT) Received: from fw-us-hou1.bmc.com (fw-us-hou1.bmc.com [172.17.0.250]) by tangelo.bmc.com (8.8.6 (PHNE_14041)/8.8.6) with SMTP id BAA28266 for ; Mon, 12 Oct 1998 01:36:17 -0500 (CDT) Message-Id: <199810120636.BAA28266@tangelo.bmc.com> Date: Mon, 12 Oct 1998 02:25:07 -0400 (EDT) From: "cyberink@ink-refills.com" Subject: ADV: printer REFILL KITS - save to 80% Netwares & Specialties You may choose to PO BOX 309 be removed from this Vestal, NY 13850 targeted list by selecting 607 - 754 - 9378 reply and put REMOVE in subject <><><><><><><><><><><><><><><> STOP BUYING those EXPENSIVE printer cartridges <><><><><><><><><><><><><><><> ************************************************* Use our complete REFILL KITS for INKJET printers and SAVE 50-80% over new cartridges. (as little as $1.50 per refill) ************************************************** ************************************************** Don't want to REFILL - NO PROBLEM ... Buy compatible cartridges and SAVE up to 60%. *************************************************** xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx ALL READY refilling - GREAT! check out our super deals on premium bulk ink and extra discounts on special BULK INK PACKAGES. xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx <><><><><><><><><><><><><><><><><> Have a fax, copier or laser? SAVE up to 50% on refurbished TONER CARTRIDGES delivered to your door. <><><><><><><><><><><><><><><><><> *************************************** ALL PRODUCTS have a 90 day 100% GUARANTEE *************************************** FREE OFFER -Check our website. We usually are offering something for FREE ... sometimes ink cartridges, sometimes ink - sometimes something totally unrelated. SEE FOR YOURSELF! <><><> FOR MORE INFO <><><> on these products: CLICK REPLY and put MORE INFO in subject or DOUBLE-CLICK BELOW: CLICK HERE NOW and put MORE INFO in the subject (HINT: for copy and paste) 1. put your mouse cursor in front of M in MORE INFO, left click and hold while dragging cursor across MORE INFO to highlight it. 2. Then right click mouse to get a drop down box and select copy. 3. Then double click on "CLICK HERE NOW" or on the mail address starting with "mailto:" and put mouse cursor in Subject box. 4. Right click mouse to get drop down box and select Paste. From Barb@resumeblaster.com Mon Oct 12 12:47:38 1998 Return-Path: Received: from tangelo.bmc.com ([172.17.7.166]) by amethyst.bmc.com (8.8.8/8.8.8) with ESMTP id MAA26749 for ; Mon, 12 Oct 1998 12:47:38 -0500 (CDT) From: Barb@resumeblaster.com 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 MAA12468; Mon, 12 Oct 1998 12:45:41 -0500 (CDT) Received: from tangelo.bmc.com (root@tangelo.bmc.com [172.17.7.166]) by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) with ESMTP id KAA00820 for ; Mon, 12 Oct 1998 10:43:42 -0700 (PDT) Received: from fw-us-hou1.bmc.com (fw-us-hou1.bmc.com [172.17.0.250]) by tangelo.bmc.com (8.8.6 (PHNE_14041)/8.8.6) with SMTP id MAA11924 for ; Mon, 12 Oct 1998 12:43:40 -0500 (CDT) Received: from 209.74.180.90 - 209.74.180.90 by spider2.merchantweb.net with Microsoft SMTPSVC(5.5.1774.114.11); Mon, 12 Oct 1998 12:45:59 -0500 To: agentx@peer.com Subject: Your Resume Date: Mon, 12 Oct 1998 12:45:59 -0500 X-Mailer: Allaire Cold Fusion 3.1 Message-ID: <01cba5945170ca8SPIDER2@spider2.merchantweb.net> Hello, You are receiving this letter because your e-mail address has appeared on a resume on the Internet. If you are not interested in what this letter has to offer, please delete it and accept our apologies. You will not receive any future mailings from us. You are NOT on a mailing list. If you happen to be a recruiter, you can be added to our Blast List by sending an e-mail with SUBSCRIBE in the body to: subscribe@resumeblaster.com. What is Resume Blaster? Read on... It's well known information that many people are getting their new jobs through the Internet. * Are you looking for a new job opportunity or do you know someone who is? * Are you interested in seeing what kind of jobs are available out there? * What's the most effective way to get a new job in today's world? . Recruiting Agencies. The best way to market yourself for a new job is to get your resume in front of as many recruiters as possible. That's where we come in. We offer an inexpensive service to BLAST your resume to over 1,000 recruiters online. In fact, our current subscribed recruiter count totals 2,516! This will get your resume MAXIMUM EXPOSURE. If you are a qualified professional, it shouldn't be long before you have the recruiters knocking down your door trying to get you a job. Recruiters WANT to place you in a job. That's how they make money. You can see a breakdown of recruiter counts and the geographical areas they serve on our web site! Now why wouldn't you just put your resume out on the web or in the newsgroups. Well think about all the people that will have access to your name, address, phone number, employment history....get the picture? That is, in no way, confidential. However, WE do NOT put your resume on the Web in ANY format whatsoever. We e-mail your resume DIRECTLY to over 1,000 recruiters. No need to worry about your personal information floating around the world for junk e-mailers, and even worse, criminals, to see. How much should a service like this cost? Well, postage alone on 1,000 resumes would be $320. What about the cost on the envelopes, paper, and the time to print, fold, stamp, address, and lick 1,000 envelopes? That time is priceless. We have many services starting as low as $49! To sign up, visit our site at: http://www.resumeblaster.com/ir121 For more info....read on: Okay then, how about you send it to them yourself. Do you know how much time it takes to locate 1,000 e-mail addresses of recruiters on the Internet AND verify that they are all up to date? The time for that alone would probably cost you much more than this service. In fact, don't forget the time it would take to address the e-mails and send your resume to EACH of the 1,000 recruiting agencies. We will put together all the information you provide us in a candidate profile. This information is sent with your resume and is expected by the recruiters. They have asked for this information and it is helpful to them to determine if you might possibly fit one of their positions. Also, this gives them the information they're looking for UP FRONT to better match you with jobs they have available. This way, hopefully, they don't waste your time with a phone call or e-mail unless they have something for you. You even get to pick whether you prefer them to contact you via e-mail or telephone! This service should cost more than $100, but it's less than that...and no, it's not $99. It's even as low as less than $50! To find out more, including the cost, visit our website. It's short, simple, and to the point. No fancy graphics or animated buzzards flying over dead bodies or little guys with jackhammers saying "we're under construction" and there's not even any flying envelopes or haunted mailboxes. And if you're not looking for a new opportunity right now, please pass this message on to someone who is. Odds are you know at least ONE person who could benefit from this type of service. Do THEM a service and send them this e-mail! Our site is located at: http://www.resumeblaster.com/ir121 Click here to go directly to our site: Resume Blaster! (If you see the HTML code above, just ignore it. Some e-mail programs display it, some don't.) Come and visit us. Even if you're not going to use the service, give us some feedback on it! Sincerely, Barbara Bechtold Customer Response Manager Resume Blaster! a service of PC Pros, Inc. Barb@resumeblaster.com http://www.resumeblaster.com/ir121 From poc@searchengine-secrets.com Wed Oct 14 17:39:26 1998 Return-Path: Received: from tangelo.bmc.com ([172.17.7.166]) by amethyst.bmc.com (8.8.8/8.8.8) with ESMTP id RAA22354 for ; Wed, 14 Oct 1998 17:39:25 -0500 (CDT) From: poc@searchengine-secrets.com 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 RAA21101; Wed, 14 Oct 1998 17:35:31 -0500 (CDT) Received: from tangelo.bmc.com (root@tangelo.bmc.com [172.17.7.166]) by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) with ESMTP id PAA14005 for ; Wed, 14 Oct 1998 15:31:04 -0700 (PDT) Received: from fw-us-hou1.bmc.com (fw-us-hou1.bmc.com [172.17.0.250]) by tangelo.bmc.com (8.8.6 (PHNE_14041)/8.8.6) with SMTP id RAA20005 for ; Wed, 14 Oct 1998 17:31:02 -0500 (CDT) Message-Id: <199810142231.RAA20005@tangelo.bmc.com> To: Subject: Your Web Site location Date: Wed, 14 Oct 1998 09:04:38 Would you like to improve your web site's position on the Search Engines? Over the past two years we've been acknowledged by Internet Experts as the definitive source for information on how to obtain top placement on the major search engines. My name is Stephen Mahaney. I am the president of Planet Ocean Communications. My web marketing company has literally "written the book" on how to position your website on the front page -- the Top Ten -- of each of the major search engines... and we guarantee your satisfaction! The "UnFair Advantage Book on Winning the Search Engine Wars" is an 85 page manual that identifies every known trick & technique being used on the Internet to gain top search engine positioning -- right where you need to be so that potential customers who are seeking your services or products can find you. Our monthly "Search Engine Wars Update Newsletter" keeps you informed of the latest techniques and frequent changes that take place in the dynamic world of "search engine" positioning. However, understanding the process does not require a degree in "rocket" science -- nor do you need to be "technically oriented". Whether your website is a "do-it-yourself" project or you are paying someone to maintain your site, you (or your webmaster) need to know the tricks in this book in order to compete with the professionals who are dominating the front pages of the various search categories. To learn more about how you can obtain this essential information and receive a free subscription to our monthly update Newsletter, go to.... http://www.searchengine-secrets.com/advantage Sincerely, Stephen Mahaney - President Planet Ocean Communications *************************************************** Note: We have contacted you based on information that we gathered while visiting your website - If you would prefer not to receive mail from us in the future, simply reply with the word "remove" in the subject line and you will be automatically excluded from future correspondence. *************************************************** From traffic66@hotmail.com Thu Oct 22 19:30:59 1998 Return-Path: Received: from tangelo.bmc.com ([172.17.7.166]) by amethyst.bmc.com (8.8.8/8.8.8) with ESMTP id TAA04792 for ; Thu, 22 Oct 1998 19:30:59 -0500 (CDT) From: traffic66@hotmail.com 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 TAA21214; Thu, 22 Oct 1998 19:29:44 -0500 (CDT) Received: from tangelo.bmc.com (root@tangelo.bmc.com [172.17.7.166]) by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) with ESMTP id RAA20201; Thu, 22 Oct 1998 17:26:04 -0700 (PDT) Received: from fw-us-hou1.bmc.com (fw-us-hou1.bmc.com [172.17.0.250]) by tangelo.bmc.com (8.8.6 (PHNE_14041)/8.8.6) with SMTP id TAA20638; Thu, 22 Oct 1998 19:26:02 -0500 (CDT) Date: Thu, 22 Oct 1998 19:26:02 -0500 (CDT) Message-Id: <199810230026.TAA20638@tangelo.bmc.com> Received: from default ([154.11.101.179]) by rainier.RAINIERINDUSTRIES.COM; Thu, 22 Oct 1998 17:32:25 -0700 To: traffic66@hotmail.com Subject: Increase Your Website Traffic Within 72 Hours! Increase Your Website Traffic Within 72 Hours! We'll put YOUR website at the top of the search engines! If your site isn't getting the traffic it should, chances are it's because it's not ranked well on the major Internet search engines. According to recent studies on Internet commerce, over 90% of consumers find the websites they visit by using "The Big Eight" search engines. If your website isn't located in the top 30 listings of these engines, chances are your site will never be seen. What's the point of having an "invisible" website? The SINGLE most important thing you can do increase your website traffic is to increase your search engine rank. That's what we'll do for you. HUGE RESULTS... LITTLE EFFORT... You can spend hours marketing your site using every technique around, but they'll all pale in comparison to getting your site properly ranked. By getting to the top of the search engines, you can have HUGE amounts of visitors at your site in as little as 72 HOURS! HOW THE SEARCH ENGINES RANK YOUR SITE... When you submit your website to a search engine to be indexed in its database, it sends a "robot" out to scan your page. Then, using complex algorithms to rank your page for keyword relevance, the "robot" determines whether you'll be ranked # 1 or 1,000,000 when potential visitors conduct a search looking for sites like yours. Because the search engines are constantly changing their algorithms to help provide users the best possible search results, there's only one true solution to high search engine placement. Us. WIN THE SEARCH ENGINE WARS! We understand these algorithms and will use them very ethically and legitimately to get your website on top. Now you can experience the on-line success you originally built your website for. If you're not happy with your website's performance, let The Search Engine Success Group put YOU on top. IT WILL BE THE BEST THING YOU EVER DO TO IMPROVE YOUR ON-LINE SUCCESS. HERE'S WHAT WE DO... In order to counter the ever changing search engine algorithms, we create an entire series of "entry pages" that is optimized for the search engines - one for EVERY keyword you give us! Each entry page is optimized to do well for a different set of algorithm variables. So instead of having ONE page struggling to rank well, we simply create separate entry pages for each keyword! It's through this unique approach that we're able to help YOU conquer the search engines. Now understand, we don't use "tricks" to fool the engines. That's unethical and something we won't do. After all - it's your reputation we have to protect. What we will do is simply present very relevant keywords for your site to the search engines in the way that they like to see it. As a result, your pages rank well because they DO contain information HIGHLY relevant to the search query. We NEVER build pages for irrelevant yet "popular" keywords. The "entry pages" act as a welcome screen for your website. They will say a few introductory things about your site and then ask the visitor to "Click Here To Enter," taking them directly to your current homepage. In creating these entry pages we DO NOT make any changes to the existing structure, content, or functionality of your current site. All pages we construct will link directly into your existing site. As a result, you can rest assured that your current website will remain exactly the same. HOW WELL DOES THE SERVICE WORK? We'll send you a detailed report of your current search engine ranking onThe Big Eight engines before we begin. Then, once your new entry pages havebeen indexed, we'll send you a second report showing how they've done. You'll be able to confirm the results yourself. Here's a sampling of some results we've gotten for previous clients. These examples are for COMPETITIVE keywords - not obscure words that nobody's looking for... <> 6 top 10 rankings on Infoseek for DIFFERENT relevant keywords <> 18 top 10 rankings across the major search engines <> 3 top 10 rankings on Alta Vista for ONE keyword <> 16 total #1 rankings (and an astounding 40 top 30 rankings across the different engines!!) <> 1-2 hits per week exploded to 500 per day <> 45,000 hits per month grew to 108,000... (and it's still growing!) CLIENT COMMENTS: "INCREDIBLE!! Our site is now receiving more hits in a day than we used to get in an entire month. [My boss] is still eating his words!" -Bob W. "I knew the search engines were an incredible marketing tool, but my company simply didn't have the time to devote to search engine placement. It has proven to be the best money we've ever spent on marketing. We'll be sending you some referrals for sure! Thanks." -Shelley H. "I worked for weeks to get good search engine placement, but I could never crack the top 80...my site was deserted. Within a month [after using your service], I'd had more hits than I'd had in the last year. I wouldn't believe it if it hadn't happened to me. Please don't mention a word to the competition." -Chris L. WHAT'S THE COST? Our services are just $385. This includes: <> Construction of optimized entry pages for up to 20 keywords - This gives you good "coverage" <> Submission to the major search engines <> A complete report of your search engine rankings before we begin <> A complete report of your search engine rankings AFTER we've finished ****BE SURE TO ASK US HOW TO GET LISTED ON YAHOO!**** WHAT DO I NEED TO DO TO GET STARTED? <> Call Us - we'll answer any questions. <> Give us your keywords / keyword phrases (up to 20) <> Pay us $385 <> Sit back and enjoy the show! Your confidentiality is assured; we NEVER release any information about our clients. --Search Engine Success Group-- 410-783-8269 *** Remember - our job is to increase your website's rank. That's what we do. We can't guarantee, however, that this will increase the number of visitors you get. Some highly-ranked websites still don't get much traffic. Much depends on your particular industry and choice of keywords. ----------------------- If you're not interested in any potential future offers, just click reply. Thank you. From hire@hiredhits.com Tue Oct 27 19:09:52 1998 Return-Path: Received: from tangelo.bmc.com ([172.17.7.166]) by amethyst.bmc.com (8.8.8/8.8.8) with ESMTP id TAA08883 for ; Tue, 27 Oct 1998 19:09:52 -0600 (CST) From: hire@hiredhits.com 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 TAA00129; Tue, 27 Oct 1998 19:05:42 -0600 (CST) Received: from tangelo.bmc.com (root@tangelo.bmc.com [172.17.7.166]) by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) with ESMTP id RAA00224; Tue, 27 Oct 1998 17:00:44 -0800 (PST) Received: from fw-us-hou1.bmc.com (fw-us-hou1.bmc.com [172.17.0.250]) by tangelo.bmc.com (8.8.6 (PHNE_14041)/8.8.6) with SMTP id TAA28872; Tue, 27 Oct 1998 19:00:42 -0600 (CST) DATE: Tue, 27 Oct 1998 19:13:01 -0600 Message-ID: Subject: FREE DEMO of Software That Puts You On OVER 1000 Search Engines! To: $user@peer.com MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Greetings! I thought I would take some time today to let you know about a wonderful new software package that will dramatically increase your web site's visibility. It's called The Spider, and I have been using it for several months and enjoyed a tremendous increase in my website's traffic. This software has impressed me so much that I decided to buy the reseller rights to it. And now, we are offering it on a FREE DEMO basis. Before I let you in on our secret download location, let me tell you a bit more about it. 1) 1000 + Supported Search Engines (Pro), 450 for standard edition 2) Batch Processing - allows you to take control of your website promotions - for all of your pages and sites. With a built in on-board database and batch processing, you can accurately register as many sites or pages as you like, all at once. 3) Categorized submissions - accuracy is critical when placing your site; our program recognizes and properly places you in all of our supported search engines. Don't be fooled by the competition - the shotgun approach does not work! 4) True CGI based registration - while other programs simply email your site information to search engine webmasters in the vain hope they will manually enter your information, The Search Engine Spider interacts with the server directly, custom formatting your site information for each and every supported engine. 5) Small Size, Fast Execution : The Spider is written entirely in the C programming language, and takes advantage of the true 32 bit multithreaded programming environment provided therein. It's fast: in our internal testing, the new program will perform 450 individual registrations in just under 18 minutes. Testing was done on a 28.8 dialup line. 6) Automatic Update Feature: No more weekly and monthly downloads! In an effort to keep up to date with search engine changes and updates, we have now incorporated a feature that will automate this task. Here's how it works: a.. Each time the program is loaded, it will automatically connect to our server and verify that the current search engine database is loaded on your user's machine. If it is not, it will automatically initiate a download. b. Once the download is complete (typically 20-30 seconds on a 28.8K connection), normal program operation will resume with the new database. 7) Improved Error Checking: anytime an error is generated during submission, by any user anywhere, the program updates our server with the search engine name, time and date of the error, and the nature of the error. Our resource manager for this project checks his log daily and investigates each and every error and has the ability to dynamically and instantly update the master database with the corrections. Once the correction is made, the Automatic Update Feature kicks in, distributing the updated registration database to every user worldwide the next time they use the program. To get your FREE DEMO of this amazing software, please visit: http://www.hiredhits.com/ If you would prefer us to send you a CD with The Spider, along with free demos of over 10 of our other web promotion software packages, please visit: http://www.hiredhits.com/order/process_cd.htm If you are having problems connecting to the above links, please give us a call at 773-271-8484 and we will arrange another way for you to get your FREE DEMO. Thanks again for your time and please let me know if you have any questions. Best Regards, Amy Horowitz MasterPromote, Inc. 120 Broadview Village Square Suite 315 Broadview, IL 60153 773-271-8484 ********* To remove yourself from this mailing list, please visit http://www.hiredhits.com and type your name in the "Remove Me!" box. We will promptly remove your name from future mailings. Sorry for any inconveince we may have caused From elizab@rs7029.tr.comm.mot.com Wed Oct 28 13:13:45 1998 Return-Path: Received: from tangelo.bmc.com ([172.17.7.166]) by amethyst.bmc.com (8.8.8/8.8.8) with ESMTP id NAA16728 for ; Wed, 28 Oct 1998 13:13:45 -0600 (CST) 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 NAA20377; Wed, 28 Oct 1998 13:12:03 -0600 (CST) Received: from tangelo.bmc.com (root@tangelo.bmc.com [172.17.7.166]) by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) with ESMTP id LAA08491 for ; Wed, 28 Oct 1998 11:09:13 -0800 (PST) Received: from fw-us-hou1.bmc.com (fw-us-hou1.bmc.com [172.17.0.250]) by tangelo.bmc.com (8.8.6 (PHNE_14041)/8.8.6) with SMTP id NAA19660 for ; Wed, 28 Oct 1998 13:09:09 -0600 (CST) Received: from pobox2.mot.com (pobox2.mot.com [129.188.137.195]) by motgate2.mot.com (8.8.5/8.6.10/MOT-3.8) with ESMTP id NAA16560 for ; Wed, 28 Oct 1998 13:10:41 -0600 (CST) Comments: ( Received on motgate2.mot.com from client pobox2.mot.com, sender elizab@rs7029.tr.comm.mot.com ) Received: from rs7029.tr.comm.mot.com (rs7029.tr.comm.mot.com [173.1.21.29]) by pobox2.mot.com (8.8.5/8.6.10/MOT-3.8) with ESMTP id NAA25912 for ; Wed, 28 Oct 1998 13:08:05 -0600 (CST) Received: (from elizab@localhost) by rs7029.tr.comm.mot.com (8.8.5/8.8.5) id NAA29383; Wed, 28 Oct 1998 13:08:40 -0600 (CST) From: "Eliza Ballew" Message-Id: <981028130840.ZM29381@rs7029.tr.comm.mot.com> Date: Wed, 28 Oct 1998 13:08:39 -0600 X-Mailer: Z-Mail (4.0.1 13Jan97) To: agentx@peer.com Subject: AgentX vendors Cc: elizab@comm.mot.com MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Hi. I was wondering if anyone knows of or could suggest a few vendors that you may know of that provide AgentX demo/evaluation source code and documentation? Any advice would be appreciated. Thanks, -Eliza From Christophe.Laye@Digital.com Thu Oct 29 11:18:45 1998 Return-Path: Received: from tangelo.bmc.com ([172.17.7.166]) by amethyst.bmc.com (8.8.8/8.8.8) with ESMTP id LAA26611 for ; Thu, 29 Oct 1998 11:18:45 -0600 (CST) 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 LAA19471; Thu, 29 Oct 1998 11:11:59 -0600 (CST) Received: from tangelo.bmc.com (root@tangelo.bmc.com [172.17.7.166]) by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) with ESMTP id JAA09999 for ; Thu, 29 Oct 1998 09:08:13 -0800 (PST) Received: from fw-us-hou1.bmc.com (fw-us-hou1.bmc.com [172.17.0.250]) by tangelo.bmc.com (8.8.6 (PHNE_14041)/8.8.6) with SMTP id LAA17856 for ; Thu, 29 Oct 1998 11:08:07 -0600 (CST) Received: from reohub2.reo.dec.com (reohub2.reo.dec.com [16.37.21.19]) by mail13.digital.com (8.9.1a/8.9.1/WV2.0a) with ESMTP id MAA06565 for ; Thu, 29 Oct 1998 12:07:57 -0500 (EST) Received: by reohub2.reo.dec.com with Internet Mail Service (5.5.2232.9) id ; Thu, 29 Oct 1998 17:07:53 -0000 Message-ID: <512ADED09A12D2119EE70000F8311D1324D53C@vbeexc2.vbe.dec.com> From: Christophe Laye To: "'agentx@peer.com'" Subject: Subscribe Date: Thu, 29 Oct 1998 17:06:37 -0000 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2232.9) Content-Type: text/plain; charset="iso-8859-1" > Christophe Laye > COMPAQ > TeMIP http://www.digital.com/temip > * mailto:Christophe.laye@digital.com > * 33 (0) 4 92 95 62 25 > Fax 33 (0) 4 92 95 58 48 > > > > From jdube@avici.com Thu Oct 29 11:36:36 1998 Return-Path: Received: from tangelo.bmc.com ([172.17.7.166]) by amethyst.bmc.com (8.8.8/8.8.8) with ESMTP id LAA26754 for ; Thu, 29 Oct 1998 11:36:36 -0600 (CST) 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 LAA27724; Thu, 29 Oct 1998 11:34:50 -0600 (CST) Received: from tangelo.bmc.com (root@tangelo.bmc.com [172.17.7.166]) by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) with ESMTP id JAA10652 for ; Thu, 29 Oct 1998 09:34:21 -0800 (PST) Received: from fw-us-hou1.bmc.com (fw-us-hou1.bmc.com [172.17.0.250]) by tangelo.bmc.com (8.8.6 (PHNE_14041)/8.8.6) with SMTP id LAA27537 for ; Thu, 29 Oct 1998 11:34:18 -0600 (CST) Received: from jdube-pc (jdube-pc.avici.com [10.1.2.235]) by mlsrv1.avici.com (8.8.5/8.8.4) with SMTP id MAA08321 for ; Thu, 29 Oct 1998 12:32:48 -0500 (EST) Message-Id: <3.0.3.32.19981029122840.00bda460@mailhost.avici.com> X-Sender: jdube@mailhost.avici.com X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.3 (32) Date: Thu, 29 Oct 1998 12:28:40 -0500 To: agentx@peer.com From: Joseph Dube Subject: UnSubscribe Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" From Lauren_Heintz@crow.bmc.com Thu Oct 29 18:42:40 1998 Return-Path: Received: from tangelo.bmc.com ([172.17.7.166]) by amethyst.bmc.com (8.8.8/8.8.8) with ESMTP id SAA29956 for ; Thu, 29 Oct 1998 18:42:39 -0600 (CST) From: Lauren_Heintz@crow.bmc.com 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 SAA08434; Thu, 29 Oct 1998 18:40:57 -0600 (CST) Received: from tangelo.bmc.com (root@tangelo.bmc.com [172.17.7.166]) by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) with ESMTP id QAA17935 for ; Thu, 29 Oct 1998 16:38:38 -0800 (PST) Received: from localhost (root@localhost) by tangelo.bmc.com (8.8.6 (PHNE_14041)/8.8.6) with SMTP id SAA07522; Thu, 29 Oct 1998 18:37:47 -0600 (CST) X-OpenMail-Hops: 2 Date: Thu, 29 Oct 1998 18:37:30 -0600 Message-Id: Subject: RE: Subscribe MIME-Version: 1.0 TO: agentx@peer.com, Christophe.Laye@Digital.com Content-Type: text/plain; charset=US-ASCII; name="BDY.TXT" Content-Disposition: inline; filename="BDY.TXT" Content-Transfer-Encoding: 7bit You are now subscribed to AgentX. ------------------------------------------------------------------------ - Lauren Heintz BMC Software, Inc. (Formerly PEER Networks) Voice: +1 408 616-3169 Silicon Valley Division Fax: +1 408 616-3339 965 Stewart Drive Email: Lauren_Heintz@bmc.com Sunnyvale, California 94086 USA ------------------------------------------------------------------------ - > -----Original Message----- > From: Christophe.Laye [mailto:Christophe.Laye@Digital.com] > Sent: Thursday, October 29, 1998 9:07 AM > To: agentx > Cc: Christophe.Laye > Subject: Subscribe > > > > > Christophe Laye > > COMPAQ > > TeMIP http://www.digital.com/temip > > * mailto:Christophe.laye@digital.com > > * 33 (0) 4 92 95 62 25 > > Fax 33 (0) 4 92 95 58 48 > > > > > > > > > From sgudur@hotmail.com Thu Oct 29 19:58:00 1998 Return-Path: Received: from tangelo.bmc.com ([172.17.7.166]) by amethyst.bmc.com (8.8.8/8.8.8) with ESMTP id TAA00527 for ; Thu, 29 Oct 1998 19:58:00 -0600 (CST) 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 TAA25383; Thu, 29 Oct 1998 19:56:28 -0600 (CST) Received: from tangelo.bmc.com (root@tangelo.bmc.com [172.17.7.166]) by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) with ESMTP id RAA19775 for ; Thu, 29 Oct 1998 17:54:09 -0800 (PST) Received: from fw-us-hou1.bmc.com (fw-us-hou1.bmc.com [172.17.0.250]) by tangelo.bmc.com (8.8.6 (PHNE_14041)/8.8.6) with SMTP id TAA24937 for ; Thu, 29 Oct 1998 19:54:07 -0600 (CST) Received: (qmail 29214 invoked by uid 65534); 30 Oct 1998 01:46:57 -0000 Message-ID: <19981030014657.29213.qmail@hotmail.com> Received: from 152.67.249.57 by www.hotmail.com with HTTP; Thu, 29 Oct 1998 17:46:56 PST X-Originating-IP: [152.67.249.57] From: "Smitha Gudur" To: agentx@peer.com Cc: bnatale@acecomm.com Subject: revised agentx mib Content-Type: multipart/mixed; boundary="====================987654321_0==_" Date: Thu, 29 Oct 1998 17:46:56 PST --====================987654321_0==_ Content-Type: text/plain; charset="us-ascii" Hi, I am posting the revised agentx mib based on the inputs received so far on the mailing list. Please review it and send the comments to the mailing list(agentx@peer.com). thanks smitha ______________________________________________________ Get Your Private, Free Email at http://www.hotmail.com --====================987654321_0==_ Content-Type: text/plain; name="mib.txt" Content-Disposition: attachment; filename="mib.txt" INTERNET-DRAFT S. Gudur BMC Software, Inc. L. Heintz BMC Software, Inc. 29 October 1998 Definitions of Managed Objects for Extensible SNMP Agents | Status of this Memo This document is an Internet-Draft. Internet-Drafts are working documents of the Internet Engineering Task Force (IETF), its Areas, and its Working Groups. Note that other groups may also distribute working documents as Internet-Drafts. Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as a "work in progress". To learn the current status of any Internet-Draft, please check the "1id-abstracts.txt" listing contained in the Internet-Drafts Shadow Directories on ds.internic.net (US East Coast), nic.nordu.net (Europe), ftp.isi.edu (US West Coast), or munnari.oz.au (Pacific Rim). Copyright Notice Copyright (C) The Internet Society (1998). All Rights Reserved. Abstract This memo defines an experimental portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it describes objects managing SNMP agents that use the Agent Extensibility (AgentX) Protocol. This memo specifies a MIB module in a manner that is both compliant to the SNMPv2 SMI, and semantically identical to the peer SNMPv1 definitions. This memo does not specify a standard for the Internet community. AgentX Working Group Expires April 1999 [Page 1] Internet Draft AgentX MIB 29 October 1998 1. The SNMP Network Management Framework The SNMP Network Management Framework presently consists of three major components. They are: - the SMI, described in RFC 1902 [1] - the mechanisms used for describing and naming objects for the purpose of management. - the MIB-II, STD 17, RFC 1213 [2] - the core set of managed objects for the Internet suite of protocols. - the protocol, RFC 1157 [3] and/or RFC 1905 [4], - the protocol for accessing managed objects. The Framework permits new objects to be defined for the purpose of experimentation and evaluation. 1.1. Object Definitions Managed objects are accessed via a virtual information store, termed the Management Information Base or MIB. Objects in the MIB are defined using the subset of Abstract Syntax Notation One (ASN.1) defined in the SMI. In particular, each object type is named by an OBJECT IDENTIFIER, an administratively assigned name. The object type together with an object instance serves to uniquely identify a specific instantiation of the object. For human convenience, we often use a textual string, termed the descriptor, to also refer to the object type. 2. Introduction The SNMP Agent Extensibility Protocol (AgentX) is a protocol used to distribute the implementation of an SNMP agent amongst a single "master agent" and multiple "subagents". See [5] for details about the AgentX protocol. The goals of the AgentX MIB are: - List the set of subagents that currently have logical sessions open with the master agent. - Identify each subagent's type, vendor, transport address, AgentX protocol version, and other characteristics. - Identify the set of MIB objects each subagent implements, the context in which the objects are registered, and the priority of the registration. AgentX Working Group Expires April 1999 [Page 2] Internet Draft AgentX MIB 29 October 1998 - Provide statistics about the protocol operation such as the number of packets to and from each subagent. - Determine protocol operational parameters such as the timeout interval for responses from a subagent and the priority at which a subagent registers a particular MIB region. - Allow (but do not require) managers to be able to modify AgentX protocol operational parameters and to explicitly close subagent sessions with the master agent. 3. Overview This MIB is organized into four groups. The agentxGeneral group provides information describing the master agent's Agentx support, including the protocol version supported and the supported transport mechanisms. The agentxConnection group provides information describing the current set of connections capable of carrying Agentx sessions. The agentxSession group provides information describing the current set of AgentX sessions. The agentxRegistration group provides information describing the current set of registrations. Three tables form the heart of this mib. These are the connection, session, and registration tables. Entries in the registration table exist in a many-to-one relationship with entries in the session table. This relationship is represented through the agentxSessionIndex and agentxConnIndex. Registration entries are indexed by agentxConnIndex and agentxSessionIndex, to determine which registration(s), a subagent session is responsible for a given connection. Entries in the session table exist in a many-to-one relationship with entries in the connection table. This relationship is represented through the agentxConnIndex in a session table. Session entries are indexed by agentxConnIndex to determine which sessions(s), are carried by a given connection. AgentX Working Group Expires April 1999 [Page 3] Internet Draft AgentX MIB 29 October 1998 4. Definitions AGENTX-MIB DEFINITIONS ::= BEGIN IMPORTS MODULE-IDENTITY, OBJECT-TYPE, experimental, Counter32, Gauge32, Unsigned32, TDomain, TAddress FROM SNMPv2-SMI SnmpAdminString | FROM SNMP-FRAMEWORK-MIB | MODULE-COMPLIANCE, OBJECT-GROUP FROM SNMPv2-CONF TEXTUAL-CONVENTION, TimeStamp, TruthValue FROM SNMPv2-TC; agentxMIB MODULE-IDENTITY LAST-UPDATED "9804141200Z" -- Sept 15, 1998 | ORGANIZATION "IETF AgentX Working Group" CONTACT-INFO "WG-email: agentx@peer.com Subscribe: agentx-request@peer.com http://www.ietf.org/html.charters/agentx-charter.html Chair: Bob Natale ACE*COMM Corporation Email: bnatale@acec.com Editor: Smitha Gudur BMC Software, Inc. 965 Stewart Drive Sunnyvale, CA 94086 Phone: +1 408-616-3100 Email: sgudur@hotmail.com " DESCRIPTION "This is the MIB module for the SNMP Agent Extensibility Protocol (AgentX). This MIB module will be implemented by the master agent." -- For testing purposes only. Need to get an experimental id ::= { experimental 2001 } agentxObjects OBJECT IDENTIFIER ::= { agentxMIB 1 } -- -- Define the four groups that serve to organize the -- objects in this MIB -- AgentX Working Group Expires April 1999 [Page 4] Internet Draft AgentX MIB 29 October 1998 agentxGeneral OBJECT IDENTIFIER ::= { agentxObjects 1 } agentxConnection OBJECT IDENTIFIER ::= { agentxObjects 2 } agentxSession OBJECT IDENTIFIER ::= { agentxObjects 3 } agentxRegistration OBJECT IDENTIFIER ::= { agentxObjects 4 } agentxDefaultTimeout OBJECT-TYPE SYNTAX INTEGER (0..255) UNITS "seconds" MAX-ACCESS read-write STATUS current DESCRIPTION "The default length of time, in seconds, that the master agent should allow to elapse after dispatching a message to a subagent before it regards the subagent as not responding. This is a system-wide value that may be overridden by the values associated with a particular subagent (agentxSessionTimeout) or a particular registered MIB region (agentxRegTimeout)." DEFVAL { 5 } ::= { agentxGeneral 1 } agentxMasterAgentXVer OBJECT-TYPE SYNTAX INTEGER (1..255) MAX-ACCESS read-only STATUS current DESCRIPTION "The AgentX protocol version supported by this master agent. Current version is 1. Note that the master agent must allow registration of earlier version subagents." ::= { agentxGeneral 2 } -- -- The Agentx Subagent Connection Group -- agentxConnTableLastChange OBJECT-TYPE SYNTAX TimeStamp MAX-ACCESS read-only STATUS current DESCRIPTION "The value of sysUpTime when the last row creation or deletion occurred in the agentxConnectionTable." ::= { agentxConnection 1 } agentxConnectionTable OBJECT-TYPE SYNTAX SEQUENCE OF AgentxConnectionEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "The agentxConnectionTable tracks all current Agentx transport AgentX Working Group Expires April 1999 [Page 5] Internet Draft AgentX MIB 29 October 1998 connections. There may be zero, one, or more agentx sessions on a given Agentx connection. If agentx connection table is | deleted, agentxConnIndex will be deleted from all other | tables as an index." | ::= { agentxConnection 2 } agentxConnectionEntry OBJECT-TYPE SYNTAX AgentxConnectionEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "An agentxConnectionEntry contains information describing a single Agentx transport connection. A connection may be used to support zero or more Agentx sessions. Entries come into being when the transport connection is established, and are not deleted unless the transport connection has been terminated." INDEX { agentxConnIndex } ::= { agentxConnectionTable 1 } AgentxConnectionEntry ::= SEQUENCE { agentxConnIndex Unsigned32, agentxConnOpenTime TimeStamp, agentxConnTransportDomain TDomain, agentxConnTransportAddress TAddress } agentxConnIndex OBJECT-TYPE SYNTAX Unsigned32 MAX-ACCESS not-accessible STATUS current DESCRIPTION "The value of agentxConnIndex uniquely identifies each open transport connection used by this master agent to provide AgentX service. Values of this index should not be re-used. The value assigned to a given transport connection is constant for the lifetime of that connection." ::= { agentxConnectionEntry 1 } agentxConnOpenTime OBJECT-TYPE SYNTAX TimeStamp MAX-ACCESS read-only STATUS current DESCRIPTION "The value of sysUpTime when this connection was established and, therefore, its value when this entry was added to the table." ::= { agentxConnectionEntry 2 } AgentX Working Group Expires April 1999 [Page 6] Internet Draft AgentX MIB 29 October 1998 agentxConnTransportDomain OBJECT-TYPE SYNTAX TDomain MAX-ACCESS read-only STATUS current DESCRIPTION "The transport protocol in use for this connection to the master agent." ::= { agentxConnectionEntry 3 } agentxConnTransportAddress OBJECT-TYPE SYNTAX TAddress MAX-ACCESS read-only STATUS current DESCRIPTION "The transport address of the remote (subagent) end of this connection to the master agent. The object is likely to be | null for unix-domain sockets, since the subagent need not bind | a filename to its local socket." | ::= { agentxConnectionEntry 4 } -- -- The AgentX Subagent Session Group -- agentxSessionTableLastChange OBJECT-TYPE SYNTAX TimeStamp MAX-ACCESS read-only STATUS current DESCRIPTION "The value of sysUpTime when the last row creation or deletion occurred in the agentxSessionTable." ::= { agentxSession 1 } -- -- The AgentX Subagent Session Table -- agentxSessionTable OBJECT-TYPE SYNTAX SEQUENCE OF AgentxSessionEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "A table of AgentX subagents that have open sessions with the AgentX master agent." ::= { agentxSession 3 } agentxSessionEntry OBJECT-TYPE SYNTAX AgentxSessionEntry MAX-ACCESS not-accessible STATUS current AgentX Working Group Expires April 1999 [Page 7] Internet Draft AgentX MIB 29 October 1998 DESCRIPTION "Information about a single open session between the AgentX master agent and a subagent." INDEX { agentxConnIndex, agentxSessionIndex } | ::= { agentxSessionTable 1 } AgentxSessionEntry ::= SEQUENCE { agentxSessionIndex Unsigned32, agentxSessionObjectID OBJECT IDENTIFIER, agentxSessionDescr SnmpAdminString, | agentxSessionAdminStatus INTEGER, agentxSessionOpenTime TimeStamp, agentxSessionAgentXVer INTEGER, agentxSessionTimeout INTEGER } agentxSessionIndex OBJECT-TYPE SYNTAX Unsigned32 MAX-ACCESS not-accessible STATUS current DESCRIPTION "A unique index for the subagent session. It is same as | h.sessionID defined in the agentx header. Note that if | a subagent's session with the master agent is closed for any reason its index should not be re-used, therefore, the values of agentxSessionIndex may be discontiguous and will generally not be the same for the same subagent across multiple sessions." ::= { agentxSessionEntry 1 } agentxSessionObjectID OBJECT-TYPE SYNTAX OBJECT IDENTIFIER MAX-ACCESS read-only STATUS current DESCRIPTION "This is taken from the o.id field of the agentx-Open-PDU." | ::= { agentxSessionEntry 2 } agentxSessionDescr OBJECT-TYPE SYNTAX SnmpAdminString | MAX-ACCESS read-only STATUS current DESCRIPTION "A textual description of the subagent. This is analogous to sysDescr defined in MIB-2 [2] and is taken from the o.descr field of the agentx-Open-PDU." ::= { agentxSessionEntry 3 } AgentX Working Group Expires April 1999 [Page 8] Internet Draft AgentX MIB 29 October 1998 agentxSessionAdminStatus OBJECT-TYPE SYNTAX INTEGER { up(1), down(2) } MAX-ACCESS read-write STATUS current DESCRIPTION "The administrative (desired) status of the subagent. Setting the value to 'down(2)' closes the subagent session (with c.reason set to 'reasonByManager')." ::= { agentxSessionEntry 4 } agentxSessionOpenTime OBJECT-TYPE SYNTAX TimeStamp MAX-ACCESS read-only STATUS current DESCRIPTION "The value of sysUpTime when this session was opened and, therefore, its value when this entry was added to the table." ::= { agentxSessionEntry 5 } agentxSessionAgentXVer OBJECT-TYPE SYNTAX INTEGER (1..255) MAX-ACCESS read-only STATUS current DESCRIPTION "The version of the AgentX protocol supported by the subagent. This will be less than or equal to the value of agentxMasterAgentXVer." ::= { agentxSessionEntry 6 } agentxSessionTimeout OBJECT-TYPE SYNTAX INTEGER (0..255) UNITS "seconds" MAX-ACCESS read-only STATUS current DESCRIPTION "The length of time, in seconds, that a master agent should allow to elapse after dispatching a message to this subagent before it regards the subagent as not responding. This value is taken from the o.timeout field of the agentx-Open-PDU. This is a subagent-specific value that may be overridden by values associated with specific registered MIB regions (see agentxRegTimeout). The default value of '0' indicates that the master agent's default timeout value should be used (see agentxDefaultTimeout)." AgentX Working Group Expires April 1999 [Page 9] Internet Draft AgentX MIB 29 October 1998 ::= { agentxSessionEntry 7 } -- -- The AgentX Registration Information group -- -- The statistics in this group are maintained by the Master Agent. -- -- Other stats have been removed. Support trap generation based -- on certain situations for duplicate registration. -- agentxRegisterDuplicate OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "The number of agentx-Response-PDU messages sent by this master agent where the res.error field was set to 'duplicateRegistration'." ::= { agentxRegistration 1 } -- -- The AgentX Registration Table -- agentxRegistrationTableLastChange OBJECT-TYPE | SYNTAX TimeStamp | MAX-ACCESS read-only | STATUS current | DESCRIPTION | "The value of sysUpTime when the last row creation or deletion | occurred in the agentxRegistrationTable." | ::= { agentxRegistration 2 } | agentxRegistrationTable OBJECT-TYPE SYNTAX SEQUENCE OF AgentxRegistrationEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "A table of registered OBJECT IDENTIFIER regions. This is the table used to identify a registered region of a subagent. Note that a subagent registration may be broken up into multiple entries in this table, as described in the AgentX Protocol specification [5]." ::= { agentxRegistration 3 } agentxRegistrationEntry OBJECT-TYPE SYNTAX AgentxRegistrationEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION AgentX Working Group Expires April 1999 [Page 10] Internet Draft AgentX MIB 29 October 1998 "A single registered region. Regions are added by the master agent when subagents register and are removed from the table when the subagents unregister the region or their sessions are closed. Note that the combination of agentxRegContext, agentxRegStart and agentxRegDispatchOrder will be unique and could have been used for indexing purposes, but would have potentially resulted in excessively long OBJECT IDENTIFIERs." INDEX { agentxConnIndex, agentxSessionIndex, agentxRegIndex } ::= { agentxRegistrationTable 1 } AgentxRegistrationEntry ::= SEQUENCE { agentxRegIndex Unsigned32, agentxRegContext OCTET STRING, agentxRegStart OBJECT IDENTIFIER, agentxRegRangeSubId OBJECT IDENTIFIER, | agentxRegUpperBound OBJECT IDENTIFIER, | agentxRegPriority Unsigned32, agentxRegTimeout INTEGER, agentxRegInstance TruthValue } agentxRegIndex OBJECT-TYPE SYNTAX Unsigned32 MAX-ACCESS not-accessible STATUS current DESCRIPTION "AgentxRegIndex is an integer that uniquely identifies a registration entry. Its value is constant for the lifetime of an entry." ::= { agentxRegistrationEntry 1 } agentxRegContext OBJECT-TYPE SYNTAX OCTET STRING MAX-ACCESS read-only STATUS current DESCRIPTION "The context in which the subagent supports the objects in this region. A zero-length context indicates the default context." ::= { agentxRegistrationEntry 2 } agentxRegStart OBJECT-TYPE SYNTAX OBJECT IDENTIFIER MAX-ACCESS read-only STATUS current DESCRIPTION "The starting OBJECT IDENTIFIER of this registration entry. The subagent identified by agentxSessionIndex implements objects starting at this value (inclusive). Note that this value could AgentX Working Group Expires April 1999 [Page 11] Internet Draft AgentX MIB 29 October 1998 identify an object type, an object instance, or a partial object instance." ::= { agentxRegistrationEntry 3 } agentxRegRangeSubId OBJECT-TYPE | SYNTAX OBJECT IDENTIFIER | MAX-ACCESS read-only | STATUS current | DESCRIPTION | "agentxRegRangeSubId can be used to specify the range. This is | r.region_subid in registration PDU. If the value of this | object is 0, no range is specified. If it is not zero | it identifies the sub-identifier in r.region. r.region can | be a fully-qualified instance name, a partial instance name, a | MIB table, an entire MIB, or ranges of any of these. " | ::= { agentxRegistrationEntry 4 } | agentxRegUpperBound OBJECT-TYPE | SYNTAX OBJECT IDENTIFIER | MAX-ACCESS read-only | STATUS current | DESCRIPTION | "agentxRegUpperBound represents upper-bound sub-identifier in | a registration. This is r.upper_bound in registration PDU. | This is an optional field in registration field in registration. | If agentxRegRangeSub (r.region_subid) is zero, there is no | agentxRegUpper bound (r.upper_bound)." | ::= { agentxRegistrationEntry 5 } | -- -- To support other subagent types that can be visible -- to the manager. -- agentxRegPriority OBJECT-TYPE SYNTAX Unsigned32 MAX-ACCESS read-only STATUS current DESCRIPTION "The subagent's priority when exporting this OID range. Lower values have higher priority." ::= { agentxRegistrationEntry 6 } | agentxRegTimeout OBJECT-TYPE SYNTAX INTEGER (0..255) UNITS "seconds" MAX-ACCESS read-only STATUS current DESCRIPTION AgentX Working Group Expires April 1999 [Page 12] Internet Draft AgentX MIB 29 October 1998 "The timeout value, in seconds, for subagent responses to requests associated with this OID range. The value '0' indicates that the default value (indicated by agentxSessionTimeout or agentxDefaultTimeout) is to be used. This value is taken from the r.timeout field of the agentx-Register-PDU." ::= { agentxRegistrationEntry 7 } | agentxRegInstance OBJECT-TYPE SYNTAX TruthValue MAX-ACCESS read-only STATUS current DESCRIPTION "The value of agentxRegInstance is `true' for registrations for which the INSTANCE_REGISTRATION was set, and is `false' for all other registrations." ::= { agentxRegistrationEntry 8 } | -- -- Conformance Statements for the AgentX MIB -- agentxConformance OBJECT IDENTIFIER ::= { agentxMIB 2 } agentxMIBGroups OBJECT IDENTIFIER ::= { agentxConformance 1 } agentxMIBCompliances OBJECT IDENTIFIER ::= { agentxConformance 2 } agentxMIBCompliance MODULE-COMPLIANCE STATUS current DESCRIPTION "The compliance statement for SNMP entities that implement the AgentX protocol. Note that a compliant agent can implement all objects in this MIB module as read-only." MODULE -- this module MANDATORY-GROUPS { agentxMIBGroup } OBJECT agentxDefaultTimeout MIN-ACCESS read-only DESCRIPTION "Write access is not required." OBJECT agentxSessionAdminStatus MIN-ACCESS read-only DESCRIPTION "Write access is not required." ::= { agentxMIBCompliances 1 } agentxMIBGroup OBJECT-GROUP AgentX Working Group Expires April 1999 [Page 13] Internet Draft AgentX MIB 29 October 1998 OBJECTS { agentxDefaultTimeout, agentxMasterAgentXVer, agentxConnOpenTime, agentxConnTransportDomain, | agentxConnTransportAddress, | agentxSessionTableLastChange, agentxSessionTimeout, agentxSessionObjectID, agentxSessionDescr, agentxSessionAdminStatus, agentxSessionOpenTime, agentxSessionAgentXVer, agentxRegisterDuplicate, agentxRegistrationTableLastChange, agentxRegContext, agentxRegStart, agentxRegRangeSubId, | agentxRegRangeUpperBound, | agentxRegPriority, agentxRegTimeout, agentxRegInstance } STATUS current DESCRIPTION "All accessible objects in the AgentX MIB." ::= { agentxMIBGroups 1 } END 5. Acknowledgments This document is a product of the IETF's AgentX Working Group. Special acknowledgement is made to: Maria Greene | Xedia | 119 Russell Street, Littleton MA 01460 | USA | Phone: +1 978-952-6000 | EMail: maria@xedia.com | This MIB is an evolution of the Subagent MIB by Bert Wijnen (wijnen@vnet.ibm.com) which in turn was derived from the SMUX-MIB by Marshall Rose [6]. AgentX Working Group Expires April 1999 [Page 14] Internet Draft AgentX MIB 29 October 1998 6. References [1] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Structure of Management Information for Version 2 of the Simple Network Management Protocol (SNMPv2)", RFC1902, SNMP Research,Inc., Cisco Systems, Inc., Dover Beach Consulting, Inc., International Network Services, January 1996. [2] McCloghrie, K., and M. Rose, Editors, "Management Information Base for Network Management of TCP/IP-based internets: MIB-II", STD 17, RFC 1213, Hughes LAN Systems, Performance Systems International, March 1991. [3] Case, J., Fedor, M., Schoffstall, M., and J. Davin, "Simple Network Management Protocol", RFC 1157, SNMP Research, Performance Systems International, Performance Systems International, MIT Laboratory for Computer Science, May 1990. [4] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Protocol Operations for Version 2 of the Simple Network Management Protocol (SNMPv2)", RFC1905, SNMP Research,Inc., Cisco Systems, Inc., Dover Beach Consulting, Inc., International Network Services, January 1996. [5] Daniele, M., Wijnen, B., and D. Francisco, "Agent Extensibility (AgentX) Protocol, Version 1", draft-ietf-agentx-ext-pro-02.txt, Digital Equipment Corporation, T.J. Watson Research Center, IBM Corp., Cisco Systems, November, 1996. [6] Rose, M., "SNMP MUX Protocol and MIB", RFC1227, Performance Systems International, Inc., May 1991. [7] Wijnen, B., Carpenter, G., Curran, K., Sehgal, A., and G. Waters, "Simple Network Management Protocol: Distributed Protocol Interface, Version 2.0", RFC 1592, T.J. Watson Research Center, IBM Corp., Bell Northern Research, Ltd., March 1994. [8] F. Yergeau, "UTF-8, a transformation format of Unicode and ISO 10646,", RFC 2044, October 1996. 7. Security Considerations In most cases, MIBs are not themselves security risks; if SNMP security is operating as intended, the use of a MIB to view information about a system, or to change some parameter at the system, is a tool, not a threat. None of the read-only objects in this MIB reports a password, user data, or anything else that is particularly sensitive. If access to these AgentX Working Group Expires April 1999 [Page 15] Internet Draft AgentX MIB 29 October 1998 objects is not limited by an appropriate access control policy, these objects can provide an attacker with information about a system's configuration and the services that that system is providing. Some enterprises view their network and system configurations themselves, as well as information about usage and performance, as corporate assets; such enterprises may wish to restrict SNMP access to most of the objects in the MIB. This MIB contains two read-write objects: agentxDefaultTimeout and agentxSessionAdminStatus. Setting agentxDefaultTimeout to an inappropriately small value can prevent new subagent sessions from being usable. Setting agentxSessionAdminStatus to an inappropriate value can effectively prevent access to management information, or provide access to inappropriate information. Since changes to either of these objects can adversely impact the manageability of a system, write access to these objects should be subject to an appropriate access control policy. Such a policy may be realized in an implementation by limiting support for these objects to read-only access. 8. Editor's Address Smitha Gudur BMC Software, Inc. 965 Stewart Drive | Sunnyvale, CA 94086 | USA Phone: +1 408-616-3100 | EMail: sgudur@bmc.com 9. Full Copyright Statement Copyright (C) The Internet Society (1997). All Rights Reserved. This document and translations of it may be copied and furnished to others, and derivative works that comment on or otherwise explain it or assist in its implmentation may be prepared, copied, published and distributed, in whole or in part, without restriction of any kind, provided that the above copyright notice and this paragraph are included on all such copies and derivative works. However, this document itself may not be modified in any way, such as by removing the copyright notice or references to the Internet Society or other Internet organizations, except as needed for the purpose of developing Internet standards in which case the procedures for copyrights defined in the Internet Standards process must be followed, or as required to translate it into languages other than English. The limited permissions granted above are perpetual and will not be revoked by the Internet Society or its successors or assigns. AgentX Working Group Expires April 1999 [Page 16] Internet Draft AgentX MIB 29 October 1998 This document and the information contained herein is provided on an "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. AgentX Working Group Expires April 1999 [Page 17] --====================987654321_0==_ Content-Type: text/plain; charset="us-ascii" --====================987654321_0==_-- From wvinson@erols.com Fri Oct 30 03:26:57 1998 Return-Path: Received: from tangelo.bmc.com ([172.17.7.166]) by amethyst.bmc.com (8.8.8/8.8.8) with ESMTP id DAA03928 for ; Fri, 30 Oct 1998 03:26:57 -0600 (CST) 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 DAA17476; Fri, 30 Oct 1998 03:25:41 -0600 (CST) Received: from tangelo.bmc.com (root@tangelo.bmc.com [172.17.7.166]) by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) with ESMTP id BAA29860 for ; Fri, 30 Oct 1998 01:24:27 -0800 (PST) Received: from fw-us-hou1.bmc.com (fw-us-hou1.bmc.com [172.17.0.250]) by tangelo.bmc.com (8.8.6 (PHNE_14041)/8.8.6) with SMTP id DAA17309 for ; Fri, 30 Oct 1998 03:24:26 -0600 (CST) Received: from erols.com (cm0561h.jones.com [208.159.208.119]) by dc.jones.com (8.8.8/8.8.8) with ESMTP id EAA12457 for ; Fri, 30 Oct 1998 04:20:20 -0500 (EST) Message-ID: <3639870E.9516D4C9@erols.com> Date: Fri, 30 Oct 1998 04:29:50 -0500 From: Will Vinson Reply-To: wvinson@erols.com Organization: Jones Internet Channel X-Mailer: Mozilla 4.03 [en]C-JIC-DC (Win95; I) MIME-Version: 1.0 To: agentx@peer.com Subject: unsubscribe Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit unsubscribe From rpresuhn@dorothy.bmc.com Fri Oct 30 10:50:23 1998 Return-Path: Received: from tangelo.bmc.com ([172.17.7.166]) by amethyst.bmc.com (8.8.8/8.8.8) with ESMTP id KAA07209 for ; Fri, 30 Oct 1998 10:50:22 -0600 (CST) 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 KAA02616; Fri, 30 Oct 1998 10:43:40 -0600 (CST) Received: (from rpresuhn@localhost) by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) id IAA01397 for agentx@peer.com; Fri, 30 Oct 1998 08:41:32 -0800 (PST) Date: Fri, 30 Oct 1998 08:41:32 -0800 (PST) From: Randy Presuhn Message-Id: <199810301641.IAA01397@dorothy.bmc.com> To: agentx@peer.com Subject: Re: unsubscribe Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Hi - When unsubscribing from this list, PLEASE abide by long-established convention and use the address, as listed at http://www.ietf.org/html.charters/agentx-charter.html ----------------------------------------------------------------------- Randy Presuhn Email: randy_presuhn@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 rpresuhn@dorothy.bmc.com Fri Oct 30 20:11:03 1998 Return-Path: Received: from tangelo.bmc.com ([172.17.7.166]) by amethyst.bmc.com (8.8.8/8.8.8) with ESMTP id UAA11384 for ; Fri, 30 Oct 1998 20:11:02 -0600 (CST) 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 UAA07351; Fri, 30 Oct 1998 20:08:30 -0600 (CST) Received: (from rpresuhn@localhost) by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) id SAA13231 for agentx@peer.com; Fri, 30 Oct 1998 18:05:10 -0800 (PST) Date: Fri, 30 Oct 1998 18:05:10 -0800 (PST) From: Randy Presuhn Message-Id: <199810310205.SAA13231@dorothy.bmc.com> To: agentx@peer.com Subject: Re: revised agentx mib Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Hi - > From: "Smitha Gudur" > To: agentx@peer.com > Cc: bnatale@acecomm.com > Subject: revised agentx mib > Date: Thu, 29 Oct 1998 17:46:56 PST ... > Definitions of Managed Objects for > Extensible SNMP Agents > | ... May we assume that this has also gone to internet-drafts@ietf.org? ----------------------------------------------------------------------- Randy Presuhn Email: randy_presuhn@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." -----------------------------------------------------------------------