Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa05405; 1 Apr 93 13:26 EST Received: from CNRI.RESTON.VA.US by IETF.CNRI.Reston.VA.US id aa05401; 1 Apr 93 13:26 EST Received: from THOR.INNOSOFT.COM by CNRI.Reston.VA.US id aa16533; 1 Apr 93 13:26 EST Received: from INNOSOFT.COM by INNOSOFT.COM (PMDF V4.2-11 #1336) id <01GWHQQZE6E88Y4YWX@INNOSOFT.COM>; Thu, 1 Apr 1993 09:47:00 PST Received: from relay.hp.com by INNOSOFT.COM (PMDF V4.2-11 #1336) id <01GWHQQQUAA88Y4ZBP@INNOSOFT.COM>; Thu, 1 Apr 1993 09:46:44 PST Received: from hpindda.cup.hp.com by relay.hp.com with SMTP (16.6/15.5+IOS 3.13) id AA07039; Thu, 1 Apr 93 09:46:36 -0800 Received: by hpindda.cup.hp.com (15.11/15.5+IOS 3.20+cup+OMrelay) id AA21641; Thu, 1 Apr 93 09:48:42 pst Date: Thu, 01 Apr 1993 09:48:38 -0800 (PST) Sender:ietf-archive-request@IETF.CNRI.Reston.VA.US From: Eva Kuiper Subject: RE: your mail In-reply-to: <199304010222.AA18745@comm.Tandem.COM>; from "LEBECK_SUE@tandem.com" at Apr 1, 93 2:21 am To: LEBECK_SUE@tandem.com Cc: s.kille@isode.com, ietf-madman@innosoft.com, ifip-emailmgt@ics.uci.edu, pjb@mbunix.mitre.org, eva@hpindda.cup.hp.com Errors-to: ned+madman-errors@INNOSOFT.COM Resent-message-id: <01GWHQQZKC828Y4YWX@INNOSOFT.COM> Message-id: <9304011748.AA21641@hpindda.cup.hp.com> X-VMS-To: IN%"LEBECK_SUE@tandem.com" X-VMS-Cc: IN%"s.kille@isode.com", IN%"ietf-madman@INNOSOFT.COM", IN%"ifip-emailmgt@ics.uci.edu", IN%"pjb@mbunix.mitre.org", IN%"eva@hpindda.cup.hp.com" Content-type: TEXT/PLAIN; CHARSET=US-ASCII Content-transfer-encoding: 7BIT Mailer: Elm [revision: 64.9] Status: OR Sue, I agree with your suggestions. I also would add, though, that since MADMAN would have real, tested, interworking implementations way before EMAIL-MGMT has reached consensus on the objects, it will likely occur the other way around, that EMAIL-MGMT will absorb the objects from MADMAN rather than MADMAN re-engineer to incorporate what EMAIL-MGMT has done. I think that one MIB is essential, and I'd like to see EMAIL-MGMT working closely with MADMAN so that the management objects in EMAIL-MGMT are those which have been shown to be useful in the working environment which the Internet provides. For these reasons, I think the two groups need to work closely together. I also think that your proposal will facilitate achieving the goal of one MIB. Cheers, Eva Kuiper HP > stef@nma.com > Subject: A suggestion re: MADMAN and EMAIL-MGMT > > > ------------ REPLY ATTACHMENT -------- > SENT 04-01-93 FROM LEBECK_SUE > > > Steve -- > > I join yourself and others in the belief that it is > critical that a single MIB be developed which represents > the needs of SMTP, X.400, and other messaging systems. > To create a separate set of "open objects" for each messaging > system type, and to leave it to the managment application > to present a normalized view of all this stuff to the management > user, is to shortchange the potential of open network management. > > Motivated by this belief, I recently took responsibility > within the Email-Mgmt group to lead a technical effort > to help ensure that the MIB defined by that group will be > generic to all messaging systems wherever possible, and > to organize messaging-system-specific aspects using > mechanisms designed for that (e.g. conditional packages > within Object definitions.) > > I believe it would be extremely beneficial to our mutual purposes > if representation from the MADMAN group participated in this effort. > (Through other vendor interest groups to which I belong, I have > contacts which represent a variety of other messaging systems. > I will also be soliciting input/participation from these contingents.) > > I appreciate your desire not to de-focus, and thus slow down, your > group's efforts. However, if the single-MIB goal is ever to be > reached, your target audience will need to re-engineer at some point > if it is to benefit from the single-MIB. > Longer-range re-engineering by your target community can be > minimized if we work together to reach common definitions where > possible at the outset. > > I can easily imagine a process whereby our work efforts could be > aligned. One idea: > > - We contribute object definitions as input for your group's use. > (We have a contact person who is collecting existing object > definitions. These definitions come from X.400 management > pilots, from proprietary management systems for X.400, > from proprietary management systems for non-X.400 messaging > systems, etc.) > > - Your group could in turn contribute your draft objects back > into our collection point. > > - We would include your objects in our definition and normalization > activities,and contribute back proposed modifications to your > objects. > > Participation in this process by MADMAN members would optimize the > acceptability of these proposals to your group. > > - We would need to understand your timetable, and work out > a feedback loop that fits within those timing constraints. > > Being largely unfamiliar with MADMAN, I may be making suggestions > that are not entirely appropriate. > I welcome alternate process suggestions from you. > > To expedite this, I would be happy to host a meeting to discuss > how we can organize our efforts to our mutual benefit. > A face-to-face discussion would likely enhance our progress. > > I have high regard for work that has been conducted under your > leadership. I would welcome the opportunity to work with you on this. > > I look forward to your hearing your thoughts, > Cheers, > Sue (Klein) Lebeck > > p.s. It's important to note that, altho' the Requirements list > developed/collected by the Email-mgmt group is substantial, > I don't believe we have any requirement to fulfill all those > requirements in a first pass. Instead, we will begin by > defining objects which address the needs of a base set of > requirements, and build from there. > >   Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa09901; 1 Apr 93 23:58 EST Received: from CNRI.RESTON.VA.US by IETF.CNRI.Reston.VA.US id aa09897; 1 Apr 93 23:58 EST Received: from THOR.INNOSOFT.COM by CNRI.Reston.VA.US id aa03317; 1 Apr 93 23:58 EST Received: from INNOSOFT.COM by INNOSOFT.COM (PMDF V4.2-11 #1336) id <01GWIDCIFZUO8Y4ZH4@INNOSOFT.COM>; Thu, 1 Apr 1993 20:34:14 PST Received: from ics.uci.edu by INNOSOFT.COM (PMDF V4.2-11 #1336) id <01GWIDCDNQ348Y5019@INNOSOFT.COM>; Thu, 1 Apr 1993 20:34:04 PST Received: from ics.uci.edu by q2.ics.uci.edu id aa10478; 1 Apr 93 19:55 PST Date: Thu, 01 Apr 1993 19:55:21 -0800 Sender:ietf-archive-request@IETF.CNRI.Reston.VA.US From: Einar Stefferud Subject: In-reply-to: 01 Apr 1993 02:21:00 +0200. <199304010222.AA18745@comm.Tandem.COM> X-Orig-Sender: stef@ics.uci.edu To: LEBECK_SUE@tandem.com Cc: s.kille@isode.com, ietf-madman@innosoft.com, ifip-emailmgt@ics.uci.edu, pjb@mbunix.mitre.org Cc: stef@nma.com Errors-to: ned+madman-errors@INNOSOFT.COM Reply-to: stef@nma.com Resent-message-id: <01GWIDCIJ7LE8Y4ZH4@INNOSOFT.COM> Message-id: <10475.733722921@ics.uci.edu> X-VMS-To: IN%"LEBECK_SUE@tandem.com" X-VMS-Cc: IN%"s.kille@isode.com", IN%"ietf-madman@INNOSOFT.COM", IN%"ifip-emailmgt@ics.uci.edu", IN%"pjb@mbunix.mitre.org" Content-type: TEXT/PLAIN; CHARSET=US-ASCII Content-transfer-encoding: 7BIT Status: OR Hi All -- Thsi is to clarify the results of our MADMAN and EMGT meetings on coordination here at IETF. I think we have a handle on it all. We have cross participation between the two groups with Ned Freed (MADMAN Doc Editor) and Harald Alverstrand (EMGT Modeling Task Team Leader). What we need next is a complete esxchange of relvant documetns with Bernard Ferret who is leading the OIW based MO/MIB development effort. We should make sure that we have excahnged all available MIB examples, and the MADMAN draft should go to Bernad for his group. We will also want cross participation between MADMAN and Bernard's MO/MIB Task Team. So, things are on a proper track, and I look forward to fruitful collaboration. Cheers...\Stef   Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa04660; 7 Apr 93 10:02 EDT Received: from CNRI.RESTON.VA.US by IETF.CNRI.Reston.VA.US id ac04638; 7 Apr 93 10:02 EDT Received: from THOR.INNOSOFT.COM by CNRI.Reston.VA.US id aa07617; 7 Apr 93 2:52 EDT Received: from INNOSOFT.COM by INNOSOFT.COM (PMDF V4.2-11 #1336) id <01GWPII6481S8Y4ZGK@INNOSOFT.COM>; Tue, 6 Apr 1993 23:17:07 PDT Received: from ics.uci.edu by INNOSOFT.COM (PMDF V4.2-11 #1336) id <01GWPII10N8W8Y524Y@INNOSOFT.COM>; Tue, 6 Apr 1993 23:16:57 PDT Received: from nma.com by q2.ics.uci.edu id ak04561; 6 Apr 93 23:10 PDT Received: from localhost by odin.nma.com id aa16862; 6 Apr 93 22:23 PDT Date: Tue, 06 Apr 1993 22:23:02 -0700 Sender:ietf-archive-request@IETF.CNRI.Reston.VA.US From: Einar Stefferud Subject: RE: X.400 Managed Object Definitions In-reply-to: Your message of 06 Apr 1993 08:37:00 -0800. <9304061916.ae06280@ncrcom.DaytonOH.NCR.COM> X-Orig-Sender: stef@nma.com To: Jukka Saukkonen Cc: ifip-emailmgt@ics.uci.edu, ietf-madman@innosoft.com Errors-to: ned+madman-errors@INNOSOFT.COM Reply-to: Stef@nma.com Resent-message-id: <01GWPII67Z2Q8Y4ZGK@INNOSOFT.COM> Message-id: <16860.734160182@odin.nma.com> X-VMS-To: IN%"jukka@ccgate.sandiegoca.ncr.com" "Jukka Saukkonen" X-VMS-Cc: IN%"ifip-emailmgt@ics.uci.edu", IN%"ietf-madman@INNOSOFT.COM" Content-type: TEXT/PLAIN; CHARSET=US-ASCII Content-transfer-encoding: 7BIT Status: O Hello Jukka -- Yes, I am co-convenor (With Paul Brusil) of the IFIP-EMailMgt Working Group, which is first trying to complete some "pre-standards" work on REQUIREMENTS and MODELS before anyone can close on MO/MIB definitions. Actually, we are in a horse race between REQUIREMENTS/MODELS and MO/MIB DEFINITIONS. From message 6 Apr 93 08:37:00 PST: }To: Einar Steffarud } Network Management Associates }From: Jukka Saukkonen } NCR Network Products Division } }Einar, I got your name from Lisa Phifer @ Bellcore. } }I understand that you chair the X.400 Managed Object Definitions }working group for SNMP and GDMO. } }We are currently working on manageability for our X.400 product. }We would like to get any information that is available on }the X.400 Managed Object Definitions. } }Please, give me a call } }Jukka Saukkonen }Systems Architect }NCR Network Products Division }9900 Old Grove Road }San Diego, Ca 92131 }(619) 693-5617 } }Thank you, Jukka I will send you a copy of our Charter by separate message. You can request addition to our main IFIP-EMailMgt mailing list by request to . I am including all the contact information I have, for the benefit of all concerned. There are 4 (sub)groups working on REQUIREMENTS, MODELS, MO/MIB specs in the OIW context, and MIB specs in the IETF context. The IETF group is known as "MADMAN" and is well along on a 2nd draft SNMP MIB for X.400/SMTP. MADMAN is fully independent from IFIP-EMailMgt, and does not recognize any subordination to IFIP-EMailMgt, though we do have a good cross-participation. You are most welcome to join and participate in our efforts. If you have any MO/MIB specs that you can share, we will greatly appreciate seeing them. We already have a rather large collection. The relevant (sub)group chairs (and lists) are: Main EMailMgt Mailing List: -- Paul Brusil and Einar Stefferud -- for subscriptions. Requirements Task Team: -- Emily McCoy and Ray Freiwirth <5242391@mcimail.com> -- to join. Modeling Task Team: -- Harald Tveit Alvestrand to join. X.400 MO/MIB Task Team (OIW Based): -- Bernard Ferret -- to join. IETF MIB (MADMAN) Working Group: -- Steve Kille -- for subscriptions. Best...\Stef   Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa09876; 8 Apr 93 13:41 EDT Received: from CNRI.RESTON.VA.US by IETF.CNRI.Reston.VA.US id aa09872; 8 Apr 93 13:41 EDT Received: from THOR.INNOSOFT.COM by CNRI.Reston.VA.US id aa19294; 8 Apr 93 13:41 EDT Received: from INNOSOFT.COM by INNOSOFT.COM (PMDF V4.2-11 #1336) id <01GWRJN6HCY88Y52J8@INNOSOFT.COM>; Thu, 8 Apr 1993 10:11:45 PDT Received: from MCIGATEWAY.MCIMail.com by INNOSOFT.COM (PMDF V4.2-11 #1336) id <01GWRJN04F8G8Y52KS@INNOSOFT.COM>; Thu, 8 Apr 1993 10:11:35 PDT Received: from mcimail.com by MCIGATEWAY.MCIMail.com id ar10533; 8 Apr 93 16:49 GMT Date: Thu, 08 Apr 1993 16:45 +0000 (GMT) Sender:ietf-archive-request@IETF.CNRI.Reston.VA.US From: Action Motivation <0004367585@mcimail.com> Subject: NETWORK MANAGEMENT SHOWCASE FEATURING LIVE MULTI-VENDOR DEMOS To: NOMS To: OIW Security SIG To: Electronic Mail Management Group To: OIW NMSIG To: Regional Workshop To: ANSI To: MITRE-NADIS To: MITRE-OSI To: MITRE To: OSI Mgt Implementation To: OSI API To: IETF MADMAN Cc: Paul Brusil Errors-to: ned+madman-errors@INNOSOFT.COM Resent-message-id: <01GWRJN6KJPU8Y52J8@INNOSOFT.COM> Message-id: <81930408164518/0004367585NA1EM@mcimail.com> X-VMS-To: IN%"NOMS@tdd.sj.nec.com" "NOMS" X-VMS-Cc: IN%"pjb@mbunix.mitre.org" "Paul Brusil" Content-type: TEXT/PLAIN; CHARSET=US-ASCII Content-transfer-encoding: 7BIT Status: O ============================================================= THE THIRD INTERNATIONAL SYMPOSIUM ON INTEGRATED NETWORK MANAGEMENT ============================================================= A UNIQUE OPPORTUNITY TO VIEW FIRST HAND THE LATEST IN NETWORK MANAGEMENT TECHNOLOGY ** WHERE: April 18-23,1993, The Sheraton Palace Hotel, San Francisco, CA ** WHAT: STATE-OF-THE-ART TECHNOLOGY CENTERS demonstrating new and emerging network management technologies, EXPERT SPEAKERS, THOUGHT-PROVOKING PANEL SESSIONS,IN-DEPTH TUTORIALS,TECHNICAL PAPERS - Gary Francis,James Herman, Marshall Rose, and more....... (See Communications Week ad of April 5, p. 48 for more details) ** WHO WILL BE THERE: 40 LEADING VENDORS discussing, demonstrating, and distributing literature about their network management products and capabilities, members of the research, development and academic communities, sophisticated end users, all with the COMMON OBJECTIVE OF MOVING NETWORK MANAGEMENT TECHNOLOGY FORWARD. ** VENDOR DAY: Wednesday, April 21, a full day devoted to Vendor presentations, a unique opportunity to hear directly from the vendor community. ** SHOWCASE FLOOR OPENS TUESDAY, APRIL 20 AT 12:00 P.M. ** LIVE NETWORK -- SEE THE LATEST IN SNMPV2, RMON, OSI, OMNIPOINT, AND NETWORK MANAGEMENT APPLICATIONS. Registration Information: Call +1 415 512 1316 Fax +1 415-512-1325 EMAIL amotive@mcimail.com Network Management Week Discount still available (includes Symposium registration and four Tutorial Sessions), Symposium Registration (excludes Tutorials), SHOWCASE FLOOR PASSES AND SPECIAL VENDOR DAY PASSES ARE AVAILABLE. Sponsored by the International Federation for Information Processing (IFIP) with participation by the Institute of Electrical and Electronics Engineers (IEEE) Communications Society and support from the Institute for Educational Services (IES).   Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa25382; 13 Apr 93 14:18 EDT Received: from CNRI.RESTON.VA.US by IETF.CNRI.Reston.VA.US id aa25378; 13 Apr 93 14:18 EDT Received: from thumper.bellcore.com by CNRI.Reston.VA.US id aa16908; 13 Apr 93 14:18 EDT Received: by thumper.bellcore.com (4.1/4.7) id for ietf-archive@nri.reston.va.us; Tue, 13 Apr 93 14:18:25 EDT Received: from MCIGATEWAY.MCIMail.com by thumper.bellcore.com (4.1/4.7) id for /usr/lib/sendmail -oi -fowner-snmp2 X-snmp2; Tue, 13 Apr 93 14:18:12 EDT Received: from mcimail.com by MCIGATEWAY.MCIMail.com id aj11108; 13 Apr 93 17:48 GMT Date: Tue, 13 Apr 93 17:47 GMT Sender:ietf-archive-request@IETF.CNRI.Reston.VA.US From: Action Motivation <0004367585@mcimail.com> To: NOMS To: OIW Security SIG To: Electronic Mail Management Group To: OIW NMSIG To: Regional Workshop To: ANSI To: MITRE-NADIS To: MITRE-OSI To: MITRE To: OSI Mgt Implementation To: OSI API To: IETF MADMAN To: Network Management To: Network Management To: Network Management Subject: Network Management Strategies for the 90's Message-Id: <40930413174704/0004367585NA3EM@mcimail.com> Status: O -------------------------------------------------------------------------- Network Management Strategies for the 90's -The ISINM '93 Showcase - RMON, SNMPv2, OSI, OMNIPoint, and Applications -------------------------------------------------------------------------- ****THE THIRD INTERNATIONAL SYMPOSIUM ON INTEGRATED NETWORK MANAGEMENT**** **APRIL 18-23, 1993, THE SHERATON PALACE HOTEL, SAN FRANCISCO, CA** Registration Information: CALL +1-415-512-1316 FAX +1-415-512-1325 or EMAIL - amotive@mcimail.com *LEARN how OMNIPoint can benefit you today while ensuring a smooth migration to the future. See the advantages of using a multi-technology, multi-standards approach.* *SEE interoperable RMON implementations by numerous vendors showcasing RMON agents and RMON management station tool sets* *TALK to the SNMPv2 authors and discover how SNMPv2, an evolutionary update to the SNMP framework, provides speed, security, systems management and manager-to-manager communications while continuing to co-exist with the huge installed base of SNMP products.* *DONT' MISS the OSI Technology Center demonstrations which will prove OSI management technology is real and supported by many vendors, service providers, and other organizations. *WATCH for the Applications Technology Center which will demonstrate the integration of independent management applications from many different vendors with each other and with the popular management platforms* ** VENDOR DAY, WEDNESDAY, APRIL 21, A FULL DAY DEVOTED TO VENDOR PRESENTATIONS** - Showcase Floor Passes and Special Vendor Day Passes Are Available Sponsored by the International Federation for Information Processing (IFIP) with participation by the Institute of Electrical and Electronics Engineers (IEEE) Communications Society and support from the Institute for Educational Services (IES).   Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa01440; 15 Apr 93 5:08 EDT Received: from CNRI.RESTON.VA.US by IETF.CNRI.Reston.VA.US id aa01436; 15 Apr 93 5:08 EDT Received: from THOR.INNOSOFT.COM by CNRI.Reston.VA.US id aa04073; 15 Apr 93 5:08 EDT Received: from INNOSOFT.COM by INNOSOFT.COM (PMDF V4.2-11 #1336) id <01GX0TCCORTS8Y55SX@INNOSOFT.COM>; Thu, 15 Apr 1993 01:26:29 PDT Received: from CEARN.CERN.CH (MAILER@CEARN) by INNOSOFT.COM (PMDF V4.2-11 #1336) id <01GX0TC8B8J48Y5621@INNOSOFT.COM>; Thu, 15 Apr 1993 01:26:20 PDT Received: from CEARN (NJE origin SMTP@CEARN) by CEARN.CERN.CH (LMail V1.1d/1.7f) with BSMTP id 2073; Thu, 15 Apr 1993 10:26:14 +0200 Received: from dxmint.cern.ch by CEARN.cern.ch (IBM VM SMTP V2R2) with TCP; Thu, 15 Apr 93 10:26:12 SET X400-Received: by mta chx400.switch.ch in /PRMD=switch/ADMD=arcom/C=CH/; Relayed; Thu, 15 Apr 1993 10:25:45 +0200 X400-Received: by /PRMD=SWITCH/ADMD=ARCOM/C=CH/; Relayed; Thu, 15 Apr 1993 10:25:36 +0200 Date: Thu, 15 Apr 1993 10:25:36 +0200 Sender:ietf-archive-request@IETF.CNRI.Reston.VA.US From: Urs Eppenberger Subject: Draft Columbus MADMAN BOF minutes To: ietf-madman Errors-to: ned+madman-errors@INNOSOFT.COM Resent-message-id: <01GX0TCCRG9U8Y55SX@INNOSOFT.COM> Message-id: <1438*/S=Eppenberger/O=switch/PRMD=SWITCH/ADMD=ARCOM/C=CH/@MHS> X-VMS-To: IN%"ietf-madman@INNOSOFT.COM" "ietf-madman" Content-identifier: 1438 Content-type: TEXT/PLAIN; CHARSET=US-ASCII Content-transfer-encoding: 7BIT X400-Content-type: P2-1984 (2) X400-MTS-identifier: [/PRMD=SWITCH/ADMD=ARCOM/C=CH/;930415102536] X400-Originator: Eppenberger@switch.ch X400-Recipients: ietf-madman@innosoft.bitnet Status: O Dear colleagues, here is a copy of my notes from the MADMAN BOF. I will work in comments any time but those I receive within the next 24 hours will make it probably for the IETF proceedings. Kind regards, Urs Eppenberger, SWITCH ------------------------------------------------------------------------------- Draft Minutes of the Mail and Directory Management (MADMAN) BOF Columbus, March 30, 1993 Chair: Steve Kille, ISODE Consortium Minutes: Urs Eppenberger, SWITCH Documents Application monitoring MIB MTA monitoring MIB DSA monitoring MIB Charter of the group Minutes of the Washington SAM BOF (Understanding of SNMP MIBs) Agenda 19:30 - 22:00 Minutes of the SAM BOF Review of the charter Review of the documents Minutes of the SAM BOF The minutes are accepted without any comments Review of the charter o Monitoring of Message Store is added to the charter. Message Store does include X.400(88) Message Store, POP, IMAP... o The management of the applications is not a working item for the group. The MIB enables MTA and DSA managers to detect when things go wild by monitoring the most important system variables. o The application monitoring MIB is planned to be finalised for the Amsterdam IETF. o The DSA and MTA monitoring MIBs are planned for the fall IETF. o Work on the Message Store MIB will start afterwards. o The IFIP working group on email management has a more general approach. Good relations are ensured by cross participation of working group members and the sharing of documents. Review of the Application monitoring MIB o It is based on Steves original proposal and should form a framework for all network applications. o A name string will be added o A version indication per application is needed o The concept on representation of processes in the host MIB will be checked. o There are already two other MIBs defined, a very short one from HP and one from CDC, concentrating on Mail and Directory. Review of the DSA monitoring MIB o Additional variables: operations pending, active change operations to other DSAs, current number of requests from clients in process, counters for replications, fail indication Review of the MTA monitoring MIB o Support now for multiple MTAs on a single system is added o A new abstraction has been added: channel This is to get some figures out of very simple MTAs. A problem is deferred delivered messages and alarms set on 'oldest message per channel' o A counter for rejected messages is added o A separate document is needed, also as RFC, to define object identifiers as a basis for identifying TCP services based on their port number. o Glenn volunteers to work on a layered model of the MTA monitoring approach. An association layer which receives and sends the messages and a higher level which routes and modifies (in case of gateway functions) the messages. The Message Store MIB o Monitor UAs connected to the message store, submission, retrieval, messages locked in the store o The MIB should support capacity planning o Ed Reed volunteered to work on a document to study the issues involved.   Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa12270; 21 Apr 93 15:32 EDT Received: from CNRI.RESTON.VA.US by IETF.CNRI.Reston.VA.US id aa12263; 21 Apr 93 15:32 EDT Received: from THOR.INNOSOFT.COM by CNRI.Reston.VA.US id aa25992; 21 Apr 93 15:32 EDT Received: from INNOSOFT.COM by INNOSOFT.COM (PMDF V4.2-12 #1336) id <01GX9TETXRSG8Y58O2@INNOSOFT.COM>; Wed, 21 Apr 1993 12:05:38 PDT Received: from haig.cs.ucl.ac.uk by INNOSOFT.COM (PMDF V4.2-12 #1336) id <01GX9TENAFUO8Y59BE@INNOSOFT.COM>; Wed, 21 Apr 1993 12:05:27 PDT Received: from glengoyne.isode.com by haig.cs.ucl.ac.uk with Internet SMTP id ; Wed, 21 Apr 1993 20:05:04 +0100 Received: from glengoyne.isode.com by glengoyne.isode.com with SMTP (PP) id <12163-0@glengoyne.isode.com>; Wed, 21 Apr 1993 20:07:26 +0100 Date: Wed, 21 Apr 1993 20:07:24 +0100 Sender:ietf-archive-request@IETF.CNRI.Reston.VA.US From: Steve Kille Subject: Draft Charter To: ietf-madman@innosoft.com Cc: Marshall Rose Errors-to: ned+madman-errors@INNOSOFT.COM Resent-message-id: <01GX9TEU1ITE8Y58O2@INNOSOFT.COM> Message-id: <12161.735419244@isode.com> X-VMS-To: IN%"ietf-madman@INNOSOFT.COM" X-VMS-Cc: IN%"mrose@dbc.mtview.ca.us" "Marshall Rose" MIME-version: 1.0 Content-type: text/plain; charset=us-ascii Content-transfer-encoding: 7BIT Phone: +44-71-721-7582 Status: O I've been working with Marshall Rose (the new area director) on revised charter for the working group. This has taken the output of the Columbus meeting, and Marshall's input to align the work with other network management area activities. We are both keen to get the group chartered rapidly, and to submit the charter to the IESG. Let Marshall and myself have any comment on this before close of business on Friday (UK time). Steve DRAFT DRAFT DRAFT DRAFT DRAFT DRAFT DRAFT DRAFT Mail and Directory Management (madman) Charter Chair(s): Steve Kille Network Management Area Director(s) Marshall NM-Directorate Consultant: Marshall Rose Mailing lists: General Discussion:madman@innosoft.com To Subscribe: mailserv@innosoft.com In Body: subscribe ietf-madman Archive: host=innosoft.com, dir=IETF-MADMAN, name=ARCHIVE.TXT Description of Working Group: The Mail and Directory Management working group is chartered to define four MIB modules: one for generic application monitoring, one for message relays (either SMTP or X.400 based), one for OSI Directory service (X.500), and a fourth for message stores. The MIB modules will provide basic monitoring capabilities, and will be consistent with the SNMP framework and existing SNMP standards. Goals and Milestones: May 93 Post internet-drafts for discussion for generic application monitoring (APPL), message relays (MR) and directory (DS) monitoring. Jul 93 Submit APPL, MR and DS internet-drafts to IESG for standards track evaluation. Jul 93 Post internet-draft for discussion for message store (MS) monitoring. Nov 93 Submit MS internet-draft to IESG for standards track evaluation.   Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa16368; 20 Apr 93 20:38 EDT Received: from CNRI.RESTON.VA.US by IETF.CNRI.Reston.VA.US id aa16364; 20 Apr 93 20:38 EDT Received: from THOR.INNOSOFT.COM by CNRI.Reston.VA.US id aa04963; 20 Apr 93 20:38 EDT Received: from INNOSOFT.COM by INNOSOFT.COM (PMDF V4.2-12 #1336) id <01GX8PXUEDSG8Y4ZHS@INNOSOFT.COM>; Tue, 20 Apr 1993 17:15:39 PDT Received: from MCIGATEWAY.MCIMail.com by INNOSOFT.COM (PMDF V4.2-12 #1336) id <01GX8PXOEKPC8Y58TA@INNOSOFT.COM>; Tue, 20 Apr 1993 17:15:27 PDT Received: by MCIGATEWAY.MCIMail.com id aa11361; 21 Apr 93 0:05 GMT Received: from mcimail.com by MCIGATEWAY.MCIMail.com id bp07991; 20 Apr 93 22:40 GMT Date: Tue, 20 Apr 1993 21:44 +0000 (GMT) Sender:ietf-archive-request@IETF.CNRI.Reston.VA.US From: Action Motivation <0004367585@mcimail.com> Subject: NETWORK MANAGEMENT SHOWCASE FEATURING LIVE MULTI-VENDOR DEMOS To: NOMS To: OIW Security SIG To: Electronic Mail Management Group To: OIW NMSIG To: Regional Workshop To: ANSI To: MITRE-NADIS To: MITRE-OSI To: MITRE To: OSI Mgt Implementation To: OSI API To: IETF MADMAN Errors-to: ned+madman-errors@INNOSOFT.COM Resent-message-id: <01GX8PXUHLJ68Y4ZHS@INNOSOFT.COM> Message-id: <03930420214430/0004367585NA3EM@mcimail.com> X-VMS-To: IN%"NOMS@tdd.sj.nec.com" "NOMS" Content-type: TEXT/PLAIN; CHARSET=US-ASCII Content-transfer-encoding: 7BIT Status: O ============================================================= THE THIRD INTERNATIONAL SYMPOSIUM ON INTEGRATED NETWORK MANAGEMENT ============================================================= A UNIQUE OPPORTUNITY TO VIEW FIRST HAND THE LATEST IN NETWORK MANAGEMENT TECHNOLOGY ** WHERE: April 18-23,1993, The Sheraton Palace Hotel, San Francisco, CA ** WHAT: STATE-OF-THE-ART TECHNOLOGY CENTERS demonstrating new and emerging network management technologies, EXPERT SPEAKERS, THOUGHT-PROVOKING PANEL SESSIONS,IN-DEPTH TUTORIALS,TECHNICAL PAPERS - Gary Francis,James Herman, Marshall Rose, and more....... (See Communications Week ad of April 5, p. 48 for more details) ** WHO WILL BE THERE: 40 LEADING VENDORS discussing, demonstrating, and distributing literature about their network management products and capabilities, members of the research, development and academic communities, sophisticated end users, all with the COMMON OBJECTIVE OF MOVING NETWORK MANAGEMENT TECHNOLOGY FORWARD. ** VENDOR DAY: Wednesday, April 21, a full day devoted to Vendor presentations, a unique opportunity to hear directly from the vendor community. ** SHOWCASE FLOOR OPENS TUESDAY, APRIL 20 AT 12:00 P.M. ** LIVE NETWORK -- SEE THE LATEST IN SNMPV2, RMON, OSI, OMNIPOINT, AND NETWORK MANAGEMENT APPLICATIONS. Registration Information: ISINM '93 Registration The Sheraton Palace Hotel 2 New Montgomery Street San Francisco, CA 94105-3402 Call +1 415 543-0671 Fax +1 415-543-6021 EMAIL amotive@mcimail.com Network Management Week Discount still available (includes Symposium registration and four Tutorial Sessions), Symposium Registration (excludes Tutorials), SHOWCASE FLOOR PASSES AND SPECIAL VENDOR DAY PASSES ARE AVAILABLE. Sponsored by the International Federation for Information Processing (IFIP) with participation by the Institute of Electrical and Electronics Engineers (IEEE) Communications Society and support from the Institute for Educational Services (IES).   Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa16868; 27 Apr 93 18:43 EDT Received: from CNRI.RESTON.VA.US by IETF.CNRI.Reston.VA.US id aa16864; 27 Apr 93 18:43 EDT Received: from THOR.INNOSOFT.COM by CNRI.Reston.VA.US id aa20692; 27 Apr 93 18:43 EDT Received: from INNOSOFT.COM by INNOSOFT.COM (PMDF V4.2-12 #1336) id <01GXIDRZHB7K8Y5BYB@INNOSOFT.COM>; Tue, 27 Apr 1993 15:15:17 PDT Received: from ics.uci.edu by INNOSOFT.COM (PMDF V4.2-12 #1336) id <01GXIDRH4PDS8Y56LQ@INNOSOFT.COM>; Tue, 27 Apr 1993 15:14:50 PDT Received: from nma.com by q2.ics.uci.edu id ai14522; 27 Apr 93 14:52 PDT Received: from localhost by odin.nma.com id aa06329; 27 Apr 93 12:39 PDT Date: Tue, 27 Apr 1993 12:39:40 -0700 Sender:ietf-archive-request@IETF.CNRI.Reston.VA.US From: Einar Stefferud Subject: RE: MADMAN In-reply-to: Your message of "Tue, 27 Apr 1993 10:39:45 EDT." <9304270742.aa28907@q2.ics.uci.edu> X-Orig-Sender: stef@nma.com To: "Bernard A. Ferret" Cc: Bernard Ferret , IETF-MADMAN , Steve Kille , Ned Freed Errors-to: ned+madman-errors@INNOSOFT.COM Reply-to: Stef@nma.com Resent-message-id: <01GXIDRZK9B68Y5BYB@INNOSOFT.COM> Message-id: <6327.735939580@odin.nma.com> X-VMS-To: IN%"bernard@dacnet.com" "Bernard A. Ferret" X-VMS-Cc: IN%"bernard@stubby.dacnet.com" "Bernard Ferret", IN%"ietf-madman@INNOSOFT.COM" "IETF-MADMAN", IN%"s.kille@isode.com" "Steve Kille", IN%"ned@INNOSOFT.COM" "Ned Freed" MIME-version: 1.0 Content-type: text/plain; charset=us-ascii Content-transfer-encoding: 7BIT Status: O The address of IETF-MADMAN mailing list is in the CC, along with addresses for Steve Kille (Chair) and Ned Freed (Editor). Subscription address is: "IETF-MADMAN Administrivia" Cheers...\Stef From message Tue, 27 Apr 93 10:39:45 EDT: }Hi Stef, }What is the address of MADMAN? }Thanks }Bernard }