From Lauren_Heintz@crow.bmc.com Mon Nov 2 14:39:48 1998 Received: from tangelo.bmc.com (liverbird.bmc.com [198.207.223.252]) by ietf.org (8.8.5/8.8.7a) with ESMTP id OAA25284 for ; Mon, 2 Nov 1998 14:39:42 -0500 (EST) 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 NAA25859; Mon, 2 Nov 1998 13:35:43 -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 LAA01236 for ; Mon, 2 Nov 1998 11:31:22 -0800 (PST) Received: from localhost (root@localhost) by tangelo.bmc.com (8.8.6 (PHNE_14041)/8.8.6) with SMTP id NAA22509; Mon, 2 Nov 1998 13:25:25 -0600 (CST) X-OpenMail-Hops: 2 Date: Mon, 2 Nov 1998 13:24:59 -0600 Message-Id: Subject: RE: revised agentx mib MIME-Version: 1.0 TO: agentx@peer.com, sgudur@hotmail.com Content-Type: text/plain; charset=US-ASCII; name="BDY.TXT" Content-Disposition: inline; filename="BDY.TXT" Content-Transfer-Encoding: 7bit Hi Smitha, Seems that agentxRegRangeSubId should not be an OBJECT IDENTIFIER, but rather an integer whose possible values are between 0..128. agentxRegRangeSubid denotes the n'th subid in the agentxRegStart OID, and is not itself an OID. Similarly, agentxRegUpperBound is not an OID, but should rather be an actual subid value of type Unsigned32. Lauren Smitha wrote ------------------------------------------------------------------- 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 } | ------------------------------------------------------------------------ - 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 ------------------------------------------------------------------------ - From Lauren_Heintz@crow.bmc.com Mon Nov 2 15:04:38 1998 Received: from tangelo.bmc.com (liverbird.bmc.com [198.207.223.252]) by ietf.org (8.8.5/8.8.7a) with ESMTP id PAA25866 for ; Mon, 2 Nov 1998 15:04:37 -0500 (EST) 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 OAA04034; Mon, 2 Nov 1998 14:02:56 -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 MAA01292 for ; Mon, 2 Nov 1998 12:02:25 -0800 (PST) Received: from localhost (root@localhost) by tangelo.bmc.com (8.8.6 (PHNE_14041)/8.8.6) with SMTP id NAA02680; Mon, 2 Nov 1998 13:58:22 -0600 (CST) X-OpenMail-Hops: 2 Date: Mon, 2 Nov 1998 13:58:03 -0600 Message-Id: Subject: RE: revised agentx mib MIME-Version: 1.0 TO: agentx@peer.com, sgudur@hotmail.com Content-Type: text/plain; charset=US-ASCII; name="BDY.TXT" Content-Disposition: inline; filename="BDY.TXT" Content-Transfer-Encoding: 7bit Smitha, I believe agentxDefaultTimeout cannot have a DEFVAL clause?? Lauren > -----Original Message----- > From: sgudur [mailto:sgudur@hotmail.com] > > 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 } ------------------------------------------------------------------------ - 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 ------------------------------------------------------------------------ - From sgudur@hotmail.com Mon Nov 2 20:53:35 1998 Received: from tangelo.bmc.com (liverbird.bmc.com [198.207.223.252]) by ietf.org (8.8.5/8.8.7a) with ESMTP id UAA00400 for ; Mon, 2 Nov 1998 20:53:35 -0500 (EST) 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 TAA14671; Mon, 2 Nov 1998 19:52:31 -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 RAA03868 for ; Mon, 2 Nov 1998 17:51:48 -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 TAA14510 for ; Mon, 2 Nov 1998 19:51:47 -0600 (CST) Received: (qmail 17897 invoked by uid 0); 3 Nov 1998 01:44:20 -0000 Message-ID: <19981103014420.17896.qmail@hotmail.com> Received: from 152.67.249.57 by www.hotmail.com with HTTP; Mon, 02 Nov 1998 17:44:20 PST X-Originating-IP: [152.67.249.57] From: "Smitha Gudur" To: rpresuhn@dorothy.bmc.com, agentx@peer.com Subject: Re: revised agentx mib MIME-Version: 1.0 Content-Type: text/plain Date: Mon, 02 Nov 1998 17:44:20 PST Hi, No. not yet. regards smitha >Received: from [198.207.223.252] by hotmail.com (1.0) with SMTP id MHotMail308725303216835065324963335512060124311; Fri Oct 30 18:17:35 1998 >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 UAA07904; > Fri, 30 Oct 1998 20:11:33 -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." > ----------------------------------------------------------------------- ______________________________________________________ Get Your Private, Free Email at http://www.hotmail.com From bnatale@acecomm.com Mon Nov 2 21:14:01 1998 Received: from tangelo.bmc.com (liverbird.bmc.com [198.207.223.252]) by ietf.org (8.8.5/8.8.7a) with ESMTP id VAA00572 for ; Mon, 2 Nov 1998 21:14:01 -0500 (EST) 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 UAA18458; Mon, 2 Nov 1998 20:13:06 -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 SAA04026 for ; Mon, 2 Nov 1998 18:12:39 -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 UAA18351; Mon, 2 Nov 1998 20:12:38 -0600 (CST) Received: from [192.152.208.5] (helo=acecomm.com) by relay3.smtp.psi.net with smtp (Exim 1.90 #1) id 0zaVxF-0005Aw-00; Mon, 2 Nov 1998 21:12:21 -0500 Received: from ppp2 by acecomm.com (5.65/3.2.083191-ACE*COMM) id AA09092; Mon, 2 Nov 1998 21:15:12 -0500 Message-Id: <4.1.19981102210349.0096e9f0@nips.acec.com> X-Sender: natale@nips.acec.com X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1 Date: Mon, 02 Nov 1998 21:13:05 -0500 To: Randy Presuhn From: Bob Natale Subject: Re: revised agentx mib Cc: agentx@peer.com In-Reply-To: <199810310205.SAA13231@dorothy.bmc.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" >At 10/30/98 06:05 PM, Randy Presuhn wrote: Hi Randy, >> Definitions of Managed Objects for >> Extensible SNMP Agents >> | >... > >May we assume that this has also gone to internet-drafts@ietf.org? No, our plan--given the break in attention that has occurred in recent weeks--was to post it to the list for review and discussion in an attempt to ensure that the next submission to the I-D repository may be the version that goes on to WG last call, Area review, IESG review and so forth. Much of the "blame" for the break belongs on my shoulders...the idea was to pace the post-Chicao-IETF work on posting of the AgentX meeting minutes. I have been in touch with Dale on several occasions via both e-mail and telephone and, as of last Friday I thought we were very close to passing this milestone. If only the DISMAN WG chair had not mis-appropriated the AgentX WG editor for the DISMAN minutes (which were posted in a timely manner), we'd be done with AgentX by now! :-):-):-) Anyway, I've noted that both DISMAN and SNMPv3 discussions have progressed during the AgentX lull, and that's a good thing. Cordially, BobN ---- ISO 9001 Registered, H/W & S/W Products| NASDAQ: ACEC ----- 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 ----- WinSNMP DLL, SDK, Apps & Agents for Win16/32 & UNIX ------ ------ WinSNMP specs and sample code at www.winsnmp.com -------- From rpresuhn@dorothy.bmc.com Tue Nov 3 17:44:52 1998 Received: from tangelo.bmc.com (liverbird.bmc.com [198.207.223.252]) by ietf.org (8.8.5/8.8.7a) with ESMTP id RAA15881 for ; Tue, 3 Nov 1998 17:44:51 -0500 (EST) 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 QAA13229; Tue, 3 Nov 1998 16:41:14 -0600 (CST) Received: (from rpresuhn@localhost) by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) id OAA22301 for agentx@peer.com; Tue, 3 Nov 1998 14:37:38 -0800 (PST) Date: Tue, 3 Nov 1998 14:37:38 -0800 (PST) From: Randy Presuhn Message-Id: <199811032237.OAA22301@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: Lauren_Heintz@crow.bmc.com > Date: Mon, 2 Nov 1998 13:24:59 -0600 > Subject: RE: revised agentx mib > TO: agentx@peer.com, sgudur@hotmail.com ... > Seems that agentxRegRangeSubId should not be an OBJECT IDENTIFIER, > but rather an integer whose possible values are between 0..128. > agentxRegRangeSubid denotes the n'th subid in the agentxRegStart > OID, and is not itself an OID. > > Similarly, agentxRegUpperBound is not an OID, but should rather be an > actual subid value of type Unsigned32. ... I think this may be connected to earlier discussions about how to deal with the representation of ranges and wildcarding, and whether the sorts of regions that can be represented by the MIB should be limited to what it is possible to express in version 1 of the AgentX protocol. ----------------------------------------------------------------------- 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 Tue Nov 3 17:46:25 1998 Received: from tangelo.bmc.com (liverbird.bmc.com [198.207.223.252]) by ietf.org (8.8.5/8.8.7a) with ESMTP id RAA15921 for ; Tue, 3 Nov 1998 17:46:24 -0500 (EST) 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 QAA13218; Tue, 3 Nov 1998 16:41:12 -0600 (CST) Received: (from rpresuhn@localhost) by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) id OAA22251 for agentx@peer.com; Tue, 3 Nov 1998 14:33:08 -0800 (PST) Date: Tue, 3 Nov 1998 14:33:08 -0800 (PST) From: Randy Presuhn Message-Id: <199811032233.OAA22251@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 sgudur@hotmail.com Thu Oct 29 17:56:57 PST 1998 > From: "Smitha Gudur" > To: agentx@peer.com > Cc: bnatale@acecomm.com > Subject: revised agentx mib > Date: Thu, 29 Oct 1998 17:46:56 PST ... A few nits: The posted text has incorrect affiliation/address information for Smitha. (first page, page 4, page 16) The posted text lacks affiliation/address information for Lauren. (page 4, page 16) The I-D boilerplate needs to be updated (third paragraph, page 1) The current MIB boilerplate should be used (see http://www.ops.ietf.org/) ... > agentxMIB MODULE-IDENTITY > LAST-UPDATED "9804141200Z" -- Sept 15, 1998 | Which is it? ... > [8] F. Yergeau, "UTF-8, a transformation format of Unicode and ISO > 10646,", RFC 2044, October 1996. This has been superceded by RFC 2279. ... > 7. Security Considerations This should be updated in accordance with the current MIB security considerations boilerplate. ... > 9. Full Copyright Statement > > Copyright (C) The Internet Society (1997). All Rights Reserved. Wrong year? > 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 implementation ----------------------------------------------------------------------- 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 dfrancis@cisco.com Tue Nov 3 19:29:28 1998 Received: from tangelo.bmc.com (liverbird.bmc.com [198.207.223.252]) by ietf.org (8.8.5/8.8.7a) with ESMTP id TAA17886 for ; Tue, 3 Nov 1998 19:29:27 -0500 (EST) 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 SAA14429; Tue, 3 Nov 1998 18:19:05 -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 QAA25614 for ; Tue, 3 Nov 1998 16:18:15 -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 SAA14172 for ; Tue, 3 Nov 1998 18:18:06 -0600 (CST) Received: (dfrancis@localhost) by zipper.cisco.com (8.8.5-Cisco.2-SunOS.5.5.1.sun4/8.6.5) id OAA02652; Tue, 3 Nov 1998 14:04:41 -0800 (PST) From: Dale Francisco Message-Id: <199811032204.OAA02652@zipper.cisco.com> Subject: IETF 42 (Chicago) AgentX minutes To: agentx@peer.com Date: Tue, 3 Nov 1998 14:04:41 -0800 (PST) X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Well, better late than not at all, I suppose. My apologies for getting these out so long after the fact, but I think there's still some value in the minutes. Dale Meeting of the SNMP Agent Extensibility (agentx) working group at IETF-42 Chicago (Wed 8/26/98 15:30-17:30) Reported by Dale Francisco (dfrancis@cisco.com) Bob Natale, Chair (bnatale@acecomm.com) For more information on the agentx wg, please see: http://www.ietf.org/html.charters/agentx-charter.html (IETF charter) http://www.scguild.com/agentx/ (AgentX home page) The meeting began with an account by Bob Natale, working group chair, of the status of the group's goals and milestones: publish protocol (rfc 2257)--done submit agentx MIB i-d to wg--done Jun 98 collect implementation reports--done Jul 98 interoperability tests (BMC Sunnyvale)--done Aug 98 meet at 42 IETF (refine or revise 2257) Sep 98 petition iesg to advance 2257 to draft or recycle at proposed. Oct 98 submit agentx mib to iesg Nov 98 submit agentx api i-d v0.1 Dec 98 submit agentx api i-d v0.2 Jan 99 agentx api i-d to iesg Feb 99 evaluate revs to rfc2257 v2.0 Mar 99 meet at 44th ietf (tbd) Assess status of agentx deployment Determine need for agentx v2 Plan future work items accordingly. Apr 99 submit new charter proposal to IESG or retire wg. Bob then recounted progress to date on RFC 2257, noting first that it is time (or actually past time) to update the document. RFC 2257 was originally published in January 1997, since which time there has been significant implementation experience. The goals of the RFC update are to: Avoid semantic changes Avoid/minimize changes to bits on the wire Provide clarifications Remove superfluous material Note limitations (already fairly complete in this regard) Schedule future work Submit updated RFC to the IESG, probably for recycling at Proposed. Bob then discussed interoperability testing and the current state of implementations. Five organizations participated at the AgentX bakeoff held at the end of July, hosted by BMC at their Sunnyvale office. He began with a list of the features not fully tested (or not tested at all): Index allocation/deallocation operations AGENT-CAPS operations UNIX domain sockets (multi-vendor configurations) (at the bakeoff only used TCP) Multiple sessions over a single connection Complex region registrations Agentx-Notify-PDUs Didn't carry to SNMP-level of actually emitting SNMP traps NON_DEFAULT_CONTEXT processing During the course of the bakeoff, several problems were exposed in implementations, though not in the protocol specification itself. Nevertheless, some of these problems indicated the need for clarifications in RFC 2257*. These problems included: Byte-ordering conventions Some implementations didn't know when to switch *TCP streams vs UDP datagrams Add language in transport mappings section *"optional" PDU elements context field or not Counter64 handling Several clarifications were proposed: PDU types not needing a response Currently, the RFC specifies two PDU types from subagent to master (Close and Notify) that don't require a response. Consensus: These PDUs should get a response; this is so the subagent knows when to stop waiting for an error. UNIX-domain socket conventions Need to define tDomain for it (MIB issue). Optional vs NULL/missing vs zero-length PDU fields: Mike Daniele will clarify the meaning of "optional". Search ranges for PDUs What happens if the master agent sends PDU to a subagent for an OID lower than anything the subagent has registered for? What about on GetNext? There were some boundary case problems here. Description of range_subid in register-PDU There was confusion over whether or not the prefix of an OID was included when specifying a range sub-id. The range sub-id number is calculated _including_ the prefix (if any). Reuse of SessionID values Is this allowed? Is 0 a valid SessionID value? Additional error codes needed: generalRegistrationFailed, unknownError Randy Presuhn suggested that clarification was needed on exactly what it means for a deregistration to "match" a registration request. Shawn, Randy, and Mike volunteered to resolve this issue on the list. Mike Daniele then presented his perspective on the bakeoff. He emphasized what had worked, and noted that the majority of AgentX features were tested. There were four "full" implementations (each with a master and subagent). Command line SNMP utilities were used to send SNMP requests to the master agents. Functionality tested included: Get, GetNext, Set PDUs Commits that failed, undos that failed Tested every data type except opaque 2 implementations tested getBulk Mike then initiated a general discussion of the bakeoff experience. Jeff Case noted that, of the two implementations that tested getBulk, one had an SNMPv3-capable master. He wondered if there had been any testing done with view-based access control enabled. Mike Thatcher replied that in one test case VACM was on and he was at first puzzled that he didn't get any information back (VACM was doing its job!). Jeff suggested doing further testing with part of a registered block in view and part out. It was suggested that we needed a TDomain and TAddresses for the AgentX MIB. Randy Presuhn suggested the possibility of a follow-on document on new transport mappings. It was noted that CMU is making AgentX code available with UNIX-domain sockets. Other topics of discussion included: Search ranges: In the current elements of procedure for the master agent, it says that for a GetNext before a registered subagent region, the master should send the starting OID of the nearest relevant session. One implementation sent an OID from immediately _before_ the registered region, and one subagent rejected it. Need to relax rules on what master can dispatch in this case, as long as the master only returns values from a registered region. Session IDs: Should they really be globally unique, or is it sufficient that they be unique per connection? Randy: Globally unique is not needed for interoperability. Mike D: There was a request from some wg members to have sessionIDs unique across all connections and all transports. Jeff: Is zero a reserved value? On the mailing list, it was suggested that 0 be a request value but never a granted value. So sessionIDs should start at 1. Lauren: This impacts indexing on sessionTable in MIB. Consensus: Disallow 0 as sessionID; it was decided to take the question of whether sessionIDs should be unique across all transports back to the list for further discussion. Additional error codes: At least two more are needed. A 'genError' error code, and a code to indicate that a registration was rejected by the master agent for administrative reasons ("you want to register something I don't want to let you register"). It was thought that this should be discussed on the list, to see if any other error codes were needed. Support for disman Credential Delegation Service (CDS): Deferred for now. Topics concerning the text of the protocol draft included: 1) The word "subagent" should often be "session" 2) openPDU response has sysUpTime in _default_ context 3) Elements of procedure for Notify 4) Cleanup the test/commit/undo text: - "PDU" not "transaction" - Don't refer to "multiple varbinds" in all PDUs if it really only applies to Test PDUs. - "all subagents" should be "all involved sessions" - Master agent will not do multiple sets on the same session. - Prohibit concurrent transactions. 5) Index allocation (Juergen's posted question) - Clarify the contents of v.name (no instance information). 6) "using index allocation" should be "registering stuff". - Use of default priority - Should default == 128? - Handling duplicates - Make clear that allocating indexes is not mandatory for registration 7) Remove "splitting" text where possible, replace with "overlapping registration". Lauren Heintz (BMC) gave an overview of the AgentX MIB as described in draft-ietf-agentx-mib-02.txt. She also discussed the MIB issues she had posted to the list on the preceding Friday. Bob Natale concluded the meeting with a brief summary of status and the work to be done. He noted that because interoperability testing was not complete, we were not in a position to petition for advancement of RFC 2257 (recycle at Proposed). He then outlined action items for the next phase of work, including: 1) An updated MIB 2) Posting of revised issues to list within a week. 3) New protocol draft with changes agreed upon at this meeting and on the list, within 5 weeks. From remove@alpha-com.net Fri Nov 6 01:38:42 1998 Received: from tangelo.bmc.com (liverbird.bmc.com [198.207.223.252]) by ietf.org (8.8.5/8.8.7a) with ESMTP id BAA23171 for ; Fri, 6 Nov 1998 01:38:41 -0500 (EST) 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 AAA00783; Fri, 6 Nov 1998 00:24:17 -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 WAA18318 for ; Thu, 5 Nov 1998 22:15:25 -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 AAA29463 for ; Fri, 6 Nov 1998 00:15:23 -0600 (CST) Received: from mail.alpha-com.net (host-209-214-80-93.ath.bellsouth.net [209.214.80.93]) by brutus.daloft.com (8.9.0/8.8.5) with SMTP id BAA28447; Fri, 6 Nov 1998 01:12:01 -0500 Message-Id: <199811060612.BAA28447@brutus.daloft.com> From: AlphaCom Date: Fri, 06 Nov 1998 00:57:39 Subject: Cheap PC Parts and Internet Services We invite you to visit the site of AlphaCom Technologies, Inc. We provide custom PC's, Servers, Computer Components, Dram, Modules, and full ISP-Internet services. We kindly Thank you for your time. http://www.alpha-com.net "Providing InSight into Worlds of Information" __________________________________________________________ If you wish to be removed from this advertiser's future mailings, please reply with the subject "REMOVE" and we will remove your email address from the list, thank you. From remove@alpha-com.net Fri Nov 6 13:43:49 1998 Received: from tangelo.bmc.com (liverbird.bmc.com [198.207.223.252]) by ietf.org (8.8.5/8.8.7a) with ESMTP id NAA03614 for ; Fri, 6 Nov 1998 13:43:48 -0500 (EST) 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 MAA03434; Fri, 6 Nov 1998 12:36: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 KAA24991 for ; Fri, 6 Nov 1998 10:35:19 -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 MAA02862 for ; Fri, 6 Nov 1998 12:35:17 -0600 (CST) Received: from mail.alpha-com.net (host-209-214-80-93.ath.bellsouth.net [209.214.80.93]) by brutus.daloft.com (8.9.0/8.8.5) with SMTP id NAA24165; Fri, 6 Nov 1998 13:28:56 -0500 Message-Id: <199811061828.NAA24165@brutus.daloft.com> From: AlphaCom Date: Fri, 06 Nov 1998 13:14:21 Subject: Cheap PC Parts and Internet Services We invite you to visit the site of AlphaCom Technologies, Inc. We provide custom PC's, Servers, Computer Components, Dram, Modules, and full ISP-Internet services. We kindly Thank you for your time. http://www.alpha-com.net "Providing InSight into Worlds of Information" __________________________________________________________ If you wish to be removed from this advertiser's future mailings, please reply with the subject "REMOVE" and we will remove your email address from the list, thank you. From scharf@cisco.com Fri Nov 6 14:02:38 1998 Received: from tangelo.bmc.com (liverbird.bmc.com [198.207.223.252]) by ietf.org (8.8.5/8.8.7a) with ESMTP id OAA03929 for ; Fri, 6 Nov 1998 14:02:37 -0500 (EST) 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 MAA09586; Fri, 6 Nov 1998 12:56:07 -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 KAA25500 for ; Fri, 6 Nov 1998 10:55:49 -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 MAA09456 for ; Fri, 6 Nov 1998 12:55:48 -0600 (CST) Received: from localhost (scharf@localhost) by stbernard.cisco.com (8.8.5-Cisco.2-SunOS.5.5.1.sun4/8.6.5) with SMTP id KAA21289 for ; Fri, 6 Nov 1998 10:55:26 -0800 (PST) Message-Id: <199811061855.KAA21289@stbernard.cisco.com> X-Mailer: exmh version 2.0.2 2/24/98 To: agentx@peer.com Subject: time to turn on SPAM filtering on this list Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 06 Nov 1998 10:55:26 -0800 From: Jerry Scharf Clearly this list has made it onto some resale SPAM lists. Who is on the hook to do this and when can we expect relief? jerry From rpresuhn@dorothy.bmc.com Fri Nov 6 16:55:10 1998 Received: from tangelo.bmc.com (liverbird.bmc.com [198.207.223.252]) by ietf.org (8.8.5/8.8.7a) with ESMTP id QAA06831 for ; Fri, 6 Nov 1998 16:55:09 -0500 (EST) 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 PAA05043; Fri, 6 Nov 1998 15:46:34 -0600 (CST) Received: (from rpresuhn@localhost) by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) id NAA27151 for agentx@peer.com; Fri, 6 Nov 1998 13:45:11 -0800 (PST) Date: Fri, 6 Nov 1998 13:45:11 -0800 (PST) From: Randy Presuhn Message-Id: <199811062145.NAA27151@dorothy.bmc.com> To: agentx@peer.com Subject: Re: time to turn on SPAM filtering on this list Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Hi - > From scharf@cisco.com Fri Nov 6 10:56:39 PST 1998 > To: agentx@peer.com > Subject: time to turn on SPAM filtering on this list > Date: Fri, 06 Nov 1998 10:55:26 -0800 > From: Jerry Scharf > > Clearly this list has made it onto some resale SPAM lists. Who is on the hook > to do this and when can we expect relief? > > jerry The list is currently manually maintained. We have list server software available, but have been reluctant to deploy it, given the very bad experiences many of us have had with anti-spam blocking on other lists. (For example, I'm now unable to post to the applmib list even though I'm one of the document editors!) If Cisco would be willing to take over the list and provide spam filtering superior to what we've seen on the entmib, rmonmib, and other lists they handle, without blocking postings from working group members, let's talk. ----------------------------------------------------------------------- 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 abierman@cisco.com Fri Nov 6 17:37:53 1998 Received: from tangelo.bmc.com (liverbird.bmc.com [198.207.223.252]) by ietf.org (8.8.5/8.8.7a) with ESMTP id RAA07859 for ; Fri, 6 Nov 1998 17:37:52 -0500 (EST) 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 QAA17260; Fri, 6 Nov 1998 16:28:24 -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 OAA27804 for ; Fri, 6 Nov 1998 14:27:19 -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 QAA16928; Fri, 6 Nov 1998 16:27:18 -0600 (CST) Received: from cisco.com (abierman-ss20.cisco.com [171.69.221.95]) by peridot.cisco.com (8.8.5-Cisco.1/8.6.5) with ESMTP id OAA22115; Fri, 6 Nov 1998 14:27:03 -0800 (PST) Sender: abierman@cisco.com Message-ID: <364377B8.B7E413A3@cisco.com> Date: Fri, 06 Nov 1998 14:27:04 -0800 From: Andy Bierman Organization: Cisco Systems, Inc. X-Mailer: Mozilla 4.07 [en] (X11; U; SunOS 5.5.1 sun4m) MIME-Version: 1.0 To: Randy Presuhn CC: agentx@peer.com Subject: Re: time to turn on SPAM filtering on this list References: <199811062145.NAA27151@dorothy.bmc.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Randy Presuhn wrote: > > Hi - > > > From scharf@cisco.com Fri Nov 6 10:56:39 PST 1998 > > To: agentx@peer.com > > Subject: time to turn on SPAM filtering on this list > > Date: Fri, 06 Nov 1998 10:55:26 -0800 > > From: Jerry Scharf > > > > Clearly this list has made it onto some resale SPAM lists. Who is on the hook > > to do this and when can we expect relief? > > > > jerry > > The list is currently manually maintained. We have list server software > available, but have been reluctant to deploy it, given the very bad > experiences many of us have had with anti-spam blocking on other lists. > (For example, I'm now unable to post to the applmib list even though > I'm one of the document editors!) > > If Cisco would be willing to take over the list and provide spam filtering > superior to what we've seen on the entmib, rmonmib, and other lists they > handle, without blocking postings from working group members, let's talk. > I am the owner of the rmonmib@cisco.com and entmib@cisco.com mailing lists. That just means all the owner-foobar mail comes to me. I'm not allowed to touch the majordomo server that runs these lists. The organization that runs this server has no charter to support 'external' (e.g., IETF WG) mailing lists. I have someone in that group who is spending some background time on SPAM filtering, but he has many things in the queue ahead of it. I've lined up a new home for the rmonmib WG list, which I hope to get done before the new year. I don't think we (cisco) are in any position to complain about SPAM on WG mailing lists, or in any way capable of taking on more external mailing lists. The IETF position on SPAM is that it's not their problem. It's up to the organization that runs each list server to control SPAM on that list. I think events in recent months have caused a re-evaluation of this position. It has been pointed out (by Karl Auerbach) that SPAMers are stealing CPU and bandwidth resources from the organizations running list servers. The rmonmib list is so big that this amounts to several minutes of server time for every message sent to the list. But it's still way too little actual dollars to ask the legal dept. to go after SPAMmers. Meanwhile, those of us involved in IETF WGs get bombarded by SPAM sent to the WG mailing lists. Andy > ----------------------------------------------------------------------- > 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 Nov 6 18:34:25 1998 Received: from tangelo.bmc.com (liverbird.bmc.com [198.207.223.252]) by ietf.org (8.8.5/8.8.7a) with ESMTP id SAA08847 for ; Fri, 6 Nov 1998 18:34:24 -0500 (EST) 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 RAA04640; Fri, 6 Nov 1998 17:27:26 -0600 (CST) Received: (from rpresuhn@localhost) by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) id PAA28259; Fri, 6 Nov 1998 15:26:31 -0800 (PST) Date: Fri, 6 Nov 1998 15:26:31 -0800 (PST) From: Randy Presuhn Message-Id: <199811062326.PAA28259@dorothy.bmc.com> To: abierman@cisco.com Subject: Re: time to turn on SPAM filtering on this list Cc: agentx@peer.com Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Hi - > Date: Fri, 06 Nov 1998 14:27:04 -0800 > From: Andy Bierman > Organization: Cisco Systems, Inc. > To: Randy Presuhn > CC: agentx@peer.com > Subject: Re: time to turn on SPAM filtering on this list > References: <199811062145.NAA27151@dorothy.bmc.com> ... > I am the owner of the rmonmib@cisco.com and entmib@cisco.com > mailing lists. That just means all the owner-foobar mail comes > to me. I'm not allowed to touch the majordomo server that runs > these lists. The organization that runs this server has no charter > to support 'external' (e.g., IETF WG) mailing lists. I have someone > in that group who is spending some background time on SPAM filtering, > but he has many things in the queue ahead of it. I've lined up a new > home for the rmonmib WG list, which I hope to get done before the new > year. ... Our situation isn't as difficult as yours. Although we have no control over the BMC.COM email infrastructure, the people once known as Peer Networks have managed to keep some control over the various distribution lists hosted at PEER.COM addresses. Of course, that has resulted in difficult moments, like the times the firewalls were configured to block all peer.com (and bgs.com and datatools.com) access. The Majordomo code is available to Lauren, but I'd hope that she and Bob Natale work out a solution to the subscriber/submitter problem before deploying it. In any case, your points are important ones. In volunteer organizations like this, we have to be careful about where we spend our cycles. ----------------------------------------------------------------------- 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 Lauren_Heintz@crow.bmc.com Tue Nov 10 13:55:54 1998 Received: from tangelo.bmc.com (fw-us-hou-2.bmc.com [198.207.223.251]) by ietf.org (8.8.5/8.8.7a) with ESMTP id NAA03006 for ; Tue, 10 Nov 1998 13:55:54 -0500 (EST) 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 MAA12956; Tue, 10 Nov 1998 12:52:47 -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 KAA22419 for ; Tue, 10 Nov 1998 10:48:21 -0800 (PST) Received: from localhost (root@localhost) by tangelo.bmc.com (8.8.6 (PHNE_14041)/8.8.6) with SMTP id MAA09746; Tue, 10 Nov 1998 12:44:43 -0600 (CST) X-OpenMail-Hops: 2 Date: Tue, 10 Nov 1998 12:44:19 -0600 Message-Id: Subject: TAddress TC MIME-Version: 1.0 TO: agentx@peer.com, snmpv3@tis.com Content-Type: text/plain; charset=US-ASCII; name="BDY.TXT" Content-Disposition: inline; filename="BDY.TXT" Content-Transfer-Encoding: 7bit I am posting this to both the AgentX and snmpv3 lists. The TAddress TC indicates that the minimum len for such values is 1. However, there seem to be cases where valid values of TAddress could be 0. For example, the agentxConnTransportAddress object in the draft AgentX MIB is defined as follows. 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 } Seems that several options are available to solve this: 1. Change the TAddress TC to allow zero-length values. 2. Define a new standard TAddress-style TC that allows zero-length values. 3. Change the agentxConnTransportAddress description and all such objects in other affected MIBs that might need zero-length TAddress values) to something more appropriate. Also, I'd like to comment on a general practice I've seen of defining standard TC's that disallow NULL values of the type. Seems that the only advantage in doing so is to allow a very few MIB designers to not have to include a SIZE spec on a very few MIB objects. The disadvantages, on the other hand, seem greater. It makes it harder to implement MIBs (might not be able to set default values for a given column or specify a wildcard for the value), and the designs of some MIB objects might have to revert to tricks (i.e. define alternate TCs, or specify a special non-zero-length value which shall serve as a NULL value) to be implemented correctly. To me, it would be SLIGHTLY analagous to the designers of the C language forbidding NULL pointers. I stress the word, slightly, in the previous sentence. :) I would hope that in the future we would be more suspicious of defining new TCs that disallow a NULL value. Thanks, Lauren ------------------------------------------------------------------------ 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 ------------------------------------------------------------------------ From Randy_Presuhn@crow.bmc.com Tue Nov 10 17:47:36 1998 Received: from tangelo.bmc.com (fw-us-hou-2.bmc.com [198.207.223.251]) by ietf.org (8.8.5/8.8.7a) with ESMTP id RAA11618 for ; Tue, 10 Nov 1998 17:47:36 -0500 (EST) 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 QAA03328; Tue, 10 Nov 1998 16:45:32 -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 OAA23714 for ; Tue, 10 Nov 1998 14:44:44 -0800 (PST) Received: from sthelena (STHELENA.bmc.com [192.146.153.146]) by tangelo.bmc.com (8.8.6 (PHNE_14041)/8.8.6) with SMTP id QAA02935; Tue, 10 Nov 1998 16:44:40 -0600 (CST) Message-Id: <199811102244.QAA02935@tangelo.bmc.com> From: "Randy Presuhn" To: , Subject: RE: TAddress TC Date: Tue, 10 Nov 1998 14:43:57 -0800 X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook 8.5, Build 4.71.2173.0 In-Reply-To: Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.22 Hi - > From: Lauren_Heintz@crow.bmc.com [mailto:Lauren_Heintz@crow.bmc.com] > Sent: Tuesday, 10 November, 1998 10:44 > To: agentx@peer.com; snmpv3@tis.com > Subject: TAddress TC ... > The TAddress TC indicates that the minimum len > for such values is 1. However, there seem to be > cases where valid values of TAddress could be 0. ... We encountered a similar case in the Application MIB work. We ended up defining a new TC, "ApplTAddress", which looks suspiciously like TAddress, except that it allows length 0. ----------------------------------------------------------------------- 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 dperkins@dsperkins.com Wed Nov 11 16:18:51 1998 Received: from tangelo.bmc.com (fw-us-hou-2.bmc.com [198.207.223.251]) by ietf.org (8.8.5/8.8.7a) with ESMTP id QAA20174 for ; Wed, 11 Nov 1998 16:18:49 -0500 (EST) 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 PAA28684; Wed, 11 Nov 1998 15:17:15 -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 NAA05006 for ; Wed, 11 Nov 1998 13:13:10 -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 PAA27307; Wed, 11 Nov 1998 15:13:05 -0600 (CST) Received: from branco.desktalk.com (peace [134.70.18.99]) by crymea.desktalk.com (8.8.8/8.7.2) with SMTP id NAA02728; Wed, 11 Nov 1998 13:12:07 -0800 (PST) Received: from dperkins4.sj.scruznet.com by branco.desktalk.com (SMI-8.6/SMI-SVR4) id MAA03553; Wed, 11 Nov 1998 12:56:14 -0800 Date: Wed, 11 Nov 98 13:56:38 pst From: David Perkins Subject: RE: TAddress TC To: agentx@peer.com, snmpv3@tis.com, Lauren_Heintz@crow.bmc.com X-Mailer: Chameleon V0.05, TCP/IP for Windows, NetManage Inc. Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII; NAME="BDY.TXT" HI, Lauren shows below a good example of how not to use the term "null" in SNMP MIB definitions. The term "null" means different things based on where it is used. In SNMP, the term "null" is not defined. In SNMP, when one is describing values of the OCTET STRING or BITS data types, a value with a length of zero is a "zero length string". This is very different from a "missing value", that is, what you get when you try to retrieve the value of an instance that does not exist, and the SNMP operation returns an error such as noSuchName or an exception value such as noSuchInstance. In SQL, missing value are called null values, and a null value is VERY different than a zero length string value. ASN.1, from which SNMP uses elements, contains the data type NULL and the data value NULL. It doesn't include the term "null". So please do not write descriptions like that shown below. It is confusing to read, since the term "null" is not defined in SNMP. Does the description mean that the value will be a zero length string, or does it mean that an instance of the object does not exist when the transport type is unix-domain sockets. I can't tell. On Tue, 10 Nov 1998 12:44:19 -0600 Lauren_Heintz@crow.bmc.com wrote: >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 } > Regards, /dperkins@dsperkins.com, David T. Perkins Date: 11/11/98, Time: 13:56:38 From ashishkh@wipinfo.soft.net Thu Nov 12 01:33:13 1998 Received: from tangelo.bmc.com (fw-us-hou-2.bmc.com [198.207.223.251]) by ietf.org (8.8.5/8.8.7a) with ESMTP id BAA06551 for ; Thu, 12 Nov 1998 01:33:11 -0500 (EST) 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 AAA26307; Thu, 12 Nov 1998 00:32:00 -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 WAA14660 for ; Wed, 11 Nov 1998 22:30:18 -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 AAA25921 for ; Thu, 12 Nov 1998 00:30:12 -0600 (CST) Received: from tagore.wipinfo.soft.net by wipinfo.soft.net (SMI-8.6/SMI-SVR4) id LAA19379; Thu, 12 Nov 1998 11:53:41 -0500 From: "Ashish Hanwadikar" To: Cc: "Agentx" Subject: unsubscribe Date: Thu, 12 Nov 1998 11:59:47 +0530 Message-ID: <000001be0e05$d8926250$163409c0@opel.wipinfo.soft.net> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook 8.5, Build 4.71.2173.0 X-Mimeole: Produced By Microsoft MimeOLE V4.72.2106.4 Importance: Normal unsubscribe From kraj@tagore.wipinfo.soft.net Thu Nov 12 01:40:15 1998 Received: from tangelo.bmc.com (fw-us-hou-2.bmc.com [198.207.223.251]) by ietf.org (8.8.5/8.8.7a) with ESMTP id BAA06591 for ; Thu, 12 Nov 1998 01:40:11 -0500 (EST) From: kraj@tagore.wipinfo.soft.net 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 AAA27755; Thu, 12 Nov 1998 00:39:09 -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 WAA14692 for ; Wed, 11 Nov 1998 22:38:59 -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 AAA27691 for ; Thu, 12 Nov 1998 00:38:54 -0600 (CST) Received: from tagore.wipinfo.soft.net by wipinfo.soft.net (SMI-8.6/SMI-SVR4) id MAA23416; Thu, 12 Nov 1998 12:02:35 -0500 Message-ID: <9811121219.AA29392@tagore.wipinfo.soft.net> Subject: subscribe To: agentx-request@peer.com Date: Thu, 12 Nov 1998 12:18:54 +0530 (IST) Cc: agentx@peer.com X-Mailer: ELM [version 2.4 PL23] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit subscribe From kraj@wipinfo.soft.net Sat Nov 14 02:44:01 1998 Received: from tangelo.bmc.com (fw-us-hou-2.bmc.com [198.207.223.251]) by ietf.org (8.8.5/8.8.7a) with ESMTP id CAA00698 for ; Sat, 14 Nov 1998 02:44:00 -0500 (EST) 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 BAA28220; Sat, 14 Nov 1998 01:42:48 -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 XAA16147 for ; Fri, 13 Nov 1998 23:35: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 BAA27250 for ; Sat, 14 Nov 1998 01:35:18 -0600 (CST) Received: from scan.wipinfo.soft.net by donald.wipinfo.soft.net (SMI-8.6/SMI-SVR4) id NAA01528; Sat, 14 Nov 1998 13:08:43 -0500 Received: from 192.9.100.151 by scan.wipinfo.soft.net (InterScan E-Mail VirusWall NT) Received: from wipinfo.soft.net ([192.9.52.87]) by divya.wipinfo.soft.net (8.8.5/8.8.5) with ESMTP id NAA31925 for ; Sat, 14 Nov 1998 13:06:21 +0530 Sender: kraj@wipinfo.soft.net Message-ID: <364D33CB.E0F58940@wipinfo.soft.net> Date: Sat, 14 Nov 1998 13:09:55 +0530 From: Kantharaju Organization: Wipro Infotech , Technology solutions. X-Mailer: Mozilla 4.04 [en] (X11; I; HP-UX B.10.01 9000/712) MIME-Version: 1.0 To: agentx@peer.com Subject: subscribe Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit subscribe From bnatale@acecomm.com Mon Nov 16 11:35:03 1998 Received: from tangelo.bmc.com (fw-us-hou-2.bmc.com [198.207.223.251]) by ietf.org (8.8.5/8.8.7a) with ESMTP id LAA04627 for ; Mon, 16 Nov 1998 11:35:01 -0500 (EST) 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 KAA22289; Mon, 16 Nov 1998 10:30:24 -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 IAA09378 for ; Mon, 16 Nov 1998 08:22:37 -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 KAA19041; Mon, 16 Nov 1998 10:22:35 -0600 (CST) Received: from [192.152.208.5] (helo=acecomm.com) by relay1.smtp.psi.net with smtp (Exim 1.90 #1) id 0zfRQ4-0007OY-00; Mon, 16 Nov 1998 11:22:29 -0500 Received: from bnatale by acecomm.com (5.65/3.2.083191-ACE*COMM) id AA26569; Mon, 16 Nov 1998 11:25:12 -0500 Message-Id: <4.1.19981116111821.00ad5a20@nips.acec.com> X-Sender: natale@nips.acec.com X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1 Date: Mon, 16 Nov 1998 11:26:18 -0500 To: Randy Presuhn From: Bob Natale Subject: Re: time to turn on SPAM filtering on this list Cc: agentx@peer.com In-Reply-To: <199811062326.PAA28259@dorothy.bmc.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" >At 11/6/98 03:26 PM, Randy Presuhn wrote: Hi Randy, <...> >The Majordomo code is available to Lauren, but I'd hope that she and >Bob Natale work out a solution to the subscriber/submitter problem >before deploying it. Thanks...I consider this completely up to BMC/Peer personnel...they are donating the resources and I will do everything I an to cooperate with whatever policy they deem best. >In any case, your points are important ones. In volunteer organizations >like this, we have to be careful about where we spend our cycles. Yes, that's true. On the WinSNMP list, I sometimes go after SPAMMERs and sometimes I don't...depending on current workload and how inclined I feel to take an action that probably won't really help much. It certainly appears for now the much more is to be gained by getting the following message out to all non-SPAMMERs: 1. Don't reply to SPAMMERs 2. Especially, don't include a list address in your reply to SPAMMERs 3. Don't follow SPAMMERs' instructions wrt REMOVE, etc. 4. If you have the time and inclination to take some action: 4a. complain to the ISPs you can identify in the SPAM's headers (even if they are not guilty parties themselves, they will be motivated to help clean it up); and 4b. complain to uce@ftc.gov; 4c. in both 4a and 4b actions, include a copy of the original SPAM *with full headers if at all possible*; and 4d. do not copy the list on either 4a or 4b. 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 Harald@Alvestrand.no Thu Nov 19 07:39:46 1998 Received: from tangelo.bmc.com (fw-us-hou-2.bmc.com [198.207.223.251]) by ietf.org (8.8.5/8.8.7a) with ESMTP id HAA08132 for ; Thu, 19 Nov 1998 07:39:46 -0500 (EST) 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 GAA18493; Thu, 19 Nov 1998 06:36:10 -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 EAA20347 for ; Thu, 19 Nov 1998 04:31:46 -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 GAA17966; Thu, 19 Nov 1998 06:31:44 -0600 (CST) Received: from alden ([10.128.1.82]) by dokka.maxware.no (8.8.7/8.8.7) with SMTP id NAA29460; Thu, 19 Nov 1998 13:30:58 +0100 Message-Id: <3.0.2.32.19981119133117.014bd100@dokka.maxware.no> X-Sender: hta@dokka.maxware.no X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.2 (32) Date: Thu, 19 Nov 1998 13:31:17 +0100 To: Bob Natale , Randy Presuhn From: Harald Tveit Alvestrand Subject: Re: time to turn on SPAM filtering on this list Cc: agentx@peer.com In-Reply-To: <4.1.19981116111821.00ad5a20@nips.acec.com> References: <199811062326.PAA28259@dorothy.bmc.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" 1) About running Majordomo as a spam filter: I run lists under Majordomo, and have very little problem with spam. My solution runs in 2 parts: a) Configure the restrict_post keyword in config to have 2 files. Example for ietf-types@alvestrand.no: restrict_post = ietf-types ietf-types-submit Majordomo thinks "ietf-types-submit" is a mailing list, but Sendmail makes sure it's impossible to send mail to it, by not having any alias for it but "ietf-types-submit-request". b) A vigilant watcher of "BOUNCE" messages (me....arrgghh...) who, whenever a legitimate posting bounces, adds the poster to the relevant -submit list and approves the message. Most of the time, I don't think the poster notices the delay. Very few complaints so far. 2) About list hosting. In the past, the Internet Mail Consortium (postmaster@imc.org) has been very good about hosting lists, and they have done a decent job of maintaining them. I don't know if Agentx is considered relevant to them, but it doesn't hurt to ask, if no other qualified host can be found. Have fun! Harald A -- Harald Tveit Alvestrand, Maxware, Norway Harald.Alvestrand@maxware.no From barryz145@berkscountypa.com Tue Nov 24 04:42:31 1998 Received: from tangelo.bmc.com (fw-us-hou-2.bmc.com [198.207.223.251]) by ietf.org (8.8.5/8.8.7a) with ESMTP id EAA14821 for ; Tue, 24 Nov 1998 04:42:31 -0500 (EST) From: barryz145@berkscountypa.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 DAA03755; Tue, 24 Nov 1998 03:39: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 BAA24843 for ; Tue, 24 Nov 1998 01:34: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 DAA02925 for ; Tue, 24 Nov 1998 03:34:25 -0600 (CST) Date: Tue, 24 Nov 1998 03:34:25 -0600 (CST) Message-Id: <199811240934.DAA02925@tangelo.bmc.com> Received: from [205.148.246.213] by berkscountypa.com id 23d80.wrk; Tue, 24 Nov 1998 04:30:48 EDT To: Subject: What's new in Windows 98? What's New in Windows 98? Don't we all want to know! Here's a cool website that will tell you, and it's free. http://college.1usa.com/whatsnewin98.html What I like about it the most is that you can take a Quiz before and after, and it will tell you how much you've learned. Slick stuff. BarryZ